Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: plpgsql: defuault parameters and constant function parameters
- From: Peter Eisentraut <peter_e(at)gmx(dot)net>
- To: pgsql-interfaces(at)postgresql(dot)org
- Cc: 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: Tue, 18 Sep 2007 23:25:12 +0200
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. -- Peter Eisentraut http://developer.postgresql.org/~petere/
- Follow-Ups:
- Re: plpgsql: defuault parameters and constant function parameters
- From: Bruce Momjian
- Re: plpgsql: defuault parameters and constant function parameters
- Prev by Date: Problem with getting static libpq.a from PostgresSQL 8.2.4 sources using MinGW
- Next by Date: Re: plpgsql: defuault parameters and constant function parameters
- Previous by thread: Problem with getting static libpq.a from PostgresSQL 8.2.4 sources using MinGW
- Next by thread: Re: plpgsql: defuault parameters and constant function parameters
- Indexes: