| 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:23:51 |
| Message-ID: | 67260E8D-E229-48FC-A6F1-4A1FCBF59908@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tan Tran | 2014-02-28 04:29:48 | GSoC proposal |
| Previous Message | Joshua D. Drake | 2014-02-28 04:21:30 | Re: jsonb and nested hstore |