Re: CoreData faulting - does it rely on #self?
Re: CoreData faulting - does it rely on #self?
- Subject: Re: CoreData faulting - does it rely on #self?
- From: mmalcolm crawford <email@hidden>
- Date: Fri, 14 Apr 2006 16:38:09 -0700
On Apr 14, 2006, at 3:23 PM, Todd Blanchard wrote:
Still looking for the answer to "under what circumstances does core
data turn an object into a fault".
The intent of the previous paragraph I quoted was to make clear that
there is no way you can know this 100%. It's not clear why you would
need to ensure that no object is ever turned into a fault, but there
is again no way of assuring this 100%. Any time you touch any object
you can invoke willAccessValueForKey:, and you can set the staleness
interval for all objects to some time in the distant future, but at
some point an object may get turned into a fault... this is almost
certainly going to be as a result of you doing something, such as
saving changes (in a situation where there is a merge) or -- in
particular -- refreshing the data (see <http://developer.apple.com/
documentation/Cocoa/Reference/CoreData_ObjC/Classes/
NSManagedObjectContext.html#//apple_ref/occ/instm/
NSManagedObjectContext/refreshObject:mergeChanges:> -- note that the
documentation for this method does not adequately make clear that
this relates to faulting; this will be fixed).
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