Re: Document NULL - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Document NULL
Date
Msg-id CAKFQuwY6ctmky5e+ahKGB2e3p48_fJ15xjmvVA4kTb1sOU650A@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 Tue, Mar 11, 2025 at 1:19 PM Marcos Pegoraro <marcos@f10.com.br> wrote:
Em ter., 11 de mar. de 2025 às 16:47, David G. Johnston <david.g.johnston@gmail.com> escreveu:
Since COPY uses \N I figured it was a decent choice. <null> or <NULL> came to mind too, but there were long compared to 1, 2, and 4 that appear along side it.
Well, I would use <null>, it doesn't need any explanation and we could use it everywhere else.
I understand that this page we have more NULL values than everywhere else combined, but it's a good opportunity to set a standard for all documentation


If someone writes a patch to make everywhere <null> and changes this page in the process I wouldn't complain.  For now there is no such standard, we use empty string everywhere else, and that isn't a good choice here IMO.  It is probably a good choice for elsewhere since the empty string is our default.  While specific to this page \N reads the best for these examples IMO.  But I'll concede to whatever if others think this choice is a review/commit blocker.

David J.

pgsql-hackers by date:

Previous
From: Marcos Pegoraro
Date:
Subject: Re: Document NULL
Next
From: Tom Lane
Date:
Subject: Re: Document NULL