Re: Forcing Core Data to save attribute changed behind its back?
Re: Forcing Core Data to save attribute changed behind its back?
- Subject: Re: Forcing Core Data to save attribute changed behind its back?
- From: Sixten Otto <email@hidden>
- Date: Tue, 24 Jul 2012 05:31:22 -0700
On Mon, Jul 23, 2012 at 3:03 PM, Sean McBride <email@hidden> wrote:
> when I change it, instead of the usual setAttribute:newValue I mutate the object directly.
> - will/didChangeValueForKeyPath: but that's not a sufficient 'kick'
Out of random curiousity, does this big mutable object you're updating
change in a way Core Data would see? Does the object's "before" state
-isEqual: its "after" state?
_______________________________________________
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