SET autocommit=(0|1) causes [ERROR] Unable to parse query.

[GregorFritzE2]

reproducible bug for ProxySQL.

If you are submitting a reproducible bug report, please provide:

• A clear description of the issue
  As of version 2.5.4 ProxySQL emits an error message when using SQL command SET autocommit=(0|1) disable or enable commit behaviour of MySQL.
  We are aware that SET autocommit itself does not start or end a transaction. We were able to verify that SET autocommitis received by MySQL AND that the queries that happen between START TRANSACTION and COMMIT are routed to the correct hostgroup despite the log output.
  Code that relies heavily on changing the commit behaviour of MySQL on a session basis will clutter the logs with output like this.
• ProxySQL version: 2.5.4 and 2.5.5
• OS version: CentOS from proxysql/proxysql:2.5.4-centos and proxysql/proxysql:2.5.5-centos
• The steps to reproduce the issue

• Send SET autocommit=0 to MySQL via ProxySQL
• See error in log.

• The full ProxySQL error log (default location: /var/lib/proxysql/proxysql.log)
  proxysql.log

[renecannao]

Hi @GregorFritzE2 , and thank you for the report.

Although, the issue is not related to autocommit at all .
It has to do with trailing semicolon at the end of the SET statement.
Therefore this issue is a duplicate of #4369 and #4380 , both solved in PR #4385 .

Unless you have any objection, I will proceed closing this ticket.

[GregorFritzE2]

Hi @renecannao thanks for the fast reply!

I have no objections and look forward to the next release.

[renecannao]

Thank you!