Re: json (b) and null fields
| От | Stephen Frost |
|---|---|
| Тема | Re: json (b) and null fields |
| Дата | |
| Msg-id | CAOuzzgpvx5EDt+KBUKjs7_mUH78nudDNRxbJYUYGSHMAv9MK=A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: json (b) and null fields (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: json (b) and null fields
|
| Список | pgsql-hackers |
All,
On Saturday, September 27, 2014, Andrew Dunstan <andrew@dunslane.net> wrote:
On Saturday, September 27, 2014, Andrew Dunstan <andrew@dunslane.net> wrote:
On 09/27/2014 10:52 PM, Tom Lane wrote:Andrew Dunstan <andrew@dunslane.net> writes:On 09/27/2014 06:27 PM, Tom Lane wrote:I thought you were proposing that we should revert the committed patchSo my vote is for a separate function and no optional arguments.You mean like row_to_json_no_nulls() and json_agg_no_nulls()?
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
В списке pgsql-hackers по дате отправления: