Re: compound primary key ("failed to provide new primary keys")
Re: compound primary key ("failed to provide new primary keys")
- Subject: Re: compound primary key ("failed to provide new primary keys")
- From: Gavin Eadie <email@hidden>
- Date: Sat, 14 Jun 2008 18:57:45 -0400
My reading would indicate that I don't want to "propagates primary key". If I do, then the creation of an Advert WILL always create a Select. But Selects are not mandatory, in fact in this business model they are scarce. The real world model is a bulletin board of advertisements whose users may select some favorite ads that they want to keep track of. So a boring ad will have no connecting Select, and someone who is not a frequent visitor may have no connecting Select. On the other hand a really interesting ad may have dozens of Selects (dozens of people putting it in their favorites), and a busy user may have dozens Selects (ads they are tracking). Any one Select contains only the pkeys of the Advert and Author (user) it relates. This may have been modeled badly seven years ago, but it's what I have to work with !! Gav
On Jun 14, 2008, at 2:55 PM, Johann Werner wrote: Hi Gavin,
did you check "Propagates Primary Key" on the Author and Advert entity?
jw
|
_______________________________________________
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