Re: NSPredicate performance considerations
Re: NSPredicate performance considerations
- Subject: Re: NSPredicate performance considerations
- From: Prachi Gauriar <email@hidden>
- Date: Sun, 20 Nov 2005 21:37:19 -0500
On Nov 20, 2005, at 9:15 PM, Chris Hanson wrote:
On Nov 20, 2005, at 5:37 PM, Prachi Gauriar wrote:
Fetches are still a bit of a mystery to me, but since I've only
been playing Core Data for a day, I'll save those questions for
later. Thanks.
What do you find mysterious about them, relative to -
filteredArrayWithPredicate:?
Nothing at all relative to that method. I was just talking about
fetches in general. Like I said, I've had very little time to dig
into Core Data. I'm in that early stage where I'm still trying to
adjust to the new concepts in the framework... learning not to fight
it so much.
I'm using an old abandoned project of mine as an excuse to get into
Core Data (and avoid doing my grad school work ;-)). I have to
rethink the way I designed my classes, since my old design relied a
bit on having ordered collections. The good news is that this
redesigning process exposed other flaws in the design. The bad news
is that things I took for granted, e.g. arrays and dictionaries (with
arbitrary value types), aren't present out of the box in Core Data.
Anyway, fetching, faulting, and uniquing haven't really come up in
the little time that I've had to explore the tools and API. After I
have more time to deal with those aspects of the framework, I'm sure
things will become more clear. Thanks.
-Prachi
_______________________________________________
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