__D1_BETA__ infront of your binding name. Something like this:/accounts/${accountId}/workers/scripts/${scriptName} and D1 will be successfully bind
Note that not all limits can be increased.The original prototype backend just doesn’t perform well above 100MB. It’s pointless to increase it.
e68dccd4-7bf7-4860-ba18-17978966ec10wrangler has been, basically from the beginning, a tool that uses toml. They are adding a system to parse JSON into an object that wrangler can use that matches the toml spec, but there may be some points that don't just workwrangler used to be written in Rust, which is why it started out with toml. And you can still run Workers entirely without writing JS(see #workerd, which isn't JS at all. And they are moving toward JSON configs nowe68dccd4-7bf7-4860-ba18-17978966ec10 is on the older alpha backend)[[ d1_databases ]]
binding = "__D1_BETA__DB_ONE"
database_name = "db-one"
database_id = "<someID>"
migrations_table = "d1_migrations"
migrations_dir = "d1_migrations/db-one"
[[ d1_databases ]]
binding = "__D1_BETA__DB_TWO"
database_name = "db-two"
database_id = "<someId>"
migrations_table = "d1_migrations"
migrations_dir = "d1_migrations/db-two"__D1_BETA__metadata.bindings.push({
name: `__D1_BETA__${db.name}`,
type: 'd1',
id: db.id,
})/accounts/${accountId}/workers/scripts/${scriptName}{
"message": "D1_ERROR",
"cause": "Error: D1 storage operation exceeded timeout which caused object to be reset."
}