#27004 closed Bug (fixed)
InconsistentMigrationHistory has false positives with squashed migrations
| Reported by: | Jarek Glowacki | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.10 |
| Severity: | Release blocker | Keywords: | InconsistentMigrationHistory squashed migrate |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
a -> b -> c a_sq_b
Migrations a, b, c applied. a_sq_b not.
When graph is built, since a and b are applied, a_sq_b replaces them and becomes c's dependency. However this means that a_sq_b is unapplied while c is. This results in an InconsistentMigrationHistory error when you try to run migrations...
Looks like the results of #25850.
Unless I'm mistaken this seems like quite a critical error..
Change History (5)
comment:1 by , 9 years ago
| Has patch: | set |
|---|
comment:2 by , 9 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 9 years ago
| Severity: | Normal → Release blocker |
|---|
Note:
See TracTickets
for help on using tickets.
https://github.com/django/django/pull/7013