A problem I run into a lot with automatic migration using a Mapping Model is that I'm usually in the process of making incremental changes to my schema. So I create a Mapping Model, modify it as necessary, and things are fine.
But then if I change the schema again, that Mapping Model is not found. In this case, I added some optional attributes to an Entity, and so the Mapping Model no longer matches. But if I try to add attribute mappings for those new attributes, I can't. The Mapping Model editor only lets me choose from a set of destination attributes, and it doesn't show any of the new ones. I can create a new Mapping Model that picks those up, but then I lose the customizations I've done, which can be quite tedious and error-prone to reproduce. Does anyone have a solution for this? TIA, -- Rick Mann rm...@latencyzero.com _______________________________________________ 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