FROM : Andrew Merenbach
DATE : Mon Jul 31 20:47:42 2006
Thanks so much, Ryan. I hadn't any idea about that--now that I knew
what to look for, a perusal of the docs quickly turned up the notion
that I needed to override -managedObjectModel in my persistent
document subclass.
Appreciatively,
Andrew
On Jul 31, 2006, at 10:11 AM, Ryan Britton wrote:
> The default model-loading code for the Core Data templates
> generates a merged model from all of the models found in the app.
> Unless you've changed this to load a specific model, this is likely
> the problem you're running into.
>
>
>
> On Jul 31, 2006, at 9:43 AM, Andrew Merenbach wrote:
>
>> Hi, all. I've a Core Data document-based app that needs document
>> migration support, and I've found the Core Recipes example
>> absolutely invaluable. I have all the parts, as far as I can
>> tell, fully in place. I made my own migration framework, linked
>> it, ran my program, and... nothing. I get the following error--
>>
>>> Can't merge models with two different entities named 'Record'
>>
>> --where Record is the name of one of my entities. I have multiple
>> model files, one for each intended version of my documents; and
>> unticking the inclusion checkbox in Xcode for all of them (in my
>> framework) causes my program to run just fine.
>>
>> I'm pretty sure that I understand this much: including two Core
>> Data model files with any identical entity names would pose a
>> problem.
>>
>> What I don't get is this: the Core Recipes Migration example also
>> has a framework (MigrationFramework) that includes multiple model
>> files, both of which share an identical entity name. How on earth
>> can I be able to run the "Migrator" target in the Migration
>> example, which includes the framework, and not get the same
>> error? I'm positive that I've set up my project in the same way.
>>
>> Is there some build-setting checkbox that I'm missing? Some
>> inclusion or role setting? Something?
>>
>> Many thanks, all,
>> Andrew
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Cocoa-dev mailing list (<email_removed>)
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>>
>> This email sent to <email_removed>
>
DATE : Mon Jul 31 20:47:42 2006
Thanks so much, Ryan. I hadn't any idea about that--now that I knew
what to look for, a perusal of the docs quickly turned up the notion
that I needed to override -managedObjectModel in my persistent
document subclass.
Appreciatively,
Andrew
On Jul 31, 2006, at 10:11 AM, Ryan Britton wrote:
> The default model-loading code for the Core Data templates
> generates a merged model from all of the models found in the app.
> Unless you've changed this to load a specific model, this is likely
> the problem you're running into.
>
>
>
> On Jul 31, 2006, at 9:43 AM, Andrew Merenbach wrote:
>
>> Hi, all. I've a Core Data document-based app that needs document
>> migration support, and I've found the Core Recipes example
>> absolutely invaluable. I have all the parts, as far as I can
>> tell, fully in place. I made my own migration framework, linked
>> it, ran my program, and... nothing. I get the following error--
>>
>>> Can't merge models with two different entities named 'Record'
>>
>> --where Record is the name of one of my entities. I have multiple
>> model files, one for each intended version of my documents; and
>> unticking the inclusion checkbox in Xcode for all of them (in my
>> framework) causes my program to run just fine.
>>
>> I'm pretty sure that I understand this much: including two Core
>> Data model files with any identical entity names would pose a
>> problem.
>>
>> What I don't get is this: the Core Recipes Migration example also
>> has a framework (MigrationFramework) that includes multiple model
>> files, both of which share an identical entity name. How on earth
>> can I be able to run the "Migrator" target in the Migration
>> example, which includes the framework, and not get the same
>> error? I'm positive that I've set up my project in the same way.
>>
>> Is there some build-setting checkbox that I'm missing? Some
>> inclusion or role setting? Something?
>>
>> Many thanks, all,
>> Andrew
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Cocoa-dev mailing list (<email_removed>)
>> Help/Unsubscribe/Update your Subscription:
>> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>>
>> This email sent to <email_removed>
>
| Related mails | Author | Date |
|---|---|---|
| Andrew Merenbach | Jul 31, 18:43 | |
| Ryan Britton | Jul 31, 19:11 | |
| Andrew Merenbach | Jul 31, 20:47 |






Cocoa mail archive

