The problem with those API breaks, for me, is that it may be non trivial to work around them. Most of the open source SQLite encryption extensions have not, fo

The problem with those API breaks, for me, is that it may be non trivial to work around them. Most of the open source SQLite encryption extensions have not, for the most part, been able to work around the broken APIs, and are still stuck in the last version of SQLite that supported them. And it's not for lack of effort. There's one exception that moved to the public VFS API, while retaining the ability to load previously encrypted databases. But it was a big effort, and there are compromises involved. https://utelle.github.io/SQLite3MultipleCiphers/ https://utelle.github.io/SQLite3MultipleCiphers/