W3C home > Mailing lists > Public > xmlschema-dev@w3.org > October 2002

RE: Object to Relational??!?

From: Naren Chawla <naren_chawla@attbi.com>
Date: Fri, 4 Oct 2002 20:31:33 -0700
To: "Anthony B. Coates" <abcoates@TheOffice.net>, "xmlschema-dev" <xmlschema-dev@w3.org>
Message-ID: <AOEGLCJGIFANMEODKIBGMEDPCPAA.naren_chawla@attbi.com>

How about JDO (Java Data Objects) ?



-----Original Message-----
From: xmlschema-dev-request@w3.org
[mailto:xmlschema-dev-request@w3.org]On Behalf Of Anthony B. Coates
Sent: Wednesday, September 18, 2002 4:15 AM
To: xmlschema-dev
Subject: Re: Object to Relational??!?

** Reply to message from "Joe Warwick" <joe@icon101.com.au> on Tue, 17 Sep
10:38:44 +0800

> I would love to know if there is an industry standard way of mapping an
> inheritance typed object instance tree into a relational database while
> maintaining a high level of normalisation.

No.  Not a good workable one, anyway.

> What gets me is how to choose the point in the tree where flattening the
> objects is most efficient, yet causes least xml overflow blobs.
> Has anyone managed this task? It seems like it would be best to build an
> object oriented system on top of sql server through translation stored
> procedures.

This would only be suitable for small-scale usage, certainly not on an
enterprise system.  You would be coupling your database schema directly to
XML Schema, and if that Schema is an external one, version changes could be
unpredictable.  Also, you would probably need to support multiple Schema
versions simultaneously (2 at least), and my experience is that relational
databases don't make it particularly convenient (i.e. transparent) to use
multiple DB schema versions in the same database.

> I know that SQL server can create a database from an XML Schema, but
> does it say how it handles extension and restriction types.

Both SQL Server, Oracle, & DB2 are moving to native XML support.  I think
will negate any momentum to define a really good XML to relational mapping
it can be done at all).  No idea yet how "native XML" support in relational
databases will compare to purpose-built native XML databases, though.

Anthony B. Coates, Information & Software Architect
MDDL Editor (Market Data Definition Language)
Received on Friday, 4 October 2002 23:26:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:58 UTC