#34525: index_together warning after migration to new style
-------------------------------------+-------------------------------------
Reporter: Mateusz Legięcki | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Release blocker | Resolution: invalid
Keywords: index_together, | Triage Stage:
warning | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* needs_better_patch: 1 => 0
* has_patch: 1 => 0
* resolution: => invalid
* stage: Accepted => Unreviewed
Comment:
Deprecation warnings are not spurious as we will not support
`index_together` in migrations when the deprecation ends. You can squash
migrations (see #34529) or
[https://code.djangoproject.com/ticket/34525#comment:22 adjust them
manually] to get rid of `index_together`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34525#comment:23>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070187ea3a9ad2-dace8ee7-72c2-4e89-a02c-d6ca9d569b2c-000000%40eu-central-1.amazonses.com.
