| Summary | search results problem |
| Queue | IMP |
| Queue Version | 3.2.6 |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | mcaplin (at) miami (dot) edu |
| Created | 10/18/2004 (7712 days ago) |
| Due | |
| Updated | 11/12/2004 (7687 days ago) |
| Assigned | 11/02/2004 (7697 days ago) |
| Resolved | 11/12/2004 (7687 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
since it would require a complete rewrite of the message indexing
accessing in all of IMP. This took quite a while when we did it in
HEAD and is not easily backported due to the drastic differences
between HEAD and IMP 3.x.
State ⇒ Assigned
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ search results problem
Queue ⇒ IMP
When searching a few mailboxes, if the search results include duplicate
message numbers (for example: message 3 of mailbox2 and message 3 of
mailbox3), only the latter is displayed. I did some debugging and saw
that $sorted in mailbox.php contains the complete search results but after
$sortedIds = array_flip($sorted); [line 599 of mailbox.php]
$sortedIds (which I believe is used to create the display) is missing one
of the "duplicate" message Ids. Also, the resulting page will have
something like "1 to 16 of 16 messages" but only 15 messages are listed.
Could you use a compound key (maybe folder_index.message_id or some format
that includes the mailbox) for $sortedIds so this will not happen?