| From: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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>, 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-12 16:27:15 |
| Message-ID: | 202503121627.zbycnhvyzky5@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-Mar-12, David G. Johnston wrote:
> 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.
I agree. I think this patch is correct to treat NULLs in a special way
in the page that describes NULLs (particularly if it describes that at
the start of the page), but leave null values in other parts of the
documentation as they are today.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"I'm impressed how quickly you are fixing this obscure issue. I came from
MS SQL and it would be hard for me to put into words how much of a better job
you all are doing on [PostgreSQL]."
Steve Midgley, http://archives.postgresql.org/pgsql-sql/2008-08/msg00000.php
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2025-03-12 16:27:21 | Re: Question about duplicate JSONTYPE_JSON check |
| Previous Message | Álvaro Herrera | 2025-03-12 16:23:25 | Re: remove open-coded popcount in acl.c |