TT
M
follow up: it seems like bracketing it with PRAGMA defer_foreign_keys = ON; and PRAGMA defer_foreign_keys = OFF; does make it work. I am not familiar enough with arcane SQLite stuff to give a super informed view on whether this should be automatically applied to every migration, but I suspect it might be a good idea - my understanding is that the foreign key constraints will still be checked, but just at the time that the transaction is committed.
T
PRAGMA defer_foreign_keys = ON/PRAGMA defer_foreign_keys = OFF but it does not work either...TMTPRAGMA defer_foreign_keys, Table B was modified and my table A are cascaded without any errors like before
JJT
.wrangler/state/v3/d1. It's a sqlite file, you could explore or even modify it using your favorite toolTJTJJTTTJJ
TJT
ITIIITI
M
wrangler d1 export: https://github.com/cloudflare/workers-sdk/pull/5425JIIJI
I
II
JJJJMM
KJJJJ
PRAGMA defer_foreign_keys = ONPRAGMA defer_foreign_keys = OFFPRAGMA defer_foreign_keys.wrangler/state/v3/d1The Database Tools and SQL plugin is available only in IntelliJ IDEA Ultimate.✘ [ERROR] Wrangler could not process the provided SQL file, as it contains several transactions.
D1 runs your SQL in a transaction for you.
Please export an SQL file from your SQLite database and try again.wrangler d1 export async scheduled(event, env, ctx) {
ctx.waitUntil(doSomeTaskOnASchedule(env, ctx));
ctx.waitUntil(theOtherTask(env, ctx));
}