Trees | Indices | Help |
|
---|
|
PluginIndexes.PathIndex.PathIndex.PathIndex --+ | ExtendedPathIndex
A path index stores all path components of the physical path of an object: Internal datastructure (regular pathindex): - a physical path of an object is split into its components - every component is kept as a key of a OOBTree in self._indexes - the value is a mapping 'level of the path component' to 'all docids with this path component on this level' In addition - there is a terminator (None) signifying the last component in the path
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|||
|
|
|||
meta_type = "ExtendedPathIndex"
|
|||
manage_options = {'label': 'Settings', 'action': 'manage_main'
|
|||
query_options = "query", "level", "operator", "depth", "navtre
|
|||
index_html = DTMLFile('dtml/index', globals())
|
|||
manage_workspace = DTMLFile('dtml/manageExtendedPathIndex', gl
|
|
Insert an entry. parent_path is the path of the parent object path is the object path, it is assumed to be unique, i.e. there is a one to one mapping between physical paths and docids. This will be large, and is only used for breadcrumbs. id is the docid |
path is either a string representing a relative URL or a part of a relative URL or a tuple (path,level). level >= 0 starts searching at the given level level < 0 not implemented yet |
hook for (Z)Catalog 'request' -- mapping type (usually {"path": "..." } additionaly a parameter "path_level" might be passed to specify the level (see search()) 'cid' -- ??? |
|
manage_options
|
query_options
|
manage_workspace
|
Trees | Indices | Help |
|
---|
Generated by Epydoc 3.0.1.1812 on Tue Oct 11 12:51:34 2011 | http://epydoc.sourceforge.net |