Addition to content

Started by PG Bug reporting formover 5 years ago3 messagesdocs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/13/functions-conditional.html
Description:

Hello

I would be helpful to add that NULLIF and COALESCE need to be of same data
type.

Thank you

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: PG Bug reporting form (#1)
Re: Addition to content

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.

regards, tom lane

#3Bruce Momjian
bruce@momjian.us
In reply to: Tom Lane (#2)
Re: Addition to content

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: /messages/by-id/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