Opened 10 years ago

Closed 6 years ago

#10720 closed New feature (wontfix)

OrderedManyToMany API Implementation

Reported by: Aryeh Leib Taurog <vim@…> Owned by: nobody
Component: Database layer (models, ORM) Version: master
Severity: Normal Keywords: Ordered ManyToMany
Cc: gregor@… Triage Stage: Design decision needed
Has patch: yes Needs documentation: yes
Needs tests: yes Patch needs improvement: no
Easy pickings: no UI/UX: no


In response to my post on django-users, Russ Magee suggested I open a ticket.

This patch uses the standard python list interface to provide a very simple
API for keeping a singly-ordered many-to-many relation field.

More info, plus a simple example and unit-tests here:

Attachments (1)

patch_for_django_rev-10131.diff (25.3 KB) - added by Aryeh Leib Taurog <vim@…> 10 years ago.
Provides OrderedManyToManyField with convenient API

Download all attachments as: .zip

Change History (8)

Changed 10 years ago by Aryeh Leib Taurog <vim@…>

Provides OrderedManyToManyField with convenient API

comment:1 Changed 10 years ago by Dennis Kaarsemaker

Needs documentation: set
Needs tests: set

comment:2 Changed 9 years ago by Alex Gaynor

Triage Stage: UnreviewedDesign decision needed

comment:3 Changed 9 years ago by Gregor Müllegger

Cc: gregor@… added

I have implemented an ordered m2m relation in a reusable app. Its not exactly the same approach you wanted to take like you described in your blog post but maybe a starting point.

Have a look here:

Or start hacking and make the API the way you want by branching the code from launchpad:

bzr branch lp:django-sorted-m2m-field

comment:4 Changed 8 years ago by Chris Beaven

Severity: Normal
Type: New feature

comment:5 Changed 7 years ago by Aymeric Augustin

UI/UX: unset

Change UI/UX from NULL to False.

comment:6 Changed 7 years ago by Aymeric Augustin

Easy pickings: unset

Change Easy pickings from NULL to False.

comment:7 Changed 6 years ago by Anssi Kääriäinen

Resolution: wontfix
Status: newclosed

This can be implemented externally, and the demand isn't big enough to include this in core. This doesn't seem to be something that most projects need.

Closing as wontfix.

Note: See TracTickets for help on using tickets.
Back to Top