@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?
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])
Mariaex.query("UPDATE mytable SET data = BINARY ?, [data])
Mariaex.query("INSERT INTO mytable (id, data) VALUES (?,BINARY ?), [id,data])
Maybe this helps for finding the issue or moving forward for now?
Activity
wojtekmach commentedon May 9, 2019
@chulkilee hello, could you provide a bit more context what the problem is? Perhaps you can reproduce this problem with just Mariaex function calls?
chulkilee commentedon May 9, 2019
@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?
IanLuites commentedon May 24, 2019
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
latin1.StanAnsems commentedon Jun 17, 2019
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])
Mariaex.query("UPDATE mytable SET data = BINARY ?, [data])
Mariaex.query("INSERT INTO mytable (id, data) VALUES (?,BINARY ?), [id,data])
Maybe this helps for finding the issue or moving forward for now?