<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Thanks, Olly. <br><br>The eruptions of information in the last decade have definitely expanded the dimension and size of the data collection to an extremely great extent. That makes it even harder to reach out to something we're really looking for, and possibly that's why we now need more exact filter to get rid of the nonsense.<br><br>As for "operator chain", I intended to mean a combination of maybe 2-3 operators applied in a particular order. For instance, use NEAR first and then use FILTER to narrow down. I know this could be expensive in time and efficiency, but I just want to try whether it could work and what could be the possible result. <br><br>Best, <br>Shen<br><br><br>> Date: Fri, 25 Mar 2011 04:34:06 +0000<br>> From: olly@survex.com<br>> To: te_quira@hotmail.com<br>> CC: xapian-devel@lists.xapian.org<br>> Subject: Re: [Xapian-devel] how to change the default operator?<br>> <br>> On Fri, Mar 25, 2011 at 06:04:26AM +0800, Shen Li wrote:<br>> > Thanks very much for your advice! I've managed to explicitly set the<br>> > default operator each time with php binding instead of changing the<br>> > Xapian core.<br>> <br>> Incidentally, OR as the default operator does seem like the wrong choice<br>> now (though it was reasonable 10+ years ago when we chose it). It's<br>> just rather disruptive to change now.<br>> <br>> I've been wondering if it's something we should change for a Xapian 2<br>> release though. There are likely to be API incompatibilities there<br>> anyway, and this one has an easy fix which works with the current API<br>> (i.e. setting the operator to OR explicitly). I suspect that almost<br>> everyone sets it to AND anyway, so few people would be affected, but<br>> it would give us the saner default going forwards.<br>> <br>> > However, I'm still wondering that whether it's possible<br>> > to use multiple operators like a operators chain in queryparser. And<br>> > if it is, how should I implement that? I really appreciate your help<br>> > and maybe some reference would be even better!<br>> <br>> I'm not sure what you mean by an "operators chain" - can you give an<br>> example?<br>> <br>> Cheers,<br>> Olly<br> </body>
</html>