fix(transaction): delete autocommit when transaction begin (#9877)

[tsasaki609]

Pull Request check-list

Please make sure to review and check all of these items:

• Does npm run test or npm run test-DIALECT pass with this change (including linting)?
• Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
• Have you added new tests to prevent regressions?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Did you follow the commit message conventions explained in CONTRIBUTING.md?

Description of change

fix #9877
Statements within a transaction should either be all successful, or all fail. Autocommit arguments that initiate transactions are misleading and should not be provided. If we want to enable autocommit, we should explicitly call auto-commit. How do you think?

[sushantdhiman]

MySQL transaction with AUTO COMMIT = 1 does defeat purpose of having transaction i.e. each statement is committed as soon as it is finished without any chance of rollback. This is also default behaviour of MySQL.

Two things can be done here

1. Set autocommit = false by default, so transactions is predictable
2. Related to fixing MySQL connections have autocommit disabled after transaction with autocommit: false. #9877 , we need to reset AUTO COMMIT status when transaction exits. How we will do that is not sure, may be a session variable to store current auto commit value and reset it after transaction

[tsasaki609]

Since we are executing START TRANSACTION internally, is not it possible to do SET autocommit = 0 to affect the behavior until the end of the transaction?

If we explicitly use a transaction, it seems that it was behavior that autocommit had no effect until you explicitly commit or roll back.

Sorry if my understanding was wrong.

[sushantdhiman]

Hmm you are right, https://dev.mysql.com/doc/refman/8.0/en/commit.html

By default, MySQL runs with autocommit mode enabled. This means that as soon as you execute a statement that updates (modifies) a table, MySQL stores the update on disk to make it permanent. The change cannot be rolled back.

To disable autocommit mode implicitly for a single series of statements, use the START TRANSACTION statement:

START TRANSACTION;
SELECT @A:=SUM(salary) FROM table1 WHERE type=1;
UPDATE table2 SET summary=@A WHERE type=1;
COMMIT;

With START TRANSACTION, autocommit remains disabled until you end the transaction with COMMIT or ROLLBACK. The autocommit mode then reverts to its previous state.

So If I understood correctly AUTO COMMIT will not affect statement under transactions it only works for statement not under transaction as an implicit transaction

SET AUTOCOMMIT = 0;
#DO STUFF
COMMIT;

None of other database engine use auto commit so in addition to removing this statement from here we need to remove this option and its query generation methods

[tsasaki609]

@sushantdhiman
I am glad you understood.

In addition to MySQL, PostgreSQL, SQLite, and MS SQL Server seem to have autocommit statement.
https://www.postgresql.jp/document/9.4/html/ecpg-sql-set-autocommit.html
https://www.sqlite.org/c3ref/get_autocommit.html
https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms187878(v=sql.105)

However, the essential meaning of the autocommut statement is that any product is similar,
we don't need to think about separately.

I also deleted options and query generation methods.

Thank you for your review.

[sushantdhiman]

In addition to MySQL, PostgreSQL, SQLite, and MS SQL Server seem to have autocommit statement.
https://www.postgresql.jp/document/9.4/html/ecpg-sql-set-autocommit.html
https://www.sqlite.org/c3ref/get_autocommit.html
https://docs.microsoft.com/en-us/previous-versions/sql/sql-server-2008-r2/ms187878(v=sql.105)

Yeah I meant more at Sequelize level, where we only support/implemented this for MySQL.

[sushantdhiman]

Thanks @tsasaki609