#23378 closed Bug (fixed)
No migration detected when adding index_together
| Reported by: | Markus Amalthea Magnuson | Owned by: | nobody |
|---|---|---|---|
| Component: | Migrations | Version: | 1.7-beta-2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I have a model that has previous migrations. The only change I make is adding an index_together meta option to the model, specifying two of its fields in a tuple/list. Then running ./manage.py makemigrations will not pick up this index change, just printing "No changes detected". Doing the same thing but using unique_together will be picked up and create a migration.
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I can reproduce this using beta2 but the problem has been fixed in more recent releases.
The fix came with the autodetector rewrite: 31fc34e447137631e6ea58fc33f3642e65479472.
Thanks.
comment:3 by , 10 years ago
Yes, I was on the beta, in which I can reproduce this but not in rc3.
Sorry for the noise before testing on latest.
Note:
See TracTickets
for help on using tickets.
Are you using beta 2 as indicated by "Version" instead of RC3? I couldn't reproduce the issue.