similar to: FLAG_BOOLEAN_ANY_CASE does not work

David — this isn't the behaviour I see what 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)'

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

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

Hi, all! I want to change current RHEL 4.0 ES into CentOS 4.2 on Sun X4100 server. The server has SAS SCSI based two 2.5" hard disks. I could only install RHEL 4.0 Update 1 because the server is equipped with RHEL 4.0 Update 1's device driver only. I've included below the boot process messages concerned with SCSI controller. If it's possible for me to install CentOS 4.0 on my

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

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

Greetings, I'm trying to code a test case for get_corrected_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',

I wanted to update to CentOS 4.3 from CentOS 4.2. While updating packages using yum, there was serveral error messages, and I've found that some packages has not been updated. So I tried to update again but the packages would not be updated. I attached the messages shown below. Sungsoo Kim ------------------------------------------- [root at phobos ~]# yum update Setting up Update Process

Dear xapian developers, I've added a function named "set_sort_by_relevance_then_value()". Now I want to rebuild python-bindings to include the new function and test if it works or not. I guess there is a way to rebuild all of the binding modules include the new function. I am not used to SWIG. I want to which files I need to change and how to build it. Thanks! Sungsoo Kim

There are two issues with rpmbuild xapian-bindings-0.9.5. xapian.pyo is missing in the source package but it is defined in xapian-bindings.spec. After removing the following line from xapian-bindings.spec I could finish rpmbuild without error. %ghost %{_libdir}/python%{python_ver}/site-packages/xapian.pyo csharp binding is turned on by default in xapian-bindings.spec. As you know csharp

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

This is another error different from the previous posting. I want to compile xapian-core-0.9.4_svn6707 with UTF-8 patch. But I failed to compile it due to the following errors. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- g++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I../common -I../api -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include

I wrote: > I think it's a bug. Or at least QueryParser uses a rather delicate rule > for when to add a ":" between the prefix and the term, which scriptindex > doesn't implement. The rule is undocumented (except in the code) so > it's arguable who is correct. I've been looking at this some more. We need some way to distinguish the term prefix from the term

I hope I'm not beating a dead horse here, but we recently started evaluating xapian and Xapwrap (python wrapper around it) for our project and I've been quickly trying to soak up a lot of the docs and concepts, so I hope I can explain my question clearly. We have a use case where we must return the first 50 most recent documents that match our query. We don't want the first 50

There is is bug when setting XAPIAN_FLUSH_THRESHOLD=20000000 When trying for force Xapian flush documents to flush after 20 million documents Xapian ignores the size and flush it after only 10,000 documents. Data captured from delve after 60 seconds interval when has been set as follow: XAPIAN_FLUSH_THRESHOLD=20000000 perl -e ' while(1) { system("delve ."); sleep(60); } '

I posted this message first. But it was missing so I post again. I think there is a some bug in build configration files. Can you check up the following errors and fix it? The error has no concern with UTF-8 patch. Environment : CentOS 4.3 x86_64 Sungsoo Kim ---------------------------------- [root at saturn xapian-core-0.9.4_svn6707]# make ... ... mkdir .libs/libxapian.lax/libqueryparser.a

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

The symbols file generated in the Debian package to aid the package maintainer automatically detect future changes shows internal library and helper function names, whereas it should only be exporting hivex_* function names. This page may help with this: http://gcc.gnu.org/wiki/Visibility Symbols: asnprintf at Base 1.2.1 c_isalnum at Base 1.2.1 c_isalpha at Base 1.2.1 c_isascii at Base