Spitting out XML (was RE: Will XML eat the web?)

[Bill la Forge]

>Sometimes XML can represent the database itself if the database is
>very small (i.e. it would traditionally be stored as a flat ASCII file
>and batch-processed with Perl rather being stored in an RDBM): that's
>not really what sales wonks would call an enterprise-strength
>solution, but I (for example) use it for my own record-keeping.


If the XML is broken into subtrees, might that then add to the scalability
of this aproach? 

Think about b-trees for a bit. Couldn't we develop analogous algorithms
for transparently managing the size of a fragment? 

Anyone interested in doing a native-XML database? This would be a great
project for Open Source Software development!

Bill



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/
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)