Storing Lots of Fiddly Bits (was Re: What is XML for?)

[Clark Evans]

Jonathan Borden wrote:

> Another approach is to use data shaping to create hierarchical recordsets. 

This is what I did at Ford Motor Co., it gets messy quick. 
Even when the table is a snapshot.  Nothing like a big hierarchical 
table with 400 columns. *evil grin*

> A third approach is to let the database vendors optimize the queries 
> internally when XML is to be returned. This would seem to be the 
> optimal situation and data shaping/OLAP techniques fit here ... 
> remember "Arbor Software" is an OLAP vendor.

Nice.  This could be the beginnings of a 
HDBMS/RDBMS blend.  That'd be cool.

The danger is thinking that OLAP (HDBMS) is the
total answer.  It is almost impossible to avoid
duplication in a hierarchical database.  For
transaction processing, I bet that a relational
database will still be the best solution.

Ballance,

Clark

-----------------------------------------------------
software n : 
  1. written programs or procedures or rules and 
     associated documentation pertaining to the 
     operation of a computer system.
  2. applied philosophy

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)