Skip site navigation (1) Skip section navigation (2)

Re: functional call named notation clashes with SQL feature

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: functional call named notation clashes with SQL feature
Date: 2010-05-27 17:27:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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.



In response to


pgsql-hackers by date

Next:From: Mohammad Heykal AbdillahDate: 2010-05-27 17:58:45
Subject: Why my manualy constructed raw parser tree produce failed to execute?
Previous:From: Simon RiggsDate: 2010-05-27 17:26:26
Subject: Re: Keepalive for max_standby_delay

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group