For now, as a workaround, I open the db, do my request, close it and
repeat the process 5/10 sec later. I hope it does not add to much
overhead ?! Anyway, it owuld be nice to have this fixed in one way or
another.
Thanks for your answer David.
Best regards
2014-12-16 9:02 GMT+01:00 David Bremner
For now, as a workaround, I open the db, do my request, close it and
repeat the process 5/10 sec later. I hope it does not add to much
overhead ?! Anyway, it owuld be nice to have this fixed in one way or
another.
Thanks for your answer David.
Best regards
2014-12-16 9:02 GMT+01:00 David Bremner
Matt writes:
> 2014-12-15 21:41 GMT+01:00 David Bremner :
>> Matt writes:
>>
> But for exceptions in general, yes the notmuch library does need to be
> fixed to allow the caller of functions to distinguish between things
> like "no matches found" and "an exception occurred, so
Matt matta...@gmail.com writes:
2014-12-15 21:41 GMT+01:00 David Bremner da...@tethera.net:
Matt matta...@gmail.com writes:
But for exceptions in general, yes the notmuch library does need to be
fixed to allow the caller of functions to distinguish between things
like no matches found
2014-12-15 21:41 GMT+01:00 David Bremner :
> Matt writes:
>
>>> > But for exceptions in general, yes the notmuch library does need to be
>>> > fixed to allow the caller of functions to distinguish between things
>>> > like "no matches found" and "an exception occurred, so it's unknown if
>>> >
Matt writes:
>> > But for exceptions in general, yes the notmuch library does need to be
>> > fixed to allow the caller of functions to distinguish between things
>> > like "no matches found" and "an exception occurred, so it's unknown if
>> > any messages match the search". That's a general
> > But for exceptions in general, yes the notmuch library does need to be
> > fixed to allow the caller of functions to distinguish between things
> > like "no matches found" and "an exception occurred, so it's unknown if
> > any messages match the search". That's a general class of library
> >
But for exceptions in general, yes the notmuch library does need to be
fixed to allow the caller of functions to distinguish between things
like no matches found and an exception occurred, so it's unknown if
any messages match the search. That's a general class of library
interface bugs
Matt matta...@gmail.com writes:
But for exceptions in general, yes the notmuch library does need to be
fixed to allow the caller of functions to distinguish between things
like no matches found and an exception occurred, so it's unknown if
any messages match the search. That's a general
On Thu, 04 Nov 2010 12:31:48 -0700, Carl Worth wrote:
> On Tue, 15 Jun 2010 11:03:55 +0200, "Sebastian Spaeth" wrote:
> > > A Xapian exception occurred finding message: The revision being read
> > > has been discarded - you should call Xapian::Database::reopen() and
> > > retry the
On Thu, 04 Nov 2010 12:31:48 -0700, Carl Worth cwo...@cworth.org wrote:
On Tue, 15 Jun 2010 11:03:55 +0200, Sebastian Spaeth wrote:
A Xapian exception occurred finding message: The revision being read
has been discarded - you should call Xapian::Database::reopen() and
retry the
On Tue, 15 Jun 2010 11:03:55 +0200, "Sebastian Spaeth" wrote:
> > A Xapian exception occurred finding message: The revision being read
> > has been discarded - you should call Xapian::Database::reopen() and
> > retry the operation.
> > It makes the Python bindings almost useless to me.
>
>
On Tue, 15 Jun 2010 11:03:55 +0200, Sebastian Spaeth sebast...@sspaeth.de
wrote:
A Xapian exception occurred finding message: The revision being read
has been discarded - you should call Xapian::Database::reopen() and
retry the operation.
It makes the Python bindings almost useless
> A Xapian exception occurred finding message: The revision being read
> has been discarded - you should call Xapian::Database::reopen() and
> retry the operation.
> It makes the Python bindings almost useless to me.
Not sure, if the python bindings should simply drop and reopen a
database
On Tue, 15 Jun 2010 11:03:55 +0200, "Sebastian Spaeth" wrote:
> > A Xapian exception occurred finding message: The revision being read
> > has been discarded - you should call Xapian::Database::reopen() and
> > retry the operation.
> > It makes the Python bindings almost useless to me.
>
>
A Xapian exception occurred finding message: The revision being read
has been discarded - you should call Xapian::Database::reopen() and
retry the operation.
It makes the Python bindings almost useless to me.
Not sure, if the python bindings should simply drop and reopen a
database
On Tue, 15 Jun 2010 11:03:55 +0200, Sebastian Spaeth sebast...@sspaeth.de
wrote:
A Xapian exception occurred finding message: The revision being read
has been discarded - you should call Xapian::Database::reopen() and
retry the operation.
It makes the Python bindings almost useless
Is anything happening about:
A Xapian exception occurred finding message: The revision being read
has been discarded - you should call Xapian::Database::reopen() and
retry the operation.
?
It makes the Python bindings almost useless to me.
dme.
--
David Edmondson, http://dme.org
Is anything happening about:
A Xapian exception occurred finding message: The revision being read
has been discarded - you should call Xapian::Database::reopen() and
retry the operation.
?
It makes the Python bindings almost useless to me.
dme.
--
David Edmondson, http://dme.org
19 matches
Mail list logo
