Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Coredata and faulting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Coredata and faulting

Subject: Coredata and faulting
From: email@hidden
Date: Tue, 29 Nov 2005 14:35:23 -0800

I have a question concerning the implications of implementing search in a coredata application containing a potentially large data set. When searching a particular entity for say a string value, when coredata fetches the objects, does it un-fault the entire object or simply the values associated with the specific key?

As an example, I have an entity with several attributes some maybe binary, which would/could incur a performance penalty when un-faulted, so if I searched with a simple query based on a string value, say ENITY.NAME, would coredata only unfault the specific data associated with that key? Or would it un-fault the entire object?

I'm wondering because this would effect the way I design my data model...

Thanks in advance.

Andre _______________________________________________ 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 Follow-Ups: Re: Coredata and faulting From: Scott Stevenson <email@hidden> Prev by Date: Unified instead of Brushed Metal NSDrawer Next by Date: Re: NSArrayController usage Previous by thread: Re: Unified instead of Brushed Metal NSDrawer Next by thread: Re: Coredata and faulting Index(es): Date Thread