sql, toc: refine character set and collation document #2884
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TomShawn
added
type/enhancement
5 tasks
yikeke
reviewed
Apr 26, 2020
|
|
||
| 在 4.0 版本之前，TiDB 中可以指定大部分 MySQl 中的 Collation，并把这些 Collation 按照默认 Collation 处理，即以编码字节序为字符定序。和 MySQL 不同的是，TiDB 在比较字符前按照 Collation 的 `PADDING` 属性将字符补齐空格，因此会造成以下的行为区别： | ||
| 在 4.0 版本之前，TiDB 中可以指定大部分 MySQl 中的排序规则，并把这些排序规则按照默认排序规则处理，即以编码字节序为字符定序。和 MySQL 不同的是，TiDB 在比较字符前按照 排序规则 的 `PADDING` 属性将字符补齐空格，因此会造成以下的行为区别： |
There was a problem hiding this comment.
Suggested change
| 在 4.0 版本之前，TiDB 中可以指定大部分 MySQl 中的排序规则，并把这些排序规则按照默认排序规则处理，即以编码字节序为字符定序。和 MySQL 不同的是，TiDB 在比较字符前按照 排序规则 的 `PADDING` 属性将字符补齐空格，因此会造成以下的行为区别： | |
| 在 4.0 版本之前，TiDB 中可以指定大部分 MySQL 中的排序规则，并把这些排序规则按照默认排序规则处理，即以编码字节序为字符定序。和 MySQL 不同的是，TiDB 在比较字符前按照排序规则的 `PADDING` 属性将字符补齐空格，因此会造成以下的行为区别： |
There was a problem hiding this comment.
这里有误，应该是 “TiDB 在比较字符前按照排序规则的 PADDING 属性将字符末尾的空格删除”， 英文版也需要更改。
yikeke
reviewed
Apr 26, 2020
yikeke
reviewed
Apr 29, 2020
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
yikeke
reviewed
Apr 29, 2020
yikeke
reviewed
Apr 29, 2020
yikeke
reviewed
Apr 29, 2020
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
TomShawn
added
the
status/can-merge
TomShawn
removed
the
status/can-merge
sre-bot
added a commit
to sre-bot/docs-cn
that referenced
this pull request
Apr 29, 2020
* sql, toc: refine character set and collation document * address comments * address comments Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com> * Apply suggestions from code review Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com>
5 tasks
|
cherry pick to release-4.0 in PR #2928 |
TomShawn
added a commit
that referenced
this pull request
Apr 29, 2020
* sql, toc: refine character set and collation document * address comments * address comments Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com> * Apply suggestions from code review Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com> Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com>
|
This PR‘s commits need to be manually cherry-picked to release-3.1, release-3.0, and release-2.1. @TomShawn will help open the PRs. |
5 tasks
rleungx
pushed a commit
to rleungx/docs-cn
that referenced
this pull request
May 22, 2020
* sql, toc: refine character set and collation document * address comments * address comments Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com> * Apply suggestions from code review Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: Keke Yi <40977455+yikeke@users.noreply.github.com> Co-authored-by: pingcap-github-bot <sre-bot@pingcap.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is changed, added or deleted? (Required)
排序规则andcollation-->排序规则Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?