From: Olly Betts <olly@survex.com>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] [PATCH] Allow thread index view to sort oldest first
Date: Tue, 13 Oct 2009 20:51:10 +0000 (UTC) [thread overview]
Message-ID: <slrnhd9q1u.gga.olly@msgid.survex.com> (raw)
In-Reply-To: <1255388543-sup-7477@yoom.home.cworth.org>
On 2009-10-12, Carl Worth <cworth@cworth.org> wrote:
> How do we get this behavior in xapian? I'm fine if the index is not
> optimized for this. The current newest-first optimization is perfect
> for actual searching, (as opposed to reading of new messages), and the
> patches don't change that.
@enquire.docid_order = Xapian::Enquire::DESCENDING
This means that the docid order (which is used as the least significant
ordering) is descending rather than ascending. In this case (I assume)
we're using Xapian::BoolWeight so this is the only ordering.
Cheers,
Olly
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-10-13 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 21:08 Carl Worth
2009-10-01 17:04 ` William Morgan
2009-10-01 17:43 ` Carl Worth
2009-10-12 12:48 ` William Morgan
2009-10-12 23:02 ` Carl Worth
2009-10-13 20:51 ` Olly Betts [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnhd9q1u.gga.olly@msgid.survex.com \
--to=olly@survex.com \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox