Am Di., 23. Jan. 2024 um 15:15 Uhr schrieb Laurenz Albe <laurenz.a...@cybertec.at>: > I understand the motivation, but I bet it's not what will make users > happy. > > If you need to disambiguate between SQL NULL and JSON null, my > preferred solution would be to omit SQL NULL columns from the output > altogether.
I fully support Laurenz's proposal and argumentation. The main use case for such a JSON output feature is further processing somewhere else. --Stefan Am Di., 23. Jan. 2024 um 15:15 Uhr schrieb Laurenz Albe <laurenz.a...@cybertec.at>: > > On Mon, 2024-01-22 at 16:19 +0100, Christoph Berg wrote: > > What I did now in v3 of this patch is to print boolean and numeric > > values (ints, floats, numeric) without quotes, while adding the quotes > > back to json. This solves the NULL vs 'null'::json problem. > > The patch is working as advertised. > > I am kind of unhappy about this change. It seems awkward and undesirable > so have JSON values decorated with weird quoting in JSON output. > I understand the motivation, but I bet it's not what will make users > happy. > > If you need to disambiguate between SQL NULL and JSON null, my > preferred solution would be to omit SQL NULL columns from the output > altogether. > > Yours, > Laurenz Albe > >
