-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
info_schema: fix memtable column flag type #15944
Conversation
Codecov Report
@@ Coverage Diff @@
## master #15944 +/- ##
===========================================
Coverage 80.5056% 80.5056%
===========================================
Files 505 505
Lines 135598 135598
===========================================
Hits 109164 109164
Misses 17938 17938
Partials 8496 8496 |
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run-all-tests |
@AilinKid merge failed. |
/merge |
/run-all-tests |
cherry pick to release-4.0 in PR #16004 |
What problem does this PR solve?
when building a memory table, TiDB will use flag =
unsigned
to fill those columns with number type, such asTypeLong
,TypeLonglong
... exceptTypevarchar
andTypeblob
.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