similar to: how to change the default operator?

On Thu, 30 Mar 2023 at 04:58, Olly Betts <olly at survex.com> wrote: > > Another option is to import the things you want with `use` and then > you can just use `XapianWritableDatabase` without to prefix it with > `\`. To do that add this after your `namespace literallyanynamespace;` > line: > > use \XapianWritableDatabase; Thank you very much. This then (because

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:');

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

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

Hi All, I know that from version 1.2.6, if default_op is OP_NEAR or OP_PHRASE then stemming of the terms is disabled, since positional information isn't indexed for stemmed terms by default. However, I would like to try using OP_NEAR as default_op with stemming because I think the near operator is somehow different from exact phrase. Then I wanna see how the search results looks with this

On Thu, Mar 30, 2023 at 05:16:16AM +0100, John Handelaar wrote: > This then (because of course) led to some more things needing tidying > up and I've run into something I can't work out while trying to update > previously-worked-in-php7 code in the actual file I'm trying to update > > $this->queryparser->set_default_op(Query_OP_AND); > > ...leads to

Hello, can I get an explanation of the following. Running the following code: .... pqp=new QueryParser(); Stem stem("norwegian"); cout << "DEBUG " << stem.stem_word(_sXapian)<< endl; pqp->set_stemmer(stem); pqp->set_database(*_pdatabase); pqp->set_default_op(Query::OP_AND); //Set the

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

Probably an uncaught malformed query - the following form of search queries causes a crash for me (core 1.2.3, Perl API, 64bit Debian Lenny, self-compiled): x-y NEAR test NEAR test The first term can be anything with a hyphen in it but word characters at the beginning and end ("3--3" will do). The other 2 terms can be anything. "test NEAR x-y NEAR test" will not cause a

Hi, Under gcc 2.95 Xapian fails to build like so: g++ -DHAVE_CONFIG_H -I. -I./common -I./include -I/home/dsainty/not-backed-up/pkgsrc/textproc/xapian/work/.buildlink/include -Wall -W -Wredundant-decls -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long -Wformat-security -fno-gnu-keywords -Wundef -O2 -c queryparser/queryparser_internal.cc

i have 300 millions records and my search file like this , i want the newest 10 results that match my query , so i use boolean search and "enquire.set_docid_order(enquire.DESCENDING)" , but this method seems a little slow . when i remove "enquire.set_docid_order(enquire.DESCENDING)" it run much faster . how can i fetch the newest 10 results as fast as possible? search.py

I've been getting excellent performance out of xapian but when searches on phrases of common terms such as [ "north america" ] or [ "art history" ] get run it will take a very long time to come up with results. Examples: ------------------------------ [ south africa ] -- 10379 results found in ~.2 sec [ white house ] -- 17988 results found in <1 sec Quoting either of

On Thu, Mar 30, 2023 at 04:42:41AM +0100, John Handelaar wrote: > It appears that I can't use anything in PHP8.2 if the PHP file from > which I want to access xapian contains a namespace declaration, > because the PHP functions themselves cannot be found. You need to tell PHP to look in the root namespace, e.g.: $test = new \XapianWritableDatabase('searchdb'); Another

Hi all, public-inbox allows searching for git blob names (e.g. "badc0ffee") in patches. Initially, I chose to use add_prefix for probabilistic terms, since I assumed it could be a superset of what boolean searching offered. Unfortunately, it doesn't seem to be the case because stemming is interfering. So switching to boolean filtering seems to work; and it is fine for mechanical

Hi all, I've come across an issue caused when I try to set the query parser's default op to OP_PHRASE: Xapian raises an Unimplemented Error if the query contains hyphenated words or other terms that implicitly generate a phrase. This can be shown with the following Python extract: >>> from xapian import * >>> qp = QueryParser() >>>

Hi All, I wanted to add a small tweak to my installation of the Query Parser. Should I be editing queryparser.lemony? I tried that and the make didn't include my change. I applied the same change to queryparser_internal.cc and it worked fine. Is the .lemony file something used internally and I can ignore? Or do I need to run something prior to make to convert the files? Thanks, Mike Boone.

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

I have encountered the following build errors after applying xapian-qp-utf8-0.9.2.patch. There is no build error before the patch. - CentOS 4.2 64 bit version (RHEL 4.0.2 compatible) - AMD Opteron dual processor Can anybody tell me what I am missing? Thanks! Sungsoo Kim -------------------------------------------------- [root at saturn queryparser]# make make all-am make[1]: Entering

mple (see attachment). > > Attachments get stripped out by the mailing list, so I?ve made a private gist of the two files here: <https://gist.github.com/jaylett/ce8455b37e2b84422346>. > > Actually, when I run it I get 0 matches, which would explain why you?re just getting the start of the document. However if I adjust things (match the stemming strategy for TermGenerator to

I have written a very simple function to return the match count based on the simplesearch.cc code. It fails with a seg fault. The relevant code is: -------------------- int ftQuery(char* qs, const char* dbname,char* results, int msize) { long docid; char* op; char fullDB[1024]; string queryString;