Register

Login

• search
• browse source
• diff source
• search source variables

Error Buddy

Do you have an error message from your application? Then find the answer with Error Buddy. You can search over 40000 source code files and troubleshooting documents using our beta lucene/nutch search interface or if you prefer, search as normal using google. With LXR technology you can drill right down into the line of source code where it came from with full cross-referencing.

If after searching you didn't get your ideal answer, or you are still unclear what the error means, you can choose to post that question to the community forums following the link included in the search results.

corestack/ phpMyAdmin-2.6.1-pl3/ Documentation.txt [1.6]

    ______________________________________________________________________
 
    Top  -  Requirements  -  Introduction  -  Installation  -  Configuration
    Transformations  -  FAQ  -  Developers  -  Credits  -  Translators
    ______________________________________________________________________
 
                       phpMyAdmin 2.6.1-pl3 Documentation
 
      * SourceForge phpMyAdmin project page   [ http://www.phpmyadmin.net/ ] 
      * Local documents:
           + Version history: ChangeLog
           + General notes: README
           + License: LICENSE
      * Documentation version: $Id: Documentation.html,v 2.103.2.5 2005/03/03        20:54:24 rabus Exp $
 
 Requirements
 
      * PHP
           + You need PHP 4.1.0 or newer (*)
           + If you want to display inline thumbnails of JPEGs with the original
             aspect ratio, you also need GD2 support in PHP
           + Starting with phpMyAdmin 2.6.1, MIME-based transformations that use
             an external program need PHP 4.3.0 or newer
      * MySQL 3.23.32 or newer (details);
      * Not really a requirement but a strong suggestion: if you are using th       e "cookie" authentication method, having the mcrypt PHP extension on
        your web server accelerates not only the login phase but every other
        action that you do in phpMyAdmin.
      * a web-browser (doh!).
 
 Introduction
 
    phpMyAdmin can manage a whole MySQL server (needs a super-user) as well a   s a single database. To accomplish the latter you'll need a properly set    up MySQL user who can read/write only the desired database. It's up to   you to look up the appropriate part in the MySQL manual.
    Currently phpMyAdmin can:
      * create and drop databases
      * create, copy, drop, rename and alter tables
      * do table maintenance
      * delete, edit and add fields
      * execute any SQL-statement, even batch-queries
      * manage keys on fields
      * load text files into tables
      * create (*) and read dumps of tables
      * export (*) data to CSV, XML and Latex formats
      * administer multiple servers
      * manage MySQL users and privileges
      * check referential integrity in MyISAM tables
      * using Query-by-example (QBE), create complex queries automatically co       nnecting required tables
      * create PDF graphics of your Database layout
      * search globally in a database or a subset of it
      * transform stored data into any format using a set of predefined funct       ions, like displaying BLOB-data as image or download-link or ...
      * support InnoDB tables and foreign keys (see FAQ 3.6)
      * support mysqli, the improved MySQL extension (see FAQ 1.17)
      * communicate in 47 different languages
 
    (*)  phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dump   s and CSV exports if you use PHP4 >= 4.0.4 with Zlib support (--with-zli   b) and/or Bzip2 support (--with-bz2).
 
 Installation
 
    NOTE: phpMyAdmin does not apply any special security methods to the MySQL    database server. It is still the system administrator's job to grant pe   rmissions on the MySQL databases properly. phpMyAdmin's "Privileges" pag   e can be used for this.
 
    Warning for Mac users:if you are on a MacOS version before OS X, StuffIt   unstuffs with Mac formats.
    So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin script   s before uploading them to your server, as PHP seems not to like Mac-sty   le end of lines character ("\r").
 
   Quick Install
 
     1. Untar or unzip the distribution (be sure to unzip the subdirectories)       : tar -xzvf phpMyAdmin_x.x.x.tar.gz in your webserver's document root.
        If you don't have direct access to your document root, put the files in
        a directory on your local machine, and, after step 3, transfer the
        directory on your web server using, for example, ftp.
     2. Ensure that all the scripts have the appropriate owner (if PHP is run       ning in safe mode, having some scripts with an owner different from the
        owner of other scripts will be a problem). See FAQ 4.2 for suggestions.
     3. Open the file config.inc.php in your favorite editor and change the v       alues for host, user, password and authentication mode to fit your
        environment.  Here, "host" means the MySQL server. Also insert the
        correct value for $cfg['PmaAbsoluteUri']. Have a look at Configuration
        section  for  an  explanation  of all values. Please also read the
        remaining  of  this  Installation  section  for  information about
        authentication modes and the linked-tables infrastructure.
     4. It is recommended that you protect the directory in which you install       ed phpMyAdmin (unless it's on a closed intranet, or you wish to use
        HTTP  or  cookie authentication), for example with HTTP-AUTH (in a
        .htaccess  file).  See  the  multi-user sub-section of the FAQ for
        additional information, especially FAQ 4.4.
     5. Open the file <www.your-host.com>/<your-install-dir>/index.php in you       r browser. phpMyAdmin should now display a welcome screen and your
        databases, or a login dialog if using HTTP or cookie authentication
        mode.
 
   Linked-tables infrastructure
 
    For a whole set of new features (bookmarks, comments, SQL-history, PDF-ge   neration, field contents transformation, etc.) you need to create a set   of special tables. Those tables can be located in your own database, or   in a central database for a multi-user installation (this database would    then be accessed by the controluser, so no other user should have right   s to it).
    Please look at your scripts/ directory, where you should find a file call   ed create_tables.sql. (If you are using a Windows server, pay special at   tention to FAQ 1.23).
    If your MySQL server's version is 4.1.2 or later, please use create_table   s_mysql_4_1_2+.sql instead, for a new installation.
    If you already had this infrastructure and upgraded to MySQL 4.1.2 or lat   er, please use upgrade_tables_mysql_4_1_2+.sql.
    You can use your phpMyAdmin to create the tables for you. Please be aware    that you may need special (administrator) privileges to create the data   base and tables, and that the script may need some tuning, depending on   the database name.
    After having imported the create_tables.sql file, you should specify the   table names in your config.inc.php file. The directives used for that ca   n be found in the Configuration section. You will also need to have a co   ntroluser with the proper rights to those tables (see section Using auth   entication modes below).
 
   Upgrading from an older version
 
      * You can safely copy your older config.inc.php over a new one, if you       can live with default values for possible new parameters (you can check
        release notes to see what new features were added). This compatibility
        will stay for long time, current version supports importing config files
        from 2.2 and maybe even older (nobody has tried that).
 
   Using authentication modes
 
      * HTTP and cookie authentication modes are recommended in a multi-user       environment where you want to give users access to their own database
        and don't want them to play around with others.
        Nevertheless be aware that MS Internet Explorer seems to be really buggy
        about cookies, at least till version 6. And PHP 4.1.1 is also a bit
        buggy in this area!
        Even in a single-user environment, you might prefer to use HTTP or
        cookie mode so that your user/password pair are not in clear in the
        configuration file.
      * HTTP and cookie authentication modes are more secure: the MySQL login        information does not need to be set in the phpMyAdmin configuration
        file (except possibly for the controluser).
        However, keep in mind that the password travels in plain text, unless
        you are using the HTTPS protocol.
        In cookie mode, the password is stored, encrypted with the blowfish
        algorithm, in a temporary cookie.
      * Note: starting with phpMyAdmin 2.6.1, configuring the controluser to       enable HTTP and cookie authentication applies only to MySQL servers
        older than 4.1.2.
        For 'HTTP' and 'cookie' modes, phpMyAdmin needs a controluser that has
        only  the  SELECT  privilege on the mysql.user (all columns except
        "Password"),  mysql.db (all columns), mysql.host (all columns) and
        mysql.tables_priv (all columns except "Grantor" & "Timestamp") tables.
        You must specify the details for the controluser in the config.inc.php
        file       under      the      $cfg['Servers'][$i]['controluser']&
        $cfg['Servers'][$i]['controlpass'] settings.
        The following example assumes you want to use pma as the controluser and
        pmapass as the controlpass, but this is only an example: use something
        else in your file!
        Of course you have to replace localhost by the webserver's host if it's
        not the same as the MySQL server's one.
 
 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
 GRANT SELECT (
     Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
     Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
     File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
     Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
     Execute_priv, Repl_slave_priv, Repl_client_priv
     ) ON mysql.user TO 'pma'@'localhost';
 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
     ON mysql.tables_priv TO 'pma'@'localhost';
 
        If you are using an old MySQL version (below 4.0.2), please replace the
        first GRANT SELECT query by this one:
 
 GRANT SELECT (
     Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
     Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
     File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
     ) ON mysql.user TO 'pma'@'localhost';
 
        ... and if you want to use the many new relation and bookmark features:
 
 GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db>.* TO 'pma'@'localhost';
 
        (this of course requires you to have a special DB for phpMyAdmin, the
        contents will be explained later)
        Of course, the above queries only work if your MySQL version supports
        the GRANT command. This is the case since 3.22.11.
      * Then each of the true users should be granted a set of privileges on       a set of particular databases. Normally you shouldn't give global
        privileges to an ordinary user, unless you understand the impact of
        those privileges (for example, you are creating a superuser).
        For example, to grant the user real_user with all privileges on the
        database user_base:
           GRANT  ALL  PRIVILEGES  ON user_base.* TO 'real_user'@localhost
        IDENTIFIED BY 'real_password';
        What  the user may now do is controlled entirely by the MySQL user
        management system.
        With HTTP or cookie authentication mode, you don't need to fill the
        user/password fields inside the $cfg['Servers'] array.
 
     'http' authentication mode
 
      * Was called 'advanced' in versions before 2.2.3.
      * Introduced in 1.3.0, it uses Basic HTTP authentication method and all       ows you to login as any valid MySQL user.
      * Is supported with PHP running as an Apache module. For IIS (ISAPI) su       pport using CGI PHP, see FAQ 1.32.
      * See also FAQ 4.4 about not using the .htaccess mechanism along with '       http' authentication mode.
 
     'cookie' authentication mode
 
      * You can use this method as a replacement for the HTTP authentication       (for example, if you're running IIS).
      * Obviously, the user must enable cookies in the browser.
      * With this mode, the user can truly logout of phpMyAdmin and login bac       k with the same username.
      * If you want to login to arbitrary server see $cfg['AllowArbitraryServ       er'] directive.
      * See also the requirements section for a way to improve the interface       speed while using this mode.
 
     'config' authentication mode
 
      * This mode is the less secure one because it requires you to fill the        $cfg['Servers'][$i]['user'] and $cfg['Servers'][$i]['password'] fields.
        But  you  don't  need  to  setup  a  "controluser" here: using the
        $cfg['Servers'][$i]['only_db'] might be enough.
      * In the ISP FAQ section, there is an entry explaining how to protect y       our configuration file.
      * For additional security in this mode, you may wish to consider the Ho       st  authentication  $cfg['Servers'][$i]['AllowDeny']['order'] and
        $cfg['Servers'][$i]['AllowDeny']['rules'] configuration directives.
 
 Configuration
 
    Warning for Mac users: PHP seems not to like Mac end of lines character (   "\r"). So ensure you choose the option that allows to use the *nix end o   f line character ("\n") in your text editor before registering a script   you have modified.
 
    Configuration note: Almost all configurable data is placed in config.inc.   php. The parameters which relate to design (like colors) are placed in t   hemes/themename/layout.inc.php. You might also want to modify config.foo   ter.inc.php and config.header.inc.php files to add your site specific co   de to be included on start and end of each page.
 
    $cfg['PmaAbsoluteUri'] string
           Sets  here the complete URL (with full path) to your phpMyAdmin
           version. E.g.
           http://www.your_web.net/path_to_your_phpMyAdmin_directory/.
           phpMyAdmin needs this setting, because of requirements of the HTTP
           protocol, explained in RFC2616, section 14.30.
           Don't forget the slash at the end of your URL. The URL must contain
           characters that are valid for a URL, and on some servers, the path is
           case-sensitive.
           Starting with version 2.3.0, you can try to leave this parameter
           empty, because the program tries to auto-detect its proper value.
           Additional details are in the configuration file.
 
    $cfg['PmaAbsoluteUri_DisableWarning'] boolean
           By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the
           system detects your absolute URI automatically, we display a warning
           to remind you. If you have tested the automatic detection, and it
           works perfectly for your setup, then you can set this variable to
           squelch the warning.
 
    $cfg['PmaNoRelation_DisableWarning'] boolean
           Starting with version 2.3.0 phpMyAdmin offers a lot of features to
           work with master / foreign - tables (see
           $cfg['Servers'][$i]['pmadb']).
           If you tried to set this up and it does not work for you, have a look
           on the "Structure" page of one database where you would like to use
           it. You will find a link that will analyze why those features have
           been disabled.
           If you do not want to use those features set this variable to TRUE to
           stop this message from appearing.
 
    $cfg['blowfish_secret'] string
           Starting with version 2.5.2, the 'cookie' auth_type uses blowfish
           algorithm to encrypt the password.
           If  you  are  using the 'cookie' auth_type, enter here a random
           passphrase of your choice. It will be used internally by the blowfish
           algorithm: you won't be prompted for this passphrase. The maximum
           number of characters for this parameter seems to be 46.
 
    $cfg['Servers'] array
           Since  version 1.4.2, phpMyAdmin supports the administration of
           multiple MySQL servers. Therefore, a $cfg['Servers']-array has been
           added which contains the login information for the different servers.
           The first $cfg['Servers'][$i]['host'] contains the hostname of the
           first server, the second $cfg['Servers'][$i]['host'] the hostname of
           the second server, etc. If you have only one server to administer,
           simply leave free the hostname of the other $cfg['Server']-entries.
 
    $cfg['Servers'][$i]['host'] string
           The  hostname  or  IP  address of your $i-th MySQL-server. E.g.
           localhost.
 
    $cfg['Servers'][$i]['port'] string
           The port-number of your $i-th MySQL-server. Default is 3306 (leave
           blank). If you use "localhost" as the hostname, MySQL ignores this
           port number and connects with the socket, so if you want to connect
           to a port different from the default port, use "127.0.0.1" or the
           real hostname in $cfg['Servers'][$i]['host'].
 
    $cfg['Servers'][$i]['socket'] string
           The path to the socket to use. Leave blank for default.
           To use the socket feature you must run PHP 3.0.10 or more.
 
    $cfg['Servers'][$i]['connect_type'] string
           What type connection to use with the MySQL server. Your options are
           'socket' & 'tcp'. It defaults to 'tcp' as that is nearly guaranteed
           to be available on all MySQL servers, while sockets are not supported
           on some platforms.
           To use the socket mode, your MySQL server must be on the same machine
           as the Web server.
 
    $cfg['Servers'][$i]['extension'] string
           What php MySQL extension to use for the connection. Valid options
           are:
           mysql :  The classic MySQL extension. This is the recommended and
           default method at this time.
           mysqli :   The  improved MySQL extension. This extension became
           available with php 5.0.0 and is the recommended way to connect to a
           server running MySQL 4.1.x.
           Note: phpMyAdmin's MySQL 4.1 support is experimental!
 
    $cfg['Servers'][$i]['compress'] boolean
           Whether to use a compressed protocol for the MySQL server connection
           or not (experimental).
           This feature requires PHP >= 4.3.0.
 
    $cfg['Servers'][$i]['controluser'] string
           $cfg['Servers'][$i]['controlpass'] string
           Note: starting with phpMyAdmin 2.6.1, configuring the controluser to
           enable HTTP and cookie authentication applies only to MySQL servers
           older than 4.1.2.
           This  special  account is used for 2 distinct purposes: to make
           possible all relational features (see $cfg['Servers'][$i]['pmadb'])
           and, for a MySQL server older than 4.1.2, to enable a multi-user
           installation (http or cookie authentication mode).
           When  using  HTTP  or  cookie authentication modes (or 'config'
           authentication mode since phpMyAdmin 2.2.1), you need to supply the
           details  of  a  MySQL  account that has SELECT privilege on the
           mysql.user (all columns except "Password"), mysql.db (all columns) &
           mysql.tables_priv  (all columns except "Grantor" & "Timestamp")
           tables. This account is used to check what databases the user will
           see at login.
           Please see the install section on "Using authentication modes" for
           more information.
           Note that if you try login to phpMyAdmin with this "controluser", you
           could get some errors, depending the exact privileges you gave to the
           "controluser". phpMyAdmin does not support a direct login with the
           "controluser".
           In   phpMyAdmin   versions  before  2.2.5,  those  were  called
           "stduser/stdpass".
 
    $cfg['Servers'][$i]['auth_type'] string ['http'|'cookie'|'config']
           Whether config or cookie or http authentication should be used for
           this server.
 
           + 'config' authentication ($auth_type = 'config') is the plain old
             way: username and password are stored in config.inc.php.
           + 'cookie' authentication mode ($auth_type = 'cookie') as introduced
             in 2.2.3 allows you to log in as any valid MySQL user with the help
             of cookies. Log name and password are stored in cookies during the
             session and password is deleted when it ends. This can also allow
             you to login in arbitrary server if $cfg['AllowArbitraryServer']
             enabled.
           + 'http' authentication (was called 'advanced' in older versions)
             ($auth_type = 'http') as introduced in 1.3.0 allows you to log in
             as any valid MySQL user via HTTP-Auth.
 
           Please see the install section on "Using authentication modes" for
           more information.
 
    $cfg['Servers'][$i]['user'] string
           $cfg['Servers'][$i]['password'] string
           The user/password-pair which phpMyAdmin will use to connect to this
           MySQL-server. This user/password pair is not needed when HTTP or
           cookie authentication is used, and should be empty.
 
    $cfg['Servers'][$i]['only_db'] string or array
           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
           ("_"  and  "%"):  if you want to use literal instances of these
           characters, escape them (I.E. use 'my\_db' and not 'my_db').
           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 it does not replace the privileges rules of the
           MySQL database server. If set, it just means only these databases
           will be displayed but not that all other databases can't be used.
           An    example    of    using    more    that    one   database:
           $cfg['Servers'][$i]['only_db'] = array('db1', 'db2');
           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.
           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: $cfg['Servers'][$i]['only_db'] = array('db3', 'db4', '*');
           instead to tell phpMyAdmin that it should display db3 and db4 on top,
           and the rest in alphabetic order.
 
    $cfg['Servers'][$i]['verbose'] string
           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.
 
    $cfg['Servers'][$i]['pmadb'] string
           The name of the database containing the linked-tables infrastructure.
           See the Linked-tables infrastructure section in this document to see
           the benefits of this infrastructure, and for a quick way of creating
           this database and the needed tables.
           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 $cfg['Servers'][$i]['pmadb'].
           For a multi-user installation, set this parameter to the name of your
           central database containing the linked-tables infrastructure.
 
    $cfg['Servers'][$i]['bookmarktable'] string
           Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can
           be useful for queries you often run.
           To allow the usage of this functionality:
 
           + set up pmadb and the linked-tables infrastructure
           + enter the table name in $cfg['Servers'][$i]['bookmarktable']
 
    $cfg['Servers'][$i]['relation'] string
           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
 
           + make clickable, when you browse the master table, the data values
             that point to the foreign table;
           + display in an optional tool-tip the "display field" when browsing
             the master table, if you move the mouse to a column containing a
             foreign key (use also the 'table_info' table);
             (see FAQ 6.7)
           + in edit/insert mode, display a drop-down list of possible foreign
             keys (key value and "display field" are shown)
             (see FAQ 6.21)
           + display links on the table properties page, to check referential
             integrity (display missing foreign keys) for each described key;
           + in query-by-example, create automatic joins (see FAQ 6.6)
           + enable you to get a PDF schema of your database (also uses the
             table_coords table).
 
           The keys can be numeric or character.
           To allow the usage of this functionality:
 
           + set up pmadb and the linked-tables infrastructure
           + put the relation table name in $cfg['Servers'][$i]['relation']
           + now as normal user open phpMyAdmin and for each one of your tables
             where you want to use this feature, click "Structure/Relation
             view/" and choose foreign fields.
 
           Please note that in the current version, master_db must be the same
           as foreign_db. Those fields have been put in future development of
           the cross-db relations.
 
    $cfg['Servers'][$i]['table_info'] string
           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.
           This configuration variable will hold the name of this special table.
           To allow the usage of this functionality:
 
           + set up pmadb and the linked-tables infrastructure
           + put the table name in $cfg['Servers'][$i]['table_info']
           + then for each table where you want to use this feature, click
             "Structure/Relation view/Choose field to display" to choose the
             field.
 
           Usage tip: Display field.
 
    $cfg['Servers'][$i]['table_coords'] string
           $cfg['Servers'][$i]['pdf_pages'] string
           Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
           the relations between your tables. To do this it needs two tables
           "pdf_pages" (storing information about the available PDF pages) and
           "table_coords" (storing coordinates where each table will be placed
           on a PDF schema output).
           You must be using the "relation" feature.
           To allow the usage of this functionality:
 
           + set up pmadb and the linked-tables infrastructure
           + put the correct table names in $cfg['Servers'][$i]['table_coords']
             and $cfg['Servers'][$i]['pdf_pages']
 
           Usage tips: PDF output.
 
    $cfg['Servers'][$i]['column_info'] string
           Since release 2.3.0 you can store comments to describe each column
           for each table. These will then be shown on the "printview".
           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.
           Also new in release 2.5.0 is a MIME-transformation system which is
           also based on the following table structure. See Transformations for
           further information. To use the MIME-transformation system, your
           column_info  table has to have the three new fields 'mimetype',
           'transformation', 'transformation_options'.
           To allow the usage of this functionality:
 
           + set up pmadb and the linked-tables infrastructure
           + put the table name in $cfg['Servers'][$i]['column_info']
           + to update your PRE-2.5.0 Column_comments Table use this:
                  ALTER TABLE `pma_column_comments`
                    ADD `mimetype` VARCHAR( 255 ) NOT NULL ,
                    ADD `transformation` VARCHAR( 255 ) NOT NULL ,
                    ADD `transformation_options` VARCHAR( 255 ) NOT NULL ;
             and remember that the Variable in config.inc.php has been renamed
             from
             $cfg['Servers'][$i]['column_comments']                     to
             $cfg['Servers'][$i]['column_info']
 
    $cfg['Servers'][$i]['history'] string
           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.
           Using $cfg['QueryHistoryMax'] 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.
           The query history is only available if you use the JavaScript-based
           query window, see $cfg['QueryFrame'].
           To allow the usage of this functionality:
 
           + set up pmadb and the linked-tables infrastructure
           + put the table name in $cfg['Servers'][$i]['history']
 
    $cfg['Servers'][$i]['verbose_check'] boolean
           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 TRUE (default) phpMyAdmin will check if you
           have the latest table structure available. If not, it will emit a
           warning to the superuser.
           You can disable this checking behavior by setting the variable to
           false, which should offer a performance increase.
           Recommended to set to FALSE, when you are sure, your table structure
           is up to date.
 
    $cfg['Servers'][$i]['AllowRoot'] boolean
           Whether to allow root access, This is just simplification of rules
           below.
 
    $cfg['Servers'][$i]['AllowDeny']['order'] string
           If your rule order is empty, then IP authentication is disabled.
           If your rule order is set to 'deny,allow' 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.
           If your rule order is set to 'allow,deny' 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.
           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 must be listed
           in the allow rules, and not listed in the deny rules. This is the
           most secure means of using Allow/Deny rules, and was available in
           Apache by specifying allow and deny rules without setting any order.
 
    $cfg['Servers'][$i]['AllowDeny']['rules'] array of strings
           The general format for the rules is as such:
                 <'allow' | 'deny'> <username> [from] <ipmask>
           If you wish to match all users, it is possible to use a '%' as a
           wildcard in the username field.
           There are a few shortcuts you can use in the ipmask field as well:
                'all' -> 0.0.0.0/0
                'localhost' -> 127.0.0.1/8
           Having an empty rule list is equivalent to either using 'allow % from
           all' if your rule order is set to 'deny,allow' or 'deny % from all'
           if your rule order is set to 'allow,deny' or 'explicit'.
           For the IP matching system, the following work:
           xxx.xxx.xxx.xxx (an exact IP address)
           xxx.xxx.xxx.[yyy-zzz] (an IP address range)
           xxx.xxx.xxx.xxx/nn (CIDR, Classless Inter-Domain Routing type IP
           addresses)
           But the following does not work:
           xxx.xxx.xxx.xx[yyy-zzz] (partial IP address range)
 
    $cfg['ServerDefault'] integer
           If  you  have  more  than  one  server  configured, you can set
           $cfg['ServerDefault'] 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.
           If you have only one server configured, $cfg['ServerDefault'] MUST be
           set to that server.
 
    $cfg['OBGzip'] string/boolean
           Defines whether to use GZip output buffering for increased speed in
           HTTP transfers.
           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.
 
    $cfg['PersistentConnections'] boolean
           Whether persistent connections should be used or not (mysql_connect
           or mysql_pconnect).
 
    $cfg['ExecTimeLimit'] integer [number of seconds]
           Set the number of seconds a script is allowed to run. If seconds is
           set to zero, no time limit is imposed.
           This setting is used while importing/exporting dump files but has no
           effect when PHP is running in safe mode.
 
    $cfg['SkipLockedTables'] boolean
           Mark used tables and make it possible to show databases with locked
           tables (since 3.23.30).
 
    $cfg['ShowSQL'] boolean
           Defines  whether  SQL-queries generated by phpMyAdmin should be
           displayed or not.
 
    $cfg['AllowUserDropDatabase'] boolean
           Defines whether normal users (non-administrator) are allowed to
           delete their own database or not. If set as FALSE, the link "Drop
           Database" will not be shown, and even a "DROP DATABASE mydatabase"
           will be rejected. Quite practical for ISP's with many customers.
 
    $cfg['Confirm'] boolean
           Whether a warning ("Are your really sure...") should be displayed
           when you're about to lose data.
 
    $cfg['LoginCookieRecall'] boolean
           Define whether the previous login should be recalled or not in cookie
           authentication mode.
 
    $cfg['UseDbSearch'] boolean
           Define whether the "search string inside database" is enabled or not.
 
    $cfg['IgnoreMultiSubmitErrors'] boolean
           Define whether phpMyAdmin will continue executing a multi-query
           statement if one of the queries fails. Default is to abort execution.
 
    $cfg['VerboseMultiSubmit'] boolean
           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 TRUE.
 
    $cfg['AllowArbitraryServer'] boolean
           If enabled allows you to login to arbitrary server using cookie auth.
           NOTE: Please use this carefully, as this may allow to access MySQL
           servers behind firewall where your http server is placed.
 
    $cfg['LeftFrameLight'] boolean
           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']
 
    $cfg['LeftFrameTableSeparator'] string
           Defines a string to be used to nest table spaces. Defaults to '__'.
           This means if you have tables like 'first__second__third' this will
           be shown as a three-level hierarchie like: first > second > third. If
           set to FALSE or empty, the feature is disabled. NOTE: You shall not
           use this Separator in a table name at the beginning or end of a table
           name, or multiple times after another without any other characters in
           between.
 
    $cfg['LeftFrameTableLevel'] string
           Defines how many sublevels should be displayed when splitting up
           tables by the above Separator.
 
    $cfg['ShowTooltip'] boolean
           Defines whether to display table comment as tool-tip in left frame or
           not.
 
    $cfg['ShowTooltipAliasDB'] boolean
           If tool-tips are enabled and a DB comment is set, this will flip the
           comment and the real name. That means, if you have a table called
           'user0001' and add the comment 'MyName' on it, you will see the name
           'MyName' used consequently in the left frame and the tool-tip shows
           the real name of the DB.
 
    $cfg['ShowTooltipAliasTB'] boolean/string
           Same as $cfg['ShowTooltipAliasDB'], except this works for table
           names. When setting this to 'nested', the Alias of the Tablename is
           only   used   to   split/nest   the  tables  according  to  the
           $cfg['LeftFrameTableSeparator'] directive. So only the folder is
           called like the Alias, the tablename itself stays the real tablename.
 
    $cfg['LeftDisplayLogo'] boolean
           Defines whether to display the phpMyAdmin logo at the top of the left
           frame or not. Defaults to TRUE.
 
    $cfg['LeftDisplayServers'] boolean
           Defines whether to display a server choice at the top of the left
           frame or not. Defaults to FALSE.
 
    $cfg['DisplayServersList'] boolean
           Defines whether to display this server choice as links instead of in
           a drop-down. Defaults to FALSE (drop-down).
 
    $cfg['ShowStats'] boolean
           Defines whether to display space usage and statistics about databases
           and tables or not.
           Note that statistics requires at least MySQL 3.23.3 and that, at this
           date, MySQL doesn't return such information for Berkeley DB tables.
 
    $cfg['ShowMysqlInfo'] boolean
           $cfg['ShowMysqlVars'] boolean
           $cfg['ShowPhpInfo'] boolean
           $cfg['ShowChgPassword'] boolean
           Defines whether to display the "MySQL runtime information", "MySQL
           system variables", "PHP information" and "Change password " links or
           not for simple users at the starting main (right) frame. This setting
           does not check MySQL commands entered directly.
           Please note that to block the usage of phpinfo() in scripts, you have
           to put this in your php.ini:
               disable_functions = phpinfo()
           Also note that enabling the "Change password " link has no effect
           with "config" authentication mode: because of the hard coded password
           value in the configuration file, end users can't be allowed to change
           their passwords.
 
    $cfg['SuggestDBName'] boolean
           Defines whether to suggest a database name on the "Create Database"
           form or to keep the textfield empty.
 
    $cfg['ShowBlob'] boolean
           Defines whether BLOB fields are shown when browsing a table's content
           or not.
 
    $cfg['NavigationBarIconic'] boolean
           Defines whether navigation bar buttons contain text or symbols only.
 
    $cfg['ShowAll'] boolean
           Defines whether an user should be displayed a "show all (records)"
           button in browse mode or not.
 
    $cfg['MaxRows'] integer
           Number of rows displayed when browsing a result set. If the result
           set contains more rows, Previous/Next links will be shown.
 
    $cfg['Order'] string [DESC|ASC|SMART]
           Defines whether fields are displayed in ascending (ASC) order, in
           descending  (DESC)  order  or in a "smart" (SMART) order - I.E.
           descending order for fields of type TIME, DATE, DATETIME & TIMESTAMP,
           ascending order else- by default.
 
    $cfg['ProtectBinary'] boolean or string
           Defines whether BLOB or BINARY fields are protected from edition when
           browsing a table's content or not. Valid values are:
           - FALSE to allow edition of all fields;
           - blob to allow edition of all fields except BLOBS;
           - all to disallow edition of all BINARY or BLOB fields.
 
    $cfg['ShowFunctionFields'] boolean
           Defines whether MySQL functions fields should be displayed or not in
           edit/insert mode.
 
    $cfg['CharEditing'] string
           Defines which type of editing controls should be used for CHAR and
           VARCHAR fields. Possible values are:
 
           + input - this allows to limit size of text to size of field in
             MySQL, but has problems with newlines in fields
           + textarea - no problems with newlines in fields, but also no length
             limitations
 
           Default is old behavior so input.
 
    $cfg['ZipDump'] boolean
           $cfg['GZipDump'] boolean
           $cfg['BZipDump'] boolean
           Defines whether to allow the use of zip/GZip/BZip2 compression when
           creating a dump file or not.
 
    $cfg['CompressOnFly'] boolean
           Defines  whether to allow on the fly compression for GZip/BZip2
           compressed exports. This doesn't affect smaller dumps and allows to
           create larger dumps, that won't fit otherwise in memory due to php
           memory limit. Produced files contain more GZip/BZip2 headers, but all
           normal programs handle this correctly.
 
    $cfg['LightTabs'] string
           If set to True, do use less graphically intense tabs on the top of
           the mainframe.
 
    $cfg['PropertiesIconic'] string
           If set to True, will display icons instead of text for db and table
           properties links (like 'Browse', 'Select', 'Insert', ...).
           Can be set to 'both' if you want icons AND text.
           When set to False, will only show text.
 
    $cfg['PropertiesNumColumns'] integer
           How  many columns will be utilized to display the tables on the
           database property view? Default is 1 column. When setting this to a
           value larger than 1, the type of the database will be omitted for
           more display space.
 
    $cfg['DefaultTabServer'] string
           Defines the tab displayed by default on server view. Possible values:
           "main.php"     (recommended     for     multi-user     setups),
           "server_databases.php","server_status.php","server_variables.php",
           "server_privileges.php" or "server_processlist.php".
 
    $cfg['DefaultTabDatabase'] string
           Defines the tab displayed by default on database view. Possible
           values:    "db_details_structure.php",    "db_details.php"   or
           "db_search.php".
 
    $cfg['DefaultTabTable'] string
           Defines the tab displayed by default on table view. Possible values:
           "tbl_properties_structure.php",           "tbl_properties.php",
           "tbl_select.php" or "tbl_change.php".
 
    $cfg['MySQLManualBase'] string
           If  set to an URL which points to the MySQL documentation (type
           depends on $cfg['MySQLManualType']), appropriate help links are
           generated.
           See MySQL Documentation page for more information about MySQL manuals
           and their types.
 
    $cfg['MySQLManualType'] string
           Type of MySQL documentation:
 
           + old - old style used in phpMyAdmin 2.3.0 and earlier
           + searchable - "Searchable, with user comments"
           + chapters - "HTML, one page per chapter"
           + big - "HTML, all on one page"
           + none - do not show documentation links
 
    $cfg['DefaultLang'] string
           Defines  the default language to use, if not browser-defined or
           user-defined.
           See the select_lang.inc.php scri