Bring back the insert_thread_id function.
authorCarl Worth <cworth@cworth.org>
Thu, 22 Oct 2009 06:10:19 +0000 (23:10 -0700)
committerCarl Worth <cworth@cworth.org>
Thu, 22 Oct 2009 06:21:12 +0000 (23:21 -0700)
commitc58ee818b5e116d00172c8406149106c97c2e377
treed6c94c7e61a6dd31a38191f61297f5f19d76a352
parent6c5054ebee5beb72c22d91a57c66b8ecdc65f7bf
Bring back the insert_thread_id function.

We deleted this in favor of our fancy new thread_ids iterator
from the message object. But one of the previous callers of
insert_thread_id isn't using notmuch_message_t yet. I made
the mistake of thinking I could just call g_hash_table_insert
directly, but the problem was that nobody was splitting
up the thread_id string at its commas.

So with this, we were inserting bogus comma-separated IDs
into the hash table, so thread_id values were ballooning
out of control. Should be much better now.
database.cc