Re: BUG #14178: output of jsonb_object and json_object doesn't match textually - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #14178: output of jsonb_object and json_object doesn't match textually
Date
Msg-id CAB7nPqRrdJeRcTGv+64xLZuGfVo9xvQyv+zu0_96SALiFrP=5g@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14178: output of jsonb_object and json_object doesn't match textually  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: BUG #14178: output of jsonb_object and json_object doesn't match textually  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-bugs
On Tue, Jun 7, 2016 at 3:48 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> On Tue, Jun 7, 2016 at 2:40 PM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
>> On Tue, Jun 7, 2016 at 10:42 AM,  <ap@zip.com.au> wrote:
>>> I think json_object should provide similar output. Consistency is nice
>>> aesthetically and as being in line with the principle of least surprise.
>>> Its lack may lead to possible unpleasant results if anyone tries to deal
>>> with a JSON structure as TEXT (for whatever reason).
>>
>> That's a debatable point, and as any output is legal json it does not
>> actually hurt one way or another. However, as json_object has been
>> introduced at the same time as jsonb, I'd tend as well to think that
>> consistency is a good idea if possible, see the patch attached.
>
> (It's a shame that json_build_object and json_object_agg also don't
> agree on where to put whitespace...)

Right, missed that, as well as json_object_two_arg.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #14178: output of jsonb_object and json_object doesn't match textually
Next
From: dmigowski@ikoffice.de
Date:
Subject: BUG #14179: Not enough info in error message