From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, obartunov(at)gmail(dot)com, Peter Geoghegan <pg(at)heroku(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-07 01:20:01 |
Message-ID: | 53191EC1.7070407@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 03/06/2014 12:58 PM, Daniele Varrazzo wrote:
> On Thu, Mar 6, 2014 at 6:54 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>
>> The actual storage upgrade of hstore-->hstore2 is fairly painless from
>> the user perspective; they don't have to do anything. The problem is
>> that the input/output strings are different, something which I didn't
>> think to check for (and Peter did), and which will break applications
>> relying on Hstore, since the drivers which support Hstore (like
>> psycopg2) rely on string-parsing to convert it. I haven't
>> regression-tested hstore2 against psycopg2 since I don't have a good
>> test, but that would be a useful thing to do.
>
> 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.
Looks like that won't be necessary, Daniele. But thanks for speaking up!
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Kouhei Kaigai | 2014-03-07 01:32:18 | Re: Custom Scan APIs (Re: Custom Plan node) |
Previous Message | Greg Stark | 2014-03-07 00:07:41 | Re: GSoC on WAL-logging hash indexes |