search for: xapia

Displaying 4 results from an estimated 4 matches for "xapia".

Did you mean: xapian
2018 Sep 19
2
Couldn't detect type of database
...jwl 383213568 Aug 28 23:44 postlist.glass -rw-rw-r-- 1 jwl jwl 203341824 Aug 28 23:44 termlist.glass -rw-rw-r-- 1 jwl jwl         0 Aug 28 23:44 flintlock I know that I was using 1.4.1 before, so I reinstalled that version and now delve decided that the db was OK, however when I went to install Xapia./XS/WritableDatabase.xs:30:47: error: missing binary operator before token "("  #if defined XAPIAN_AT_LEAST && XAPIAN_AT_LEAST(1,5,0)                                                ^ ./XS/QueryParser.xs:54:47: error: missing binary operator before token "("  #if defi...
2018 Sep 19
0
Couldn't detect type of database
...- 1 jwl jwl 203341824 Aug 28 23:44 termlist.glass > -rw-rw-r-- 1 jwl jwl         0 Aug 28 23:44 flintlock This error just doesn't make sense to me - it should be impossible to get it when there's a file "current.1/iamglass", as there is here (unless you were running an ancient Xapian from before glass was added). I'd check that the code giving the exception is actually looking at the same directory your "ls -l" is. If you think it is, then I'd try "xapian-delve current.1", and if that fails "xapian-check current.1". > I know that I w...
2018 Sep 20
1
Couldn't detect type of database
Hi, Olly, I have no idea what was going on.  I installed xapian from Ubuntu repos and had the issue.  xapian-delve and xapian-check gave me the same errors.  I've now build the libs and perl bindings from source and all is well.  I do not know, but I'm happy it's working again. Thanks, Jim. On 09/19/2018 04:23 PM, Olly Betts wrote: > On Wed,...
2005 Oct 08
1
*wildcard* support?
Hello, First I wanted to say thanks for a great piece of software, thanks Olly and others who've contributed! I know that Xapian supports right-truncating, if that's the proper name for wildcard support, as in a search for "xapia*". I don't believe Xapian supports wildcards on both sides of a term, correct? Is this something that is technically unfeasable, unpalatable for performance reasons, or just not...