Re: [Leopard] Core Data model versioning vs. NSPersistentDocument

FROM : mmalc crawford
DATE : Wed Nov 07 06:03:00 2007

On Nov 2, 2007, at 8:53 AM, Pierre Bernard wrote:

> There however seems to be a problem with my 1.0 files created under 
> Tiger. These files have no versioning information in their metadata. 
> Thus I had to resort to manual migration for those files. Guess that 
> ought to be documented.
>

Indeed.  I'm sure this and in particular the no-custom-classes issue 
were documented at some stage.  I don't know where those paragraphs 
went  :-(

> The only remaining problem I have is that for an odd reason the 
> migrated file is opened as "File.hspt~" rather than just "File.hspt" 
> which causes unwanted behavior on save later on. Any ideas how this 
> comes about?
>

Hmm, no.  Generally NSPersistentDocument doesn't seem very happy with 
the original implementation.  I've created an updated version that 
uses a subclass of NSDocumentController to perform the migration: <http://homepage.mac.com/mmalc/CocoaExamples/controllers.html
>.  I still don't think it's ideal, but thus far it seems better than 
the original.  I'll let you know if it changes significantly again.

mmalc