notmuch/lib/database.cc, branch 0.1

Add is: as a synonym for tag: in search terms.

2010-03-10T00:03:58Z

I like the readability of this, it provides compatibility with people trained in this syntax by sup, and it even saves one character.

lib: Rename iterator functions to prepare for reverse iteration.

2010-03-09T17:22:29Z

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'.

Fix printf for when uint64_t != unsigned long long int

2010-02-09T19:14:16Z

Thanks to Michal Sojka for pointing out the correct fix, which I verified in the freely-available WG14/N1124 draft (from the C99 working group) which is available here: http://www.open-std.org/JTC1/SC22/wg14/www/docs/n1124.pdf

Switch from random to sequential thread identifiers.

2010-02-09T19:14:11Z

The sequential identifiers have the advantage of being guaranteed to be unique (until we overflow a 64-bit unsigned integer), and also take up half as much space in the "notmuch search" output (16 columns rather than 32). This change also has the side effect of fixing a bug where notmuch could block on /dev/random at startup (waiting for some entropy to appear). This bug was hit hard by the test suite, (which could easily exhaust the available entropy on common systems---resulting in large delays of the test suite).

notmuch new: Print upgrade progress report as a percentage.

2010-01-10T01:38:23Z

Previously we were printing a number of messages upgraded so far. The original motivation for this was to accurately reflect the fact that there are two passes, (so each message is processed twice and it's not accurate to represent with a single count). But as it turns out, the second pass takes zero time (relatively speaking) so we're still not accounting for it. If nothing else, the percentage-based reporting makes for a cleaner API for the progress_notify function.

lib: Split the database upgrade into two phases for safer operation.

2010-01-09T19:13:12Z

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.

lib: Delete stale timestamp documents during database upgrade.

2010-01-08T17:57:09Z

Once we move the timestamp to the new directory document, we don't need the old one anymore.

notmuch new: Fix progress notification on database upgrade.

2010-01-08T05:24:44Z

This was firing continuously rather than just once per second as intended.

lib: Implement versioning in the database and provide upgrade function.

2010-01-08T02:26:31Z

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

Prefer READ_ONLY consistently over READONLY.

2010-01-07T18:29:05Z

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.