Re: awakeFromFetch : when it is called ?
Re: awakeFromFetch : when it is called ?
- Subject: Re: awakeFromFetch : when it is called ?
- From: mmalcolm crawford <email@hidden>
- Date: Mon, 16 Jan 2006 09:48:59 -0800
On Jan 16, 2006, at 12:39 AM, Eric Morand wrote:
I had some problem with the term "fetched". I thought the
"executeFetchRquest..." method was actually a fetch. But it is not.
The object are fecthed only when I'm trying to access its
properties/relationships.
Fetched objects (that is, those that are instances of the entity that
is fetched, and that meet the criteria given by the fetch predicate)
are fully instantiated -- they are not faults.
"If you execute a fetch using executeFetchRequest:error:, it always
fetches the data and caches the results in memory. If you fire a
fault in the result array from executeFetchRequest:error:, Core Data
will not go back to the store. Converting a fault into a complete
managed object is very fast with a cache hit—it is basically the same
as normal instantiation of a managed object."
By the wat, are fetched and unfaulted synonyms ? It seems to me but
there may be some subtlenesses I've not yet discover.
"Core Data avoids the term "unfaulting" because it is confusing.
There's no "unfaulting" a virtual memory page fault. Page faults are
triggered, caused, fired, or encountered. Of course, you can release
memory back to the kernel in a variety of ways (vm_deallocate,
munmap, sbrk). Core Data describes this as "turning an object into a
fault"."
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/
Articles/cdFaultingUniquing.html#//apple_ref/doc/uid/TP30001202>
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