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

From Peter Eisentraut
Subject Re: plpgsql: defuault parameters and constant function parameters
Date
Msg-id 200709182325.12677.peter_e@gmx.net
Whole thread Raw
In response to Re: plpgsql: defuault parameters and constant function parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: plpgsql: defuault parameters and constant function parameters  (Bruce Momjian <bruce@momjian.us>)
List pgsql-interfaces
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/


pgsql-interfaces by date:

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