pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedAddition to content
3+ messages / 3 participants
[nested] [flat]
Commits from this thread:
2020-11-09 d4fd571b3e a24cda29e2 d4fb509d07 7b9cee45ad ca0c8ea666 f47841fbad 24b83a5082 Doc: clarify data type behavior of COALESCE and NULLIF.
* Addition to content
@ 2020-11-08 18:31 PG Doc comments form <noreply@postgresql.org>
2020-11-09 16:09 ` Re: Addition to content Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2020-11-08 18:31 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: vadym.feskin@gmail.com
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Addition to content
2020-11-08 18:31 Addition to content PG Doc comments form <noreply@postgresql.org>
@ 2020-11-09 16:09 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-11-11 19:32 ` Re: Addition to content Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2020-11-09 16:09 UTC (permalink / raw)
To: vadym.feskin@gmail.com; +Cc: pgsql-docs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Addition to content
2020-11-08 18:31 Addition to content PG Doc comments form <noreply@postgresql.org>
2020-11-09 16:09 ` Re: Addition to content Tom Lane <tgl@sss.pgh.pa.us>
@ 2020-11-11 19:32 ` Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 3+ messages in thread
From: Bruce Momjian @ 2020-11-11 19:32 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: vadym.feskin@gmail.com; pgsql-docs@lists.postgresql.org
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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2020-11-11 19:32 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-11-08 18:31 Addition to content PG Doc comments form <noreply@postgresql.org>
2020-11-09 16:09 ` Tom Lane <tgl@sss.pgh.pa.us>
2020-11-11 19:32 ` Bruce Momjian <bruce@momjian.us>
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