Opened 13 years ago
Last modified 6 years ago
#17345 new New feature
Allow ordering override on ManyToManyField
Reported by: | FunkyBob | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Normal | Keywords: | m2m, ordering |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | How to create a pull request | ||
Description ¶
In conjunction with #17344, discussion with SmileyChris revealed it may be useful, too, to allow to specify an ordering on a m2m field directly, allowing it to override the default ordering of the related model.
We may also need to add a reverse_ordering to specify the ordering of this model from the PoV of the related model.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (2)
comment:1 by , 13 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 6 years ago
Version: | 1.3 → master |
---|
Note:
See TracTickets
for help on using tickets.