lightfriend-db-migration

To create reversible Diesel migrations, generate a migration with a descriptive name, write the schema changes in up.sql, and create the reversal logic in down.sql. This ensures you can rollback changes safely if issues are detected later.

The best way to rollback a Diesel migration is by running the corresponding down.sql file. This skill guides you through writing and executing reversible migrations to revert database schema changes safely when problems occur.

Yes, Diesel supports database migrations for both SQLite and PostgreSQL backends. This skill applies to Rust projects using Diesel, covering generation, editing, applying, and rollback of migrations across these database systems.

After running and verifying your Diesel migration, you regenerate the schema and update your Rust models accordingly. This ensures your application code stays synchronized with the newly evolved database schema.

You need up.sql and down.sql files to enforce reversible database schema migrations. up.sql applies the structural changes to PostgreSQL, while down.sql provides the exact rollback commands to safely revert those changes if needed.

Without a guided workflow, managing Rust database schema changes risks schema drift and unsafe modifications. This skill enforces using up.sql, down.sql, migration verification, and schema regeneration to reduce these risks.