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

From David E. Wheeler
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 837B023C-E18D-47FC-B523-E9E7B28DAEDA@kineticode.com
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: functional call named notation clashes with SQL feature  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
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?

Best,

David

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