planner: DELETE
cannot delete data in some cases when the database name is capitalized (#21202)
#21206
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.
cherry-pick #21202 to release-4.0
What problem does this PR solve?
Issue Number: close #21200
Problem Summary:
The
CurrentDB
in session vars is stored the original string representation. (i.e. if we create the database name astEsT1
, theCurrentDB
would betEsT1
.However, in the codes that we changed in the pr, we treat the
CurrentDB
as its lower representation. This leads to wrong string comparison result. SoDELETE
might not delete the data correctly.What is changed and how it works?
Proposal: xxx
What's Changed:
Wrap
CIStr
upon theCurrentDB
.Related changes
Check List
Tests
Release note
DELETE
may not delete data correctly when the database name is not in pure lower representation.