anyone seeing a higher than usual amount of D1 errors (timeout, connection lost, etc)
anyone seeing a higher than usual amount of D1 errors (timeout, connection lost, etc)
D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be resetD1_ERROR: Network connection lost.D1_ERROR: internal error; reference = 3n7qu7dkdd0atgp7vioes6a5 589bafbd-d600-4e01-8879-7443811d45a1 if that's of any use.
wrangler pages dev may not work as expected, even when preview_database_id is set in wrangler.toml and --persist-to is used in the dev script. Runtime operations (e.g., API calls creating new data) might connect to a new, blank D1 instance instead of the schema-initialized, persisted one. This leads to "no such table" errors and data loss between development server restarts.So you've to use D1 for that with different concept. Cloudflare database (D1, DO) is broken. D1 has different limitation while DO has differentI wonder why you say this. Actually, D1 has exactly the same limitations as a single Durable Object, and even more since your worker code is remotely from the actual storage and you don't have things like transactions across queries interleaved with JS code, whereas in the DO case your code runs next to the storage and is fast. Resource limits wise, a D1 database IS a single Durable Object, so zero differences.
this in each new constructor instanceD1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset. .... Or just accept and move on?D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.