SQLite 3.32.3 build issues about sqleet

[utelle]

It appears the current approach to interfacing with sqlite3 is not going to work going forward past 3.32.0.

Yes, that is correct. On Feb 7, 2020 serious changes were applied to the SQLite sources (see SQLite timeline: “Simplify the code by removing the unsupported and undocumented SQLITE_HAS_CODEC compile-time option”). SQLite 3.32.0 and later are affected by this change. The SQLITE_HAS_CODEC API, on which the current implementation of SQLeet is based, is gone forever, unfortunately.

However, I started a new project, SQLite3MultipleCiphers, which adds encryption support to SQLite 3.32.0 and later using a new implementation based on SQLite's Virtual File System API. Supported ciphers are SQLCipher (all versions from 1 up to 4), SQLeet, System.Data.SQLite, and wxSQLite3.

[AdamSLevy]

It appears the current approach to interfacing with sqlite3 is not going to work going forward past 3.32.0.

https://sqlite.org/forum/forumpost/08481b3fac

[resilar]

See #39 for discussion about VFS-based rewrite of sqleet.