GNOME Bugzilla – Bug 554455
"Advanced search -> Include threads" does not work
Last modified: 2008-10-22 04:18:58 UTC
evolution 2.23.92 openSUSE 11.1 beta 1 x86_64 "Advanced search -> Include threads" does nor work I tried to create Advanced search and virtual folder "Threads I participate on": Advanced search -> Include threads -> All related Sender -> Contains -> sbrabec It seems that "Advanced search -> Include threads -> All related" does nor work and behaves like "Include threads -> None". Marking as Major: This feature saves a lot of time when searching for answers to my mails in high traffic mailing lists. Related: bug 503013 (feature request for tools to manipulate high traffic mailing lists)
Note that it is a regression: It works well in evolution-2.22.1.1
Yep, it is known, not to work with disk summary branch. Hmm, I can make it fallback to old in-memory search model, for thread-based-searches. I have heard this from more people. I should fix this up asap.
+1 from me for fixing this ASAP. I depend on this feature a lot to the point that I'll rather continue to use 2.22.x instead of upgrading.
Created attachment 120089 [details] [review] Proposed patch This will make the code fallback to old search model for thread search. With this even vfolders must work.
Created attachment 120263 [details] [review] evolution-data-server-thread-search.patch As attached patch did not fit on 2.24.0, I tried to backport it. I can confirm, that attachec patch works.
The stable code base for 2.24.1 is changed and the patch I had attached was for that :-) Anyways thanks for the test. I will commit it asap for 2.24.1 which we would be picking for code-11
fixed to stable/trunk. Should be there in 2.24.1
*** Bug 557020 has been marked as a duplicate of this bug. ***
I built a modified version of Fedora's evolution-data-server-2.24.0-1.fc9 with the patch from comment #5 (posted at http://mattmccutchen.net/rpm/), but the problem is not fixed. I guess I will try to either fix the backport or rebuild with the tagged evolution-data-server 2.24.1 code.
Actually, the problem seems not to be completely fixed in the trunk; see bug 557348.
Matt, its about the expression, not refreshing the cache. I would fix it.