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

From Robert Haas
Subject Re: hstore ==> and deprecate =>
Date
Msg-id AANLkTinAfxpP4Q0btNy6sWSQJf2br3jOEjmeKE2lZAiL@mail.gmail.com
Whole thread Raw
In response to hstore ==> and deprecate =>  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: hstore ==> and deprecate =>
Re: hstore ==> and deprecate =>
List pgsql-hackers
On Tue, Jun 8, 2010 at 3:56 PM, Michael Glaesemann <grzm@seespotcode.net> wrote:
> On Jun 8, 2010, at 15:38 , Robert Haas wrote:
>> On Tue, Jun 8, 2010 at 3:34 PM, Merlin Moncure <mmoncure@gmail.com> wrote:
>>> hm.  any chance of a  shorter operator, like '#'?  I kinda agree that
>>> hstore_in and the operator don't have to be the same, but requiring
>>> three letter token for the two most high traffic operations w/hstore
>>> seems off to me.
>>>
>>> # is currently used for bitwise xor/geo
>>
>> I'm happy to do whatever the consensus is.  I thought it would be
>> easier to remember if the two operators were spelled at least somewhat
>> similarly, but I just work here.
>
> Perhaps
> ->

That's already in use to mean something else.

> Would a colon work?

Nope.

ERROR:  syntax error at or near ":"

> (That's enough bikeshedding for me.)

Test first, then post?  :-)

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


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: hstore ==> and deprecate =>
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] Add _PG_init to PL language handler documentation