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

From David E. Wheeler
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id A44F8BB3-1CC7-4E3D-B25A-538C60662723@kineticode.com
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: functional call named notation clashes with SQL feature
List pgsql-hackers
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.

Best,

David



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Keepalive for max_standby_delay
Next
From: Mohammad Heykal Abdillah
Date:
Subject: Why my manualy constructed raw parser tree produce failed to execute?