Re: BUG #18451: NULL fails to coerce to string when performing string comparison - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #18451: NULL fails to coerce to string when performing string comparison
Date
Msg-id CAKFQuwZ63T4idGFrJY5SYk658Jas9fs1yS2SHu2rr4DVaEM-ug@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18451: NULL fails to coerce to string when performing string comparison  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Apr 30, 2024 at 7:53 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
David Rowley <dgrowleyml@gmail.com> writes:
> On Wed, 1 May 2024 at 10:30, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Yeah, there's a documentation gap here.  I dug around a little and
>> really couldn't find anything anywhere in our SGML docs that explains
>> NULL in any detail; we tend to assume that you've already heard of it.

> What is really generic enough about SQL NULLs to put somewhere
> generic?

I think the key points I'd want to get across include:

I got the ball rolling here:


incorporating roughly all the points listed below, though not necessarily in the exact form shown or envisioned.

David J.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #18449: Altering column type fails when an SQL routine depends on the column
Next
From: Kostiantyn Tomakh
Date:
Subject: Re: BUG #18433: Logical replication timeout