From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
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 19:38:55 |
Message-ID: | CAB-JLwY-nOpxcpCWjT3DNuC+fTAa-6AuXSWZPmJvRzS2BRbajA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em ter., 11 de mar. de 2025 às 12:52, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:
> The markup surrounding the examples is correct now and I decided \N was
> the most useful representation of NULL given that the query data is single
> digit numbers. I really hate the non-readability of t/f output for
> booleans so I manually cleaned those up.
>
You defined \N to show NULL values. But then all other places in the DOCs
do not use this definition, so it can be confusing for the user.
Here we have a \N and everywhere else only spaces ?
I understand that there are many places to replace, but I think it would be
better to have a single standard everywhere, don't you think ?
On the other hand, if we replace them all, other users can be confused too,
if they do not read this page and see an \N on any other page.
What's this \N, he can think. \N is not self-explanatory.
regards
Marcos
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2025-03-11 19:41:08 | Re: AIO v2.5 |
Previous Message | Andres Freund | 2025-03-11 19:29:29 | Re: Some read stream improvements |