.exec() await db.batch(statements).exec()await db.batch(statements)
MMM
H
run() itself? Like, if you have a statement where you don’t need the results at all, or loading the results into memory would be a waste, then you run() instead of first() or all(). And I would expect the size argument to be even more compelling if you are batching many statements togetherHH
M
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!Hbatch(): In the case of an UPDATE, you probably don't care what it returns, just that the entire thing completes, so returning anything more than statistics on the statement execution isn't needed. And this isn't for a specific use case, this was more just out of curiosity on why batch() 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...run()run()run()first()all()batch()batch()UPDATE[column].all()await 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 ),
]);