aboutsummaryrefslogtreecommitdiff
path: root/ext/wasm/api/sqlite3-api-glue.js
diff options
context:
space:
mode:
authorstephan <stephan@noemail.net>2024-04-22 11:48:03 +0000
committerstephan <stephan@noemail.net>2024-04-22 11:48:03 +0000
commit2469350ad9f84d902793d9c8c6b8caeffd4c0a7c (patch)
treefc3f31423e6470ca410a6f8cfc5cb5de16a9bc2f /ext/wasm/api/sqlite3-api-glue.js
parent2c26adb87397842f90122a1029cb84d3f45a4090 (diff)
downloadsqlite-2469350ad9f84d902793d9c8c6b8caeffd4c0a7c.tar.gz
sqlite-2469350ad9f84d902793d9c8c6b8caeffd4c0a7c.zip
For sqlite3.oo1.DB JavaScript classes, bypass execution of any on-open() SQL in SEE-capable builds because it would necessarily run before the client has an opportunity to provide their decryption key, which would leave the db handle in an unusable state and cause the ctor to throw. This currently affects only the OPFS VFSes. We may want to consider extending the ctor options object to optionally accept an SEE key and apply it when opening the db.
FossilOrigin-Name: 5c505ee8a73f4b4a7053d98a12024d98340676f6ae9982311f9f88a9b46c8ae2
Diffstat (limited to 'ext/wasm/api/sqlite3-api-glue.js')
0 files changed, 0 insertions, 0 deletions