| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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 17:58:13 |
| Message-ID: | 20060615175813.GE19896@fetter.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-06-15 18:00:24 | Re: pgsql: Clarify dynamic pl/pgsql item and add URLs. |
| Previous Message | Bruce Momjian | 2006-06-15 17:52:48 | pgsql: Fix to_ascii() markup error. |