search for: flag_wildcard

Hello, I have once again a small question: Is it possible to search a pattern like "*foo*" ? I saw that we can use QueryParser::FLAG_WILDCARD but only with "foo*" patterns. Have you got a trick to do that ? And an other question with wildcards: i tested FLAG_WILDCARD and the QueryParser, but i have some problems with special characters (by example "/"). Is it possible to use escape characters to do that? I tried &quo...

...ETURN(NULL); Index: tests/queryparsertest.cc =================================================================== --- tests/queryparsertest.cc (revision 7552) +++ tests/queryparsertest.cc (working copy) @@ -655,7 +655,7 @@ qobj = queryparser.parse_query("muscle*", Xapian::QueryParser::FLAG_WILDCARD); TEST_EQUAL(qobj.get_description(), "Xapian::Query((muscle:(pos=1) OR musclebound:(pos=1)))"); qobj = queryparser.parse_query("meat*", Xapian::QueryParser::FLAG_WILDCARD); - TEST_EQUAL(qobj.get_description(), "Xapian::Query()"); + TEST_EQUAL(qobj.get_d...

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 much Markus

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, I've just noticed that set_max_wildcard_expansion() has been removed in favour of set_max_expansion() in Xapian. Has the new method been added to the Perl-bindings? We have some old Perl code that uses set_max_wildcard_expansion(), and I have a test of too large expansion that now returns "something terrible happened" instead of"Exception: Wildcard ... expands too much

I tried to register yesterday, twice with 2 email addresses. The website said it sent me mail, I never got a mail. Someone else, please confirm this is broken. A bug I'd like to file is that I'd like an option to search *word. Currently you can only search word*. The example where I would find this useful is searching for urls and email addresses. For example, I want to find emals from

I tried to register yesterday, twice with 2 email addresses. The website said it sent me mail, I never got a mail. Someone else, please confirm this is broken. A bug I'd like to file is that I'd like an option to search *word. Currently you can only search word*. The example where I would find this useful is searching for urls and email addresses. For example, I want to find emals from

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

...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 thing is the encoding of...

Hi, I am looking for Chinese Japanese and Korean tokenizer that could can be use to tokenize terms for CJK languages. I am not very familiar with these languages however I think that these languages contains one or more words in one symbol which it make more difficult to tokenize into searchable terms. Lucene has CJK Tokenizer ... and I am looking around if there is some open source that we