Skip to content
9aacd2c
Compare
Choose a tag to compare
4ffc078
Compare
Choose a tag to compare
f4682f0
Compare
Choose a tag to compare
8a6fdfc
Compare
Choose a tag to compare
bb39806
Compare
Choose a tag to compare
8ec9114
Compare
Choose a tag to compare
28b082d
Compare
Choose a tag to compare

Changes since previous release

99b012d
Compare
Choose a tag to compare
db947a9
Compare
Choose a tag to compare
9c0ccfe
Compare
Choose a tag to compare

Changes since previous release

⚠️ Important Information when operating SQLite in WAL journal mode ⚠️

To allow concurrent use of SQLite databases in WAL journal mode with legacy encryption implementations like System.Data.SQLite or SQLCipher a new WAL journal encryption implementation was introduced in SQLite3 Multiple Ciphers version 1.3.0.

Unfortunately, WAL journals left behind by versions <= 1.2.5 are not compatible with this new implementation. To be able to access WAL journals created by prior versions, the configuration parameter mc_legacy_wal was introduced. If the parameter is set to 1, then the prior WAL journal encryption mode is used. The default of this parameter can be set at compile time by setting the symbol SQLITE3MC_LEGACY_WAL accordingly, but the actual value can also be set at runtime using the pragma or the URI parameter mc_legacy_wal.

In principle, operating generally in WAL legacy mode is possible, but it is strongly recommended to use the WAL legacy mode only to recover WAL journals left behind by prior versions without data loss.