| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-28 04:43:10 |
| Message-ID: | F1CF141E-0238-482A-BDDC-82FEA10E8B1C@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 27, 2014, at 8:31 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Thu, Feb 27, 2014 at 8:23 PM, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>> Surely, the answer is to define a jsonb || jsonb (and likely the other combinatorics of json and jsonb), along with the appropriate GIN and GiST interfaces for jsonb. Why would that not work?
>
> I'm not the one opposed to putting jsonb stuff in the hstore module!
My proposal is that we break the dependencies of jsonb (at least, at the user-visible level) on hstore2, thus allowing it in core successfully. jsonb || jsonb returning hstore seems like a bug to me, not a feature we should be supporting.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2014-02-28 05:10:48 | Re: extension_control_path |
| Previous Message | Peter Geoghegan | 2014-02-28 04:31:16 | Re: jsonb and nested hstore |