hi,
i want you to propose just an idea , a remark, on apple documentation is
said
The NSFetchRequest class is used to describe search criteria used to retrieve
data from a persistent store. implicitely you must record all of them and
update them sometimes
in your idea there is a l
On Feb 10, 2011, at 7:28 PM, Quincey Morris wrote:
> On Feb 10, 2011, at 12:59, WT wrote:
>
>> So, why doesn't it sort them correctly when it's accessing the "indexOrName"
>> stored value?
>
> You *cannot* have an attribute that's both a derived property and a stored
> property at the same tim
(Apologies if this message reaches you in duplicate. The first time I sent it,
it was flagged as 10 KB too large.)
I spoke too soon...
Forcing -indexOrName to be invoked at entity creation time ensures that the
corresponding attribute has the correct value but the fetched results
controller s
On Feb 10, 2011, at 12:59, WT wrote:
> So, why doesn't it sort them correctly when it's accessing the "indexOrName"
> stored value?
You *cannot* have an attribute that's both a derived property and a stored
property at the same time. The two things are mutually contradictory. What
you've actua
Your statement that I need to get the values of "indexOrName" stored in the
store led me to write the odd-looking line of code below
cdCountry.indexOrName = cdCountry.indexOrName;
when the entities are created and it fixes the problem in the test project. I'm
now more convinced than ever that C
On Feb 10, 2011, at 3:54 PM, Quincey Morris wrote:
> Perhaps you're assuming that Core Data will internally call the above getter
> to figure out what to put into the store. It doesn't work that way. Most
> likely your store contains nil values for the "indexOrName" attribute. (I'm
> assuming y
On Feb 10, 2011, at 07:19, WT wrote:
> The test project's core data model has a single entity, "CountryCD", with the
> attributes "name", "index", "selected" (representing a boolean), and a
> transformable attribute "indexOrName" which returns the entity's index if
> it's selected or its name i
The example of countries is just that, an example. The actual app is about
something else. Also, the color of the text is not a model property - the
selected status is.
I think you didn't quite understand what the problem I'm having is. The problem
is that NSFetchedResultsController is ignoring
Hello list,
a little while ago I posted a question regarding some strange behavior by an
NSFetchedResultsController (under the same subject line as this message). Since
then I've narrowed the problem down a bit more and now have a test project to
show it.
Here's what the goal is, in a nutshell
Hello list,
I'm experiencing a strange behavior on the part of NSFetchedResultsController
and I can't seem to find why, although I suspect it's something utterly simple
that I'm just not seeing.
Here's the setup. I have a list of some 20 keys the user can choose from to
sort some experimental
10 matches
Mail list logo
