similar to: How "NOT expression" used in Xapian

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,

Hello :-) We have Xapian and Omega working nicely. Now we would like more functionality at the browser UI, such as being able to specify date ranges and being able to search the file name including looking only for, say, .odt files. Question is whether the best choice for this would be to develop a template using OmegaScript or to switch to C++ or some other language. Availability of skills

Hi, I configured XAPIAN 1.0.1 and OMEGA 1.0.1. on my development machine (first removed the old ones). I recreated my databases (both quartz and flint) and tried to run original queries against the databases created by the new versions. I'm getting empty result sets from OMEGA. If I use the delve tool I actually see that the records are created fine. No log files are written as far as I

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

Hi, I'm having some problems compiling on Mac OS X: nekomimi:xapian samuel$ sudo port install libiconv ---> Configuring gperf ---> Building gperf ---> Staging gperf into destroot ---> Installing gperf @3.0.4_0+universal ---> Deactivating gperf @3.0.4_0 ---> Cleaning gperf ---> Activating gperf @3.0.4_0+universal ---> Cleaning gperf ---> Computing

To Olly Betts: Thank you very much for any feedback. I apologise for this belated reply and also for the fact that the text of the previous posting appeared fragmented, due to its fixed chars/line format. With reference to: > Can, or could, one construct a query so that Omega (Xapian) can handle > this ? > > ... perhaps with some type of Regex ? > > It would seem

Are there any options to forming queries with Omega? For instance can you specify a proximity search like "file near 5 manager"? If so, where might I find this documented? I don't see it in the docs directory. Thanks Jim.

I've uploaded Xapian 1.0.19 (including Search::Xapian 1.0.19.0), which as usual you can download from: http://xapian.org/download The most notable changes in this release are: QueryParser: * Fix memory leak if Database throws an exception during parsing. Flint backend: * Updating positional information for a document optimised a little. Search::Xapian: * Wrap

When I submit a filename to the query parser it breaks it up Example: /home/user/file_name.ext becomes Xapian::Query((home:(pos=1) PHRASE 5 user:(pos=2) PHRASE 5 file:(pos=3) PHRASE 5 name:(pos=4) PHRASE 5 ext:(pos=5))) which does not find the document. If I do an single term query not using the query parser then I find the document. The Query Parser also breaks up hyphenated terms

All, I'm having some issues compiling omega. Here are the particulars I'm on win7, using cygwin 4.9.2 64 bit. Here's the relevant output from make: libtool: link: g++ -fshow-column -Wall -W -Wredundant-decls -Wpointer-arith -Wca st-qual -Wcast-align -Wno-long-long -Wformat-security -fno-gnu-keywords -Wundef -Woverloaded-virtual -Wstrict-null-sentinel -Wshadow -Wstrict-overflow=1

I've uploaded Xapian 1.0.18 (including Search::Xapian 1.0.18.0), which as usual you can download from: http://xapian.org/download The most notable changes in this release are: QueryParser: * Improve support for languages such as Burmese which use Unicode enclosing mark and combining spacing mark characters. Flint backend: * When updating documents, don't update posting entries

I've just been looking at ICU with an eye to reworking the unicode queryparser patch to use it. A few things have jumped out so far which make we wonder if it's the best option. I don't really know what the alternatives are though (currently QueryParser uses glib's unicode routines). The first is that there seems to be bad version skew. Ubuntu breezy (the latest release) has

Hello, I am working on replacing atoi () and atol() functions with strtol() and strtoul() . I came across many files which uses statement like these time_t secs= atoi(data_span.c_str()), here time_t Datatype is not known but wikipedia says that it is integer so is it necessary to replace atoi with strtol over here ?? And is their any document which helps me what each file function does like

On Tue, May 11, 2004 at 05:41:58PM +0100, Richard Boulton wrote: > * If the queryserver can't parse a query, strip out all special > characters, and then retry. This means that we get some kind of > result even if the query is broken. That's probably a feature worth pushing down into Xapian::QueryParser... Cheers, Olly

Hello, It's probably quite troll-risky to put a title like this, but did anyone take the trouble to compare Lucene to Xapian and make a list of differences? As I told the list at the end of last year, I'm going to have to integrate an indexing/search engine in the coming weeks or months. It will be integrated to Dokeos, an open-source e-learning application in PHP, and at the moment we

Hello everyone, I'm using Xapian at work (PHP bindings) and I have to make it accept '##' as a term to index. We have a layer on top of xapian, but as far as I can tell, Xapian's QueryParser is removing them from the query. So, if I search for just '##' I get an empty query, after Xapian parsed it. I've seen the flags this class accepts, but I can't do what I want

On Thu, 18 Apr 2024 at 06:24, Olly Betts <olly at survex.com> wrote: [ ... ] > Yes - it's in the xapian-omega package you already have installed: > > /usr/lib/cgi-bin/omega/omega Thank you, Mr. Betts. for your replying to my questions. Please consider me a novice and elaborate further, Mr. Betts. > You may need to configure apache to tell it to use this for a URL on

Hello friends, I have installed xapian-omega for my system installed from Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46, It is an old edition but I am okay with it, I tasted the power of xapian while using recoll. I read that xapian is a powerful database building package for character strings, and indexes a directory of files really well. I want to use xapian-omega as a customisable

Hi, all: I check out the trunk code from svn yesterday *svn co svn://svn.xapian.org/xapian/trunk xapian* compile process: *./bootstrap* *mkdir build* *cd build* *../configure --disable-documentation* *make* then the error occur: cd xapian-applications/omega && make all make[1]: Entering directory `/home/white127/xapian-svn/build/xapian-applications/omega' /usr/bin/perl