| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Dan Wilson" <phpPgAdmin(at)acucore(dot)com> |
| Cc: | "pgsql general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: version issue? |
| Date: | 2001-02-26 16:51:08 |
| Message-ID: | 26515.983206268@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Dan Wilson" <phpPgAdmin(at)acucore(dot)com> writes:
> : Possibly some future release will actually do the right thing with ORDER
> : BY of an expression on the output columns, but right now it has to be an
> : output column, period.
> OK... I tried adding UPPER(last_name) to the result column lists of both
> sides of the union and it still gives me the same error.
You have to use the SQL-standard syntax for ORDER BY, ie column name or
number, no shortcuts:
SELECT ..., UPPER(last_name) AS upper_last_name
UNION
SELECT ..., UPPER(last_name) AS upper_last_name
ORDER BY upper_last_name;
or if you prefer, ORDER BY n where n is the ordinal number of the
column.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Wilson | 2001-02-26 16:55:43 | Re: version issue? |
| Previous Message | Dan Wilson | 2001-02-26 16:47:38 | Re: version issue? |