#28862: Removing a field from index_together and from the model generates a
migration that crashes
-------------------------------------+-------------------------------------
Reporter: Artem Maslovskiy | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution:
Keywords: models migrations | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tomer Chachamu):
We have a test that says the generated migrations are in said order:
https://github.com/django/django/blob/6c0042430e3618ce5c276d195d92a6b884daa3a3/tests/migrations/test_autodetector.py#L1323
The docstring is incorrect, it says "Removed fields will be removed after
updating index/unique_together." but the test actually checks for "Removed
fields will be removed before updating index/unique_together."
--
Ticket URL: <https://code.djangoproject.com/ticket/28862#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.5de5e30863ec18583d83aece3ece2106%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
