From: Jani Nikula <jani@nikula.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] TODO: date range queries - check
Date: Sun, 09 Dec 2012 00:32:18 +0200 [thread overview]
Message-ID: <87sj7gp43x.fsf@nikula.org> (raw)
In-Reply-To: <871uf0fdnh.fsf@servo.finestructure.net>
On Sat, 08 Dec 2012, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Sat, Dec 08 2012, David Bremner <david@tethera.net> wrote:
>> Patch? Concrete wording suggestion?
>
> How about:
>
> It would be nice to not require both endpoints to be specified in date
> searches. For example it would be nice to be able to say things like
> "date:2009-01-1", to specify a search over a particular day, or
> "since:'1 month' to specify an open-ended range, and have the other
> endpoint be implicit. To do any of this we're probably going to need to
> break down an write our own parser for the query string rather than
> using Xapian's QueryParser class.
FWIW, this means, in practice:
Make date:<expr> an alias for date:<expr>..<expr>
Make since:<expr> an alias for date:<expr>..
Make until:<expr> an alias for date:..<expr>
We'll either need to write our own query parser or some new features to
upstream Xapian to do any of these.
BR,
Jani.
next prev parent reply other threads:[~2012-12-08 22:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 22:34 [PATCH] TODO: date range queries - check Jani Nikula
2012-12-07 2:53 ` Jameson Graef Rollins
2012-12-07 8:58 ` Jani Nikula
2012-12-07 12:19 ` David Bremner
2012-12-07 16:42 ` Jameson Graef Rollins
2012-12-07 21:35 ` Jani Nikula
2012-12-07 21:45 ` Jameson Graef Rollins
2012-12-08 13:22 ` David Bremner
2012-12-08 21:16 ` Jameson Graef Rollins
2012-12-08 22:32 ` Jani Nikula [this message]
2012-12-09 1:53 ` Tomi Ollila
2012-12-10 12:35 ` David Bremner
2012-12-07 16:52 ` Daniel Kahn Gillmor
2012-12-07 21:27 ` Jani Nikula
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=87sj7gp43x.fsf@nikula.org \
--to=jani@nikula.org \
--cc=david@tethera.net \
--cc=jrollins@finestructure.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).