Version sans cache

Mise en cache désactivé. Réglage défaut pour cette page : actif (code DEF204)
Si l'affichage est trop lent, vous pouvez désactiver le mode utilisateur pour visualiser la version en cache.

Rechercher dans le manuel MySQL

15.7.2.2 autocommit, Commit, and Rollback

Table des matières

In InnoDB, all user activity occurs inside a transaction. If autocommit mode is enabled, each SQL statement forms a single transaction on its own. By default, MySQL starts the session for each new connection with autocommit enabled, so MySQL does a commit after each SQL statement if that statement did not return an error. If a statement returns an error, the commit or rollback behavior depends on the error. See Section 15.20.4, “InnoDB Error Handling”.

A session that has autocommit enabled can perform a multiple-statement transaction by starting it with an explicit START TRANSACTION or BEGIN statement and ending it with a COMMIT or ROLLBACK statement. See Section 13.3.1, “START TRANSACTION, COMMIT, and ROLLBACK Syntax”.

If autocommit mode is disabled within a session with SET autocommit = 0, the session always has a transaction open. A COMMIT or ROLLBACK statement ends the current transaction and a new one starts.

If a session that has autocommit disabled ends without explicitly committing the final transaction, MySQL rolls back that transaction.

Some statements implicitly end a transaction, as if you had done a COMMIT before executing the statement. For details, see Section 13.3.3, “Statements That Cause an Implicit Commit”.

A COMMIT means that the changes made in the current transaction are made permanent and become visible to other sessions. A ROLLBACK statement, on the other hand, cancels all modifications made by the current transaction. Both COMMIT and ROLLBACK release all InnoDB locks that were set during the current transaction.

Grouping DML Operations with Transactions

By default, connection to the MySQL server begins with autocommit mode enabled, which automatically commits every SQL statement as you execute it. This mode of operation might be unfamiliar if you have experience with other database systems, where it is standard practice to issue a sequence of DML statements and commit them or roll them back all together.

To use multiple-statement transactions, switch autocommit off with the SQL statement SET autocommit = 0 and end each transaction with COMMIT or ROLLBACK as appropriate. To leave autocommit on, begin each transaction with START TRANSACTION and end it with COMMIT or ROLLBACK. The following example shows two transactions. The first is committed; the second is rolled back. 

shell> mysql test
  1. mysql> CREATE TABLE customer (a INT, b CHAR (20), INDEX (a));
  2. Query OK, 0 rows affected (0.00 sec)
  3. mysql> -- Do a transaction with autocommit turned on.
  4. mysql> START TRANSACTION;
  5. Query OK, 0 rows affected (0.00 sec)
  6. mysql> INSERT INTO customer VALUES (10, 'Heikki');
  7. Query OK, 1 row affected (0.00 sec)
  8. mysql> COMMIT;
  9. Query OK, 0 rows affected (0.00 sec)
  10. mysql> -- Do another transaction with autocommit turned off.
  11. mysql> SET autocommit=0;
  12. Query OK, 0 rows affected (0.00 sec)
  13. mysql> INSERT INTO customer VALUES (15, 'John');
  14. Query OK, 1 row affected (0.00 sec)
  15. mysql> INSERT INTO customer VALUES (20, 'Paul');
  16. Query OK, 1 row affected (0.00 sec)
  17. mysql> DELETE FROM customer WHERE b = 'Heikki';
  18. Query OK, 1 row affected (0.00 sec)
  19. mysql> -- Now we undo those last 2 inserts and the delete.
  20. mysql> ROLLBACK;
  21. Query OK, 0 rows affected (0.00 sec)
  22. mysql> SELECT * FROM customer;
  23. +------+--------+
  24. | a    | b      |
  25. +------+--------+
  26. |   10 | Heikki |
  27. +------+--------+
  28. 1 row in set (0.00 sec)
  29. mysql>

Table des matières Haut

Transactions in Client-Side Languages

In APIs such as PHP, Perl DBI, JDBC, ODBC, or the standard C call interface of MySQL, you can send transaction control statements such as COMMIT to the MySQL server as strings just like any other SQL statements such as SELECT or INSERT. Some APIs also offer separate special transaction commit and rollback functions or methods.


Rechercher dans le manuel MySQL

Traduction non disponible

Le manuel MySQL n'est pas encore traduit en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.

Document créé le 26/06/2006, dernière modification le 26/10/2018
Source du document imprimé : https://www.gaudry.be/mysql-rf-innodb-autocommit-commit-rollback.html

L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.

Références

  1. Consulter le document html Langue du document :en Manuel MySQL : https://dev.mysql.com/

Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.

Table des matières Haut