Fixing D1 "no such table" after a migration that seemed to run
Covers the two most common causes: applying a migration to the wrong local/remote target, and a Worker binding pointing at a different database_id than the one that was migrated. Does not cover a migration file that itself has a SQL error (that fails loudly at apply time, not later as "no such table"), or drift specifically caused by an ORM's own migration tracking — see the Drizzle-specific playbook for that. Also covers a preview_database_id on the binding sending wrangler dev to a different database from the one the migration was applied to.
Unverifiedno reproductions yetWhy this confidence?