aboutsummaryrefslogtreecommitdiff
path: root/lib/database.cc
diff options
context:
space:
mode:
authorAustin Clements <amdragon@mit.edu>2014-10-23 08:30:34 -0400
committerDavid Bremner <david@tethera.net>2014-10-25 19:26:03 +0200
commitd9f5da00bb7707f3244654b4e44df2284e3634be (patch)
treed95224e769ab326032aa48db68f68a0c0bdb23cc /lib/database.cc
parent1cdb96d3c4a2fc5ddf3a6e5c73c59c0f0e65cae2 (diff)
lib: Update database schema doc for ghost messages
This describes the structure of ghost mail documents. Ghost messages are not yet implemented.
Diffstat (limited to 'lib/database.cc')
-rw-r--r--lib/database.cc20
1 files changed, 18 insertions, 2 deletions
diff --git a/lib/database.cc b/lib/database.cc
index 8fd7fad6..c641bcde 100644
--- a/lib/database.cc
+++ b/lib/database.cc
@@ -50,8 +50,8 @@ typedef struct {
/* Here's the current schema for our database (for NOTMUCH_DATABASE_VERSION):
*
- * We currently have two different types of documents (mail and
- * directory) and also some metadata.
+ * We currently have three different types of documents (mail, ghost,
+ * and directory) and also some metadata.
*
* Mail document
* -------------
@@ -109,6 +109,15 @@ typedef struct {
*
* The data portion of a mail document is empty.
*
+ * Ghost mail document [if NOTMUCH_FEATURE_GHOSTS]
+ * -----------------------------------------------
+ * A ghost mail document is like a mail document, but where we don't
+ * have the message content. These are used to track thread reference
+ * information for messages we haven't received.
+ *
+ * A ghost mail document has type: ghost; id and thread fields that
+ * are identical to the mail document fields; and a MESSAGE_ID value.
+ *
* Directory document
* ------------------
* A directory document is used by a client of the notmuch library to
@@ -172,6 +181,13 @@ typedef struct {
* generated is 1 and the value will be
* incremented for each thread ID.
*
+ * Obsolete metadata
+ * -----------------
+ *
+ * If ! NOTMUCH_FEATURE_GHOSTS, there are no ghost mail documents.
+ * Instead, the database has the following additional database
+ * metadata:
+ *
* thread_id_* A pre-allocated thread ID for a particular
* message. This is actually an arbitrarily large
* family of metadata name. Any particular name is