Re: Core Data versioning woes
Re: Core Data versioning woes
- Subject: Re: Core Data versioning woes
- From: Steve Steinitz <email@hidden>
- Date: Mon, 11 Aug 2008 11:12:45 +1000
Hi Graham,
On 10/8/08, Graham Perks wrote:
>>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?
>
>The document that's open post-migration is the "foo~" version -
>the backup of the old file. So of course it can't save it. How
>did I mess things up to get the tilde backup version open
>following migration? The upgraded file "foo" is correctly in
>place, and can be edited once opened normally.
Perhaps you feel like you are talking to yourself but I assure you
myself and others are watching your progress. The migration, in its
current state, presents many difficulties and deserves further attention
from Apple.
I eventually had to roll back to my 10.4 migration which is working well
but is messy and hard to maintain. So, we're counting on you and other
brave pioneers to pave the way.
Steve
ps. one special problem I have is that I don't want the migration to
happen automatically because four users share the same database. The
file-level information you describe may help that.
_______________________________________________
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