2009/9/28 Jeff Davis <pg...@j-davis.com>: > On Mon, 2009-09-28 at 11:50 +0200, Pavel Stehule wrote: >> This is maybe too strict. I thing, so safe version is allow variadic >> packed parameter with VARIADIC keyword as Jeff proposes. > > The combination of variadic parameters and named call notation is > somewhat strange, on second thought. Can you identify a use case? >
I have not any use case now. Simply when I have a variadic function, then I would to allow call it with named notation. Some like create or replace foo (a int, variadic b int[]) ... SELECT foo(10 as int, variadic array[10,20] as b) > If not, then it should probably be blocked in this version of the patch. > Even if it makes sense from a syntax standpoint, it might be confusing > to users. > when I though about control, I found so syntax with mandatory VARIADIC is difficult implementable. So probably the most feasible solution for this moment is to discard a variadic functions from set of functions that are callable with named notation. So I thing we are in tune, and I am going to update patch. Regards Pavel Stehule > Robert, did you have a specific concern in mind? Do you see a behavior > there that we might want to change in the future? > > Regards, > Jeff Davis > > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
