Displaying 2 results from an estimated 2 matches for "cancel_transaction".
2004 May 05
1
buffered tables, sessions, and transactions
...rg/docs/apidoc/html/classXapian_1_1WritableDatabase.html#a7
This is actually very easy to implement like so:
* begin_transaction flushes any pending changes and sets an
"in_transaction" flag
* if "in_transaction" is set, we ignore explicit flushes and don't autoflush
* cancel_transaction closes and reopens the Btree table (or calls a
new method of Btree which has this effect but without all the file
descriptor and memory allocation releasing and reobtaining)
* commit_transaction flushes any pending changes and clears the
"in_transaction" flag
That's a lot of...
2009 Dec 23
1
flush() definitely required before close()
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