fix(prqlc, sort): do not require sort columns if it's followed by an aggregation #5347
+24
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #3200
sortalways required sorted columns which caused an unwanted column selection in the nextaggregate:column <SORTED_COLUMN> must appear in the GROUP BY clause or be used in an aggregate functionTo fix it, it simply checks if an
aggregateis present in the following transformsI didn't find a PRQL query where this change can be a regression. If you have something in mind, please share it! 🙏