galaxy-db-migration

To create a database migration after updating a SQLAlchemy model, generate a new Alembic migration revision to capture the schema changes for the Galaxy project. This ensures your codebase and live database stay consistent.

Alembic manages database schema migrations for Galaxy by tracking revisions across both gxy and tsi branches, allowing you to apply schema modifications, resolve version conflicts, and maintain consistency between code and database versions.

Yes, you can upgrade or downgrade the Galaxy database to specific versions using Alembic revision commands. This allows you to apply new schema changes or roll back to previous database states during development.

The best way to check migration status is to verify the current Galaxy database version against the codebase using Alembic status commands. This confirms whether all pending schema migrations have been applied or if updates are required.

To troubleshoot common Galaxy database migration errors, use the Skill to diagnose and resolve version conflicts or schema inconsistencies. It helps identify pending migrations and ensures the database matches the expected SQLAlchemy models.

You need to use Alembic for Galaxy database schema modifications whenever you update SQLAlchemy models and must propagate those structural changes to the live database without losing existing data.