Re: functional call named notation clashes with SQL feature

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: functional call named notation clashes with SQL feature
Date: 2010-05-28 14:26:52
Message-ID: 4BFFD2AC.7080502@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2010-05-28 15:01:58 Re: [9.1] pg_stat_get_backend_server_addr
Previous Message Bruce Momjian 2010-05-28 14:21:23 Re: [9.1] pg_stat_get_backend_server_addr