documentation.html

一个用PHP编写的

        To allow the usage of this functionality:
        <ul>
            <li>set up <a href="#pmadb">pmadb</a> and the linked-tables infrastructure</li>
            <li>
                put the correct table names in
                <tt>$cfg['Servers'][$i]['table_coords']</tt> and
                <tt>$cfg['Servers'][$i]['pdf_pages']</tt>
            </li>
        </ul>
        Usage tips: <a href="#faqpdf">PDF output</a>.
    </dd>

    <dt>
        <a name="col_com"></a>
        <b><a name="cfg_Servers_column_info"></a>$cfg['Servers'][$i]['column_info']</b> string
    </dt>
    <dd>
        <!-- This part requires a content update! -->
        Since release 2.3.0 you can store comments to describe each column
        for each table. These will then be shown on the &quot;printview&quot;.
        <br /><br />
        Starting with release 2.5.0, comments are consequently used on the table property
        pages and table browse view, showing up as tool-tips above the column name (properties page)
        or embedded within the header of table in browse view. They can also be shown
        in a table dump. Please see the relevant configuration directives later on.
        <br /><br />
        Also new in release 2.5.0 is a MIME-transformation system which is also based on
        the following table structure. See <a href="#transformations">Transformations</a>
        for further information. To use the MIME-transformation system, your column_info
        table has to have the three new fields 'mimetype', 'transformation', 'transformation_options'.
        <br /><br />
        To allow the usage of this functionality:
        <ul>
            <li>set up <a href="#pmadb">pmadb</a> and the linked-tables infrastructure</li>
            <li>
                put the table name in
                <tt>$cfg['Servers'][$i]['column_info']</tt>
            </li>
            <li>
                to update your PRE-2.5.0 Column_comments Table use this:<br />
                <tt>
                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ALTER TABLE `pma_column_comments` <br />
                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ADD `mimetype` VARCHAR( 255 ) NOT NULL ,<br />
                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ADD `transformation` VARCHAR( 255 ) NOT NULL ,<br />
                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ADD `transformation_options` VARCHAR( 255 ) NOT NULL ;<br />
                </tt>
                and remember that the Variable in <i>config.inc.php</i> has been renamed
                from <br /><tt>$cfg['Servers'][$i]['column_comments']</tt> to <tt>$cfg['Servers'][$i]['column_info']</tt>
            </li>
        </ul>
    </dd>

    <dt>
        <a name="history"></a>
        <b><a name="cfg_Servers_history"></a>$cfg['Servers'][$i]['history']</b> string
    </dt>
    <dd>
        Since release 2.5.0 you can store your SQL history, which means all queries you
        entered manually into the phpMyAdmin interface. If you don't want to use a table-
        based history, you can use the JavaScript-based history. Using that, all your
        history items are deleted when closing the window.<br /><br />

        Using <b><a name="cfg_QueryHistoryMax"></a>$cfg[QueryHistoryMax]</b> you can specify an amount of history items
        you want to have on hold. On every login, this list gets cut to the maximum amount.
        <br /><br />

        The query history is only available if JavaScript is enabled in your
        browser.
        <br /><br />

        To allow the usage of this functionality:
        <ul>
            <li>set up <a href="#pmadb">pmadb</a> and the linked-tables infrastructure</li>
            <li>
                put the table name in
                <tt>$cfg['Servers'][$i]['history']</tt>
            </li>
        </ul>
    </dd>

    <dt>
        <b><a name="cfg_Servers_verbose_check"></a>$cfg['Servers'][$i]['verbose_check']</b> boolean
    </dt>
    <dd>
        Because release 2.5.0 introduced the new MIME-transformation support, the
        column_info table got enhanced with three new fields. If the above variable is
        set to <tt>TRUE</tt> (default) phpMyAdmin will check if you have the latest table structure
        available. If not, it will emit a warning to the superuser.<br /><br />

        You can disable this checking behavior by setting the variable to false, which
        should offer a performance increase.<br /><br />

        Recommended to set to FALSE, when you are sure, your table structure is up to date.
    </dd>
    <dt>
        <b><a name="cfg_Servers_AllowRoot"></a>$cfg['Servers'][$i]['AllowRoot']</b> boolean
    </dt>
    <dd>
        Whether to allow root access, This is just simplification of rules below.
    </dd>
    <dt>
<a name="servers_allowdeny_order"></a>
        <b><a name="cfg_Servers_AllowDeny_order"></a>$cfg['Servers'][$i]['AllowDeny']['order']</b> string
    </dt>
    <dd>
        If your rule order is empty, then IP authentication is disabled.
        <br /><br />
        If your rule order is set to <tt>'deny,allow'</tt> then the system
        applies all deny rules followed by allow rules.
        Access is allowed by default. Any client which does not match a Deny
        command or does match an Allow command will be allowed access to the
        server.
        <br /><br />
        If your rule order is set to <tt>'allow,deny'</tt> then the system
        applies all allow rules followed by deny rules. Access is denied by
        default.  Any client which does not match an Allow directive or does
        match a Deny directive will be denied access to the server.
        <br /><br />
        If your rule order is set to 'explicit', the authentication is
        performed in a similar fashion to rule order 'deny,allow', with the
        added restriction that your host/username combination <b>must</b> be
        listed in the <i>allow</i> rules, and not listed in the <i>deny</i>
        rules. This is the <b>most</b> secure means of using Allow/Deny rules,
        and was available in Apache by specifying allow and deny rules without
        setting any order.
    </dd>
    <dt>
<a name="servers_allowdeny_rules"></a>
        <b><a name="cfg_Servers_AllowDeny_rules"></a>$cfg['Servers'][$i]['AllowDeny']['rules']</b> array of strings
    </dt>
    <dd>
        The general format for the rules is as such:<br />
        <tt>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
        &lt;'allow' | 'deny'&gt; &lt;username&gt; [from] &lt;ipmask&gt;
        </tt>
        <br /><br />

        If you wish to match all users, it is possible to use a <tt>'%'</tt> as
        a wildcard in the <i>username</i> field.<br />
        There are a few shortcuts you can use in the <i>ipmask</i> field as
        well (please note that those containing SERVER_ADDRESS might not be
        available on all webservers):<br /><br />
        <tt>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'all' -&gt; 0.0.0.0/0<br />
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'localhost' -&gt; 127.0.0.1/8<br />
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'localnetA' -&gt; SERVER_ADDRESS/8<br />
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'localnetB' -&gt; SERVER_ADDRESS/16<br />
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;'localnetC' -&gt; SERVER_ADDRESS/24
        </tt>
        <br /><br />

        Having an empty rule list is equivalent to either using
        <tt>'allow % from all'</tt> if your rule order is set to
        <tt>'deny,allow'</tt> or <tt>'deny % from all'</tt> if your rule order
        is set to <tt>'allow,deny'</tt> or <tt>'explicit'</tt>.
        <br /><br />

        For the IP matching system, the following work:<br />
        <tt>xxx.xxx.xxx.xxx</tt>        (an exact IP address)<br />
        <tt>xxx.xxx.xxx.[yyy-zzz]</tt>  (an IP address range)<br />
        <tt>xxx.xxx.xxx.xxx/nn</tt>     (CIDR, Classless Inter-Domain Routing type IP addresses)<br />
        But the following does not work:<br />
        <tt>xxx.xxx.xxx.xx[yyy-zzz]</tt> (partial IP address range)
    </dd>

    <dt><b><a name="cfg_ServerDefault"></a>$cfg[ServerDefault]</b> integer</dt>
    <dd>
        If you have more than one server configured, you can set
        <tt>$cfg['ServerDefault']</tt> to any one of them to autoconnect to
        that server when phpMyAdmin is started, or set it to 0 to be given a
        list of servers without logging in.<br />
        If you have only one server configured, <tt>$cfg['ServerDefault']</tt>
        MUST be set to that server.
    </dd>

    <dt><b><a name="cfg_OBGzip"></a>$cfg[OBGzip] </b>string/boolean</dt>
    <dd>
        Defines whether to use GZip output buffering for increased
        speed in HTTP transfers.<br />
        Set to true/false for enabling/disabling. When set to 'auto' (string),
        phpMyAdmin tries to enable output buffering and will automatically disable
        it, if your browser has some problems with buffering. IE6 with a certain patch
        is known to cause data corruption having enabled buffering.
    </dd>

    <dt><b><a name="cfg_PersistentConnections"></a>$cfg[PersistentConnections] </b>boolean</dt>
    <dd>
        Whether persistent connections should be used or not (mysql_connect or
        mysql_pconnect).
    </dd>

    <dt><b><a name="cfg_ForceSSL"></a>$cfg[ForceSSL] </b>boolean</dt>
    <dd>
        Whether to force using https while accessing phpMyAdmin.
    </dd>

    <dt><b><a name="cfg_ExecTimeLimit"></a>$cfg[ExecTimeLimit] </b>integer [number of seconds]</dt>
    <dd>
        Set the number of seconds a script is allowed to run. If seconds is set
        to zero, no time limit is imposed.<br />
        This setting is used while importing/exporting dump files but has no
        effect when PHP is running in safe mode.
    </dd>

    <dt><b><a name="cfg_MemoryLimit"></a>$cfg[MemoryLimit] </b>integer [number of bytes]</dt>
    <dd>
        Set the number of bytes a script is allowed to allocate. If number set
        to zero, no limit is imposed.<br />
        This setting is used while importing/exporting dump files but has no
        effect when PHP is running in safe mode.<br />
        You can also use any string as in php.ini, eg. '16M'.
    </dd>

    <dt><b><a name="cfg_SkipLockedTables"></a>$cfg[SkipLockedTables] </b>boolean</dt>
    <dd>
        Mark used tables and make it possible to show databases with locked
        tables (since 3.23.30).
    </dd>

    <dt><b><a name="cfg_ShowSQL"></a>$cfg[ShowSQL] </b>boolean</dt>
    <dd>
        Defines whether SQL-queries generated by phpMyAdmin should be displayed
        or not.
    </dd>

    <dt><b><a name="cfg_AllowUserDropDatabase"></a>$cfg[AllowUserDropDatabase] </b>boolean</dt>
    <dd>
        Defines whether normal users (non-administrator) are allowed to
        delete their own database or not. If set as FALSE, the link &quot;Drop
        Database&quot; will not be shown, and even a &quot;DROP DATABASE
        mydatabase&quot; will be rejected. Quite practical for ISP's with many
        customers.
  </dd>

    <dt><b><a name="cfg_Confirm"></a>$cfg[Confirm] </b>boolean</dt>
    <dd>
        Whether a warning (&quot;Are your really sure...&quot;) should be
        displayed when you're about to lose data.
    </dd>

    <dt><b><a name="cfg_LoginCookieRecall"></a>$cfg[LoginCookieRecall] </b>boolean</dt>
    <dd>
        Define whether the previous login should be recalled or not in cookie
        authentication mode.
    </dd>

    <dt><b><a name="cfg_UseDbSearch"></a>$cfg[UseDbSearch] </b>boolean</dt>
    <dd>
        Define whether the "search string inside database" is enabled or not.
    </dd>

    <dt><b><a name="cfg_IgnoreMultiSubmitErrors"></a>$cfg[IgnoreMultiSubmitErrors] </b>boolean</dt>
    <dd>
        Define whether phpMyAdmin will continue executing a multi-query
        statement if one of the queries fails. Default is to abort execution.
    </dd>

    <dt><b><a name="cfg_VerboseMultiSubmit"></a>$cfg[VerboseMultiSubmit] </b>boolean</dt>
    <dd>
        Define whether phpMyAdmin will output the results of each query of a
        multi-query statement embedded into the SQL output as inline comments.
        Defaults to <tt>TRUE</tt>.
    </dd>
    <dt>
<a name="AllowArbitraryServer"></a>
<b><a name="cfg_AllowArbitraryServer"></a>$cfg[AllowArbitraryServer] </b>boolean</dt>
    <dd>
        If enabled allows you to login to arbitrary server using cookie auth.
        <br /><br />
        <b>NOTE:</b> Please use this carefully, as this may allow to access
        MySQL servers behind firewall where your http server is placed.
        <br /><br />
    </dd>

    <dt><b><a name="cfg_LeftFrameLight"></a>$cfg[LeftFrameLight]</b> boolean</dt>
    <dd>
        Defines whether to use select-based menu and display only the current
        tables in the left frame (smaller page).
        Only in Non-Lightmode you can use the feature to display nested folders
        using $cfg['LeftFrameTableSeparator']
    </dd>

    <dt><b><a name="cfg_LeftFrameDBTree"></a>$cfg[LeftFrameDBTree]</b> boolean</dt>