On 03/06/2014 12:58 PM, Daniele Varrazzo wrote: > On Thu, Mar 6, 2014 at 6:54 PM, Josh Berkus <j...@agliodbs.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
