| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| 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 14:53:10 |
| Message-ID: | Pine.LNX.4.33.0305220851330.23585-100000@css120.ihs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 21 May 2003, Bruno Wolff III wrote:
> On Wed, May 21, 2003 at 10:58:26 +0100,
> "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> wrote:
> >
> > Syntax:
> > SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
> > * | expression [ AS output_name ] [, ...]
>
> This syntax expression does seem wrong. Usually concatenation takes
> precedence over alternation. I think there really should be {}s around
> the second line.
Wouldn't we also need them around the expression on the select line?
SELECT [ ALL | DISTINCT [ ON {( expression [, ...] ) } ] ]
{ * | expression [ AS output_name ] [, ...] }
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arjen van der Meijden | 2003-05-22 15:12:48 | Re: Is this a bug? : select '26/10/2003'::date + interval '1 |
| Previous Message | scott.marlowe | 2003-05-22 14:50:34 | Re: VACUUM and transaction ID wraparound |