Re: json (b) and null fields - Mailing list pgsql-hackers

From Tom Lane
Subject Re: json (b) and null fields
Date
Msg-id 10962.1412022756@sss.pgh.pa.us
Whole thread Raw
In response to Re: json (b) and null fields  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: json (b) and null fields
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 09/29/2014 04:14 PM, Tom Lane wrote:
>> More to the point, the way to fix any concerns about double parsing is to
>> create row_to_jsonb(), not to plaster a bunch of options on row_to_json().

> row_to_jsonb would be completely redundant with to_jsonb() in my recent 
> patch.

Right, which raises the question of whether we shouldn't just be
deprecating both array_to_json() and row_to_json()...

> And I don't want to add options like this there for the same reasons I 
> didn't want them in row_to_json().

Agreed.  IMO the place to have put the "pretty" functionality was in some
sort of json-to-text conversion function; it never belonged in an input
conversion function.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: open items for 9.4
Next
From: Tom Lane
Date:
Subject: Re: open items for 9.4