Re: CoreData migration and file change
Re: CoreData migration and file change
- Subject: Re: CoreData migration and file change
- From: Dan Grassi <email@hidden>
- Date: Wed, 4 Feb 2009 15:25:49 -0500
After having read everything I can google I have only progressed to:
"The document “project.xml” has been moved."
I am doing a manual migration so I do not call
configurePersistentStore:... as Miguel suggests but have tried
setFileModificationDate as suggested and I only get a slightly better
but still confusing message as above.
I have tried FSExchangeObjects but that did not help.
I have not tried moving the migration code to a -writeToURL: or -
saveToURL: method and calling that if I need to migrate, surely there
is a less convoluted way.
Any help will be greatly appreciated.
Dan
On Feb 4, 2009, at 12:42 PM, Barry Wark wrote:
I recently asked a related question on StackOverflow:
http://stackoverflow.com/questions/380076/manual-core-data-schema-migration-without-document-changed-warning
.
The answer should help you out.
On Tue, Feb 3, 2009 at 9:08 AM, Dan Grassi <email@hidden> wrote:
I have a CoreData application and am migrating the data store.
When the
user opens an old store the migration happens automatically
creating a new
file. The problem is when the user saves the first time after the
migration
he gets the message: "This document's file has been changed by
another
application since you opened or saved it."
What is the correct procedure for handling the file change or how
can I
avoid this message?
Thanks,
Dan
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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