| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Subject: | Re: WIP: default values for function parameters |
| Date: | 2008-11-30 18:04:33 |
| Message-ID: | 9405E2FD-CB0D-4369-A36F-63970E4E8173@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 30, 2008, at 6:49 PM, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> There are two ways to fix this, both having some validity:
>
>> 1. We create a second version of pg_get_function_arguments() that
>> produces
>> arguments without default values decoration. This is probably the
>> technically sound thing to do.
>
> Yes. I think that the argument for allowing parameter names in
> commands
> like ALTER FUNCTION is that the user might consider them part of the
> function's identity. This can hardly be claimed for default values.
Agreed, default values should not be a part of function signatures,
although it might be nice if ALTER FUNCTION to allow default values to
be changed.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-11-30 18:49:36 | pgsql: Remove inappropriate memory context switch in |
| Previous Message | Tom Lane | 2008-11-30 17:49:31 | Re: WIP: default values for function parameters |