diff options
Diffstat (limited to 'ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js')
| -rw-r--r-- | ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js b/ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js index 39094a6f8..e1e7b45b8 100644 --- a/ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js +++ b/ext/wasm/api/sqlite3-vfs-opfs-sahpool.c-pp.js @@ -867,9 +867,9 @@ globalThis.sqlite3ApiBootstrap.initializers.push(function(sqlite3){ This function throws if SQLite has any opened file handles hosted by this VFS, as the alternative would be to invoke - Undefined Behavior by closing file handles out from under any - the library. Similarly, automatically closing any database - handles opened by this VFS would invoke Undefined Behavior in + Undefined Behavior by closing file handles out from under the + library. Similarly, automatically closing any database handles + opened by this VFS would invoke Undefined Behavior in downstream code which is holding those pointers. If this function throws due to open file handles then it has @@ -1314,7 +1314,7 @@ globalThis.sqlite3ApiBootstrap.initializers.push(function(sqlite3){ returned Promise resolves to this object on success. A rejected Promise means there was a problem reacquiring the SAH handles (possibly because they're in use by another instance or have - since been removed). Generically speaking, there is recovery + since been removed). Generically speaking, there is no recovery strategy for that type of error, but if the problem is simply that the OPFS files are locked, then a later attempt to unpause it, made after the concurrent instance releases the SAHs, may |