Re: What is the logic of storing XML in a Database?
From: Karen Hill <karen_hill22_at_yahoo.com>
Date: 28 Mar 2007 15:56:49 -0700
Message-ID: <1175122609.672629.42770_at_d57g2000hsg.googlegroups.com>
> Standardized XML transport formats are commonly used for representing
> messages. Consider a problem space where messages are sent from a
> front office system to a back office system, and middleware needs to
> keep a repository of messages to support auditing and playback. In
> that case it would make perfect sense to strip out any fields required
> for querying, and store them plus the message. Storing all the fields
> relationally would not meet any business objective, and it might not
> be possible to reliably reproduce the original message from the
> relational representation.
Date: 28 Mar 2007 15:56:49 -0700
Message-ID: <1175122609.672629.42770_at_d57g2000hsg.googlegroups.com>
On Mar 27, 7:10 am, "Daniel" <danielapar..._at_gmail.com> wrote:
>
> Standardized XML transport formats are commonly used for representing
> messages. Consider a problem space where messages are sent from a
> front office system to a back office system, and middleware needs to
> keep a repository of messages to support auditing and playback. In
> that case it would make perfect sense to strip out any fields required
> for querying, and store them plus the message. Storing all the fields
> relationally would not meet any business objective, and it might not
> be possible to reliably reproduce the original message from the
> relational representation.
Yet, the SQL:2003 standard has SQL/XML. In fact, DB2, Oracle and now even PostgreSQL have these features, and they are not just for "representing messages". It seems that the Kool-Aid these developers drank is going to make Date faint! Look at this link on the upcoming PostgreSQL 8.3 version which will have SQL:2003 SQL/XML support:
http://developer.postgresql.org/index.php/XML_Support Received on Thu Mar 29 2007 - 00:56:49 CEST