From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.134.218 with SMTP id k26cs69143bkt; Thu, 10 Jun 2010 05:13:07 -0700 (PDT) Received: by 10.231.144.147 with SMTP id z19mr55247ibu.81.1276171986515; Thu, 10 Jun 2010 05:13:06 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id l24si12360029ibj.33.2010.06.10.05.13.06; Thu, 10 Jun 2010 05:13:06 -0700 (PDT) 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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 1C8FF185838B; Thu, 10 Jun 2010 08:13:05 -0400 (EDT) Received: from mail-vw0-f50.google.com (mail-vw0-f50.google.com [209.85.212.50]) by rubyforge.org (Postfix) with ESMTP id B0CA3185835D for ; Thu, 10 Jun 2010 07:53:13 -0400 (EDT) Received: by vws10 with SMTP id 10so5643169vws.23 for ; Thu, 10 Jun 2010 04:53:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type:cc :subject:from:to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=VJheqPX6MxZ7G/wI3+mfe5PcV6LWhpjbhTj+QmS5n/E=; b=v8ESFKkJ76xY6BoQus/8oUXwrbSK/wfiiWWrWvEQWLkncZeHU5d2ZtBOcP53/EIvjn qf6fIcdLFNqSS84ie2Oo9kLEvSubTZUxuqQ2Z4r37eW8Ky3HyYrKgL6gNW0GdfZgqOOl V0qCQle84oqUyIQKJXP9kAky7PAm6y0OozXY8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=xStTlW7H0MtPBeoxRrZO0ZLTiLyNUffEzrrRLyzo6fcnlhMDI/dlvxNRmV47YUzvKA o9MjyCQvRda+woOFxpdYzTzGvUnJ1J3yyc+uknUcJdbIxO7UbUATL+WEvsX3FHOuXlK/ oxsyzhfDcec0y53O2SuariKLbF74nnXQ9N1zM= Received: by 10.224.51.17 with SMTP id b17mr51394qag.175.1276170791918; Thu, 10 Jun 2010 04:53:11 -0700 (PDT) Received: from localhost (c-24-63-138-235.hsd1.vt.comcast.net [24.63.138.235]) by mx.google.com with ESMTPS id m29sm13851493qck.4.2010.06.10.04.53.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Jun 2010 04:53:09 -0700 (PDT) From: Mark Alexander To: Gregor Hoffleit In-reply-to: <1276098490-sup-8738@sam.mediasupervision.de> References: <1276098490-sup-8738@sam.mediasupervision.de> Date: Thu, 10 Jun 2010 07:53:08 -0400 Message-Id: <1276170636-sup-6551@r61> User-Agent: Sup/0.11 Cc: sup-talk Subject: Re: [sup-talk] Bug with searching for multiple labels at once X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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 Gregor Hoffleit's message of Thu Jun 10 06:39:54 -0400 2010: > I have a strange problem with search strings including multiple labels. > I was at the impression that the search > > label:somelabel label:anotherlabel I ran into this confusing behavior a while back when I upgraded from a ferret index to a Xapian index. It appears that the query language now requires you to use an explicit AND operator between search terms. Without that, the implied operator appears to be an OR. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk