function Connection::__destruct
Ensures that the client connection can be garbage collected.
2 calls to Connection::__destruct()
- Connection::__destruct in core/
modules/ sqlite/ src/ Driver/ Database/ sqlite/ Connection.php - Destructor for the SQLite connection.
- Connection::__destruct in core/
modules/ mysql/ src/ Driver/ Database/ mysql/ Connection.php - Ensures that the client connection can be garbage collected.
2 methods override Connection::__destruct()
- Connection::__destruct in core/
modules/ sqlite/ src/ Driver/ Database/ sqlite/ Connection.php - Destructor for the SQLite connection.
- Connection::__destruct in core/
modules/ mysql/ src/ Driver/ Database/ mysql/ Connection.php - Ensures that the client connection can be garbage collected.
File
-
core/
lib/ Drupal/ Core/ Database/ Connection.php, line 347
Class
- Connection
- Base Database API class.
Namespace
Drupal\Core\DatabaseCode
public function __destruct() {
// Call the ::destroy method to provide a BC layer.
// @todo https://www.drupal.org/project/drupal/issues/3153864 Remove this
// call in Drupal 10 as the logic in the destroy() method is no longer
// required now we implement a proper destructor.
$this->destroy();
// Ensure that the circular reference caused by Connection::__construct()
// using $this in the call to set the statement class can be garbage
// collected.
$this->connection = NULL;
}
Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.