From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Issues for named/mixed function notation patch |
Date: | 2009-10-07 22:09:56 |
Message-ID: | 1254953396.16369.60.camel@monkey-cat.sm.truviso.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2009-10-07 at 17:45 -0400, Tom Lane wrote:
> I think what he was considering was the question of insisting that
> the VARIADIC keyword be attached to the named argument that actually
> matches the VARIADIC parameter. I think we could do it, but it might
> be a bit of a wart. I notice that right now, an unnecessary VARIADIC
> keyword in a regular positional call does not cause an error, it's just
> ignored --- so we're already being a bit lax with it.
>From a semantic standpoint, I lean towards requiring the VARIADIC
keyword consistently between named and positional notation.
It seems strange to me if we have a situation where changing the call:
foo(a, b, VARIADIC c)
to be more explicit by using named call notation:
foo(a AS x, b AS y, VARIADIC c AS z)
is "less correct" in the sense that the VARIADIC keyword goes from
"required" to "ignored".
Also, requiring VARIADIC seems to guard us better against future
changes, which seemed like a concern before.
I don't have a strong opinion or a specific problem with making VARIADIC
optional, so it's OK with me.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-10-07 22:14:26 | pgsql: Make it possibly to specify GUC params per user and per database. |
Previous Message | Brendan Jurd | 2009-10-07 21:57:40 | Re: Triggers on columns |