]> git.ipfire.org Git - thirdparty/sqlite.git/commit
More work on the sahpool digest fix. New/fixed versions can read legacy (no digest...
authorstephan <stephan@noemail.net>
Wed, 26 Feb 2025 03:03:08 +0000 (03:03 +0000)
committerstephan <stephan@noemail.net>
Wed, 26 Feb 2025 03:03:08 +0000 (03:03 +0000)
commitd2f7dfa6190f529f7e543380b6663074e9078207
treeb4b05288802bc0f0c8910b8aff4d040c7ec77ebf
parentc97abeac0b33a06a274bc4363b5162c5eed6a5d0
More work on the sahpool digest fix. New/fixed versions can read legacy (no digest) files but the reverse is only possible in limited circumstances (when files originated from a legacy version). The burning question is whether the real fix would be to remove this digest check altogether, as it only applies in a very limited context, and the fact that it was broken for some 18 months unnoticed suggests that its value might not be worth the CPU cycles.

FossilOrigin-Name: 0df62b776c68bebb0e187b353b6f29b0a41a29f0a1c8d6728fa6b9f7ce0d13f7
ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js
ext/wasm/tests/opfs/sahpool/digest-worker.js
ext/wasm/tests/opfs/sahpool/digest.html
manifest
manifest.uuid