| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | 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:33:38 |
| Message-ID: | CAM3SWZRfj9Kut+VT=FC37VNACOG3x5DtsUh0jH5cGAM7p=bn-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-02-26 04:43:26 | Re: Custom Scan APIs (Re: Custom Plan node) |
| Previous Message | Stephen Frost | 2014-02-26 04:22:21 | Re: Custom Scan APIs (Re: Custom Plan node) |