#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: Release blocker | Resolution: fixed
Keywords: index_together | Triage Stage: Ready for
| checkin
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"b44efdfe543c9b9f12690b59777e6b275cb08103" b44efdfe]:
{{{#!CommitTicketReference repository=""
revision="b44efdfe543c9b9f12690b59777e6b275cb08103"
Fixed #34856 -- Fixed references to index_together in historical
migrations.
While AlterUniqueTogether has been documented to be still allowed in
historical
migrations for the foreseeable future it has been crashing since
2abf417c815c20
was merged because the latter removed support for Meta.index_together
which the
migration framework uses to render models to perform schema changes.
CreateModel(options["unique_together"]) was also affected.
Refs #27236.
Co-authored-by: Simon Charette <[email protected]>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27236#comment:51>
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 visit
https://groups.google.com/d/msgid/django-updates/01070193d3d8573d-60a2d53a-d710-4683-87ab-a773b67db58d-000000%40eu-central-1.amazonses.com.
