Transaction.php

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

Namespace

Drupal\Core\Database

File

core/lib/Drupal/Core/Database/Transaction.php

View source
<?php

namespace Drupal\Core\Database;


/**
 * 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.
 */
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
   *
   * @deprecated in drupal:10.2.0 and is removed from drupal:11.0.0. There is
   *   no replacement.
   *
   * @see https://www.drupal.org/node/3381002
   */
  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, protected readonly string $id = '') {
    // Transactions rely on objects being destroyed in order to be committed.
    // PHP makes no guarantee about the order in which objects are destroyed so
    // ensure all transactions are committed on shutdown.
    Database::commitAllOnShutdown();
    if ($connection->transactionManager()) {
      $this->connection = $connection;
      $this->name = $name;
      return;
    }
    // Start of BC layer.
    $this->connection = $connection;
    // If there is no transaction depth, then no transaction has started. Name
    // the transaction 'drupal_transaction'.
    // @phpstan-ignore-next-line
    if (!($depth = $connection->transactionDepth())) {
      $this->name = 'drupal_transaction';
    }
    elseif (!$name) {
      $this->name = 'savepoint_' . $depth;
    }
    else {
      $this->name = $name;
    }
    // @phpstan-ignore-next-line
    $this->connection
      ->pushTransaction($this->name);
    // End of BC layer.
  }
  public function __destruct() {
    if ($this->connection
      ->transactionManager()) {
      $this->connection
        ->transactionManager()
        ->unpile($this->name, $this->id);
      return;
    }
    // Start of BC layer.
    // If we rolled back then the transaction would have already been popped.
    // @phpstan-ignore-next-line
    if (!$this->rolledBack) {
      // @phpstan-ignore-next-line
      $this->connection
        ->popTransaction($this->name);
    }
    // End of BC layer.
  }
  
  /**
   * 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 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()
   */
  public function rollBack() {
    if ($this->connection
      ->transactionManager()) {
      $this->connection
        ->transactionManager()
        ->rollback($this->name, $this->id);
      return;
    }
    // Start of BC layer.
    // @phpstan-ignore-next-line
    $this->rolledBack = TRUE;
    // @phpstan-ignore-next-line
    $this->connection
      ->rollBack($this->name);
    // End of BC layer.
  }

}

Classes

Title Deprecated Summary
Transaction A wrapper class for creating and managing database transactions.

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