wxSQLite3 4.8.1 (based on SQLite 3.38.5)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.4.3 (based on SQLite 3.38.5)

wxSQLite3 4.8.0 (based on SQLite 3.38.3)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.4.2 (based on SQLite 3.38.3)

wxSQLite3 4.7.9 (based on SQLite 3.38.2)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.9 (based on SQLite 3.38.2)

wxSQLite3 4.7.8 (based on SQLite 3.38.1)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.9 (based on SQLite 3.38.1)

wxSQLite3 4.7.7 (based on SQLite 3.38.0)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.8 (based on SQLite 3.38.0)

wxSQLite3 4.7.6 (based on SQLite 3.37.2)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.7 (based on SQLite 3.37.2)

wxSQLite3 4.7.5 (based on SQLite 3.37.0)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.5 (based on SQLite 3.37.0)
• Add build support for Visual C++ 2022

wxSQLite3 4.7.4 (based on SQLite 3.36.0)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.4 (based on SQLite 3.36.0)

wxSQLite3 4.7.3 (based on SQLite 3.36.0)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.3 (based on SQLite 3.36.0)

wxSQLite3 4.7.2 (based on SQLite 3.35.5)

Changes since previous release

• Upgrade to SQLite3 Multiple Ciphers version 1.3.2 (based on SQLite 3.35.5)

⚠️ 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.