Re: pgsql: Remove hstore's text => text operator.

From: Thom Brown <thom(at)linux(dot)com>
To: Robert Haas <rhaas(at)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Remove hstore's text => text operator.
Date: 2011-11-08 07:38:37
Message-ID: CAA-aLv5pRNyv67v=qHFUR1sS3mh6KW_cDYhvuS65D_e6ZibFJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 8 November 2011 02:51, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Remove hstore's text => text operator.
>
> Since PostgreSQL 9.0, we've emitted a warning message when an operator
> named => is created, because the SQL standard now reserves that token
> for another use.  But we've also shipped such an operator with hstore.
> Use of the function hstore(text, text) has been recommended in
> preference to =>(text, text).  Per discussion, it's now time to take
> the next step and stop shipping the operator.  This will allow us to
> prohibit the use of => as an operator name in a future release if and
> when we wish to support the SQL standard use of this token.
>
> The release notes should mention this incompatibility.
>
> Patch by me, reviewed by David Wheeler, Dimitri Fontaine and Tom Lane.

There's a typo here:

+/* contrib/hstore/hstore-1.0-1.1.sql */

Should be:

+/* contrib/hstore/hstore-1.0--1.1.sql */

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Thom Brown 2011-11-08 07:43:55 Re: pgsql: Make VACUUM avoid waiting for a cleanup lock, where possible.
Previous Message Peter Eisentraut 2011-11-08 04:56:49 pgsql: -DLINUX_OOM_ADJ=0 should be in CPPFLAGS, not CFLAGS