Let's say you're on branch and you have a migration, you test it out, it 
works: everything is cool. The version in `public.alembic_version` is your 
latest migration.
Before you merge it you have to switch to a different branch to work on 
something else and you also have a migration there.

You want to use `alembic stamp` to move back to the previous state, but 
`alembic` will complain that it can't find the revision stored in 
`public.alembic_version`, since it was in your other branch.

The work around is to just drop the table and redo the stamp. I think it 
would be convenient for `alembic` to bypass this check, what do you think?

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 sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to