feat: Support SELECT DISTINCT ON - #221
Merged
Merged
Conversation
MazterQyou
force-pushed
the
cubesql/distinct-on
branch
2 times, most recently
from
July 15, 2026 17:24
4f27d07 to
a9c4984
Compare
Signed-off-by: Alex Qyoun-ae <4062971+MazterQyou@users.noreply.github.com>
MazterQyou
force-pushed
the
cubesql/distinct-on
branch
from
July 16, 2026 21:42
a9c4984 to
b36b8e5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR implements
SELECT DISTINCT ON (...), which was previously silently ignored during planning: it is planned as aROW_NUMBER()window partitioned by theONexpressions and ordered by the query'sORDER BY, followed by a filter keeping the first row per partition, with Postgres validation thatORDER BYstarts with theONexpressions. Related test is included.