Opened 13 years ago
Closed 13 years ago
#16947 closed Bug (duplicate)
wrong ordering of a column with list_editable
Reported by: | anonymous | Owned by: | nobody |
---|---|---|---|
Component: | contrib.admin | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | makovick | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When there are no ordering options specified in the request, the column with list_editable still behaves as if the table were sorted by the primary key. This causes the editable items being displayed in the wrong rows.
Tested with SQLite. A simple testcase is here:
https://sites.google.com/site/makovick/junkyard/testcase.tar.gz?attredirects=0&d=1
- http://localhost:8000/admin/testapp/configuration
- login as admin/admin
- see the Configuration table containing key/value pairs
- key 'zzz' is paired with value '999' but after clicking on 'zzz' one can see there is '555' as a value
Change History (2)
comment:1 by , 13 years ago
Cc: | added |
---|
comment:2 by , 13 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Thanks for the report. I think this is essentially the same issue as in #16819, so I'm closing this one as duplicate. The point is that some default ordering (probably by primary key) should systematically be enforced in the changelist.