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

Borden, Jonathan jborden at
Fri Feb 5 04:09:53 GMT 1999

Clark Evans wrote:

> Therefore, I picture a DOM implementation
> using thousands of nested queries to generate
> the same tree that a few large queries would have
> handled nicely.  In this case, the database
> engine would not be able to take advantage
> of aggregate indexing and elimination
> algorithems. In effect, negating the benifits
> of having corporate information in a relational
> database.  *smile*

	This is a good point, the problem with the relational model is that the few
large queries flatten the hierarchy into a table. Another approach is to use
data shaping to create hierarchical recordsets. 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.

> Anyway, I just can't picture using DOM in this
> context as an interface to a relational database.
> For this case I feel using a stream-oriented solution
> on the server with an object-oriented event processing
> system on the client seems the better approach.

	Again, the db/OLAP vendors might be able to squeeze some performance out of
the interface that we couldn't once the data has left the engine. just a

Jonathan Borden

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

More information about the Xml-dev mailing list