Re: Removing an object from an inverse (not deleting) does not remove from the other side?
Re: Removing an object from an inverse (not deleting) does not remove from the other side?
- Subject: Re: Removing an object from an inverse (not deleting) does not remove from the other side?
- From: Chris Hanson <email@hidden>
- Date: Wed, 28 Dec 2005 23:46:26 -0800
On Dec 28, 2005, at 1:41 PM, email@hidden wrote:
Is the standard behavior of removing an object from a many-to-many
with inverse relationship using NSArrayController not to remove the
object from the other side of the relationship?
When you remove an object from a relationship in Core Data, the
inverse relationship is maintained for you automatically.
This is completely orthogonal to whether you use a controller object
to manipulate your objects or whether you write code yourself to
manipulate them. As long as you're manipulating the relationship
correctly, the appropriate behavior should result with respect to
both it and its inverse.
Here are some things to look at:
(1) Is your array controller set to entity mode?
(2) Does your array controller have the correct entity set?
(3) Does your array controller have its managedObjectContext binding
configured and bound to a valid managedObjectContext?
(4) Are you using a custom managed object class for your entity?
(5) Does your managed object model specify your custom managed object
class for your entity?
-- Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden