database-migrations

PostgreSQL schema migrations are created using the make migrate-create command and applied via Make targets. This generates sequential SQL scripts in the services/migrations directory and tracks them using a schema_migrations table for safe rollbacks.

The best way to add columns or indexes safely is using versioned migration scripts. This Skill automates PostgreSQL schema evolution by generating sequential up/down SQL files, ensuring changes are tracked and can be rolled back if issues arise.

Yes, this database migration approach supports production environments. It automates PostgreSQL schema evolution for both development and production workflows, using a schema_migrations tracking mechanism to ensure safe rollbacks.

To rollback a schema change in PostgreSQL, this Skill uses down migration scripts stored in the services/migrations directory. The schema_migrations tracking mechanism ensures that applied changes can be safely reversed.

Yes, you need Make to run these PostgreSQL migrations. The workflow requires Make targets to generate, apply, and rollback migrations, specifically executing commands like make migrate-create within the services directory.

Versioned migration scripts provide structured schema evolution by storing forward and backward SQL sequentially. This ensures database changes are tracked consistently and allows safe rollbacks when modifying PostgreSQL tables, columns, or indexes.