Re: functional call named notation clashes with SQL feature

On 27/05/10 22:55, Tom Lane wrote:
> Peter Eisentraut<peter_e@gmx.net>  writes:
>> How about
>> select myfunc(a := 7, b := 6);
>> ?
>
> Hey, that's a thought.  We couldn't have used that notation before
> because we didn't have := as a separate token, but since I hacked that
> in for plpgsql's benefit, I think it might be an easy fix.  It'd be
> nice that it puts the argument name first like the spec syntax, too.

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 =>.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com