Lists Home |
Date Index |
Oracle and DB2 have had this functionality since I was in college, see http://www.25hoursaday.com/StoringAndQueryingXML.html. SQL Server 2005 will have this functionality when it is released next year.
PITHY WORDS OF WISDOM
If you don't change your direction, you may end up where you were headed.
From: Owen Walcher [mailto:email@example.com]
Sent: Wed 8/25/2004 8:26 AM
To: Ken North; firstname.lastname@example.org
Subject: Re: [xml-dev] are native XML databases needed?
> > the fact is: if you have to round-trip your XML to a client in order to
> validate and or execute from it
> Are you suggesting that for retrieving XML an SQL server must pass its XML
> to the client, which executes the queries and validates documents -- as
> to the SQL server executing queries over XML data and validating
If a relational database has the capabilities to store XML documents without
knowing the structure apriori, and lets you query (using XPATH and/or
Xquery - not SQL), insert, update and delete nodes, subtrees or entire XML
documents within and across all these XML documents stored in the DB, then I
would put to you that you are not using a relational database, but what
Cache calls a post-relational database.
Do any of the big 3 (Oracle, DB2, MS SQL-Server) do that yet? Unless Yukon
functionality has changed, it is the only one I am aware of that will (and
that is not released yet). Please correct me if I am wrong. Relational
databases did the same thing to Object databases in the 90's (although I
think Objectstore still claims the worlds largest database :), and will
eventually get there with XML, but by then they really will be much more
than a relational database.
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription