search for: flag_loveh

Salve, Thank you very much for your kind answer. Spelling correction works very well now. I have just one more question. I am using Xapian::QueryParser() to create the Query. The flags are: FLAG_PHRASE | FLAG_LOVEHATE | FLAG_WILDCARD If I search, lets say for "king queen" (without quotes), I get all documents with either "king" or "queen". Is there a chance to find only documents with "king" and "queen" without boolean operators (like Google)? Thank you very...

Hello, Thanks Olly , by following to your suggestion I could do the indexing in the CSV file while the search results retrieved from the Postgres and it's working fine. [ I am using the Xapian PHP-binding to index and search.] How could I enable the WILDCARDS in it ? I followed with the online manual which says it is disabled by default there given some method to enable but I am not

...yParser_parse_query' in */usr/local/share/php5/xapian.php* on line *1409 *The error occurs at this code $query = $qp->parse_query( $query_string , XapianQueryParser::FLAG_PHRASE | XapianQueryParser::FLAG_BOOLEAN | XapianQueryParser::FLAG_LOVEHATE | XapianQueryParser::FLAG_SPELLING_CORRECTION ); I also tried $query = $qp->parse_query($query_string); It's really got me scratching my head because I've had it working before, any ideas where I should start looking, could it be a system config e...

I have found that lower cased boolean operators such as "and" or "or" does not work. Of course I never forget setting FLAG_BOOLEAN_ANY_CASE flag. QP seems to treat them as terms. Just look at the following tests regardless of search results! $ python search.py -v woman AND man Performing query 'Xapian::Query((woman:(pos=1) AND man:(pos=2)))' 0 results

...= queryparser.parse_query("mUTTON++"); TEST_EQUAL(qobj.get_description(), "Xapian::Query(mutton:(pos=1))"); + // Regression test: check that wildcards work with +terms. + unsigned flags = Xapian::QueryParser::FLAG_WILDCARD | + Xapian::QueryParser::FLAG_LOVEHATE; + qobj = queryparser.parse_query("+mai* main", flags); + TEST_EQUAL(qobj.get_description(), "Xapian::Query((main:(pos=1) AND_MAYBE main:(pos=2)))"); + // Regression test (if we had a +term which was a wildcard and wasn't + // present, the query could still ma...

...;german"); $myQueryParser->setStemmer($stemmer); $myQueryParser->setStemmingStrategy(STEM_ALL); #$querystring = removeUmlaute($querystring); #wildcard search $myQuery = $myQueryParser->parseQuery($querystring, Xapian::FLAG_PHRASE|Xapian::FLAG_BOOLEAN|Xapian::FLAG_LOVEHATE|Xapian::FLAG_WILDCARD); ... So what am I doing wrong? The second thing I wondered about, is there any possibility to forbid queryparser lowercasing of the query string. At least for exact phrase matching I found this quite meaningful. (Data is indexed both, upper- and lowercase) Another...