unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: feature request: caching message arrival time
Date: Sat, 01 Jun 2019 11:13:25 -0300	[thread overview]
Message-ID: <874l59qtq2.fsf@tethera.net> (raw)
In-Reply-To: <8736kuhtky.fsf@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

>  * i don't think we have a way to search properties by range (e.g. the
>    way that we can search date ranges).  i don't need that feature for
>    my use case, but maybe someone will come up with a use case that
>    wants it?  is there a way to store the datestamp in a way that it can
>    be scanned the way that "date" can?  or do we already have this and
>    i'm just unaware?

you'd need to use a value slot to get (native Xapian) range
searches. To quote the xapian docs

      For performance it is important to keep the amount of data stored
      in the values to a minimum, since the values for a large number of
      documents may be read during the search - the more data that has
      to be read, the slower the search will be.

So it's definitely something that would need to be profiled.

Probably the patches that added lastmod: are a good example for someone
wanting to investigate this.

  reply	other threads:[~2019-06-01 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-01  3:29 feature request: caching message arrival time Daniel Kahn Gillmor
2019-06-01 14:13 ` David Bremner [this message]
2019-06-01 14:19 ` Ralph Seichter
2019-06-01 15:30   ` Daniel Kahn Gillmor
2019-06-03  8:57     ` Örjan Ekeberg
2019-06-03 13:17       ` Daniel Kahn Gillmor
2019-06-03 14:02         ` Ralph Seichter
2019-06-03 22:16           ` Daniel Kahn Gillmor
2019-06-03 16:02         ` Örjan Ekeberg
2019-06-03 22:21           ` Daniel Kahn Gillmor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874l59qtq2.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).