Re: pgsql: Clarify dynamic pl/pgsql item and add URLs. - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.
Date
Msg-id 200606151742.k5FHgAd06736@candle.pha.pa.us
Whole thread Raw
In response to Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.  (David Fetter <david@fetter.org>)
Re: pgsql: Clarify dynamic pl/pgsql item and add URLs.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Tom Lane wrote:
> momjian@postgresql.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.

--
  Bruce Momjian   http://candle.pha.pa.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update syntax suggestion: < get_employee_salary(emp_id =>
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Add mention that preload_libraries check the magic block, so