[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XML-enabled databases, XQuery APIs

• To: Ronald Bourret <rpbourret@r...>
• Subject: Re: XML-enabled databases, XQuery APIs
• From: Peter Hunsberger <peter.hunsberger@g...>
• Date: Fri, 15 Apr 2005 14:23:23 -0500
• Cc: xml-dev@l...
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lkMwAXXAXLaIRyvTw7V4tmeF1yEWzK+3sexUI//3T0ohA7oIjRvbG4YpDRgJQtHnebK8s73dYwPG+747s2H0mDhTyR++1YX1hsh2xNm1kCiG67vqwN2+IHxXtHdWEBsbSGw66HqjXKL1gdHfwmDRLdeVuVizS/E6a0BcqPLd3Jg=
• In-reply-to: <42600E69.8000809@r...>
• References: <003001c54133$ae25d660$1601a8c0@DURANTE> <425FE648.2090506@r...> <cc159a4a05041510265cc2d696@m...> <42600E69.8000809@r...>
• Reply-to: Peter Hunsberger <peter.hunsberger@g...>

On 4/15/05, Ronald Bourret <rpbourret@r...> wrote:
> We're talking apples and oranges here.
> 
> What you're talking about is a generic set of relational tables like
> Elements, Attributes, Text, Comments, and ProcessingInstructions. 

Well, no, not in our case, but that's beside the point.

> This
> is generally considered to be a native XML database implemented on top
> of a relational database. In fact, this is roughly how SQL Server
> implements their XML data type.
> 
> What I'm talking about is a set of tables designed to store documents
> corresponding to a particular XML schema. For example, mapping a sales
> order document to the Sales, Items, Customers, and Parts tables. While
> such tables can, in theory, store things like sibling order, comments,
> and processing instructions, in practice they almost never do. This is
> generally known as "shredding".
> 
> One significant difference between the two is that the first in some way
> looks like an XML document while the second is indistinguishable from
> other relational data.

Given that any general XML schema has a direct mapping to things like
"Elements, Attributes, Text, Comments, and ProcessingInstructions"
you're examples aren't apples and oranges, they're different degrees
of normalization. Thus, the point is; if your going to "shred" you can
shred with as much fidelity to the XML model as you choose to
implement.  Whether you end up using a "native XML on top of
relational" schema or some other schema has little to do with the
issue.

-- 
Peter Hunsberger

• References:
  • XML-enabled databases, XQuery APIs
    • From: "Ken North" <kennorth@s...>
  • Re: XML-enabled databases, XQuery APIs
    • From: Ronald Bourret <rpbourret@r...>
  • Re: XML-enabled databases, XQuery APIs
    • From: Peter Hunsberger <peter.hunsberger@g...>
  • Re: XML-enabled databases, XQuery APIs
    • From: Ronald Bourret <rpbourret@r...>

• Prev by Date: Re: XML-enabled databases, XQuery APIs
• Next by Date: RE: XML-enabled databases, XQuery APIs
• Previous by thread: Re: XML-enabled databases, XQuery APIs
• Next by thread: Re: XML-enabled databases, XQuery APIs
• Index(es):
  • Date
  • Thread