Skip to content

faq: update mysql8 client fail to connect tidb#3577

Merged
ti-srebot merged 7 commits into
pingcap:masterfrom
tiancaiamao:update-faq-mysql8
Jul 3, 2020
Merged

faq: update mysql8 client fail to connect tidb#3577
ti-srebot merged 7 commits into
pingcap:masterfrom
tiancaiamao:update-faq-mysql8

Conversation

@tiancaiamao
Copy link
Copy Markdown
Contributor

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • v4.0 (TiDB 4.0 versions)
  • v3.1 (TiDB 3.1 versions)
  • v3.0 (TiDB 3.0 versions)
  • v2.1 (TiDB 2.1 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

pingcap/tidb#6942
pingcap/tidb#7606

@tiancaiamao
Copy link
Copy Markdown
Contributor Author

PTAL @tennix @jackysp

@jackysp
Copy link
Copy Markdown
Contributor

jackysp commented Jun 9, 2020

Please fix CI.

Comment thread faq/tidb-faq.md Outdated
Comment thread 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)。
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

什么的原因呢?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

就兼容性问题呀
我们兼容的是 mysql7 的行为
mysql8 把默认的密码加密方式改掉了,所以要加参数指定使用旧的加密方式

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这句话没说清楚,改成无法登陆的原因是 MySQL 8.0 会更改默认的密码加密方式,所以需要添加以上参数指定使用旧的加密方式

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

无法登陆的原因是因为我们对字符集的支持以及我们在密码验证方式上的兼容性
没有兼容 mysql8 的默认行为
所以需要添加以上参数指定使用旧的加密方式

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

无法登陆的原因是 TiDB 对字符集的支持和密码校验方式上不兼容 MySQL 的默认行为,所以需要添加以上参数指定使用旧的加密方式。 这样呢?可以把解释加进文档里

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

可以再丰富一下描述,不着急。 @tiancaiamao

@TomShawn TomShawn added the translation/doing This PR’s assignee is translating this PR. label Jun 10, 2020
@TomShawn TomShawn requested review from TomShawn, jackysp and tennix June 10, 2020 03:22
Comment thread faq/tidb-faq.md Outdated
@TomShawn TomShawn assigned tiancaiamao and unassigned toutdesuite Jun 10, 2020
@TomShawn TomShawn added translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. and removed translation/doing This PR’s assignee is translating this PR. labels Jun 10, 2020
Comment thread faq/tidb-faq.md Outdated
TomShawn and others added 5 commits June 10, 2020 17:20
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
@tiancaiamao
Copy link
Copy Markdown
Contributor Author

PTAL @TomShawn @jackysp

@TomShawn
Copy link
Copy Markdown
Contributor

LGTM

Copy link
Copy Markdown
Member

@tennix tennix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot ti-srebot added the status/LGT1 Indicates that a PR has LGTM 1. label Jul 3, 2020
Copy link
Copy Markdown
Contributor

@ti-srebot ti-srebot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-srebot
Copy link
Copy Markdown
Contributor

@tennix,Thanks for your review.

@TomShawn
Copy link
Copy Markdown
Contributor

TomShawn commented Jul 3, 2020

/merge

@ti-srebot ti-srebot added the status/can-merge Indicates a PR has been approved by a committer. label Jul 3, 2020
@ti-srebot
Copy link
Copy Markdown
Contributor

/run-all-tests

@ti-srebot ti-srebot merged commit 3d19bdd into pingcap:master Jul 3, 2020
ti-srebot pushed a commit to ti-srebot/docs-cn that referenced this pull request Jul 3, 2020
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Copy Markdown
Contributor

cherry pick to release-3.0 in PR #3871

ti-srebot pushed a commit to ti-srebot/docs-cn that referenced this pull request Jul 3, 2020
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Copy Markdown
Contributor

cherry pick to release-3.1 in PR #3872

ti-srebot pushed a commit to ti-srebot/docs-cn that referenced this pull request Jul 3, 2020
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Copy Markdown
Contributor

cherry pick to release-4.0 in PR #3873

TomShawn pushed a commit that referenced this pull request Jul 3, 2020
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>

Co-authored-by: tiancaiamao <tiancaiamao@gmail.com>
TomShawn added a commit that referenced this pull request Jul 3, 2020
* cherry pick #3577 to release-3.1

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>

* Update tidb-faq.md

Co-authored-by: tiancaiamao <tiancaiamao@gmail.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
ti-srebot added a commit that referenced this pull request Jul 3, 2020
* cherry pick #3577 to release-3.0

Signed-off-by: ti-srebot <ti-srebot@pingcap.com>

* Update tidb-faq.md

Co-authored-by: tiancaiamao <tiancaiamao@gmail.com>
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/can-merge Indicates a PR has been approved by a committer. status/LGT1 Indicates that a PR has LGTM 1. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants