| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| 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:26:39 |
| Message-ID: | m2txfa3bs0.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)justatheory(dot)com> writes:
> 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.
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.
Now, if it turns out that the new hstore is not dealing with json input
and output, we could have json, jstore and hstore.
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2013-11-17 22:28:35 | Re: additional json functionality |
| Previous Message | David E. Wheeler | 2013-11-17 22:20:14 | Re: additional json functionality |