From: Carl Worth <cworth@cworth.org>
To: Michael McDermott <mcdermott.michaelj@gmail.com>,
sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sorting
Date: Mon, 14 Dec 2009 15:12:41 -0800 [thread overview]
Message-ID: <87eimx2lqu.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1260809732-sup-4895@zion>
[-- Attachment #1.1: Type: text/plain, Size: 991 bytes --]
On Mon, 14 Dec 2009 11:01:39 -0600, Michael McDermott <mcdermott.michaelj@gmail.com> wrote:
> After running a search in Sup, is there any way to sort the result set? Or,
> perhaps, specify the ordering in the query? (ala SQL)
The Xapian database (which Sup uses optionally now and perhaps
exclusively in the future) allows results to be sorted by anything
stored in a "value" field of the documents.
If I recall correctly, Sup is currently storing three things in "value"
fields:
1. Message ID
2. Thread ID (which is Message ID of a representative message)
3. Date
So it's quite easy to have Xapian return things based on an ordering of
any one of those values (in either direction). And this does not require
fetching all documents.
Sorting on anything else would require either fetching all documents,
(and doing the sort in the user-interface), or else storing an
additional value for each document in the database.
What is it that you actually want to sort on?
-carl
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-12-14 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 17:01 Michael McDermott
2009-12-14 17:13 ` Marc Weber
2009-12-14 17:17 ` Edward Z. Yang
2009-12-14 20:45 ` Michael McDermott
2009-12-19 19:10 ` William Morgan
2009-12-14 23:12 ` Carl Worth [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=87eimx2lqu.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=mcdermott.michaelj@gmail.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