class Transaction

Same name in this branch
  1. 8.9.x core/modules/system/tests/modules/driver_test/src/Driver/Database/DrivertestMysql/Transaction.php \Drupal\driver_test\Driver\Database\DrivertestMysql\Transaction
  2. 8.9.x core/modules/system/tests/modules/driver_test/src/Driver/Database/DrivertestPgsql/Transaction.php \Drupal\driver_test\Driver\Database\DrivertestPgsql\Transaction
  3. 8.9.x core/lib/Drupal/Core/Database/Driver/sqlite/Transaction.php \Drupal\Core\Database\Driver\sqlite\Transaction
  4. 8.9.x core/lib/Drupal/Core/Database/Driver/mysql/Transaction.php \Drupal\Core\Database\Driver\mysql\Transaction
  5. 8.9.x core/lib/Drupal/Core/Database/Driver/pgsql/Transaction.php \Drupal\Core\Database\Driver\pgsql\Transaction
Same name in other branches
  1. 9 core/tests/fixtures/database_drivers/module/corefake/src/Driver/Database/corefakeWithAllCustomClasses/Transaction.php \Drupal\corefake\Driver\Database\corefakeWithAllCustomClasses\Transaction
  2. 9 core/lib/Drupal/Core/Database/Transaction.php \Drupal\Core\Database\Transaction
  3. 10 core/tests/fixtures/database_drivers/module/core_fake/src/Driver/Database/CoreFakeWithAllCustomClasses/Transaction.php \Drupal\core_fake\Driver\Database\CoreFakeWithAllCustomClasses\Transaction
  4. 10 core/lib/Drupal/Core/Database/Transaction.php \Drupal\Core\Database\Transaction
  5. 11.x core/tests/fixtures/database_drivers/module/core_fake/src/Driver/Database/CoreFakeWithAllCustomClasses/Transaction.php \Drupal\core_fake\Driver\Database\CoreFakeWithAllCustomClasses\Transaction
  6. 11.x core/lib/Drupal/Core/Database/Transaction.php \Drupal\Core\Database\Transaction

A wrapper class for creating and managing database transactions.

Not all databases or database configurations support transactions. For example, MySQL MyISAM tables do not. It is also easy to begin a transaction and then forget to commit it, which can lead to connection errors when another transaction is started.

This class acts as a wrapper for transactions. To begin a transaction, simply instantiate it. When the object goes out of scope and is destroyed it will automatically commit. It also will check to see if the specified connection supports transactions. If not, it will simply skip any transaction commands, allowing user-space code to proceed normally. The only difference is that rollbacks won't actually do anything.

In the vast majority of cases, you should not instantiate this class directly. Instead, call ->startTransaction(), from the appropriate connection object.

Hierarchy

Expanded class hierarchy of Transaction

4 files declare their use of Transaction
DatabaseLegacyTest.php in core/tests/Drupal/KernelTests/Core/Database/DatabaseLegacyTest.php
Transaction.php in core/lib/Drupal/Core/Database/Driver/sqlite/Transaction.php
Transaction.php in core/lib/Drupal/Core/Database/Driver/mysql/Transaction.php
Transaction.php in core/lib/Drupal/Core/Database/Driver/pgsql/Transaction.php
1 string reference to 'Transaction'
Connection::startTransaction in core/lib/Drupal/Core/Database/Connection.php
Returns a new DatabaseTransaction object on this connection.

File

core/lib/Drupal/Core/Database/Transaction.php, line 24

Namespace

Drupal\Core\Database
View source 
class Transaction {
    
    /**
     * The connection object for this transaction.
     *
     * @var \Drupal\Core\Database\Connection
     */
    protected $connection;
    
    /**
     * A boolean value to indicate whether this transaction has been rolled back.
     *
     * @var bool
     */
    protected $rolledBack = FALSE;
    
    /**
     * The name of the transaction.
     *
     * This is used to label the transaction savepoint. It will be overridden to
     * 'drupal_transaction' if there is no transaction depth.
     *
     * @var string
     */
    protected $name;
    public function __construct(Connection $connection, $name = NULL) {
        $this->connection = $connection;
        // If there is no transaction depth, then no transaction has started. Name
        // the transaction 'drupal_transaction'.
        if (!($depth = $connection->transactionDepth())) {
            $this->name = 'drupal_transaction';
        }
        elseif (!$name) {
            $this->name = 'savepoint_' . $depth;
        }
        else {
            $this->name = $name;
        }
        $this->connection
            ->pushTransaction($this->name);
    }
    public function __destruct() {
        // If we rolled back then the transaction would have already been popped.
        if (!$this->rolledBack) {
            $this->connection
                ->popTransaction($this->name);
        }
    }
    
    /**
     * Retrieves the name of the transaction or savepoint.
     */
    public function name() {
        return $this->name;
    }
    
    /**
     * Rolls back the current transaction.
     *
     * This is just a wrapper method to rollback whatever transaction stack we are
     * currently in, which is managed by the connection object itself. Note that
     * logging (preferable with watchdog_exception()) needs to happen after a
     * transaction has been rolled back or the log messages will be rolled back
     * too.
     *
     * @see \Drupal\Core\Database\Connection::rollBack()
     * @see watchdog_exception()
     */
    public function rollBack() {
        $this->rolledBack = TRUE;
        $this->connection
            ->rollBack($this->name);
    }

}

Members

Title Modifiers Object type Summary
Transaction::$connection protected property The connection object for this transaction.
Transaction::$name protected property The name of the transaction.
Transaction::$rolledBack protected property A boolean value to indicate whether this transaction has been rolled back.
Transaction::name public function Retrieves the name of the transaction or savepoint.
Transaction::rollBack public function Rolls back the current transaction.
Transaction::__construct public function
Transaction::__destruct public function

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.