-
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
faq: update mysql8 client fail to connect tidb #3577
Conversation
Please fix CI. |
faq/tidb-faq.md
Outdated
mysql -h 127.0.0.1 -u root -P 4000 --default-auth=mysql_native_password --default-character-set=utf8 | ||
``` | ||
|
||
原因是字符集支持以及[密码验证方式的兼容性](/security-compatibility-with-mysql.md)。 |
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.
什么的原因呢?
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.
就兼容性问题呀
我们兼容的是 mysql7 的行为
mysql8 把默认的密码加密方式改掉了,所以要加参数指定使用旧的加密方式
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.
这句话没说清楚,改成无法登陆的原因是 MySQL 8.0 会更改默认的密码加密方式,所以需要添加以上参数指定使用旧的加密方式
?
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.
无法登陆的原因是因为我们对字符集的支持以及我们在密码验证方式上的兼容性
没有兼容 mysql8 的默认行为
所以需要添加以上参数指定使用旧的加密方式
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.
无法登陆的原因是 TiDB 对字符集的支持和密码校验方式上不兼容 MySQL 的默认行为,所以需要添加以上参数指定使用旧的加密方式。
这样呢?可以把解释加进文档里
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.
可以再丰富一下描述,不着急。 @tiancaiamao
Co-authored-by: TomShawn <[email protected]>
Co-authored-by: TomShawn <[email protected]>
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
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
@tennix,Thanks for your review. |
/merge |
/run-all-tests |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-3.0 in PR #3871 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-3.1 in PR #3872 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-4.0 in PR #3873 |
Signed-off-by: ti-srebot <[email protected]> Co-authored-by: tiancaiamao <[email protected]>
* cherry pick #3577 to release-3.1 Signed-off-by: ti-srebot <[email protected]> * Update tidb-faq.md Co-authored-by: tiancaiamao <[email protected]> Co-authored-by: TomShawn <[email protected]>
* cherry pick #3577 to release-3.0 Signed-off-by: ti-srebot <[email protected]> * Update tidb-faq.md Co-authored-by: tiancaiamao <[email protected]> Co-authored-by: TomShawn <[email protected]>
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
pingcap/tidb#6942
pingcap/tidb#7606