(mysql.info.gz) InnoDB and AUTOCOMMIT

Info Catalog

(mysql.info.gz) InnoDB transaction model

(mysql.info.gz) InnoDB transaction model

(mysql.info.gz) InnoDB transaction isolation

 
 15.11.1 `InnoDB' and `AUTOCOMMIT'
 ---------------------------------
 
 In `InnoDB', all user activity occurs inside a transaction. If the
 autocommit mode is enabled, each SQL statement forms a single
 transaction on its own. MySQL always starts a new connection with
 autocommit enabled.
 
 If the autocommit mode is switched off with `SET AUTOCOMMIT = 0', then
 we can consider that a user always has a transaction open. An SQL
 `COMMIT' or `ROLLBACK' statement ends the current transaction and a new
 one starts. Both statements will release all `InnoDB' locks that were
 set during the current transaction.  A `COMMIT' means that the changes
 made in the current transaction are made permanent and become visible
 to other users.  A `ROLLBACK' statement, on the other hand, cancels all
 modifications made by the current transaction.
 
 If the connection has autocommit enabled, the user can still perform a
 multiple-statement transaction by starting it with an explicit `START
 TRANSACTION' or `BEGIN' statement and ending it with `COMMIT' or
 `ROLLBACK'.
 

Info Catalog

(mysql.info.gz) InnoDB transaction model

(mysql.info.gz) InnoDB transaction model

(mysql.info.gz) InnoDB transaction isolation