• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: setting default order of entity fetches
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: setting default order of entity fetches


  • Subject: Re: setting default order of entity fetches
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 22 Aug 2007 20:38:34 -0700


On Aug 22, 2007, at 6:22 PM, Lachlan Deck wrote:

On 23/08/2007, at 10:46 AM, Chuck Hill wrote:

On Aug 22, 2007, at 5:09 PM, Lachlan Deck wrote:

Hi there,

EOEntity has a restrictingQualifier that's applied to every fetch for the relevant entity.

Is there any similar mechanism for installing a default ordering for fetched objects of each entity (e.g., when following a toMany relationship)? Or any delegate methods somewhere?

No. And don't override the EOF methods to do this or you risk messing with EOF. And we all know how that ends up. :-) The reason for the lack of sorting, as I understand it, is that EOF would then need to keep the list sorted each time something was added to it.

It's already keeping them sorted (think about it...). Just not how I'd like.

No, they are not sorted.


Furthermore, it's impossible to fetch records from a database without them sorted in some kind of order.

Where on earth did you get that idea from? An unordered list is not sorted. If there is no ORDER BY clause on a SELECT, the order in the result set is undefined. It most databases it will change over time as the query optimizer changes strategies.



I'm simply wanting to override the arbitrary sort order that the database wants to return to suit this particular application.

And what if you wanted alternate sorts?

Simply apply the default sorting in the absence of a specific sort orderings array. Not hard conceptually.

Not sure how that differs from what I suggested and it means two sorts so additional unneeded load on the machine.



The standard approach is to have a cover method that sorts the contents of the relationship and returns it.

Which kinda makes *every* toMany relationship generated from each EOEntity useless don't you think?

I dunno, I have always found them to be be pretty useful. YMMV.

Like Ken said, ordering is a UI thing.


Chuck

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: setting default order of entity fetches
      • From: Lachlan Deck <email@hidden>
References: 
 >setting default order of entity fetches (From: Lachlan Deck <email@hidden>)
 >Re: setting default order of entity fetches (From: Chuck Hill <email@hidden>)
 >Re: setting default order of entity fetches (From: Lachlan Deck <email@hidden>)

  • Prev by Date: Re: setting default order of entity fetches
  • Next by Date: Re: setting default order of entity fetches
  • Previous by thread: Re: setting default order of entity fetches
  • Next by thread: Re: setting default order of entity fetches
  • Index(es):
    • Date
    • Thread