Re: Re: [Xapian-commits] 9092: trunk/xapian-core/ trunk/xapian-core/api/ trunk/xapian-core/common/ trunk/xapian-core/include/xapian/

On Sat, Jun 30, 2007 at 06:27:01PM +0100, Richard Boulton wrote:
> I was thinking that it would probably be useful to have a 
> Xapian::Document::get_database_name() method, to allow the database that 
> a document came from (in a multi-database situation) to be obtained.

What do you see this new method being useful for?  Not saying it isn't
useful, but I don't see a use immediately - in the case of wanting to
be able to "refile" a modified document, there can only be one database
(we don't support writable multi-databases).

It might be better to simply return the "multi-docid" here rather than
introduce API complications.

> For a Flint database, this would return the path that was used to open 
> the database.  For a remote (TCP) database, it would return a string 
> indicating the host and port that the database is at (probably in a 
> pseudo URL form something like "remotetcp://host:port/"), and something 
> similar for a remote progsrv database.  Not sure what an inmemory one 
> would return...

We already have a "textual form" for most database backends - that used
in a stub database file.  There isn't one for InMemory though.

> Alternatively, databases could have a new "set_name()" method which sets 
> the name to return (possibly with something like the above as the 
> default) to avoid having to do long string compares to work out which 
> database a document came from.

Note that long string comparisons are only really slower than short ones
if there are a lot of non-matches with a long prefix that matches the

Latest patches for win32 build files

Hi all,

Some small patches are attached for the Win32 build files. Also, 
currently it's failing a test on some of the new stuff:
...
Running test: spell1... ok
Running test: spell2... ok
Running test: spell3....flint\dbw\flintlock - The process cannot access 
the file because it is being used by another process.
.flint\dbw\postlist.DB - The process cannot access the file because it 
is being used by another process.
.flint\dbw\record.DB - The process cannot access the file because it is 
being used by another process.
.flint\dbw\termlist.DB - The process cannot access the file because it 
is being used by another process.
  DatabaseLockErrorDatabaseLockError: Unable to acquire database write 
lock on .flint/dbw
Running test: spell4... ok
...

Cheers

Charlie

Index: win32_api.mak
===================================================================
--- win32_api.mak	(revision 9118)
+++ win32_api.mak	(working copy)
 <at>  <at>  -31,7 +31,9  <at>  <at> 

Re: Latest patches for win32 build files

Charlie Hull wrote:
> Hi all,
> 
> Some small patches are attached for the Win32 build files.

Applied.

> Also, currently it's failing a test on some of the new stuff:

I see the problem - the testsuite is at fault really.  I'll try and fix it.

--

-- 
Richard

Re: Latest patches for win32 build files

Richard Boulton wrote:
> I see the problem - the testsuite is at fault really.  I'll try and fix it.

I've disabled the test on windows for now - and created bug #177 so we 
don't forget to fix this properly.  It's definitely a testsuite bug, 
however.

--

-- 
Richard

Website

I've had to move the website onto a different partition on ixion. It
should all be running happily off the new one, and existing scripts
etc. should work fine. Let me know if there are any problems.

J

--

-- 
/--------------------------------------------------------------------------\
  James Aylett                                                  xapian.org
  james <at> tartarus.org                               uncertaintydivision.org