yah if i were storing XML id go with this kind of thing too (although
i prefer straight adjacency list with a "root id" node to store
groups of XML tags...since when are you going to load only part of
the XML for a particular document ?)
with regards to nested sets, what id really *love* to use is this,
but i dont know how to do it without PL/SQL (it is amazing with oracle):
http://www.dbazine.com/oracle/or-articles/tropashko4
On May 8, 2006, at 6:40 PM, Luís Bruno wrote:
Michael Bayer wrote:
like if i hired you and said, "we have to store XML docs, heres
our DTD" youd go and make a table for every DTD element ?
Just a friendly note to tell you I'm a rabid fan of the nested set
model to store hierarchical data (this case, the document structure).
In (the longshot) case you haven't seen it:
http://www.developersdex.com/gurus/articles/112.asp
--
Luís Bruno
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Sqlalchemy-users mailing list
Sqlalchemy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
