Minor improvement of SqlServerParameterBasedSqlProcessor.Optimize
#33758
Conversation
This file contains 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
This opens up some additional query optimization opportunities.
|
This was found while investigating #33752, but is actually unrelated to that issue. |
maumar
approved these changes
Jun 4, 2024
|
I'm always a bit scared when changing order of operations in the optimizer, but this one should be safe. Thanks @ranma42 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Running the
SkipTakeCollapsingExpressionVisitorbeforeRelationalParameterBasedSqlProcessor.Optimizeopens up some additional query optimization opportunities that can lead to a simpler query.