SQlite3 Encryption Not Possible Any More Since 3.32.x

About latest SQlite3 3.32.xxx there is a big problem with codecs.

Critical changes to the public SQLite code were introduced on Feb 7, 2020: “Simplify the code by removing the unsupported and undocumented SQLITE_HAS_CODEC compile-time option”. With the release of SQLite version 3.32.0 on May 22, 2020 these changes finally took officially effect, although they weren't officially announced.

As a sad and unexpected consequence, we are NOT ANY MORE able to compile the new SQlite3 amalgamation with our encryption patch.

Reverting the patch is not an option, since it is much more than a few lines, and it messes with SQLite3 VM opcodes, so it will induce a lot of potential errors.

Perhaps a dedicated VFS may be the solution - this is the path chosen by https://github.com/utelle/SQLite3MultipleCiphers for instance.
But a VFS is a lot of work, error prone, and performance may also decrease.
If we go this VFS path, we may add a compression feature, too...

Any feedback is welcome!
If anyone has an idea...

Edit/Update: We have implemented a solution based on VFS.
Please see https://synopse.info/forum/viewtopic.php?pid=32327#p32327

Synopse Open Source

SQlite3 Encryption Not Possible Any More Since 3.32.x