Re: Parsing ambiguity for ORDER BY ... NULLS FIRST/LAST - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Parsing ambiguity for ORDER BY ... NULLS FIRST/LAST
Date
Msg-id 1168159641.3951.44.camel@silverbirch.site
Whole thread Raw
In response to Re: Parsing ambiguity for ORDER BY ... NULLS FIRST/LAST  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 2007-01-06 at 13:05 -0500, Tom Lane wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > Presumably you could put extra grammar rules in to throw errors when you
> > see FROM NULLS FIRST?
> 
> It'll throw an error just fine without any extra rules, because there
> won't be any production allowing the NULLS_FIRST pseudo-token there.
> You already see this in 8.2:
> 
> regression=# select * from with cascaded;
> ERROR:  syntax error at or near "cascaded"
> LINE 1: select * from with cascaded;
>                            ^

OK, Sounds good.

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: [PATCHES] COPY with no WAL, in certain circumstances
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] COPY with no WAL, in certain circumstances