-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Correct MySQL Shell/Client section (#12987) #13134
Correct MySQL Shell/Client section (#12987) #13134
Conversation
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
Co-authored-by: shichun-0415 <89768198+shichun-0415@users.noreply.github.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: ab9e489
|
/verify |
1 similar comment
/verify |
This is an automated cherry-pick of #12987
Signed-off-by: Aolin aolin.zhang@pingcap.com
What is changed, added or deleted? (Required)
There are two official command-line clients for MySQL, both open-source and released by the Oracle MySQL team.
MySQL Client (
mysql
), which is part of the MySQL Server code base, but can be installed separately viayum install mysql
on most YUM based linux distributions. With the offical YUM repo this becomesyum install mysql-community-client
. This client is written in C and has existed for as long as MySQL does.MySQL Shell (
mysqlsh
), which is a separate code base and can be installed separately. This is a newer tool and supports SQL, but also JS and Python. It has a more modern code base and is more extendable than the 'old' client.It looks like these two were mixed up into a single section of the docs.
Simpletab preview:
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 (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?