-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
Tidb uhhex() results are conflicting with mysql( 5.7 and 8.0) when collation_database =gbk_chinese_ci #30362
Comments
Tried on MySQL 8.0.27, the behavior is same as TiDB. But on 8.0.12, the result is 1. :(
|
But we still have some problems with unhex() func related gbk.
mysql
TiDB
|
I think the problem is about insert to a gbk filed. The minimal step to reproduce it:
Use a hack way to fix it, it works. Seems we think all string is decoded as
|
Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label. |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: