| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Johnston <polobo(at)yahoo(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-20 17:43:41 |
| Message-ID: | 528CF4CD.9080304@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/20/2013 04:52 AM, Robert Haas wrote:
> I confess to being a bit perplexed by why we want hstore and json to
> share a common binary format. hstore doesn't store hierarchical data;
> json does. If we design a binary format for json, doesn't that just
> obsolete store? Why go to a lot of trouble to extend our home-grown
> format if we've got a standard format to plug into?
See hstore2 patch from Teodor. That's what we're talking about, not
hstore1, which as you point out is non-heirarchical.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-11-20 17:45:23 | Re: -d option for pg_isready is broken |
| Previous Message | Heikki Linnakangas | 2013-11-20 17:02:44 | Re: GIN improvements part 1: additional information |