Re: Issues for named/mixed function notation patch - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Issues for named/mixed function notation patch
Date
Msg-id 162867790909262137y7a9ac557h341ed2be621998a0@mail.gmail.com
Whole thread Raw
In response to Re: Issues for named/mixed function notation patch  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: Issues for named/mixed function notation patch
List pgsql-hackers
> "However, a named variadic argument can only be called the way shown in
> the example above. The VARIADIC keyword must not be specified and a
> variadic notation of all arguments is not supported. To use variadic
> argument lists you must use positional notation instead."
>
> What is the intended behavior? I think we should always require VARIADIC
> to be specified regardless of using named notation.
>

maybe we could to support variadic named parameters in future - then
using VARIADIC keyword should be necessary - like

foo(10 AS p1, 20 AS p1, 30 AS p3) is equalent of
foo(VARIADIC ARRAY[10,20] AS p1, 30 AS p3)

if we plan this feature, the VARIADIC keyword have to be mandatory.

Regards
Pavel Stehule

> I'm still reviewing the code.
>
> Regards,
>        Jeff Davis
>
>


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: TODO item: Allow more complex user/database default GUC settings
Next
From: Tom Lane
Date:
Subject: Re: Using results from INSERT ... RETURNING