SunshinePHP Developer Conference 2015


(PHP 5 >= 5.3.0)

SQLite3::execEjecutar una consulta que no devuelve resultados en una base de datos dada


public bool SQLite3::exec ( string $query )

Ejecuta una consulta que no devuelve resultados en una base de datos dada.



La consulta SQL a ejecutar (típicamente una consulta INSERT, UPDATE, o DELETE).

Valores devueltos

Devuelve TRUE si la consulta tuvo éxito, FALSE en caso de error.


Ejemplo #1 Ejemplo de SQLite3::exec()

= new SQLite3('mibdsqlite.db');

$bd->exec('CREATE TABLE bar (bar STRING)');

add a note add a note

User Contributed Notes 4 notes

1 year ago
SQLite needs to create some temp-files (journals...) to execute certain statements, so php needs write-permission in your db-directory.
Rob Haverkort
11 months ago
Actually, sqlite creates a journal-file when changing data and so it needs the write-permissions in the directory.
moodsey211 at gmail dot com
3 years ago
If you get the error message saying "SQLite3::exec. database locked." You just need to define a busyTimeout to work around this.
info at tellmatic dot org
1 year ago
IMPORTANT! just a note:

weird behaviour when doing an exec on a sqlite db!!!

if want to execute a query on a sqlite db with exec, and your dbfile already was e.g. mode 777, and you get some php errors saying

"SQLite3::exec(): unable to open database file in ...."

and you get crazy while debugging, just add write üermissions to the whole directory for the user the webserver/php runs.

this behaviour makes absolutely NO sense, and is a source of frustration.
at least a more meaningful errormessage would be nice.
i couldnt figure out why sqlite needs write permissions for the whole dir instead of only one file. this is stupid and must be a bug!
(to be secure you have to create a directory with write permissions only for php/apache)
To Top