Re: jsonb and nested hstore

* Peter Geoghegan (pg@heroku.com) wrote:
> 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?

Err, I'm not following this thread all *that* closely, but I was pretty
sure the issue was json vs. jsonb, and I'd be mighty confused as to wtf
was going on if those were binary-coercible...
Thanks,
    Stephen