database-migrations

Zero-downtime database migrations require strategies like forward-compatible rollbacks and phased schema changes to avoid locking tables. This approach provides guidelines for safe schema changes and data migrations across PostgreSQL and MySQL.

To add a new column to a PostgreSQL table without downtime, you should use backward-compatible schema changes and avoid locking operations. This Skill provides best practices for safely altering tables and rolling back changes if needed.

Yes, this database migration skill works with Prisma and Drizzle, as well as Kysely, Django, TypeORM, and golang-migrate. It covers best practices for schema changes and data migrations across these specific ORMs.

Handling data backfilling during schema changes involves strategies for transforming and validating data while the database is live. This Skill includes specific guidelines for executing data migrations safely alongside zero-downtime deployment strategies.

Yes, you can ensure safe rollbacks when altering database tables by using forward-compatible deployment strategies. This Skill ensures that rollbacks are possible with minimal downtime and data loss across supported databases.