Ok yep, looks like an issue our side - gonna let the team know! Thanks for reporting, we'll get it f
Ok yep, looks like an issue our side - gonna let the team know!
Thanks for reporting, we'll get it fixed!
Thanks for reporting, we'll get it fixed!


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? import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";
export default defineWorkersConfig({
test: {
globals: true,
poolOptions: {
workers: {
isolatedStorage: true,
wrangler: { configPath: "./wrangler.toml" },
},
},
},
});import { Hono } from 'hono'
export type Env = {
DB: D1Database
}
const app = new Hono<{ Bindings: Env}>()
app.get('/', async (c) => {
console.log(c.env.DB)
return c.text("Hello world!")
})
export default appsamworkerdbigintINTEGERnpx wrangler d1 export dharmaradio --remote --output=dump.sqlnpx wrangler d1 execute dharmaradio --remote --file=dump.sql{"D1_RESET_DO":true}ENAM_OBJECTSENAM_USERSWNAMCOUNT(id)