In a CentOS 5 default installation, SQLite requires the pdo, sqlite and
pdo_sqlite extensions, which are not installed. The previous note was very
helpful, but needed some additions:
- get your source version from the historical releases page
- repeat the compile process below for pdo, sqlite and pdo-sqlite extensions,
(gcc is required and may have to be installed)
tar xvf php-your.version.here.tar.gz
- create file /etc/php.d/sqlite.ini:
; Enable sqlite extension module
- [restart apache] service httpd restart
- search phpinfo(); for 'sqlite' to verify correct installation
Since PHP 5.0 this extension was bundled with PHP. Beginning with PHP 5.4, this extension is available only via PECL.
Windows users must enable php_sqlite.dll inside of php.ini in order to use these functions. A DLL for this PECL extension is currently unavailable. See also the building on Windows section.
Windows builds must also enable PDO because as of PHP 5.1.0 it depends on it. So, php.iniwill end up with something like this:
On Linux or Unix operating systems, if you build PDO as a shared extension, you must build SQLite as a shared extension using the –with-sqlite=sharedconfigure option.
The PHP 5.0.x series of Windows builds enabled this extension by default, where no DLL file is necessary.
SQLite 3 is supported through PDO SQLite.
Note: Windows installation for unprivileged accounts
On Windows operating systems, unprivileged accounts don’t have the TMP environment variable set by default. This will make sqlite create temporary files in the windows directory, which is not desirable. So, you should set the TMP environment variable for the web server or the user account the web server is running under. If Apache is your web server, you can accomplish this via a SetEnv directive in your httpd.conffile. For example:SetEnv TMP c:/temp
If you are unable to establish this setting at the server level, you can implement the setting in your script:
The setting must refer to a directory that the web server has permission to create files in and subsequently write to and delete the files it created. Otherwise, you may receive the following error message: malformed database schema – unable to open a temporary database file for storing temporary tables