| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-17 22:20:14 |
| Message-ID: | DBD1B9B9-F3E1-4256-9321-0E94804E5BFF@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 17, 2013, at 1:51 PM, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> wrote:
> I'm wondering about just pushing hstore in core (even if technically
> still an extension, install it by default, like we do for PLpgSQL), and
> calling it a day.
It’s syntax is different than JSON, so one would need to convert to and from JSON all the time to parse and serialize. PITA.
> For bikeshedding purposes, what about calling it jstore, as in “we
> actually know how to store your json documents”?
-1 Sounds like a Java storage API.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-11-17 22:26:39 | Re: additional json functionality |
| Previous Message | Hannu Krosing | 2013-11-17 22:15:00 | Re: additional json functionality |