database-migrations

Zero-downtime database migrations require breaking schema changes into backward-compatible steps. This Skill provides patterns for safe column alterations and deployments across SQL, Prisma, Drizzle, Django, and golang-migrate to prevent user-facing interruptions.

Backfilling large data without table locks involves batch processing strategies. This Skill outlines data migration patterns for transforming data safely, avoiding prolonged locks, and ensuring production stability during large-scale schema changes.

Yes, this database migration guidance integrates with Django and Prisma. It also covers Drizzle and golang-migrate, providing ORM-specific examples and best practices for schema changes, rollbacks, and zero-downtime deployments.

Safely adding a nullable column to PostgreSQL involves applying non-breaking schema changes first. This Skill guides you through the exact steps to add, alter, or remove columns without causing downtime or data loss.

Common anti-patterns for production database schema changes include locking tables and breaking backward compatibility. This Skill provides a safety checklist to identify these issues and ensure safe rollbacks.

You need specific database migration patterns when altering schema or backfilling data in production. This Skill addresses when to apply these patterns to prevent data loss and manage safe rollbacks across multiple database systems.