parser: fix bug empty string in "ESCAPED BY" subclause of "FIELDS" cause panic #7880
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
|
@lzmhhh123 please add some tests. |
|
LGTM |
|
/run-all-tests |
jackysp
added
status/LGT2
lzmhhh123
added a commit
to lzmhhh123/tidb
that referenced
this pull request
Oct 23, 2018
lzmhhh123
added a commit
to lzmhhh123/tidb
that referenced
this pull request
Oct 23, 2018
ngaut
pushed a commit
that referenced
this pull request
Oct 23, 2018
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.
What problem does this PR solve?
When
fieldsclause has empty string ofescaped bysubclause. It will cause panic.What is changed and how it works?
Simple change. Just add a judgement.
Check List
Tests