-
Notifications
You must be signed in to change notification settings - Fork 89
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
Invalid utf-8 byte sequences in varchar #252
Comments
@chulkilee hello, could you provide a bit more context what the problem is? Perhaps you can reproduce this problem with just Mariaex function calls? |
@wojtekmach updated the issue description with more tests. I found that it only happens when I talk to ProxySQL. If I run the query directly MySQL, it works. Interesting.. I don't know much details how ProxySQL handles it. Probably it's a ProxySQL bug? |
We actually experienced the exact same issue. UTF issues when Mariaex connects through ProxySQL. Unable to read existing UTF fields and when writing writes garbled |
It looks like we have the same problem, for now we found a workaround that works for us. we added BINARY before the field we select, update or insert: Mariaex.query("SELECT BINARY data FROM mytable WHERE id = ?", [id]) Maybe this helps for finding the issue or moving forward for now? |
I have an invalid utf-8 string in varchar, and mariaex returns it as binary, not string.
CHARSET=utf8 COLLATE=utf8_unicode_ci
varchar(255) CHARACTER SET utf8 COLLATE utf8_unicode_ci
Query:
When talking to ProxySQL:
When talking directly to MySQL:
Examining the value:
The text was updated successfully, but these errors were encountered: