| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json (b) and null fields |
| Date: | 2014-09-28 03:58:27 |
| Message-ID: | CAOuzzgpvx5EDt+KBUKjs7_mUH78nudDNRxbJYUYGSHMAv9MK=A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
All,
On Saturday, September 27, 2014, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> 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.
>
I'm fine with that. I'd like the strip-Nulls capability, but seems like
it'd be better off as an independent function (or functions) instead.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2014-09-28 04:32:21 | Re: Patch to support SEMI and ANTI join removal |
| Previous Message | Andrew Dunstan | 2014-09-28 03:00:49 | Re: json (b) and null fields |