thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.11_rc1 2011-12-23T19:08:34Z 2011-12-23T19:08:34Z Thomas Jost schnouki@schnouki.net 2011-12-13T17:11:41Z urn:sha1:824dad76b6ae4a7e4a3ca41991af8e7d67f4cfd5 Commit 567bcbc2 introduced two new values for each message (content of the "From" and "Subject" headers), but the comments about the database schema had not been updated accordingly. 2011-12-21T11:32:16Z David Edmondson dme@dme.org 2011-12-20T15:20:04Z urn:sha1:77ec8108a10a8d372bed6298e22c89d7de651577 Cast away the result of various *write functions. Provide a default value for some variables to avoid "use before set" warnings. 2011-12-05T02:00:25Z David Bremner bremner@debian.org 2011-12-04T19:20:39Z urn:sha1:69dc421ab3355930f23ec6aa47e7e936cbfafb97 We want to make sure g_type_init is called before any GObject functionality is used. 2011-11-14T21:10:58Z Austin Clements amdragon@MIT.EDU 2011-11-06T17:17:36Z urn:sha1:567bcbc294b3aed632d18eb22056840292bdeb1e This is a rebase and cleanup of Istvan Marko's patch from id:m3pqnj2j7a.fsf@zsu.kismala.com Search retrieves these headers for every message in the search results. Previously, this required opening and parsing every message file. Storing them directly in the database significantly reduces IO and computation, speeding up search by between 50% and 10X. Taking full advantage of this requires a database rebuild, but it will fall back to the old behavior for messages that do not have headers stored in the database. 2011-11-02T23:38:22Z David Bremner bremner@debian.org 2011-10-28T14:56:30Z urn:sha1:606e4461f803829077af4e3b2579583f7e39bc3e Apparently the method was renamed in Xapian 1.1.0 but the old method name will stay around for a while. It seems better to stick with the old name to make notmuch compile with older versions of Xapian, at least for now. 2011-10-31T02:09:49Z David Bremner bremner@debian.org 2011-10-23T15:05:13Z urn:sha1:1dedfc90f6eee7cad10f1a1ceb39a7a1c4dbd1b1 We keep the lib/xutil.c version. As a consequence, also factor out _internal_error and associated macros. It might be overkill to make a new file error_util.c for this, but _internal_error does not really belong in database.cc. 2011-10-04T04:55:29Z Ali Polatel alip@exherbo.org 2011-10-04T04:55:29Z urn:sha1:02a30767116ad8abcbd0a3351f2e4d43bbbd655f Previously, the functions notmuch_database_find_message() and notmuch_database_find_message_by_filename() functions did not properly report error condition to the library user. For more information, read the thread on the notmuch mailing list starting with my mail "id:871uv2unfd.fsf@gmail.com" Make these functions accept a pointer to 'notmuch_message_t' as argument and return notmuch_status_t which may be used to check for any error condition. restore: Modify for the new notmuch_database_find_message() new: Modify for the new notmuch_database_find_message_by_filename() 2011-10-04T04:39:57Z Ali Polatel alip@exherbo.org 2011-10-03T20:27:32Z urn:sha1:9b3f16ce715d2371224955bc5b6f948eaa4ee325 notmuch_database_remove_message() must call notmuch_message_destroy() once it is done handling message removal. 2011-09-24T23:00:28Z Austin Clements amdragon@mit.edu 2011-06-11T04:42:58Z urn:sha1:51c3c0b2d27c8d0ba8e1ae242fd907c59f82d992 Adding a message may involve changes to multiple database documents, and thus needs to be done in a transaction. This makes add_message (and, I think, the whole library) atomicity-safe: library callers only needs to use atomic sections if they needs atomicity across multiple library calls. 2011-09-24T23:00:28Z Austin Clements amdragon@mit.edu 2011-06-11T04:19:31Z urn:sha1:7a8046ced8c0e61ddd0ff463cfc17ed63e6edad3 notmuch_database_find_message_by_filename is mostly stolen from notmuch_database_remove_message, so this patch also vastly simplfies the latter using the former. This API is also useful in its own right and will be used in a later patch for eager maildir flag synchronization.