]> git.ipfire.org Git - thirdparty/sqlite.git/commit
JS: add a random element when assigning db IDs to Worker1 db instances. This addresse...
authorstephan <stephan@noemail.net>
Wed, 30 Jul 2025 14:50:44 +0000 (14:50 +0000)
committerstephan <stephan@noemail.net>
Wed, 30 Jul 2025 14:50:44 +0000 (14:50 +0000)
commitf402509b62a3839a27ba08de1202143e6ba4550f
tree1e9963c73a879896ff50bfafda2be613cd1a2734
parentbac6793a8a0218e5fc16d8e0a34a6786200eab8a
JS: add a random element when assigning db IDs to Worker1 db instances. This addresses [https://github.com/sqlite/sqlite-wasm/issues/113 | the npm project's ticket #113], which demonstrates that two independent workers can end up generating non-globally-unique IDs. That's not a bug, per se, but it makes the IDs useless for client-side mapping of db connection IDs to client-side state, so we add some randomness to them.

FossilOrigin-Name: 6d2a43075fda9c4eae28f9ca4aaf459c41d305c861947a47fb2cbd513249c4b9
ext/wasm/api/sqlite3-api-worker1.c-pp.js
manifest
manifest.uuid