Re: additional json functionality - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: additional json functionality
Date
Msg-id 59BB3A1A-3044-4E23-8C32-5EF274C699F0@justatheory.com
Whole thread Raw
In response to Re: additional json functionality  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Nov 17, 2013, at 2:26 PM, Dimitri Fontaine <dimitri@2ndQuadrant.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-levelobject. :-( 

> 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




pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: additional json functionality
Next
From: Andrew Dunstan
Date:
Subject: Re: additional json functionality