From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: vadym.feskin@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Addition to content
Date: Wed, 11 Nov 2020 14:32:13 -0500
Message-ID: <20201111193213.GA25840@momjian.us> (raw)
In-Reply-To: <1984017.1604938199@sss.pgh.pa.us>
References: <160486028730.25500.15740897403028593550@wrigleys.postgresql.org>
<1984017.1604938199@sss.pgh.pa.us>
On Mon, Nov 9, 2020 at 11:09:59AM -0500, Tom Lane wrote:
> PG Doc comments form <noreply@postgresql.org> writes:
> > I would be helpful to add that NULLIF and COALESCE need to be of same data
> > type.
>
> That's not actually a correct statement ... which I guess just reinforces
> your point that the behavior needs to be documented.
FYI, this was done in this commit:
commit 24b83a5082
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon Nov 9 12:02:24 2020 -0500
Doc: clarify data type behavior of COALESCE and NULLIF.
After studying the code, NULLIF is a lot more subtle than you might
have guessed.
Discussion: https://postgr.es/m/160486028730.25500.15740897403028593550@wrigleys.postgresql.org
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: bruce@momjian.us, tgl@sss.pgh.pa.us, vadym.feskin@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Addition to content
In-Reply-To: <20201111193213.GA25840@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox