Skip to content

Conversation

hawkfish
Copy link
Contributor

These should only be a allowed when the ordering expressions are in the argument list. Anything else is confusing and ambiguous. This is what PG does too.

fixes: #11269
fixes: duckdblabs/duckdb-internal#1639

These should only be a allowed when the ordering expressions
are in the argument list. Anything else is confusing and ambiguous.
This is what PG does too.

fixes: duckdb#11269
fixes: duckdblabs/duckdb-internal#1639
@github-actions github-actions bot marked this pull request as draft March 22, 2024 22:37
@Mytherin Mytherin marked this pull request as ready for review March 22, 2024 22:45
@github-actions github-actions bot marked this pull request as draft March 23, 2024 02:56
@Mytherin Mytherin marked this pull request as ready for review March 23, 2024 14:31
@Mytherin Mytherin merged commit 8ef134f into duckdb:main Mar 25, 2024
@Mytherin
Copy link
Collaborator

Thanks!

@hawkfish hawkfish deleted the distinct-sorted-aggs branch March 26, 2024 16:04
github-actions bot pushed a commit to duckdb/duckdb-r that referenced this pull request Mar 28, 2024
Merge pull request duckdb/duckdb#11321 from hawkfish/distinct-sorted-aggs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DISTINCT not compatible with ORDER BY in aggregate functions
2 participants