mysqli::autocommit

mysqli_autocommit

(PHP 5)

mysqli::autocommit -- mysqli_autocommitTurns on or off auto-committing database modifications

Description

Object oriented style

bool mysqli::autocommit ( bool $mode )

Procedural style

bool mysqli_autocommit ( mysqli $link , bool $mode )

Turns on or off auto-commit mode on queries for the database connection.

To determine the current state of autocommit use the SQL command SELECT @@autocommit.

Parameters

link

Procedural style only: A link identifier returned by mysqli_connect() or mysqli_init()

mode

Whether to turn on auto-commit or not.

Return Values

Returns TRUE on success or FALSE on failure.

Notes

Note:

This function doesn't work with non transactional table types (like MyISAM or ISAM).

Examples

Example #1 mysqli::autocommit() example

Object oriented style

<?php
$mysqli 
= new mysqli("localhost""my_user""my_password""world");

if (
mysqli_connect_errno()) {
    
printf("Connect failed: %s\n"mysqli_connect_error());
    exit();
}

/* turn autocommit on */
$mysqli->autocommit(TRUE);

if (
$result $mysqli->query("SELECT @@autocommit")) {
    
$row $result->fetch_row();
    
printf("Autocommit is %s\n"$row[0]);
    
$result->free();
}

/* close connection */
$mysqli->close();
?>

Procedural style

<?php
$link 
mysqli_connect("localhost""my_user""my_password""world");

if (!
$link) {
    
printf("Can't connect to localhost. Error: %s\n"mysqli_connect_error());
    exit();
}

/* turn autocommit on */
mysqli_autocommit($linkTRUE);

if (
$result mysqli_query($link"SELECT @@autocommit")) {
    
$row mysqli_fetch_row($result);
    
printf("Autocommit is %s\n"$row[0]);
    
mysqli_free_result($result);
}

/* close connection */
mysqli_close($link);
?>

The above examples will output:

Autocommit is 1

See Also

Коментарии

Автор:
I've found that if PHP exits due to a code bug during a transaction, an InnoDB table can remain locked until Apache is restarted.

The simple test is to start a transaction by setting $mysqli_obj->autocommit(false) and executing an insert statement.  Before getting to a $mysqli_obj->commit statement - have a runtime code bug bomb PHP.  You check the database, no insert happened (you assume a rollback occurred) .. and you go fix the bug, and try again... but this time the script takes about 50 seconds to timeout - the insert statement returning with a “1205 - Lock wait timeout exceeded; try restarting transaction”.  No rollback occurred. And this error will not go away until you restart Apache - for whatever reason, the resources are not released until the process is killed.

I found that an ‘exit’, instead of a PHP code bug, will not cause a problem. So there is an auto-rollback mechanism in place - it just fails miserably when PHP dies unexpectantly. Having to restarting apache is a pretty drastic measure to overcome a code bug.

To avoid this problem, I use “register_shutdown_function()” when I start a transaction, and set a flag to indicate a transaction is in process (because there is no unregister_shutdown_function()). See below. So the __shutdown_check() routine (I beleive it needs to be public) is called when the script bombs - which is able to invoke the rollback().

these are just the relevant bits to give u an idea...

<?php 

public function begin_transaction() {
 
$ret $this->mysqli_obj->autocommit(false);
 
$this->transaction_in_progress true;
 
register_shutdown_function(array($this"__shutdown_check"));
}

public function 
__shutdown_check() {
  if (
$this->transaction_in_progress) {
   
$this->rollback();
  }
}

public function 
commit() {
 
$ret $this->mysqli_obj->commit();
 
$this->transaction_in_progress false;
}

public function 
rollback() {
 
$ret $this->mysqli_obj->rollback();
 
$this->transaction_in_progress false;
}
?>

True for PHP 5.1.6 + MySQL 5.0.24a.
2007-03-11 14:22:35
http://php5.kiev.ua/manual/ru/mysqli.autocommit.html
Автор:
It's worth noting that you can perform transactions without disabling autocommit just using standard sql. "START TRANSACTION;" will start a transaction. "COMMIT;" will commit the results and "ROLLBACK;" will revert to the pre-transaction state.

CREATE TABLE and CREATE DATABASE (and probably others) are always commited immediately and your transaction appears to terminate. Thus any commands before and after will be commited, even if a subsequent rollback is attempted.

If you are in the middle of a transaction and you call mysqli_close() it appears that you get the funcitonality of an implicit rollback.

I can't reproduce the "code bug causes lock" problem outlined below (I always get a successful rollback and the script will run umtine times successfully). Therefore, I would suggest that the problem is fixed in php-5.2.2.
2007-05-12 21:02:32
http://php5.kiev.ua/manual/ru/mysqli.autocommit.html
Just to be clear, autocommit not only turns on/off transactions, but will also 'commit' any waiting queries.
<?php
mysqli_autocommit
($linkFALSE); // turn OFF auto
-some query 1;
-
some query 2;
mysqli_commit($link); // process ALL queries so far
-some query 3;
-
some query 4;
mysqli_autocommit($linkTRUE); // turn ON auto
?>
All 4 will be processed.
2007-11-11 03:03:36
http://php5.kiev.ua/manual/ru/mysqli.autocommit.html

    Поддержать сайт на родительском проекте КГБ