#389 closed enhancement (invalid)
[patch] admin interface only sorts by first ordering field
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | contrib.admin | Version: | |
| Severity: | normal | Keywords: | ordering |
| Cc: | dcf@… | Triage Stage: | Unreviewed |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I have added an ordering attribute to a model with two field names:
ordering = ["crate", "card"]
I find that get_list() on the model sorts by "crate", then "card", as I expect. However, when I look at the list of objects in the admin interface, it only sorts by "crate" and not both "crate" and "card".
Attachments (1)
Change History (7)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
| Summary: | admin interface only sorts by first ordering field → [patch] admin interface only sorts by first ordering field |
|---|
Added patch for this issue.
comment:3 by , 20 years ago
| Cc: | added |
|---|
comment:4 by , 20 years ago
| milestone: | → Version 1.1 |
|---|---|
| priority: | normal → low |
| Type: | defect → enhancement |
The added patch breaks the changelist view (in django.db.models.handle_legacy_ordering).
comment:5 by , 20 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
The patch still breaks the changelist view, and since it hasn't been updated I'm marking this INVALID.
Note:
See TracTickets
for help on using tickets.
I have encountered the same thing. I am using MySQL