Hi all
I've been looking at the different methods for working with storing
trees in SQL.
At the moment, I'm looking at the 'Materialized Path' technique, and
have a couple of questions regarding XSL.
If I were to have a table along the following lines:
+----+---------------+------+
| id | name | path |
+----+---------------+------+
| 1 | About | 1 |
| 2 | Services | 2 |
| 3 | Environmental | 2.1 |
| 4 | Landscaping | 2.2 |
+----+---------------+------+
And this were converted to XML, eg:
<directories>
<item>
<id>1</id>
<name>About</name>
<path>1</path>
</item>
<item>
<id>2</id>
<name>Services</name>
<path>2</path>
</item>
... etc ...
</directories>
Would it be relatively easy to use the path to build a tree stucture? eg:
<directories>
<directory name="About"/>
<directory name="Services">
<directory name="Environmental" />
<directory name="Landscaping" />
</directory>
</directories>
Are there any disadvantages to using Materialized Paths?
Phill
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--