#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: assigned
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Samriddha Kumar Tripathi):
I've submitted a PR that adds a documentation note clarifying the behavior
when switching from an implicit ManyToManyField to a custom through model.
It includes a recommendation to use UniqueConstraint to preserve
uniqueness.
I've unset the "patch needs improvement" flag and ensured all doc checks
pass.
Looking forward to feedback!
--
Ticket URL: <https://code.djangoproject.com/ticket/35877#comment:11>
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/0107019974f8e43e-89861f3e-1cd1-4e64-8997-a7ad2427f405-000000%40eu-central-1.amazonses.com.
