Re: Adding CalendarStore.framework changes managed object model version?

FROM : Brad Willoughby
DATE : Wed Mar 26 03:33:34 2008

Thanks, Melissa.  That was it.

It looks like the template code generated by XCode in our AppDelegate 
from 2006 had this line:

managedObjectModel = [[NSManagedObjectModel mergedModelFromBundles: 
[allBundles allObjects]] retain];

Since we're using Leopard and Garbage Collection, I've changed it to 
the following and the error is now gone:

managedObjectModel = [NSManagedObjectModel mergedModelFromBundles:nil];

Cheers,
Brad
TinyPlanet Software, LLC
http://tinyplanetsoftware.com/

On Mar 25, 2008, at 6:11 PM, Melissa J. Turner wrote:
> Brad -
>
> At a guess, you're somehow pulling in CalendarStore.calmom into your 
> model. This might happen if you're doing [NSManagedObjectModel 
> mergedModelFromBundles: [NSBundle allBundles]], which is declared 
> dangerous for just this reason.
>
> +Melissa
>
> On Mar 25, 2008, at 17:56, Brad Willoughby wrote:
>

>> When I add /System/Library/Frameworks/CalendarStore.framework to my 
>> Leopard Core Data application in XCode 3.0 and click Build & Run, I 
>> get the following error:
>>
>> "The managed object model version used to open the persistent store 
>> is incompatible with the one that was used to create the persistent 
>> store."
>>
>> This makes no sense to me.  I have not touched my data model and 
>> can confirm that it has not changed via subversion's "svn status". 
>> I Googled and checked the cocoa-dev archives, but there's not much 
>> out there regarding the Calendar Store framework.
>>
>> Any ideas as to why adding CalendarStore.framework is causing this 
>> Core Data error?
>>
>> Cheers,
>> Brad
>> TinyPlanet Software, LLC
>> http://tinyplanetsoftware.com/