Re: Proper syntax to update an hstore key-value pair - Mailing list pgsql-admin

From John Scalia
Subject Re: Proper syntax to update an hstore key-value pair
Date
Msg-id EE53D6C9-60D3-49ED-9F5B-76D9AB90F17A@gmail.com
Whole thread Raw
In response to Re: Proper syntax to update an hstore key-value pair  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proper syntax to update an hstore key-value pair
List pgsql-admin
Sorry if I wasn't clear. Every version I found did include that operator, but there were differences in how they were
defined.In the 1.1 version the arguments for "||" were listed as being public.hstore while in 1.3 the args were just
hstore.I'm going to revisit my tests tomorrow morning. I've gotten all my versions now at 1.3, but it's been a very
longday since I started at 6:30 am this morning. 

Thanks for your help, everyone.

Sent from my iPad

> On Aug 3, 2016, at 2:49 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> John Scalia <jayknowsunix@gmail.com> writes:
>> Well, I discovered that I had different versions of hstore across several
>> databases. Some were 1.1 and others were 1.3. On the 1.3 hstore versions,
>> the \do *.|| produces a public hstore - hstore operator, while the 1.1
>> shows the same as public.hstore. Maybe I just wasn't casting this far
>> enough. On both versions that operator shows as being in the public schema.
>> My search path does include that.
>
> Hmm.  AFAICS, every extant version of hstore ought to provide
>
> operator ||(hstore,hstore)
>
> and no other operator named ||.  You might try comparing the results
> of "\dx+ hstore" across your installations.
>
>            regards, tom lane


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Proper syntax to update an hstore key-value pair
Next
From: Tom Lane
Date:
Subject: Re: Proper syntax to update an hstore key-value pair