db-migrate

You generate Alembic migrations by autogenerating a revision from SQLAlchemy model changes using a descriptive snake_case message. The tool creates the revision from apps/api, presents the resulting table and column changes, and validates downgrade behavior before applying anything.

To safely apply database schema migrations to a non-empty PostgreSQL database, the tool presents the generated migration changes for review and only executes alembic upgrade head after explicit confirmation. This reduces the risk of breaking existing production databases by validating intent first.

Yes, you can review and validate downgrade behavior before running an Alembic migration. The tool highlights table and column changes alongside downgrade correctness, requiring you to confirm intent before it applies the alembic upgrade head command to your PostgreSQL schema.

Yes, db-migrate works with PostgreSQL for adding columns and altering constraints. It fits workflows requiring controlled schema evolution for PostgreSQL-backed services, generating SQLAlchemy migrations that accurately capture constraint alterations and column additions for your database.

If an Alembic migration fails during the upgrade head process, the tool surfaces the full error details. This immediate error reporting helps developers diagnose schema evolution issues without guessing what went wrong during the PostgreSQL database migration.