<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML ><HEAD ><TITLE >DBAddr</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REL="HOME" TITLE="mnoGoSearch 3.3.9 reference manual" HREF="index.html"><LINK REL="UP" TITLE="mnoGoSearch command reference" HREF="msearch-cmdref.html"><LINK REL="PREVIOUS" TITLE="DateFormat" HREF="msearch-cmdref-dateformat.html"><LINK REL="NEXT" TITLE="DefaultContentType" HREF="msearch-cmdref-defaultcontenttype.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="mnogo.css"><META NAME="Description" CONTENT="mnoGoSearch - Full Featured Web site Open Source Search Engine Software over the Internet and Intranet Web Sites Based on SQL Database. It is a Free search software covered by GNU license."><META NAME="Keywords" CONTENT="shareware, freeware, download, internet, unix, utilities, search engine, text retrieval, knowledge retrieval, text search, information retrieval, database search, mining, intranet, webserver, index, spider, filesearch, meta, free, open source, full-text, udmsearch, website, find, opensource, search, searching, software, udmsearch, engine, indexing, system, web, ftp, http, cgi, php, SQL, MySQL, database, php3, FreeBSD, Linux, Unix, mnoGoSearch, MacOS X, Mac OS X, Windows, 2000, NT, 95, 98, GNU, GPL, url, grabbing"></HEAD ><BODY CLASS="refentry" BGCOLOR="#EEEEEE" TEXT="#000000" LINK="#000080" VLINK="#800080" ALINK="#FF0000" ><!--#include virtual="body-before.html"--><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" ><SPAN CLASS="application" >mnoGoSearch</SPAN > 3.3.9 reference manual: Full-featured search engine software</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="msearch-cmdref-dateformat.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" ><A HREF="msearch-cmdref-defaultcontenttype.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><H1 ><A NAME="cmdref-dbaddr" ></A >DBAddr</H1 ><DIV CLASS="refnamediv" ><A NAME="AEN8312" ></A ><H2 >Name</H2 ><B CLASS="command" >DBAddr</B > -- sets the database connection string<P ><B ></B ><TT CLASS="filename" >indexer.conf</TT > <TT CLASS="filename" >search.htm</TT ></P ></DIV ><DIV CLASS="refsynopsisdiv" ><A NAME="AEN8319" ></A ><H2 >Synopsis</H2 ><P ><B CLASS="command" >DBAddr</B > {type://[user[:password]@]hostname[:port]/dbname/[?DBMode=mode][&param1=value1...]}</P ></DIV ><DIV CLASS="refsect1" ><A NAME="AEN8323" ></A ><H2 >Description</H2 ><P >The <B CLASS="command" >DBAddr</B > command defines the connection string for the database <SPAN CLASS="application" >mnoGoSearch</SPAN > will use for indexing and searching, using <ACRONYM CLASS="acronym" >URL</ACRONYM >-style notation. </P ><P > <B CLASS="command" >DBAddr</B > must be used before any other commands, and has global effect on the entire configuration file. Multiple <B CLASS="command" >DBAddr</B > entries are possible in the case of a distributed search engine (see <A HREF="msearch-cluster.html" >Chapter 11</A >). </P ><P > <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Type</I ></SPAN >, <SPAN CLASS="emphasis" ><I CLASS="emphasis" >hostname</I ></SPAN >, <SPAN CLASS="emphasis" ><I CLASS="emphasis" >dbname</I ></SPAN >, <SPAN CLASS="emphasis" ><I CLASS="emphasis" >user</I ></SPAN >, <SPAN CLASS="emphasis" ><I CLASS="emphasis" >password</I ></SPAN > and <SPAN CLASS="emphasis" ><I CLASS="emphasis" >port</I ></SPAN > are the most important parts of a <B CLASS="command" >DBAddr</B > value. </P ><P > The main part of a <B CLASS="command" >DBAddr</B > command can also be optionally followed by a number of additional parameters, like <SPAN CLASS="emphasis" ><I CLASS="emphasis" >DBMode</I ></SPAN >. </P ><P > The main part is separated from the parameters using the <TT CLASS="literal" >QUESTION MARK</TT > character (<TT CLASS="literal" >?</TT >), and the parameters are separated from each other using the <TT CLASS="literal" >AMPERSAND SIGN</TT > character (<TT CLASS="literal" >&</TT >). </P ><DIV CLASS="refsect2" ><A NAME="AEN8349" ></A ><H3 >Notes on <SPAN CLASS="emphasis" ><I CLASS="emphasis" >type</I ></SPAN ></H3 ><P >Currently supported <SPAN CLASS="emphasis" ><I CLASS="emphasis" >type</I ></SPAN > values are <TT CLASS="literal" >mysql</TT >, <TT CLASS="literal" >pgsql</TT >, <TT CLASS="literal" >mssql</TT >, <TT CLASS="literal" >sybase</TT >, <TT CLASS="literal" >oracle</TT >, <TT CLASS="literal" >ibase</TT >, <TT CLASS="literal" >db2</TT >, <TT CLASS="literal" >mimer</TT >, <TT CLASS="literal" >sqlite</TT >, <TT CLASS="literal" >sqlite3</TT >, <TT CLASS="literal" >cache</TT >. </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8365" ></A ><H3 >Notes on <SPAN CLASS="emphasis" ><I CLASS="emphasis" >hostname</I ></SPAN ></H3 ><P >An empty host name with <SPAN CLASS="application" >PostgreSQL</SPAN >, for example, <PRE CLASS="programlisting" > pgsql://user:password@/dbname/ </PRE > means that <SPAN CLASS="application" >mnoGoSearch</SPAN > will communicate with the <SPAN CLASS="application" >PostgreSQL</SPAN > server using a <ACRONYM CLASS="acronym" >UNIX</ACRONYM > socket rather than a <ACRONYM CLASS="acronym" >TCP</ACRONYM > port. </P ><P > <CODE CLASS="option" >Hostname</CODE > is not important when describing an <ACRONYM CLASS="acronym" >ODBC</ACRONYM > database (on <SPAN CLASS="application" >Windows</SPAN >, or on <ACRONYM CLASS="acronym" >UNIX</ACRONYM > when <SPAN CLASS="application" >mnoGoSearch</SPAN > is compiled with <SPAN CLASS="application" >UnixODBC</SPAN > or <SPAN CLASS="application" >iODBC</SPAN > support). Specifying an <SPAN CLASS="emphasis" ><I CLASS="emphasis" ><ACRONYM CLASS="acronym" >ODBC</ACRONYM > Data Source Name (<ACRONYM CLASS="acronym" >DSN</ACRONYM >)</I ></SPAN > in the <SPAN CLASS="emphasis" ><I CLASS="emphasis" >dbname</I ></SPAN > part is enough, so the <SPAN CLASS="emphasis" ><I CLASS="emphasis" >hostname</I ></SPAN > part can be either omitted or can be set to <TT CLASS="literal" >localhost</TT >: <PRE CLASS="programlisting" > mysql://root@/myodbc/ mysql://root@localhost/myodbc/ </PRE > </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8390" ></A ><H3 >Special characters in <SPAN CLASS="emphasis" ><I CLASS="emphasis" >user</I ></SPAN > and <SPAN CLASS="emphasis" ><I CLASS="emphasis" >password</I ></SPAN ></H3 ><P >Some special characters, if they appear in the user name or password, need to be escaped using <TT CLASS="literal" >%XX</TT > notation, where <TT CLASS="literal" >XX</TT > is a hexadecimal character code. Use <TT CLASS="literal" >%3A</TT > for "<TT CLASS="literal" >:</TT >", <TT CLASS="literal" >%3B</TT > for "<TT CLASS="literal" >;</TT >", <TT CLASS="literal" >%3C</TT > for "<TT CLASS="literal" ><</TT >", <TT CLASS="literal" >%3D</TT > for "<TT CLASS="literal" >=</TT >", <TT CLASS="literal" >%3E</TT > for "<TT CLASS="literal" >></TT >", <TT CLASS="literal" >%3F</TT > for "<TT CLASS="literal" >?</TT >" and <TT CLASS="literal" >%40</TT > for "<TT CLASS="literal" >@</TT >" characters. For example, <PRE CLASS="programlisting" > DBAddr pgsql://user:pwd%3Awith%40special%3Cchars@/search/ </PRE > corresponds to the local <SPAN CLASS="application" >PostgreSQL</SPAN > database <TT CLASS="literal" >search</TT > with the user name <TT CLASS="literal" >user</TT > and password "<TT CLASS="literal" >pwd:with@special<chars</TT >". </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8416" ></A ><H3 >The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >DBMode</I ></SPAN > parameter</H3 ><P >The <CODE CLASS="option" >DBMode</CODE > optional parameter can be set to one of the three values: <TT CLASS="literal" >single</TT >, <TT CLASS="literal" >multi</TT > or <TT CLASS="literal" >blob</TT >. The default value is <TT CLASS="literal" >blob</TT >. See <A HREF="msearch-howstore.html#sql-stor" >the Section called <I >Word modes with an <ACRONYM CLASS="acronym" >SQL</ACRONYM > database</I > in Chapter 7</A > for details. </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8426" ></A ><H3 >The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Socket</I ></SPAN > parameter</H3 ><P ><SPAN CLASS="application" >MySQL</SPAN > and <SPAN CLASS="application" >PostgreSQL</SPAN > users can specify a path to the <ACRONYM CLASS="acronym" >UNIX</ACRONYM > socket when connecting to a server running on the local machine: <PRE CLASS="programlisting" > DBAddr mysql://foo:bar@localhost/mnogosearch/?socket=/tmp/mysql.sock DBAddr pgsql://foo:bar@/mnogosearch/?socket=/tmp/s.PGSQL.5432 </PRE > </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8434" ></A ><H3 >The <CODE CLASS="option" >SetNames</CODE > parameter</H3 ><P ><SPAN CLASS="application" >MySQL</SPAN > and <SPAN CLASS="application" >PostgreSQL</SPAN > users can set connection character set by specifying the <CODE CLASS="option" >SetNames</CODE > parameter. It is important if the default <SPAN CLASS="application" >MySQL</SPAN > or <SPAN CLASS="application" >PostgreSQL</SPAN > client character set settings does not correspond to the <A HREF="msearch-cmdref-localcharset.html" >LocalCharset</A > setting of <SPAN CLASS="application" >mnoGoSearch</SPAN >. <PRE CLASS="programlisting" > LocalCharset utf8 DBAddr http://root@localhost/test/?setnames=utf8 </PRE > If a non-empty <TT CLASS="literal" >SetNames</TT > value is specified, <SPAN CLASS="application" >MySQL</SPAN > and <SPAN CLASS="application" >PostgreSQL</SPAN > drivers will send a <SPAN CLASS="emphasis" ><I CLASS="emphasis" >SET NAMES</I ></SPAN > query after connection is established. </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8450" ></A ><H3 >The <CODE CLASS="option" >QCache</CODE > parameter</H3 ><P > When <CODE CLASS="option" >QCache</CODE > is set to <TT CLASS="literal" >yes</TT >, <SPAN CLASS="application" >search.cgi</SPAN > enables <I CLASS="firstterm" >search results cache</I >, which is used to improve search performance of the subsequent queries for the same words, including navigating through the search result pages (e.g. watching documents <TT CLASS="literal" >11-20</TT >, <TT CLASS="literal" >21-30</TT > and so on. Also, search results cache enables the <SPAN CLASS="emphasis" ><I CLASS="emphasis" >search in found</I ></SPAN > feature. </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8461" ></A ><H3 >The <CODE CLASS="option" >ps</CODE > parameter</H3 ><P > <SPAN CLASS="application" >MySQL</SPAN > and <SPAN CLASS="application" >PostgreSQL</SPAN > users can specify <CODE CLASS="option" >ps=yes</CODE > to tell <SPAN CLASS="application" >indexer</SPAN > to use the <SPAN CLASS="emphasis" ><I CLASS="emphasis" >prepared statement</I ></SPAN > <ACRONYM CLASS="acronym" >API</ACRONYM > at crawling and indexing time. </P ><P > Using prepared statements for a series of similar <ACRONYM CLASS="acronym" >SQL</ACRONYM > queries is usually somewhat faster than direct execution of the same set of non-prepared <ACRONYM CLASS="acronym" >SQL</ACRONYM > statements, however prepared statements for <SPAN CLASS="application" >MySQL</SPAN > and <SPAN CLASS="application" >PostgreSQL</SPAN > appeared in <SPAN CLASS="application" >mnoGoSearch</SPAN > version <TT CLASS="literal" >3.3.8</TT > and is not enabled by default yet for stability purposes. </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8478" ></A ><H3 >Parameters affecting score (<SPAN CLASS="emphasis" ><I CLASS="emphasis" >wf</I ></SPAN > and <SPAN CLASS="emphasis" ><I CLASS="emphasis" >nwf</I ></SPAN >) </H3 ><P >Starting from the version <TT CLASS="literal" >3.3.0</TT > it is possible to specify the <CODE CLASS="option" >wf=XXXX</CODE > parameter for <B CLASS="command" >DBAddr</B > in <TT CLASS="filename" >search.htm</TT >. Starting from the version <TT CLASS="literal" >3.3.3</TT >, <CODE CLASS="option" >nwf=XXXX</CODE > is also allowed. </P ><P > These parameters are useful if you merge two or more databases and want to give more score to the search results coming from a certain database. </P ><P > The <B CLASS="command" >DBAddr</B > parameters have higher precedence over the search query parameters. For example, if <CODE CLASS="option" >wf</CODE > is specified as a <B CLASS="command" >DBAddr</B > parameter, then the global <B CLASS="command" >wf</B > values (specified in <CODE CLASS="varname" >QUERY_STRING</CODE > or using <A HREF="msearch-cmdref-wf.html" >wf</A > in <TT CLASS="filename" >search.htm</TT >) are not used. The format of the <CODE CLASS="option" >wf</CODE > and <CODE CLASS="option" >nwf</CODE > <B CLASS="command" >DBAddr</B > parameters is similar to the format described in <A HREF="msearch-doingsearch.html#search-changeweight" >the Section called <I >Changing weights of the different document parts at search time</I > in Chapter 10</A >. <PRE CLASS="programlisting" > DBAddr mysql://root@localhost/db1/?wf=FFFF DBAddr mysql://root@localhost/db2/?wf=1111 DBAddr mysql://root@localhost/db3/?wf=1111 </PRE > </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8503" ></A ><H3 >The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >MaxResults</I ></SPAN > parameter</H3 ><P >Starting from the version <TT CLASS="literal" >3.3.0</TT >, the <CODE CLASS="option" >MaxResults=num</CODE > parameter is available to specify the maximum number of search results returned from the database. It can be useful if you want to add a limited number of sponsored links in the top of the search results: <PRE CLASS="programlisting" > DBAddr mysql://root@localhost/avd/?wf=FFFF=1&MaxResults=1 DBAddr mysql://root@localhost/db1/?wf=1111 DBAddr mysql://root@localhost/db2/?wf=1111 </PRE > </P ><P > <CODE CLASS="varname" >MaxResults</CODE > affects the value of the <CODE CLASS="varname" >$(total)</CODE > template variable. The number of results beyond <CODE CLASS="varname" >MaxResults</CODE > is not included into <CODE CLASS="varname" >$(total)</CODE >. </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8515" ></A ><H3 >The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >DebugSQL</I ></SPAN > parameter</H3 ><P >Starting from the version <TT CLASS="literal" >3.3.3</TT >, the <CODE CLASS="option" >DebugSQL=yes/no</CODE > parameter is understood. When <CODE CLASS="option" >DebugSQL</CODE > is set to <TT CLASS="literal" >yes</TT >, <SPAN CLASS="application" >indexer</SPAN > and <SPAN CLASS="application" >search.cgi</SPAN > print all <ACRONYM CLASS="acronym" >SQL</ACRONYM > queries sent to the database. <SPAN CLASS="application" >mnoGoSearch</SPAN > must be compiled with <TT CLASS="literal" >--with-debug</TT >, otherwise <CODE CLASS="option" >DebugSQL=yes</CODE > is ignored. <PRE CLASS="programlisting" > DBAddr mysql://root@localhost/test/?DebugSQL=yes </PRE > </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8530" ></A ><H3 >The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >TrackQuery</I ></SPAN > parameter</H3 ><P > Use the <CODE CLASS="option" >trackquery=yes</CODE > parameter to activate search query tracking. Please refer to <A HREF="msearch-track.html" >the Section called <I >Tracking search queries <A NAME="AEN6117" ></A ></I > in Chapter 10</A > for details.. </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8536" ></A ><H3 >Parameters related to <CODE CLASS="option" >DBMode=blob</CODE ></H3 ><P >Starting from the version <TT CLASS="literal" >3.2.36</TT >, <B CLASS="command" >DBAddr</B > supports the <CODE CLASS="option" >Deflate=yes|no</CODE > parameter. With <CODE CLASS="option" >Deflate=yes</CODE > specified, <SPAN CLASS="application" >indexer</SPAN > compresses data when creating fast search index with <KBD CLASS="userinput" >indexer -Eblob</KBD >, which gives a smaller database size and faster search. This option is effective for <CODE CLASS="option" >DBMode=blob</CODE > only. There is no need to specify this option in search template, <SPAN CLASS="application" >search.cgi</SPAN > detects and handles compressed data automatically. <PRE CLASS="programlisting" > DBAddr mysql://foo:bar@localhost/mnogosearch/?DBMode=blob&Deflate=yes </PRE > </P ><P >Starting from the version <TT CLASS="literal" >3.2.36</TT >, <B CLASS="command" >DBAddr</B > supports <CODE CLASS="option" >zint4=yes|no</CODE > parameter. With <CODE CLASS="option" >zint4=yes</CODE > specified, <SPAN CLASS="application" >indexer</SPAN > compresses document <CODE CLASS="varname" >IDs</CODE > using a special compression method which we called <SPAN CLASS="emphasis" ><I CLASS="emphasis" >zint4</I ></SPAN >. This method is very effective for a sorted array of document <CODE CLASS="varname" >IDs</CODE > and compresses data up to <TT CLASS="literal" >85%</TT > with relative good decompression speed. In conjunction with the <CODE CLASS="option" >Deflate=yes</CODE > parameter, compression ratio can be up to <TT CLASS="literal" >99.8%</TT >. This option is used with <CODE CLASS="option" >DBMode=blob</CODE >, for the <CODE CLASS="varname" >#rec_id</CODE > array only. <PRE CLASS="programlisting" > DBAddr mysql://foo:bar@localhost/mnogosearch/?DBMode=blob&Deflate=yes&zint4=yes </PRE > </P ></DIV ><DIV CLASS="refsect2" ><A NAME="AEN8564" ></A ><H3 ><SPAN CLASS="application" >MySQL</SPAN > specific parameters</H3 ><DIV CLASS="refsect3" ><A NAME="AEN8567" ></A ><H4 ><SPAN CLASS="emphasis" ><I CLASS="emphasis" >MyCnfGroup</I ></SPAN > - Loading <TT CLASS="filename" >my.cnf</TT > file</H4 ><P >When initializing a connection to <SPAN CLASS="application" >MySQL</SPAN >, <SPAN CLASS="application" >mnoGoSearch</SPAN > forces loading of the <TT CLASS="filename" >my.cnf</TT > configuration file from the <TT CLASS="literal" >client</TT > option group by default. Use <CODE CLASS="option" >MyCnfGroup=group</CODE > to load options from another group, or <CODE CLASS="option" >MyCnfGroup=no</CODE > to prevent loading of <TT CLASS="filename" >my.cnf</TT >: <PRE CLASS="programlisting" > # Load options from a non-default option group DBAddr mysql://foo:bar@localhost/mnogosearch/?MyCnfGroup=mnogosearch # Prevent loading my.cnf DBAddr mysql://foo:bar@localhost/mnogosearch/?MyCnfGroup=no </PRE > When connecting to <SPAN CLASS="application" >MySQL</SPAN >, <SPAN CLASS="application" >mnoGoSearch</SPAN > uses <SPAN CLASS="application" >MySQL</SPAN > <SPAN CLASS="application" >C</SPAN > <ACRONYM CLASS="acronym" >API</ACRONYM > call to tell the <SPAN CLASS="application" >MySQL</SPAN > connection handler which option group to load (unless <SPAN CLASS="emphasis" ><I CLASS="emphasis" >MyCnfGroup=no</I ></SPAN > is specified): <PRE CLASS="programlisting" > mysql_options(mysql, MYSQL_READ_DEFAULT_GROUP, MyCnfGroup); </PRE > </P ></DIV ><DIV CLASS="refsect3" ><A NAME="AEN8588" ></A ><H4 ><SPAN CLASS="emphasis" ><I CLASS="emphasis" >SQLLog</I ></SPAN > - Using general log</H4 ><P ><SPAN CLASS="application" >MySQL</SPAN > users can specify whether to switch <SPAN CLASS="application" >MySQL</SPAN > query logging on/off using the <CODE CLASS="option" >SQLLog</CODE > parameter: <PRE CLASS="programlisting" > DBAddr mysql://foo:bar@localhost/mnogosearch/?sqllog=0 DBAddr mysql://foo:bar@localhost/mnogosearch/?sqllog=1 </PRE > If <CODE CLASS="option" >SQLLog</CODE > parameter is given, then <SPAN CLASS="application" >mnoGoSearch</SPAN > sends the <KBD CLASS="userinput" >SET SQL_LOG_OFF=X</KBD > query after connection is established. Only users with <SPAN CLASS="application" >MySQL</SPAN > <SPAN CLASS="emphasis" ><I CLASS="emphasis" >SUPER</I ></SPAN > privilege can use this parameter. </P ></DIV ><DIV CLASS="refsect3" ><A NAME="AEN8601" ></A ><H4 ><SPAN CLASS="emphasis" ><I CLASS="emphasis" >SQLLogBin</I ></SPAN > - Using binary log</H4 ><P ><SPAN CLASS="application" >MySQL</SPAN > users can specify whether to do binary logging by setting the <CODE CLASS="option" >SQLLogBin</CODE > parameter: <PRE CLASS="programlisting" > DBAddr mysql://foo:bar@localhost/mnogosearch/?sqllogbin=0 DBAddr mysql://foo:bar@localhost/mnogosearch/?sqllogbin=1 </PRE > If <CODE CLASS="option" >SQLLogBin</CODE > parameter is given, then <SPAN CLASS="application" >mnoGoSearch</SPAN > sends the <KBD CLASS="userinput" >SET SQL_LOG_BIN=X</KBD > after connection is established. Only users with <SPAN CLASS="application" >MySQL</SPAN > <SPAN CLASS="emphasis" ><I CLASS="emphasis" >SUPER</I ></SPAN > privilege can use this parameter. </P ></DIV ><DIV CLASS="refsect3" ><A NAME="AEN8613" ></A ><H4 ><SPAN CLASS="emphasis" ><I CLASS="emphasis" >Compress</I ></SPAN > - Using compression in client-server protocol</H4 ><P > <PRE CLASS="programlisting" > # Enable client-server compression DBAddr mysql://foo:bar@localhost/mnogosearch/?Compress=yes # Disable client-server compression DBAddr mysql://foo:bar@localhost/mnogosearch/?Compress=no </PRE > </P ><P > If <CODE CLASS="option" >Compression=yes</CODE > is specified then <SPAN CLASS="application" >mnoGoSearch</SPAN > uses <SPAN CLASS="application" >MySQL</SPAN > <SPAN CLASS="application" >C</SPAN > <ACRONYM CLASS="acronym" >API</ACRONYM > call to activate client-server compression: <PRE CLASS="programlisting" > mysql_options(mysql, MYSQL_OPT_COMPRESS, 0); </PRE > </P ><P > If <CODE CLASS="option" >Compression=no</CODE > is specified, or <CODE CLASS="option" >Compression</CODE > is omitted, then this call is not done and therefore no compression happens. </P ><P > Compression improves crawling, indexing and search performance when connecting to a remote <SPAN CLASS="application" >MySQL</SPAN > server. It is not recommended to use compression with <TT CLASS="literal" >localhost</TT >. </P ></DIV ></DIV ></DIV ><DIV CLASS="refsect1" ><A NAME="AEN8631" ></A ><H2 >Examples</H2 ><DIV CLASS="informalexample" ><P ></P ><A NAME="AEN8633" ></A ><PRE CLASS="programlisting" > DBAddr mysql://foo:bar@localhost/mnogosearch/?DBMode=multi DBAddr mysql://foo:pwd%3Awith%40special%3Cchars@localhost/mnogosearch/ </PRE ><P ></P ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="msearch-cmdref-dateformat.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="msearch-cmdref-defaultcontenttype.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >DateFormat</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="msearch-cmdref.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >DefaultContentType</TD ></TR ></TABLE ></DIV ><!--#include virtual="body-after.html"--></BODY ></HTML >