Re: Using NULLS FIRST/LAST on sort orderings
Re: Using NULLS FIRST/LAST on sort orderings
- Subject: Re: Using NULLS FIRST/LAST on sort orderings
- From: Miguel Arroz <email@hidden>
- Date: Wed, 7 Jan 2009 01:59:03 +0000
Hi!
On 2009/01/06, at 23:56, Lachlan Deck wrote:
On 07/01/2009, at 4:29 AM, Miguel Arroz wrote:
Nop. Must be in the DB, it's too many data to handle in memory (the
table that shows it is paged).
This is not achievable apart from in-memory. SQL does not allow for
this. Period.
Yes it does! :) It depends on the DB you are using (and the version).
Check, for instance, <http://www.postgresql.org/docs/current/interactive/queries-order.html
>. You can append NULLS FIRST or NULLS LAST to each ORDER BY
expression.
It would rock to have a way to use this on WO. I've been wondering
how to add this to Wonder (ok, lame sentence, but I'm sleepy), but the
issue is that I would need to hit ERXSortOrdering and the database
plugins. There's the additional problem of Wonder DB plugins not
knowing nothing about ERX classes due to a (correct, IMO) design
decision, so the communication between the plugins and the
ERXSortOrdering would have to be done using reflection or some other
trick. All this means ugly, very ugly code.
For now I'm using a trick (replaced all NULLs by a value that will
never be used) but that also sucks.
Yours
Miguel Arroz
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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