SQL: 2023 is finished: Here is what's new

Re:SQL: 2023 is finished: Here is what's new by Dylan16807 on Thursday April 13, 2023 @11:36PM (#35565245)

It's already grouping by the primary key of `product`. Why would you need to add another column in `product` to the group by?

[ Parent | on HN ]

Re:SQL: 2023 is finished: Here is what's new by jbverschoor on Friday April 14, 2023 @03:38AM (#35566610)

If that’s the very specific case, then they should be clear about it. But my interpretation was that our order by ungrouped column

If it’s about preferring by non selected columns, that’d be fine.

Something is wrong somewhere imo

[ Parent | on HN ]

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.*

[ Parent | on HN ]