You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this may actually be by design. I recently read through the discussion in #1363 and this comment suggests that using group, even if it is empty, will reset (remove) sorting.
Ok I see part of it might be by design but if the sorting is private only to the group then I'd say the output should be a combination of CTEs where the sorting still affects the take 1 within the grouping but leaves the final sorting of the relation unaffected.
Our use case is that our prql is dynamically generated so grouping by nothing is just an edge case that we have to handle manually, which is not unreasonable, but from the way aggregations and things are seemingly unaffected by an empty group, we got the impression that group {} is basically noop.
What happened?
It seems grouping by nothing is otherwise a valid thing to do, except it makes an inner
sort
do nothing.PRQL input
SQL output
Expected SQL output
MVCE confirmation
Anything else?
No response
The text was updated successfully, but these errors were encountered: