Home | Trees | Indices | Help |
|
---|
|
object --+ | ProcessedDocument
A processed document, as stored in the index.
This represents an item which is ready to be stored in the search engine, or which has been returned by the search engine.
Instance Methods | |||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
Inherited from |
Properties | |
data The data stored in this processed document. |
|
id The unique ID for this document. |
|
Inherited from |
Method Details |
Create a ProcessedDocument. fieldmappings is the configuration from a database connection used lookup the configuration to use to store each field. If supplied,
|
Add a term to the document. Terms are the main unit of information used for performing searches.
|
Add a value to the document. Values are additional units of information used when performing searches. Note that values are _not_ intended to be used to store information for display in the search results - use the document data for that. The intention is that as little information as possible is stored in values, so that they can be accessed as quickly as possible during the search operation. Unlike terms, each document may have at most one value in each field (whereas there may be an arbitrary number of terms in a given field). If an attempt to add multiple values to a single field is made, only the last value added will be stored. |
Prepare the document for adding to a xapian database. This updates the internal xapian document with any changes which have been made, and then returns it. |
|
Property Details |
dataThe data stored in this processed document. This data is a dictionary of entries, where the key is a fieldname, and the value is a list of strings.
|
idThe unique ID for this document.
|
Home | Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0beta1 on Tue Apr 29 09:21:55 2008 | http://epydoc.sourceforge.net |