| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
| Cc: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: SELECT DISTINCT ON bug? |
| Date: | 2003-05-22 15:49:57 |
| Message-ID: | 20030522154957.GA1667@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 22, 2003 at 08:53:10 -0600,
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> wrote:
>
> Wouldn't we also need them around the expression on the select line?
>
> SELECT [ ALL | DISTINCT [ ON {( expression [, ...] ) } ] ]
> { * | expression [ AS output_name ] [, ...] }
I don't think so. Where you put them you have enclosed tokens that
are only concatenated so precedence doesn't cause a problem.
The original format implies that you can have a select statement without
the SELECT keyword and that if you use the SELECT keyword you also have
to use * for the target list.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-05-22 16:13:22 | Re: Is this a bug? : select '26/10/2003'::date + interval |
| Previous Message | Tom Lane | 2003-05-22 15:44:05 | Re: Is this a bug? : select '26/10/2003'::date + interval '1 day'; |