-
Notifications
You must be signed in to change notification settings - Fork 976
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
MySQL Syntax errors with multi_query #2631
Comments
Verified. |
Same here with ProxySQL 2.0.10, 2.0.9, 2.0.8, 2.0.7 and MariaDB 10.4.12 as backend : multi_query() returns a SQL syntax error (Error 1064). Tested with Moodle 3.8 DDL statements and the script above. |
Even I'm facing this issue, we are sending bulk. " UPDATE x set t1=2; UPDATE x set t2=2; UPDATE x set t3=2;" getting string(156) "You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'UPDATE x' at line 1" Can we have a fix sooner for this? It has been breaking our application for bulk UPDATE. |
This is now fixed in upcoming 2.0.11 . |
Well done ! Thanks ! |
Thanks, tested new build and works. Cheers. |
Hi,
We are using ProxySQL v2.0.10 on Debian 10. It is configured with very simple query rules to split reads/writes to master-slaves. There is 1 master and 2 slaves, all running MariaDB 10.4.12, also on Debian 10.
We are talking to ProxySQL from a Debian 8 server using PHP. The PHP version is:
PHP 7.1.33-14+0~20200320.35+debian8~1.gbpb15fae
We are seeing different behaviour when routing queries through ProxySQL, compared to directly talking with MariaDB itself. We have a script to reproduce this:
Interestingly, when we change:
single('SELECT @@report_host');
-->single('SELECT 1');
it does work correctly. It appears to be related to queries with
@
prior to the multi_query function.See:
This is affecting some of our migrations as well where of course we use different queries however this was the most minimal example we were able to make to show/reproduce this issue.
These are our query rules:
I have also attached a list of all the proxysql variables.
proxysql-vars.log
Is this a setting we have wrong or is something else the cause? Thank you!
The text was updated successfully, but these errors were encountered: