#27236: Deprecate Model.Meta.index_together in favour of Model.Meta.indexes
-------------------------------------+-------------------------------------
Reporter: Akshesh Doshi | Owner: David
Type: | Wobrock
Cleanup/optimization | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: index_together | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Collin Anderson):
> "run only on unapplied migrations"
makes sense to me.
> "Ultimately they'll have to squash their migrations before 5.1 if they
want to avoid having their migration breaking"
The deprecation warning/check says "Support for it (except in historical
migrations) will be removed in Django 5.1", so that seems to say to me
that it _won't_ be removed for historical migrations, and I as a developer
don't need to worry about it for historical migrations.
I'm mostly just providing feedback here on the wording. If Django wants me
to do something to my project to fix this issue, it should tell me what I
should do (like squash, or is there an alternative migration operation
that I should use instead?). Or if I don't need to do anything then there
shouldn't be a warning.
--
Ticket URL: <https://code.djangoproject.com/ticket/27236#comment:32>
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/01070182036b931e-1733a29b-e1be-4fc4-a125-3d812aef2a2d-000000%40eu-central-1.amazonses.com.
