db-migration

To set up database migrations for a FastAPI and SQLModel project, initialize Alembic using the alembic init command, then configure it to integrate with SQLModel metadata for autogenerating schema revisions.

Yes, you can autogenerate Alembic migration revisions directly from SQLModel metadata by running the alembic revision --autogenerate command, which detects schema changes and creates corresponding version scripts.

The best way to rollback a database migration in production is to use the alembic downgrade command, which this skill enforces with safe, idempotent rollback guidance to ensure predictable schema evolution.

Yes, this Alembic migration skill handles data migrations alongside schema evolution by providing templates for common scenarios, ensuring safe upgrades and downgrades across evolving schemas in development and production.

Alembic migrations may fail during SQLModel schema evolution if not properly integrated with metadata or if migrations lack idempotency; this skill provides safe templates and rollback guidance to prevent such issues.