From mboxrd@z Thu Jan  1 00:00:00 1970
Received: by 10.90.79.9 with SMTP id c9cs32500agb;
        Tue, 3 Nov 2009 08:12:26 -0800 (PST)
Received: by 10.224.116.133 with SMTP id m5mr93903qaq.214.1257264745366;
        Tue, 03 Nov 2009 08:12:25 -0800 (PST)
Return-Path: <sup-talk-bounces@rubyforge.org>
Received: from rubyforge.org (rubyforge.org [205.234.109.19])
        by mx.google.com with ESMTP id 31si268898qyk.121.2009.11.03.08.12.25;
        Tue, 03 Nov 2009 08:12:25 -0800 (PST)
Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org
Received: from rubyforge.org (rubyforge.org [127.0.0.1])
	by rubyforge.org (Postfix) with ESMTP id 0BFED159807E;
	Tue,  3 Nov 2009 11:12:25 -0500 (EST)
Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.cmu.edu [128.237.157.88])
	by rubyforge.org (Postfix) with ESMTP id 8B12718582AC
	for <sup-talk@rubyforge.org>; Tue,  3 Nov 2009 11:12:12 -0500 (EST)
Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69)
	(envelope-from <rlane@zyrg.net>)
	id 1N5LzP-00086b-QE; Tue, 03 Nov 2009 11:12:11 -0500
From: Rich Lane <rlane@club.cc.cmu.edu>
To: Nicolas Pouillard <nicolas.pouillard@gmail.com>
In-reply-to: <1257237468-sup-5663@peray>
References: <1257118189-sup-7392@zyrg.net> <1257163403-sup-9032@masanjin.net>
	<1257196293-sup-6882@zyrg.net> <1257237468-sup-5663@peray>
Date: Tue, 03 Nov 2009 11:12:11 -0500
Message-Id: <1257263951-sup-6837@zyrg.net>
User-Agent: Sup/git
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] updated xapian experimental branch
X-BeenThere: sup-talk@rubyforge.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: User & developer discussion of Sup <sup-talk.rubyforge.org>
List-Unsubscribe: <http://rubyforge.org/mailman/options/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=unsubscribe>
List-Archive: <http://rubyforge.org/pipermail/sup-talk>
List-Post: <mailto:sup-talk@rubyforge.org>
List-Help: <mailto:sup-talk-request@rubyforge.org?subject=help>
List-Subscribe: <http://rubyforge.org/mailman/listinfo/sup-talk>,
	<mailto:sup-talk-request@rubyforge.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sup-talk-bounces@rubyforge.org
Errors-To: sup-talk-bounces@rubyforge.org

Excerpts from Nicolas Pouillard's message of Tue Nov 03 03:39:48 -0500 2009:
> What are non simple queries which would cause 'red X's to appear? My guess
> is that since we cannot change other attributes than the labels, we can
> statically know if the thread is still relevant without the label. No?

is:inbox OR foo

We have to use xapian to check relevance here because of the fulltext
term 'foo'.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk