Using search front-end
=======================


Doing search
------------

http://your.web.server/path/to/search.php

To find something just type words you want to find and press SUBMIT button.
For example, "mysql odbc". You should not use quotes " in query,
they are written here only to divide a query from other text. mnoGoSearch
will find all documents that contain word "mysql" and/or word "odbc". 
Best documents having bigger weights will be displayed first.


Search parameters
-----------------

mnoGoSearch frontends support the following parameters given in CGI query 
string. You may use them in HTML form on search page.

q	text parameter with search query
ps	page size, number of search results displayed on one page,
	20 by default. Maximum page size is 100. This value does
	not allow to pass very big page sizes to avoid server overload
	and might be changed with MAX_PS definition in search.c.
np	page number, 0 by default (first page)
m	search mode. Currently "all","any" and "bool" values are supported.
o	search result type. 0 by default. You may describe several template 
	sections for every part, for example "res". This allows to choose
	for example "Long" or "Short" search result output types. Up to 100
	different formats are allowed in the same template.
t	tag limit. Limits search through only documents with given tag.
	This parameter has the same effect with -t indexer option
cat	Category limit. Take a look into "categories.txt" for datails.
lang    Language limit. 
dp,dt,dx,dd,dm,dy,db,de Time limits.
ul,ue	URL limit and URL exclusion, URL substring to limit search through
        subsection of database. It supports SQL % and _  LIKE wildcards. 
	This parameter has the same effect with -u indexer option.
	By default search.cgi inserts % signs before and after "ul" value.
	It allows to write URL substring in HTML from to limit search,
	for example <OPTION VALUE="/manual/"> instead of VALUE="%/manual/%".
	You may specify --disable-auto-wildcard to configure script
	at installation time to disallow automatic addition of % signs.

	Disabling automatic addition sometimes allow to make search faster.
	For example, specifying whole begining of URL
	<OPTION VALUE="http://www.somewhere.com/manual/%"> allows most 
	of SQL servers to use indexes when executing the query with given 
	value in LIKE expression.

Advanced boolean search
-----------------------
If you want more advanced results you may use query language.
You should select "bool" match mode in the search from.

mnoGoSearch understands next boolean operators:

& - logical AND.
For example, "mysql & odbc". mnoGoSearch will find any URLs that 
contain both "mysql" and "odbc".

| - logical OR. For example "mysql|odbc". mnoGoSearch will find any URLs, 
that contain word "mysql" or word "odbc".

~ - logical NOT. For example "mysql & ~odbc". 
mnoGoSearch will find URLs that contain word "mysql" and do not contain
word "odbc" at the same time. Note that ~ just excludes given word from results.
Query "~odbc" will find nothing! 

() - group command to compose more complex queries.
For example "(mysql | msql) & ~postgres".
Query language is simple and powerful at the same time. Just consider 
query as usual boolean expression.

