Expand tuple comparisons into nested OR/AND form before normalization#68
Open
axiak wants to merge 1 commit into
Open
Expand tuple comparisons into nested OR/AND form before normalization#68axiak wants to merge 1 commit into
axiak wants to merge 1 commit into
Conversation
Rewrites expressions like (a,b,c) > (x,y,z) into the equivalent nested form: (a>x OR (a=x AND (b>y OR (b=y AND c>z)))). This enables MySQL to use individual column indexes instead of requiring a composite index matching the tuple order. Applies to >, >=, <, <= operators when the LHS consists entirely of column references. Gated behind --expand_tuple_comparisons flag (default false). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Description
Rewrites expressions like (a,b,c) > (x,y,z) into the equivalent nested form: (a>x OR (a=x AND (b>y OR (b=y AND c>z)))). This enables MySQL to use individual column indexes instead of requiring a composite index matching the tuple order.
Applies to >, >=, <, <= operators when the LHS consists entirely of column references.
Gated behind --expand_tuple_comparisons flag (default false).
Related Issue(s)
This is a workaround over this longstanding MySQL bug: https://bugs.mysql.com/bug.php?id=111952
Checklist
Deployment Notes