You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after upgrading to heads, we want to do a downgrade to a2. a2 is a depedency of b3.
#!
[classic@photon2 tmp]$ python -m alembic.config downgrade e429
INFO [alembic.runtime.migration] Context impl SQLiteImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
INFO [alembic.runtime.migration] Running downgrade aa1788c001d4 -> e429b4a0d347, a3
INFO [alembic.runtime.migration] Running downgrade 677fdb99c800 -> 72b2398778e8, b4
INFO [alembic.runtime.migration] Running downgrade 72b2398778e8 -> 0d4fdbc6d7bf, e429b4a0d347, b3
So now we are on "a2", but in doing so, it downgraded b3 as well! there's no reason to downgrade b3, its dependency a2 is still there. The reason this happens is because it's treated as an unmerge point, which in reality, it's not.
The text was updated successfully, but these errors were encountered:
Don't remove dependent version when downgrading to a version.
Adjusted the version traversal on downgrade
such that we can downgrade to a version that is a dependency for
a version in a different branch, without needing to remove that
dependent version as well. Previously, the target version would be
seen as a "merge point" for it's normal up-revision as well as the
dependency. This integrates with the changes for 🎫377
and 🎫378 to improve treatment of branches with dependencies
overall.
Migrated issue, originally created by Michael Bayer (@zzzeek)
Lets build this:
after upgrading to heads, we want to do a downgrade to a2. a2 is a depedency of b3.
So now we are on "a2", but in doing so, it downgraded b3 as well! there's no reason to downgrade b3, its dependency a2 is still there. The reason this happens is because it's treated as an unmerge point, which in reality, it's not.
The text was updated successfully, but these errors were encountered: