Squashed migration is not marked as unapplied
When unapplying a squashed migration and the replaced migration files are still around, the MigrationExecutor mark the squash migration as unapplied, too, not only the replaced migrations.
Change History
(10)
| Triage Stage: |
Unreviewed → Accepted
|
| Description: |
modified (diff)
|
| Summary: |
MigrationExecutor.check_replacements() doesn't take care of unapplied migrations → Squashed migration is not marked as unapplied
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Patch needs improvement: |
set
|
| Triage Stage: |
Ready for checkin → Accepted
|
| Has patch: |
unset
|
| Patch needs improvement: |
unset
|
| Has patch: |
set
|
| Patch needs improvement: |
set
|
| Owner: |
changed from nobody to Jacob Walls
|
| Patch needs improvement: |
unset
|
| Status: |
new → assigned
|
| Triage Stage: |
Accepted → Ready for checkin
|
| Resolution: |
→ fixed
|
| Status: |
assigned → closed
|
While working on #24800 I realized that the issue is actually not fully correct. The squashed migration is not marked as applied.