Hi Amita,
Amita Vadhavkar wrote:
For SDO Types -> XSD , there is XSDHelper.generate(List of Types) support
existing in SDO Impl.
Super. Thanks for the heads up.
For XSD-> DB Schema - I have a question, as far as SDO does not support
IDREF/KEYREF
in SDO definitions, how a containment relationship in XSD model can get
successfully translated
into referential integrity constraint (relationship) in a database?
It's a good question. Do you know whether the following cases are true (I'm
just assuming it at the moment)?
==============================
SDO > XSD > DB Schema
==============================
In this case the SDO to XSD transformation will only generate XSD types that
exclude attributes with the IDREF/KEYREF type, so the transformation does not
need to be done when going to DB Schema?
------------------------------
I'm also assuming this:
==============================
XSD > SDO
==============================
In this case the XSD to SDO transformation will map XSD IDREF/KEYREF types to a
corresponding SDO types.
-------------------------------
If these two are true, then it seems like the way SDO database schema creation via XSD >
DB Schema would be supported by doing XSD > SDO > XSD > DB Schema just to get a
clean mapping of SDO types.
Thoughts?
Thanks,
- Ole
For this (i.e. lack of IDREF) RDB DAS has provided <config>/<relationship>
where user can specify the
required information. And it is used during data access.
Regards,
Amita
On Jan 7, 2008 11:13 AM, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Hi,
I know Amita is looking into DB > XSD. I was wondering if there is any
work being done on XSD > DB? Also can the SDO implementation generate the
XSD if the SDO types are provided, enabling SDO Type > XSD > DB?
Thanks,
- Ole
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
