From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Clarify dynamic pl/pgsql item and add URLs. |
Date: | 2006-06-15 18:00:24 |
Message-ID: | 200606151800.k5FI0Od22525@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
David Fetter wrote:
> On Thu, Jun 15, 2006 at 01:42:10PM -0400, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > momjian(at)postgresql(dot)org (Bruce Momjian) writes:
> > > >> o Allow function parameters to be passed by name,
> > > >> get_employee_salary(emp_id => 12345, tax_year => 2001)
> > >
> > > The odds of that syntax getting accepted may not be exactly zero,
> > > but they are certainly vanishingly small. I thought we'd agreed
> > > that a usable syntax would be like get_employee_salary(12345 AS
> > > emp_id, 2001 AS tax_year)
> >
> > TODO updated, but I thought "=>" was the Oracle syntax.
>
> It is. I understand Tom's concern about not unnecessarily grabbing
> operator symbols, but in this case, I believe it's overblown.
Interesting. Seems it is something we will have to discuss when we get
closer to a patch.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-06-15 18:02:22 | pgsql: Add STRICT to PL/pgSQL SELECT INTO, so exceptions are thrown if |
Previous Message | David Fetter | 2006-06-15 17:58:13 | Re: pgsql: Clarify dynamic pl/pgsql item and add URLs. |