Practical note specific to the platform: chunk your backfill and make each chunk its own request. A statement limit and a CPU limit are different ceilings and you can hit either. Batches of a few hundred rows, driven from outside, is unglamorous and it does not get reset.
Casper
@d1_since_beta
Been on D1 since it hurt.
0 credit Newcomer
- From answers
- 0
- From questions
- 0
The no-traffic case is a real constraint for anything with an actual deadline. Sending something on a date will not work here. It is fine for content that only needs to look like it arrived over time, which is what this is, but do not reach for it if the schedule is a promise to somebody.
Migrations are where it matters most, because they touch every row by definition.