Re: failing to provide new primary keys
Re: failing to provide new primary keys
- Subject: Re: failing to provide new primary keys
- From: Lachlan Deck <email@hidden>
- Date: Wed, 19 Nov 2008 07:17:25 +1100
On 19/11/2008, at 2:57 AM, Mike Schrag wrote:
Propagate primary key turned on for all relationships where the
FK is part of the PK?
Is this a general check that can be performed? If your EO has a
composite primary key then the inverse relationship of each PK
join must be propagates primary key?
I can't think of an exception to this when the PK is a combination
of FKs. But I can see people making a composite key of non-FK
values. I could name names... ;-)
so if every pk attribute is an fk, then this should be true, is that
the consensus?
I think so.
I'm thinking though (in this age of optimisations) that this means you
have to map the reverse relationship in order for the pk to propogate.
Either way it seems to me that it'd make more sense if the option to
propogate (or labelled 'propogated') was on the relationship from the
join rather than to the join. I'm not sure at this stage how that
would be dealt with by the database context.
Thoughts?
with regards,
--
Lachlan Deck
_______________________________________________
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