I never recomend to use the ? with only one value variant like: $var = expression ? $var : other_value or $var = expression ? null : other_value ,and php suport Exception catchin so,use it :)
here my opinion abut lorenzo's post:
<?php
//variants combined
$mysqli->autocommit(FALSE);
try{
$mysqli->query("INSERT INTO myCity (id) VALUES (100)") or throw new Exception('error!');
// or we can use
if( !$mysqli->query("INSERT INTO myCity (id) VALUES (200)"){
throw new Exception('error!');
}
}catch( Exception $e ){
$mysqli->rollback();
}
$mysqli->commit();
?>
mysqli::commit
mysqli_commit
(PHP 5, PHP 7, PHP 8)
mysqli::commit -- mysqli_commit — Commits the current transaction
Açıklama
Nesne yönelimli kullanım
Yordamsal kullanım
Commits the current transaction for the database connection.
Bağımsız Değişkenler
-
bağlantı -
Sadece yordamsal tarz: mysqli_connect() veya mysqli_init() işlevinden dönen bir mysqli nesnesi.
-
flags -
A bitmask of
MYSQLI_TRANS_COR_*constants. -
name -
If provided then
COMMIT/*name*/is executed.
Dönen Değerler
Başarı durumunda true, başarısızlık durumunda false döner.
Hatalar/İstisnalar
Eğer mysqli hata bildirimi etkinse (MYSQLI_REPORT_ERROR)
ve istenen işlem başarısız olursa bir uyarı üretilir. Ek olarak, kip
MYSQLI_REPORT_STRICT ise bunun yerine
mysqli_sql_exception istisnası oluşur.
Sürüm Bilgisi
| Sürüm: | Açıklama |
|---|---|
| 8.0.0 |
name is now nullable.
|
Notlar
Bilginize:
This function does not work with non transactional table types (like MyISAM or ISAM).
Ayrıca Bakınız
- mysqli_autocommit() - Turns on or off auto-committing database modifications
- mysqli_begin_transaction() - Starts a transaction
- mysqli_rollback() - Rolls back current transaction
- mysqli_savepoint() - Set a named transaction savepoint
add a note
User Contributed Notes 6 notes
snchzantonio at gmail dot com ¶
11 years ago
mvanlamz ¶
15 years ago
Please note that calling mysqli::commit() will NOT automatically set mysqli::autocommit() back to 'true'.
This means that any queries following mysqli::commit() will be rolled back when your script exits.
Lorenzo - webmaster AT 4tour DOT it ¶
15 years ago
This 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!
NoMan2000 ¶
9 years ago
This is to clarify the Flags parameters and what they mean:
MYSQLI_TRANS_COR_AND_CHAIN:
Appends "AND CHAIN" to mysqli_commit or mysqli_rollback.
MYSQLI_TRANS_COR_AND_NO_CHAIN:
Appends "AND NO CHAIN" to mysqli_commit or mysqli_rollback.
MYSQLI_TRANS_COR_RELEASE:
Appends "RELEASE" to mysqli_commit or mysqli_rollback.
MYSQLI_TRANS_COR_NO_RELEASE:
Appends "NO RELEASE" to mysqli_commit or mysqli_rollback.
To clarify those options:
The AND CHAIN clause causes a new transaction to begin as soon as the current one ends, and the new transaction has the same isolation level as the just-terminated transaction.
The RELEASE clause causes the server to disconnect the current client session after terminating the current transaction.
zattechnology at gmail dot com ¶
5 years ago
When you have alot of transactions to make, say you are applying inserting items to the database from a loop, it will be better to use the mysqli_commit for this kind of process as it will only hit the database once.
//Wrong way
Example 1:
$con = mysqli_connect("host", "username", "password", "database") or die("Could not establish connection to database");
$users = ["chris", "james", "peter", "mark", "joe", "alice", "bob"]
for($i=0; $i<count($users); $i++){
$user= $users[$i];
$query = mysqli_query($con, "INSERT INTO users (username) VALUES ('$user') ");
}
//Correct Way
Example 2
$con = mysqli_connect("host", "username", "password", "database") or die("Could not establish connection to database");
$users = ["chris", "james", "peter", "mark", "joe", "alice", "bob"]
//Turn off autocommit
mysqli_autocommit($con, FALSE)
//Make some transactions
for($i=0; $i<count($users); $i++){
$user= $users[$i];
$query = mysqli_query($con, "INSERT INTO users (username) VALUES ('$user') ");
}
//Make a one-time hit to the database
mysqli_commit($con)
As with the Example 1, since we had 7 items in the list, this means that their will be a 7 times hit to our database which can really affect performance. But with the Example 2, since we already turned off autocommit this means that the transactions will be queued ontill will explicitly call mysqli_commit($con)
Bob Johnson ¶
15 years ago
The compactness of Lorenzo's code is admirable.
However, it is a good idea to also check $mysqli->affected_rows to make sure that the INSERT statement did not fail.
<?php
$result_query = @mysqli_query($query, $connect);
if (($result_query == false) &&
(mysqli_affected_rows($connect) == 0))
{
// verify the query executed completely and verify that it
// had impact on the table
$success = false;
// here also, the developer could choose to add a ROLLBACK
// statement
}
?>
