| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, Darryl Dixon <darryl(dot)dixon(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18451: NULL fails to coerce to string when performing string comparison |
| Date: | 2024-05-01 15:25:41 |
| Message-ID: | CAKFQuwZ63T4idGFrJY5SYk658Jas9fs1yS2SHu2rr4DVaEM-ug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Apr 30, 2024 at 7:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> > On Wed, 1 May 2024 at 10:30, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kostiantyn Tomakh | 2024-05-01 17:25:35 | Re: BUG #18433: Logical replication timeout |
| Previous Message | Tom Lane | 2024-05-01 14:08:43 | Re: BUG #18449: Altering column type fails when an SQL routine depends on the column |