| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-interfaces(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Roger Moloney <ramoloney(at)hotmail(dot)com> |
| Subject: | Re: plpgsql: defuault parameters and constant function parameters |
| Date: | 2007-09-18 22:11:47 |
| Message-ID: | 200709182211.l8IMBl527174@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Peter Eisentraut wrote:
> Tom Lane wrote:
> > It's easier if the defaultable parameters are at the end, but I
> > rather wonder how your informix system is disambiguating the calls
> > either with a signature like that. ?If you leave off just one of the
> > two defaultable parameters, how does it know which?
>
> Several other SQL systems allow naming the parameters in calls, such as
>
> CALL foo(a = 1, b = 2)
>
> That's the only way to stay sane with function having 20 or more
> parameters anyway.
TODO has:
o Allow function parameters to be passed by name,
get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Ayrapetyan | 2007-09-20 08:17:34 | Re: Problem with getting static libpq.a from PostgresSQL 8.2.4 sources using MinGW |
| Previous Message | Peter Eisentraut | 2007-09-18 21:25:12 | Re: plpgsql: defuault parameters and constant function parameters |