similar to: How to make QueryParser select entire word like "H.O.T"

I don't know whether this is a BUG or for special purpose... According to the definition of "xapian/queryparser.h", FLAG_AUTO_MULTIWORD_SYNONYMS contains bit of FLAG_AUTO_SYNONYMS . Therefore, long as I set the parse flag with FLAG_AUTO_SYNONYMS, the query parser will automatically activate the function of FLAG_AUTO_MULTIWORD_SYNONYMS. See the below source code part from

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

Hello. There are several problems I couldn't find a solution. 1. QueryParser does not perform stemming I am working with PHP5 and use the xapian wrapper written by Daniel M?nard I build a query using parseQuery. Output of the parsed query shows that terms are not stemmed, although a stemmer is set ( see code snippet) # create a XapianDatabase object to search in $db = new

I've got a small test database setup with one record. $ delve -r 1 -V /tmp/1/ Values for record #1: 0:DD4F2162FFFF0E43741A4A1C2B8EC0E7 1:./Text_page_scan_2.jpg 2:jpg 3:.jpg Term List for record #1: E:.jpg P:./Text_page_scan_2.jpg Q:DD4F2162FFFF0E43741A4A1C2B8EC0E7 T:jpg The terms were added with lines like this: doc.add_term(string("P:") + path); Problem is, I can't seem to

Hello, I'm wondering about how the QueryParser parses a query containing an "alias" when the default operator is OP_AND (by "alias", I mean a search field mapped to multiple term prefixes). With the following php code : <?php $parser=new XapianQueryParser(); $parser->set_default_op(XapianQuery::OP_AND); $parser->add_prefix('alias', 'AUT1:');

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,

Very few people seem to be using synonym in Xapian, I recently found some problems in the use of synonyms. Normally, I think we should not contain any prefix info in synonym table except that 'Z'. For example, I have the following synonyms and prefix info: db.add_synonym("search", "find"); db.add_synonym("Zsearch", "Zfind");

olly wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: olly > Revision: 9476 > Date: 2007-10-19 03:47:11 +0100 (Fri, 19 Oct 2007) > > Log message (14 lines): > include/xapian/queryparser.h,queryparser/queryparser.cc, > queryparser/queryparser.lemony,queryparser/queryparser_internal.h, > tests/queryparsertest.cc: Since calling

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

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

I want to be able to do searches with FLAG_PARTIAL and some without. Most searches without but with the PARTIAL for an autocomplete widget. I'm using xappy and I can't find where to send the flag when I build up the query. The docs talk of setting up the database with or without FLAG_PARTIAL but that's probably not what I want. Peter

Hi guys I'm trying to figure out how I can use probabilistic searching on a given field within a document; I've written to the list about this before, but haven't quite figured out what's required and, following a little research, I think I understand what I need to do but I'd like a clarification on this. o We have a database of a number of documents, with fields: title,

Please keep replies on-list so everyone can help and benefit. Begin forwarded message: > From: Greg <freediving at gmail.com> > >>> We're using it this way: >>> xq = qp.ParseQuery(query, (uint)Xapian.QueryParser.feature_flag.FLAG_PARTIAL); >>> The op is AND and the get_description is fairly long (I removed some >>> of it since there is a limit

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 to all, First, I would like to say a big thank you for the work which was done on my 'wish bug' to allow mapping one field to multiple prefixes (http://www.xapian.org/cgi-bin/bugzilla/show_bug.cgi?id=93). That's great! I have upgraded to 1.0.4 and I am revisiting my code, replacing the php query parser I wrote with Xapian's one. Everything works well, but I have some

--- search-xapian/XS/QueryParser.xs | 6 ++++++ search-xapian/Xapian/QueryParser.pm | 7 +++++++ xapian-core/include/xapian/queryparser.h | 3 +++ xapian-core/queryparser/queryparser.cc | 6 ++++++ xapian-core/queryparser/queryparser.lemony | 9 +++++++++ xapian-core/queryparser/queryparser_internal.h | 4 +++- 6 files changed, 34

Hi all, Thanks to the authors for the amazing work on Ferret! I have a question about setting up the standard operators on a QueryParser. I would like my parser to default to AND queries rather than the default OR. In Java I would simply do: QueryParser parser = new QueryParser("contents", new StandardAnalyzer()); parser.setDefaultOperator(QueryParser.Operator.AND); But I

I cooked up a little script to show what I mean. This doesn''t look right to me, but maybe I just completely misunderstand QueryParser. Same output on mswin32, unix, ferret 0.9 and 0.10 Cheers, Sam require ''rubygems'' require ''ferret'' p Ferret::VERSION # 0.10.6 index = Ferret::Index::Index.new() index << {:title => "Programming

I use the QueryParser::parse_query() method but I see it uses "OR" by default between words? Is there a way to make it use "AND" instead? I see there are flags I can pass to the parse_query() method but none seems to allow a switch from OR to AND. I would like to do that without having to write my own query parser. Everything else is fine with the QueryParser parsing, for

hey. I'm using the Search::Xapian interface version 0.9.2 (and xapian-core 0.9.2), and feeding the queryparser such things as "one AND NOT two" or "test NOT NOT really" makes it go "Aborted"... I've tried adding the exception handling from the other stubs to QueryParser.xs as well, but I still can't catch this error from perl. Does this mean