???? only happens on the jurisdiction *table* not sure why its throwing a r2 bucket error lol
???? only happens on the jurisdiction table not sure why its throwing a r2 bucket error lol

token_hash is an indexed column in the table, but that query took 16.59 seconds to complete in a table that has 64,360 items in itamount -= 100 might cause a problem known as a race condition (I think). It seems D1 doesn't support transactions, so could async operations cause issues here?I have seen high hundreds of thousands or single digit millions reads per second.Wait! How is that possible? I've been using no more 1,000 request/messages per second as design ceiling for DOs, eventhough, I've seen as high as 5,000. Even assuming 5,000, you'd need 200 read replicas to hit 1M. Does D1 go to that level?
batch() query and they will all run within the same transaction.
batch() method for running independent queries in a transaction.
