documentation.html

phpMyAdmin图形界面化操作,我已经配置好了,只要把解要压缩后的文件放到站点下就可以用了

    </dt>
    <dd>
        When using auth_type = 'config', this is the user/password-pair
        which phpMyAdmin will use to connect to the
        MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
        cookie authentication is used and should be empty.</dd>
    <dt id="servers_nopassword">
        <span
        id="cfg_Servers_nopassword">$cfg['Servers'][$i]['nopassword']</span> boolean
    </dt>
    <dd>
        Allow attempt to log in without password when a login with password
        fails. This can be used together with http authentication, when
        authentication is done some other way and phpMyAdmin gets user name
        from auth and uses empty password for connecting to MySQL. Password
        login is still tried first, but as fallback, no password method is
        tried.</dd>
    <dt id="servers_only_db">
        <span id="cfg_Servers_only_db">$cfg['Servers'][$i]['only_db']</span> string or array
    </dt>
    <dd>
        If set to a (an array of) database name(s), only this (these) database(s)
        will be shown to the user. Since phpMyAdmin 2.2.1, this/these
        database(s) name(s) may contain MySQL wildcards characters
        (&quot;_&quot; and &quot;%&quot;): if you want to use literal instances
        of these characters, escape them (I.E. use <tt>'my\_db'</tt> and not
        <tt>'my_db'</tt>).<br />
        This setting is an efficient way to lower the server load since the
        latter does not need to send MySQL requests to build the available
        database list. But <span class="important">it does not replace the
        privileges rules of the MySQL database server</span>. If set, it just
        means only these databases will be displayed but
        <span class="important">not that all other databases can't be used.</span>
        <br /><br />

        An example of using more that one database:
        <tt>$cfg['Servers'][$i]['only_db'] = array('db1', 'db2');</tt>
        <br /><br />

        As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
        databases in the left frame, so that you can individually arrange your databases.<br />
        If you want to have certain databases at the top, but don't care about the others, you do not
        need to specify all other databases. Use:
        <tt>$cfg['Servers'][$i]['only_db'] = array('db3', 'db4', '*');</tt>
        instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
        order.</dd>

    <dt><span id="cfg_Servers_hide_db">$cfg['Servers'][$i]['hide_db']</span> string
    </dt>
    <dd>Regular expression for hiding some databases. This only hides them
        from listing, but a user is still able to access them (using, for example,
        the SQL query area). To limit access, use the MySQL privilege system.
        <br /><br />
        For example, to hide all databases starting with the letter &#34;a&#34;, use<br />
        <pre>$cfg['Servers'][$i]['hide_db'] = '^a';</pre>
        and to hide both &#34;db1&#34; and &#34;db2&#34; use <br />
        <pre>$cfg['Servers'][$i]['hide_db'] = '(db1|db2)';</pre>
        More information on regular expressions can be found in the
        <a href="http://php.net/manual/en/reference.pcre.pattern.syntax.php">
        PCRE pattern syntax</a> portion of the PHP reference manual.
        </dd>

    <dt id="cfg_Servers_verbose">$cfg['Servers'][$i]['verbose'] string</dt>
    <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
        this string will be displayed instead of the hostname in the pull-down
        menu on the main page. This can be useful if you want to show only
    certain databases on your system, for example. For HTTP auth, all
    non-US-ASCII characters will be stripped.</dd>

    <dt id="pmadb">
        <span id="cfg_Servers_pmadb">$cfg['Servers'][$i]['pmadb']</span> string
    </dt>
    <dd>The name of the database containing the linked-tables infrastructure.
        <br /><br />

        See the <a href="#linked-tables">Linked-tables infrastructure</a>
        section in this document to see the benefits of this infrastructure,
        and for a quick way of creating this database and the needed tables.
        <br /><br />

        If you are the only user of this phpMyAdmin installation, you can
        use your current database to store those special tables; in this
        case, just put your current database name in
        <tt>$cfg['Servers'][$i]['pmadb']</tt>. For a multi-user installation,
        set this parameter to the name of your central database containing
        the linked-tables infrastructure.</dd>

    <dt id="bookmark">
        <span id="cfg_Servers_bookmarktable">$cfg['Servers'][$i]['bookmarktable']</span> string
    </dt>
    <dd>Since release 2.2.0 phpMyAdmin allows users to bookmark queries. This can be
        useful for queries you often run.<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>enter the table name in
                <tt>$cfg['Servers'][$i]['bookmarktable']</tt></li>
        </ul>
    </dd>

    <dt id="relation">
        <span id="cfg_Servers_relation">$cfg['Servers'][$i]['relation']</span> string
    </dt>
    <dd>Since release 2.2.4 you can describe, in a special 'relation' table,
        which field is a key in another table (a foreign key). phpMyAdmin
        currently uses this to
        <ul><li>make clickable, when you browse the master table, the data values
                that point to the foreign table;</li>
            <li>display in an optional tool-tip the &quot;display field&quot;
                when browsing the master table, if you move the mouse to a column
                containing a foreign key (use also the 'table_info' table);<br />
                (see <a href="#faqdisplay"><abbr title="Frequently Asked Questions">
                FAQ</abbr> 6.7</a>)</li>
            <li>in edit/insert mode, display a drop-down list of possible foreign
                keys (key value and &quot;display field&quot; are shown)<br />
                (see <a href="#faq6_21"><abbr title="Frequently Asked Questions">
                FAQ</abbr> 6.21</a>)</li>
            <li>display links on the table properties page, to check referential
                integrity (display missing foreign keys) for each described key;
            </li>
            <li>in query-by-example, create automatic joins (see <a href="#faq6_6">
                <abbr title="Frequently Asked Questions">FAQ</abbr> 6.6</a>)</li>
            <li>enable you to get a <abbr title="Portable Document Format">PDF</abbr>
                schema of your database (also uses the table_coords table).</li>
        </ul>

        The keys can be numeric or character.<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 relation table name in
                <tt>$cfg['Servers'][$i]['relation']</tt></li>
            <li>now as normal user open phpMyAdmin and for each one of your
                tables where you want to use this feature, click
                &quot;Structure/Relation view/&quot; and choose foreign fields.
                </li>
        </ul>

        Please note that in the current version, <tt>master_db</tt>
        must be the same as <tt>foreign_db</tt>. Those fields have been put in
        future development of the cross-db relations.
    </dd>

    <dt id="table_info">
        <span id="cfg_Servers_table_info">$cfg['Servers'][$i]['table_info']</span> string
    </dt>
    <dd>
        Since release 2.3.0 you can describe, in a special 'table_info'
        table, which field is to be displayed as a tool-tip when moving the
        cursor over the corresponding key.<br />
        This configuration variable will hold the name of this special
        table. 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]['table_info']</tt></li>
            <li>then for each table where you want to use this feature,
                click &quot;Structure/Relation view/Choose field to display&quot;
                to choose the field.</li>
        </ul>
        Usage tip: <a href="#faqdisplay">Display field</a>.
    </dd>
    <dt id="table_coords">
        <span id="cfg_Servers_table_coords">$cfg['Servers'][$i]['table_coords']</span> string<br />
        <span id="cfg_Servers_pdf_pages">$cfg['Servers'][$i]['pdf_pages']</span> string
    </dt>
    <dd>Since release 2.3.0 you can have phpMyAdmin create
        <abbr title="Portable Document Format">PDF</abbr> pages showing
        the relations between your tables. To do this it needs two tables
        &quot;pdf_pages&quot; (storing information about the available
        <abbr title="Portable Document Format">PDF</abbr>
        pages) and &quot;table_coords&quot; (storing coordinates where each
        table will be placed on a <abbr title="Portable Document Format">PDF</abbr>
        schema output).<br /><br />

        You must be using the &quot;relation&quot; feature.<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 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"><abbr title="Portable Document Format">PDF</abbr> output</a>.
    </dd>

    <dt id="col_com">
        <span id="cfg_Servers_column_info">$cfg['Servers'][$i]['column_info']</span> 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:

                <pre>
ALTER TABLE `pma_column_comments`
    ADD `mimetype` VARCHAR( 255 ) NOT NULL,
    ADD `transformation` VARCHAR( 255 ) NOT NULL,
    ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
</pre>

                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 id="history">
        <span id="cfg_Servers_history">$cfg['Servers'][$i]['history']</span> string
    </dt>
    <dd>Since release 2.5.0 you can store your
        <abbr title="structured query language">SQL</abbr> 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
        <a href="#cfg_QueryHistoryMax" class="configrule">$cfg['QueryHistoryMax']</a>
        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 />