Re: jsonb and nested hstore - Mailing list pgsql-hackers

From Christophe Pettus
Subject Re: jsonb and nested hstore
Date
Msg-id F1CF141E-0238-482A-BDDC-82FEA10E8B1C@thebuild.com
Whole thread Raw
In response to Re: jsonb and nested hstore  (Peter Geoghegan <pg@heroku.com>)
Responses Re: jsonb and nested hstore  (Craig Ringer <craig@2ndquadrant.com>)
Re: jsonb and nested hstore  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Feb 27, 2014, at 8:31 PM, Peter Geoghegan <pg@heroku.com> wrote:

> On Thu, Feb 27, 2014 at 8:23 PM, Christophe Pettus <xof@thebuild.com> wrote:
>> Surely, the answer is to define a jsonb || jsonb (and likely the other combinatorics of json and jsonb), along with
theappropriate GIN and GiST interfaces for jsonb.  Why would that not work? 
>
> I'm not the one opposed to putting jsonb stuff in the hstore module!

My proposal is that we break the dependencies of jsonb (at least, at the user-visible level) on hstore2, thus allowing
itin core successfully. jsonb || jsonb returning hstore seems like a bug to me, not a feature we should be supporting. 

--
-- Christophe Pettus  xof@thebuild.com




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: jsonb and nested hstore
Next
From: Stephen Frost
Date:
Subject: Re: extension_control_path