thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.2 2010-03-09T17:22:29Z 2010-03-09T17:22:29Z Carl Worth cworth@cworth.org 2010-03-09T17:22:29Z urn:sha1:4e5d2f22db290a830c0267f34b519c6138af00ed We rename 'has_more' to 'valid' so that it can function whether iterating in a forward or reverse direction. We also rename 'advance' to 'move_to_next' to setup parallel naming with the proposed functions 'move_to_first', 'move_to_last', and 'move_to_previous'. 2010-01-09T19:13:12Z Carl Worth cworth@cworth.org 2010-01-09T19:13:12Z urn:sha1:d12801c8b4d04a50fcb912b75017244fb09658e8 The first phase copies data from the old format to the new format without deleting anything. This allows an old notmuch to still use the database if the upgrade process gets interrupted. The second phase performs the deletion (after updating the database version number). If the second phase is interrupted, there will be some unused data in the database, but it shouldn't cause any actual harm. 2010-01-08T02:26:31Z Carl Worth cworth@cworth.org 2010-01-08T02:26:31Z urn:sha1:909f52bd8c4bdfa11cd3e75e3d0959e0293689bd The recent support for renames in the database is our first time (since notmuch has had more than a single user) that we have a database format change. To support smooth upgrades we now encode a database format version number in the Xapian metadata. Going forward notmuch will emit a warning if used to read from a database with a newer version than it natively supports, and will refuse to write to a database with a newer version. The library also provides functions to query the database format version: notmuch_database_get_version to ask if notmuch wants a newer version than that: notmuch_database_needs_upgrade and a function to actually perform that upgrade: notmuch_database_upgrade 2010-01-07T18:29:05Z Carl Worth cworth@cworth.org 2010-01-07T18:29:05Z urn:sha1:807aef93d3bf02884f7a37b44b894c11d9e1df58 Previously we had NOTMUCH_DATABASE_MODE_READ_ONLY but NOTMUCH_STATUS_READONLY_DATABASE which was ugly and confusing. Rename the latter to NOTMUCH_STATUS_READ_ONLY_DATABASE for consistency. 2010-01-07T18:19:44Z Carl Worth cworth@cworth.org 2010-01-07T18:19:44Z urn:sha1:f93b7218c3e2d11c5b3cdd4c367a42ca7a7ede77 Previously, many checks were deep in the library just before a cast operation. These have now been replaced with internal errors and new checks have instead been added at the beginning of all top-levelentry points requiring a read-write database. The new checks now also use a single function for checking and printing the error message. This will give us a convenient location to extend the check, (such as based on database version as well). 2010-01-06T18:32:06Z Carl Worth cworth@cworth.org 2010-01-05T21:29:23Z urn:sha1:d807e28f43579ecc91aa40ae3e42760991c2f810 This new directory ojbect provides all the infrastructure needed to detect when files or directories are deleted or renamed. There's still code needed on top of this (within "notmuch new") to actually do that detection. 2010-01-06T18:32:05Z Carl Worth cworth@cworth.org 2009-12-21T23:09:56Z urn:sha1:498edff50373785c9dcc889d0fb6bc9bfc13dfcb The code to map a filename to a direntry is something that we're going to want in a future _remove_message function, so put it in a new function _notmuch_database_filename_to_direntry . 2010-01-06T18:32:05Z Carl Worth cworth@cworth.org 2009-12-21T20:08:46Z urn:sha1:1376a90db622b71e0997fca52c50ccf34faeed22 The library interface is unchanged so far, (still just notmuch_database_add_message), but internally, the old _set_filename function is now _add_filename instead. 2010-01-06T18:32:05Z Carl Worth cworth@cworth.org 2009-12-21T16:23:26Z urn:sha1:6ca6c089e9df7affe6bee0392197509a24ab2546 Instead of storing the complete message filename in the data portion of a mail document we now store a 'direntry' term that contains the document ID of a directory document and also the basename of the message filename within that directory. This will allow us to easily store multple filenames for a single message, and will also allow us to find mail documents for files that previously existed in a directory but that have since been deleted. 2010-01-06T18:32:05Z Carl Worth cworth@cworth.org 2009-12-21T16:14:52Z urn:sha1:84742d86ab2fd3e5b5b601f073351454b993575e Some pending commits want the _split_path functionality separate from mapping a directory to a document ID. The split_path function now returns the basename as well as the directory name.