Re: json (b) and null fields

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-28 03:00:49
Message-ID: 542779E1.2070702@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 09/27/2014 10:52 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 09/27/2014 06:27 PM, Tom Lane wrote:
>>> So my vote is for a separate function and no optional arguments.
>> You mean like row_to_json_no_nulls() and json_agg_no_nulls()?
> I thought you were proposing that we should revert the committed patch
> lock-stock-n-barrel, and instead invent json_strip_null_fields().
> That's instead, not in addition to. Even if you weren't saying that
> exactly, that's where my vote goes.

I was just exploring alternatives. But I think that's where my vote goes
too.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-09-28 03:58:27 Re: json (b) and null fields
Previous Message Tom Lane 2014-09-28 02:52:59 Re: json (b) and null fields