> Hot to activate SQLite WAL when using DAL? >
you need to have a sqlite3 (or pysqlite2) linked to a sqlite version >= 3.7.0. There are two version number: the module itself and the linked static library (.so on unix and .dll on Windows) >>> import sqlite3 #or from pysqlite2 import dbapi2 as sqlite3 >>> sqlite3.version '2.4.1' >>> sqlite3.sqlite_version '3.6.22' Fastest way to update pysqlite2 now on unix (for windows there are standard .exe installers) is (assuming pip, python-dev and make are available) sudo pip install http://pysqlite.googlecode.com/files/pysqlite-2.6.3.tar.gz--global-option build_static sqlite3.sqlite_version is the value that needs to be >= 3.7.0 . If this is True, just issue (one-time-only) this command to the db PRAGMA journal_mode=WAL; >From then on, that db will work with WAL activated. For a complete review of pros and cons, see http://www.sqlite.org/draft/wal.html Thanks. I'll try using SQLite and WAL - that having been said I'd still be > vote for getting the scheduler working with NoSQL (couchDB) at some stage. > First things first: having CouchDB exiting from the "experimental" phase on the DAL. --
