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: James Dessart <email@hidden>
- Date: Wed, 11 May 2005 13:56:43 -0400
On 5/11/05, SA Dev <email@hidden> wrote:
> All very true and valid, but I don't think whether it's a 'new'
> model is what's in question here. 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, then
> properly handling the merge or migrate scenarios. Even in good DB
> design, migrations are sometimes unavoidable.
Right, however the semantics of migrations are very application
specific. You have both models, and you try to load a file first with
the new model, if that fails you load it with the old model, then use
your application specific migration path. How can Apple know, in
advance, what data you want to migrate?
--
James Dessart
Blog: http://skwirl.net/
Software dev. services: http://skwirl.com/
_______________________________________________
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