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

From Andrew Dunstan
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 4BFFD2AC.7080502@dunslane.net
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: functional call named notation clashes with SQL feature
List pgsql-hackers

Tom Lane wrote:
> 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.
>
>             
>   

What's poor about it? It probably comes from PLSQL which in turn got it 
from Ada, so they aren't just making this up.  I agree it's inconvenient 
for us, but that's a different issue.

cheers

andrew


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [9.1] pg_stat_get_backend_server_addr
Next
From: Peter Eisentraut
Date:
Subject: Re: [9.1] pg_stat_get_backend_server_addr