From: | Mathieu Arnold <mat(at)mat(dot)cc> |
---|---|
To: | mario(dot)splivalo(at)mobart(dot)hr |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: ORDER BY CASE ... |
Date: | 2006-02-13 16:10:48 |
Message-ID: | B6687EF0F11B9302F7A56031@[192.168.9.47] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
+-le 13/02/2006 16:47 +0100, Mario Splivalo a dit :
| On Mon, 2006-02-13 at 16:39 +0100, Mathieu Arnold wrote:
|> |
|> | I tought I'd get differently sorted data, since in the first query I
|> | said 5=5, and in second I said 5=6.
|>
|> Well, no, in the first, the result of the CASE is 2, and in the second 3,
|> it means that for every line, it'll sort using "2" as value for the first,
|> and "3" for the second query.
|>
|
| Yes, I realized just a second ago that when ORDER BY is CASED, numbers
| aren't the column numbers, but the integers itself.
|
| It works like this:
|
| ORDER BY (CASE WHEN 5=5 THEN "from"::varchar ELSE
| receiving_time::varchar) DESC.
|
| Is there a way to have DESC/ASC inside of a CASE?
|
| Mario
No, you don't understand, you should do something like :
case when foo = bar then from else receiving_time desc end
--
Mathieu Arnold
From | Date | Subject | |
---|---|---|---|
Next Message | Bryce Nesbitt | 2006-02-13 17:27:37 | Re: Very slow updates when using IN syntax subselect |
Previous Message | Mario Splivalo | 2006-02-13 15:47:48 | Re: ORDER BY CASE ... |