imo this is on the to-do-list. as a workaround you can still use extents and super-references but you should take care that the primary key is UNIQUE within the class hierarchy.
for further details hava look at the thread: "Extents and the various inheritance hierarchy mappings" in ojb-dev.
jakob
Peter Wieland wrote:
hi peter,
you could try to define an extent in classdescriptor of Address pointing to PersonAddress. BUT the problem is that extents and super-references do not go together well. you may end up with instances of the wrong class. the support for mapping one class to multiple tables needs improvement ;)
jakob
Hi,
well, I would have prefered another answer but at least it is a clear answer. Are there any plans to spent the work needed on the joined-table per subclass mapping in the near future?
Peter
--------------------------------------------------------------------- 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]
