similar to: Patch for perl Search::Xapian spelling

This is my test case, what am I doing wrong? It seems that the API is used incorrectly, but I cannot find the problem... --- 8< --- #!/usr/bin/perl use Search::Xapian qw(:all); use strict; my $xa = new Search::Xapian::WritableDatabase ("/tmp/xapian", DB_CREATE_OR_OVERWRITE); my $indexer = Search::Xapian::TermGenerator->new();

Greets, I'm giving a stab at patching the CPAN module to add the missing WritableDatabase::add_spelling and remove_spelling, but need a bit of guidance since I'm coming in cold, and pressed for time (aren't we all). I've modified XS/WritableDatabase.xs and added the two necessary functions, and also added the two basic tests in t/index.t. Compilation completes cleanly, but

Hi Guys, Here's a simple test case that causes a segfault with the perl bindings patched to enable spelling correction: use strict; use warnings; use Search::Xapian; my $db = Search::Xapian::WritableDatabase->new("test.db", Search::Xapian::DB_CREATE_OR_OPEN); if (!defined($db)) { die("Failed to open xapian_database: $!"); } my $indexer =

On Mon, Mar 27, 2023 at 11:46:04AM +0000, Eric Wong wrote: > I'm using Search::Xapian XS from Debian stable and I'm getting what > appears to be an unwrapped C++ exception: > > terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' > > Using `eval' from Perl5 doesn't seem effective in catching it. > > I'm using

Resurrecting an old thread from 2012! Finally got back to working on this. I have been stuck in JavaScript land for too long. Come to find out, on windows, perl does indeed define open to be win32_open and close to be win32_close. This is done in perl/lib/CORE/win3iop.h. So, to get past this problem, I had to modify Xapian.xs to do an #undef of open and close if WIN32 is defined. Also, I had

Hi All, I'm using the TermGenerator::index_text() on version 1.0.4 with the FLAG_SPELLING turned on, because the new spelling suggestion stuff seems awesome, but I'm getting a segv. (gdb) bt #0 0xb7ae153c in Xapian::WritableDatabase::add_spelling (this=0xa553988, word=@0xbff97724, freqinc=1) at ./include/xapian/ base.h:154 #1 0xb7becf47 in

Hi, The Perl module Search::Xapian's README file ends with these lines: ===================================================================== This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. ===================================================================== (http://cpansearch.perl.org/src/OLLY/Search-Xapian-1.2.4.0/README) But

The disclaimer automatically added and is not intended to limit legitimate discourse, and any code I write for this is expected to be licensed under whatever license the original work is using. I haven't tried compiling latest code under visual studio yet (is this possible?). I wonder if there is a way to tell gcc to not mangle the names during cross compile. I was able to successfully

Greets, I suppose this isn't a major issue, but are there any plans to complete the spelling suggestion facility across a search cluster? I seem to recall reading somewhere in the docs that it's TODO. Regards Henry

Dear Olly Betts, I think the tests for the perl module Search-Xapian-1.2.21.0 might be fewer in number than the perl tests included with xapian-bindings-1.2.21. If some of the tests have similar but modified content I do not know. I am not so skilled as to interpret the compared test results. If you want to suggest a paired earlier version of Xapian to a specific xapian.bindings version, I might

I'm using Search::Xapian XS from Debian stable and I'm getting what appears to be an unwrapped C++ exception: terminate called after throwing an instance of 'Xapian::DatabaseModifiedError' Using `eval' from Perl5 doesn't seem effective in catching it. I'm using postlist_begin, postlist_end and ++ to iterate a PositionIterator, and reading XS/*Iterator.xs, I see the

On Tue, Sep 12, 2017 at 04:47:52PM -0400, Alex Aminoff wrote: >         my $filterepoch = time() - ($datefilter * 60 * 60 * 24); >         my $filterquery = > Xapian::Query->new(OP_VALUE_GE,I_DATE,$filterepoch); I think your issue here is that $filterepoch is a number rather than a string (a Perl scalar can have different representations internally). In t/valuerange.t this testcase

Hi, Trying to learn Search::Xapian and be better at perl at the same time, I'm stuck, at the DB_CREATE_OR_OPEN error. Perl says this: ~/dev/sandbox/Xapian-perl$ ./Index1-Xap.pl 100-objects-v1.csv db "db" is not exported by the Search::Xapian module Can't continue after import errors at ./Index1-Xap.pl line 7. BEGIN failed--compilation aborted at ./Index1-Xap.pl line 7. What I

Greets, WRT this discussion: http://lists.xapian.org/pipermail/xapian-discuss/2009-November/007300.html Richard recommends calling flush() before closing a index database segment, etc. Well, I can confirm that calling flush() is *required* before calling close() since close() on it's own does not commit/flush any pending writes/whatever unless the Perl script terminates, etc. So, for a

On Mon, Sep 05, 2016 at 01:51:26PM +0200, Markus W?rle wrote: > I am currently using xapian 1.2.23 with the Search::Xapian perl > bindings. I'd like to upgrade to 1.4.0, but it seems that there is no > suitable Search::Xapian available, and the SWIG-generated bindings are > marked as experimental. So, my question is: Do I have to wait for the > new API to get stable, or is

Hi Everyone, I?m a student in Peking University, China, my name is Xiaobing Liu, I?m interest in Spelling correction project. I think Xapian?s Spelling correction is based on edit distance with trusted dictionary. I have some questions about the spelling correction algorithm. 1. The Spelling correction algorithm depends on which dictionary, the dictionary in inverted index or other

I've uploaded Xapian 1.2.3 (including Search::Xapian 1.2.3.0). As usual you can download from: http://xapian.org/download You can read an overview of the release here: http://trac.xapian.org/wiki/ReleaseOverview/1.2.3 The full lists of user-visible changes are linked to from there, and from the "[news]" links on the download page. As always, if you encounter problems, please

Olly, The cygwin linker requires -shared, otherwise WinMain at 16 will not be skipped. BTW: mingw also. But this should test and fix someone else. -- Reini Urban http://phpwiki.org/ http://murbreak.at/ http://spacemovie.mur.at/ http://helsinki.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: Search-Xapian-1.0.2.0-cyg.patch Type:

On Thu, Sep 19, 2019 at 08:12:58PM +0000, Alyssa Ross wrote: > > Thanks for spotting, applied in git. > > Where is the appropriate git repository? Sorry, it's a bit obscure: https://git.xapian.org/?p=xapian;a=tree;f=search-xapian;hb=refs/heads/svn/1.2 We've now retired the 1.2 release branch apart from this directory so it perhaps should be re-homed in its own repo, but

Greetings, I've been wondering about the index format and backwards compatibility. We're using the dev version (for chert) and each svn up means that any indexes created prior to this revision cannot be read. Is this purely a cautious move to prevent errors, and, barring any obvious index format changes, can I safely force the current revision to read existing indexes? eg, by