• 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 09:29:44 -0500

I've got a little further. I made both model versions identical. Then reset the file back to the old version. Doc opened OK. Add one attribute to the file, reset the file, and I now get:

Error Domain=NSCocoaErrorDomain Code=256 "The file could not be opened."

from initWithContentsOfUrl:... Not very useful. Nothing from Core Data about why the file couldn't be opened. I do get the "blah.new" file adjacent to my data file, so I know migration has been attempted.

I swear Core Data costs me as much time as it saves me :-)

Graham.

On Aug 10, 2008, at 12:36 AM, Graham Perks wrote:

Wow, versioning looks SO much better in 10.5. I had my own code for 10.4, I am glad to delete it.
_______________________________________________

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 versioning woes (From: Graham Perks <email@hidden>)

  • Prev by Date: CGImage failed to write Exif Auxiliary metadata to image
  • Next by Date: Re: Core Data versioning woes
  • Previous by thread: Core Data versioning woes
  • Next by thread: Re: Core Data versioning woes
  • Index(es):
    • Date
    • Thread