You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The result differs between tidb and mysql when collate is disabled is because of that:
The default collate of tidb is case-sensitive, but the default collate of mysql is case-insensitive.
After we changing the CHARSET=latin1 COLLATE=latin1_bin to CHARSET=utf8mb4 COLLATE=utf8mb4_bin, we can get the same result from tidb and mysql.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
1.txt
collation is on
download and source the 1.txt
execute the sql
2. What did you expect to see? (Required)
23
3. What did you see instead (Required)
24
4. What is your TiDB version? (Required)
Release Version: v5.2.0-alpha-586-g1c90b8e0b
Edition: Community
Git Commit Hash: 1c90b8e
Git Branch: master
UTC Build Time: 2021-08-11 10:18:44
GoVersion: go1.16.4
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false
The text was updated successfully, but these errors were encountered: