Re: Documentation enancement regarding NULL and operators

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Luca Dametto <postgresqlmailing(at)damettoluca(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Documentation enancement regarding NULL and operators
Date: 2024-12-18 14:32:34
Message-ID: 3a2d42ac40a5f7aac315227aab374c693b701781.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, 2024-12-15 at 17:35 +0000, Luca Dametto wrote:
> Most programming languages return "true" when two null values are compared,
> and false when, being the two values nullable, one of them is null and the
> other one isn't.
>
> [not SQL, however]
>
> Whilst I'd love to discuss the reasons of this, I understand that it would
> be a waste of time for everyone, as we cannot change the status-quo even
> if it made sense, as it would break many thousands of projects.
>
> For that reason, I'd just like to improve the documentation to add at least
> a note about "hey, this won't work as you might expect, because it works
> in a different way than 99% of programming languages out there.".

There are already efforts to improve the documentation concerning NULL:
https://commitfest.postgresql.org/51/5086/
If that doesn't cover your case, perhaps you can join the discussion
and suggest improvements.

Yours,
Laurenz Albe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2024-12-18 15:11:54 Re: Intermittent errors when fetching cursor rows on PostgreSQL 16
Previous Message Laurenz Albe 2024-12-18 14:28:43 Re: Query about pg_wal directory filled up