Lists Home |
Date Index |
I know of at least one that was doing ok: B-Bop. They got bought out when they were not growing as fast as their VCs where hoping...
Also, if you for example look at how we design our primary XML index in SQL Server to encode the XML document structure on top of a relational database, you will see that it can be done, but in order to operate on it efficiently, it is much better if you extend your relational algebra with specific operations over the relational storage structure.
As to indexing XML natively, there are many papers published at the academic database conferences such as SIGMOD, WISE, VLDB, XSym, XIME-P etc that describe different approaches.
> -----Original Message-----
> From: Michael Kay [mailto:email@example.com]
> Sent: Tuesday, November 29, 2005 12:52 PM
> To: 'Peter Hunsberger'
> Cc: 'Timo Hildén'; firstname.lastname@example.org
> Subject: RE: [xml-dev] Indexing solution for native XML database
> > Sure, a relational database might not be the best fit for a given
> > hierarchical structure. But for other cases the fit may be as good or
> > better than any other database....
> I was under the impression the OP was trying to design a relational
> to hold arbitrary XML documents, not to hold a specific document. In other
> words, to implement a hierarchical database on top of a relational
> I don't think that's a good way of implementing a hierarchical database. I
> apologize that I don't have time to write a detailed rationale for that
> view, but it's based on a lot of experience, including expensive failures
> projects that tried to do exactly that.
> Michael Kay
> 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
> manager: <http://www.oasis-open.org/mlmanage/index.php>