Re: Problem with relationships in Core Data
Re: Problem with relationships in Core Data
- Subject: Re: Problem with relationships in Core Data
- From: "I. Savant" <email@hidden>
- Date: Tue, 26 Sep 2006 13:27:47 -0400
I'm not sure if I'm understanding you clearly, but if you make a
change in one array controller that affects whether objects are
represented in another, those changes will not be reflected in most
(all?) cases until you perform another fetch in the second controller.
Without more information (or rephrasing the existing information),
I'm afraid I have nothing else to offer ... Sorry. :-)
--
I.S.
On Sep 26, 2006, at 1:23 PM, Remco Poelstra wrote:
Both deletion rules are set to nullify. Doing a fetch on the
arraycontroller doesn't work. But isn't the object which needs
updating allready removed from the arraycontroller when I do a
remove and than a fetch?
Thanks again,
Remco Poelstra
Op 26-sep-2006, om 19:04 heeft I. Savant het volgende geschreven:
It sounds as though your array controller is simply not
reflecting the changes made via the other. This is a common
problem. You should at least try forcing a fetch to see if that
fixes your problem.
Otherwise, try checking your deletion rules in your model to
verify the action taken is the one you want / expect.
--
I.S.
On Sep 26, 2006, at 12:56 PM, Remco Poelstra wrote:
Hi,
Thanks for your reply.
I'm sorry, but I don't see how fetching an object solves my
problem of nullify'ing the relationship from B to A. Or do you
mean that that method enables me to manually nullify the
relationship?
Thanks in advance,
Remco Poelstra
Op 26-sep-2006, om 17:40 heeft I. Savant het volgende geschreven:
See NSArrayController's -fetch: method.
--
I.S.
_______________________________________________
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