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

From Robert Haas
Subject Re: jsonb and nested hstore
Date
Msg-id CA+TgmoaRH=B25NTb8JqrZtRgPsHk4_DmtkeV+TvX0n18heHSpQ@mail.gmail.com
Whole thread Raw
In response to Re: jsonb and nested hstore  (Josh Berkus <josh@agliodbs.com>)
Responses Re: jsonb and nested hstore  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
On Wed, Feb 26, 2014 at 3:45 PM, Josh Berkus <josh@agliodbs.com> wrote:
> On 02/26/2014 11:39 AM, Merlin Moncure wrote:
>> On Wed, Feb 26, 2014 at 12:05 PM, Josh Berkus <josh@agliodbs.com> wrote:
>>> On 02/26/2014 09:57 AM, Merlin Moncure wrote:
>>>> What is not going to be so clear for users (particularly without good
>>>> supporting documentation) is how things break down in terms of usage
>>>> between hstore and jsonb.
>>>
>>> Realistically?  Once we get done with mapping the indexes and operators,
>>> users who are used to Hstore1 use Hstore2, and everyone else uses jsonb.
>>>  jsonb is nothing other than a standardized syntax interface to hstore2,
>>> and most users will choose the syntax similar to what they already know
>>> over learning new stuff.
>>
>> The problem is that as of today, they are not done and AFAICT will not
>> be for 9.4.
>
> Well, we plan to push to have the indexes and operators available as an
> extension by the time that 9.4 comes out.

Why can't this whole thing be shipped as an extension?   It might well
be more convenient to have the whole thing packaged as an extension
than to have parts of it in core and parts of it not in core.

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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: jsonb and nested hstore
Next
From: Robert Haas
Date:
Subject: Re: Changeset Extraction v7.7