#36128: Document the necessity of adding unique constraints to related models in
intermediary m2m model.
-------------------------------------+-------------------------------------
Reporter: Guillaume LEBRETON | Owner: Clifford
| Gama
Type: Bug | Status: closed
Component: Documentation | Version: 5.1
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:"6f3813e4b6e3db7fa3cc612c78f898142468bca9" 6f3813e4]:
{{{#!CommitTicketReference repository=""
revision="6f3813e4b6e3db7fa3cc612c78f898142468bca9"
[5.2.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/36128#comment:15>
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/0107019994461a66-68deec20-439f-4731-ac21-3945728b04d8-000000%40eu-central-1.amazonses.com.
