Re: proposal: disallow operator "=>" and use it for named parameters

2015-03-10 19:02 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Presumably we are going to change it at some point; maybe we
> >> should just do it rather than waiting another 5 years.
>
> > +1
>
> > It has been deprecated long enough that I don't see the point of waiting.
>
> Uh, just to clarify, this has nothing to do with how long the operator has
> been deprecated. The issue is whether pg_dump should dump a function-call
> syntax that will not be recognized by any pre-9.5 release, when there is
> an alternative that will be recognized back to 9.0.
>
> BTW, I just noticed another place that probably should be changed:
>
> regression=# select foo(x => 1);
> ERROR: 42883: function foo(x := integer) does not exist
> LINE 1: select foo(x => 1);
> ^
> HINT: No function matches the given name and argument types. You might
> need to add explicit type casts.
> LOCATION: ParseFuncOrColumn, parse_func.c:516
>

1. funcname_signature_string
2. get_rule_expr

>
> regards, tom lane
>