Last modified: 2013-12-30 18:59:05 UTC
To be able to rollback transactions, sqlite write a journal file on disk which is kind of slow. When one doesn't care about dataloss (ex a dev wiki), it would be nice to have the journal held in memory and thus saving disk I/O. Doc: http://www.sqlite.org/pragma.html#pragma_journal_mode Whenever a connection to a sqlite file is made, one can issue the command: pragma journal_mode=memory; Should probably be yet another global variable such as $wgSqliteJournalMode
Mmm, so you're proposing a change analogous to downgrading MySQL from InnoDB to MyISAM?:P
For testing purpose, we don't care about lost of data during transaction, at worth test will fail :-D That is merely to speed up tests when being run against a sqlite backend.