summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
6e9fdf0)
Maybe ths lack of this documentation is why I forgot we were actually
storing this and wrote the ugly code to fetch In-Reply-To from message
files rather than from the database.
* Mail document
* -------------
* A mail document is associated with a particular email message file
* Mail document
* -------------
* A mail document is associated with a particular email message file
- * on disk. It is indexed with the following prefixed terms:
+ * on disk. It is indexed with the following prefixed terms which the
+ * database uses to construct threads, etc.:
*
* Single terms of given prefix:
*
*
* Single terms of given prefix:
*
*
* thread: The ID of the thread to which the mail belongs
*
*
* thread: The ID of the thread to which the mail belongs
*
+ * replyto: The ID from the In-Reply-To header of the mail (if any).
+ *
* Multiple terms of given prefix:
*
* reference: All message IDs from In-Reply-To and Re ferences
* Multiple terms of given prefix:
*
* reference: All message IDs from In-Reply-To and Re ferences
*
* MESSAGE_ID: The unique ID of the mail mess (see "id" above)
*
*
* MESSAGE_ID: The unique ID of the mail mess (see "id" above)
*
+ * In addition, terms from the content of the message are added with
+ * "from", "to", "attachment", and "subject" prefixes for use by the
+ * user in searching. But the database doesn't really care itself
+ * about any of these.
+ *
* Timestamp document
* ------------------
* A timestamp document is used by a client of the notmuch library to
* Timestamp document
* ------------------
* A timestamp document is used by a client of the notmuch library to