Re: CoreData issue when updating a file format
Re: CoreData issue when updating a file format
- Subject: Re: CoreData issue when updating a file format
- From: mmalcolm crawford <email@hidden>
- Date: Wed, 11 May 2005 11:12:31 -0700
On May 11, 2005, at 10:40 AM, SA Dev wrote:
Rather, we're all wondering (myself included) just how to handle
the actual coded act of intelligently differentiating between the
'old' and 'new' model at load time
This was answered early on:
The best thing to do is likely to be to add a metadata flag to the file:
(1) Put a version number in the metadata of your stores. (Of
course, the lack of a version number key being present is
indicative of version 1. :)
(2) When opening the store, first grab the metadata and check the
version #. You don't need a model (or even the type of the store)
to grab the metadata.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden