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.
Fixed bug where the indexes would not be included in a
migration that was dropping the owning table. The fix
now will also emit DROP INDEX for the indexes ahead of time,
but more importantly will include CREATE INDEX in the
downgrade migration.
Fixed bug where the indexes would not be included in a
migration that was dropping the owning table. The fix
now will also emit DROP INDEX for the indexes ahead of time,
but more importantly will include CREATE INDEX in the
downgrade migration.
Change-Id: I15852bf1cca6de26dd6e7e5ede69bc9e2145c5c0
Fixes: sqlalchemy#468
vvvrrooomm
pushed a commit
to vvvrrooomm/alembic
that referenced
this issue
Jan 10, 2019
Fixed bug where the indexes would not be included in a
migration that was dropping the owning table. The fix
now will also emit DROP INDEX for the indexes ahead of time,
but more importantly will include CREATE INDEX in the
downgrade migration.
Change-Id: I15852bf1cca6de26dd6e7e5ede69bc9e2145c5c0
Fixes: sqlalchemy#468
Migrated issue, originally created by Michael Bayer (@zzzeek)
Step 1, env.py:
step 2:
migration file has:
now remove the table:
run again:
migration file is missing the index:
we need to generate MigrateTableOps for tables that are removed during autogenerate.
The text was updated successfully, but these errors were encountered: