Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Sascha Silbe <sascha-ml-reply-to-2011-1@silbe.org>
To: Rich Lane <rlane@club.cc.cmu.edu>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] fix handling of multiple label: terms in search
Date: Tue, 18 Jan 2011 19:11:05 +0100	[thread overview]
Message-ID: <1295374111-sup-5154@xo15-sascha.sascha.silbe.org> (raw)
In-Reply-To: <1295245113-sup-5823@zyrg.net>


[-- Attachment #1.1: Type: text/plain, Size: 712 bytes --]

Excerpts from Rich Lane's message of Mon Jan 17 07:20:08 +0100 2011:
> Excerpts from Sascha Silbe's message of Wed Sep 29 10:16:02 -0400 2010:
> > By default Xapian will join query terms with the same prefix with OR instead
> > of AND, so searching for multiple labels doesn't return the expected results.
> > By making use of a parameter to add_boolean_prefix (added in Xapian 1.2) we
> > can tell Xapian to use OR only for the search terms that are guaranteed to be
> > unique.
> 

> Merged to master.

Thanks! I've rebased my branch on top of next and will submit another
round of patches that should be ready for inclusion.

Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

      reply	other threads:[~2011-01-18 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 14:16 Sascha Silbe
2010-09-29 15:27 ` Edward Z. Yang
2010-10-08  4:30 ` Rich Lane
2011-01-17  6:20 ` Rich Lane
2011-01-18 18:11   ` Sascha Silbe [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=1295374111-sup-5154@xo15-sascha.sascha.silbe.org \
    --to=sascha-ml-reply-to-2011-1@silbe.org \
    --cc=rlane@club.cc.cmu.edu \
    --cc=sup-devel@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