Correct MySQL Shell/Client section (#12987) #13133
Merged
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.
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?