On Oct 1, 2010, at 10:02 PM, Jerry Krinock wrote: > > On 2010 Oct 01, at 10:44, Quincey Morris wrote: > >> Core Data implements Save As as a migration process using a mapping model >> that it constructs on the fly > > Eeek. I never knew that. >
I'm late to the game, but this is incorrect. The Save As functionality does not use the migration feature. Save As simply(?) loads all the objects, messes with the objectIDs, and saves to the new location. This means that all the standard rules for loading objects (ie don't touch relationships in awakeFromFetch) apply, and any business logic your classes implement on save will be triggered (unlike migration, which modifies the model to use NSManagedObject instead of custom classes). +Melissa _______________________________________________ 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
