From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] U (unread) search is off
Date: Thu, 10 Sep 2009 12:16:35 -0400 [thread overview]
Message-ID: <1252595946-sup-171@zyrg.net> (raw)
In-Reply-To: <1252590993-sup-3885@masanjin.net>
There are actually 2 bugs in this thread. Ben is still using Xapian
1.0.14 which doesn't have my fix for the phantom labels problem.
Ingmar's message was about the surprise Xapian::QueryParser feature.
Excerpts from William Morgan's message of Thu Sep 10 09:59:13 -0400 2009:
> Reformatted excerpts from Ingmar Vanhassel's message of 2009-09-10:
> > Known issue, see http://mid.gmane.org/1251792282-sup-2057 at cannonball and
> > Rich's answer to my mail.
>
> Actually, I haven't been following this too closely, but what is the status?
> I noticed we have this in xapian_index.rb:
> qp.default_op = Xapian::Query::OP_AND
>
> Is that not sufficient (combined with a newish Xapian, I guess?) to fix
> the problem?
I thought it was, but it turns out that unless you explicitly add AND
operators Xapian will OR terms over the same field such that
"label:foo label:bar" gives you the union instead of the intersection.
We could fix this by patching Xapian to make this behavior configurable,
or we could come up with an index-agnostic simple query language that
doesn't support boolean operators. The native query language would still
be available, of course, but the simple one would suffice for most usage
and potentially have Sup-specific features.
next prev parent reply other threads:[~2009-09-10 16:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 13:54 Ben Walton
2009-09-10 11:22 ` Ingmar Vanhassel
2009-09-10 13:59 ` William Morgan
2009-09-10 14:04 ` Ben Walton
2009-09-10 16:17 ` Rich Lane
2009-09-10 17:13 ` Ben Walton
2009-09-10 14:08 ` Ingmar Vanhassel
2009-09-10 16:16 ` Rich Lane [this message]
2009-09-12 16:47 ` William Morgan
2009-09-14 0:31 ` Rich Lane
2009-09-15 7:18 ` Olly Betts
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=1252595946-sup-171@zyrg.net \
--to=rlane@club.cc.cmu.edu \
/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