#34525: index_together warning after migration to new style
-------------------------------------+-------------------------------------
Reporter: Mateusz Legięcki | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: index_together, | Triage Stage: Accepted
warning |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* stage: Unreviewed => Accepted
Comment:
I'm able to reproduce the warning using latest `main` and the Django test
framework. But removing the migrations from the test repo and starting
fresh does not raise the warning (as expected).
Thank you Tim for the pointer to the release notes, while it's true
nothing is said about supporting `index_together` in older migrations,
IMHO it would be ideal if the `RemovedInDjango51Warning` is not emitted
for code bases that were already migrated out of the deprecated feature.
I'm not familiar with migrations but I think this is a valid report,
accepting (at least until with more experience in this topic decides
otherwise).
--
Ticket URL: <https://code.djangoproject.com/ticket/34525#comment:5>
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/01070187c8652418-9a7f2e6c-47fb-4596-947c-dc388dcdfca5-000000%40eu-central-1.amazonses.com.
