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 |
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.
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.