| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-26 04:50:42 |
| Message-ID: | 20140226045041.GL2921@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Peter Geoghegan (pg(at)heroku(dot)com) wrote:
> On Tue, Feb 25, 2014 at 8:07 PM, Craig Ringer <craig(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yugo Nagata | 2014-02-26 06:26:12 | Re: Fwd: Proposal: variant of regclass |
| Previous Message | Stephen Frost | 2014-02-26 04:43:26 | Re: Custom Scan APIs (Re: Custom Plan node) |