hi peter,
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
Hi Peter,
You might want to try declaring PersonAddress as an extend in the
class-descriptor for Address (see the Advanced OR Mapping Tutorial on
the website). I haven't tried this myself, but I was reading that
section of the tutorial last night and I think an extent might solve
your problem.
: Thursday, December 04, 2003 9:23 AM
To: [EMAIL PROTECTED]
Subject: RE: Problem mapping inheritance hierarchy using joined tables
for subclasses
Try refresh=false on the super reference.
Does not work either. I tried
refresh=false
auto-retrieve=false
auto-delete=false
auto-update
Well, that's what I tried resulting in a StackOverflow error. I guess it has
to do with the auto-update, auto-delete and auto-retrieve attributes of the
super reference-descriptor in the subclass. Could anyone tell what
settings for those attribute are needed/possible for a correct mapping of
Hi Peter,
Try refresh=false on the super reference.
Wally
-Original Message-
From: Peter Wieland [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 8:50 AM
To: [EMAIL PROTECTED]
Subject: RE: Problem mapping inheritance hierarchy using joined tables
for subclasses
Well
Try refresh=false on the super reference.
Does not work either. I tried
refresh=false
auto-retrieve=false
auto-delete=false
auto-update=false
on the super reference. But I stell get the StackOverflowError when
querying:
Hi Peter,
You will need to add PersonAddress as an Extent of Address if you want
PersonAddress to be in the seach domain of a query for class Address.
Wally
-Original Message-
From: Peter Wieland [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2003 4:22 AM
To: [EMAIL PROTECTED]
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
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
