| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Parsing ambiguity for ORDER BY ... NULLS FIRST/LAST |
| Date: | 2007-01-07 08:47:21 |
| Message-ID: | 1168159641.3951.44.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 2007-01-06 at 13:05 -0500, Tom Lane wrote:
> "Simon Riggs" <simon(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-01-07 08:53:28 | Re: COPY with no WAL, in certain circumstances |
| Previous Message | Simon Riggs | 2007-01-07 08:45:40 | Re: COPY with no WAL, in certain circumstances |