Noop the 0008 and conditional the 0009 migration
We removed a column in the same release that we removed it from the model. This creates a gap where the code still looks for a column which has been dropped until the new code has been deployed. The initial fix was to put the column back, but that creates a window during the alterations where views will error. This noops the 0008 migration and effectively noops 0009 unless you've run the old migration.
Showing
Please
register
or
sign in
to comment