That's actually one of the things the first patch fixes (among other seemingly read only fields).

sqlite3.inc.php has a comment about "SQLite3 only fetches by assoc, we will emulate the other result types" (index and both index and column name). So pdo-sqlite did the same emulation (copy-paste from ...

Thank you!

If you know of any other outstanding issues with pdo-sqlite, please let me know, I'm willing to do further maintenance as it benefits myself as well (I use it on my low-traffic personal blog, so it hardly gets any stress tests from my part - took me almost a year to spot the previous ...

The following take care of a few other hickups caused by the fact that the db type is no longer 'sqlite3', but 'pdo-sqlite'. It also contains the quicksearch patch here , that seems to still be missing.
*** include/functions_entries.inc.php.orig 2010-07-25 01:26:43.000000000 +0300
--- include ...

sqlite3.inc.php emulated num and assoc fetch results so I did it as well, without realizing PDO takes care of this as well, hence this wasn't only unneeded, but also caused trouble in some situations (changes to static pages could not be saved, for example). :oops:

*** pdo-sqlite.inc.php.orig ...

Try installing PDO and using pdo_sqlite (sqlite3 driver) instead of php-sqlite3. If installed properly, it should show up in the detected database extensions as "PDO::SQLite". But note that this was introduced in 1.5 as experimental, so you might want to try it first on a separate test install. :)

Hi there!

I'm in the middle of migrating my home server to a new machine and stumbled on this same issue. Given the (small) size of my db and that the machine is used for more than webserving, I wanted to stick to sqlite. So check the attachment. :mrgreen:

I adapted pdo-postgres.inc.php with bits ...