Re: functional call named notation clashes with SQL feature - Mailing list pgsql-hackers

From Robert Haas
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id AANLkTim2RN5tmLwh6wTWBj5bVA4JE9BtcWu0b4oZqzMv@mail.gmail.com
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: functional call named notation clashes with SQL feature
Re: functional call named notation clashes with SQL feature
List pgsql-hackers
On Thu, May 27, 2010 at 1:27 PM, David E. Wheeler <david@kineticode.com> wrote:
> On May 27, 2010, at 9:59 AM, Tom Lane wrote:
>
>>> I think we should fix it now.  Quick thought: maybe we could use FOR
>>> instead of AS: select myfunc(7 for a, 6 for b);
>>
>> I'm afraid FOR doesn't work either; it'll create a conflict with the
>> spec-defined SUBSTRING(x FOR y) syntax.
>
> How about "ISPARAMVALUEFOR"? That shouldn't conflict with anything.

Or we could use the Finnish word
epäjärjestelmällistyttämättömyydellänsäkäänköhän, which I'm pretty
sure is not currently used in our grammar.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Idea for getting rid of VACUUM FREEZE on cold pages
Next
From: "David E. Wheeler"
Date:
Subject: Re: functional call named notation clashes with SQL feature