Is D1 having an especially hard time currently?
Is D1 having an especially hard time currently?

668d0e1f-b01a-4048-8796-fdf4530fb192
when we enable global read replication, you won’t have to pay extra for it, nor will replication multiply your storage consumption. 
5/19/23, 1:29 PM



sqlite3 file.sqlite3 .dump > db.sqlwrangler trying to parse your file. We haven't optimized this yet (it's unrelated to D1 / the storage backend). Break it up into ~5k line files.Error: D1_ERRORs

668d0e1f-b01a-4048-8796-fdf4530fb192when we enable global read replication, you won’t have to pay extra for it, nor will replication multiply your storage consumption.sqlite3 file.sqlite3 .dump > db.sql~/repos/d1-demo (master) ✗
➜ npx wrangler@3 d1 execute key-value-db --file src/kv-5k.sql
🌀 Mapping SQL input into an array of statements
🌀 Parsing 5000 statements
🌀 Executing on key-value-db (a197cf87-47ad-4473-b900-4c59c42f509d):
🚣 Executed 5000 commands in 201.99864504113793msError: D1_ERROR{
"message": "D1_ERROR",
"cause": "Error: Error 9000: something went wrong"
}