#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: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* status: new => closed
* resolution: => wontfix
Comment:
A list isn't appropriate because the database wouldn't preserve ordering
of many-to-many relations.
Maybe [https://pypi.python.org/pypi/django-sortedm2m django-sortedm2m]
would be appropriate for your use case.
To revisit a "wontfix" decision, see
TicketClosingReasons/DontReopenTickets.
By the way, the `add()`, `create()`, etc. limitation of using a `through`
model will be lifted when #9475 is completed.
--
Ticket URL: <https://code.djangoproject.com/ticket/28624#comment:4>
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.224fcaee8ee27d9b9ab6c52a745fa61d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
