--persist-to=/path/to/file to persist data to a specific location but no luck and on seeding I couldn't find any relevant info.--persist-to=/path/to/file
C
AA
prestart script that runs a ts file to init local sqlite and seed it
VVwrangler 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 agoAA
--persist-to=/path/to/file
Mpreview_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 migrations inside your tests: the example shows that.MAAdb. Is there a way to change that by just changing binding 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
prestartwrangler d1 migrationswrangler d1 migrationswrangler d1 migrations apply <db-name> --localname.sqlitedbbindingwrangler 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⛅️ wrangler 3.1.0 (update available 3.1.1)