strange EO inheritance issue
strange EO inheritance issue
- Subject: strange EO inheritance issue
- From: Patrick Robinson <email@hidden>
- Date: Thu, 3 Aug 2006 17:05:23 -0400
I've got a rather strange EO inheritance question. I've got a
situation where I've set up single-table inheritance (with a
subclass "type" column) for 7 out of 8 of my subclasses; and a
separate table (with the same "type" column) that has a bunch more
columns for the 8th, just because I didn't want all those columns
sitting there empty for most of the rows (i.e. for the other 7
subclasses). Probably false economy, but be that as it may....
My structure looks like this:
A <-->> B <<--> C
C is modeled as an inheritance hierarchy using horizontal mapping,
and B is modeled as the inheritance hierarchy described above, using
mostly single-table mapping. There is a different subclass of B for
each corresponding subclass of C.
It all built just fine, but when it came time to save an object of my
new C subclass (the one that corresponds to the B subclass with its
own table), the primary key of the C subclass object did not
propagate to the B subclass object -- it was left as null. This is
done with Oracle, so there's an Oracle sequence C_SEQ that's used to
obtain C's primary key, and C_ID is the primary key of all C
subclasses. Normally, this propagates to the B subclass objects just
fine (with all the other B subclasses, that is), but it isn't working
with the B subclass that is set in EOModeler to use its own table.
Has anyone else tried to do this kind of thing, or am I just trying
to do something idiotic? :-)
--
Patrick Robinson
AHNR Info Technology, Virginia Tech
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden