Skip site navigation (1) Skip section navigation (2)

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: 2007-09-18 21:25:12
Message-ID: 200709182325.12677.peter_e@gmx.net (view raw or flat)
Thread:
Lists: 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/

In response to

Responses

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2007-09-18 22:11:47
Subject: Re: plpgsql: defuault parameters and constant function parameters
Previous:From: Robert AyrapetyanDate: 2007-09-17 13:23:46
Subject: Problem with getting static libpq.a from PostgresSQL 8.2.4 sources using MinGW

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group