On Nov 16, 2010, at 12:32 PM, Ray Kiddy wrote: > > On Nov 16, 2010, at 6:32 AM, David Avendasora wrote: > >> Hi all, >> >> I have a Many-to-Many relationship and the join table does _not_ have a >> compound PK. It has a normal PK with a dataType of Long. The FKs that >> represent the to-One relationships on the join table are simply FKs and not >> part of the PK. >> >> I would like to flatten the toMany relationships, but when I add an object >> to the relationship and EOF tries to create a row in the join table it >> tries to create a compound PK for the join table, even though the Model is >> very clear as to what the PK is. >> >> Is this the normal EOF behavior to ignore the Model's PK settings for the >> join table and just assume that the PK is compound? >> >> I've always avoided flattened relationships because every time I try to use >> them I run into problems and give up and go back to regular relationships >> because it seems the work that flattened relationships save always gets >> offset by the limitations they impose (either that or my limitations of >> ability to use them properly). >> >> Dave _______________________________________________ > > Riffing off a problem I had recently, I would guess that the tool (ever so > helpfully) set the 'propagate primary key' on the relationships going into > the join table. If that property is set on the two relationships, that may be > enough to confuse things.
I checked that and no, Propagates Primary Key isn't set on any of the 4 relationships involved. Another detail is that I'm using Oracle and sequences to create the primary key, so I'm looking into a problem with that sequence as well. Dave _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
