Expand the worker1 'exec' op handling for per-row callbacks for API-level consistency and smooth some edges between worker1 core and worker1-promiser. Add worker1 'config-get' message to fetch the serializable parts of the sqlite3.config state. Improve the 'open' op's handling of the 'persistent' option (noting that we cannot yet test that case from a worker).

FossilOrigin-Name: 509f8839201ec1ea4863bd31493e6c29a0721ca6340755bb96656b828758fea7

1 files changed, 15 insertions, 0 deletions

diff --git a/ext/wasm/api/sqlite3-api-oo1.js b/ext/wasm/api/sqlite3-api-oo1.js
index be9d8af5a..e16b45bb5 100644
--- a/ext/wasm/api/sqlite3-api-oo1.js
+++ b/ext/wasm/api/sqlite3-api-oo1.js
@@ -252,6 +252,21 @@ self.sqlite3ApiBootstrap.initializers.push(function(sqlite3){
               out.cbArg = (stmt)=>stmt.get(out.opt.rowMode);
               break;
             }
+            /*
+              TODO?: how can we define rowMode such that it uses
+              rowMode of 'object' and returns a given named field from
+              the object. Something like:
+
+              if(?what goes here?){
+                out.cbArg = function f(stmt){return stmt.get(this.obj)[this.colName]}
+                  .bind({obj:{}, colName: ???what goes here???}});
+                break;
+              }
+
+              Maybe rowMode:['colName1',... 'colNameN']? That could be
+              ambiguous: might mean "return an object with just these
+              columns".
+            */
             toss3("Invalid rowMode:",out.opt.rowMode);
       }
     }