Re: XMLType performance

> When a schema is highly volatile, e.g. tax-return forms, XML beats
> relational hands down. Tables are so...square.
> Also XML documents can contain electronic signatures. Shredding and
> reconstitution can cause serious headache to that end.
> What I see is that XML is stored in the database, but the core reference
> attributes are pulled out into regular column for quick processing (and
> RI enforcement, ..).
>
> The right tool for the right job.
> Cheers
> Serge

The XML structure is hierarchical in nature. Haven't we shown over the last umpteen years that hierarchical databases are have more than enough issues in which to make relational databases a much more attractive solution? There will always be the exceptions to the rule, but give me relational databases over hierarchical databases almost any day. To that end, why store XML data in XML form in a relational database? One is just forcing a hierarchical database into a relational model.

Granted, if you are storing an XML document, then I can see the need to store this in an Oracle database no different than if I were storing a PDF or Word document in the database, as a single instance of an entity. And I only want to be querying for the entire document. I do not want to be pulling pieces out of that XML document. If I'm going to do that, then I'd much rather store the attributes in a relational table.

Cheers,
Brian

-- 
===================================================================

Brian Peasland
dba_at_nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown

-- 
Posted via a free Usenet account from http://www.teranews.com