#27236: Deprecate Model.Meta.index_together in favour of Model.Meta.indexes
-------------------------------------+-------------------------------------
Reporter: Akshesh Doshi | Owner: Olivier
Type: | Tabone
Cleanup/optimization | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: index_together | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Markus Holtermann):
While this is the one step of the deprecation process of `index_together`
there is currently no way to migrate an existing from `index_together` to
`indexes` w/o dropping and recreating indexes. Since removing and adding
an index can be a quite expensive operation, this is not an option to do
so for now.
The next step in the deprecation process needs to treat `indexes` and
`index_together` similarly in the sense that the latter is translated into
the former internally (inside the migration framework). Once this is done,
the deprecation of actually using `index_together` can start.
--
Ticket URL: <https://code.djangoproject.com/ticket/27236#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.a0d002aea48ad3193fdf1994b78a85a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
