Almost all configurable data is placed in config.inc.php. If this file
does not exist, please refer to the Installation section to create one. This
file only needs to contain the parameters you want to change from their
corresponding default value in libraries/config.default.php.
If a directive is missing from your file, you can just add another line with
the file. This file is for over-writing the defaults; if you wish to use the
default value there’s no need to add a line here.
The parameters which relate to design (like colors) are placed in
themes/themename/layout.inc.php. You might also want to create
config.footer.inc.php and config.header.inc.php files to add
your site specific code to be included on start and end of each page.
Note
Some distributions (eg. Debian or Ubuntu) store config.inc.php in
/etc/phpmyadmin instead of within phpMyAdmin sources.
Warning
Mac users should note that if you are on a version before
Mac OS X, PHP does not seem to
like Mac end of lines character (\r). So
ensure you choose the option that allows to use the *nix end of line
character (\n) in your text editor before saving a script you have
modified.
Sets here the complete URL (with full path) to your phpMyAdmin
installation’s directory. E.g.
http://www.example.net/path_to_your_phpMyAdmin_directory/. Note also
that the URL on most of web servers are case–sensitive. Don’t
forget the trailing slash at the end.
Starting with version 2.3.0, it is advisable to try leaving this blank. In
most cases phpMyAdmin automatically detects the proper setting. Users of
port forwarding will need to set $cfg['PmaAbsoluteUri']
(more info).
A good test is to browse a table, edit a row and save it. There should be
an error message if phpMyAdmin is having trouble auto–detecting the correct
value. If you get an error that this must be set or if the autodetect code
fails to detect your path, please post a bug report on our bug tracker so
we can improve the code.
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.
Sets the default behavior for JavaScript error reporting.
Whenever an error is detected in the JavaScript execution, an error report
may be sent to the phpMyAdmin team if the user agrees.
The default setting of 'ask' will ask the user everytime there is a new
error report. However you can set this parameter to 'always' to send error
reports without asking for confirmation or you can set it to 'never' to
never send error reports.
This directive is available both in the configuration file and in users
preferences. If the person in charge of a multi-user installation prefers
to disable this feature for all users, a value of 'never' should be
set, and the $cfg['UserprefsDisallow'] directive should
contain 'SendErrorReports' in one of its array values.
Setting this to true allows phpMyAdmin to be included inside a frame,
and is a potential security hole allowing cross-frame scripting attacks or
clickjacking.
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. In
libraries/config.default.php, there is only one section for server
definition, however you can put as many as you need in
config.inc.php, copy that block or needed parts (you don’t have to
define all settings, just those you need to change).
Note
The $cfg['Servers'] array starts with
$cfg[‘Servers’][1]. Do not use $cfg[‘Servers’][0]. If you want more
than one server, just copy following section (including $i
incrementation) serveral times. There is no need to define full server
array, just define values you need to change.
The port-number of your $i-th MySQL-server. Default is 3306 (leave
blank).
Note
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'].
The path to the socket to use. Leave blank for default. To determine
the correct socket, check your MySQL configuration or, using the
mysql command–line client, issue the status command. Among the
resulting information displayed will be the socket used.
What type connection to use with the MySQL server. Your options are
'socket' and '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.
Whether config or cookie or HTTP or signon 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. Username and password are stored in cookies
during the session and password is deleted when it ends. This can also
allow you to log in in arbitrary server if $cfg['AllowArbitraryServer'] enabled.
‘http’ authentication (was
called ‘advanced’ in previous versions and can be written also as
‘http’) ($auth_type = 'http';') as introduced in 1.3.0 allows you to log in as any
valid MySQL user via HTTP-Auth.
‘signon’ authentication mode ($auth_type = 'signon') as
introduced in 2.10.0 allows you to log in from prepared PHP session
data or using supplied PHP script. This is useful for implementing
single signon from another application. Sample way how to seed session
is in signon example: examples/signon.php. There is also
alternative example using OpenID - examples/openid.php and example
for scripts based solution - examples/signon-script.php. You need
to configure $cfg['Servers'][$i]['SignonSession'] or
$cfg['Servers'][$i]['SignonScript'] and
$cfg['Servers'][$i]['SignonURL'] to use this authentication
method.
When using auth_type = http, this field allows to define a custom
HTTP Basic Auth Realm which will be displayed to the user. If not
explicitly specified in your configuration, a string combined of
“phpMyAdmin ” and either $cfg['Servers'][$i]['verbose'] or
$cfg['Servers'][$i]['host'] will be used.
When using $cfg['Servers'][$i]['auth_type'] set to
‘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
HTTP or cookie authentication is used
and should be empty.
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.
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.
Regular expression for hiding some databases from unprivileged users.
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. For example, to hide all databases
starting with the letter “a”, use
$cfg['Servers'][$i]['hide_db']='^a';
and to hide both “db1” and “db2” use
$cfg['Servers'][$i]['hide_db']='^(db1|db2)$';
More information on regular expressions can be found in the PCRE
pattern syntax portion
of the PHP reference manual.
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.
The name of the database containing the phpMyAdmin configuration
storage.
See the phpMyAdmin configuration storage section in this document to see the benefits of
this feature, 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 phpMyAdmin configuration storage.
Since release 2.2.0 phpMyAdmin allows users to bookmark queries. This
can be useful for queries you often run. To allow the usage of this
functionality:
Since release 2.2.4 you can describe, in a special ‘relation’ table,
which column 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 column” when browsing the
master table, if you move the mouse to a column containing a foreign
key (use also the ‘table_info’ table); (see 6.7 How can I use the “display column” feature?)
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 columns.
Note
In the current version, master_db must be the same as foreign_db.
Those columns have been put in future development of the cross-db
relations.
Since release 2.3.0 you can describe, in a special ‘table_info’
table, which column 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:
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.
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 “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 columns ‘mimetype’,
‘transformation’, ‘transformation_options’.
to update your PRE-2.5.0 Column_comments Table use this: and
remember that the Variable in config.inc.php has been renamed from
$cfg['Servers'][$i]['column_comments'] to
$cfg['Servers'][$i]['column_info']
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 JavaScript is enabled in
your browser.
Since release 3.5.0 you can show recently used tables in the
navigation panel. It helps you to jump across table directly, without
the need to select the database, and then select the table. Using
$cfg['NumRecentTables'] you can configure the maximum number
of recent tables shown. When you select a table from the list, it will jump to
the page specified in $cfg['NavigationTreeDefaultTabTable'].
Without configuring the storage, you can still access the recently used tables,
but it will disappear after you logout.
To allow the usage of this functionality persistently:
Since release 3.5.0 phpMyAdmin can be configured to remember several
things (sorted column $cfg['RememberSorting'], column order,
and column visibility from a database table) for browsing tables. Without
configuring the storage, these features still can be used, but the values will
disappear after you logout.
To allow the usage of these functionality persistently:
Since release 4.1.0 you can create different user groups with menu items
attached to them. Users can be assigned to these groups and the logged in
user would only see menu items configured to the usergroup he is assigned to.
To do this it needs two tables “usergroups” (storing allowed menu items for each
user group) and “users” (storing users and their assignments to user groups).
Since release 3.3.x a tracking mechanism is available. It helps you to
track every SQL command which is
executed by phpMyAdmin. The mechanism supports logging of data
manipulation and data definition statements. After enabling it you can
create versions of tables.
The creation of a version has two effects:
phpMyAdmin saves a snapshot of the table, including structure and
indexes.
phpMyAdmin logs all commands which change the structure and/or data of
the table and links these commands with the version number.
Of course you can view the tracked changes. On the Tracking
page a complete report is available for every version. For the report you
can use filters, for example you can get a list of statements within a date
range. When you want to filter usernames you can enter * for all names or
you enter a list of names separated by ‘,’. In addition you can export the
(filtered) report to a file or to a temporary database.
Since release 3.4.x phpMyAdmin allows users to set most preferences by
themselves and store them in the database.
If you don’t allow for storing preferences in
$cfg['Servers'][$i]['pmadb'], users can still personalize
phpMyAdmin, but settings will be saved in browser’s local storage, or, it
is is unavailable, until the end of session.
Whether to allow logins without a password. The default value of
false for this parameter prevents unintended access to a MySQL
server with was left with an empty password for root or on which an
anonymous (blank) user is defined.
If your rule order is empty, then IP
authorization 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', authorization 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.
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 (please note that those containing
SERVER_ADDRESS might not be available on all webservers):
Having an empty rule list is equivalent to either using 'allow%fromall' if your rule order is set to 'deny,allow' or 'deny%fromall' if your rule order is set to 'allow,deny' or
'explicit'.
For the IP address matching
system, the following work:
Name of PHP script to be sourced and executed to obtain login
credentials. This is alternative approach to session based single
signon. The script needs to provide function
get_login_credentials which returns list of username and
password, accepting single parameter of existing username (can be
empty). See examples/signon-script.php for an example.
Name of session which will be used for signon authentication method.
You should use something different than phpMyAdmin, because this
is session which phpMyAdmin uses internally. Takes effect only if
$cfg['Servers'][$i]['SignonScript'] is not configured.
Enables caching of TABLESTATUS outputs for specific databases on
this server (in some cases TABLESTATUS can be very slow, so you
may want to cache it). APC is used (if the PHP extension is available,
if not, this setting is ignored silently). You have to provide
$cfg['Servers'][$i]['StatusCacheLifetime'].
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.
The url of the proxy to be used when phpmyadmin needs to access the outside
intenet such as when retrieving the latest version info or submitting error
reports. You need this if the server where phpMyAdmin is installed does not
have direct access to the internet.
The format is: “hostname:portnumber”
The username for authenticating with the proxy. By default, no
authentication is performed. If a username is supplied, Basic
Authentication will be performed. No other types of authentication
are currently supported.
The maximum number of table names to be displayed in the main panel’s
list (except on the Export page). This limit is also enforced in the
navigation panel when in Light mode.
The maximum number of characters when a SQL query is displayed. The
default limit of 1000 should be correct to avoid the display of tons of
hexadecimal codes that represent BLOBs, but some users have real
SQL queries that are longer than 1000 characters. Also, if a
query’s length exceeds this limit, this query is not saved in the history.
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.
Set the number of bytes a script is allowed to allocate. If set to
'-1', no limit is imposed.
This setting is used while importing/exporting dump files and at some other
places in phpMyAdmin so you definitely don’t want to put here a too low
value. It has no effect when PHP is running in safe mode.
You can also use any string as in php.ini, eg. ‘16M’. Ensure you
don’t omit the suffix (16 means 16 bytes!)
Defines whether to use a Javascript code editor for SQL query boxes.
CodeMirror provides syntax highlighting and line numbers. However,
middle-clicking for pasting the clipboard contents in some Linux
distributions (such as Ubuntu) is not supported by all browsers.
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 DROPDATABASEmydatabase will
be rejected. Quite practical for ISP ‘s with many customers.
Note
This limitation of SQL queries is not
as strict as when using MySQL privileges. This is due to nature of
SQL queries which might be quite
complicated. So this choice should be viewed as help to avoid accidental
dropping rather than strict privilege limitation.
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. There
is no maximum length for this secret.
Changed in version 3.1.0: Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
makes a bit weaker security as this generated secret is stored in
session and furthermore it makes impossible to recall user name from
cookie.
Define how long a login cookie is valid. Please note that php
configuration option session.gc_maxlifetime might limit session validity and if the session is lost,
the login cookie is also invalidated. So it is a good idea to set
session.gc_maxlifetime at least to the same value of
$cfg['LoginCookieValidity'].
Define how long login cookie should be stored in browser. Default 0
means that it will be kept for existing session. This is recommended
for not trusted environments.
If enabled (default), logout deletes cookies for all servers,
otherwise only for current one. Setting this to false makes it easy to
forget to log out from other server, when you are using more of them.
The string used to separate the parts of the database name when
showing them in a tree. Alternatively you can specify more strings in
an array and all of them will be used as a separator.
Defines a string to be used to nest table spaces. This means if you have
tables like first__second__third this will be shown as a three-level
hierarchy like: first > second > third. If set to false or empty, the
feature is disabled. NOTE: You should not use this separator at the
beginning or end of a table name or multiple times after another without
any other characters in between.
Defines the minimum number of items (tables, views, routines and
events) to display a JavaScript filter box above the list of items in
the navigation tree.
To disable the filter completely some high number can be used (e.g. 9999)
Defines whether or not to display space usage and statistics about
databases and tables. 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.
Defines whether to display detailed server information on main page.
You can additionally hide more information by using
$cfg['Servers'][$i]['verbose'].
Defines whether to display the PHP information and
Change password links and form for creating database or not 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.
Defines whether a user should be displayed a “Show all” button in browse
mode or not in all cases. By default it is shown only on small tables (less
than 500 rows) to avoid performance issues while getting too many rows.
Number of rows displayed when browsing a result set and no LIMIT
clause is used. If the result set contains more rows, “Previous” and
“Next” links will be shown. Possible values: 25,50,100,250,500.
Defines whether columns are displayed in ascending (ASC) order, in
descending (DESC) order or in a “smart” (SMART) order - I.E.
descending order for columns of type TIME, DATE, DATETIME and
TIMESTAMP, ascending order else- by default.
Defines whether or not MySQL functions fields should be initially
displayed in edit/insert mode. Since version 2.10, the user can toggle
this setting from the interface.
If there are fewer items than this in the set of foreign keys, then a
drop-down box of foreign keys is presented, in the style described by
the $cfg['ForeignKeyDropdownOrder'] setting.
For the foreign key drop-down fields, there are several methods of
display, offering both the key and value data. The contents of the
array should be one or both of the following strings: content-id,
id-content.
Defines whether to allow on the fly compression for GZip/BZip2
compressed exports. This doesn’t affect smaller dumps and allows users
to create larger dumps that won’t otherwise fit in memory due to php
memory limit. Produced files contain more GZip/BZip2 headers, but all
normal programs handle this correctly.
In this array are defined default parameters for export, names of
items are similar to texts seen on export page, so you can easily
identify what they mean.
In this array are defined default parameters for import, names of
items are similar to texts seen on import page, so you can easily
identify what they mean.
If set to icons, 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 text, will only show text.
How many columns will be utilized to display the tables on the database
property view? When setting this to a value larger than 1, the type of the
database will be omitted for more display space.
Defines the default language to use, if not browser-defined or user-
defined. The corresponding language file needs to be in
locale/code/LC_MESSAGES/phpmyadmin.mo.
Defines the default connection collation to use, if not user-defined.
See the MySQL documentation for list of possible values. This setting is
ignored when connected to Drizzle server.
Limit list of available languages to those matching the given regular
expression. For example if you want only Czech and English, you should
set filter to '^(cs|en)'.
You can select here which functions will be used for character set
conversion. Possible values are:
auto - automatically use available one (first is tested iconv, then
recode)
iconv - use iconv or libiconv functions
recode - use recode_string function
mb - use mbstring extension
none - disable encoding conversion
Enabled charset conversion activates a pull-down menu in the Export
and Import pages, to choose the character set when exporting a file.
The default value in this menu comes from
$cfg['Export']['charset'] and $cfg['Import']['charset'].
Specify some parameters for iconv used in charset conversion. See
iconv documentation for details. By default
//TRANSLIT is used, so that invalid characters will be
transliterated.
Available character sets for MySQL conversion. You can add your own
(any of supported by recode/iconv) or remove these which you don’t
use. Character sets will be shown in same order as here listed, so if
you frequently use some of these move them to the top.
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 when having enabled
buffering.
Lists proxies and HTTP headers which are trusted for
$cfg['Servers'][$i]['AllowDeny']['order']. This list is by
default empty, you need to fill in some trusted proxy servers if you
want to use rules for IP addresses behind proxy.
The following example specifies that phpMyAdmin should trust a
HTTP_X_FORWARDED_FOR (X-Forwarded-For) header coming from the proxy
1.2.3.4:
We normally check the permissions on the configuration file to ensure
it’s not world writable. However, phpMyAdmin could be installed on a
NTFS filesystem mounted on a non-Windows server, in which case the
permissions seems wrong but in fact cannot be detected. In this case a
sysadmin would set this parameter to false.
Limit for length of URL in links. When length would be above this
limit, it is replaced by form with button. This is required as some web
servers (IIS) have problems with long URL .
Additional string to include in allowed script and image sources in Content
Security Policy header.
This can be useful when you want to include some external javascript files
in config.footer.inc.php or config.header.inc.php, which
would be normally not allowed by Content Security Policy.
To allow some sites, just list them within the string:
In the database Structure page, it’s possible to mark some tables then
choose an operation like optimizing for many tables. This can slow
down a server; therefore, setting this to true prevents this kind
of multiple maintenance operation.
The colors (HTML) uses for the pointer and the marker in browse mode.
The former feature highlights the row over which your mouse is passing
and the latter lets you visually mark/unmark rows by clicking on the
corresponding checkbox. Highlighting / marking a column is done by
hovering over / clicking the column’s header (outside of the text).
See themes/themename/layout.inc.php.
Defines the place where table row links (Edit, Copy, Delete) would be
put when tables contents are displayed (you may have them displayed at
the left side, right side, both sides or nowhere). “left” and “right”
are parsed as “top” and “bottom” with vertical display mode.
There are 3 display modes: horizontal, horizontalflipped and vertical.
Define which one is displayed by default. The first mode displays each
row on a horizontal line, the second rotates the headers by 90
degrees, so you can use descriptive headers even though columns only
contain small values and still print them out. The vertical mode sorts
each row on a vertical lineup.
The HeaderFlipType can be set to ‘auto’, ‘css’ or ‘fake’. When using
‘css’ the rotation of the header for horizontalflipped is done via
CSS. The CSS transformation currently works only in Internet
Explorer.If set to ‘fake’ PHP does the transformation for you, but of
course this does not look as good as CSS. The ‘auto’ option enables
CSS transformation when browser supports it and use PHP based one
otherwise.
By setting the corresponding variable to true you can enable the
display of column comments in Browse or Property display. In browse
mode, the comments are shown inside the header. In property mode,
comments are displayed using a CSS-formatted dashed-line below the
name of the column. The comment is shown as a tool-tip for that
column.
Defines which type of editing controls should be used for CHAR and
VARCHAR columns. Applies to data editing and also to the default values
in structure editing. Possible values are:
input - this allows to limit size of text to size of columns in MySQL,
but has problems with newlines in columns
textarea - no problems with newlines in columns, but also no length
limitations
Number of columns and rows for the textareas. This value will be
emphasized (*2) for SQL query
textareas and (*1.25) for SQL
textareas inside the query window.
The Char* values are used for CHAR
and VARCHAR editing (if configured via $cfg['CharEditing']).
The name of the directory where SQL files have been uploaded by
other means than phpMyAdmin (for example, ftp). Those files are available
under a drop-down box when you click the database or table name, then the
Import tab.
If
you want different directory for each user, %u will be replaced with
username.
Please note that the file names must have the suffix ”.sql”
(or ”.sql.bz2” or ”.sql.gz” if support for compressed formats is
enabled).
This feature is useful when your file is too big to be
uploaded via HTTP, or when file
uploads are disabled in PHP.
If the directory where phpMyAdmin is installed is
subject to an open_basedir restriction, you need to create a
temporary directory in some directory accessible by the web server.
However for security reasons, this directory should be outside the
tree published by webserver. If you cannot avoid having this directory
published by webserver, place at least an empty index.html file
there, so that directory listing is not possible.
This directory should have as strict permissions as possible as the only
user required to access this directory is the one who runs the webserver.
If you have root privileges, simply make this user owner of this directory
and make it accessible only by it:
chown www-data:www-data tmp
chmod 700 tmp
If you cannot change owner of the directory, you can achieve a similar
setup using ACL:
If neither of above works for you, you can still make the directory
chmod 777, but it might impose risk of other users on system
reading and writing data in this directory.
All those variables affect the query window feature. A SQL link or
icon is always displayed in the navigation panel. If JavaScript is enabled
in your browser, a click on this opens a distinct query window, which is a
direct interface to enter SQL queries. Otherwise, the right panel
changes to display a query box.
The size of this query window can be customized with
$cfg['QueryWindowWidth'] and
$cfg['QueryWindowHeight'] - both integers for the size in
pixels. Note that normally, those parameters will be modified in
layout.inc.php` for the theme you are using.
If $cfg['EditInWindow'] is set to true, a click on [Edit]
from the results page (in the Showing Rows section) opens the
query window and puts the current query inside it. If set to false,
clicking on the link puts the SQL query
in the right panel’s query box.
If $cfg['QueryHistoryDB'] is set to true, all your
Queries are logged to a table, which has to be created by you (see
$cfg['Servers'][$i]['history']). If set to false, all your
queries will be appended to the form, but only as long as your window is
opened they remain saved.
When using the JavaScript based query window, it will always get updated
when you click on a new table/db to browse and will focus if you click on
Edit SQL after using a query. You can suppress updating the
query window by checking the box Do not overwrite this query
from outside the window below the query textarea. Then you can browse
tables/databases in the background without losing the contents of the
textarea, so this is especially useful when composing a query with tables
you first have to look in. The checkbox will get automatically checked
whenever you change the contents of the textarea. Please uncheck the button
whenever you definitely want the query window to get updated even though
you have made alterations.
The query window also has a custom tabbed look to group the features.
Using the variable $cfg['QueryWindowDefTab'] you can
specify the default tab to be used when opening the query window. It can be
set to either sql, files, history or full.
For InnoDB tables, determines for how large tables phpMyAdmin should
get the exact row count using SELECTCOUNT. If the approximate row
count as returned by SHOWTABLESTATUS is smaller than this value,
SELECTCOUNT will be used, otherwise the approximate count will be
used.
For VIEWs, since obtaining the exact count could have an impact on
performance, this value is the maximum to be displayed, using a
SELECTCOUNT...LIMIT. Setting this to 0 bypasses any row
counting.
Sorts database and table names according to natural order (for
example, t1, t2, t10). Currently implemented in the navigation panel
and in Database view, for the table list.
If set to 'closed', the visual sliders are initially in a closed
state. A value of 'open' does the reverse. To completely disable
all visual sliders, use 'disabled'.
Contains names of configuration options (keys in $cfg array) that
users can’t set through user preferences. For possible values, refer
to libraries/config/user_preferences.forms.php.
Functions selected by default when inserting/changing row, Functions
are defined for meta types as (FUNC_NUMBER, FUNC_DATE, FUNC_CHAR,
FUNC_SPATIAL, FUNC_UUID) and for first_timestamp, which is used
for first timestamp column in table.