• 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: compound primary key ("failed to provide new primary keys")
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: compound primary key ("failed to provide new primary keys")


  • Subject: Re: compound primary key ("failed to provide new primary keys")
  • From: Chuck Hill <email@hidden>
  • Date: Sat, 14 Jun 2008 16:08:46 -0700


On Jun 14, 2008, at 3:57 PM, Gavin Eadie wrote:

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.


Nope. That is what Owns Destination does for a to-one, mandatory relationship.


But Selects are not mandatory, in fact in this business model they are scarce.

Why do they even have a class? If it is just two keys, just use an EOGenericRecord and flatten the relationships. Then all you need to do is to say user().addToFavoriteAdverts(ad); I don't think you should even need the addObjectToBothSidesOfRelationshipWithKey. That might cause too much faulting for popular ads.



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

Seems to me like it should be no trouble at all.

Chuck



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

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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: compound primary key ("failed to provide new primary keys")
      • From: Gavin Eadie <email@hidden>
    • Re: compound primary key ("failed to provide new primary keys")
      • From: Gavin Eadie <email@hidden>
References: 
 >compound primary key ("failed to provide new primary keys") (From: Gavin Eadie <email@hidden>)
 >Re: compound primary key ("failed to provide new primary keys") (From: Johann Werner <email@hidden>)
 >Re: compound primary key ("failed to provide new primary keys") (From: Gavin Eadie <email@hidden>)

  • Prev by Date: Re: compound primary key ("failed to provide new primary keys")
  • Next by Date: WOLips BUG: can't configure frameworks set used in application
  • Previous by thread: Re: compound primary key ("failed to provide new primary keys")
  • Next by thread: Re: compound primary key ("failed to provide new primary keys")
  • Index(es):
    • Date
    • Thread