Re: refreshObject:mergeChanges: vs. stale transient properties
Re: refreshObject:mergeChanges: vs. stale transient properties
- Subject: Re: refreshObject:mergeChanges: vs. stale transient properties
- From: Jakob Olesen <email@hidden>
- Date: Sat, 5 Aug 2006 03:01:43 +0200
On 01/08/2006, at 9.18, Jakob Olesen wrote:
The problem is when implementing non-standard attributes as
described in the Core Data Programming Guide,
refreshObject:mergeChanges:YES no longer works as expected. The
documentation says that transient attributes are unaffected by
refreshObject:mergeChanges:YES, so when using "The Pre-calculated
Get" pattern you get the old value since it is cached in a
transient attribute.
I think, I finally managed a solution that makes transient attributes
behave like persistent attributes during refreshObject:mergeChanges:
Description here: http://www.2pi.dk/tech/cocoa/transient_properties.html
_______________________________________________
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