Re: Core Data versioning woes
Re: Core Data versioning woes
- Subject: Re: Core Data versioning woes
- From: Graham Perks <email@hidden>
- Date: Sun, 10 Aug 2008 10:00:25 -0500
Astonishing: The migration happens for sure: I end up with a "foo.new"
file adjacent to my original file. If I delete the original and open
the .new file, it is the migrated version complete will all data,
including the new attribute (with its default value) that I added in
the new data model version!
So the migration happened... I have a .new file which is the upgraded
file... but what would stop the upgrade process copying the .new file
over the original data file?
The original file is not locked or readonly. Isn't it supposed to
backup the old file to foo.~ ? That hasn't happened. Why not? No
useful errors in the console. Any ideas on what to check?
Cheers,
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