Lhow are we supposed to do long running maintenance operations in d1?What do you want to do exactly? What's "maintenance operations" here? A D1 database processes 1 request at a time and since SQLite queries are usually a few milliseconds you can execute many per second, But, if you are doing something that takes more than a few seconds/minutes, then it won't behave nicely for several reasons.
L
DDL
RDDJDJJDJJL
bind(), not how many rows you can operate on.
D
D
R
D1_ERROR: Network connection lost errors? 
D
AL
ZLZ
LZLZZLZBy the end of 2024, D1 will support automatic read replication for scalability and low-latency access around the world. If this managed model appeals to you, use D1.
J
P
UNION ALL SELECT terms. According to SQLite documentation, the number of terms in the query is limited by the value SQLITE_MAX_COMPOUND_SELECT which defaults to 500. But in D1 this is set to 5 and any query with more than 5 terms (like for inserting multiple values at once) fail with too many terms in compound SELECT. P
AD1_ERROR: Network connection lost. errors being thrown since friday. Any idea if this is on d1 or my side?AK
LKK.sqlite file not found in ${basePath});Error ${err});A
D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.
CAAACAADELETE FROM table_name
WHERE id IN (
SELECT id
FROM table_name
WHERE condition
LIMIT 10
);bind()D1_ERROR: Network connection lostUNION ALL SELECTSQLITE_MAX_COMPOUND_SELECTtoo many terms in compound SELECTD1_ERROR: Network connection lost..sqlite file not found in ${basePath}Error ${err}D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.select * from table where timestamp > ? order by timestamp desc