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: email@hidden
- Date: Fri, 17 Feb 2006 16:01:44 -0800
mmalcolm crawford wrote:
Chris Hanson wrote:
Thanks guys for the help.
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 [...]
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.
See also <http://developer.apple.com/documentation/Cocoa/Conceptual/
CoreData/Articles/cdPerformance.html#//apple_ref/doc/uid/TP40003468-
SW5>.
I thought I read that, but I guess I missed it, or maybe it was
revised...
I think a fetch predicate could be easier, but I want the objects
only in a specific relationship. Not in the whole store....
Also, at most, I would only pull one object out of the search because
each object would have a unique name.
So, I guess the balance to find is, search speed vs. ease of coding....
I also didn't want to factor out the blob data into an entity
separate from its "name" identifier, so I thought a cache, even when
the object is faulted, could be an answer.
So I want to avoid this:
[OWNER ENTITY]<-->[BLOB NAME ENTITY]<--->[BLOB ENTITY]
Thanks for all you help BTW.
Andre
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
Andre
email@hidden
_______________________________________________
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