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

From Peter Geoghegan
Subject Re: jsonb and nested hstore
Date
Msg-id CAM3SWZRfj9Kut+VT=FC37VNACOG3x5DtsUh0jH5cGAM7p=bn-w@mail.gmail.com
Whole thread Raw
In response to Re: jsonb and nested hstore  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: jsonb and nested hstore  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Tue, Feb 25, 2014 at 8:07 PM, Craig Ringer <craig@2ndquadrant.com> wrote:
> Please also highlight that any change will require a full table rewrite
> with an exclusive lock, so data type choices on larger tables may be
> hard to change later.

It sure looks like they're binary-coercible to me:

+ CREATE CAST (hstore AS jsonb)
+   WITHOUT FUNCTION AS IMPLICIT;
+
+ CREATE CAST (jsonb AS hstore)
+   WITHOUT FUNCTION AS IMPLICIT;

Is this okay?
-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Custom Scan APIs (Re: Custom Plan node)
Next
From: Stephen Frost
Date:
Subject: Re: Custom Scan APIs (Re: Custom Plan node)