Re: Batch faulting
Re: Batch faulting
- Subject: Re: Batch faulting
- From: mmalcolm crawford <email@hidden>
- Date: Wed, 16 Nov 2005 16:47:09 -0800
On Nov 16, 2005, at 4:41 PM, Timothy Larkin wrote:
Yes, but this doesn't work. I've tried it. Objects that are faults
before the suggested fetch are faults after the fetch. In any
event, "EOF supports pre-fetching and batch faulting of
relationships, Core Data does not." (From the CoreData FAQ") And my
search transverses a relationship.
Object faulting is not the same as whether the data has been read
from the database. Object faulting simply means whether or not a
given managed object has all its attributes populated and is ready to
use. If [isFault] returns [NO], then the data must be in memory.
However, if [isFault] returns [YES], it does not imply that the data
is not in memory. The data
may be in memory, or it may not, depending on many factors
influencing caching.
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.
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