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
Cascade ProxySQL and Charset #1019
Comments
Hi. |
Yes, exactly... |
Ok, so if charset is changed all the way down when a query is executed, that is working ok. |
Yes, behind ProxySQL1 i have two ProxySQL, something like this: With mysql-multiplexing='true', charset is working randomly. |
@stangred : can you please describe your setup and the result you get with further details, so that I will try to reproduce it? Thanks |
@stangred : a lot of improvements were implemented since when this issue was created. |
@renecannao We will try to test this configuration one more time, thank you |
Please wait for 2.0.7 |
I have the same issue with "SET NAMES utf8" command, with an easier infrastructure: |
Im not sure if this is a bug, but i have configuration:
App -> ProxySQL -> ProxySQL -> DB
Right now when application send query "set names to utf-8" only ProxySQL1 will change this, ProxySQL2 is still working on latin1. I know that this query is not sent to a backend, but tracked internally on ProxySQL1. Maybe it will be good to add some variable that will change this and will force ProxySQL to sent query also to a backend ?
The text was updated successfully, but these errors were encountered: