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.
follow up to #4035 to explicitly answer misunderstandings exhibited in duckdb/duckdb#14755 and duckdb/duckdb#14941
By the way: Do you folks have recommendations for the common situation that one has a large table that's sorted by multiple columns (C1,...,Cn) and one wants to successively perform aggregations over Cn then Cn-1, ...? In that situation, there would be a trivial O(N) solution to doing each of the aggregations by hand, simply by checking group boundaries on the fly and producing aggregate values in an order preserving manner. Feels like the following duckdb snippet