Displaying 20 results from an estimated 2000 matches similar to: "Re: [Xapian-commits] Changes in xapian/xapian-applications/queryserver/ xapian/xapian-applications/queryserver/source/"
2007 Oct 19
1
Re: [Xapian-commits] 9476: trunk/xapian-core/ trunk/xapian-core/include/xapian/ trunk/xapian-core/queryparser/ trunk/xapian-core/tests/
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
2015 May 03
2
Make Xapian accept all characters
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
2009 Jun 01
2
Xapian .lemony files
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.
2004 Oct 22
1
Re: [Xapian-commits] Changes in xapian/xapian-bindings/ xapian/xapian-bindings/python/docs/
On Thu, Oct 21, 2004 at 05:45:42PM +0100, Olly Betts wrote:
> Log message:
> python/docs/bindings.html: Remove documentation explicitly saying
> how we wrap Xapian::QueryParser and Xapian::Stem since we wrap them
> exactly as we wrap everything else we don't mention! Also mention
> simpleexpand example.
The point of this comment was to highlight that they exist within the
2010 Jan 28
3
Problem getting Xapian working with Burmese
On Fri, Aug 21, 2009 at 02:44:44PM +0200, emmanuel at engelhart.org wrote:
>> I want to update my request.
>> Is my question bad formulated? too trivial? ... or maybe pretty
>> complicated/unclear?
>
>I think nobody answered as it was hard to follow your example because
>the Burmese characters seem to have been mangled (at least the message I
>received wasn't
2018 Sep 30
1
xapian parser bug?
On Sun, Sep 30, 2018 at 09:05:25AM -0300, David Bremner wrote:
> if (str.find (' ') != std::string::npos)
> query_str = '"' + str + '"';
> else
> query_str = str;
>
> return parser.parse_query (query_str, NOTMUCH_QUERY_PARSER_FLAGS, term_prefix);
I wouldn't recommend trying to generate strings to feed to
2005 Dec 15
6
Dynamic Text Replacement
I noticed there are a lot of PHP based dynamic text replacement
examples out there such as:
http://artypapers.com/csshelppile/pcdtr/
Is there anything like this for Ruby / Rails? I know there''s always
SiFR but that method is often frustrating because I''ve noticed
significant slow down in page load time even on pages that use it
sparingly.
2007 Jun 11
3
Xapian 1.0.1 released
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
2007 Jun 11
3
Xapian 1.0.1 released
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
2011 Sep 14
1
Integrated Chinese tokenizer SCWS in xapian-core
Xapian is a very excellent open source search engine library, but there is no native support for Chinese word segmentation in queryparser and termgenerator.
Therefore, I modified small amount of source codes, integrated into the SCWS tokenizer, that is the same open-source and developped by myself.
Anyone can obtain the patch from below URL. After patching, Xapian::QueryParser::parse_query and
2015 May 04
2
Make Xapian accept all characters
Ok, but suppose I have a complex query, something like "(a OR b) AND NOT c OR ##". Do I have to parse the query by myself?
> Date: Mon, 4 May 2015 03:03:24 +0100
> From: olly at survex.com
> To: lautaromedrano at hotmail.com
> CC: xapian-discuss at lists.xapian.org
> Subject: Re: [Xapian-discuss] Make Xapian accept all characters
>
> On Sun, May 03, 2015 at
2009 Jan 15
2
Xapian core build failure under gcc 2.95
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
2007 Jun 12
1
Empty results OMEGA with XAPIAN 1.0.1
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
2018 Sep 30
3
xapian parser bug?
On Sun, Sep 30, 2018 at 09:50:30AM +0100, James Aylett wrote:
> Note that I'm using 1.4.7, and from your output I believe you're not
> (the * in the query description I believe doesn't happen in those
> situations any more).
1.4.4 and later eliminate redundant 0 scaling factors, but this one
isn't actually redundant:
> > Query(((Tmail AND 0 * XSUBJECTnot at 1)
2018 Sep 29
2
xapian parser bug?
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
2014 Oct 30
2
Does Xapian support retrieval optional?
Hi,
I've been using Xapian for a while. But there is a scene I don't know
whether supported already.
Suppose:
1. Raw query: how to make pizza
2. Parsed query: how AND to AND make AND pizza
3. Documents:
d1: how to make pizza at home
d2: 3 ways to make pizza
d3: make pizza in 4 easy steps
Question:
1. During searching process, how to retrieve d2, d3 (although they don't
2004 May 17
1
xapian & debian
This is mostly for Richard, but others may have useful thoughts too.
I just took a look at the debian stuff. It's generally looking good
(though I haven't actually tried to build the debs). A few comments
on items in TODO:
> xapian-doc: in index.html, there is one broken link (which occurs in
> two places, pointing to the full source documentation, since we don't
>
2016 Dec 29
2
Formulating Advanced Queries with Xapian-Omega
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
2005 Dec 15
6
Navigation menu
I have a navigation menu that contains a link per controller in my
application.
This menu is the same for all controllers, but I want this behaviour:
<a>Users</a>
<span>Statistics</span>
and
<span>Users</span>
<a>Statistics</a>
depending on the page you''re currently on.
I''ve put a <render :partial =>
2010 Apr 15
1
Xapian 1.0.19 released
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