@@global.autocommit=1 @@session.autocommit becomes 0 Why?

Shintaro Sasaki 96 Reputation points
2020-10-22T05:49:43.89+00:00

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

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
824 questions
0 comments
Accepted answer
  1. Shintaro Sasaki 96 Reputation points
    2020-10-22T05:53:24.863+00:00

    It was server parameter init_connect setting the autocommit to 0... I wonder who set that -_-; Removing that fixed the problem

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.