#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: Release blocker | 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
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Mariusz: the warning is shown every time the tests are run, and the
`index_together` is declared in the `0001_initial.py` migration. This may
be caused by the test database setup, when migrations are run, so perhaps
the answer to you question is "no" because the initial migration is being
applied in the test database. When running the dev server or other
operations (`makemigrations`, `migrate`, etc.), the warning is not
printed. This is why I did not consider it a release blocker, but a "nice
to have" (IMHO).
This happens for `4.2` and `main`, will check against `4.1` and report
back.
--
Ticket URL: <https://code.djangoproject.com/ticket/34525#comment:9>
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/01070187c8c2adee-a0c21b8a-36f3-4d02-8252-3107e150d95d-000000%40eu-central-1.amazonses.com.
