• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: strange EO inheritance issue
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: strange EO inheritance issue


  • Subject: Re: strange EO inheritance issue
  • From: Sacha Michel Mallais <email@hidden>
  • Date: Thu, 3 Aug 2006 14:24:04 -0700

On Aug 3, 2006, at 2:05 PM, Patrick Robinson wrote:

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? :-)

Hi Patrick,

I've recently tried a similar thing to no success. It appears that there is a WO bug WRT propagating PKs to tables that are not correlation tables (a correlation table is a table mapping two entities in a many-to-many relationship with no other attributes -- if B had attributes B.aPK and B.cPK, and no others, it would be a correlation table). What I did was to throw out propagation and instead use a standard integer PK.

HTH,


sacha


-- Sacha Michel Mallais Code Sculptor Global Village Consulting Inc. http://www.global-village.net/ PGP Key ID: 7D757B65 AIM: smallais Roses are #FF0000, violets are #0000FF, all my base are belong to you.


_______________________________________________ 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
  • Follow-Ups:
    • Re: strange EO inheritance issue
      • From: Patrick Robinson <email@hidden>
References: 
 >strange EO inheritance issue (From: Patrick Robinson <email@hidden>)

  • Prev by Date: Re: Event update ; notice
  • Next by Date: Re: strange EO inheritance issue
  • Previous by thread: Re: strange EO inheritance issue
  • Next by thread: Re: strange EO inheritance issue
  • Index(es):
    • Date
    • Thread