From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Document NULL |
Date: | 2025-03-11 20:32:00 |
Message-ID: | CAKFQuwY6ctmky5e+ahKGB2e3p48_fJ15xjmvVA4kTb1sOU650A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 11, 2025 at 1:19 PM Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
> Em ter., 11 de mar. de 2025 às 16:47, David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-03-11 20:43:49 | Re: Document NULL |
Previous Message | Marcos Pegoraro | 2025-03-11 20:18:28 | Re: Document NULL |