| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-02-05 20:45:56 |
| Message-ID: | CAHyXU0xCLNgRR_cA7jK90SKUFTXS-t0wZbJibAsPiK0Vxy9b5Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 5, 2014 at 2:37 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> The time for this discussion was months ago. I would not have spent many
> many hours of my time if I thought it was going to be thrown away. I find
> this attitude puzzling, to say the least. You were a major part of the
> discussion when we said "OK, we'll leave json as it is (text based) and add
> jsonb." That's exactly what we're doing.
certainly. I'll shut my yap; I understand your puzzlement. At the
time though, I had assumed the API was going to incorporate more of
the hstore feature set than it did.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2014-02-05 20:58:01 | Re: jsonb and nested hstore |
| Previous Message | Andrew Dunstan | 2014-02-05 20:37:24 | Re: jsonb and nested hstore |