Alembic.command.check (v.1.9.0) #1179
-
Hello, My team has a few redundant operations in the revision history of some our projects. I'd like to remove them since it is conflicting with the adoption of a naming convention but have encountered some unexpected errors. For example, Here we have the addition and removal of the same foreign key on two different tables. My expectation was that the "sum" of these operations would not count as a pending upgrade operation. This is because when I try to generate a migration with Flask-Migrate for these pending upgrade operations, there are no changes in the schema detected: Is this expected behaviour for the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
the check command should produce the same result as a plain autogenerate command, they run the same comparison routine. there is also no consideration of actual upgrade operations during autogenerate or check, it strictly looks at the MetaData collection passed and compares its contents to what reflection sees. |
Beta Was this translation helpful? Give feedback.
the check command should produce the same result as a plain autogenerate command, they run the same comparison routine. there is also no consideration of actual upgrade operations during autogenerate or check, it strictly looks at the MetaData collection passed and compares its contents to what reflection sees.