Repository navigation
Conversation
…olumn A nullable UNIQUE column permits multiple NULL rows that may differ in other columns, so it does not functionally determine them once NULLs are grouped together. Only use dependencies that are valid across NULLs when removing redundant GROUP BY expressions.
Only eliminate DISTINCT when the functional dependency remains valid across NULLs, preventing duplicate NULL values after GROUP BY. Add SQL regressions for grouped projections, aliases, subqueries, outer counts, and composite keys. Preserve NOT NULL UNIQUE optimizations.
github-actions
Bot
added
documentation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #26220 +/- ##
==========================================
- Coverage 82.93% 82.93% -0.01%
==========================================
Files 1154 1154
Lines 458002 458049 +47
Branches 458002 458049 +47
==========================================
+ Hits 379856 379888 +32
- Misses 55123 55131 +8
- Partials 23023 23030 +7 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
2 participants
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.
Which issue does this PR close?
Rationale for this change
A nullable UNIQUE column permits multiple NULL rows, so it cannot safely
determine other grouping columns. Dropping those columns can merge distinct
groups and return incorrect results.
What changes are included in this PR?
What is the testing strategy for this PR?
SLT and plan-builder tests cover nullable and composite UNIQUE keys,
DISTINCT after GROUP BY, and valid PRIMARY KEY / NOT NULL UNIQUE cases.
The DISTINCT regressions fail without the fix.
Are there any user-facing changes?
Yes: incorrect results are fixed