GNOME Bugzilla – Bug 713150
Represent conversations in the database
Last modified: 2021-07-05 13:27:38 UTC
---- Reported by chaz@yorba.org 2013-06-06 16:09:00 -0700 ---- Original Redmine bug id: 7050 Original URL: http://redmine.yorba.org/issues/7050 Searchable id: yorba-bug-7050 Original author: Charles Lindsay Original description: A performance problem with searching (and Geary in general) is that it's slow to pull out messages for full conversations, taking upwards of a half a second in the search folder for example. Our current method of associating by Message-Id on the fly isn't scaling well. Instead, we should add some infrastructure so we can instantly determine what conversation a message belongs to. This might consist of a Conversations table that acts as the bridge between the many to many relationship of message row ids and Message-IDs in each conversation, and one table for each end of that relationship. There may be simpler ways of representing this too, so we should discuss before going forward. Not only does this involve setting up the infrastructure and keeping the tables consistent, but also making use of this in the local search methods for full conversations. The ultimate goal is to have an O(1) database lookup when building full conversations. Related issues: related to geary - 7049: limit search results from database (Fixed) ---- Additional Comments From geary-maint@gnome.bugs 2013-09-04 17:44:00 -0700 ---- ### History #### #1 Updated by Charles Lindsay 6 months ago * **Description** updated (diff) #### #2 Updated by Jim Nelson 6 months ago * **Priority** changed from _Normal_ to _High_ #### #3 Updated by Jim Nelson 3 months ago * **Target version** changed from _0.4.0_ to _0.5.0_ --- Bug imported by chaz@yorba.org 2013-11-21 20:19 UTC --- This bug was previously known as _bug_ 7050 at http://redmine.yorba.org/show_bug.cgi?id=7050 Unknown milestone "unknown in product geary. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/geary/-/issues/ Thank you for your understanding and your help.