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 201006031613.o53GDY409304@momjian.us
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  ("David E. Wheeler" <david@kineticode.com>)
List pgsql-hackers
David E. Wheeler wrote:
> On Jun 3, 2010, at 8:53 AM, Dimitri Fontaine wrote:
> 
> > Now that it's pretty clear from Peter that the standard is not going to
> > change its choice here, I'll vote adding a WARNING each time an operator
> > called => is created, so that we get a chance to move later on.
> 
> Should support for ==> be added to hstore for 9.0? So both => and ==> will work?

I have added the idea to the 9.0 open items wiki:
http://wiki.postgresql.org/wiki/PostgreSQL_9.0_Open_Items#Code

--  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: Bruce Momjian
Date:
Subject: Re: functional call named notation clashes with SQL feature
Next
From: Tom Lane
Date:
Subject: Re: Did we really want to force an initdb in beta2?