#28366: AlterUniqueTogether and RemoveField on same field lead to migration
error
-------------------------------------+-------------------------------------
Reporter: Rhaskaas | Owner: nobody
Type: Bug | Status: new
Component: | Version: 1.11
Migrations | Keywords: AlterUniqueTogether
Severity: Normal | RemoveField migrate makemigrations
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Consider a model with a field who's used in unique_together.\\
You want to remove this field and so change the uniquet_together Meta at
the same time (in models.py).
When you do this and apply "makemigrations", the resulting migration file
is not usable.\\
Indeed, "migrations.RemoveField" is use "before
migrations.AlterUniqueTogether" and lead to
"django.core.exceptions.FieldDoesNotExist" error.\\
If you change order manualy in migration file (i.e. alter first and remove
after) there is no more problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/28366>
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/051.1655e4e3fc67c3d3f4831fbbb7e3776a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
