InList optimisation on more expressions#3347
Merged
Conversation
Contributor
Author
Tracking
Standard development
CI Testing Labels
Documentation checklist
|
Now always generating a FrameChangeId for each InList operator. This means we now support the optimisation for queries like `x IN range(0,1000)`.
Ignition
force-pushed
the
2025_10_15_InList_generalise
branch
from
0423f3d to
9b33267
Compare
|
imilinovic
approved these changes
Oct 16, 2025
as51340
pushed a commit
that referenced
this pull request
Oct 24, 2025
Now always generating a FrameChangeId for each InList operator. This means we now support the optimisation for queries like `x IN range(0,1000)`.
40 tasks
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.
Now always generating a FrameChangeId for each InList operator.
This means we now support the optimisation for queries like
x IN range(0,1000).