#10784: list_editable will not work for the default ordering field.
----------------------------------------------+-----------------------------
          Reporter:  andreplebl...@gmail.com  |         Owner:  nobody
            Status:  reopened                 |     Milestone:  1.1   
         Component:  django.contrib.admin     |       Version:  SVN   
        Resolution:                           |      Keywords:        
             Stage:  Unreviewed               |     Has_patch:  0     
        Needs_docs:  0                        |   Needs_tests:  0     
Needs_better_patch:  0                        |  
----------------------------------------------+-----------------------------
Changes (by Will Hardy):

  * milestone:  => 1.1

Comment:

 Putting this under the 1.1 milestone... sorry core developers :-(

 It will come up anytime someone uses `list_editable` to edit a non-unique
 field which determines the ordering of objects. Despite what Karen wrote
 in the django-developers thread for #10922, I have the impression that
 this is a pretty common way to implement manual object ordering, and
 `list_editable` would be a great way to control it from the admin.

 If it can't be fixed, we should at least add an admin validation, which
 throws an error when any non-unique field is listed in list_editable and
 determines the default ordering. Failing that, a little bit of
 documentation on the issue.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/10784#comment:8>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to