ADOdb

Database Abstraction Layer for PHP

User Tools

Site Tools


v5:userguide:transactions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
v5:userguide:transactions [2016/02/27 17:08] – [Smart Transactions] mnewnhamv5:userguide:transactions [2020/08/26 10:09] (current) – [Usage] Add braces as suggested by @peterdd in #629 dregad
Line 1: Line 1:
 ======Transaction Handling In ADOdb ====== ======Transaction Handling In ADOdb ======
 ===== Overview ===== ===== Overview =====
-There are 2 ways of overriding the default transaction handling in ADOdb, **Granular** and **Smart**. Each way holds benefits but they cannot be mixed. Each method comprises a series of methods.+There are 2 ways of overriding the default database transaction handling methods in ADOdb, **Granular** and **Smart**. Each way holds benefits but they cannot be mixed. Each method comprises a series of methods.
  
   * Granular transactions allow full control of individual commits   * Granular transactions allow full control of individual commits
Line 11: Line 11:
 <WRAP right info 300px> <WRAP right info 300px>
 MySQL myIsam tables are always granular, and ignore any transaction control methods coded. You cannot rollback or fail an update into that table type. Use InnoDB table types instead. MySQL myIsam tables are always granular, and ignore any transaction control methods coded. You cannot rollback or fail an update into that table type. Use InnoDB table types instead.
 +
 +This also applies to any sequences that might have been updated in the transaction, and are not subject to transactional rollback.
 </WRAP> </WRAP>
 If ADOdb transaction handling is not used, then the transaction handling method is controlled by whatever is set by the database. Possible methods are: If ADOdb transaction handling is not used, then the transaction handling method is controlled by whatever is set by the database. Possible methods are:
Line 23: Line 25:
 <WRAP right box> <WRAP right box>
 == Available Methods == == Available Methods ==
-[[v5:reference:connection:begintrans]]\\ +[[v5:reference:connection:begintrans|beginTrans()]]\\ 
-[[v5:reference:connection:rollbacktrans]]\\ +[[v5:reference:connection:rollbacktrans|rollbackTrans()]]\\ 
-[[v5:reference:connection:completetrans]]+[[v5:reference:connection:completetrans|completeTrans()]]\\ 
 +== See Also == 
 +[[v5:reference:connection:transOff|Temporarily Disabling Transactions]]\\ 
 +[[v5:reference:connection:transCnt|Checking Transaction Status]]\\
 </WRAP> </WRAP>
 When using granular transactions, it is the duty of the programmer to check whether a transaction execution has succeeded or failed. This allows the code to branch as desired in the case of a transaction failure. When using granular transactions, it is the duty of the programmer to check whether a transaction execution has succeeded or failed. This allows the code to branch as desired in the case of a transaction failure.
Line 41: Line 46:
 $ok = $conn->execute($sql); $ok = $conn->execute($sql);
  
-if ($ok)+if ($ok) {
    /*    /*
    * The previous execution succeeded, do some more    * The previous execution succeeded, do some more
    */     */ 
    $ok = $conn->execute($sql2);    $ok = $conn->execute($sql2);
-else+else {
    /*    /*
    * Branch, do some other work, then return    * Branch, do some other work, then return
    */    */
-if (!$ok) +
 + 
 +if (!$ok) {
     /*     /*
     * Test the last insertion, if not successful roll      * Test the last insertion, if not successful roll 
Line 56: Line 63:
     */     */
     $conn->rollbackTrans();     $conn->rollbackTrans();
-else+else {
     /*     /*
     * Go ahead and commit     * Go ahead and commit
     */      */ 
     $conn->commitTrans();     $conn->commitTrans();
 +}
 </code> </code>
 ----------------------------- -----------------------------
Line 66: Line 74:
 <WRAP right box> <WRAP right box>
 == Available Methods == == Available Methods ==
-[[v5:reference:connection:starttrans]]\\ +[[v5:reference:connection:starttrans|startTrans()]]\\ 
-[[v5:reference:connection:failtrans]]\\ +[[v5:reference:connection:failtrans|failTrans()]]\\ 
-[[v5:reference:connection:hasfailedtrans]]\\ +[[v5:reference:connection:hasfailedtrans|hasFailedTrans()]]\\ 
-[[v5:reference:connection:completetrans]]+[[v5:reference:connection:completetrans|completeTrans()]] 
 +== See Also == 
 +[[v5:reference:connection:transOff|Temporarily Disabling Transactions]]\\ 
 +[[v5:reference:connection:transCnt|Checking Transaction Status]]\\
 </WRAP> </WRAP>
-Smart Transactions are much easier to use in large procedures because you do not have to track the error status. You start a smart transaction by calling StartTrans():+Smart Transactions are much easier to use in large procedures because you do not have to track the error status. You start a smart transaction by calling startTrans():
  
 <code php> <code php>
Line 82: Line 93:
 * Execute some SQL * Execute some SQL
 */ */
-$conn->Execute($sql);+$conn->execute($sql);
  
 /* /*
 * Execute some more SQL * Execute some more SQL
 */ */
-$conn->Execute($Sql2);+$conn->execute($sql2);
  
 /* /*
Line 96: Line 107:
 </code> </code>
  
-[[v5:reference:connection:completetrans]] detects when an SQL error occurs, and will Rollback or Commit the transactions as appropriate. +[[v5:reference:connection:completetrans|completeTrans()]] detects when an SQL error occurs, and will Rollback or Commit the transactions as appropriate. 
  
-You can force a rollback even if no error occured, using [[v5:reference:connection:failtrans]]. Note that the rollback is done in completeTrans(), so any updates/inserts done after ''failTrans()'' is called will also be rolled back.+You can force a rollback even if no transactional error has occured, using [[v5:reference:connection:failtrans|failTrans()]]. Note that the rollback is done in completeTrans(), so any updates/inserts done after ''failTrans()'' is called will also be rolled back.
  
 <code php> <code php>
Line 105: Line 116:
 $conn->execute($sql); $conn->execute($sql);
  
-if (!CheckRecords()) +if (!checkRecords()) 
     $conn->failTrans();     $conn->failTrans();
  
-$conn->Execute($Sql2);+/* 
 +* Even though failTrans was issued before this statement, 
 +* it will also be rolled back 
 +*/ 
 +$conn->execute($sql2);
  
-$conn->CompleteTrans();+$conn->completeTrans();
 </code> </code>
  
-You can also check if a transaction has failed, using [[v5:reference:connection:hasfailedtrans]], which returns true: +You can also check if a transaction has failed, using [[v5:reference:connection:hasfailedtrans|hasFailedTrans()]], which returns true: 
-  * if [[v5:reference:connection:failtrans]] was called,  +  * if [[v5:reference:connection:failtrans|failTrans()]] was called,  
-  * There was an error in the SQL execution. +  * There was an error in the SQL execution. This execution comprises all scenarios where the SQL statement was successfully issued, but failed to complete. This does not include scenarios where the construction of the statement failed, and an error occurred that was trapped by PHP error handling.
  
-Make sure you call ''hasFailedTrans()'' before you call ''completeTrans()'', as it is only works between StartTrans/CompleteTrans.+Make sure you call ''hasFailedTrans()'' before you call ''completeTrans()'', as it is only works between startTrans/completeTrans.
  
  
Line 136: Line 151:
 */ */
 $conn->startTrans(); $conn->startTrans();
-if (!CheckRecords()) +if (!checkRecords()) 
     /*     /*
     * This is applied to the outer block     * This is applied to the outer block
Line 155: Line 170:
 ==== Savepoints ==== ==== Savepoints ====
 Savepoints are currently not supported. Savepoints are currently not supported.
- 
v5/userguide/transactions.1456589327.txt.gz · Last modified: 2017/04/21 11:39 (external edit)