Re: Document NULL

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: 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: 2024-12-09 21:57:17
Message-ID: CAKFQuwbqKCEw-NdA=TaYYD7=4CBtoZA4qEbnRvixyusPBV8KWw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 20, 2024 at 7:24 PM jian he <jian(dot)universality(at)gmail(dot)com> wrote:

>
> attached image.png for
> 5.2.7.2. Array Elements and IN Bag Members
> the example is too overwhelming, one or two should be enough?
>

Agreed, fixed in the upcoming v5. The four outputs are actually two
equivalent pairs so I framed them up as such and removed two of the results.

> 5.2.7.3. Single-Column Subquery Rows.
> two examples, can be reduced to one.
>

Disagree, the fact that the two outputs are different is precisely the
point of having the two queries. I could see an argument for removing
both, given the pair outputs are indeed the same pair in the previous
sect3. But since they are separate sect3s I'm inclined to keep this intact.

> "does not support...does not include" double negation, can we make it
> "positive".
> "not null constraints." should be "not-null constraints"?
>

I've also reworked this for v5

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2024-12-09 22:10:30 Unmark gen_random_uuid() function leakproof
Previous Message Andres Freund 2024-12-09 21:42:58 Managing IO workers in postmaster's state machine