Re: Core Data: inverse relationship not updated until next Run Loop
Re: Core Data: inverse relationship not updated until next Run Loop
- Subject: Re: Core Data: inverse relationship not updated until next Run Loop
- From: Jim Correia <email@hidden>
- Date: Fri, 12 Mar 2010 00:59:54 -0500
On Mar 11, 2010, at 8:11 PM, Eric Lin wrote:
> In using Core Data, I was under the impression that if I do this:
>
> [department addEmployeesObject:employee] // department now has 1 employee
> [moc deleteObject:employee]
>
> Then department will end up with no employees, assuming that the inverse
> relationship is set correctly.
>
> But it turns out within the same run loop, if I inspect
> [department.employees count], then the value is 1. But in the next run loop,
> the value becomes 0, which is what it should be.
>
> Is my observation accurate or is something wrong?
Deletes are propagated at the end of he current event, or at save time, depending how the MOC is configured.
Jim
_______________________________________________
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