DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 

(mysql.info.gz) Implicit commit

Info Catalog (mysql.info.gz) Cannot roll back (mysql.info.gz) Transactional Commands (mysql.info.gz) Savepoints
 
 13.4.3 Statements That Cause an Implicit Commit
 -----------------------------------------------
 
 Each of the following statements (and any synonyms for them) implicitly
 end a transaction, as if you had done a `COMMIT' before executing the
 statement:
 
 `ALTER TABLE'      `BEGIN'            `CREATE INDEX'
 `DROP DATABASE'    `DROP INDEX'       `DROP TABLE'
 `LOAD MASTER       `LOCK TABLES'      `RENAME TABLE'
 DATA'                                 
 `SET               `START             `TRUNCATE TABLE'
 AUTOCOMMIT=1'      TRANSACTION'       
 
 `UNLOCK TABLES' also ends a transaction if any tables currently are
 locked.  Prior to MySQL 4.0.13, `CREATE TABLE' ends a transaction if
 the binary update log is enabled.
 
 Transactions cannot be nested. This is a consequence of the implicit
 `COMMIT' performed for any current transaction when you issue a `START
 TRANSACTION' statement or one of its synonyms.
 
Info Catalog (mysql.info.gz) Cannot roll back (mysql.info.gz) Transactional Commands (mysql.info.gz) Savepoints
automatically generated byinfo2html