Re: SELECT DISTINCT ON bug? - Mailing list pgsql-general

From scott.marlowe
Subject Re: SELECT DISTINCT ON bug?
Date
Msg-id Pine.LNX.4.33.0305220851330.23585-100000@css120.ihs.com
Whole thread Raw
In response to Re: SELECT DISTINCT ON bug?  (Bruno Wolff III <bruno@wolff.to>)
Responses Re: SELECT DISTINCT ON bug?  (Bruno Wolff III <bruno@wolff.to>)
List 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@investsystems.co.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 ] [, ...] }




pgsql-general by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: VACUUM and transaction ID wraparound
Next
From: Hubert Fröhlich
Date:
Subject: postgres and postgis