Re: Document NULL - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Document NULL
Date
Msg-id CAKFQuwYsCyCyeyxysUxL0r=P6s751LbkmQ4R-2cZ6OjXWJa1vQ@mail.gmail.com
Whole thread Raw
In response to Re: Document NULL  (Marcos Pegoraro <marcos@f10.com.br>)
Responses Re: Document NULL
List pgsql-hackers
On Wednesday, March 12, 2025, Marcos Pegoraro <marcos@f10.com.br> wrote:
Em ter., 11 de mar. de 2025 às 17:43, Tom Lane <tgl@sss.pgh.pa.us> escreveu:
I think that idea (changing all the docs) is a complete nonstarter
because people would not understand why the results they get don't
look like what it says in the docs.  Of course, we could fix that
by changing the factory default for \pset null, but that seems like
even more of a nonstarter.

And if we use a tag to display nulls, like <nullvalue>NULL</nullvalue>
Then all null values would be the same, and the user would understand what it means, because it's painted differently.
And then would be an unique way of appearance, on this page and all others

I’m not accepting this line of work as part of this patch.  Please limit this to the merits of choosing \N as the particular value for \pset null on this page.  You can start a new thread regarding a policy change for marking up null values in the whole of the documentation.  But as Tom said, I don’t see that going anywhere.

David J.

pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: Question about duplicate JSONTYPE_JSON check
Next
From: torikoshia
Date:
Subject: Re: Change log level for notifying hot standby is waiting non-overflowed snapshot