#3264 closed defect (duplicate)
[patch] object_list in archive_year view always contains items in ascending order
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Generic views | Version: | dev |
| Severity: | normal | Keywords: | archive_year object_list order ordering |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
When the keyword make_object_list is True (see #697), object_list contains items in ascending order and 'ordering' option in class Meta has no effect.
Attachments (1)
Change History (4)
by , 18 years ago
| Attachment: | respect_model_ordering.diff added |
|---|
comment:1 by , 18 years ago
See #3134 where another solution is proposed, would you mind writing a small comparison of both patches so the people with SVN commiting powers can review it and decide if/what to implement in trunk?. I don´t dare to mark one of both tickets as duplicate of the other because it will close it in the process.
comment:2 by , 18 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
I'm marking this as a duplicate of #3134, as I think that is the better solution.
To compare the two: this patch changes the archive_year view to use the model's default ordering (thus changing the behaviour of the view); the patch at #3134 offers an optional parameter to specify ordering, defaulting to the current behaviour if left blank. The latter patch also updates the docs.
#3134 is missing unit tests though; unless anyone else provides them first I will add them when I can.
respect ordering specified in the model