M
B
H
wrangler.wranglerwrangler d1--local to run locallywrangler dev--remote
Jpnpm run build & npx wrangler pages dev ./public --compatibility-date=2023-11-15 --d1=DB creates a d1 database under .wrangler/state/v3/d1/miniflare-D1DatabaseObject folder. This is different from CF worker which store database under .wrangler/state/v3/{database_id} which can be operated like wrangler d1 execute $DATABASE_NAME --file=./seed.sql --local which observes wrangler.toml
{database_id} folder and the one in the miniflare-D1DatabaseObject folder? which one is local and which one is prod?Hminiflare-prefixed SQLite files are used for internal storage in wrangler
C
_
MWe’re setting a clear goal: we want to make D1 “generally available” (GA) for production use-cases by early next year (Q1 2024).
_
TMM
BCB_HHB
S
J
UCCM
VVVM
M
K
undefinedNot supported. Queries with undefined values will return a D1_TYPE_ERROR
KundefinedbindMK
bind and seeing which one is undefined, and going from there - the part of the D1 binding that throws that error hasn't changed functionally in a very long time.J--localpnpm run build & npx wrangler pages dev ./public --compatibility-date=2023-11-15 --d1=DB.wrangler/state/v3/d1/miniflare-D1DatabaseObject.wrangler/state/v3/{database_id}wrangler d1 execute $DATABASE_NAME --file=./seed.sql --local{database_id}miniflare-D1DatabaseObjectminiflarebindbind[env.staging]
d1_databases = [
{ binding = "DB", database_name = "test1", database_id = "1111", preview_database_id = "DB" },
]
wrangler pages deploy ./public --project-name myproj --env staging # works
[env.production]
d1_databases = [
{ binding = "DB", database_name = "test1-prod", database_id = "1111" },
]
wrangler pages deploy ./public --project-name myproj --env production --branch main # throw "Cannot read properties of undefined (reading 'prepare')"