Remember that MyISAM tables do not support rollbacks.
I just drove myself crazy for an afternoon trying to figure out what was wrong with my code - meanwhile it was fine all along
(PHP 5, PHP 7, PHP 8)
mysqli::rollback -- mysqli_rollback — Rolls back current transaction
Object-oriented style
Procedural style
Rollbacks the current transaction for the database.
mysqlProcedural style only: A mysqli object returned by mysqli_connect() or mysqli_init()
flags
A bitmask of MYSQLI_TRANS_COR_* constants.
name
If provided then ROLLBACK/*name*/ is executed.
If mysqli error reporting is enabled (MYSQLI_REPORT_ERROR) and the requested operation fails,
a warning is generated. If, in addition, the mode is set to MYSQLI_REPORT_STRICT,
a mysqli_sql_exception is thrown instead.
| Version | Description |
|---|---|
| 8.0.0 |
name is now nullable.
|
Note:
This function does not work with non transactional table types (like MyISAM or ISAM).
Remember that MyISAM tables do not support rollbacks.
I just drove myself crazy for an afternoon trying to figure out what was wrong with my code - meanwhile it was fine all alongThis is an example to explain the powerful of the rollback and commit functions.
Let's suppose you want to be sure that all queries have to be executed without errors before writing data on the database.
Here's the code:
<?php
$all_query_ok=true; // our control variable
//we make 4 inserts, the last one generates an error
//if at least one query returns an error we change our control variable
$mysqli->query("INSERT INTO myCity (id) VALUES (100)") ? null : $all_query_ok=false;
$mysqli->query("INSERT INTO myCity (id) VALUES (200)") ? null : $all_query_ok=false;
$mysqli->query("INSERT INTO myCity (id) VALUES (300)") ? null : $all_query_ok=false;
$mysqli->query("INSERT INTO myCity (id) VALUES (100)") ? null : $all_query_ok=false; //duplicated PRIMARY KEY VALUE
//now let's test our control variable
$all_query_ok ? $mysqli->commit() : $mysqli->rollback();
$mysqli->close();
?>
hope to be helpful!If you use savepoints - eg savepoint($foo) - be wary of trying to rollback to the save point with rollback(0, $foo) as that executes "ROLLBACK /* $foo */" instead of "ROLLBACK TO `$foo`".
The manual page is clear about this, but is easily overlooked.
Instead use: $mysqli->query("ROLLBACK TO `$foo`");Just a note about auto incremental ids and rollback.
When using transactions and inserting into a table containing a column with auto incremental ids, the id will be incremented even though the transaction is rolled back.
This might occupy a lot of ids if a lot of rollbacks are performed.
Example:
<?php
$mysqli = new mysqli("localhost", "gugbageri", "gugbageri", "gugbageri");
/* check connection */
if (mysqli_connect_errno()) {
printf("Connect failed: %s\n", mysqli_connect_error());
exit();
}
/* disable autocommit */
$mysqli->autocommit(FALSE);
/* We just create a test table with one auto incremental primary column and a content column*/
$mysqli->query("CREATE TABLE TestTable ( `id_column` INT NOT NULL AUTO_INCREMENT , `content` INT NOT NULL , PRIMARY KEY ( `id_column` )) ENGINE = InnoDB;");
/* commit newly created table */
$mysqli->commit();
/* we insert a row */
$mysqli->query("INSERT INTO TestTable (content) VALUES (99)");
/* we commit the inserted row */
$mysqli->commit();
/* we insert another three rows */
$mysqli->query("INSERT INTO TestTable (content) VALUES (99)");
$mysqli->query("INSERT INTO TestTable (content) VALUES (99)");
$mysqli->query("INSERT INTO TestTable (content) VALUES (99)");
/* we the rollback */
$mysqli->rollback();
/* we insert a row */
$mysqli->query("INSERT INTO TestTable (content) VALUES (99)");
/* we commit the inserted row */
$mysqli->commit();
if ($result = $mysqli->query("SELECT id_column FROM TestTable")) {
while($row = $result->fetch_row()) {
printf("Id: %d.\n", $row[0]);
}
/* Free result */
$result->close();
}
/* Drop table TestTable */
$mysqli->query("DROP TABLE TestTable");
$mysqli->close();
?>
This will output:
Id: 1.
Id: 5.Something to consider when using transact is that you should not perform a normal query on the same table (such as a DELETE) immediately after a transaction. If the transaction rolls-back, the DELETE will execute and even show affected rows, but the row can be magically re-inserted even if the rollback() command comes before the DELETE query.