heh, well the problem is "reducing" the size briefly increases the size due to writing all the chang
heh, well the problem is "reducing" the size briefly increases the size due to writing all the changes to the WAL file
no such table: dbstatSQLITE_ENABLE_DBSTAT_VTAB)workerdarray (oneOf) [objects] next to the bindings until you find the D1 one.
database_id vs id was fixed though, since the API does return database_id in a few places, so I'll ask the team on Monday..mf/d1/miniflare-D1DatabaseObject/{hash}.sqlite. But if I run wrangler d1 migrations apply DB --local --persist-to ./.mf it creates a new db at .mf/v3/d1/miniflare-D1DatabaseObject/{hash}.sqlite instead (note the extra /v3/)..wrangler/state/v3/d1/miniflare-D1DatabaseObject/{hash}.sqlitev3.28.3, and if I add path to wrangler.toml like you have it does nothing. The migration script still targets the .wrangler folderno such table: dbstatSQLITE_ENABLE_DBSTAT_VTABarray (oneOf) [objects].mf/d1/miniflare-D1DatabaseObject/{hash}.sqlitewrangler d1 migrations apply DB --local --persist-to ./.mf.mf/v3/d1/miniflare-D1DatabaseObject/{hash}.sqlite/v3/.wrangler/state/v3/d1/miniflare-D1DatabaseObject/{hash}.sqlitev3.28.3import { Miniflare } from 'miniflare'
const mf = new Miniflare({
d1Databases: ["DB"],
modules: true,
script: "",
d1Persist: true,
})