supabase-migration-local

To generate a timestamped Supabase migration safely, describe your desired schema change and SQL content to create a file in supabase/migrations/ that follows naming conventions and is prepared for manual review rather than automatic execution.

The best way to add a rollback to a Supabase SQL migration is to include an optional rollback section when generating the file, allowing you to safely revert schema changes like adding tables or altering columns during deployment.

You cannot automatically execute schema changes, but you can automatically generate a timestamped SQL migration file for altering tables and columns that is safely prepared for your manual review and application.

To enforce a naming convention for database migrations in a Supabase project, use a migration generator that automatically timestamps and formats the SQL file in the supabase/migrations/ directory, capturing details for traceability.

Generating a Supabase migration file does not automatically apply the SQL changes to your database; the file is explicitly prepared for manual review and application to reduce the risk of unintended schema changes.

You need a timestamped SQL migration file for Supabase database schema changes when adding or altering tables, columns, or indexes, ensuring the changes are traceable and safely separated from automatic execution.