• 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 versioning woes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core Data versioning woes


  • Subject: Re: Core Data versioning woes
  • From: Graham Perks <email@hidden>
  • Date: Sun, 10 Aug 2008 13:44:25 -0500

So after some too-late coding and placing my NSLogs in the wrong place, I now find the normal Multiple Validation Errors. After dumping the extra messages in NSDetailedErrorsKey I see the offenders are items that are marked as transient but non-optional. They're set in my entity's awakeFromFetch but since my entity class isn't used during migration, these fields were never getting set. As non-optional, that's a validation error.

Setting those transient fields to optional made the migration work. Yippee!

Now when I save my document I get a sheet saying, "This document's file has been changed by another application since you opened or saved it", and asking if I want to save or not. Eh? What's that all about?

Someone else had the same warning: http://lists.apple.com/archives/applescript-users/2008/Feb/msg00401.html but no answer was offered there.

Any clues?

Graham.
_______________________________________________

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 versioning woes
      • From: Graham Perks <email@hidden>
References: 
 >Core Data versioning woes (From: Graham Perks <email@hidden>)
 >Re: Core Data versioning woes (From: Graham Perks <email@hidden>)

  • Prev by Date: Re: Lazy Loading of images
  • Next by Date: Re: Core Data versioning woes
  • Previous by thread: Re: Core Data versioning woes
  • Next by thread: Re: Core Data versioning woes
  • Index(es):
    • Date
    • Thread