Re: When exactly does a fault get fired?
Re: When exactly does a fault get fired?
- Subject: Re: When exactly does a fault get fired?
- From: Chris Hanson <email@hidden>
- Date: Fri, 17 Feb 2006 08:41:58 -0800
On Feb 17, 2006, at 2:14 AM, Andre wrote:
Here's my reason. I'm working on a way to have a specific entity,
that is accessed by a key that names it. So, the entity actually
may contain a binary data or a large blob of text. Since I choose
the object I want based on its "name" set a runtime (not the entity
name), I want to scan through the set of items and get the one with
the name I want, without tripping up the fault, as this can be very
slow if there were a lot of objects to go over... imagine going
through a list of 40+ objects, and some may have large RAW images
attached, then coredata needs to fetch each one out of the
persistent store just to find its name...... seems pretty inefficient.
You can use a predicate on a fetch request to do this efficiently, so
long as the possible objects you might fetch are all instances of the
same entity.
-- Chris
_______________________________________________
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