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

From Bruce Momjian
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 201005280332.o4S3WMF25017@momjian.us
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: functional call named notation clashes with SQL feature
List pgsql-hackers
Peter Eisentraut wrote:
> On tor, 2010-05-27 at 12:59 -0400, 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
> 
> select myfunc(a := 7, b := 6);

One concern I have is that in PL/pgSQL, := and = behave the same, while
in SQL, they would not.  That might cause confusion.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com


pgsql-hackers by date:

Previous
From: Mohammad Heykal Abdillah
Date:
Subject: Re: Why my manualy constructed raw parser tree produce failed to execute?
Next
From: Takahiro Itagaki
Date:
Subject: Re: mingw initdb failure on HEAD