executor: throw error when prepared statement is execute, deallocate or prepare (#21962) #21972
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
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
|
/run-all-tests |
ti-srebot
added
sig/execution
|
@xuyifangreeneyes you're already a collaborator in bot's repo. |
qw4990
approved these changes
Jan 26, 2021
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.
cherry-pick #21962 to release-4.0
What problem does this PR solve?
Issue Number: close #17412
Problem Summary:
TiDB regards sql like
prepare stmt1 from "execute stmt"as valid.What is changed and how it works?
What's Changed:
When prepared statement is execute, deallocate or prepare, throw error
ERROR 1295 (HY000): This command is not supported in the prepared statement protocol yet.Related changes
Check List
Tests
Release note