From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Cc: | magnus(dot)falch(at)gmail(dot)com |
Subject: | Unnest discards rows with empty or null arrays |
Date: | 2021-12-20 11:40:47 |
Message-ID: | 164000044713.26048.13078806558253708431@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2021-12-20 12:03:03 | Re: The pg_stop_backup will return one row with three values. |
Previous Message | PG Doc comments form | 2021-12-19 21:08:09 | The pg_stop_backup will return one row with three values. |