core-data-migration

I've found documentation very limited and my problem solution nowhere. I need to add new entity (with relationship to existing one). Also add and rename some of attributes of existing entity. Lightweighted example: Old model has one entity Item with one attribute name . In new model I want to Item to have one new attribute dateAdded and rename name to title . At this point, if dateAdded would be optional or given default value, I could use lightweight migration feature. Correct me if I am wrong. But I also want to add new List entity with title attribute. And add to-many relationship. List can

I'm having a problem performing a lightweight migration when migrating from a store that is defined by two separate xcdatamodel files. In version 1.0 of my app, I had the models broken out into an analytics model, model-A, and everything else in model-B. When compiling, the models would be grouped together and everything proceeded smoothly. When working on the new version, 1.1, I upgraded model-B by adding a new model version to model-B and setting that new version as active. The issue arises when upgrading from 1.0 to 1.1. It seems Core Data checks the model store on disk (created by version

I'm trying to use the migration feature in CoreData. I've followed the Apple Documentation. I have a problem in the following method: /** Returns the managed object model for the application. If the model doesn't already exist, it is created by merging all of the models found in the application bundle. */ - (NSManagedObjectModel *)managedObjectModel { if (managedObjectModel != nil) { return managedObjectModel; } /* * NSInvalidArgumentException', reason: '*** -[NSCFArray insertObject:atIndex:]: attempt to insert nil' * 2010-02-17 16:27:15.338 Patrimoine[3037:207] */ managedObjectModel = [

I'm using Core Data's automatic lightweight migration successfully. However, when a particular entity gets created during a migration, I'd like to populate it with some data. Of course I could check if the entity is empty every time the application starts, but this seems inefficient when Core Data has a migration framework. Is it possible to detect when a lightweight migration occurs (possibly using KVO or notifications), or does this require implementing standard migrations? I've tried using the NSPersistentStoreCoordinatorStoresDidChangeNotification , but it doesn't fire when migrations

I'm really stuck here with upgrade testing from v1 to v2 of an iPhone application. I have IPA releases that I'm testing via ad hoc distribution via iTunes to my iPhone device, one for v1 of the app and one for v2. Note that: v1 installs runs fine on my device if I delete v1 and deploy v2 (so no migration) then it works fine when I deploy v2 whilst v1 is already there I get the error: "reason=Can't find model for source store" A snippet from the error...* reason=**Can't find model for source store**}, { URL = "file://localhost/var/mobile/Applications/AAAAF424-D6ED-40FE-AB8D-66879386739D