Re: Core Data : Managed Object Models : Configurations, Versions
Re: Core Data : Managed Object Models : Configurations, Versions
- Subject: Re: Core Data : Managed Object Models : Configurations, Versions
- From: Jerry Krinock <email@hidden>
- Date: Wed, 16 Jun 2010 19:51:15 -0700
On 2010 Jun 16, at 17:59, Dave Fernandes wrote:
> Let's say I have an app with data model X, and a plugin with data model Y. So the app with the plugin installed has data model X+Y. Now let's say this app + plugin is used to create a document. The questions is: If this document is opened by someone who does not have the plugin installed, is there anyway for the app to open the document and only load the entities from data model X?
If this is possible, it would certainly center on overriding -[NSManagedObjectModel isConfiguration:compatibleWithStoreMetadata:].
On 2010 Jun 16, at 09:27, Kyle Sluder wrote:
>> Then: Why do we have four methods for merging models? Why would a developer want models to be merged at runtime?
>
> Frameworks, for one.
Score one for Kyle. Still seems odd though, that ...mergedModels: is so commonly used.
And we still don't have an answer on the magic I questioned in my previous post, how Core Data knows not to merge models that are different versions of the same model. By deduction, I presume this is based on reading the VersionInfo.plist in the .momd resource.
But why does the documentation for all those mergedModelXXX not state that "different versions of the same model are not merged"?
And although reverse-engineering VersionInfo.plist appears to be trivially easy, why is there no API?
_______________________________________________
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