• 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
Why is it wrong to have relationships without an inverse in Core Data?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Why is it wrong to have relationships without an inverse in Core Data?


  • Subject: Why is it wrong to have relationships without an inverse in Core Data?
  • From: Rick Mann <email@hidden>
  • Date: Fri, 21 Jun 2013 13:55:11 -0700

I find myself frequently wanting to do something like this:

Parent
  children     to-many to Child
  activeChild  to-one to Child

Child
  parent       to-one to Parent

But Core Data complains that activeChild is misconfigured because it doesn't have an inverse. But I have no need for an inverse, why does Core Data?

Thanks,


--
Rick




_______________________________________________

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: Why is it wrong to have relationships without an inverse in Core Data?
      • From: Ian Joyner <email@hidden>
    • Re: Why is it wrong to have relationships without an inverse in Core Data?
      • From: Kyle Sluder <email@hidden>
  • Prev by Date: Strange AVFoundation Errors
  • Next by Date: Re: Why is it wrong to have relationships without an inverse in Core Data?
  • Previous by thread: Strange AVFoundation Errors
  • Next by thread: Re: Why is it wrong to have relationships without an inverse in Core Data?
  • Index(es):
    • Date
    • Thread