I am changing the model of my Core Data app in a big way for the next update, and custom migration is definitely needed. After reading Apple's docs on migration policy subclasses, I find it very convoluted and wondered if there is an easier way. I am thinking, why not just bring up the data in the old context/model, and bring up a blank context with the new model, and copy object one by one into the new context/model and perform any needed logic in between? This way, I can even make use of logic in my NSManagedObject subclasses to construct data in the new model instead of working with the complex mechanism in migration policy. Has anyone tried something like this with any success?
Yi _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
