On 06/09/2025 02:02, Jason Tiller wrote:
Thanks for your feedback! I'm a SQL newbie and the "implicit row constructor"
syntax was an unwelcome surprise.
The reason for it is so you can write WHERE (a, b) > (1, 2) and similar.
Perhaps WHERE ROW(a, b) > ROW(1, 2) would have been better, perha
Hi, Tom,
Thanks for your feedback! I'm a SQL newbie and the "implicit row constructor"
syntax was an unwelcome surprise. I guess painful debugging is one way to
cement a concept...
Seems like this is a nothing-burger and probably has no place in the PostgreSql
documentation. Although I feel li
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/17/sql-select.html
Description:
Here: https://www.postgresql.org/docs/current/sql-select.html
There is no mention of the difference in PostgreSql behavior if the select
list of columns is su
On Thursday, September 4, 2025, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/17/sql-select.html
> Description:
>
> Here: https://www.postgresql.org/docs/current/sql-select.html
>
> There is no mention o
PG Doc comments form writes:
> There is no mention of the difference in PostgreSql behavior if the select
> list of columns is surrounded by parentheses or not.
What you've written there is an implicit row constructor, that is
"(a,b,...)" is taken as "ROW(a,b,...)". These are documented at [1],
