• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Core data model configuration & Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core data model configuration & Leopard


  • Subject: Re: Core data model configuration & Leopard
  • From: Aurélien Hugelé <email@hidden>
  • Date: Mon, 29 Oct 2007 07:05:44 +0100

I've seen no info about the "isIndexed" attributes migration.
I have model working on Tiger with no index placed on any attributes, but now, I would like to index some attributes. How does it affect models compatibility?
Is it managed by the migration manager ? is it safe to simply check this checkbox in Xcode modeler?


Thanks.


On 29 oct. 07, at 02:12, mmalc crawford wrote:


On Oct 28, 2007, at 5:45 PM, email@hidden wrote:

I have a relatively simple core data non-document application that runs fine under OS 10.4. However, when I run the same app on OS 10.5, it cannot open the data file. I get the error "The model configuration used to open the store is incompatible with the one that was used to create the store." I traced the first time this was called to the code below, the call to addPersistentStoreWithType. The method "managedObjectContext" has not changed since I created the project with Xcode. Does anyone have any suggestions as what I can do to get my app to read the store in OS 10.5?

Has the *model* changed in any way? With the new versioning and migration feature in 10.5, Core Data takes the following into account:
Core Data’s perspective on versioning is that it is only interested in features of the model that affect persistence. This means that for two models to be compatible:


• For each entity the following attributes must be equal: name, parent, isAbstract, and properties.
className, userInfo, and validation predicates are not compared.


• For each property in each entity, the following attributes must be equal: name, isOptional,isTransient, isReadOnly, for attributes attributeType, and for relationshipsdestinationEntity, minCount, maxCount, deleteRule, and inverseRelationship.
userInfo and validation predicates are not compared.


(see Core Data Model Versioning and Data Migration Programming Guide > Versioning).

Not all this information is maintained in the store, but it *may* be that you managed to get away with something on Tiger that isn't now allowed on Leopard.

mmalc

_______________________________________________

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



Aurélien, Objective Decision Team




_______________________________________________

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


References: 
 >Core data model configuration & Leopard (From: email@hidden)
 >Re: Core data model configuration & Leopard (From: mmalc crawford <email@hidden>)

  • Prev by Date: [Moderator] Re: Failing downloads (was: Connections not made with new IB)
  • Next by Date: Re: NSTableView behavior change in Leopard
  • Previous by thread: Re: Core data model configuration & Leopard
  • Next by thread: Re: Core data model configuration & Leopard
  • Index(es):
    • Date
    • Thread