Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


[xsl] Theory question: Node trees and SQL.

From: Phillip B Oldham <phillip.oldham@---------->
To:
Date: 7/4/2006 12:16:00 PM
Hi all



I posted a question a few months ago asking how to use trees stored in
SQL using Joe Celko's "nested sets" model and re-create the tree in HTML
(and got a very quick response - thanks guys).

I'd like to ask what in your opinion is the best way to store trees in
SQL for use with XSL translation. At the moment, using the nested set
model, my XML is similar to the following:

<departments>
    <department name="Stationery" left="1" right="2" />
    <department name="Misc" left="3" right="6" />
    <department name="Haberdashery" left="4" right="5" />
</departments>

Which should produce:
   Stationery
   - Misc
   Haberdashery

While it works fine for the output, the current storage method is
volatile, and is causing us problems in manipulation.

Can anyone suggest better techniques (other than using a native XML
database)?

Thanks,
Phill


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent