| From: | Avi Schwartz <avi(at)CFFtechnologies(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: generic return for functions |
| Date: | 2003-06-01 15:21:36 |
| Message-ID: | BBDB60B2-9444-11D7-ACB0-000393AE5044@CFFtechnologies.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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(at)CFFtechnologies(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-06-01 15:46:47 | Re: generic return for functions |
| Previous Message | Rod Taylor | 2003-06-01 12:21:12 | Re: generic return for functions |