Re:SQL: 2023 is finished: Here is what's new
by amluto on Friday April 14, 2023 @05:04PM
(#35574736)
I assume that query optimizers are able to detect a GROUP BY of a primary key and other columns in the same table and optimize accordingly. But using this trick to change the set of valid queries seems odd. I think I'd rather see special syntax for it:
GROUP BY table.*
If it’s about preferring by non selected columns, that’d be fine.
Something is wrong somewhere imo