#28624: Add attribute to let a ManyToMany field behave like a list instead of a
set
-------------------------------------+-------------------------------------
Reporter: david simmen | Owner: david
| simmen
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Hello David, what's the purpose of disabling this constraint?
Isn't something you can achieve by defining a through model without a
`unique_together` constraint? I'm not convinced this is a scenario common
enough to warrant yet another option to `ManyToManyField`.
--
Ticket URL: <https://code.djangoproject.com/ticket/28624#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c7a1a1325e13c2e948924538efcf4499%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
