Re: plpgsql: defuault parameters and constant function parameters - Mailing list pgsql-interfaces

From Bruce Momjian
Subject Re: plpgsql: defuault parameters and constant function parameters
Date
Msg-id 200709182211.l8IMBl527174@momjian.us
Whole thread Raw
In response to Re: plpgsql: defuault parameters and constant function parameters  (Peter Eisentraut <peter_e@gmx.net>)
List 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@momjian.us>          http://momjian.us EnterpriseDB
http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-interfaces by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: plpgsql: defuault parameters and constant function parameters
Next
From: Robert Ayrapetyan
Date:
Subject: Re: Problem with getting static libpq.a from PostgresSQL 8.2.4 sources using MinGW