| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Akim Demaille <akim(at)lrde(dot)epita(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Remove useless associativity/precedence from parsers |
| Date: | 2019-06-05 21:54:08 |
| Message-ID: | 20190605215408.GA17377@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-May-28, Andrew Gierth wrote:
> The main cases I know of are:
>
> 1. RANGE UNBOUNDED PRECEDING - this one is actually a defect in the
> standard SQL grammar, since UNBOUNDED is a non-reserved keyword and so
> it can also appear as a legal <identifier>, and the construct
> RANGE <unsigned value specification> PRECEDING allows <identifier> to
> appear as a <SQL parameter reference>.
Should we report this to the SQL committee?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2019-06-05 22:47:57 | Re: Binary support for pgoutput plugin |
| Previous Message | Peter Geoghegan | 2019-06-05 21:32:49 | Re: crash testing suggestions for 12 beta 1 |