| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(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:31:16 |
| Message-ID: | CAM3SWZTzic3XRLTM424KGYSwYhP2gVNJ4PLJwfCYpBwSwK3sPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 27, 2014 at 8:23 PM, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
> On Feb 27, 2014, at 8:04 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>
>> I'm hearing a lot about how important jsonb is, but not much on how to
>> make the simple jsonb cases that are currently broken (as illustrated
>> by my earlier examples [1], [2]) work.
>
> 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!
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christophe Pettus | 2014-02-28 04:43:10 | Re: jsonb and nested hstore |
| Previous Message | Tan Tran | 2014-02-28 04:29:48 | GSoC proposal |