#35877: Documentation on "Changing a ManyToManyField to use a through model"
does
not respect database index
-------------------------------------+-------------------------------------
Reporter: robwa | Owner: Samriddha
Type: | Kumar Tripathi
Cleanup/optimization | Status: closed
Component: Documentation | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | 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 Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"956455dc8a8654bad1264c39d02bd5ffafc7733d" 956455dc]:
{{{#!CommitTicketReference repository=""
revision="956455dc8a8654bad1264c39d02bd5ffafc7733d"
[6.0.x] Fixed #35877, Refs #36128 -- Documented unique constraint when
migrating a m2m field to use a through model.
Backport of daba609a9bdc7a97bcf327c7ba0a5f7b3540b46e from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35877#comment:17>
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/0107019994451d87-7f88edb8-d3b2-4b83-b162-a19a9096bb7a-000000%40eu-central-1.amazonses.com.
