PHP 8.4.0 RC4 available for testing

SQLite3::busyTimeout

(PHP 5 >= 5.3.3, PHP 7, PHP 8)

SQLite3::busyTimeoutDéfinit le gestionnaire d'attente de la connexion

Description

public SQLite3::busyTimeout(int $milliseconds): bool

Définit le gestionnaire d'attente qui patientera tant que la base de données n'est pas verrouillée ou que le délai d'attente ne soit atteint.

Liste de paramètres

milliseconds

Les millisecondes à attendre. Le fait de définir cette valeur à une valeur inférieure ou égale à zéro désactivera un gestionnaire d'attente précédemment défini.

Valeurs de retour

Retourne true en cas de succès, ou false si une erreur survient.

add a note

User Contributed Notes 3 notes

up
10
ppryor63 at gmail dot com
10 years ago
The busyTimeout() method and related API sqlite3_busy_timeout() is a connection level attribute and affects whole connection and should be set once after opening connection. Do not set to zero or you will encounter "Database is busy" error message when calling query, querySingle, prepare, or execute methods. Also ensure that sqlite3 library is compiled with HAVE_USLEEP defined, otherwise busyTimeout() can only time out in seconds. It is very highly recommended to call busyTimeout() with non-zero timeout for reliability in concurrent environment.
up
4
anthony at domps dot fr
3 years ago
It's possible to use PRAGMA to set busyTimeout (milliseconds) :

<?php

$db
= new SQLite3('my.db');
$db->exec("PRAGMA busy_timeout=5000");

?>
up
4
dkarnout at gmail dot com
9 years ago
For SQLite2 (http://php.net/manual/en/function.sqlite-busy-timeout.php), PHP sets the default busy timeout to be 60 seconds when the database is opened.
However, this does not happen for v3 and it has to be done manually.

My personal experience is that the default value of SQLite3, which is 0, is not enough when you have to do consecutive read/write commits and the file has not been accessed for long time.
To Top