Re: mixed, named notation support

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Steve Prentice <prentice(at)cisco(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: mixed, named notation support
Date: 2009-08-04 22:24:11
Message-ID: 7BDBD3EB5372749FCC49FC45@amenophis
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On 4. August 2009 20:22:05 +0200 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:

> Named notation has different algorithm for function detection then
> positional notation. There are not exist variadic parameters (because
> these parameters hasn't individual names). So only "packed" variadic
> parameter should be there, and this parameter have to be named - so
> keyword VARIADIC is optional.

I wonder wether it wouldn't better to force positional notation for such
functions then. I found it surprising that this works at all, but of
course, someone else might enjoy this as a cool feature. To me, it feels
strange and confusing that a function declared as VARIADIC suddenly accepts
a "sloppy" argument only because you are using some other calling notation
where others enforces you to use an additional keyword to match the
function.

At least, we need to document that both notations behaves different in this
case.

--
Thanks

Bernd

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-08-04 22:28:04 Re: the case for machine-readable error fields
Previous Message Greg Sabino Mullane 2009-08-04 22:06:37 Re: the case for machine-readable error fields