#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
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"daba609a9bdc7a97bcf327c7ba0a5f7b3540b46e" daba609a]:
{{{#!CommitTicketReference repository=""
revision="daba609a9bdc7a97bcf327c7ba0a5f7b3540b46e"
Fixed #35877, Refs #36128 -- Documented unique constraint when migrating a
m2m field to use a through model.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35877#comment:16>
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/010701999442e363-8d5bc615-c087-4f69-904c-1f7fd0321a1f-000000%40eu-central-1.amazonses.com.
