From: Avi Schwartz <avi@CFFtechnologies.com>
To: pgsql-sql@postgresql.org
Subject: Re: generic return for functions
Date: Sun, 1 Jun 2003 10:21:36 -0500
Message-ID: <BBDB60B2-9444-11D7-ACB0-000393AE5044@CFFtechnologies.com> (raw)
In-Reply-To: <1054470071.11968.115.camel@jester>
Exactly. It is used with named parameters when the parameter is not
provided.
Avi
On Sunday, Jun 1, 2003, at 07:21 America/Chicago, Rod Taylor wrote:
>> thing that causes me some minor grief is the fact that currently you
>> cannot have default values to function parameters, a feature we use a
>> lot.
>
> The default value is used when the parameter is NULL or unprovided?
>
> fn(integer, integer, integer default 32)
>
> select fn(integer, integer); <- Third argument would be '32'?
>
>
> When PostgreSQL gets named parameters the above probably makes sense to
> add.
>
> A TODO item?
--
Avi Schwartz
avi@CFFtechnologies.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: avi@CFFtechnologies.com
Subject: Re: generic return for functions
In-Reply-To: <BBDB60B2-9444-11D7-ACB0-000393AE5044@CFFtechnologies.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox