CoreData: Incompatible model configuration problem...
CoreData: Incompatible model configuration problem...
- Subject: CoreData: Incompatible model configuration problem...
- From: Martin Linklater <email@hidden>
- Date: Mon, 17 Mar 2008 17:05:19 +0000
Hi. My Core Data Application is producing 'Incompatible model
configuration' errors which don't make sense to me.... Anyone got any
ideas ...?
My Application contains 4 data models - OptDataDump, Market, Local and
EVEAPI. Each of the entities in the data models are set to have the
configuration matching their respective models. So all the entities in
the 'OptDataDump' model are set to have 'OptDataDump' as their
configuration, all Local entities have the configuration 'Local' etc...
These models are combined into one MOM, which is then used to create 4
separate physical stores. The stores break down like this:
OptDataDump - SQLite
Local - SQLite
EVEAPI - XML
Market - SQLite
My problem is that when I change the model in the 'Local' data model I
get errors when I add persistent stores for the OptDataDump and Market
models. Yet these two data models have not changed. Is this normal ?
if (![persistentStoreCoordinator
addPersistentStoreWithType:NSSQLiteStoreType
configuration:@"OptDataDump" URL:dataDumpURL options:nil error:&error])
{
[[NSApplication sharedApplication] presentError:error]; <<
ERROR !
}
if (![persistentStoreCoordinator
addPersistentStoreWithType:NSXMLStoreType configuration:@"EVEAPI"
URL:EVEAPIURL options:nil error:&error])
{
[[NSApplication sharedApplication] presentError:error];
}
if (![persistentStoreCoordinator
addPersistentStoreWithType:NSSQLiteStoreType configuration:@"Market"
URL:marketURL options:nil error:&error])
{
[[NSApplication sharedApplication] presentError:error]; <<
ERROR !
}
if (![persistentStoreCoordinator
addPersistentStoreWithType:NSSQLiteStoreType configuration:@"Local"
URL:localURL options:nil error:&error])
{
[[NSApplication sharedApplication] presentError:error];
}
Creating the OptDataDump data takes about 2 hours on my machine so I
really don't want to have to keep on regenerating it every time I
change the data model in a different store...
Splitting my data into separate physical stores should mean that I can
change one without the others complaining, yes ? But this seems to be
a false assumption...
Can anyone help explain this behavior ?
Thanks.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden