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

From Robert Haas
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id AANLkTim09yzPtzMSqjPets0Rj1mjwcR2lnnWDGS4wMu5@mail.gmail.com
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, May 31, 2010 at 11:36 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "David E. Wheeler" <david@kineticode.com> writes:
>> On May 31, 2010, at 7:40 PM, Robert Haas wrote:
>>> I was going to propose ==> across the board.
>
>> What about -> ?
>
> hstore already uses that for something else.
>
> Robert's idea isn't a bad one if we're forced to rename the operator.
> I'd still like to know exactly how hard the concrete has set on the
> SQL spec draft, first.  (Peter?)

Given the way hstore uses ->, another reasonable choice might be -->

That way we'd have -> and --> instead of -> and ==>

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: functional call named notation clashes with SQL feature
Next
From: Tom Lane
Date:
Subject: Re: functional call named notation clashes with SQL feature