The problem with this and similar requests is that it would change the identifier scoping in incompatible ways and therefore potentially break a lot of existing SQL code.
That might be nice for manual experimentation, but for application use, this seems brittle compared to specifying the columns you really want to have and process.
So, why not a SORT BY ALL or a GROUPSORT BY ALL, too? Not always what you want (e.g., when you're ranking on a summarized column), but it often alphabetic order on the GROUP BY columns is just what the doctor ordered! :-)
17 comments
[ 782 ms ] story [ 1589 ms ] threadhttps://duckdb.org/docs/stable/sql/query_syntax/groupby
it's not something that i've found a particular use for, but it IS a thing you can do.