version-3.45.2
Extend the refactoring into extensions. Clean up stray newlines.
Fix harmless compiler warnings seen with MSVC.
Fix various harmless scan-build warnings.
Fix harmless "unused parameter" compiler warning in the new fts3IntegrityMethod implementation.
Handle an OOM case in fts5 code to query tokendata=1 tables.
Tweak sqlite3-worker1.js to be able to load either sqlite3.js or sqlite3-wasmfs.js, noting that the latter still does not load in a Worker because of an Emscripten loader bug.
Back out [99d11e6d0ae6] (enabling of STAT4 in WASM/JNI), per /chat discussion.
Ensure that all fields of static sqlite3_module objects are explicitly initialized, in order to hush-up nuisance compiler warnings.
When doing a text-affinity comparison between two values where one or both have both a text and a numeric type, make sure the numeric type does not confuse the answer. This is a deeper fix to the problem observed by [forum:/forumpost/3776b48e71|forum post 3776b48e71]. The problem bisects to [25f2246be404f38b] on 2014-08-24, prior to version 3.8.7.
Fix the rbu_exclusive_checkpoint=1 option so that it works with a zipvfs database in pass-through mode.
Fix the rtreeJ.test module to align it with [cd017c28d516399e].
Fix a comment in sessions. No functional changes. [forum:/forumpost/8c20dc935b|Forum post 8c20dc935b].
Fix a problem in the userauth extension causing it to occasionally set "PRAGMA count_changes" (and some others) to true.
wasm build: reformulate an awk invocation to account for awks which do not support the -e flag. Problem reported on the forum via a docker-hosted build.
Updates to README files under the ext/ hierarchy. No changes to code.