Hi Fritz,

I have it running that way in one of my applications. The user base is small (< 50 users), so I might not have yet had the chance to discover magic not happening. I also invested a lot of time in the model process, to avoid too many changes.

My changes, that worked well, included addition of new properties/ fields. No changes to relationships so far. These will be harder I guess.

I also have a manual upgrade process for older version files - still dating back to 10.4. The manual migration isn't too hard if you can't rely on the automagic process.

Hth,

Volker

Am 26.10.2009 um 17:00 schrieb Fritz Anderson:

I'm about to unleash a Core Data-based application, and I'm sure the schema will change in later versions. The Core Data Model Versioning and Data Migration Programming Guide seems to say that migrating a store from one version to another, at least in simple cases, is magical: The application embeds the historical MOMs, with one of them marked "current," and when a store built to an earlier model is opened, it is (in SIMPLE cases) migrated to the current model.

Is this the case?

In that event, is it necessary to do anything at all (other, perhaps, than attaching a version string for human consumption) in version 1 to prepare for migration?

        — F

_______________________________________________

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/volker_lists%40ecoobs.de

This email sent to volker_li...@ecoobs.de

_______________________________________________

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

Reply via email to