Hi, Here's something quite fundamental I don't understand about alembic. I've initialized my database and created a revision meant to be executed online. I went like this: alembic init app/alembic # edit configuration alembic revision -m 'Data modification' # edit revision script alembic upgrade
If I run alembic upgrade a second time, it runs the upgrade function again, which results in an error because my function should not be run on the new database (it's not idempotent). Why doesn't alembic figure out that the upgrade has already been applied? This is especially annoying in production where I just want to make sure the database is up to date without having to guess which revision script to execute. Best, -- Bertrand -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
