the potential issue that TiFlash cannot delete the delta data – Fix a bug that TiFlash adds wrong padding for non-binary characters in the CAST function – Fix the issue of incorrect results when handling order. Different from MySQL, TiDB deletes the space at the end of the character according to the PADDING attribute of the collation before comparing characters, which causes the following behavior differences: is case-insensitive and accent- insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY KEY);

order. Different from MySQL, TiDB deletes the space at the end of the character according to the PADDING attribute of the collation before comparing characters, which causes the following behavior differences: is case-insensitive and accent- insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY KEY); 'PRIMARY' # TiDB modifies �→ the `PADDING` behavior to be compatible with MySQL. Note: The implementation of padding in TiDB is different from that in MySQL. In MySQL, padding is implemented by filling in

order. Different from MySQL, TiDB deletes the space at the end of the character according to the PADDING attribute of the collation before comparing characters, which causes the following behavior differences: is case-insensitive and accent- insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY KEY); 'PRIMARY' # TiDB modifies �→ the `PADDING` behavior to be compatible with MySQL. Note: The implementation of padding in TiDB is different from that in MySQL. In MySQL, padding is implemented by filling in

order. Different from MySQL, TiDB deletes the space at the end of the character according to the PADDING attribute of the collation before comparing characters, which causes the following behavior differences: is case-insensitive and accent- insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: 2832 CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY 'PRIMARY' # TiDB modifies �→ the `PADDING` behavior to be compatible with MySQL. Note: The implementation of padding in TiDB is different from that in MySQL. In MySQL, padding is implemented by filling in

is case-insensitive and accent- insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY KEY); # TiDB modifies �→ the `PADDING` behavior to be compatible with MySQL. 3546 Note: The implementation of padding in TiDB is different from that in MySQL. In MySQL, padding is implemented by filling filling in spaces. In TiDB, padding is implemented by cutting out the spaces at the end. The two approaches are the same in most cases. The only exception is when the end of the string contains characters that

results might be incorrect when the LIKE operator is used for index range scans on a column with PADDING SPACE #48821 @time-and- fate • Fix the issue that generated columns might trigger concurrent read is case- insensitive and accent-insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY KEY); PRIMARY' -- TiDB �→ modifies the `PADDING` behavior to be compatible with MySQL. Note: The implementation of padding in TiDB is different from that in MySQL. In MySQL, padding is implemented by filling in

is case-insensitive and accent- insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY KEY); PRIMARY' # TiDB �→ modifies the `PADDING` behavior to be compatible with MySQL. Note: The implementation of padding in TiDB is different from that in MySQL. In MySQL, padding is implemented by filling in in spaces. In TiDB, padding is implemented by cutting out the spaces at the end. The two approaches are the same in most cases. The only exception is when the end of the string contains characters that are

版本之前，TiDB 中可以指定大部分 MySQL 中的排序规则，并把这些排序规则按照默认排序规则处理，即 以编码字节序为字符定序。和 MySQL 不同的是，TiDB 在比较字符前按照排序规则的 PADDING 属性将字符末尾 的空格删除，因此会造成以下的行为区别： CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci utf8mb4_unicode_ci 中任一种时，字符串 之间的比较是大小写不敏感 (case-insensitive) 和口音不敏感 (accent-insensitive) 的。同时，TiDB 还修正了排序规则 的 PADDING 行为： CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci PRIMARY KEY); Query Duplicate entry 'a ' for key 'PRIMARY' # TiDB 修正了 `PADDING` 行为，与 MySQL �→ 兼容。 注意： TiDB 中 padding 的实现方式与 MySQL 的不同。在 MySQL 中，padding 是通过补齐空格实现的。而 在 TiDB 中 padding 是通过裁剪掉末尾的空格来实现的。两种做法在绝大多数情况下是一致的， 唯一的例外是字符串尾部包含小于空格

版本之前，TiDB 中可以指定大部分 MySQL 中的排序规则，并把这些排序规则按照默认排序规则处理，即 以编码字节序为字符定序。和 MySQL 不同的是，TiDB 在比较字符前按照排序规则的 PADDING 属性将字符末尾 的空格删除，因此会造成以下的行为区别： CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci utf8mb4_unicode_ci 中任一种时，字符串 之间的比较是大小写不敏感 (case-insensitive) 和口音不敏感 (accent-insensitive) 的。同时，TiDB 还修正了排序规则 的 PADDING 行为： CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci PRIMARY KEY); Query Duplicate entry 'a ' for key 'PRIMARY' # TiDB 修正了 `PADDING` 行为，与 MySQL �→ 兼容。 注意： TiDB 中 padding 的实现方式与 MySQL 的不同。在 MySQL 中，padding 是通过补齐空格实现的。而 在 TiDB 中 padding 是通过裁剪掉末尾的空格来实现的。两种做法在绝大多数情况下是一致的， 唯一的例外是字符串尾部包含小于空格

is case-insensitive and accent- insensitive. At the same time, TiDB also corrects the collation’s PADDING behavior: 4251 CREATE TABLE t(a varchar(20) charset utf8mb4 collate utf8mb4_general_ci �→ PRIMARY PRIMARY' -- TiDB �→ modifies the `PADDING` behavior to be compatible with MySQL. Note: The implementation of padding in TiDB is different from that in MySQL. In MySQL, padding is implemented by filling in in spaces. In TiDB, padding is implemented by cutting out the spaces at the end. The two approaches are the same in most cases. The only exception is when the end of the string contains characters that are