#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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"290fd5ecece400490ad6bb557720d3b76f647eaf" 290fd5ec]:
{{{
#!CommitTicketReference repository=""
revision="290fd5ecece400490ad6bb557720d3b76f647eaf"
[4.2.x] Fixed #34529, Refs #34525 -- Reduced index operations with
Meta.indexes/index_together when optimizing migrations.
This makes squashing migrations an available path for changing
Meta.index_together, which is deprecated, to Meta.indexes.
Follow up to f81032572107846922745b68d5b7191058fdd5f5.
Backport of 8e2460d599aec95f8cfe514d3cc8acdd4ca4b1fb from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/34525#comment:21>
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/01070187e14e9c1d-3c19e335-1a7f-4f4a-99ee-a44ade3f1178-000000%40eu-central-1.amazonses.com.
