Re: refreshObject:mergeChanges: vs. stale transient properties
Re: refreshObject:mergeChanges: vs. stale transient properties
- Subject: Re: refreshObject:mergeChanges: vs. stale transient properties
- From: mmalcolm crawford <email@hidden>
- Date: Mon, 8 Aug 2005 15:03:28 -0700
On Aug 8, 2005, at 12:32 PM, Jim Correia wrote:
When a managed object context is saved, I sync the the other ones
by faulting the objects with refreshObject:mergeChanges:.
If I pass NO for mergeChanges, then committed but unsaved edits in
the target context are lost, so I'm passing YES.
That is the gotcha - if you pass YES the transient properties are
unaffected. But I have a transient property which is the cached
decoded value of a binary attribute. If that attribute was the one
which was saved in the alternate context, my transient property is
now stale and needs to be relcalculated.
What is the recommended way to handle this situation?
<http://developer.apple.com/documentation/Cocoa/Reference/
CoreData_ObjC/Classes/NSManagedObject.html#//apple_ref/doc/uid/
TP30001171-BBCCEDDC>
mmalc
_______________________________________________
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