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

From Bruce Momjian
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 201006010344.o513idX28605@momjian.us
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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane 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?)

I don't know, but based on the fact it matches Oracle, I think it is
pretty well set by now.

If we can't come up with a good syntax (and there isn't an SQL standard
for it), we often review how Oracle or other databases handle such
cases, and my guess is that the SQL committee does the same thing.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + None of us is going to be here forever. +


pgsql-hackers by date:

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