H
NNHNN
N
YYYYYY
LY
Y
NH
wrangler deploy
CNNYLone() does not return null, it will throw when it doesn't find a result.LrowsRead you get is not the number of results. It's the number of rows read by SQLite to satisfy your query. So, if you do joins, scans, etc, and only end up with 1 row, you are not just charged for 1 row, but all the rows that had to be read to answer your query. YYYY
thank you for the info!
I
1
S
LIf you invoke put() (or delete()) multiple times without performing any await in the meantime, the operations will automatically be combined and submitted atomically. In case of a machine failure, either all of the writes will have been stored to disk or none of the writes will have been stored to disk.
HLIL
.batch([query_1, query_2]) function will use SQLite transactions under the hood so you can make sure both queries either commit or rollback. https://developers.cloudflare.com/d1/build-with-d1/d1-client-api/#dbbatchHstorage.transaction work with SQLite-engine DOs?Lstorage.transaction working for "SQLite-engine DOs" is great! However, is that just for the old get(), put(), etc. calls or does it work for SQL statements also?HHLfetch
HL
.exec() method does the prepare statements for you. Soon they will be cached automatically as well.L.sql.exec()If you invoke put() (or delete()) multiple times without performing any await in the meantime, the operations will automatically be combined and submitted atomically. In case of a machine failure, either all of the writes will have been stored to disk or none of the writes will have been stored to disk.
Cannot create binding for class 'Trainer' because it is not currently configured to implement durable objects. Did you forget to apply a --new-class migration to it? [code: 10061]npx wrangler deploy --new-class Trainer
✘ [ERROR] Unknown arguments: new-class, newClass[[durable_objects.bindings]]
name = "DURABLE_TRAINER"
class_name = "Trainer"
[[migrations]]
tag = "v1"
new_classes = ["Trainer"] Cannot create binding for class 'Trainer' because it is not currently configured to implement
durable objects. Did you forget to apply a --new-class migration to it? [code: 10061]one()rowsRead.batch([query_1, query_2])storage.transactionstorage.transactionget()put().exec().sql.exec()