Re: CoreData issue
Re: CoreData issue
- Subject: Re: CoreData issue
- From: Patrick Perroud <email@hidden>
- Date: Thu, 7 Sep 2006 14:54:54 +0200
On 7 Sep 2006, at 14:34 , David Emme wrote:
On Sep 7, 2006, at 5:13 AM, Patrick Perroud wrote:
I just need to fetch the oiginal data in its original unsorted order.
In a relational database (I know, CoreData is not a database, but
it sometimes plays one on TV), there is by definition no such thing
as the "original data *in its original unsorted order*". I found
that out using MySQL, where I wrote data into a temp table in the
desired order, then when I fetched it the order of the result was
not what I had written!
Moral of the story: if you need the data in a certain order, you
must arrange for field(s) and sorting to obtain that order. You
cannot rely on retrieving the data in the order you wrote it.
HTH,
-Dave
>
Hi Dave,
I've done a lot of SQL programming in my life and one could always
query for a sorted data cursor - but this is not my point here.
My point is: binding a listbox to a managed object doesn't seem to be
working as espected.
I mean: if the end user was adding rows in a given order into a
listbox, then I don't think this user could accept rows fetch back
later in a random order after it was saved/opened.
So - yes: one could just say - don't use a listbox w/ CoreData ;+)
But Apple is doing it in their own tutorial movies, so here we only
have 2 rationnal explanations, IMO:
1- they just don't know what they are doing and someone should tell them
2- the ignorant myself is missing something important
#2 being my favorite - indeed
Best regards
Patrick Perroud
--
I started out with nothing, and I still have most of it.
_______________________________________________
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