debian/notmuch
1
0
Fork 0
mirror of https://git.notmuchmail.org/git/notmuch synced 2024-12-22 17:34:54 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

TODO: Note several changes we want to make to the database schema.

Browse source 
Since database upgrades can be fairly painful, we'll want to do all of
these within a single release.
This commit is contained in:
Carl Worth 2010-04-13 08:09:12 -07:00
parent 14073b8851
commit 22d117d144
1 changed files with 17 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
TODO
View file

@ -152,8 +152,6 @@ Fix to use the *last* Message-ID header if multiple such headers are
encountered, (I noticed this is one thing that kept me from seeing the encountered, (I noticed this is one thing that kept me from seeing the
same message-ID values as sup). same message-ID values as sup).
Add support for the user to specify custom headers to be indexed.
Add support for configuring "virtual tags" which are a tuple of Add support for configuring "virtual tags" which are a tuple of
(tag-name, search-specification). The database is responsible for (tag-name, search-specification). The database is responsible for
ensuring that the virtual tag is always consistent. ensuring that the virtual tag is always consistent.
@ -187,6 +185,23 @@ notmuch searches. Here was one proposal made in IRC:
Provide a ~me Xapian synonym for all of the user's configured email Provide a ~me Xapian synonym for all of the user's configured email
addresses. addresses.
Database changes
----------------
Store a reference term for every message-id that appears in
References. We just started doing this for newly-added documents, but
at the next convenient database-schema upgrade, we should go back and
fix old messages to be consistent.
Start indexing the List-Id header, (and re-index this header for
existing messages at the next database upgrade).
Start indexing the message file's directory ana make it available for
search as "folder:" (and re-index this value for existing messages at
the next database upgrade).
Add support for the user to specify custom headers to be indexed (and
re-index these for existing messages at the next database upgrade).
Test suite Test suite
---------- ----------
Achieve 100% test coverage with the test suite. Achieve 100% test coverage with the test suite.