• 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: Core Data modeling question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data modeling question


  • Subject: Re: Core Data modeling question
  • From: Jerry Krinock <email@hidden>
  • Date: Fri, 4 Dec 2009 05:58:42 -0800

On 2009 Dec 04, at 04:37, Mark Smith wrote:

> However... when I do a unidirectional one to many relationship, the compiler (rightly) complains as I do not have inverse relationships.  However, it makes no sense to me to clutter up my address object with pointers back to "company" and "contact" and perhaps any other entity down the line that may need an "address."

The conventional solution to this "problem" is to ignore your common sense and just add the inverse relationships to your data model anyhow.  I don't believe that any pointers will be created unless Core Data feels like it needs them while running, which if your common sense is correct, it won't.

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Core Data modeling question (From: Mark Smith <email@hidden>)

  • Prev by Date: Re: beginSheetForDirectory:file:types:modalForWindow:modalDelegate:didEndSelector: on 10.6
  • Next by Date: Re: NSHTTPCookieStorage to implement "Sign Out" functionality
  • Previous by thread: Core Data modeling question
  • Next by thread: IKImageBrowserView D&D with IKImageBrowserNSDataRepresentationType
  • Index(es):
    • Date
    • Thread