On 2010 Nov 16, at 09:48, Adam Swift wrote: > That the objects will be fetched as NSManagedObjects is documented in the > versioning & migration guide … Three-Stage Migration.
Thank you, Adam. I see that it says "the class of all entities is changed to NSManagedObject". However, I think that I'm probably not alone in wondering exactly what it means to ** change the class of an entity ** , and the programming implications of it, which I learned when exceptions were raised. > You should be able to use the standard KVC accessors during migration, > NSManagedObjects will respond to the foo/setFoo: accessors for properties > defined in your managed object model - Yes, unless, as I found, accessors have been overridden, and the overrides invoke methods which are not defined in NSManagedObject. > the accessors will perform better than valueForKey/setValue:forKey: (see > Dynamically-Generated Accessor Methods) Well, since migration only happens once in a lifetime of a database, I'm not too worried about it, unless it falls to zero, which is what happens when a "method does not respond to selector" exception is raised :( _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
