php[world] 2018 - Call for Speakers

SQLite3

add a note add a note

User Contributed Notes 3 notes

up
15
Anonymous
6 years ago
As of PHP 5.4 support for Sqlite2 has been removed. I have a large web app that was built with sqlite2 as the database backend and thus it exploded when I updated PHP. If you're in a similar situation I've written a few wrapper functions that will allow your app to work whilst you convert the code to sqlite3.

Firstly convert your DB to an sqlite3 db.

sqlite OLD.DB .dump | sqlite3 NEW.DB

Then add the following functions to your app:

<?php
function sqlite_open($location,$mode)
{
   
$handle = new SQLite3($location);
    return
$handle;
}
function
sqlite_query($dbhandle,$query)
{
   
$array['dbhandle'] = $dbhandle;
   
$array['query'] = $query;
   
$result = $dbhandle->query($query);
    return
$result;
}
function
sqlite_fetch_array(&$result,$type)
{
   
#Get Columns
   
$i = 0;
    while (
$result->columnName($i))
    {
       
$columns[ ] = $result->columnName($i);
       
$i++;
    }
   
   
$resx = $result->fetchArray(SQLITE3_ASSOC);
    return
$resx;
}
?>

They're not perfect by any stretch but they seem to be working ok as a temporary measure while I convert the site.
Hope that helps someone
up
0
Anonymous
4 months ago
PHP doesn't seem to support password protection for SQLite3. We can specify password on the db(I think) but you will still be able to open the DB without using a password so it is not working.
up
-18
alan at chandlerfamily dot org dot uk
7 years ago
PHP 5.3.3 introduced sqlite3::busyTimeout(int milliseconds) which does not currently seem to be documented.

It believe it acts like sqlite::busyTimeout - that is it tells sqlite3 to call an internal busyHandler if SQLITE_BUSY is returned from any call which waits a short period and then retries.  It continues to do this until milliseconds milliseconds have elapsed and then returns the SQLITE_BUSY status.

I don't know whether the default 60 second value is in place if this function is not called.
To Top