public Log::end($logging_key) Stop logging for the specified logging key. Parameters $logging_key: The logging key to stop. File core/lib/Drupal/Core/Database/Log.php, line 98 Class Log Database query logger. Namespace Drupal\Core\Database Code public function end($logging_key) { unset($this->queryLog[$logging_key]); }

public Log::clear($logging_key) Empty the query log for the specified logging key. This method does not stop logging, it simply clears the log. To stop logging, use the end() method. Parameters $logging_key: The logging key to empty. File core/lib/Drupal/Core/Database/Log.php, line 88 Class Log Database query logger. Namespace Drupal\Core\Database Code public function clear($logging_key) { $this->queryLog[$logging_key] = array(); }

Cache of logged queries. This will only be used if the query logger is enabled. The structure for the logging array is as follows: array( $logging_key = array( array('query' => '', 'args' => array(), 'caller' => '', 'target' => '', 'time' => 0), array('query' => '', 'args' => array(), 'caller' => '', 'target' => '', 'time' => 0), ), ); Type: array File core/lib/Drupal/Core/Database/Log.php, line 32 Class Log Database query logger. Namespace Drupal\Core\Data

The connection key for which this object is logging. Type: string File core/lib/Drupal/Core/Database/Log.php, line 39 Class Log Database query logger. Namespace Drupal\Core\Database Code protected $connectionKey = 'default';

Database query logger. We log queries in a separate object rather than in the connection object because we want to be able to see all queries sent to a given database, not database target. If we logged the queries in each connection object we would not be able to track what queries went to which target. Every connection has one and only one logging object on it for all targets and logging keys. Hierarchy class \Drupal\Core\Database\Log File core/lib/Drupal/Core/Database/Log.php, line 16 N

Functions to coordinate long-running operations across requests. In most environments, multiple Drupal page requests (a.k.a. threads or processes) will execute in parallel. This leads to potential conflicts or race conditions when two requests execute the same code at the same time. For instance, some implementations of hook_cron() implicitly assume they are running only once, rather than having multiple calls in parallel. To prevent problems with such code, the cron system uses a locking proce

public LockBackendInterface::wait($name, $delay = 30) Waits a short amount of time before a second lock acquire attempt. While this method is subject to have a generic implementation in abstract backend implementation, some backends may provide non blocking or less I/O intensive wait mechanism: this is why this method remains on the backend interface. Parameters string $name: Lock name currently being locked. int $delay: Milliseconds to wait for. Defaults to 30. Return value bool TRUE if the

public LockBackendInterface::releaseAll($lockId = NULL) Releases all locks for the given lock token identifier. Parameters string $lockId: (optional) If none given, remove all locks from the current page. Defaults to NULL. File core/lib/Drupal/Core/Lock/LockBackendInterface.php, line 121 Class LockBackendInterface Lock backend interface. Namespace Drupal\Core\Lock Code public function releaseAll($lockId = NULL);

public LockBackendInterface::release($name) Releases the given lock. Parameters string $name: File core/lib/Drupal/Core/Lock/LockBackendInterface.php, line 112 Class LockBackendInterface Lock backend interface. Namespace Drupal\Core\Lock Code public function release($name);

public LockBackendInterface::lockMayBeAvailable($name) Checks if a lock is available for acquiring. Parameters string $name: Lock to acquire. Return value bool File core/lib/Drupal/Core/Lock/LockBackendInterface.php, line 86 Class LockBackendInterface Lock backend interface. Namespace Drupal\Core\Lock Code public function lockMayBeAvailable($name);