| Summary | Turba sort of search results and browse by many criteria |
| Queue | Turba |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | mhennessy (at) cloud9 (dot) net |
| Created | 04/01/2005 (7403 days ago) |
| Due | |
| Updated | 05/23/2006 (6986 days ago) |
| Assigned | 05/19/2005 (7355 days ago) |
| Resolved | 05/23/2006 (6986 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
What is the status of this bounty? Why the original patch wasn't accepted?
1. You need to read horde/docs/CODING_STANDARDS
2. The patch is out of date with CVS now and needs to be updated.
3. I don't see any place to affect more than the primary sort field,
though that could just be the lack of comments in whatever is going on
at the top of browse.php in the "Evaluate Sorting" block.
4. Why did you add multisort() instead of making sort() aware of
multiple sort fields?
5. If all this work is being done it's a shame not to use *any* of the
driver work for sorting, even if we can't do it for lastname sorts."
What is the status of this bounty? Why the original patch wasn't accepted?
this update need to function for?
Horde, and should not be specific to MySQL or to SQL at all. Thanks!
it, the original contributor responds, or someone else can submit a
patch.
this update need to function for?
State ⇒ Stalled
the original contributor responds, or someone else can submit a patch.
like it's still listed in the open bounties as well although it would
appear that another party chose to sponsor it.
We're willing to pay a bounty on it, but it looks like all
correspondence dropped on it in May.
State ⇒ Rejected
the search result sorting.
I agree; it would be good if it would be integrated into at least the
SQL drivers from which I know that they can natively do it.
non-wrapped lines?
takes over the main sort column and the previously selected ones act
as secondary sort columns.
on at the top of browse.php in the "Evaluate Sorting" block.
sort information. The sort info is stored in the $_SESSION. The array
structure should be documented.
multiple sort fields?
could be converted to a wrapper of multisort though.
the driver work for sorting, even if we can't do it for lastname
sorts.
I didn't try to implement it.
State ⇒ Feedback
1. You need to read horde/docs/CODING_STANDARDS
2. The patch is out of date with CVS now and needs to be updated.
3. I don't see any place to affect more than the primary sort field,
though that could just be the lack of comments in whatever is going on
at the top of browse.php in the "Evaluate Sorting" block.
4. Why did you add multisort() instead of making sort() aware of
multiple sort fields?
5. If all this work is being done it's a shame not to use *any* of the
driver work for sorting, even if we can't do it for lastname sorts.
State ⇒ Assigned
New Attachment: turba_browse_multiple-sorting[1].patch
New Attachment: turba_browse_multiple-sorting_files.tar.gz
New Attachment: turba_browse_multiple-sorting.patch
State ⇒ Accepted
Priority ⇒ 2. Medium
Version ⇒ HEAD
Priority ⇒ 3. High
State ⇒ New
Queue ⇒ Turba
Type ⇒ Enhancement
Summary ⇒ Turba sort of search results and browse by many criteria
sorted by many selectible criteria, not just one. I am willing to
sponsor this feature request and as such will pay a bounty. Please
e-mail me for more details. I have submitted this to the Turba 1.x
codebase queue because I need this feature to exist in 1.x.