pydoc > xapian

πŸ“– NAME

🐍 Help on package xapian β€” a Xapian search engine library binding.

πŸ“– DESCRIPTION

πŸ”§ Xapian is a highly adaptable toolkit which allows developers to easily add advanced πŸ“Š indexing and search facilities to their own applications. It has built-in support for several families of βš–οΈ weighting models and also supports a rich set of πŸ” boolean query operators.

πŸ“š In addition to the doc strings provided by this python library, you may wish to look at the library's overall documentation, either installed along with the bindings or online at <https://xapian.org/docs/bindings/python/>, as well as the library's documentation, possibly installed with the library or with its development files, or again online at <https://xapian.org/docs/>.

πŸ“¦ PACKAGE CONTENTS

πŸ“š CLASSES

πŸ”΄ Error (base exception class)

All Xapian exceptions inherit from Error. Provides context and error message retrieval.

Inherited from builtins.Exception: __new__, args.

Inherited from builtins.BaseException: __delattr__, __getattribute__, __reduce__, __setstate__, with_traceback, __cause__, __context__, __dict__, __suppress_context__, __traceback__.

πŸ”΄ AssertionError

Thrown when a logical assertion inside Xapian fails (debug builds). Indicates a bug in Xapian.

Inherits from LogicError β†’ Error.

πŸ”΄ InvalidArgumentError

Thrown when an invalid argument is supplied.

Inherits from LogicError β†’ Error.

πŸ”΄ InvalidOperationError

Thrown when an operation is attempted in an invalid context.

Inherits from LogicError β†’ Error.

πŸ”΄ UnimplementedError

Thrown when a method is not implemented (e.g., on a remote backend).

Inherits from LogicError β†’ Error.

πŸ”΄ RuntimeError

Base class for runtime errors. All subclasses below inherit from RuntimeError β†’ Error.

πŸ”΄ DatabaseError

Base for database-related errors.

Inherits from RuntimeError β†’ Error.

πŸ”΄ DatabaseClosedError

Attempt to access a closed database.

Inherits from DatabaseError.

πŸ”΄ DatabaseCorruptError

Database corruption detected.

Inherits from DatabaseError.

πŸ”΄ DatabaseCreateError

Failure to create a database.

Inherits from DatabaseError.

πŸ”΄ DatabaseLockError

Failure to lock a database.

Inherits from DatabaseError.

πŸ”΄ DatabaseModifiedError

Database was modified during a read operation. Call reopen() to recover.

Inherits from DatabaseError.

πŸ”΄ DatabaseOpeningError

Failure to open a database.

Inherits from DatabaseError.

πŸ”΄ DatabaseNotFoundError

Database not present at the specified path.

Inherits from DatabaseOpeningError.

πŸ”΄ DatabaseVersionError

Database in an unsupported format (too old or too new).

Inherits from DatabaseOpeningError.

πŸ”΄ DocNotFoundError

Requested document does not exist in the database.

Inherits from RuntimeError.

πŸ”΄ FeatureUnavailableError

Feature not available (e.g., during compaction).

Inherits from RuntimeError.

πŸ”΄ InternalError

Internal Xapian error (should not happen).

Inherits from RuntimeError.

πŸ”΄ NetworkError

Base for network-related errors.

Inherits from RuntimeError.

πŸ”΄ NetworkTimeoutError

Network timeout occurred.

Inherits from NetworkError.

πŸ”΄ QueryParserError

Query parsing failed.

Inherits from RuntimeError.

πŸ”΄ RangeError

Value out of range.

Inherits from RuntimeError.

πŸ”΄ SerialisationError

Error during serialisation/deserialisation.

Inherits from RuntimeError.

πŸ”΄ WildcardError

Wildcard expansion error.

Inherits from RuntimeError.

πŸ—‚οΈ Database

Provides access to a database or group of databases. Used with Enquire for searching.

Constructor: Database(*args) β€” Copying (reference counted) or open from path. Throws InvalidArgumentError, DatabaseOpeningError, DatabaseVersionError.

πŸ—‚οΈ WritableDatabase (extends Database)

Adds write operations: indexing, updating, deleting documents.

πŸ—‚οΈ Compactor

Utility to compact or merge databases. Deprecated in favor of Database::compact().

Class constants: STANDARD=0, FULL=1, FULLER=2.

πŸ—‚οΈ Document

Represents a document in the database.

πŸ—‚οΈ Enquire

Performs searches on a database.

πŸ—‚οΈ MSet

Result set from a search.

πŸ—‚οΈ MSetItem

Represents a single result in an MSet.

πŸ—‚οΈ ESet

Result set from query expansion.

πŸ—‚οΈ ESetItem

πŸ—‚οΈ RSet

Relevance set for query expansion.

πŸ—‚οΈ Query

Represents a query. Can be built from operators and subqueries.

πŸ—‚οΈ QueryParser

Parses a human-readable query string into a Query object.

πŸ—‚οΈ Stem

Stemming algorithm.

πŸ—‚οΈ Stopper (abstract)

Base class for stop word lists.

πŸ—‚οΈ SimpleStopper

Simple stop word list.

πŸ—‚οΈ TermGenerator

Converts text into terms.

πŸ—‚οΈ ValueRangeProcessor (abstract)

Base for range processors.

πŸ—‚οΈ StringValueRangeProcessor

Range processor for string values.

πŸ—‚οΈ DateValueRangeProcessor (deprecated, use DateRangeProcessor)

πŸ—‚οΈ NumberValueRangeProcessor (deprecated, use NumberRangeProcessor)

πŸ—‚οΈ RangeProcessor (abstract)

Base for range processors (new API).

πŸ—‚οΈ DateRangeProcessor

πŸ—‚οΈ NumberRangeProcessor

πŸ—‚οΈ ExpandDecider (abstract)

Base for expansion deciders.

πŸ—‚οΈ ExpandDeciderAnd

Logical AND of two deciders.

πŸ—‚οΈ ExpandDeciderFilterPrefix

Filter by prefix.

πŸ—‚οΈ KeyMaker (abstract)

Base for key makers (sort keys).

πŸ—‚οΈ MultiValueKeyMaker

Key from multiple value slots.

πŸ—‚οΈ LatLongDistanceKeyMaker

Key from distance to a center point.

πŸ—‚οΈ LatLongCoord

Latitude/longitude coordinate.

πŸ—‚οΈ LatLongCoords

Sequence of coordinates.

πŸ—‚οΈ LatLongMetric (abstract)

Base for distance metrics.

πŸ—‚οΈ GreatCircleMetric

Great-circle distance.

πŸ—‚οΈ PostingSource (abstract)

Custom source of postings.

πŸ—‚οΈ FixedWeightPostingSource

Posting source with constant weight for all documents.

πŸ—‚οΈ ValuePostingSource (abstract)

Base for value-based posting sources.

πŸ—‚οΈ ValueWeightPostingSource

Weight from values in a slot (serialised with sortable_serialise()).

πŸ—‚οΈ DecreasingValueWeightPostingSource

Like ValueWeightPostingSource but for values known to decrease with docid.

πŸ—‚οΈ ValueMapPostingSource

Map values to weights via a mapping function.

πŸ—‚οΈ LatLongDistancePostingSource

Weight from distance to a center point.

πŸ—‚οΈ MatchDecider (abstract)

Base for match deciders (filter results).

πŸ—‚οΈ ValueSetMatchDecider

Filter documents where value is in a set.

πŸ—‚οΈ MatchSpy (abstract)

Base for match spies (collect statistics during search).

πŸ—‚οΈ ValueCountMatchSpy

Count occurrences of values in slots.

πŸ—‚οΈ Registry

Registry for weighting schemes, posting sources, etc.

πŸ—‚οΈ FieldProcessor (abstract)

Base for field processors (e.g., for query parser).

πŸ—‚οΈ Weight (abstract)

Base class for weighting schemes.

πŸ—‚οΈ BB2Weight

Implements the BB2 weighting scheme (Divergence from Randomness framework).

πŸ—‚οΈ BM25PlusWeight

BM25+ (BM25 with a lower bound).

πŸ—‚οΈ BM25Weight

Standard BM25 weighting.

πŸ—‚οΈ BoolWeight

Boolean weighting (all documents weight zero).

πŸ—‚οΈ CoordWeight

Coordinate Matching: each matching term scores one point.

πŸ—‚οΈ DLHWeight

DLH weighting scheme (parameter-free DFR).

πŸ—‚οΈ DPHWeight

DPH weighting scheme (parameter-free DFR).

πŸ—‚οΈ IfB2Weight

IfB2 weighting scheme.

πŸ—‚οΈ InL2Weight

InL2 weighting scheme.

πŸ—‚οΈ IneB2Weight

IneB2 weighting scheme.

πŸ—‚οΈ LMWeight

Language Model weighting.

πŸ—‚οΈ PL2PlusWeight

PL2+ weighting scheme.

πŸ—‚οΈ PL2Weight

PL2 weighting scheme.

πŸ—‚οΈ TfIdfWeight

TF-IDF weighting.

πŸ—‚οΈ TradWeight

Traditional probabilistic weighting.

πŸ—‚οΈ PostingIter

Iterator over postings.

πŸ—‚οΈ PostingItem

Element from a posting list.

πŸ—‚οΈ PositionIter

Iterator over positions.

πŸ—‚οΈ TermIter

Iterator over terms.

πŸ—‚οΈ TermListItem

Element from a term list.

πŸ—‚οΈ ValueIter

Iterator over values.

πŸ—‚οΈ ValueItem

Element from a value stream.

πŸ—‚οΈ ValueStreamItem

Element from a value stream (similar to ValueItem).

πŸ—‚οΈ ValueStreamIter

Iterator over value stream (ordered by docid).

πŸ—‚οΈ ESetIter

Iterator over ESet.

πŸ—‚οΈ LatLongCoordsIter

Iterator over LatLongCoords.

πŸ—‚οΈ MSetIter

Iterator over MSet.

πŸ—‚οΈ TermGenerator (already covered)

See above.

πŸ—‚οΈ Stem (already covered)

See above.

πŸ—‚οΈ StemImplementation (abstract)

Interface for custom stemmers.

πŸ—‚οΈ FieldProcessor (abstract, already covered)

See above.

πŸ—‚οΈ KeyMaker (abstract, already covered)

See above.

πŸ›οΈ CLASSES

πŸ—‚οΈ ValuePostingSource

ValuePostingSource is a base class for posting sources which read values from a document.

This class provides a default implementation which can be used to make it easy to write a PostingSource which looks at values in a document. It provides an implementation of many of the PostingSource methods based on a value stream.

You only need to subclass this if you want to implement a PostingSource which returns a subset of the documents in the database - for example, to return documents within a certain geographical region.

Subclasses should implement the next(), skip_to() and check() methods, and should also call the set_termfreq_*() methods to set the term frequency bounds.

This class was added in Xapian 1.2.23 and 1.3.5.

πŸ”§ Methods defined here:

void Xapian::ValuePostingSource::ValuePostingSource(Xapian::valueno slot_)

Parameters:

virtual bool Xapian::ValuePostingSource::at_end() const =0

At least one of next(), skip_to() or check() will be called before this method is first called.

virtual bool Xapian::ValuePostingSource::check(Xapian::docid did, double min_wt)

If it does, it must move to that document id, and return true. If it does not, it may either:

Generally, this method should act like skip_to() and return true if that can be done at little extra cost. Otherwise it should simply check if a particular docid is present, returning true if it is, and false if it isn't.

The default implementation calls skip_to() and always returns true.

Xapian will always call init() on a PostingSource before calling this for the first time.

Note: In the case of a multi-database search, the docid specified is the docid in the single subdatabase relevant to this posting source. See the init() method for details.

Parameters:

void Xapian::ValuePostingSource::done()

Calls to at_end() will return true after calling this method.

Added in 1.2.23 and 1.3.5.

Xapian::Database Xapian::ValuePostingSource::get_database() const

Added in 1.2.23 and 1.3.5.

Xapian::docid Xapian::ValuePostingSource::get_docid() const

This method may assume that it will only be called when there is a "current document". See get_weight() for details.

Note: In the case of a multi-database search, the returned docid should be in the single subdatabase relevant to this posting source. See the init() method for details.

Xapian::valueno Xapian::ValuePostingSource::get_slot() const

Added in 1.2.23 and 1.3.5.

bool Xapian::ValuePostingSource::get_started() const

Added in 1.2.23 and 1.3.5.

Xapian::doccount Xapian::ValuePostingSource::get_termfreq_est() const

It must always be true that: get_termfreq_min() <= get_termfreq_est() <= get_termfreq_max()

Xapian will always call init() on a PostingSource before calling this for the first time.

Xapian::doccount Xapian::ValuePostingSource::get_termfreq_max() const

Xapian will always call init() on a PostingSource before calling this for the first time.

Xapian::doccount Xapian::ValuePostingSource::get_termfreq_min() const

Xapian will always call init() on a PostingSource before calling this for the first time.

std::string Xapian::ValuePostingSource::get_value() const

Added in 1.2.23 and 1.3.5.

void Xapian::ValuePostingSource::set_termfreq_est(Xapian::doccount termfreq_est_)

Subclasses should set this if they are overriding the next(), skip_to() or check() methods.

Added in 1.2.23 and 1.3.5.

void Xapian::ValuePostingSource::set_termfreq_max(Xapian::doccount termfreq_max_)

Subclasses should set this if they are overriding the next(), skip_to() or check() methods.

Added in 1.2.23 and 1.3.5.

void Xapian::ValuePostingSource::set_termfreq_min(Xapian::doccount termfreq_min_)

Subclasses should set this if they are overriding the next(), skip_to() or check() methods to return fewer documents.

Added in 1.2.23 and 1.3.5.

void Xapian::ValuePostingSource::skip_to(Xapian::docid min_docid, double min_wt)

If the specified docid isn't in the list, position ourselves on the first document after it (or at_end() if no greater docids are present).

If the current position is already the specified docid, this method will leave the position unmodified.

If the specified docid is earlier than the current position, the behaviour is unspecified. A sensible behaviour would be to leave the current position unmodified, but it is also reasonable to move to the specified docid.

The default implementation calls next() repeatedly, which works but skip_to() can often be implemented much more efficiently.

Xapian will always call init() on a PostingSource before calling this for the first time.

Note: In the case of a multi-database search, the docid specified is the docid in the single subdatabase relevant to this posting source. See the init() method for details.

Parameters:

πŸ“‹ Methods inherited from PostingSource:

double Xapian::PostingSource::get_maxweight() const

const PostingSource* Xapian::PostingSource::release() const

You can hand ownership of a dynamically allocated PostingSource object to Xapian by calling release() and then passing the object to a Xapian method. Xapian will arrange to delete the object once it is no longer required.

void Xapian::PostingSource::set_maxweight(double max_weight)

This upper bound is used by the matcher to perform various optimisations, so if you can return a good bound, then matches will generally run faster.

This method should be called after calling init(), and may be called during iteration if the upper bound drops. It is probably only useful to call from subclasses (it was actually a "protected" method prior to Xapian 1.3.4, but that makes it tricky to wrap for other languages).

It is valid for the posting source to have returned a higher value from get_weight() earlier in the iteration, but the posting source must not return a higher value from get_weight() than the currently set upper bound, and the upper bound must not be increased (until init() has been called).

If you don't call this method, the upper bound will default to 0, for convenience when implementing "weight-less" PostingSource subclasses.

Parameters:

πŸ“¦ Data descriptors inherited from PostingSource:


❌ DocNotFoundError

Indicates an attempt to access a document not present in the database.

Method resolution order: DocNotFoundError β†’ RuntimeError β†’ Error β†’ builtins.Exception β†’ builtins.BaseException β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::DocNotFoundError::DocNotFoundError(const std::string &msg_, int errno_)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data and other attributes defined here:

πŸ“‹ Methods inherited from Error:

const std::string& Xapian::Error::get_context() const

This context is intended for use by Xapian::ErrorHandler (for example so it can know which remote server is unreliable and report the problem and remove that server from those being searched). But it's typically a plain-text string, and so also fit for human consumption.

const char* Xapian::Error::get_error_string() const

The system error string may come from errno, h_errno (on UNIX), or GetLastError() (on MS Windows). If there is no associated system error string, NULL is returned.

const std::string& Xapian::Error::get_msg() const

const char* Xapian::Error::get_type() const

πŸ“¦ Data descriptors inherited from Error:

πŸ“‹ Methods inherited from builtins.Exception:

πŸ“‹ Methods inherited from builtins.BaseException:

πŸ“¦ Data descriptors inherited from builtins.BaseException:


πŸ“„ Document

A handle representing a document in a Xapian database.

The Document class fetches information from the database lazily. Usually this behaviour isn't visible to users (except for the speed benefits), but if the document in the database is modified or deleted, then preexisting Document objects may return the old or new versions of data (or throw Xapian::DocNotFoundError in the case of deletion).

Since Database objects work on a snapshot of the database's state, the situation above can only happen with a WritableDatabase object, or if you call Database::reopen() on a Database object.

We recommend you avoid designs where this behaviour is an issue, but if you need a way to make a non-lazy version of a Document object, you can do this like so: doc = Xapian::Document::unserialise(doc.serialise());

πŸ”§ Methods defined here:

Xapian::Document::Document()

The iterator will return TermListItem objects.

Access to term frequency and position information is only available until the iterator has moved on.

Note that term frequency information is only meaningful for a document retrieved from a database. If term frequency information is requested for a document which was freshly created, an InvalidOperationError will be raised.

std::string Xapian::Document::get_description() const

void Xapian::Document::add_boolean_term(const std::string &term)

This method adds term to the document with wdf of 0 - this is generally what you want for a term used for boolean filtering as the wdf of such terms is ignored, and it doesn't make sense for them to contribute to the document's length.

If the specified term already indexes this document, this method has no effect.

It is exactly the same as add_term(term, 0).

This method was added in Xapian 1.0.18.

Parameters:

void Xapian::Document::add_posting(const std::string &tname, Xapian::termpos tpos, Xapian::termcount wdfinc=1)

Multiple occurrences of the term at the same position are represented only once in the positional information, but do increase the wdf.

If the term is not already in the document, it will be added to it.

Parameters:

void Xapian::Document::add_term(const std::string &tname, Xapian::termcount wdfinc=1)

Any existing positional information for the term will be left unmodified.

Parameters:

void Xapian::Document::add_value(Xapian::valueno slot, const std::string &value)

The new value will replace any existing value with the same number (or if the new value is empty, it will remove any existing value with the same number).

Parameters:

void Xapian::Document::clear_terms()

void Xapian::Document::clear_values()

std::string Xapian::Document::get_data() const

This is potentially a relatively expensive operation, and shouldn't normally be used during the match (e.g. in a PostingSource or match decider functor). Put data for use by match deciders in a value instead.

docid Xapian::Document::get_docid() const

NB If multiple databases are being searched together, then this will be the document id in the individual database, not the merged database!

If this document came from a database, return the document id in that database. Otherwise, return 0 (in Xapian 1.0.22/1.2.4 or later; prior to this the returned value was uninitialised).

std::string Xapian::Document::get_value(Xapian::valueno slot) const

Returns an empty string if no value with the given number is present in the document.

Parameters:

void Xapian::Document::remove_posting(const std::string &tname, Xapian::termpos tpos, Xapian::termcount wdfdec=1)

Note that the term will still index the document even if all occurrences are removed. To remove a term from a document completely, use remove_term().

Parameters:

Throws:

Xapian::termpos Xapian::Document::remove_postings(const std::string &term, Xapian::termpos term_pos_first, Xapian::termpos term_pos_last, Xapian::termcount wdf_dec=1)

Any instances of the term at positions >= term_pos_first and <= term_pos_last will be removed, and the wdf reduced by wdf_dec for each instance removed (the wdf will not ever go below zero though).

It's OK if the term doesn't occur in the range of positions specified (unlike remove_posting()). And if term_pos_first > term_pos_last, this method does nothing.

The number of postings removed.

Throws:

Added in Xapian 1.4.8.

void Xapian::Document::remove_term(const std::string &tname)

Parameters:

Throws:

void Xapian::Document::remove_value(Xapian::valueno slot)

std::string Xapian::Document::serialise() const

The document representation may change between Xapian releases: even between minor versions. However, it is guaranteed not to change if the remote database protocol has not changed between releases.

void Xapian::Document::set_data(const std::string &data)

Xapian treats the data as an opaque blob. It may try to compress it, but other than that it will just store it and return it when requested.

Parameters:

The iterator will return TermListItem objects.

Access to term frequency and position information is only available until the iterator has moved on.

Note that term frequency information is only meaningful for a document retrieved from a database. If term frequency information is requested for a document which was freshly created, an InvalidOperationError will be raised.

Xapian::termcount Xapian::Document::termlist_count() const

the number of different terms which index this document.

The iterator will return ValueItem objects, in ascending order of value number.

Xapian::termcount Xapian::Document::values_count() const

πŸ”§ Static methods defined here:

Xapian::Document::~Document()

πŸ“¦ Data descriptors defined here:


πŸ“Š ESet

Class representing a list of search results (expand set).

πŸ”§ Methods defined here:

Xapian::ESet::ESet()

Creates an empty ESet, mostly useful as a placeholder.

The iterator will return ESetItem objects.

std::string Xapian::ESet::get_description() const

ESetIterator Xapian::ESet::back() const

bool Xapian::ESet::empty() const

Xapian::termcount Xapian::ESet::get_ebound() const

This is a bound on size() if get_eset() had been called with maxitems set high enough that all results were returned.

Xapian::doccount Xapian::ESet::size() const

πŸ”§ Static methods defined here:

Xapian::ESet::~ESet()

πŸ“¦ Data descriptors defined here:


πŸ“ˆ ESetItem

An item returned from iteration of the ESet.

The item supports access to the following attributes:

πŸ”§ Methods defined here:

πŸ“¦ Data descriptors defined here:


πŸ” ESetIter

An iterator over the items in an ESet.

The iterator will return ESetItem objects.

πŸ”§ Methods defined here:


πŸ” Enquire

This class provides an interface to the information retrieval system for the purpose of searching.

Databases are usually opened lazily, so exceptions may not be thrown where you would expect them to be. You should catch Xapian::Error exceptions when calling any method in Xapian::Enquire.

Throws:

πŸ”§ Methods defined here:

Xapian::Enquire::Enquire(const Database &database, ErrorHandler *errorhandler_)

This specification cannot be changed once the Xapian::Enquire is opened: you must create a new Xapian::Enquire object to access a different database, or set of databases.

The database supplied must have been initialised (ie, must not be the result of calling the Database::Database() constructor). If you need to handle a situation where you have no databases gracefully, a database created with DB_BACKEND_INMEMORY can be passed here to provide a completely empty database.

Parameters:

Throws:

std::string Xapian::Enquire::get_description() const

void Xapian::Enquire::add_matchspy(MatchSpy *spy)

This matchspy will be called with some of the documents which match the query, during the match process. Exactly which of the matching documents are passed to it depends on exactly when certain optimisations occur during the match process, but it can be controlled to some extent by setting the checkatleast parameter to get_mset().

In particular, if there are enough matching documents, at least the number specified by checkatleast will be passed to the matchspy. This means that you can force the matchspy to be shown all matching documents by setting checkatleast to the number of documents in the database.

Parameters:

void Xapian::Enquire::clear_matchspies()

ESet Xapian::Enquire::get_eset(Xapian::termcount maxitems, const RSet &rset, int flags, double k, const Xapian::ExpandDecider *edecider=NULL, double min_wt=0.0) const

Parameters:

Returns an ESet object containing the results of the expand.

Throws:

MSet Xapian::Enquire::get_mset(Xapian::doccount first, Xapian::doccount maxitems, const RSet *omrset, const MatchDecider *mdecider=0) const

Parameters:

Returns a Xapian::MSet object containing the results of the query.

Throws:

const Xapian::Query& Xapian::Enquire::get_query() const

If called before set_query(), this will return a default initialised Query object.

The match set item to consider is specified by the which parameter, which may be a document ID, or an MSetItem object.

The iterator will return string objects.

void Xapian::Enquire::set_collapse_key(Xapian::valueno collapse_key, Xapian::doccount collapse_max=1)

Parameters:

The MSet returned by get_mset() will have only the "best" (at most) collapse_max entries with each particular value of collapse_key ("best" being highest ranked - i.e. highest weight or highest sorting key).

An example use might be to create a value for each document containing an MD5 hash of the document contents. Then duplicate documents from different sources can be eliminated at search time by collapsing with collapse_max = 1.

Another use is to group matches in a particular category (e.g. you might collapse a mailing list search on the Subject: so that there's only one result per discussion thread).

void Xapian::Enquire::set_cutoff(int percent_cutoff, double weight_cutoff=0)

Parameters:

void Xapian::Enquire::set_docid_order(docid_order order)

This order only has an effect on documents which would otherwise have equal rank. When ordering by relevance without a sort key, this means documents with equal weight. For a boolean match with no sort key, this means all documents.

Parameters:

void Xapian::Enquire::set_expansion_scheme(const std::string &eweightname_, double expand_k_=1.0) const

If you don't call this method, the default is as if you'd used: get_expansion_scheme("trad");

Parameters:

void Xapian::Enquire::set_query(const Xapian::Query &query, Xapian::termcount qlen=0)

Parameters:

void Xapian::Enquire::set_sort_by_key(Xapian::KeyMaker *sorter, bool reverse)

Parameters:

void Xapian::Enquire::set_sort_by_key_then_relevance(Xapian::KeyMaker *sorter, bool reverse)

Parameters:

void Xapian::Enquire::set_sort_by_relevance()

This is the default.

void Xapian::Enquire::set_sort_by_relevance_then_key(Xapian::KeyMaker *sorter, bool reverse)

Parameters:

void Xapian::Enquire::set_sort_by_relevance_then_value(Xapian::valueno sort_key, bool reverse)

Parameters:

void Xapian::Enquire::set_sort_by_value(Xapian::valueno sort_key, bool reverse)

Parameters:

void Xapian::Enquire::set_sort_by_value_then_relevance(Xapian::valueno sort_key, bool reverse)

Parameters:

void Xapian::Enquire::set_time_limit(double time_limit)

Matches with check_at_least set high can take a long time in some cases. You can set a time limit on this, after which check_at_least will be turned off.

Parameters:

Limitations: This feature is currently supported on platforms which support POSIX interval timers. Interaction with the remote backend when using multiple databases may have bugs.

void Xapian::Enquire::set_weighting_scheme(const Weight &weight_)

Parameters:

πŸ”§ Static methods defined here:

Xapian::Enquire::~Enquire()

πŸ“¦ Data descriptors defined here:

πŸ“¦ Data and other attributes defined here:


⚠️ Error

All exceptions thrown by Xapian are subclasses of Xapian::Error.

This class can not be instantiated directly - instead a subclass should be used.

Method resolution order: Error β†’ builtins.Exception β†’ builtins.BaseException β†’ builtins.object

πŸ”§ Methods defined here:

const std::string& Xapian::Error::get_context() const

This context is intended for use by Xapian::ErrorHandler (for example so it can know which remote server is unreliable and report the problem and remove that server from those being searched).

const char* Xapian::Error::get_error_string() const

The system error string may come from errno, h_errno (on UNIX), or GetLastError() (on MS Windows). If there is no associated system error string, NULL is returned.

const std::string& Xapian::Error::get_msg() const

const char* Xapian::Error::get_type() const

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“¦ Data and other attributes defined here:

πŸ“‹ Methods inherited from builtins.Exception:

πŸ“‹ Methods inherited from builtins.BaseException:

πŸ“¦ Data descriptors inherited from builtins.BaseException:


πŸ§ͺ ExpandDecider

Virtual base class for expand decider functor.

πŸ”§ Methods defined here:

Xapian::ExpandDecider::ExpandDecider()

const ExpandDecider* Xapian::ExpandDecider::release() const

You can hand ownership of a dynamically allocated ExpandDecider object to Xapian by calling release() and then passing the object to a Xapian method. Xapian will arrange to delete the object once it is no longer required.

πŸ”§ Static methods defined here:

virtual Xapian::ExpandDecider::~ExpandDecider()

πŸ“¦ Data descriptors defined here:


πŸ§ͺπŸ”— ExpandDeciderAnd

ExpandDecider subclass which rejects terms using two ExpandDeciders.

Terms are only accepted if they are accepted by both of the specified ExpandDecider objects.

Method resolution order: ExpandDeciderAnd β†’ ExpandDecider β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::ExpandDeciderAnd::ExpandDeciderAnd(const ExpandDecider *first_, const ExpandDecider *second_)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from ExpandDecider:

πŸ“¦ Data descriptors inherited from ExpandDecider:


πŸ§ͺπŸ”€ ExpandDeciderFilterPrefix

ExpandDecider subclass which restricts terms to a particular prefix.

ExpandDeciderFilterPrefix provides an easy way to choose terms with a particular prefix when generating an ESet.

Method resolution order: ExpandDeciderFilterPrefix β†’ ExpandDecider β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::ExpandDeciderFilterPrefix::ExpandDeciderFilterPrefix(const std::string &prefix_)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from ExpandDecider:

πŸ“¦ Data descriptors inherited from ExpandDecider:


🚫 FeatureUnavailableError

Indicates an attempt to use a feature which is unavailable.

Typically a feature is unavailable because it wasn't compiled in, or because it requires other software or facilities which aren't available.

Method resolution order: FeatureUnavailableError β†’ RuntimeError β†’ Error β†’ builtins.Exception β†’ builtins.BaseException β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::FeatureUnavailableError::FeatureUnavailableError(const std::string &msg_, int errno_)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data and other attributes defined here:

πŸ“‹ Methods inherited from Error:

πŸ“¦ Data descriptors inherited from Error:

πŸ“‹ Methods inherited from builtins.Exception:

πŸ“‹ Methods inherited from builtins.BaseException:

πŸ“¦ Data descriptors inherited from builtins.BaseException:


🧰 FieldProcessor

Base class for field processors.

πŸ”§ Methods defined here:

Xapian::FieldProcessor::FieldProcessor()

const FieldProcessor* Xapian::FieldProcessor::release() const

You can hand ownership of a dynamically allocated FieldProcessor object to Xapian by calling release() and then passing the object to a Xapian method. Xapian will arrange to delete the object once it is no longer required.

πŸ”§ Static methods defined here:

virtual Xapian::FieldProcessor::~FieldProcessor()

πŸ“¦ Data descriptors defined here:


βš–οΈ FixedWeightPostingSource

A posting source which returns a fixed weight for all documents.

This returns entries for all documents in the given database, with a fixed weight (specified by a parameter to the constructor).

Method resolution order: FixedWeightPostingSource β†’ PostingSource β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::FixedWeightPostingSource::FixedWeightPostingSource(double wt)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from PostingSource:

virtual void Xapian::PostingSource::next(double min_wt)=0

πŸ“¦ Data descriptors inherited from PostingSource:


🌍 GreatCircleMetric

Calculate the great-circle distance between two coordinates on a sphere.

Experimental - see https://xapian.org/docs/deprecation#experimental features

This uses the haversine formula to calculate the distance. Note that this formula is subject to inaccuracy due to numerical errors for coordinates on the opposite side of the sphere.

See https://en.wikipedia.org/wiki/Haversine_formula

Method resolution order: GreatCircleMetric β†’ LatLongMetric β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::GreatCircleMetric::GreatCircleMetric(double radius_)

This is useful for data sets in which the points are not on Earth (eg, a database of features on Mars).

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from LatLongMetric:

πŸ“¦ Data descriptors inherited from LatLongMetric:


βš–οΈπŸ“Š IfB2Weight

This class implements the IfB2 weighting scheme.

IfB2 is a representative scheme of the Divergence from Randomness Framework by Gianni Amati.

It uses the Inverse term frequency model (If), the Bernoulli method to find the aftereffect of sampling (B) and the second wdf normalization proposed by Amati to normalize the wdf in the document to the length of the document (H2).

For more information about the DFR Framework and the IfB2 scheme, please refer to: Gianni Amati and Cornelis Joost Van Rijsbergen, Probabilistic models of information retrieval based on measuring the divergence from randomness, ACM Transactions on Information Systems (TOIS) 20, (4), 2002, pp. 357-389.

Method resolution order: IfB2Weight β†’ Weight β†’ builtins.object

πŸ”§ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from Weight:

πŸ“¦ Data descriptors inherited from Weight:

πŸ“¦ Data and other attributes inherited from Weight:


βš–οΈπŸ“Š InL2Weight

This class implements the InL2 weighting scheme.

InL2 is a representative scheme of the Divergence from Randomness Framework by Gianni Amati. This weighting scheme is useful for tasks that require early precision.

It uses the Inverse document frequency model (In), the Laplace method to find the aftereffect of sampling (L) and the second wdf normalization proposed by Amati (H2).

For more information about the DFR Framework and the InL2 scheme, please refer to: Gianni Amati and Cornelis Joost Van Rijsbergen, ibid.

Method resolution order: InL2Weight β†’ Weight β†’ builtins.object

πŸ”§ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from Weight:

πŸ“¦ Data descriptors inherited from Weight:

πŸ“¦ Data and other attributes inherited from Weight:


βš–οΈπŸ“Š IneB2Weight

This class implements the IneB2 weighting scheme.

IneB2 is a representative scheme of the Divergence from Randomness Framework by Gianni Amati.

It uses the Inverse expected document frequency model (Ine), the Bernoulli method to find the aftereffect of sampling (B) and the second wdf normalization proposed by Amati (H2).

For more information about the DFR Framework and the IneB2 scheme, please refer to: Gianni Amati and Cornelis Joost Van Rijsbergen, ibid.

Method resolution order: IneB2Weight β†’ Weight β†’ builtins.object

πŸ”§ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from Weight:

πŸ“¦ Data descriptors inherited from Weight:

πŸ“¦ Data and other attributes inherited from Weight:


πŸ”΄ InternalError

InternalError indicates a runtime problem of some sort.

Method resolution order: InternalError β†’ RuntimeError β†’ Error β†’ builtins.Exception β†’ builtins.BaseException β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::InternalError::InternalError(const std::string &msg_, int errno_)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data and other attributes defined here:

πŸ“‹ Methods inherited from Error:

πŸ“¦ Data descriptors inherited from Error:

πŸ“‹ Methods inherited from builtins.Exception:

πŸ“‹ Methods inherited from builtins.BaseException:

πŸ“¦ Data descriptors inherited from builtins.BaseException:


🚫 InvalidArgumentError

InvalidArgumentError indicates an invalid parameter value was passed to the API.

Method resolution order: InvalidArgumentError β†’ LogicError β†’ Error β†’ builtins.Exception β†’ builtins.BaseException β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::InvalidArgumentError::InvalidArgumentError(const std::string &msg_, int errno_)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data and other attributes defined here:

πŸ“‹ Methods inherited from Error:

πŸ“¦ Data descriptors inherited from Error:

πŸ“‹ Methods inherited from builtins.Exception:

πŸ“‹ Methods inherited from builtins.BaseException:

πŸ“¦ Data descriptors inherited from builtins.BaseException:


🚫 InvalidOperationError

InvalidOperationError indicates the API was used in an invalid way.

Method resolution order: InvalidOperationError β†’ LogicError β†’ Error β†’ builtins.Exception β†’ builtins.BaseException β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::InvalidOperationError::InvalidOperationError(const std::string &msg_, int errno_)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data and other attributes defined here:

πŸ“‹ Methods inherited from Error:

πŸ“¦ Data descriptors inherited from Error:

πŸ“‹ Methods inherited from builtins.Exception:

πŸ“‹ Methods inherited from builtins.BaseException:

πŸ“¦ Data descriptors inherited from builtins.BaseException:


πŸ”‘ KeyMaker

Virtual base class for key making functors.

πŸ”§ Methods defined here:

Xapian::KeyMaker::KeyMaker()

const KeyMaker* Xapian::KeyMaker::release() const

You can hand ownership of a dynamically allocated KeyMaker object to Xapian by calling release() and then passing the object to a Xapian method. Xapian will arrange to delete the object once it is no longer required.

πŸ”§ Static methods defined here:

virtual Xapian::KeyMaker::~KeyMaker()

πŸ“¦ Data descriptors defined here:


βš–οΈπŸ“š LMWeight

Xapian::Weight subclass implementing the Language Model formula.

This class implements the "Language Model" Weighting scheme, as described by the early papers on LM by Bruce Croft. LM works by comparing the query to a Language Model of the document. The language model itself is parameter-free, though LMWeight takes parameters which specify the smoothing used.

Method resolution order: LMWeight β†’ Weight β†’ builtins.object

πŸ”§ Methods defined here:

Xapian::LMWeight::LMWeight(double param_log_=0.0, type_smoothing select_smoothing_=TWO_STAGE_SMOOTHING, double param_smoothing1_=-1.0, double param_smoothing2_=-1.0)

Parameters:

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:

πŸ“‹ Methods inherited from Weight:

πŸ“¦ Data descriptors inherited from Weight:

πŸ“¦ Data and other attributes inherited from Weight:


πŸ—ΊοΈ LatLongCoord

A latitude-longitude coordinate.

Experimental - see https://xapian.org/docs/deprecation#experimental features

Note that latitude-longitude coordinates are only precisely meaningful if the datum used to define them is specified. This class ignores this issue - it is up to the caller to ensure consistency.

πŸ”§ Methods defined here:

Xapian::LatLongCoord::LatLongCoord(double latitude_, double longitude_)

If the supplied longitude is out of the standard range, it will be normalised to the range 0 <= longitude < 360.

If you want to avoid the checks (for example, you know that your values are already in range), you can use the alternate constructor to construct an uninitialised coordinate, and then set the latitude and longitude directly.

Throws: InvalidArgumentError if the supplied latitude is out of range.

std::string Xapian::LatLongCoord::get_description() const

std::string Xapian::LatLongCoord::serialise() const

void Xapian::LatLongCoord::unserialise(const char **ptr, const char *end)

The buffer may contain further data after that for the coordinate.

Parameters:

Throws: Xapian::SerialisationError if the string does not start with a valid serialised latitude-longitude pair.

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:


πŸ—ΊοΈπŸ“‹ LatLongCoords

A sequence of latitude-longitude coordinates.

Experimental - see https://xapian.org/docs/deprecation#experimental features

πŸ”§ Methods defined here:

Xapian::LatLongCoords::LatLongCoords(const LatLongCoord &coord)

The iterator will return xapian.LatLongCoord objects.

std::string Xapian::LatLongCoords::get_description() const

void Xapian::LatLongCoords::append(const LatLongCoord &coord)

LatLongCoordsIterator Xapian::LatLongCoords::begin() const

bool Xapian::LatLongCoords::empty() const

LatLongCoordsIterator Xapian::LatLongCoords::end() const

std::string Xapian::LatLongCoords::serialise() const

size_t Xapian::LatLongCoords::size() const

void Xapian::LatLongCoords::unserialise(const std::string &serialised)

Parameters:

Throws: Xapian::SerialisationError if the string does not contain a valid serialised latitude-longitude pair, or contains junk at the end.

πŸ”§ Static methods defined here:

πŸ“¦ Data descriptors defined here:


πŸ—ΊοΈπŸ” LatLongCoordsIter

An iterator over all the coordinates in a LatLongCoords object.

The iterator returns LatLongCoord objects.

πŸ”§ Methods defined here:

This enhanced CLASSES section provides a visual overview of Xapian's core classes with emoji indicators for quick scanning.

πŸ“¦ CLASSES

πŸ”‘ KeyMaker

See help(type(self)) for accurate signature.

πŸ“Š Data descriptors defined here:

🏷️ Data and other attributes defined here:


πŸ“˜ LatLongDistanceKeyMaker(KeyMaker)

LatLongDistanceKeyMaker(*args)

KeyMaker subclass which sorts by distance from a latitude/longitude.

Experimental - seehttps://xapian.org/docs/deprecation#experimental- features

Results are ordered by the distance from a fixed point, or list of points, calculated according to the metric supplied. If multiple points are supplied (either in the constructor, or in the coordinates stored in a document), the closest pointwise distance is used.

If a document contains no coordinate stored in the specified slot, a special value for the distance will be used. This defaults to a large number, so that such results get a low rank, but may be specified by a constructor parameter.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

⬆️ Methods inherited from KeyMaker:

⬆️ Data descriptors inherited from KeyMaker:


πŸ“˜ LatLongDistancePostingSource(ValuePostingSource)

LatLongDistancePostingSource(*args)

Posting source which returns a weight based on geospatial distance.

Experimental - seehttps://xapian.org/docs/deprecation#experimental- features

Results are weighted by the distance from a fixed point, or list of points, calculated according to the metric supplied. If multiple points are supplied (either in the constructor, or in the coordinates stored in a document), the closest pointwise distance is used.

Documents further away than a specified maximum range (or with no location stored in the specified slot) will not be returned.

The weight returned is computed from the distance using the formula: k1 * pow(distance + k1, -k2) (Where k1 and k2 are (strictly) positive, floating point constants, which default to 1000 and 1, respectively. Distance is measured in metres, so this means that something at the centre gets a weight of 1.0, something 1km away gets a weight of 0.5, and something 3km away gets a weight of 0.25, etc)

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

⬆️ Methods inherited from ValuePostingSource:

⬆️ Methods inherited from PostingSource:

⬆️ Data descriptors inherited from PostingSource:


πŸ“˜ LatLongMetric(builtins.object)

Base class for calculating distances between two lat/long coordinates.

Experimental - seehttps://xapian.org/docs/deprecation#experimental- features

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ LogicError(Error)

LogicError(*args, **kwargs)

The base class for exceptions indicating errors in the program logic.

A subclass of LogicError will be thrown if Xapian detects a violation of a class invariant or a logical precondition or postcondition, etc.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

🏷️ Data and other attributes defined here:

⬆️ Methods inherited from Error:

⬆️ Data descriptors inherited from Error:

⬆️ Static methods inherited from builtins.Exception:

⬆️ Methods inherited from builtins.BaseException:

⬆️ Data descriptors inherited from builtins.BaseException:


πŸ“˜ MSet(builtins.object)

Class representing a list of search results.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

🏷️ Data and other attributes defined here:


πŸ“˜ MSetItem(builtins.object)

MSetItem(iter, mset)

An item returned from iteration of the MSet.

The item supports access to the following attributes and properties:

The collapse count estimate will always be less than or equal to the actual number of other documents satisfying the match criteria with the same collapse key as this document. If may be 0 even though there are other documents with the same collapse key which satisfying the match criteria. However if this method returns non-zero, there definitely are other such documents. So this method may be used to inform the user that there are "at least N other matches in this group", or to control whether to offer a "show other documents in this group" feature (but note that it may not offer it in every case where it would show other documents).

πŸ”§ Methods defined here:

πŸ“– Readonly properties defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ MSetIter(builtins.object)

MSetIter(mset)

An iterator over the items in an MSet. The iterator will return MSetItem objects, which will be evaluated lazily where appropriate.

πŸ”§ Methods defined here:


πŸ“˜ MatchDecider(builtins.object)

Base class for matcher decision functor.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ MatchSpy(builtins.object)

Abstract base class for match spies.

The subclasses will generally accumulate information seen during the match, to calculate aggregate functions, or other profiles of the matching documents.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ MultiValueKeyMaker(KeyMaker)

KeyMaker subclass which combines several values.

When the result is used for sorting, results are ordered by the first value. In the event of a tie, the second is used. If this is the same for both, the third is used, and so on. If reverse is true for a value, then the sort order for that value is reversed.

When used for collapsing, the documents will only be considered equal if all the values specified match. If none of the specified values are set then the generated key will be empty, so such documents won't be collapsed (which is consistent with the behaviour in the "collapse on a value" case). If you'd prefer that documents with none of the keys set are collapsed together, then you can set reverse for at least one of the values. Other than this, it isn't useful to set reverse for collapsing.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

⬆️ Methods inherited from KeyMaker:

⬆️ Data descriptors inherited from KeyMaker:


πŸ“˜ NetworkError(RuntimeError)

NetworkError(*args)

Indicates a problem communicating with a remote database.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

🏷️ Data and other attributes defined here:

⬆️ Methods inherited from Error:

⬆️ Data descriptors inherited from Error:

⬆️ Static methods inherited from builtins.Exception:

⬆️ Methods inherited from builtins.BaseException:

⬆️ Data descriptors inherited from builtins.BaseException:


πŸ“˜ NetworkTimeoutError(NetworkError)

NetworkTimeoutError(*args)

Indicates a timeout expired while communicating with a remote database.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

🏷️ Data and other attributes defined here:

⬆️ Methods inherited from Error:

⬆️ Data descriptors inherited from Error:

⬆️ Static methods inherited from builtins.Exception:

⬆️ Methods inherited from builtins.BaseException:

⬆️ Data descriptors inherited from builtins.BaseException:


πŸ“˜ NumberRangeProcessor(RangeProcessor)

NumberRangeProcessor(*args)

Handle a number range.

This class must be used on values which have been encoded using Xapian::sortable_serialise() which turns numbers into strings which will sort in the same order as the numbers (the same values can be used to implement a numeric sort).

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

⬆️ Methods inherited from RangeProcessor:

⬆️ Data descriptors inherited from RangeProcessor:


πŸ“˜ NumberValueRangeProcessor(StringValueRangeProcessor)

NumberValueRangeProcessor(*args)

Handle a number range.

This class must be used on values which have been encoded using Xapian::sortable_serialise() which turns numbers into strings which will sort in the same order as the numbers (the same values can be used to implement a numeric sort).

Deprecated Use Xapian::NumberRangeProcessor instead (added in 1.3.6).

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

⬆️ Methods inherited from ValueRangeProcessor:

⬆️ Data descriptors inherited from ValueRangeProcessor:


πŸ“˜ PL2PlusWeight(Weight)

PL2PlusWeight(*args)

Xapian::Weight subclass implementing the PL2+ probabilistic formula.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

⬆️ Methods inherited from Weight:

⬆️ Data descriptors inherited from Weight:

🏷️ Data and other attributes inherited from Weight:


πŸ“˜ PL2Weight(Weight)

PL2Weight(*args)

This class implements the PL2 weighting scheme.

PL2 is a representative scheme of the Divergence from Randomness Framework by Gianni Amati.

This weighting scheme is useful for tasks that require early precision.

It uses the Poisson approximation of the Binomial Probabilistic distribution (P) along with Stirling's approximation for the factorial value, the Laplace method to find the aftereffect of sampling (L) and the second wdf normalization proposed by Amati to normalize the wdf in the document to the length of the document (H2).

For more information about the DFR Framework and the PL2 scheme, please refer to : Gianni Amati and Cornelis Joost Van Rijsbergen Probabilistic models of information retrieval based on measuring the divergence from randomness ACM Transactions on Information Systems (TOIS) 20, (4), 2002, pp. 357-389.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

⬆️ Methods inherited from Weight:

⬆️ Data descriptors inherited from Weight:

🏷️ Data and other attributes inherited from Weight:


πŸ“˜ PositionIter(builtins.object)

PositionIter(start=0, end=0)

An iterator over a position list. The iterator will return integers, in ascending order.

πŸ”§ Methods defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ PostingItem(builtins.object)

PostingItem(iter)

An item returned from iteration of a posting list.

The item supports access to the following attributes and properties:

πŸ”§ Methods defined here:

πŸ“– Readonly properties defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ PostingIter(builtins.object)

PostingIter(start, end, has_positions=False)

An iterator over a posting list. The iterator will return PostingItem objects, which will be evaluated lazily where appropriate.

πŸ”§ Methods defined here:


πŸ“˜ PostingSource(builtins.object)

Base class which provides an "external" source of postings.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ Query(builtins.object)

Query(*args)

Class representing a query.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

🏷️ Data and other attributes defined here:


πŸ“˜ QueryParser(builtins.object)

Build a Xapian::Query object from a user query string.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:

🏷️ Data and other attributes defined here:


πŸ“˜ QueryParserError(RuntimeError)

QueryParserError(*args)

Indicates a query string can't be parsed.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

🏷️ Data and other attributes defined here:

⬆️ Methods inherited from Error:

⬆️ Data descriptors inherited from Error:

⬆️ Static methods inherited from builtins.Exception:

⬆️ Methods inherited from builtins.BaseException:

⬆️ Data descriptors inherited from builtins.BaseException:


πŸ“˜ RSet(builtins.object)

A relevance set (R-Set). This is the set of documents which are marked as relevant, for use in modifying the term weights, and in performing query expansion.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ RangeError(RuntimeError)

RangeError(*args)

RangeError indicates an attempt to access outside the bounds of a container.

πŸ“‹ Method resolution order:

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

🏷️ Data and other attributes defined here:

⬆️ Methods inherited from Error:

⬆️ Data descriptors inherited from Error:

⬆️ Static methods inherited from builtins.Exception:

⬆️ Methods inherited from builtins.BaseException:

⬆️ Data descriptors inherited from builtins.BaseException:


πŸ“˜ RangeProcessor(builtins.object)

RangeProcessor(*args)

Base class for range processors.

πŸ”§ Methods defined here:

βš™οΈ Static methods defined here:

πŸ“Š Data descriptors defined here:


πŸ“˜ Registry(builtins.object)

Registry for user subclasses. This class provides a way for the remote server to look up user subclasses when unserialising.

πŸ”§ Methods defined here:

πŸ“¦ CLASSES

🏷️ Registry

πŸ”’ The returned object is owned by the registry and must not be deleted by the caller.

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ RuntimeError

⚑ The base class for exceptions indicating errors only detectable at runtime.

A subclass of RuntimeError will be thrown if Xapian detects an error which is exception derived from RuntimeError is thrown when an error is caused by problems with the data or environment rather than a programming mistake.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data and other attributes defined here:

πŸ“¦ Methods inherited from Error:

πŸ“Š Data descriptors inherited from Error:

πŸ”§ Static methods inherited from builtins.Exception:

πŸ“¦ Methods inherited from builtins.BaseException:

πŸ“Š Data descriptors inherited from builtins.BaseException:


🏷️ SerialisationError

⚠️ Indicates an error in the std::string serialisation of an object.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data and other attributes defined here:

πŸ“¦ Methods inherited from Error:

πŸ“Š Data descriptors inherited from Error:

πŸ”§ Static methods inherited from builtins.Exception:

πŸ“¦ Methods inherited from builtins.BaseException:

πŸ“Š Data descriptors inherited from builtins.BaseException:


🏷️ SimpleStopper

πŸ›‘ Simple implementation of Stopper class - this will suit most users.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from Stopper:

πŸ“Š Data descriptors inherited from Stopper:


🏷️ Stem

🌿 Class representing a stemming algorithm.

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ StemImplementation

πŸ”§ Class representing a stemming algorithm implementation.

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ Stopper

πŸ›‘ Base class for stop-word decision functor.

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ StringValueRangeProcessor

πŸ”€ Handle a string range. The end points can be any strings. Deprecated: Use Xapian::RangeProcessor instead (added in 1.3.6).

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from ValueRangeProcessor:

πŸ“Š Data descriptors inherited from ValueRangeProcessor:


🏷️ TermGenerator

πŸ“ Parses a piece of text and generate terms. This module takes a piece of text and parses it to produce words which are then used to generate suitable terms for indexing. The terms generated are suitable for use with Query objects produced by the QueryParser class.

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“Š Data and other attributes defined here:


🏷️ TermIter

πŸ” An iterator over a term list. The iterator will return TermListItem objects, which will be evaluated lazily where appropriate.

πŸ“‹ Methods defined here:

πŸ“Š Data and other attributes defined here:


🏷️ TermListItem

πŸ“„ An item returned from iteration of a term list. Supports access to term, wdf, termfreq, and positer.

πŸ“‹ Methods defined here:

πŸ” Readonly properties defined here:

πŸ“Š Data descriptors defined here:


🏷️ TfIdfWeight

βš–οΈ Xapian::Weight subclass implementing the tf-idf weighting scheme.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from Weight:

πŸ“Š Data descriptors inherited from Weight:

πŸ“Š Data and other attributes inherited from Weight:


🏷️ TradWeight

βš–οΈ Xapian::Weight subclass implementing the traditional probabilistic formula. BM25 generally gives better results.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from Weight:

πŸ“Š Data descriptors inherited from Weight:

πŸ“Š Data and other attributes inherited from Weight:


🏷️ UnimplementedError

⚠️ UnimplementedError indicates an attempt to use an unimplemented feature.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data and other attributes defined here:

πŸ“¦ Methods inherited from Error:

πŸ“Š Data descriptors inherited from Error:

πŸ”§ Static methods inherited from builtins.Exception:

πŸ“¦ Methods inherited from builtins.BaseException:

πŸ“Š Data descriptors inherited from builtins.BaseException:


🏷️ ValueCountMatchSpy

πŸ“Š Class for counting the frequencies of values in the matching documents.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from MatchSpy:

πŸ“Š Data descriptors inherited from MatchSpy:


🏷️ ValueItem

πŸ“„ An item returned from iteration of the values in a document. Supports num and value attributes.

πŸ“‹ Methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ ValueIter

πŸ” An iterator over all the values stored in a document. Returns ValueItem objects in ascending order of value number.

πŸ“‹ Methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ ValueMapPostingSource

πŸ—ΊοΈ A posting source which looks up weights in a map using values as the key.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from ValuePostingSource:

πŸ“¦ Methods inherited from PostingSource:

πŸ“Š Data descriptors inherited from PostingSource:


🏷️ ValuePostingSource

πŸ“Š A posting source which generates weights from a value slot. Base class for ValueWeightPostingSource and ValueMapPostingSource.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from PostingSource:

πŸ“Š Data descriptors inherited from PostingSource:


🏷️ ValueRangeProcessor

πŸ”§ Base class for value range processors.

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ ValueSetMatchDecider

πŸ” MatchDecider filtering results based on whether document values are in a user-defined set.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from MatchDecider:

πŸ“Š Data descriptors inherited from MatchDecider:


🏷️ ValueStreamItem

πŸ“„ An item returned from iteration of the values in a document. Supports docid and value attributes.

πŸ“‹ Methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ ValueStreamIter

πŸ” An iterator over all the values stored in a document. Returns ValueStreamItem objects in ascending order of value number.

πŸ“‹ Methods defined here:

πŸ“Š Data descriptors defined here:


🏷️ ValueWeightPostingSource

βš–οΈ A posting source which reads weights from a value slot. Uses sortable_unserialise to convert values to weights.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from ValuePostingSource:

πŸ“¦ Methods inherited from PostingSource:

πŸ“Š Data descriptors inherited from PostingSource:


🏷️ Weight

βš–οΈ Abstract base class for weighting schemes.

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“Š Data and other attributes defined here:


🏷️ WildcardError

⚠️ WildcardError indicates an error expanding a wildcarded query.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data and other attributes defined here:

πŸ“¦ Methods inherited from Error:

πŸ“Š Data descriptors inherited from Error:

πŸ”§ Static methods inherited from builtins.Exception:

πŸ“¦ Methods inherited from builtins.BaseException:

πŸ“Š Data descriptors inherited from builtins.BaseException:


🏷️ WritableDatabase

πŸ’Ύ This class provides read/write access to a database.

πŸ”— Method resolution order:

πŸ“‹ Methods defined here:

πŸ”§ Static methods defined here:

πŸ“Š Data descriptors defined here:

πŸ“¦ Methods inherited from Database:

πŸ“Š Data descriptors inherited from Database:

πŸ›οΈ CLASSES

πŸ’Ύ commit

void Xapian::WritableDatabase::commit()

To ensure this, Xapian batches up modifications.

This method may be called at any time to commit any pending modifications to the database.

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.

It's not valid to call commit() within a transaction.

Beware of calling commit() too frequently: this will make indexing take much longer.

Note that commit() 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. By default, this is every 10000 documents added, deleted, or modified. This value is rather conservative, and if you have a machine with plenty of memory, you can improve indexing throughput dramatically by setting XAPIAN_FLUSH_THRESHOLD in the environment to a larger value.

This method was new in Xapian 1.1.0 - in earlier versions it was called flush().

πŸ“‹ Parameters

πŸ’³ commit_transaction

commit_transaction = WritableDatabase_commit_transaction(...)
void Xapian::WritableDatabase::commit_transaction()

Complete the transaction currently in progress.

If this method completes successfully and this is a flushed transaction, 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.

In all cases the transaction will no longer be in progress.

πŸ“‹ Parameters

πŸ—‘οΈ delete_document

delete_document = WritableDatabase_delete_document(...)
void Xapian::WritableDatabase::delete_document(const std::string &unique_term)

Delete any documents indexed by a term from the database.

This method removes any documents indexed by the specified term from the database.

A major use is for convenience when UIDs from another system are mapped to terms in Xapian, although this method has other uses (for example, you could add a "deletion date" term to documents at index time and use this method to delete all documents due for deletion on a particular date).

πŸ“‹ Parameters

πŸ“‹ Parameters (Exceptions)

πŸ”„ flush

flush = WritableDatabase_flush(...)
void Xapian::WritableDatabase::flush()

Pre-1.1.0 name for commit().

Use commit() instead.

βœ‚οΈ remove_spelling

remove_spelling = WritableDatabase_remove_spelling(...)
void Xapian::WritableDatabase::remove_spelling(const std::string &word, Xapian::termcount freqdec=1) const

Remove a word from the spelling dictionary.

The word's frequency is decreased, and if would become zero or less then the word is removed completely.

πŸ“‹ Parameters

πŸ”— remove_synonym

remove_synonym = WritableDatabase_remove_synonym(...)
void Xapian::WritableDatabase::remove_synonym(const std::string &term, const std::string &synonym) const

Remove a synonym for a term.

πŸ“‹ Parameters

πŸ” replace_document

replace_document = WritableDatabase_replace_document(...)
Xapian::docid Xapian::WritableDatabase::replace_document(const std::string &unique_term, const Xapian::Document &document)

Replace any documents matching a term.

This method replaces any documents indexed by the specified term with the specified document. If any documents are indexed by the term, the lowest document ID will be used for the document, otherwise a new document ID will be generated as for add_document.

One common use is to allow UIDs from another system to easily be mapped to terms in Xapian. Note that this method doesn't automatically add unique_term as a term, so you'll need to call document.add_term(unique_term) first when using replace_document() in this way.

Note that changes to the database won't be immediately committed to disk; see commit() for more details.

As with all database modification operations, the effect is atomic: the document(s) will either be fully replaced, or the document(s) fail to be replaced and an exception is thrown (possibly at a later time when commit() is called or the database is closed).

πŸ“‹ Parameters

The document ID that document was given.

πŸ“‹ Parameters (Exceptions)

🏷️ set_metadata

set_metadata = WritableDatabase_set_metadata(...)
void Xapian::WritableDatabase::set_metadata(const std::string &key, const std::string &metadata)

Set the user-specified metadata associated with a given key.

This method sets the metadata value associated with a given key. If there is already a metadata value stored in the database with the same key, the old value is replaced. If you want to delete an existing item of metadata, just set its value to the empty string.

User-specified metadata allows you to store arbitrary information in the form of (key, value) pairs.

There's no hard limit on the number of metadata items, or the size of the metadata values. Metadata keys have a limited length, which depend on the backend. We recommend limiting them to 200 bytes. Empty keys are not valid, and specifying one will cause an exception.

Metadata modifications are committed to disk in the same way as modifications to the documents in the database are: i.e., modifications are atomic, and won't be committed to disk immediately (see commit() for more details). This allows metadata to be used to link databases with versioned external resources by storing the appropriate version number in a metadata item.

You can also use the metadata to store arbitrary extra information associated with terms, documents, or postings by encoding the termname and/or document id into the metadata key.

πŸ“‹ Parameters

πŸ“‹ Parameters (Exceptions)


πŸ› οΈ Static methods defined here

❌ __swig_destroy__

__swig_destroy__ = delete_WritableDatabase(...)
virtual Xapian::WritableDatabase::~WritableDatabase()

Destroy this handle on the database.

If no other handles to this database remain, the database will be closed.

If a transaction is active cancel_transaction() will be implicitly called; if no transaction is active commit() will be implicitly called, but any exception will be swallowed (because throwing exceptions in C++ destructors is problematic). If you aren't using transactions and want to know about any failure to commit changes, call commit() explicitly before the destructor gets called.


πŸ“¦ Data descriptors defined here


πŸ“š Methods inherited from Database

πŸ› οΈ Static methods inherited from Database

πŸ“¦ Data descriptors inherited from Database

πŸ› οΈ FUNCTIONS

xapian
πŸ“– NAME πŸ“– DESCRIPTION πŸ“¦ PACKAGE CONTENTS πŸ“š CLASSES
πŸ”΄ Error (base exception class) πŸ”΄ AssertionError πŸ”΄ InvalidArgumentError πŸ”΄ InvalidOperationError πŸ”΄ UnimplementedError πŸ”΄ RuntimeError πŸ”΄ DatabaseError πŸ”΄ DatabaseClosedError πŸ”΄ DatabaseCorruptError πŸ”΄ DatabaseCreateError πŸ”΄ DatabaseLockError πŸ”΄ DatabaseModifiedError πŸ”΄ DatabaseOpeningError πŸ”΄ DatabaseNotFoundError πŸ”΄ DatabaseVersionError πŸ”΄ DocNotFoundError πŸ”΄ FeatureUnavailableError πŸ”΄ InternalError πŸ”΄ NetworkError πŸ”΄ NetworkTimeoutError πŸ”΄ QueryParserError πŸ”΄ RangeError πŸ”΄ SerialisationError πŸ”΄ WildcardError πŸ—‚οΈ Database πŸ—‚οΈ WritableDatabase (extends Database) πŸ—‚οΈ Compactor πŸ—‚οΈ Document πŸ—‚οΈ Enquire πŸ—‚οΈ MSet πŸ—‚οΈ MSetItem πŸ—‚οΈ ESet πŸ—‚οΈ ESetItem πŸ—‚οΈ RSet πŸ—‚οΈ Query πŸ—‚οΈ QueryParser πŸ—‚οΈ Stem πŸ—‚οΈ Stopper (abstract) πŸ—‚οΈ SimpleStopper πŸ—‚οΈ TermGenerator πŸ—‚οΈ ValueRangeProcessor (abstract) πŸ—‚οΈ StringValueRangeProcessor πŸ—‚οΈ DateValueRangeProcessor (deprecated, use DateRangeProcessor) πŸ—‚οΈ NumberValueRangeProcessor (deprecated, use NumberRangeProcessor) πŸ—‚οΈ RangeProcessor (abstract) πŸ—‚οΈ DateRangeProcessor πŸ—‚οΈ NumberRangeProcessor πŸ—‚οΈ ExpandDecider (abstract) πŸ—‚οΈ ExpandDeciderAnd πŸ—‚οΈ ExpandDeciderFilterPrefix πŸ—‚οΈ KeyMaker (abstract) πŸ—‚οΈ MultiValueKeyMaker πŸ—‚οΈ LatLongDistanceKeyMaker πŸ—‚οΈ LatLongCoord πŸ—‚οΈ LatLongCoords πŸ—‚οΈ LatLongMetric (abstract) πŸ—‚οΈ GreatCircleMetric πŸ—‚οΈ PostingSource (abstract) πŸ—‚οΈ FixedWeightPostingSource πŸ—‚οΈ ValuePostingSource (abstract) πŸ—‚οΈ ValueWeightPostingSource πŸ—‚οΈ DecreasingValueWeightPostingSource πŸ—‚οΈ ValueMapPostingSource πŸ—‚οΈ LatLongDistancePostingSource πŸ—‚οΈ MatchDecider (abstract) πŸ—‚οΈ ValueSetMatchDecider πŸ—‚οΈ MatchSpy (abstract) πŸ—‚οΈ ValueCountMatchSpy πŸ—‚οΈ Registry πŸ—‚οΈ FieldProcessor (abstract) πŸ—‚οΈ Weight (abstract) πŸ—‚οΈ BB2Weight πŸ—‚οΈ BM25PlusWeight πŸ—‚οΈ BM25Weight πŸ—‚οΈ BoolWeight πŸ—‚οΈ CoordWeight πŸ—‚οΈ DLHWeight πŸ—‚οΈ DPHWeight πŸ—‚οΈ IfB2Weight πŸ—‚οΈ InL2Weight πŸ—‚οΈ IneB2Weight πŸ—‚οΈ LMWeight πŸ—‚οΈ PL2PlusWeight πŸ—‚οΈ PL2Weight πŸ—‚οΈ TfIdfWeight πŸ—‚οΈ TradWeight πŸ—‚οΈ PostingIter πŸ—‚οΈ PostingItem πŸ—‚οΈ PositionIter πŸ—‚οΈ TermIter πŸ—‚οΈ TermListItem πŸ—‚οΈ ValueIter πŸ—‚οΈ ValueItem πŸ—‚οΈ ValueStreamItem πŸ—‚οΈ ValueStreamIter πŸ—‚οΈ ESetIter πŸ—‚οΈ LatLongCoordsIter πŸ—‚οΈ MSetIter πŸ—‚οΈ TermGenerator (already covered) πŸ—‚οΈ Stem (already covered) πŸ—‚οΈ StemImplementation (abstract) πŸ—‚οΈ FieldProcessor (abstract, already covered) πŸ—‚οΈ KeyMaker (abstract, already covered)
πŸ›οΈ CLASSES
πŸ—‚οΈ ValuePostingSource ❌ DocNotFoundError πŸ“„ Document πŸ“Š ESet πŸ“ˆ ESetItem πŸ” ESetIter πŸ” Enquire ⚠️ Error πŸ§ͺ ExpandDecider πŸ§ͺπŸ”— ExpandDeciderAnd πŸ§ͺπŸ”€ ExpandDeciderFilterPrefix 🚫 FeatureUnavailableError 🧰 FieldProcessor βš–οΈ FixedWeightPostingSource 🌍 GreatCircleMetric βš–οΈπŸ“Š IfB2Weight βš–οΈπŸ“Š InL2Weight βš–οΈπŸ“Š IneB2Weight πŸ”΄ InternalError 🚫 InvalidArgumentError 🚫 InvalidOperationError πŸ”‘ KeyMaker βš–οΈπŸ“š LMWeight πŸ—ΊοΈ LatLongCoord πŸ—ΊοΈπŸ“‹ LatLongCoords πŸ—ΊοΈπŸ” LatLongCoordsIter
πŸ“¦ CLASSES
πŸ”‘ KeyMaker πŸ“˜ LatLongDistanceKeyMaker(KeyMaker) πŸ“˜ LatLongDistancePostingSource(ValuePostingSource) πŸ“˜ LatLongMetric(builtins.object) πŸ“˜ LogicError(Error) πŸ“˜ MSet(builtins.object) πŸ“˜ MSetItem(builtins.object) πŸ“˜ MSetIter(builtins.object) πŸ“˜ MatchDecider(builtins.object) πŸ“˜ MatchSpy(builtins.object) πŸ“˜ MultiValueKeyMaker(KeyMaker) πŸ“˜ NetworkError(RuntimeError) πŸ“˜ NetworkTimeoutError(NetworkError) πŸ“˜ NumberRangeProcessor(RangeProcessor) πŸ“˜ NumberValueRangeProcessor(StringValueRangeProcessor) πŸ“˜ PL2PlusWeight(Weight) πŸ“˜ PL2Weight(Weight) πŸ“˜ PositionIter(builtins.object) πŸ“˜ PostingItem(builtins.object) πŸ“˜ PostingIter(builtins.object) πŸ“˜ PostingSource(builtins.object) πŸ“˜ Query(builtins.object) πŸ“˜ QueryParser(builtins.object) πŸ“˜ QueryParserError(RuntimeError) πŸ“˜ RSet(builtins.object) πŸ“˜ RangeError(RuntimeError) πŸ“˜ RangeProcessor(builtins.object) πŸ“˜ Registry(builtins.object)
πŸ“¦ CLASSES
🏷️ Registry 🏷️ RuntimeError 🏷️ SerialisationError 🏷️ SimpleStopper 🏷️ Stem 🏷️ StemImplementation 🏷️ Stopper 🏷️ StringValueRangeProcessor 🏷️ TermGenerator 🏷️ TermIter 🏷️ TermListItem 🏷️ TfIdfWeight 🏷️ TradWeight 🏷️ UnimplementedError 🏷️ ValueCountMatchSpy 🏷️ ValueItem 🏷️ ValueIter 🏷️ ValueMapPostingSource 🏷️ ValuePostingSource 🏷️ ValueRangeProcessor 🏷️ ValueSetMatchDecider 🏷️ ValueStreamItem 🏷️ ValueStreamIter 🏷️ ValueWeightPostingSource 🏷️ Weight 🏷️ WildcardError 🏷️ WritableDatabase
πŸ›οΈ CLASSES
πŸ’Ύ commit πŸ’³ commit_transaction πŸ—‘οΈ delete_document πŸ”„ flush βœ‚οΈ remove_spelling πŸ”— remove_synonym πŸ” replace_document 🏷️ set_metadata πŸ› οΈ Static methods defined here πŸ“¦ Data descriptors defined here πŸ“š Methods inherited from Database πŸ› οΈ Static methods inherited from Database πŸ“¦ Data descriptors inherited from Database
πŸ› οΈ FUNCTIONS πŸ“Š DATA 🏷️ VERSION πŸ“„ FILE

Generated by phpman v4.10.0-7-g98e9fd5 · Markdown · JSON · MCP Author: Che Dong Under GNU General Public License
2026-09-01 16:58 @216.73.216.239
CrawledBy Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Valid XHTML 1.0 Transitional!Valid CSS!

^_top_^