Re: functional call named notation clashes with SQL feature

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> Peter Eisentraut<peter_e(at)gmx(dot)net> writes:
>>> How about
>>> select myfunc(a := 7, b := 6);

> If we go with that, should we make some preparations to allow => in the
> future? Like provide an alternative operator name for hstore's =>, and
> add a note somewhere in the docs to discourage other modules from using =>.

I'd vote no. We're intentionally choosing to deviate from a very poor
choice of notation. Maybe Peter can interest the committee in allowing
:= as an alternate notation, instead.

regards, tom lane