Modify ↓
Opened 13 years ago
Closed 12 years ago
#10540 closed enhancement (fixed)
Allow __group__ reports to be sorted
| Reported by: | Christian Boos | Owned by: | Christian Boos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.0 |
| Component: | report system | Version: | |
| Severity: | normal | Keywords: | __group__ pagination |
| Cc: | osimons | Branch: | |
| Release Notes: |
TracReports using |
||
| API Changes: | |||
| Internal Changes: | |||
Description
This is a direct follow-up to #10530, targeted to 0.13dev.
The change aims at fixing the problem solved in r10923 in a more satisfying way:
- instead of disabling the sort by user selected column feature in case the report uses a
__group__, fix this feature by respecting the__group__ordering first, then sort by this user selected column, - the approach to paging done in #216 relied on a subquery, but in fact there's no guarantee that the order of the rows in the subquery is kept at the level of the main query… we should fix this by not using a subquery.
See the discussion there for full details.
There might be more discussion needed and follow-up changes, hence this ticket.
Attachments (1)
Change History (6)
by , 13 years ago
| Attachment: | 10530-support-SORT_COLUMN-in-__group__-reports-r10928.patch added |
|---|
comment:1 by , 13 years ago
| Owner: | set to |
|---|
comment:2 by , 12 years ago
| Keywords: | pagination added |
|---|---|
| Status: | new → assigned |
Branch rebased and applied in r11096.
In fact, I still need to update the 0.13/TracReports page as promised in the error hint in that code…
comment:3 by , 12 years ago
| Release Notes: | modified (diff) |
|---|
comment:4 by , 12 years ago
| Cc: | added |
|---|
comment:5 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Documented in 0.13/TracReports@3.
Note:
See TracTickets
for help on using tickets.
make it possible to specify where to insert the sort column