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

Core Data versioning woes


  • Subject: Core Data versioning woes
  • From: Graham Perks <email@hidden>
  • Date: Sun, 10 Aug 2008 00:36:34 -0500

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

I got a quick demo versioning app going, thanks to some excellent advice at http://www.timisted.net/blog/archive/core-data-migration/. The docs should really include that NSDocument override for configurePersistentStoreCoordinatorForURL:.

Anyway, in my real application I am having trouble. I created a new model version with an extra dummy field. Created the mapping file. And now I get an empty document shown with the following error in the console:

*** -[NSConcreteValue count]: unrecognized selector sent to instance 0x16577ca0

I get that line twice. Any ideas? I don't know where to even start with that one.

My 10.4-style versioning code I optimistically removed from the project. Please don't make me bring that mess back :-)

Thanks,
Graham Perks.
_______________________________________________

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>
    • Re: Core Data versioning woes
      • From: Graham Perks <email@hidden>
  • Prev by Date: Web links with PyObjC
  • Next by Date: Core Data, dynamic accessors and compiler warnings
  • Previous by thread: Re: Web links with PyObjC
  • Next by thread: Re: Core Data versioning woes
  • Index(es):
    • Date
    • Thread