Yes, already read that, but was not sure if applicable to the db limit in General too. Thanks!
Yes, already read that, but was not sure if applicable to the db limit in General too. Thanks!
sam? It just says it's not available but no comments on weather there are plans or not. (https://developers.cloudflare.com/d1/configuration/data-location/#available-location-hints)workerd repo like https://github.com/cloudflare/workerd/blob/main/src/workerd/util/sqlite.c%2B%2B, but if you're new to D1, the Getting Started guide is going to the best place to start: https://developers.cloudflare.com/d1/get-started/


bigint is not a valid SQLite type and gets converted to one of the native ones, in this case INTEGER.npx wrangler d1 export dharmaradio --remote --output=dump.sql creates a dump which can't be imported again via npx wrangler d1 execute dharmaradio --remote --file=dump.sql.{"D1_RESET_DO":true} . ENAM_OBJECTS is an empty database in a closer pop than ENAM_USERS. Same with the WNAM databases)COUNT(id) every X minutes and storing it somewhere like KV (from a database workload nor a performance standpoint). But I've just realized that'd be an EXTREMELY bad idea with SQLLite and D1 row-based pricing right? D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.. This happens rarely, but has been happening for weeks and when it happens no request is able to query the database. It seems like it randomly freezes for 30s and then returns that error8a298455-ac11-4e0c-b160-4db807cf3572samworkerdbigintINTEGERnpx wrangler d1 export dharmaradio --remote --output=dump.sqlnpx wrangler d1 execute dharmaradio --remote --file=dump.sql{"D1_RESET_DO":true}ENAM_OBJECTSENAM_USERSWNAMCOUNT(id)D1_ERROR: D1 DB storage operation exceeded timeout which caused object to be reset.8a298455-ac11-4e0c-b160-4db807cf3572