Use Alembic instead: http://pypi.python.org/pypi/alembic Thanks for comments, edited to add some reasoning — It’s developed by the author of SQLAlchemy, and it’s brand new and well supported. I don’t know enough about sqlalchemy-migrate to give a good comparison. But I took a quick read through the clear and concise Alembic docs, then got my own … Read more
I decided on this problem using that. I changed the code of migration, and migration looks like this: from alembic import op import sqlalchemy as sa from sqlalchemy.dialects import postgresql def upgrade(): banner_status = postgresql.ENUM(‘active’, ‘inactive’, ‘archive’, name=”banner_status”) banner_status.create(op.get_bind()) op.add_column(‘banner’, sa.Column(‘status’, sa.Enum(‘active’, ‘inactive’, ‘archive’, name=”banner_status”), nullable=True)) def downgrade(): op.drop_column(‘banner’, ‘status’) banner_status = postgresql.ENUM(‘active’, ‘inactive’, ‘archive’, … Read more
Alembic stores the version history in your database. Hence it is using the value stored in your database to search for the revision. The version number for my personal database is stored in the table alembic_version: mysql> SELECT * FROM alembic_version; +————-+ | version_num | +————-+ | c8ad125e063 | +————-+ 1 row in set (0.00 … Read more