mirror of
https://github.com/sigmasternchen/php-doc-en
synced 2025-03-16 17:08:54 +00:00
mnoGoSearch docs update.
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@41711 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
parent
9e5c5f5dbb
commit
bc5d5cdf1e
1 changed files with 47 additions and 3 deletions
|
@ -13,6 +13,19 @@
|
|||
mnogosearch at other path you should specify it:
|
||||
<option role="configure">--with-mnogosearch=DIR</option>.
|
||||
</simpara>
|
||||
<para>
|
||||
mnoGoSearch is a full-featured search engine software for intranet and internet servers,
|
||||
distributed under the GNU license. mnoGoSearch has number of unique features, which makes
|
||||
it appropriate for a wide range of application from search within your site to a specialized
|
||||
search system such as cooking recipes or newspaper search, ftp archive search, news articles search,
|
||||
etc. It offers full-text indexing and searching for HTML, PDF, and text documents. mnoGoSearch
|
||||
consists of two parts. The first is an indexing mechanism (indexer). The purpose of indexer is
|
||||
to walk through HTTP, FTP, NEWS servers or local files, recursively grabbing all the documents
|
||||
and storing meta-data about that documents in a SQL database in a smart and effective manner.
|
||||
After every document is referenced by its corresponding URL, meta-data collected by indexer is
|
||||
used later in a search process. The search is performed via Web interface. C CGI, PHP and Perl
|
||||
search front ends are included.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
php contains built-in mysql access library, which can be used to
|
||||
|
@ -121,7 +134,7 @@
|
|||
<listitem>
|
||||
<simpara>
|
||||
UDM_PARAM_SEARCH_MODE - search mode. The following values available: UDM_MODE_ALL -
|
||||
search for all words; UDM_MODE_ANY - search for any word; UDM_MODE_BOOL - boolean search. See <function>udm_find</function> for details on boolean search.
|
||||
search for all words; UDM_MODE_ANY - search for any word; UDM_MODE_PHRASE - phrase search; UDM_MODE_BOOL - boolean search. See <function>udm_find</function> for details on boolean search.
|
||||
</simpara>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
@ -139,7 +152,23 @@
|
|||
When doing a search, front-end uses those tables to store query words, a number of found documents and current UNIX timestamp in seconds.
|
||||
Available values: UDM_TRACK_ENABLED, UDM_TRACK_DISABLED.
|
||||
</simpara>
|
||||
</listitem>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
UDM_PARAM_PHRASE_MODE - defines whether index database using phrases ("phrase" parameter in indexer.conf).
|
||||
Possible values: UDM_PHRASE_ENABLED and UDM_PHRASE_DISABLED.
|
||||
Please note, that if phrase search is enabled (UDM_PHRASE_ENABLED),
|
||||
it is still possible to do search in any mode (ANY, ALL, BOOL or PHRASE).
|
||||
In 3.1.10 version of mnoGoSearch phrase search is supported only in sql and buuilt-in database modes,
|
||||
while beginning with 3.1.11 phrases are supported in cachemode as well.
|
||||
</simpara>
|
||||
<simpara>
|
||||
Examples of phrase search:
|
||||
</simpara>
|
||||
<simpara>
|
||||
"Arizona desert" - This query returns all indexed documents that contain "Arizona desert" as a phrase. Notice that you need to put double quotes around the phrase
|
||||
</simpara>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
UDM_PARAM_CHARSET - defines local charset. Available values: set of charsets supported by mnoGoSearch,
|
||||
|
@ -227,7 +256,22 @@
|
|||
<simpara>UDM_MATCH_END - word ending match;</simpara>
|
||||
<simpara>UDM_MATCH_WORD - whole word match;</simpara>
|
||||
<simpara>UDM_MATCH_SUBSTR - word substring match.</simpara>
|
||||
</listitem>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
UDM_PARAM_MIN_WORD_LEN - defines minimal word length.
|
||||
Any word shorter this limit is considered to be a stopword. Please note that this paraneter value is inclusive,
|
||||
i.e. if UDM_PARAM_MIN_WORD_LEN=3, a word 3 characters long will not be considered a stopword, while
|
||||
a word 2 characters long will be. Default value is 1.
|
||||
</simpara>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<simpara>
|
||||
UDM_PARAM_MAX_WORD_LEN - defines maximum word lenght. Any word longer this limit is considered to be a stopword. Please note that this paraneter value is inclusive,
|
||||
i.e. if UDM_PARAM_MAX_WORD_LEN=32, a word 32 characters long will not be considered a stopword, while
|
||||
a word 33 characters long will be. Default value is 32.
|
||||
</simpara>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</refsect1>
|
||||
</refentry>
|
||||
|
|
Loading…
Reference in a new issue