| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json (b) and null fields |
| Date: | 2014-09-29 20:32:36 |
| Message-ID: | 10962.1412022756@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-09-29 20:35:12 | Re: open items for 9.4 |
| Previous Message | Andres Freund | 2014-09-29 20:28:55 | Re: open items for 9.4 |