Dr Robert Sanderson wrote:
If we download and store those records in a relational table of any complexity, then every time there is a change to the schema, the tables need to be rebuilt. This would consume a lot of time and effort, rather than possibly having to change an XPath value.
The only thing that is certain in this world is change.
To use an OOo centric example, if documents were stored in a relational database and an element's content model in the schema changed, we would have a nightmare situation. In an XML database with appropriate schema version metadata, this is almost trivial.
I dont consider myself to be an expert in this field .. but to me you seem to skip over mentioning what you are pitting against eachother here.
On one side we have an approach which makes it easy of data structuring versus the ease of retrieval, especially of related information.
If I wouldnt be so young I might be reminded of a similar situation just the other way around a few decades ago :-)
regards, Lukas Smith [EMAIL PROTECTED] _______________________________ BackendMedia www.backendmedia.com [EMAIL PROTECTED]
Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin
Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
