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

Core Data modeling question


  • Subject: Core Data modeling question
  • From: Mark Smith <email@hidden>
  • Date: Fri, 4 Dec 2009 07:37:18 -0500

Good morning,

I am trying to figure out the best way to model a Core Data relationship.

Essentially, I am trying to have an "Address" object that can be referenced by "Contacts" and "Companies."

In other words, contact entities should have multiple addresses (one to many), and company entities should have multiple addresses as well.

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."

Anybody solved this one and have some advice?  Is this a place for a "fetched property?"

Thanks in advance,

Best Regards,

Mark Smith



_______________________________________________

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

  • Follow-Ups:
    • Re: Core Data modeling question
      • From: Jerry Krinock <email@hidden>
  • Prev by Date: _NSLayoutTreeSetOutsideDrawsUponLineFragmentAtGlyphIndex
  • Next by Date: Re: Best way to hook into the run loop?
  • Previous by thread: _NSLayoutTreeSetOutsideDrawsUponLineFragmentAtGlyphIndex
  • Next by thread: Re: Core Data modeling question
  • Index(es):
    • Date
    • Thread