| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: functional call named notation clashes with SQL feature |
| Date: | 2010-05-28 03:32:22 |
| Message-ID: | 201005280332.o4S3WMF25017@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Takahiro Itagaki | 2010-05-28 03:49:23 | Re: mingw initdb failure on HEAD |
| Previous Message | Mohammad Heykal Abdillah | 2010-05-28 03:18:46 | Re: Why my manualy constructed raw parser tree produce failed to execute? |