PHP 5.6.16 is available


(PHP 5 >= 5.3.0)

SQLite3::execExecutes a result-less query against a given database


public bool SQLite3::exec ( string $query )

Executes a result-less query against a given database.



The SQL query to execute (typically an INSERT, UPDATE, or DELETE query).

Valorile întoarse

Returns TRUE if the query succeeded, FALSE on failure.


Example #1 SQLite3::exec() example

= new SQLite3('mysqlitedb.db');

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

add a note add a note

User Contributed Notes 5 notes

2 years ago
SQLite needs to create some temp-files (journals...) to execute certain statements, so php needs write-permission in your db-directory.
1 year ago
If you use WAL (Write-Ahead Log) (link to sqlite doc for this: ), it needs write acces because of the implementation of multi-thread access to one db. You can turn it off, if you do not want to give the dir write access, but you can also create a certain file it needs (see the link for a description, as it is explained very well there) that you need write access to and you may get away using WAL without giving write accesss to the dir.
info at tellmatic dot org
2 years 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)
Rob Haverkort
2 years 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
4 years ago
If you get the error message saying "SQLite3::exec. database locked." You just need to define a busyTimeout to work around this.
To Top