• 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 migration and non-optional transient relationships
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data migration and non-optional transient relationships


  • Subject: Re: Core Data migration and non-optional transient relationships
  • From: Jerry Krinock <email@hidden>
  • Date: Tue, 20 May 2014 10:18:30 -0700

On 2014 May 20, at 07:21, Sean McBride <email@hidden> wrote:

> As a test I made the relationship optional, then it no longer complains.

Consider leaving it that way, Sean.  The only effect I’ve ever had from setting Core Data properties to be non-optional is the creation of mysterious errors and exceptions like this during build-ups and tear-downs.  If you need stuff validated in your data model, write your own code to do it, in places where you can make an appropriate recovery.


_______________________________________________

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 migration and non-optional transient relationships (From: Sean McBride <email@hidden>)

  • Prev by Date: Re: Quartz Display Services & Retina Display Modes
  • Next by Date: Re: Core Data migration and non-optional transient relationships
  • Previous by thread: Re: Core Data migration and non-optional transient relationships
  • Next by thread: how to mumap memory from CoreGraphics?
  • Index(es):
    • Date
    • Thread