Re: Core Data Cascade delete rule sometimes doesn't
Re: Core Data Cascade delete rule sometimes doesn't
- Subject: Re: Core Data Cascade delete rule sometimes doesn't
- From: "Doug Knowles" <email@hidden>
- Date: Mon, 11 Feb 2008 16:27:07 -0500
Well, per the tech note, I do call processPendingChanges before I do the
manual validation (which catches undeleted now-invalid objects). And my
understanding is that processPendingChanges is automatically called on a
Save, which is where I first encountered the invalid records.
The release note implies that Core Data is doing some work (like propagating
deletions) at the top of the event loop; could it be that the processing of
incoming AppleEvents is short-circuiting whatever Core Data normally does?
On Feb 11, 2008 2:19 PM, Adam Swift <email@hidden> wrote:
> Have you tried manually calling "processPendingChanges" after the
> delete? Cascade deletes are not processed immediately:
>
>
> http://developer.apple.com/releasenotes/Cocoa/CoreDataReleaseNotes/index.html
>
>
_______________________________________________
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