From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: magnus.falch@gmail.com
Subject: Unnest discards rows with empty or null arrays
Date: Mon, 20 Dec 2021 11:40:47 +0000
Message-ID: <164000044713.26048.13078806558253708431@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/functions-srf.html
Description:
https://www.postgresql.org/message-id/17340-74d17bbe94cb4190%40postgresql.org
This behaviour is unexpected from an external perspective but after speaking
with depesz I can see the exact edge case it's guarding against.
Returning rows with null values when the function does not return anything,
would be natural except for the fact that null is a valid return value by
itself.
Discarding the row is preferential to giving ambiguous answers since it's a
very clear answer.
I can't see it mentioned anywhere in the documentation though.
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: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, magnus.falch@gmail.com
Subject: Re: Unnest discards rows with empty or null arrays
In-Reply-To: <164000044713.26048.13078806558253708431@wrigleys.postgresql.org>
* 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