Postgres Pro
Downloads
Home   >   mailing lists

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 24882.1275363363@sss.pgh.pa.us
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  ("David E. Wheeler" <david@kineticode.com>)
Responses Re: functional call named notation clashes with SQL feature  (Bruce Momjian <bruce@momjian.us>)
Re: functional call named notation clashes with SQL feature  (Robert Haas <robertmhaas@gmail.com>)
Re: functional call named notation clashes with SQL feature  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Tree view 
"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?)
        regards, tom lane

pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: functional call named notation clashes with SQL feature
Next
From: Bruce Momjian
Date:
Subject: Re: functional call named notation clashes with SQL feature