| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Document NULL |
| Date: | 2024-05-03 14:09:58 |
| Message-ID: | 6c11f5a2-478c-42af-9208-e82bb710e78a@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02.05.24 17:23, David G. Johnston wrote:
> Version 2 attached. Still a draft, focused on topic picking and overall
> structure. Examples and links planned plus the usual semantic markup stuff.
>
> I chose to add a new sect1 in the user guide (The SQL Language) chapter,
> "Data".
Please, let's not.
A stylistic note: "null" is an adjective. You can talk about a "null
value" or a value "is null". These are lower-cased (or maybe
title-cased). You can use upper-case when referring to SQL syntax
elements (in which case also tag it with something like <literal>), and
also to the C-language symbol (tagged with <symbol>). We had recently
cleaned this up, so I think the rest of the documentation should be
pretty consistent about this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-05-03 14:12:46 | Re: Support LIKE with nondeterministic collations |
| Previous Message | Jacob Champion | 2024-05-03 14:05:38 | Re: [PATCH] json_lex_string: don't overread on bad UTF8 |