• 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: Gavin Eadie <email@hidden>
  • Date: Sun, 15 Jun 2008 01:32:15 -0400

Lucky I love learning!  Things I learned:

... in WebObjects, if it's difficult, you're doing it wrongly!

... Chuck is always right (even if he doesn't mention flattening in his book).

... Apple's documentation for EOF at WO version 4.5 rocks!

... Start with the model and let the database take care of itself.

WebObjects standard flattened many-to-many relationship was what I was missing. I was focused on the legacy tables I was working with and they were muddying the waters. My new code is now working perfectly, is smaller than before, easier to read and I'm happy again. Thanks to those who helped, thanks to those who didn't wonder out loud how I ever got this far without comprehending some of the simpler aspects of EOF ... Gav


On Jun 14, 2008, at 7:08 PM, Chuck Hill wrote:

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

_______________________________________________ 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: Chuck Hill <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>)
 >Re: compound primary key ("failed to provide new primary keys") (From: Chuck Hill <email@hidden>)

  • Prev by Date: ReportMill can't find Framework?
  • Next by Date: Re: compound primary key ("failed to provide new primary keys")
  • 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