@PhilippSalvisberg here's a simple prototype that's backward compatible.

Thanks for the follow-up.

AFAIU the cases I mentioned in#41 (comment) (bind definitions e.g. for output parameters andexecuteMany) are not simplified by this change.

I can see that this change simplifies some code for a series of similar SQL statements (bind/execute in a loop). However, usingexecuteMany in OracleDB or a single SQL statement would probably be more efficient.

Maybe I didn't understand the intention and the use case.

However, using executeMany in OracleDB or a single SQL statement would probably be more efficient.

Good question. I was trying to make it easier to useexecuteMany. You'd be able to do something like:

constquery=sql`UPDATE x SET y =${BIND_PARAM} WHERE z =${BIND_PARAM}`;constresult=db.executeMany(query.statement,[[1,1],[2,2],[3,4]]);

However, if you wanted better safety for the params:

constresult=db.executeMany(query.statement,[query.bind(1,1),query.bind(2,2),query.bind(3,3)]);

You are right that it's a very marginal improvement, and you could just use1 or something and ignorevalues anyway and it'd work the same as the first example. The only difference would be if you happened to have something like this mixing positions you want to bind later and bind now:

constquery=sql`UPDATE x SET y =${true} WHERE z =${BIND_PARAM}`;constresult=db.executeMany(query.statement,[query.bind(1),query.bind(2),query.bind(3)]);// Would be `[[true, 1], [true, 2], [true, 3]]`.

(...)

const query= sql`UPDATE x SET y = ${true} WHERE z = ${BIND_PARAM}`;const result=db.executeMany(query.statement, [query.bind(1),query.bind(2),query.bind(3)]);// Would be`[[true, 1], [true, 2], [true, 3]]`.

Excellent example. Thanks for the explanation. I agree. This new feature can simplify the code, especially with many "fixed" bind values and a few delayed bindings.