WAL is broken with debian libsqlcipher0 2.2.1-2
The version for libsqlcipher0 that is currently packaged in debian (2.2.1-2) (and python-sqlcipher linked against it) break the write-ahead logging functionality in the context we're using it in soledad-client (multithreading; simple tests work though).
The current visible symptoms of this breakage are that any client session after the first one will raise a sqlite error when checking for schema initialization (See #3619 -- "u1db_config: no such table").
The -wal and -shm files exist and grow when soledad is operating, but after closing the handles the database file does not get updated with the temporary information (it's kept always at 1024 bytes, which is the default page size).
The problem seems to be with some of the patches applied in the debian package. I am trying to pinpoint which one exactly to get a workaround. If we need to release the client with some minimal mail functionality for a coordinated, wide use 0.5.0, I can patch the debian package for soledad-client so it does not use write-ahead logging (performance will suffer, but mail will be testable at least).
(from redmine: created on 2014-04-22, closed on 2015-09-15)
- Relations:
- relates #3619
- relates #6688 (closed)