#include <database.h>
Inheritance diagram for Xapian::WritableDatabase:
Public Methods | |
virtual | ~WritableDatabase () |
Destroy this handle on the database. More... | |
WritableDatabase () | |
Create an empty WritableDatabase. More... | |
WritableDatabase (Database::Internal *internal) | |
WritableDatabase (const WritableDatabase &other) | |
Copying is allowed. More... | |
void | operator= (const WritableDatabase &other) |
Assignment is allowed. More... | |
void | flush () |
Flush to disk any modifications made to the database. More... | |
void | begin_transaction () |
Begin a transaction. More... | |
void | commit_transaction () |
End the transaction currently in progress, committing the modifications made to the database. More... | |
void | cancel_transaction () |
End the transaction currently in progress, cancelling the potential modifications made to the database. More... | |
Xapian::docid | add_document (const Xapian::Document &document) |
Add a new document to the database. More... | |
void | delete_document (Xapian::docid did) |
Delete a document in the database. More... | |
void | replace_document (Xapian::docid did, const Xapian::Document &document) |
Replace a given document in the database. More... | |
std::string | get_description () const |
Introspection method. More... |
|
Destroy this handle on the database. If there are no copies of this object remaining, the database will be closed, and if there are any sessions or transactions in progress these will be ended. |
|
Create an empty WritableDatabase.
|
|
Copying is allowed. The internals are reference counted, so copying is cheap. |
|
Add a new document to the database. This method adds the specified document to the database, returning a newly allocated document ID. Note that this does not mean the document will immediately appear in the database; see flush() for more details. As with all database modification operations, the effect is atomic: the document will either be fully added, or the document fails to be added and an exception is thrown (possibly at a later time when the session is ended or flushed). If a session is not in progress when this method is called, a session will be started.
|
|
Begin a transaction. For the purposes of Xapian, a transaction is a group of modifications to the database which are grouped together such that either all or none of them will succeed. Even in the case of a power failure, this characteristic should be preserved (as long as the filesystem isn't corrupted, etc). Transactions are only available with certain access methods, and as you might expect will generally have a fairly high performance cost. A transaction may only be begun within a session, see begin_session().
|
|
End the transaction currently in progress, cancelling the potential modifications made to the database. If an error occurs in this method, an exception will be thrown, but the transaction will be cancelled anyway.
|
|
End the transaction currently in progress, committing the modifications made to the database. If this completes successfully, all the database modifications made during the transaction will have been committed to the database. If an error occurs, an exception will be thrown, and none of the modifications made to the database during the transaction will have been applied to the database. Whatever occurs, after this method the transaction will no longer be in progress.
|
|
Delete a document in the database.
|
|
Flush to disk any modifications made to the database. For efficiency reasons, when performing multiple updates to a database it is best (indeed, almost essential) to make as many modifications as memory will permit in a single pass through the database. To ensure this, Xapian performs modifications in "sessions". Sessions are begun and ended implicitly, when the database is first modified, or closed. Flush may be called at any time during a modification session to ensure that the modifications which have been made are written to disk: if the flush succeeds, all the preceding modifications will have been written to disk. If any of the modifications fail, an exception will be thrown and the database will be left in a state in which each separate addition, replacement or deletion operation has either been fully performed or not performed at all: it is then up to the application to work out which operations need to be repeated. If called within a transaction, this will flush database modifications made before the transaction was begun, but will not flush modifications made since begin_transaction() was called. Beware of calling flush too frequently: this will have a severe performance cost. Note that flush need not be called explicitly: it will be called automatically when the database is closed, or when a sufficient number of modifications have been made.
|
|
Introspection method.
Reimplemented from Xapian::Database. |
|
Assignment is allowed. The internals are reference counted, so assignment is cheap. Note that only an WritableDatabase may be assigned to an WritableDatabase: an attempt to assign a Database is caught at compile-time. |
|
Replace a given document in the database.
|