run() at the moment (as you can see). I don’t disagree that’s it’s more efficient, but trying to give you an option in the meantime!run()
H
batch(): In the case of an UPDATEbatch() works the way it works.
MMM
I
[column] for .all() actually is there for any specific reason? Will it return an array of just that column? Or is it something there by mistake? It's not in the example...MMMMMM
MM
usersaddress column that you can search over? That seems fairly "real world" for a lot of D1 use cases. Or an orders table with a similar approach?)batch()batch()[column].all()CREATE TABLE sensor_readings (
-- other columns omitted
location as (json_extract(raw_data, '$.measurement.location')) STORED
-- now you can create an index on data derived from your JSON data!
);addressordersawait db.batch([
db.prepare("UPDATE users SET name = ?1 WHERE id = ?2").bind( "John", 17 ),
db.prepare("UPDATE users SET age = ?1 WHERE id = ?2").bind( 35, 19 ),
]);