Opened 9 years ago
Last modified 3 years ago
#25255 closed Bug
Squashed migration is not marked as unapplied — at Version 2
| Reported by: | Markus Holtermann | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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 (2)
comment:1 by , 9 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | MigrationExecutor.check_replacements() doesn't take care of unapplied migrations → Squashed migration is not marked as unapplied |
Note:
See TracTickets
for help on using tickets.
While working on #24800 I realized that the issue is actually not fully correct. The squashed migration is not marked as applied.