[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: XML design of Database
Vun Kannon, David <dvunkannon@xxxxxxxx> wrote: > Andreas' presentation is clear on some things, not on others. > > XML as normalised relational tables means table per element, not table per > nesting level. Er, there is no one true definition, folks :-) One table per document is also fine, and for some applications wil give a thousand-fold or more performance improvement. When you've spent an hour waiting for a document to be served by a million-dollar SPARC running Oracle, you know that the "obvious" relational schema isn't always the most appropriate. In my book (forthcoming) on the subject, I actually seggest that if you have XML documents, you store them outside a database altogether in many situations, using a relational database for metadata such as author's name, and sometimes for extracted data such as a list of parts. Lee -- Liam Quin, Barefoot Computing, Toronto; The barefoot programmer Ankh on irc.sorcery.net, http://www.holoweb.net/~liam/ co-author, The XML Specification Guide, Wiley Inc. forthcoming: The Open Source XML Database Toolkit, Wiley, 2000 XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|