Re: SELECT DISTINCT ON bug?

On Thu, May 22, 2003 at 12:05:46 -0600,
  "scott.marlowe" <scott.marlowe@ihs.com> wrote:
> 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.
>
> Good point.  As written, syntax says you can either select * OR you can
> select field1,field2,field3, but you can't select *,oid ...

This is a bit different than what I was looking at, but there still
is a problem. I didn't know you could mix * and other expressions.
I now think the second line should be:
     {* | expression [ AS output_name ]} [, ...]

What I was complaining about was that the first line was only included
on the left side of that alternation. However the above fix takes care
of that problem as well.