Re: functional call named notation clashes with SQL feature - Mailing list pgsql-hackers

From Tom Lane
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 24090.1275053216@sss.pgh.pa.us
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: functional call named notation clashes with SQL feature
Re: functional call named notation clashes with SQL feature
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
>> Peter Eisentraut<peter_e@gmx.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


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Failback with log shipping
Next
From: Bruce Momjian
Date:
Subject: Re: [9.1] pg_stat_get_backend_server_addr