#26180: Altering unique_together still sometimes missing deleted fields
-------------------------------+------------------------------------
Reporter: julianandrews | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by akki):
The patch temporarily fixes the issue (attaching for anyone who gets stuck
due to this bug) but some other edge cases would still get left. The
actual fix would involve some changes in `migrations.optimizer` or the
`reduce` methods of `AlterUniqueTogether` or `RemoveField` operations
AFAICS.
--
Ticket URL: <https://code.djangoproject.com/ticket/26180#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/071.4ec7f5e41d8c8a24cb582feedf9cf621%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
