info_schema: fix memtable column flag type (#15944) #16004
Merged
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
|
/run-all-tests |
sre-bot
added
sig/sql-infra
ghost
requested a review
from 
zimulala
approved these changes
Apr 2, 2020
zimulala
added
the
status/can-merge
|
/run-all-tests |
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 #15944 to release-4.0
What problem does this PR solve?
when building a memory table, TiDB will use flag =
unsignedto fill those columns with number type, such asTypeLong,TypeLonglong... exceptTypevarcharandTypeblob.That means it will ignore the user-specified flag in the table definition.
What is changed and how it works?
build memory table with user-defined flag rather than the default unsigned
Tests
Release note: info_schema: fix memtable column flag type