Forcing Core Data to save attribute changed behind its back?
Forcing Core Data to save attribute changed behind its back?
- Subject: Forcing Core Data to save attribute changed behind its back?
- From: Sean McBride <email@hidden>
- Date: Mon, 23 Jul 2012 18:03:19 -0400
- Organization: Rogue Research Inc.
Hi all,
I have a managed object where one of the attributes is quite large and so when I change it, instead of the usual setAttribute:newValue I mutate the object directly. Of course, Core Data does not know that I've done this. I'm looking for a way to tell it. (Otherwise, if the thing is mutated after the document is first saved, Core Data cleverly skips updating this attribute.)
I've tried:
- setAttribute:sameValue
- will/didChangeValueForKeyPath: but that's not a sufficient 'kick'
Any other suggestions?
Thanks,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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