Object to Relational??!?

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.
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.
I know that SQL server can create a database from an XML Schema, but nowhere
does it say how it handles extension and restriction types.

Received on Monday, 16 September 2002 20:40:50 UTC