#28862: Removing a field from index_together/unique_together and from the model
generates a migration that crashes
-----------------------------------+------------------------------------
Reporter: Artem Maslovskiy | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: models migrations | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Changes (by Tim Graham):
* component: Database layer (models, ORM) => Migrations
* stage: Unreviewed => Accepted
Comment:
That test is from the ticket I was thinking of: #23614 (fixed in Django
1.7.2 and later). The comment isn't accurate because the order of
operations changed in 5c9c1e029d139bd3d5213804af2ed9f317cd0b86 (Django
1.9). That change in ordering looks incorrect.
--
Ticket URL: <https://code.djangoproject.com/ticket/28862#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.dc31e60ecf9740990de01024df09e40e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
