Re: jsonb and nested hstore

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, obartunov(at)gmail(dot)com, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb and nested hstore
Date: 2014-03-06 21:27:07
Message-ID: CA+mi_8aq8KKkkew_0fpvrqxdH2vK_2JO7EVAAaN-hPzemM6=NA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 6, 2014 at 9:10 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Thu, Mar 6, 2014 at 12:58 PM, Daniele Varrazzo
> <daniele(dot)varrazzo(at)gmail(dot)com> wrote:
>> Hello, psycopg developer here. Not following the entire thread as it's
>> quite articulated and not of my direct interest (nor comprehension).
>> But if you throw at me a few test cases I can make sure psycopg can
>> parse them much before hstore2 is released.
>
> I don't think that'll be necessary. Any break in compatibility in the
> hstore format has been ruled a non-starter for having hstore support
> nested data structures. I believe on balance we're content to let
> hstore continue to be hstore. jsonb support would certainly be
> interesting, though.

Cool, just let me know what you would expect a well-behaved client
library to behave.

-- Daniele

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-03-06 22:42:33 Re: Rowcounts marked by create_foreignscan_path()
Previous Message Peter Geoghegan 2014-03-06 21:10:48 Re: jsonb and nested hstore