similar to: QueryParser lowercase / uppercase and stemming

I am working with version 1.2.7 and want to use stemming and synonyms. I use the perl-bindings and get some problems. First of all: the perl-bindings dont allow the QueryParser a third argument when calling parse_query! So i cannot set a default prefix (which perhaps is the solution to my problem, but later more) i have a simple testcase: 3 documents, every document only has one word:

I'm new to Xapian and we just recently upgraded to version 1.0.0.0. However, something seems to have changed during the upgrade and I need help figuring out how my code should be written. In version 0.9.9.1 of Search::Xapian, the following code results in this output "Xapian::Query(pet:(pos=1))". my $qp = new Search::Xapian::QueryParser; $qp->set_stemmer(new

Hi, I've a problem to integrate xapian in my web application. I've developed the code for index e for search the documents published through my application. The app is developed in PHP. I've created a file that contain some function for search (called simpleSearch and advSearch). The problem is that if i run the code through the IDE (Zend for Eclipse) as PHP script it work correctly,

Hello, With PHP, I try to get spelling corrections but after 2 days of trying I can make it work !!! Here is my < simple > code : <?php require_once( '../global.info.php' ); require_once( 'xapian.class.php' ); require_once( 'xapianencode.func.php' ); // Open the database for searching. try { $database = new XapianDatabase(

I took one of the examples and tried to run against my database ls -l /data1/mail/db/cur.1 total 1129624 -rw-r--r-- 1 jwl jwl 0 2011-06-09 02:27 flintlock -rw-r--r-- 1 jwl jwl 28 2011-06-09 02:27 iamchert -rwxrwxrwx 1 jwl jwl 7258 2011-06-09 02:27 position.baseA -rwxrwxrwx 1 jwl jwl 7046 2011-06-09 02:27 position.baseB -rwxrwxrwx 1 jwl jwl 474226688 2011-06-09 02:28

Hi everyone, I tried sending a message as a reply a while back on my previous topic, but it didn't go through. (Tried Gmane), not even when I 'authorized' the reply. So I'll just paste it here for reference, below this message. It might help some people. But now I have one other small problem, and I'm not sure if it is actually my mistake (although I'm pretty sure it is

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

I would like to know how to convert a string with characters to all uppercase or all lowercase? If anyone could let me know if there exists a function in R for the conversion, that will be very helpful. Regards, Suman [[alternative HTML version deleted]]

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

--- 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, I'm using xapian to build my search engine, but met with a problem. The code snippet is like: ----------------------Code begin------------------------------------------------------------- Xapian::QueryParser qp; qp.add_prefix("Singer", "S"); Xapian::Query query = qp.parse_query("Singer:s.h.e",

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

Hello, My name is Sean Mikalson. I am a second year Software Engineering student with a combined degree in Philosophy. I am interested in participating with Xapian in GSOC this year and a couple of projects have initially caught my eye: - Dynamic Snippets - QueryParser Reimplementation I have good working knowledge in C/C++, Java and SQL (specifically Transact-SQL). In order to determine

Hi Olly, valgrind showed me what seems to be a memory leak: QueryParser owns the Stopper and Stem instances it points to (since it deletes them e.g. in set_stemming_options), but it does not delete them at destruction. (Btw., I don't test before deleting, but maybe "delete 0;" does not work on all platforms?) -- Robert Pollak GPG Key ID: 748646AD -------------- next part

hello everyone, I am Maheshwar, a prefinal year Computer Science undergraduate student at BITS-Pilani, India. When i was going through the GSOC ideas , i felt interested in Quesry parser project. Till now i have implemented a couple of LL(1) parsers as a part of my assignment in Compiler construction course, so i would love to join and contribute to this project. So can any one tell me how to go

I am having a bit of a problem with my search queries being parsed correctly it seems, and I wonder if anyone else has experienced this. I have written an index using StandardAnalyzer for analysis. I want to search that index by passing my user query through a QueryParser instance which is also using a StandardAnalyzer. However the resultant query does not seem to be a valid term query and

During our last week of Ferret / aaf usage (also our first week of Ferret / aaf usage), I have received 8 messages stating that our app encountered a Ferret::QueryParser::QueryParseException. For instance: A Ferret::QueryParser::QueryParseException occurred in foo#search: Error occurred in src/q_parser.y:279 - yyerror couldn''t parse query "com -- 404". Error message