Remove a couple of weird quirks of the Worker1 and Promiser APIs. The Worker1 (now undocumented) unlink capability needs to be reevaluated to work equivalently for all storage backends.

FossilOrigin-Name: 9f2b331a32cbaadfd20d04c9908171355322c1aa1d9d6df3628f3b2fb4391ec1

1 files changed, 3 insertions, 7 deletions

diff --git a/ext/wasm/api/sqlite3-api-worker1.js b/ext/wasm/api/sqlite3-api-worker1.js
index c3b1fb59d..69bb8ced6 100644
--- a/ext/wasm/api/sqlite3-api-worker1.js
+++ b/ext/wasm/api/sqlite3-api-worker1.js
@@ -225,13 +225,7 @@
     type: "close",
     messageId: ...as above...
     dbId: ...as above...
-    args: OPTIONAL: {
-
-      unlink: if truthy, the associated db will be unlinked (removed)
-      from the virtual filesystems. Failure to unlink is silently
-      ignored. Does not currently work for all storage backends.
-
-    }
+    args: none
   }
   ```
 
@@ -460,6 +454,8 @@ sqlite3.initWorker1API = function(){
         filename: db && db.filename
       };
       if(db){
+        // Keep the "unlink" flag undocumented until we figure out how
+        // to apply it consistently, independent of the db storage.
         wState.close(db, ((ev.args && 'object'===typeof ev.args)
                           ? !!ev.args.unlink : false));
       }