| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Variadic parameters vs parameter defaults |
| Date: | 2008-12-17 18:40:04 |
| Message-ID: | 1572.1229539204@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Tue, 2008-12-16 at 19:07 -0500, Tom Lane wrote:
>> ISTM one could make a pretty good argument that this last case should
>> succeed, producing an empty-array argument.
> We had a similar discussion before, and you replied here:
> http://archives.postgresql.org/pgsql-patches/2008-07/msg00150.php
> Are you now in favor of allowing zero arguments for a variadic
> parameter?
No, not as such (at least not now that I've had a chance to digest the
alternatives). The default-parameter mechanism gives us another
solution tool, but if you don't use a default then the same ambiguities
as before still exist.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-12-17 18:50:22 | Re: Variadic parameters vs parameter defaults |
| Previous Message | Peter Eisentraut | 2008-12-17 18:32:41 | Re: Variadic parameters vs parameter defaults |