An Azure managed MySQL database service for app development and deployment.
It was server parameter init_connect setting the autocommit to 0... I wonder who set that -_-; Removing that fixed the problem
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Dear Azure support.
We have an Azure database for MySQL instance that is running MySQL engine version 5.7. It has the @@global rajesh .autocommit set to 1. When a fresh connection (with no connection parameter nor initSQL) is established, @@session.autocommit becomes 0. Could you tell me what the possible cause and how to make sure @@session.autocommit of the fresh connection respects the @@global rajesh .autocommit value of 1? without argumenting the connection string or setting InitSQL?
Thank you
An Azure managed MySQL database service for app development and deployment.
Answer accepted by question author
It was server parameter init_connect setting the autocommit to 0... I wonder who set that -_-; Removing that fixed the problem