| 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:28:35 |
| Message-ID: | 59BB3A1A-3044-4E23-8C32-5EF274C699F0@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 17, 2013, at 2:26 PM, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> wrote:
>> 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.
>
> Oh I misremembered about that, I though it would take JSON as input
> as-is and could be made to output JSON. And IIRC the community input at
> pgconf.eu has been to just always output json texts and get rid of the
> formating GUCs.
Yeah, but for back-compate, it has to use => instead of : to separate keys from values, and cannot use braces for a root-level object. :-(
> Now, if it turns out that the new hstore is not dealing with json input
> and output, we could have json, jstore and hstore.
That's where this is headed, yes.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-11-17 22:31:17 | Re: additional json functionality |
| Previous Message | Dimitri Fontaine | 2013-11-17 22:26:39 | Re: additional json functionality |