search for: flag_phrase

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)? T...

...-------------------------------------------------------- Xapian::QueryParser qp; qp.add_prefix("Singer", "S"); Xapian::Query query = qp.parse_query("Singer:s.h.e", Xapian::QueryParser::FLAG_PARTIAL|Xapian::QueryParser::FLAG_AUTO_MULTIWORD_SYNONYMS |Xapian::QueryParser::FLAG_PHRASE ); cout << "Performing query `" << query.get_description() << "'" << endl; ----------------------Code end--------------------------------------------------------------- See the output from the stdio, ----------------------Output begin---------------...

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

Hi all, My app uses prefixes for user-defined labels and directory names. Since these are case-sensitive, I chose XLABEL and XDIR respectively. Labels and directories may start with an upper-case, so a ":" is always inserted between the prefix and the term itself. These prefixes are mapped with add_boolean_prefix to "dir" and "label". Let's imagine I index a

...working, I get the following error: *Fatal error*: No matching function for overloaded 'QueryParser_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'...

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

Hi all. We are trying to use Xapian to index the titles of around ten million documents (music catalogue) and then do auto-complete style search on this index. After poking around we can't quite get the combination of QueryParser flags and search query that will give back the results we want. The closest we have can take a very long time (because it is searching for, and building a list of,

...($ostem);$oqparser->set_database($odb);$oqparser->set_stemming_strategy(1);$oqparser->add_boolean_prefix("Q",1);$oquery = $oqparser->parse_query($query, 1); I found some perl examples and 'ported' it over to the PHP version. Varying the flags (like XapianQueryParser::FLAG_PHRASE) or the boolean_prefix, etc. does not influence anything. I tried to lcoate the error in Xapian.php, but I think the error can be a bit deeper... I can query using XapianQuery, with a single keyword. Fatal error: No matching function for overloaded 'new_Query' in /var/www/htdocs/almar/xap...

...; $stemmer = new XapianStemmer("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 indexe...