wrangler d1 migrations, you can use a migration to seed the database or if you want a more programatic approach scroll up a bit, we had a discussion about possibilites just a few hours agowrangler d1 migrations
AA
--persist-to=/path/to/file
M
preview_database_idwrangler d1 migrations apply <db-name> --local -> you can apply migrations locally to seed the DB. As above, you can also do that programatically via your test harness
AA
name.sqlite file?AAAAMwrangler d1 migrationsdbbinding in wrangler config?
DDwrangler d1 execute --local --comand="SELECT NOTHING"DDDD
A
Error: statement too longMAM
I
I
BBB
M
cause should not be deprecated, it's still thereMBError: too many terms in compound SELECT (coming from a select {condition} union all select {another condition} ).. I suppose I'm wondering what SQLite differences would account for this seeing that the query works in the regular backend but errors out in the experimental?MBB
K
SQLITE_LIMIT_COMPOUND_SELECT set to 3BM
BMBMM.cause in that--persist-to=/path/to/filewrangler d1 migrations apply <db-name> --localname.sqlitebindingwrangler d1 execute --local --comand="SELECT NOTHING"Error: statement too longcauseError: too many terms in compound SELECTselect {condition} union all select {another condition} SQLITE_LIMIT_COMPOUND_SELECT3.cause