• To: "'Peter Hunsberger'" <peter.hunsberger@g...>
• Subject: RE: Indexing solution for native XML database
• From: "Michael Kay" <mike@s...>
• Date: Wed, 30 Nov 2005 21:59:55 -0000
• Cc: <xml-dev@l...>
• In-reply-to: <cc159a4a0511301331r7d03b0a7m6f22661233c63491@m...>
• Thread-index: AcX19W3tXkem3FEuSL2/c6VNzZ5T9gAAMoBQ

> 2) there's often a need to mix tree models with standard relational
> data.  In our case 90% of the data fits a relational model very well. 
> The 10% that doesn't is critical and it can't easily be separated out
> into something else.
> 
> For the latter case, what kind of approach do you recommend?

Sure, you often have to make compromises, using the optimal technology for
each part of a problem is probably not optimal overall.

I started out by saying that if I was building an XML database then I
wouldn't by choice build it on top of a SQL database, and I stick with that.

Michael Kay
http://www.saxonica.com/

• References:
  • Re: Indexing solution for native XML database
    • From: Peter Hunsberger <peter.hunsberger@g...>

• Prev by Date: Re: Indexing solution for native XML database
• Next by Date: Re: Common Word Processing Format
• Previous by thread: Re: Indexing solution for native XML database
• Next by thread: Question on Allowing null values iin DTD
• Index(es):
  • Date
  • Thread