supabase-database-migration

You can manage Supabase database schema changes by editing Drizzle ORM schema definitions in code, using drizzle-kit to generate timestamped SQL migrations, and applying them locally or to remote environments.

Generating SQL migrations from a Drizzle schema involves using the drizzle-kit db:generate command to automatically create timestamped SQL migration files based on your code definitions.

To apply local database migrations in a Supabase workflow, you use the `supabase migration up` command to apply new changes or `supabase db reset` to reset the local database to a clean state.

Deploying Drizzle schema changes to a remote Supabase project is done using the `supabase db push` command after testing the generated SQL migrations locally.

Schema drift occurs when code, migrations, and local databases fall out of sync; enforcing a schema-first workflow prevents this by ensuring Drizzle definitions generate matching SQL migrations.

While drizzle-kit generates the schema migrations, resetting the local Supabase database is handled by the `supabase db reset` command to ensure a clean state for testing.