| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | David Christensen <david(at)pgguru(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] GROUP BY ALL |
| Date: | 2024-07-23 20:02:15 |
| Message-ID: | b46070c0-0e98-49a0-823f-fa7e13bf626b@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23.07.24 00:29, Tom Lane wrote:
> (Personally, I'd wonder exactly what ALL is quantified over: the
> whole output of the FROM clause, or only columns mentioned in the
> SELECT tlist, or what? And why that choice rather than another?)
Looks like the main existing implementations take it to mean all entries
in the SELECT list that are not aggregate functions.
https://duckdb.org/docs/sql/query_syntax/groupby.html#group-by-all
https://docs.databricks.com/en/sql/language-manual/sql-ref-syntax-qry-select-groupby.html#parameters
https://docs.snowflake.com/en/sql-reference/constructs/group-by#parameters
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-07-23 20:07:33 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |
| Previous Message | Jeff Davis | 2024-07-23 19:56:28 | Re: [18] Policy on IMMUTABLE functions and Unicode updates |