search for: flag_boolean_any_case

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 found $ python search.py -v woman and man Performing qu...

...QueryParser alone, unless you're driving it in a way I don't expect. In python: >>> import xapian >>> qp = xapian.QueryParser() >>> qp.add_prefix('subject', 'S') >>> str(qp.parse_query('subject:"and"', qp.FLAG_DEFAULT|qp.FLAG_BOOLEAN_ANY_CASE)) 'Query(Sand at 1)' >>> str(qp.parse_query('subject:"or"', qp.FLAG_DEFAULT|qp.FLAG_BOOLEAN_ANY_CASE)) 'Query(Sor at 1)' >>> str(qp.parse_query('subject:"not"', qp.FLAG_DEFAULT|qp.FLAG_BOOLEAN_ANY_CASE)) 'Query(Snot at 1)'...

Today we noticed that keywords can't be searched as prefixed terms. Or that's what it looks like anyway. I tested and, or, and not. ╰─% NOTMUCH_DEBUG_QUERY=y notmuch search 'subject:"and"' Query string is: subject:"and" notmuch search: A Xapian exception occurred A Xapian exception occurred parsing query: Syntax: <expression> AND <expression> Query

...orrected_query_string() in perl in t/parser.t, but I'm getting the following error: Can't locate auto/Search/Xapian/Query/get_correct.al... I take it something isn't implemented yet? Here's the code: ok( $query = $qp->parse_query( 'one or two', FLAG_BOOLEAN|FLAG_BOOLEAN_ANY_CASE|FLAG_SPELLING_CORRECTION ) ); + is( $query->get_corrected_query_string(), '', "get_corrected_query_string ok" ); Thanks Henry

...f' for 'not' and so on). Currently, I pre-process the query, replacing \bet|ou|sauf\b with the correct operator, but it does not work in some cases (phrases...) Would it be possible to have something like qp->add_operator(OP_OR, 'ou') in the API? Also: QueryParser has flag FLAG_BOOLEAN_ANY_CASE to allow boolean operators in any case. Would it be possible to have something similar for the prefix names (title:xx, Title:xx, TITLE:xx would all be recognized)? That's all! Re-reading my mail, it's rather a big wish list than 'some remarks' ;-) Please forgive me for being so...

Hi, I'm Ayush an undergraduate Computer Science student from Thapar university, India. I was fiddling with xapian since the morning and trying to understand the code and internals of Xapian. I tried implementing the bite sized project idea posted here: https://trac.xapian.org/wiki/ProjectIdeas#AddnewOmegaScriptcommandtodoasubstringsearch but could not understand what needs to be returned when