Re: store management for Document Based Core Data application
Re: store management for Document Based Core Data application
- Subject: Re: store management for Document Based Core Data application
- From: Matthew Johnson <email@hidden>
- Date: Tue, 12 Dec 2006 19:29:24 -0600
So, the question is, what's the best way to deal with this?
Should I just get rid of the relationship from Entity-A to Entity-B?
Would it make sense to have only one context but the store
coordinator have multiple stores?
Any ideas or comments are appreciated.
My understanding from reading the documentation is that cross-store
relationships are not directly supported. I believe you need to
persist the object id for the destination object of the relationship.
In your case you would persist the Entity-A object id as an attribute
on the Entity-B object and then use fetched properties to dynamically
get the related objects.
One question that may help if you continue an attempt at cross-store
relationships - do you have the delete rule for Entity-B set to null
the relationship on the Entity-A side?
Also, if you do indeed get cross-store relationships working please
let us know.
Regards,
Matthew
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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