From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RfD: more powerful "any" types |
Date: | 2009-09-11 02:11:40 |
Message-ID: | 709E061A-23E3-4B62-AEF5-3D961E99BEDA@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sep 10, 2009, at 2:08 PM, Hannu Krosing wrote:
>> Perhaps you should try changing ANY to a non-reserved word in the
>> parser and see what happens. If you come up with a way to resolve
>> the
>> shift/reduce and/or reduce/reduce conflicts that will probably
>> result,
>> submit a patch.
>
> I don't want it to be a non-reserved word.
I say we use "whatever" (quotes not required).
David
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-09-11 02:27:45 | Re: RfD: more powerful "any" types |
Previous Message | Itagaki Takahiro | 2009-09-11 01:56:21 | Re: logging hook for database audit |