Re: hstore ==> and deprecate => - Mailing list pgsql-hackers

From Robert Haas
Subject Re: hstore ==> and deprecate =>
Date
Msg-id AANLkTil6nsWEs7vSeIKFTmdelG-fhtmX-WlcK8jRc5DQ@mail.gmail.com
Whole thread Raw
In response to Re: hstore ==> and deprecate =>  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: hstore ==> and deprecate =>  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
On Wed, Jun 9, 2010 at 9:06 AM, Dimitri Fontaine <dfontaine@hi-media.com> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>>> What about a WARNING at CREATE OPERATOR time?
>>
>> That's what the patch I sent already does.
>
> Great :)
> I read comments in the email instead of the commit…
>
>> I'm not following this part.
>
> I'm wondering if deprecating => as an SQL operator, we should too
> deprecate its usage in input text for hstore. I don't think so.

I don't think so, either.  The most someone might want to do is make
==> work wherever => does now, but I wouldn't want to start monkeying
with that without some input from Andrew Gierth; and I don't think
it's a stop-ship issue for 9.0.

Unless there is more than one vote for some alternative other than
what I've done here (which so far there isn't), I'm going to add some
docs to this patch and commit it later today.  Because the SQL
committee has standardized an incompatible syntax, there are no
perfect alternatives here.

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


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: hstore ==> and deprecate =>
Next
From: Robert Haas
Date:
Subject: Re: Adding XMLEXISTS to the grammar