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
In case some of the migrations being squashed are already applied and some are not, post squashing there is no way to apply the missing parts of the squashed migration to the db (other than running the SQL manually of course) and typically will lead to errors in the next migration apply.
Describe the solution you'd like
Allow squashing migrations only if all the involved migrations are either applied or unapplied. In case an inconsistency is observed, raise a warning to the user mentioning the problem this would create. Also suggest the solution, ie. apply the unapplied migrations on the database before squashing. Allow the user to ignore the warning in case they know what they are doing and have reasons to do so
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered:
Is your proposal related to a problem?
In case some of the migrations being squashed are already applied and some are not, post squashing there is no way to apply the missing parts of the squashed migration to the db (other than running the SQL manually of course) and typically will lead to errors in the next migration apply.
Describe the solution you'd like
Allow squashing migrations only if all the involved migrations are either applied or unapplied. In case an inconsistency is observed, raise a warning to the user mentioning the problem this would create. Also suggest the solution, ie. apply the unapplied migrations on the database before squashing. Allow the user to ignore the warning in case they know what they are doing and have reasons to do so
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: