-
Notifications
You must be signed in to change notification settings - Fork 688
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
Update docs for deprecate-integer-display-length=true #19159
Update docs for deprecate-integer-display-length=true #19159
Conversation
/hold |
/unhold |
Co-authored-by: Grace Cai <qqzczy@126.com>
@CbcWestwolf: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What is changed, added or deleted? (Required)
Update the docs to follow the change in default value for
deprecate-integer-display-length
.This follows the behavior in MySQL.
Integer types can be defined like
int(10)
orint(8)
orint
. People often misunderstand the meaning of the number that is specified here (e.g. the 10 and the 8 here). This does not change the capacity of the value that can be stored it only changes how it might be displayed.See also https://dev.mysql.com/doc/refman/8.0/en/numeric-type-attributes.html and pingcap/tidb#56529
Important: This changes the documentation for the variable and updates the page describing numeric types. However this does NOT update the output that might have changed.
Output that changes based on this variable:
SHOW CREATE TABLE
DESCRIBE <table>
,EXPLAIN <table>
andSHOW COLUMNS FROM ...
EXPLAIN...
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Don't merge before this PR has been merged
pingcap/tidb#56529
Do your changes match any of the following descriptions?