Remove duplicated ForceColumnEncryption property check #2166
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
Codecov ReportAll modified lines are covered by tests ✅
... and 11 files with indirect coverage changes 📢 Thoughts on this report? Let us know!. |
David-Engel
approved these changes
Oct 3, 2023
David-Engel
approved these changes
Oct 20, 2023
DavoudEshtehari
added
💡 Enhancement
DavoudEshtehari
approved these changes
Nov 7, 2023
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.
Writing parameter is done on every execution because there are always server parameters even if there aren't user parameters. I noticed this duplicated call to parameter.ForceColumnEncryption while profiling something else and since it's a hot path I thought it would be worth removing the second call to save a few cycles.