1 .. index:: config.inc.php
8 Almost all configurable data is placed in :file:`config.inc.php`. If this file
9 does not exist, please refer to the :ref:`setup` section to create one. This
10 file only needs to contain the parameters you want to change from their
11 corresponding default value in :file:`libraries/config.default.php`.
13 If a directive is missing from your file, you can just add another line with
14 the file. This file is for over-writing the defaults; if you wish to use the
15 default value there's no need to add a line here.
17 The parameters which relate to design (like colors) are placed in
18 :file:`themes/themename/layout.inc.php`. You might also want to create
19 :file:`config.footer.inc.php` and :file:`config.header.inc.php` files to add
20 your site specific code to be included on start and end of each page.
24 Some distributions (eg. Debian or Ubuntu) store :file:`config.inc.php` in
25 ``/etc/phpmyadmin`` instead of within phpMyAdmin sources.
29 :term:`Mac` users should note that if you are on a version before
30 :term:`Mac OS X`, PHP does not seem to
31 like :term:`Mac` end of lines character (``\r``). So
32 ensure you choose the option that allows to use the \*nix end of line
33 character (``\n``) in your text editor before saving a script you have
39 .. config:option:: $cfg['PmaAbsoluteUri']
44 Sets here the complete :term:`URL` (with full path) to your phpMyAdmin
45 installation's directory. E.g.
46 ``http://www.example.net/path_to_your_phpMyAdmin_directory/``. Note also
47 that the :term:`URL` on most of web servers are case–sensitive. Don’t
48 forget the trailing slash at the end.
50 Starting with version 2.3.0, it is advisable to try leaving this blank. In
51 most cases phpMyAdmin automatically detects the proper setting. Users of
52 port forwarding will need to set :config:option:`$cfg['PmaAbsoluteUri']`
53 (`more info <https://sourceforge.net/p/phpmyadmin/support-requests/795/>`_).
55 A good test is to browse a table, edit a row and save it. There should be
56 an error message if phpMyAdmin is having trouble auto–detecting the correct
57 value. If you get an error that this must be set or if the autodetect code
58 fails to detect your path, please post a bug report on our bug tracker so
59 we can improve the code.
61 .. seealso:: :ref:`faq1_40`
63 .. config:option:: $cfg['PmaNoRelation_DisableWarning']
68 Starting with version 2.3.0 phpMyAdmin offers a lot of features to
69 work with master / foreign – tables (see :config:option:`$cfg['Servers'][$i]['pmadb']`).
71 If you tried to set this
72 up and it does not work for you, have a look on the :guilabel:`Structure` page
73 of one database where you would like to use it. You will find a link
74 that will analyze why those features have been disabled.
76 If you do not want to use those features set this variable to ``true`` to
77 stop this message from appearing.
79 .. config:option:: $cfg['SuhosinDisableWarning']
84 A warning is displayed on the main page if Suhosin is detected.
86 You can set this parameter to ``true`` to stop this message from appearing.
88 .. config:option:: $cfg['McryptDisableWarning']
93 Disable the default warning that is displayed if mcrypt is missing for
94 cookie authentication.
96 You can set this parameter to ``true`` to stop this message from appearing.
98 .. config:option:: $cfg['ServerLibraryDifference_DisableWarning']
103 A warning is displayed on the main page if there is a difference
104 between the MySQL library and server version.
106 You can set this parameter to ``true`` to stop this message from appearing.
108 .. config:option:: $cfg['ReservedWordDisableWarning']
113 This warning is displayed on the Structure page of a table if one or more
114 column names match with words which are MySQL reserved.
116 If you want to turn off this warning, you can set it to ``true`` and
117 warning will no longer be displayed.
119 .. config:option:: $cfg['TranslationWarningThreshold']
124 Show warning about incomplete translations on certain threshold.
126 .. config:option:: $cfg['SendErrorReports']
131 Sets the default behavior for JavaScript error reporting.
133 Whenever an error is detected in the JavaScript execution, an error report
134 may be sent to the phpMyAdmin team if the user agrees.
136 The default setting of ``'ask'`` will ask the user everytime there is a new
137 error report. However you can set this parameter to ``'always'`` to send error
138 reports without asking for confirmation or you can set it to ``'never'`` to
139 never send error reports.
141 This directive is available both in the configuration file and in users
142 preferences. If the person in charge of a multi-user installation prefers
143 to disable this feature for all users, a value of ``'never'`` should be
144 set, and the :config:option:`$cfg['UserprefsDisallow']` directive should
145 contain ``'SendErrorReports'`` in one of its array values.
147 .. config:option:: $cfg['AllowThirdPartyFraming']
152 Setting this to ``true`` allows phpMyAdmin to be included inside a frame,
153 and is a potential security hole allowing cross-frame scripting attacks or
156 Server connection settings
157 --------------------------
159 .. config:option:: $cfg['Servers']
162 :default: one server array with settings listed bellow
164 Since version 1.4.2, phpMyAdmin supports the administration of multiple
165 MySQL servers. Therefore, a :config:option:`$cfg['Servers']`-array has been
166 added which contains the login information for the different servers. The
167 first :config:option:`$cfg['Servers'][$i]['host']` contains the hostname of
168 the first server, the second :config:option:`$cfg['Servers'][$i]['host']`
169 the hostname of the second server, etc. In
170 :file:`libraries/config.default.php`, there is only one section for server
171 definition, however you can put as many as you need in
172 :file:`config.inc.php`, copy that block or needed parts (you don't have to
173 define all settings, just those you need to change).
177 The :config:option:`$cfg['Servers']` array starts with
178 $cfg['Servers'][1]. Do not use $cfg['Servers'][0]. If you want more
179 than one server, just copy following section (including $i
180 incrementation) serveral times. There is no need to define full server
181 array, just define values you need to change.
184 .. config:option:: $cfg['Servers'][$i]['host']
187 :default: ``'localhost'``
189 The hostname or :term:`IP` address of your $i-th MySQL-server. E.g.
194 * hostname, e.g., ``'localhost'`` or ``'mydb.example.org'``
195 * IP address, e.g., ``'127.0.0.1'`` or ``'192.168.10.1'``
196 * dot - ``'.'``, i.e., use named pipes on windows systems
197 * empty - ``''``, disables this server
201 phpMyAdmin supports connecting to MySQL servers reachable via IPv6 only.
202 To connect to an IPv6 MySQL server, enter its IPv6 address in this field.
204 .. config:option:: $cfg['Servers'][$i]['port']
209 The port-number of your $i-th MySQL-server. Default is 3306 (leave
214 If you use ``localhost`` as the hostname, MySQL ignores this port number
215 and connects with the socket, so if you want to connect to a port
216 different from the default port, use ``127.0.0.1`` or the real hostname
217 in :config:option:`$cfg['Servers'][$i]['host']`.
219 .. config:option:: $cfg['Servers'][$i]['socket']
224 The path to the socket to use. Leave blank for default. To determine
225 the correct socket, check your MySQL configuration or, using the
226 :command:`mysql` command–line client, issue the ``status`` command. Among the
227 resulting information displayed will be the socket used.
229 .. config:option:: $cfg['Servers'][$i]['ssl']
234 Whether to enable SSL for the connection between phpMyAdmin and the MySQL server.
236 When using the ``'mysql'`` extension,
237 none of the remaining ``'ssl...'`` configuration options apply.
239 We strongly recommend the ``'mysqli'`` extension when using this option.
241 .. config:option:: $cfg['Servers'][$i]['ssl_key']
246 Path to the key file when using SSL for connecting to the MySQL server.
252 $cfg['Servers'][$i]['ssl_key'] = '/etc/mysql/server-key.pem';
254 .. config:option:: $cfg['Servers'][$i]['ssl_cert']
259 Path to the cert file when using SSL for connecting to the MySQL server.
261 .. config:option:: $cfg['Servers'][$i]['ssl_ca']
266 Path to the CA file when using SSL for connecting to the MySQL server.
268 .. config:option:: $cfg['Servers'][$i]['ssl_ca_path']
273 Directory containing trusted SSL CA certificates in PEM format.
275 .. config:option:: $cfg['Servers'][$i]['ssl_ciphers']
280 List of allowable ciphers for SSL connections to the MySQL server.
282 .. config:option:: $cfg['Servers'][$i]['connect_type']
287 What type connection to use with the MySQL server. Your options are
288 ``'socket'`` and ``'tcp'``. It defaults to tcp as that is nearly guaranteed
289 to be available on all MySQL servers, while sockets are not supported on
290 some platforms. To use the socket mode, your MySQL server must be on the
291 same machine as the Web server.
293 .. config:option:: $cfg['Servers'][$i]['compress']
298 Whether to use a compressed protocol for the MySQL server connection
299 or not (experimental).
302 .. config:option:: $cfg['Servers'][$i]['controlhost']
307 Permits to use an alternate host to hold the configuration storage
311 .. config:option:: $cfg['Servers'][$i]['controlport']
316 Permits to use an alternate port to connect to the host that
317 holds the configuration storage.
320 .. config:option:: $cfg['Servers'][$i]['controluser']
325 .. config:option:: $cfg['Servers'][$i]['controlpass']
330 This special account is used for 2 distinct purposes: to make possible all
331 relational features (see :config:option:`$cfg['Servers'][$i]['pmadb']`).
333 .. versionchanged:: 2.2.5
334 those were called ``stduser`` and ``stdpass``
336 .. seealso:: :ref:`setup`, :ref:`authentication_modes`, :ref:`linked-tables`
338 .. config:option:: $cfg['Servers'][$i]['auth_type']
341 :default: ``'cookie'``
343 Whether config or cookie or :term:`HTTP` or signon authentication should be
344 used for this server.
346 * 'config' authentication (``$auth_type = 'config'``) is the plain old
347 way: username and password are stored in :file:`config.inc.php`.
348 * 'cookie' authentication mode (``$auth_type = 'cookie'``) as
349 introduced in 2.2.3 allows you to log in as any valid MySQL user with
350 the help of cookies. Username and password are stored in cookies
351 during the session and password is deleted when it ends. This can also
352 allow you to log in in arbitrary server if :config:option:`$cfg['AllowArbitraryServer']` enabled.
353 * 'http' authentication (was
354 called 'advanced' in previous versions and can be written also as
355 'http') (``$auth_type = 'http';'``) as introduced in 1.3.0 allows you to log in as any
356 valid MySQL user via HTTP-Auth.
357 * 'signon' authentication mode (``$auth_type = 'signon'``) as
358 introduced in 2.10.0 allows you to log in from prepared PHP session
359 data or using supplied PHP script. This is useful for implementing
360 single signon from another application. Sample way how to seed session
361 is in signon example: :file:`examples/signon.php`. There is also
362 alternative example using OpenID - :file:`examples/openid.php` and example
363 for scripts based solution - :file:`examples/signon-script.php`. You need
364 to configure :config:option:`$cfg['Servers'][$i]['SignonSession']` or
365 :config:option:`$cfg['Servers'][$i]['SignonScript']` and
366 :config:option:`$cfg['Servers'][$i]['SignonURL']` to use this authentication
369 .. seealso:: :ref:`authentication_modes`
371 .. _servers_auth_http_realm:
372 .. config:option:: $cfg['Servers'][$i]['auth_http_realm']
377 When using auth\_type = ``http``, this field allows to define a custom
378 :term:`HTTP` Basic Auth Realm which will be displayed to the user. If not
379 explicitly specified in your configuration, a string combined of
380 "phpMyAdmin " and either :config:option:`$cfg['Servers'][$i]['verbose']` or
381 :config:option:`$cfg['Servers'][$i]['host']` will be used.
383 .. _servers_auth_swekey_config:
384 .. config:option:: $cfg['Servers'][$i]['auth_swekey_config']
389 The name of the file containing :ref:`swekey` ids and login names for hardware
390 authentication. Leave empty to deactivate this feature.
393 .. config:option:: $cfg['Servers'][$i]['user']
398 .. config:option:: $cfg['Servers'][$i]['password']
403 When using :config:option:`$cfg['Servers'][$i]['auth_type']` set to
404 'config', this is the user/password-pair which phpMyAdmin will use to
405 connect to the MySQL server. This user/password pair is not needed when
406 :term:`HTTP` or cookie authentication is used
409 .. _servers_nopassword:
410 .. config:option:: $cfg['Servers'][$i]['nopassword']
415 Allow attempt to log in without password when a login with password
416 fails. This can be used together with http authentication, when
417 authentication is done some other way and phpMyAdmin gets user name
418 from auth and uses empty password for connecting to MySQL. Password
419 login is still tried first, but as fallback, no password method is
423 .. config:option:: $cfg['Servers'][$i]['only_db']
425 :type: string or array
428 If set to a (an array of) database name(s), only this (these)
429 database(s) will be shown to the user. Since phpMyAdmin 2.2.1,
430 this/these database(s) name(s) may contain MySQL wildcards characters
431 ("\_" and "%"): if you want to use literal instances of these
432 characters, escape them (I.E. use ``'my\_db'`` and not ``'my_db'``).
434 This setting is an efficient way to lower the server load since the
435 latter does not need to send MySQL requests to build the available
436 database list. But **it does not replace the privileges rules of the
437 MySQL database server**. If set, it just means only these databases
438 will be displayed but **not that all other databases can't be used.**
440 An example of using more that one database:
444 $cfg['Servers'][$i]['only_db'] = array('db1', 'db2');
446 .. versionchanged:: 4.0.0
447 Previous versions permitted to specify the display order of
448 the database names via this directive.
450 .. config:option:: $cfg['Servers'][$i]['hide_db']
455 Regular expression for hiding some databases from unprivileged users.
456 This only hides them from listing, but a user is still able to access
457 them (using, for example, the SQL query area). To limit access, use
458 the MySQL privilege system. For example, to hide all databases
459 starting with the letter "a", use
463 $cfg['Servers'][$i]['hide_db'] = '^a';
465 and to hide both "db1" and "db2" use
469 $cfg['Servers'][$i]['hide_db'] = '^(db1|db2)$';
471 More information on regular expressions can be found in the `PCRE
473 <http://php.net/manual/en/reference.pcre.pattern.syntax.php>`_ portion
474 of the PHP reference manual.
476 .. config:option:: $cfg['Servers'][$i]['verbose']
481 Only useful when using phpMyAdmin with multiple server entries. If
482 set, this string will be displayed instead of the hostname in the
483 pull-down menu on the main page. This can be useful if you want to
484 show only certain databases on your system, for example. For HTTP
485 auth, all non-US-ASCII characters will be stripped.
487 .. config:option:: $cfg['Servers'][$i]['pmadb']
492 The name of the database containing the phpMyAdmin configuration
495 See the :ref:`linked-tables` section in this document to see the benefits of
496 this feature, and for a quick way of creating this database and the needed
499 If you are the only user of this phpMyAdmin installation, you can use your
500 current database to store those special tables; in this case, just put your
501 current database name in :config:option:`$cfg['Servers'][$i]['pmadb']`. For a
502 multi-user installation, set this parameter to the name of your central
503 database containing the phpMyAdmin configuration storage.
506 .. config:option:: $cfg['Servers'][$i]['bookmarktable']
511 Since release 2.2.0 phpMyAdmin allows users to bookmark queries. This
512 can be useful for queries you often run. To allow the usage of this
515 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
516 * enter the table name in :config:option:`$cfg['Servers'][$i]['bookmarktable']`
520 .. config:option:: $cfg['Servers'][$i]['relation']
525 Since release 2.2.4 you can describe, in a special 'relation' table,
526 which column is a key in another table (a foreign key). phpMyAdmin
527 currently uses this to:
529 * make clickable, when you browse the master table, the data values that
530 point to the foreign table;
531 * display in an optional tool-tip the "display column" when browsing the
532 master table, if you move the mouse to a column containing a foreign
533 key (use also the 'table\_info' table); (see :ref:`faqdisplay`)
534 * in edit/insert mode, display a drop-down list of possible foreign keys
535 (key value and "display column" are shown) (see :ref:`faq6_21`)
536 * display links on the table properties page, to check referential
537 integrity (display missing foreign keys) for each described key;
538 * in query-by-example, create automatic joins (see :ref:`faq6_6`)
539 * enable you to get a :term:`PDF` schema of
540 your database (also uses the table\_coords table).
542 The keys can be numeric or character.
544 To allow the usage of this functionality:
546 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
547 * put the relation table name in :config:option:`$cfg['Servers'][$i]['relation']`
548 * now as normal user open phpMyAdmin and for each one of your tables
549 where you want to use this feature, click :guilabel:`Structure/Relation view/`
550 and choose foreign columns.
554 In the current version, ``master_db`` must be the same as ``foreign_db``.
555 Those columns have been put in future development of the cross-db
559 .. config:option:: $cfg['Servers'][$i]['table_info']
564 Since release 2.3.0 you can describe, in a special 'table\_info'
565 table, which column is to be displayed as a tool-tip when moving the
566 cursor over the corresponding key. This configuration variable will
567 hold the name of this special table. To allow the usage of this
570 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
571 * put the table name in :config:option:`$cfg['Servers'][$i]['table\_info']` (e.g.
573 * then for each table where you want to use this feature, click
574 "Structure/Relation view/Choose column to display" to choose the
577 .. seealso:: :ref:`faqdisplay`
580 .. config:option:: $cfg['Servers'][$i]['table_coords']
585 .. config:option:: $cfg['Servers'][$i]['pdf_pages']
590 Since release 2.3.0 you can have phpMyAdmin create :term:`PDF` pages
591 showing the relations between your tables. To do this it needs two tables
592 "pdf\_pages" (storing information about the available :term:`PDF` pages)
593 and "table\_coords" (storing coordinates where each table will be placed on
594 a :term:`PDF` schema output). You must be using the "relation" feature.
596 To allow the usage of this functionality:
598 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
599 * put the correct table names in
600 :config:option:`$cfg['Servers'][$i]['table\_coords']` and
601 :config:option:`$cfg['Servers'][$i]['pdf\_pages']`
603 .. seealso:: :ref:`faqpdf`.
606 .. config:option:: $cfg['Servers'][$i]['column_info']
611 This part requires a content update! Since release 2.3.0 you can
612 store comments to describe each column for each table. These will then
613 be shown on the "printview".
615 Starting with release 2.5.0, comments are consequently used on the table
616 property pages and table browse view, showing up as tool-tips above the
617 column name (properties page) or embedded within the header of table in
618 browse view. They can also be shown in a table dump. Please see the
619 relevant configuration directives later on.
621 Also new in release 2.5.0 is a MIME- transformation system which is also
622 based on the following table structure. See :ref:`transformations` for
623 further information. To use the MIME- transformation system, your
624 column\_info table has to have the three new columns 'mimetype',
625 'transformation', 'transformation\_options'.
628 To allow the usage of this functionality:
630 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
631 * put the table name in :config:option:`$cfg['Servers'][$i]['column\_info']` (e.g.
632 ``pma__column_info``)
633 * to update your PRE-2.5.0 Column\_comments Table use this: and
634 remember that the Variable in :file:`config.inc.php` has been renamed from
635 :config:option:`$cfg['Servers'][$i]['column\_comments']` to
636 :config:option:`$cfg['Servers'][$i]['column\_info']`
638 .. code-block:: mysql
640 ALTER TABLE `pma__column_comments`
641 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
642 ADD `transformation` VARCHAR( 255 ) NOT NULL,
643 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
646 .. config:option:: $cfg['Servers'][$i]['history']
651 Since release 2.5.0 you can store your :term:`SQL` history, which means all
652 queries you entered manually into the phpMyAdmin interface. If you don't
653 want to use a table-based history, you can use the JavaScript-based
656 Using that, all your history items are deleted when closing the window.
657 Using :config:option:`$cfg['QueryHistoryMax']` you can specify an amount of
658 history items you want to have on hold. On every login, this list gets cut
659 to the maximum amount.
661 The query history is only available if JavaScript is enabled in
664 To allow the usage of this functionality:
666 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
667 * put the table name in :config:option:`$cfg['Servers'][$i]['history']` (e.g.
671 .. config:option:: $cfg['Servers'][$i]['recent']
676 Since release 3.5.0 you can show recently used tables in the
677 navigation panel. It helps you to jump across table directly, without
678 the need to select the database, and then select the table. Using
679 :config:option:`$cfg['NumRecentTables']` you can configure the maximum number
680 of recent tables shown. When you select a table from the list, it will jump to
681 the page specified in :config:option:`$cfg['NavigationTreeDefaultTabTable']`.
684 Without configuring the storage, you can still access the recently used tables,
685 but it will disappear after you logout.
687 To allow the usage of this functionality persistently:
689 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
690 * put the table name in :config:option:`$cfg['Servers'][$i]['recent']` (e.g.
694 .. config:option:: $cfg['Servers'][$i]['table_uiprefs']
699 Since release 3.5.0 phpMyAdmin can be configured to remember several
700 things (sorted column :config:option:`$cfg['RememberSorting']`, column order,
701 and column visibility from a database table) for browsing tables. Without
702 configuring the storage, these features still can be used, but the values will
703 disappear after you logout.
705 To allow the usage of these functionality persistently:
707 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
708 * put the table name in :config:option:`$cfg['Servers'][$i]['table\_uiprefs']` (e.g.
709 ``pma__table_uiprefs``)
711 .. _configurablemenus:
712 .. config:option:: $cfg['Servers'][$i]['users']
717 .. config:option:: $cfg['Servers'][$i]['usergroups']
722 Since release 4.1.0 you can create different user groups with menu items
723 attached to them. Users can be assigned to these groups and the logged in
724 user would only see menu items configured to the usergroup he is assigned to.
725 To do this it needs two tables "usergroups" (storing allowed menu items for each
726 user group) and "users" (storing users and their assignments to user groups).
728 To allow the usage of this functionality:
730 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
731 * put the correct table names in
732 :config:option:`$cfg['Servers'][$i]['users']` (e.g. ``pma__users``) and
733 :config:option:`$cfg['Servers'][$i]['usergroups']` (e.g. ``pma__usergroups``)
735 .. _navigationhiding:
736 .. config:option:: $cfg['Servers'][$i]['navigationhiding']
741 Since release 4.1.0 you can hide/show items in the navigation tree.
743 To allow the usage of this functionality:
745 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
746 * put the table name in :config:option:`$cfg['Servers'][$i]['navigationhiding']` (e.g.
747 ``pma__navigationhiding``)
750 .. config:option:: $cfg['Servers'][$i]['tracking']
755 Since release 3.3.x a tracking mechanism is available. It helps you to
756 track every :term:`SQL` command which is
757 executed by phpMyAdmin. The mechanism supports logging of data
758 manipulation and data definition statements. After enabling it you can
759 create versions of tables.
761 The creation of a version has two effects:
763 * phpMyAdmin saves a snapshot of the table, including structure and
765 * phpMyAdmin logs all commands which change the structure and/or data of
766 the table and links these commands with the version number.
768 Of course you can view the tracked changes. On the :guilabel:`Tracking`
769 page a complete report is available for every version. For the report you
770 can use filters, for example you can get a list of statements within a date
771 range. When you want to filter usernames you can enter \* for all names or
772 you enter a list of names separated by ','. In addition you can export the
773 (filtered) report to a file or to a temporary database.
775 To allow the usage of this functionality:
777 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
778 * put the table name in :config:option:`$cfg['Servers'][$i]['tracking']` (e.g.
783 .. config:option:: $cfg['Servers'][$i]['tracking_version_auto_create']
788 Whether the tracking mechanism creates versions for tables and views
791 If this is set to true and you create a table or view with
796 and no version exists for it, the mechanism will create a version for
800 .. config:option:: $cfg['Servers'][$i]['tracking_default_statements']
803 :default: ``'CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,CREATE INDEX,DROP INDEX,INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,CREATE VIEW,ALTER VIEW,DROP VIEW,CREATE DATABASE,ALTER DATABASE,DROP DATABASE'``
805 Defines the list of statements the auto-creation uses for new
809 .. config:option:: $cfg['Servers'][$i]['tracking_add_drop_view']
814 Whether a DROP VIEW IF EXISTS statement will be added as first line to
815 the log when creating a view.
818 .. config:option:: $cfg['Servers'][$i]['tracking_add_drop_table']
823 Whether a DROP TABLE IF EXISTS statement will be added as first line
824 to the log when creating a table.
827 .. config:option:: $cfg['Servers'][$i]['tracking_add_drop_database']
832 Whether a DROP DATABASE IF EXISTS statement will be added as first
833 line to the log when creating a database.
836 .. config:option:: $cfg['Servers'][$i]['userconfig']
841 Since release 3.4.x phpMyAdmin allows users to set most preferences by
842 themselves and store them in the database.
844 If you don't allow for storing preferences in
845 :config:option:`$cfg['Servers'][$i]['pmadb']`, users can still personalize
846 phpMyAdmin, but settings will be saved in browser's local storage, or, it
847 is is unavailable, until the end of session.
849 To allow the usage of this functionality:
851 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
852 * put the table name in :config:option:`$cfg['Servers'][$i]['userconfig']`
857 .. config:option:: $cfg['Servers'][$i]['designer_coords']
862 Since release 2.10.0 a Designer interface is available; it permits to
863 visually manage the relations.
865 To allow the usage of this functionality:
867 * set up :config:option:`$cfg['Servers'][$i]['pmadb']` and the phpMyAdmin configuration storage
868 * put the table name in :config:option:`$cfg['Servers'][$i]['designer\_coords']`
869 (e.g. ``pma__designer_coords``)
873 .. config:option:: $cfg['Servers'][$i]['MaxTableUiprefs']
878 Maximum number of rows saved in
879 :config:option:`$cfg['Servers'][$i]['table_uiprefs']` table.
881 When tables are dropped or renamed,
882 :config:option:`$cfg['Servers'][$i]['table_uiprefs']` may contain invalid data
883 (referring to tables which no longer exist). We only keep this number of newest
884 rows in :config:option:`$cfg['Servers'][$i]['table_uiprefs']` and automatically
887 .. config:option:: $cfg['Servers'][$i]['AllowRoot']
892 Whether to allow root access. This is just a shortcut for the
893 :config:option:`$cfg['Servers'][$i]['AllowDeny']['rules']` below.
895 .. config:option:: $cfg['Servers'][$i]['AllowNoPassword']
900 Whether to allow logins without a password. The default value of
901 ``false`` for this parameter prevents unintended access to a MySQL
902 server with was left with an empty password for root or on which an
903 anonymous (blank) user is defined.
905 .. _servers_allowdeny_order:
906 .. config:option:: $cfg['Servers'][$i]['AllowDeny']['order']
911 If your rule order is empty, then :term:`IP`
912 authorization is disabled.
914 If your rule order is set to
915 ``'deny,allow'`` then the system applies all deny rules followed by
916 allow rules. Access is allowed by default. Any client which does not
917 match a Deny command or does match an Allow command will be allowed
918 access to the server.
920 If your rule order is set to ``'allow,deny'``
921 then the system applies all allow rules followed by deny rules. Access
922 is denied by default. Any client which does not match an Allow
923 directive or does match a Deny directive will be denied access to the
926 If your rule order is set to ``'explicit'``, authorization is
927 performed in a similar fashion to rule order 'deny,allow', with the
928 added restriction that your host/username combination **must** be
929 listed in the *allow* rules, and not listed in the *deny* rules. This
930 is the **most** secure means of using Allow/Deny rules, and was
931 available in Apache by specifying allow and deny rules without setting
934 Please also see :config:option:`$cfg['TrustedProxies']` for
935 detecting IP address behind proxies.
937 .. _servers_allowdeny_rules:
938 .. config:option:: $cfg['Servers'][$i]['AllowDeny']['rules']
940 :type: array of strings
943 The general format for the rules is as such:
947 <'allow' | 'deny'> <username> [from] <ipmask>
949 If you wish to match all users, it is possible to use a ``'%'`` as a
950 wildcard in the *username* field.
952 There are a few shortcuts you can
953 use in the *ipmask* field as well (please note that those containing
954 SERVER\_ADDRESS might not be available on all webservers):
960 'localhost' -> 127.0.0.1/8
961 'localnetA' -> SERVER_ADDRESS/8
962 'localnetB' -> SERVER_ADDRESS/16
963 'localnetC' -> SERVER_ADDRESS/24
965 Having an empty rule list is equivalent to either using ``'allow %
966 from all'`` if your rule order is set to ``'deny,allow'`` or ``'deny %
967 from all'`` if your rule order is set to ``'allow,deny'`` or
970 For the :term:`IP address` matching
971 system, the following work:
973 * ``xxx.xxx.xxx.xxx`` (an exact :term:`IP address`)
974 * ``xxx.xxx.xxx.[yyy-zzz]`` (an :term:`IP address` range)
975 * ``xxx.xxx.xxx.xxx/nn`` (CIDR, Classless Inter-Domain Routing type :term:`IP` addresses)
977 But the following does not work:
979 * ``xxx.xxx.xxx.xx[yyy-zzz]`` (partial :term:`IP` address range)
981 For :term:`IPv6` addresses, the following work:
983 * ``xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx`` (an exact :term:`IPv6` address)
984 * ``xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:[yyyy-zzzz]`` (an :term:`IPv6` address range)
985 * ``xxxx:xxxx:xxxx:xxxx/nn`` (CIDR, Classless Inter-Domain Routing type :term:`IPv6` addresses)
987 But the following does not work:
989 * ``xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xx[yyy-zzz]`` (partial :term:`IPv6` address range)
991 .. config:option:: $cfg['Servers'][$i]['SignonScript']
996 Name of PHP script to be sourced and executed to obtain login
997 credentials. This is alternative approach to session based single
998 signon. The script needs to provide function
999 ``get_login_credentials`` which returns list of username and
1000 password, accepting single parameter of existing username (can be
1001 empty). See :file:`examples/signon-script.php` for an example.
1003 .. config:option:: $cfg['Servers'][$i]['SignonSession']
1008 Name of session which will be used for signon authentication method.
1009 You should use something different than ``phpMyAdmin``, because this
1010 is session which phpMyAdmin uses internally. Takes effect only if
1011 :config:option:`$cfg['Servers'][$i]['SignonScript']` is not configured.
1013 .. config:option:: $cfg['Servers'][$i]['SignonURL']
1018 :term:`URL` where user will be redirected
1019 to log in for signon authentication method. Should be absolute
1022 .. config:option:: $cfg['Servers'][$i]['LogoutURL']
1027 :term:`URL` where user will be redirected
1028 after logout (doesn't affect config authentication method). Should be
1029 absolute including protocol.
1031 .. config:option:: $cfg['Servers'][$i]['StatusCacheDatabases']
1033 :type: array of strings
1036 Enables caching of ``TABLE STATUS`` outputs for specific databases on
1037 this server (in some cases ``TABLE STATUS`` can be very slow, so you
1038 may want to cache it). APC is used (if the PHP extension is available,
1039 if not, this setting is ignored silently). You have to provide
1040 :config:option:`$cfg['Servers'][$i]['StatusCacheLifetime']`.
1042 .. config:option:: $cfg['Servers'][$i]['StatusCacheLifetime']
1047 Lifetime in seconds of the ``TABLE STATUS`` cache if
1048 :config:option:`$cfg['Servers'][$i]['StatusCacheDatabases']` is used.
1053 .. config:option:: $cfg['ServerDefault']
1058 If you have more than one server configured, you can set
1059 :config:option:`$cfg['ServerDefault']` to any one of them to autoconnect to that
1060 server when phpMyAdmin is started, or set it to 0 to be given a list
1061 of servers without logging in.
1063 If you have only one server configured,
1064 :config:option:`$cfg['ServerDefault']` MUST be set to that server.
1066 .. config:option:: $cfg['VersionCheck']
1071 Enables check for latest versions using javascript on main phpMyAdmin
1076 This setting can be adjusted by your vendor.
1078 .. config:option:: $cfg['ProxyUrl']
1083 The url of the proxy to be used when phpmyadmin needs to access the outside
1084 intenet such as when retrieving the latest version info or submitting error
1085 reports. You need this if the server where phpMyAdmin is installed does not
1086 have direct access to the internet.
1087 The format is: "hostname:portnumber"
1089 .. config:option:: $cfg['ProxyUser']
1094 The username for authenticating with the proxy. By default, no
1095 authentication is performed. If a username is supplied, Basic
1096 Authentication will be performed. No other types of authentication
1097 are currently supported.
1099 .. config:option:: $cfg['ProxyPass']
1104 The password for authenticating with the proxy.
1106 .. config:option:: $cfg['MaxDbList']
1111 The maximum number of database names to be displayed in the main panel's
1114 .. config:option:: $cfg['MaxTableList']
1119 The maximum number of table names to be displayed in the main panel's
1120 list (except on the Export page). This limit is also enforced in the
1121 navigation panel when in Light mode.
1123 .. config:option:: $cfg['ShowHint']
1128 Whether or not to show hints (for example, hints when hovering over
1131 .. config:option:: $cfg['MaxCharactersInDisplayedSQL']
1136 The maximum number of characters when a :term:`SQL` query is displayed. The
1137 default limit of 1000 should be correct to avoid the display of tons of
1138 hexadecimal codes that represent BLOBs, but some users have real
1139 :term:`SQL` queries that are longer than 1000 characters. Also, if a
1140 query's length exceeds this limit, this query is not saved in the history.
1142 .. config:option:: $cfg['PersistentConnections']
1147 Whether `persistent connections <http://php.net/manual/en/features
1148 .persistent-connections.php>`_ should be used or not. Works with
1149 following extensions:
1151 * mysql (`mysql\_pconnect <http://php.net/manual/en/function.mysql-
1153 * mysqli (requires PHP 5.3.0 or newer, `more information
1154 <http://php.net/manual/en/mysqli.persistconns.php>`_).
1156 .. config:option:: $cfg['ForceSSL']
1161 Whether to force using https while accessing phpMyAdmin.
1165 In some setups (like separate SSL proxy or load balancer) you might
1166 have to set :config:option:`$cfg['PmaAbsoluteUri']` for correct
1169 .. config:option:: $cfg['ExecTimeLimit']
1171 :type: integer [number of seconds]
1174 Set the number of seconds a script is allowed to run. If seconds is
1175 set to zero, no time limit is imposed. This setting is used while
1176 importing/exporting dump files but has
1177 no effect when PHP is running in safe mode.
1179 .. config:option:: $cfg['SessionSavePath']
1184 Path for storing session data (`session\_save\_path PHP parameter
1185 <http://php.net/session_save_path>`_).
1187 .. config:option:: $cfg['MemoryLimit']
1189 :type: string [number of bytes]
1192 Set the number of bytes a script is allowed to allocate. If set to
1193 ``'-1'``, no limit is imposed.
1195 This setting is used while importing/exporting dump files and at some other
1196 places in phpMyAdmin so you definitely don't want to put here a too low
1197 value. It has no effect when PHP is running in safe mode.
1199 You can also use any string as in :file:`php.ini`, eg. '16M'. Ensure you
1200 don't omit the suffix (16 means 16 bytes!)
1202 .. config:option:: $cfg['SkipLockedTables']
1207 Mark used tables and make it possible to show databases with locked
1208 tables (since MySQL 3.23.30).
1210 .. config:option:: $cfg['ShowSQL']
1215 Defines whether :term:`SQL` queries
1216 generated by phpMyAdmin should be displayed or not.
1218 .. config:option:: $cfg['RetainQueryBox']
1223 Defines whether the :term:`SQL` query box
1224 should be kept displayed after its submission.
1226 .. config:option:: $cfg['CodemirrorEnable']
1231 Defines whether to use a Javascript code editor for SQL query boxes.
1232 CodeMirror provides syntax highlighting and line numbers. However,
1233 middle-clicking for pasting the clipboard contents in some Linux
1234 distributions (such as Ubuntu) is not supported by all browsers.
1236 .. config:option:: $cfg['AllowUserDropDatabase']
1241 Defines whether normal users (non-administrator) are allowed to delete
1242 their own database or not. If set as false, the link :guilabel:`Drop
1243 Database` will not be shown, and even a ``DROP DATABASE mydatabase`` will
1244 be rejected. Quite practical for :term:`ISP` 's with many customers.
1248 This limitation of :term:`SQL` queries is not
1249 as strict as when using MySQL privileges. This is due to nature of
1250 :term:`SQL` queries which might be quite
1251 complicated. So this choice should be viewed as help to avoid accidental
1252 dropping rather than strict privilege limitation.
1254 .. config:option:: $cfg['Confirm']
1259 Whether a warning ("Are your really sure...") should be displayed when
1260 you're about to lose data.
1262 .. config:option:: $cfg['UseDbSearch']
1267 Define whether the "search string inside database" is enabled or not.
1269 .. config:option:: $cfg['IgnoreMultiSubmitErrors']
1274 Define whether phpMyAdmin will continue executing a multi-query
1275 statement if one of the queries fails. Default is to abort execution.
1277 Cookie authentication options
1278 -----------------------------
1280 .. config:option:: $cfg['blowfish_secret']
1285 The "cookie" auth\_type uses blowfish algorithm to encrypt the
1286 password. If you are using the "cookie" auth\_type, enter here a
1287 random passphrase of your choice. It will be used internally by the
1288 blowfish algorithm: you won’t be prompted for this passphrase. There
1289 is no maximum length for this secret.
1291 .. versionchanged:: 3.1.0
1292 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
1293 makes a bit weaker security as this generated secret is stored in
1294 session and furthermore it makes impossible to recall user name from
1297 .. config:option:: $cfg['LoginCookieRecall']
1302 Define whether the previous login should be recalled or not in cookie
1303 authentication mode.
1305 This is automatically disabled if you do not have
1306 configured :config:option:`$cfg['blowfish_secret']`.
1308 .. config:option:: $cfg['LoginCookieValidity']
1310 :type: integer [number of seconds]
1313 Define how long a login cookie is valid. Please note that php
1314 configuration option `session.gc\_maxlifetime
1315 <http://php.net/manual/en/session.configuration.php#ini.session.gc-
1316 maxlifetime>`_ might limit session validity and if the session is lost,
1317 the login cookie is also invalidated. So it is a good idea to set
1318 ``session.gc_maxlifetime`` at least to the same value of
1319 :config:option:`$cfg['LoginCookieValidity']`.
1321 .. config:option:: $cfg['LoginCookieStore']
1323 :type: integer [number of seconds]
1326 Define how long login cookie should be stored in browser. Default 0
1327 means that it will be kept for existing session. This is recommended
1328 for not trusted environments.
1330 .. config:option:: $cfg['LoginCookieDeleteAll']
1335 If enabled (default), logout deletes cookies for all servers,
1336 otherwise only for current one. Setting this to false makes it easy to
1337 forget to log out from other server, when you are using more of them.
1339 .. _AllowArbitraryServer:
1340 .. config:option:: $cfg['AllowArbitraryServer']
1345 If enabled, allows you to log in to arbitrary servers using cookie
1350 Please use this carefully, as this may allow users access to MySQL servers
1351 behind the firewall where your :term:`HTTP`
1354 .. config:option:: $cfg['CaptchaLoginPublicKey']
1359 The public key for the reCaptcha service that can be obtain from
1360 http://www.google.com/recaptcha.
1362 reCaptcha will be then used in :ref:`cookie`.
1364 .. config:option:: $cfg['CaptchaLoginPrivateKey']
1369 The private key for the reCaptcha service that can be obtain from
1370 http://www.google.com/recaptcha.
1372 reCaptcha will be then used in :ref:`cookie`.
1374 Navigation panel setup
1375 ----------------------
1377 .. config:option:: $cfg['MaxNavigationItems']
1382 The number of items that can be displayed on each page of the
1385 .. config:option:: $cfg['NavigationTreeEnableGrouping']
1390 Defines whether to group the databases based on a common prefix
1391 in their name :config:option:`$cfg['NavigationTreeDbSeparator']`.
1393 .. config:option:: $cfg['NavigationTreeDbSeparator']
1395 :type: string or array
1398 The string used to separate the parts of the database name when
1399 showing them in a tree. Alternatively you can specify more strings in
1400 an array and all of them will be used as a separator.
1402 .. config:option:: $cfg['NavigationTreeTableSeparator']
1404 :type: string or array
1407 Defines a string to be used to nest table spaces. This means if you have
1408 tables like ``first__second__third`` this will be shown as a three-level
1409 hierarchy like: first > second > third. If set to false or empty, the
1410 feature is disabled. NOTE: You should not use this separator at the
1411 beginning or end of a table name or multiple times after another without
1412 any other characters in between.
1414 .. config:option:: $cfg['NavigationTreeTableLevel']
1419 Defines how many sublevels should be displayed when splitting up
1420 tables by the above separator.
1422 .. config:option:: $cfg['NumRecentTables']
1427 The maximum number of recently used tables shown in the navigation
1428 panel. Set this to 0 (zero) to disable the listing of recent tables.
1430 .. config:option:: $cfg['NavigationDisplayLogo']
1435 Defines whether or not to display the phpMyAdmin logo at the top of
1436 the navigation panel.
1438 .. config:option:: $cfg['NavigationLogoLink']
1441 :default: ``'index.php'``
1443 Enter :term:`URL` where logo in the
1444 navigation panel will point to. For use especially with self made
1445 theme which changes this.
1447 .. config:option:: $cfg['NavigationLogoLinkWindow']
1450 :default: ``'main'``
1452 Whether to open the linked page in the main window (``main``) or in a
1453 new one (``new``). Note: use ``new`` if you are linking to
1456 .. config:option:: $cfg['NavigationTreeDisplayItemFilterMinimum']
1461 Defines the minimum number of items (tables, views, routines and
1462 events) to display a JavaScript filter box above the list of items in
1463 the navigation tree.
1465 To disable the filter completely some high number can be used (e.g. 9999)
1467 .. config:option:: $cfg['NavigationTreeDisplayDbFilterMinimum']
1472 Defines the minimum number of databases to display a JavaScript filter
1473 box above the list of databases in the navigation tree.
1475 To disable the filter completely some high number can be used
1478 .. config:option:: $cfg['NavigationDisplayServers']
1483 Defines whether or not to display a server choice at the top of the
1486 .. config:option:: $cfg['DisplayServersList']
1491 Defines whether to display this server choice as links instead of in a
1494 .. config:option:: $cfg['NavigationTreeDefaultTabTable']
1497 :default: ``'tbl_structure.php'``
1499 Defines the tab displayed by default when clicking the small icon next
1500 to each table name in the navigation panel. Possible values:
1502 * ``tbl_structure.php``
1504 * ``tbl_select.php``
1505 * ``tbl_change.php``
1511 .. config:option:: $cfg['ShowStats']
1516 Defines whether or not to display space usage and statistics about
1517 databases and tables. Note that statistics requires at least MySQL
1518 3.23.3 and that, at this date, MySQL doesn't return such information
1519 for Berkeley DB tables.
1521 .. config:option:: $cfg['ShowServerInfo']
1526 Defines whether to display detailed server information on main page.
1527 You can additionally hide more information by using
1528 :config:option:`$cfg['Servers'][$i]['verbose']`.
1530 .. config:option:: $cfg['ShowPhpInfo']
1535 .. config:option:: $cfg['ShowChgPassword']
1540 .. config:option:: $cfg['ShowCreateDb']
1545 Defines whether to display the :guilabel:`PHP information` and
1546 :guilabel:`Change password` links and form for creating database or not at
1547 the starting main (right) frame. This setting does not check MySQL commands
1550 Please note that to block the usage of ``phpinfo()`` in scripts, you have to
1551 put this in your :file:`php.ini`:
1555 disable_functions = phpinfo()
1557 Also note that enabling the :guilabel:`Change password` link has no effect
1558 with config authentication mode: because of the hard coded password value
1559 in the configuration file, end users can't be allowed to change their
1565 .. config:option:: $cfg['ShowDbStructureCreation']
1570 Defines whether the database structure page (tables list) has a
1571 "Creation" column that displays when each table was created.
1573 .. config:option:: $cfg['ShowDbStructureLastUpdate']
1578 Defines whether the database structure page (tables list) has a "Last
1579 update" column that displays when each table was last updated.
1581 .. config:option:: $cfg['ShowDbStructureLastCheck']
1586 Defines whether the database structure page (tables list) has a "Last
1587 check" column that displays when each table was last checked.
1589 .. config:option:: $cfg['HideStructureActions']
1594 Defines whether the table structure actions are hidden under a "More"
1600 .. config:option:: $cfg['TableNavigationLinksMode']
1603 :default: ``'icons'``
1605 Defines whether the table navigation links contain ``'icons'``, ``'text'``
1608 .. config:option:: $cfg['ShowAll']
1613 Defines whether a user should be displayed a "Show all" button in browse
1614 mode or not in all cases. By default it is shown only on small tables (less
1615 than 500 rows) to avoid performance issues while getting too many rows.
1617 .. config:option:: $cfg['MaxRows']
1622 Number of rows displayed when browsing a result set and no LIMIT
1623 clause is used. If the result set contains more rows, "Previous" and
1624 "Next" links will be shown. Possible values: 25,50,100,250,500.
1626 .. config:option:: $cfg['Order']
1629 :default: ``'SMART'``
1631 Defines whether columns are displayed in ascending (``ASC``) order, in
1632 descending (``DESC``) order or in a "smart" (``SMART``) order - I.E.
1633 descending order for columns of type TIME, DATE, DATETIME and
1634 TIMESTAMP, ascending order else- by default.
1636 .. config:option:: $cfg['DisplayBinaryAsHex']
1641 Defines whether the "Show binary contents as HEX" browse option is
1644 .. config:option:: $cfg['GridEditing']
1647 :default: ``'double-click'``
1649 Defines which action (``double-click`` or ``click``) triggers grid
1650 editing. Can be deactived with the ``disabled`` value.
1652 .. config:option:: $cfg['SaveCellsAtOnce']
1657 Defines whether or not to save all edited cells at once for grid
1663 .. config:option:: $cfg['ProtectBinary']
1665 :type: boolean or string
1666 :default: ``'blob'``
1668 Defines whether ``BLOB`` or ``BINARY`` columns are protected from
1669 editing when browsing a table's content. Valid values are:
1671 * ``false`` to allow editing of all columns;
1672 * ``'blob'`` to allow editing of all columns except ``BLOBS``;
1673 * ``'noblob'`` to disallow editing of all columns except ``BLOBS`` (the
1674 opposite of ``'blob'``);
1675 * ``'all'`` to disallow editing of all ``BINARY`` or ``BLOB`` columns.
1677 .. config:option:: $cfg['ShowFunctionFields']
1682 Defines whether or not MySQL functions fields should be initially
1683 displayed in edit/insert mode. Since version 2.10, the user can toggle
1684 this setting from the interface.
1686 .. config:option:: $cfg['ShowFieldTypesInDataEditView']
1691 Defines whether or not type fields should be initially displayed in
1692 edit/insert mode. The user can toggle this setting from the interface.
1694 .. config:option:: $cfg['InsertRows']
1699 Defines the maximum number of concurrent entries for the Insert page.
1701 .. config:option:: $cfg['ForeignKeyMaxLimit']
1706 If there are fewer items than this in the set of foreign keys, then a
1707 drop-down box of foreign keys is presented, in the style described by
1708 the :config:option:`$cfg['ForeignKeyDropdownOrder']` setting.
1710 .. config:option:: $cfg['ForeignKeyDropdownOrder']
1713 :default: array('content-id', 'id-content')
1715 For the foreign key drop-down fields, there are several methods of
1716 display, offering both the key and value data. The contents of the
1717 array should be one or both of the following strings: ``content-id``,
1720 Export and import settings
1721 --------------------------
1723 .. config:option:: $cfg['ZipDump']
1728 .. config:option:: $cfg['GZipDump']
1733 .. config:option:: $cfg['BZipDump']
1738 Defines whether to allow the use of zip/GZip/BZip2 compression when
1739 creating a dump file
1741 .. config:option:: $cfg['CompressOnFly']
1746 Defines whether to allow on the fly compression for GZip/BZip2
1747 compressed exports. This doesn't affect smaller dumps and allows users
1748 to create larger dumps that won't otherwise fit in memory due to php
1749 memory limit. Produced files contain more GZip/BZip2 headers, but all
1750 normal programs handle this correctly.
1752 .. config:option:: $cfg['Export']
1755 :default: array(...)
1757 In this array are defined default parameters for export, names of
1758 items are similar to texts seen on export page, so you can easily
1759 identify what they mean.
1761 .. config:option:: $cfg['Export']['method']
1764 :default: ``'quick'``
1766 Defines how the export form is displayed when it loads. Valid values
1769 * ``quick`` to display the minimum number of options to configure
1770 * ``custom`` to display every available option to configure
1771 * ``custom-no-form`` same as ``custom`` but does not display the option
1772 of using quick export
1776 .. config:option:: $cfg['Import']
1779 :default: array(...)
1781 In this array are defined default parameters for import, names of
1782 items are similar to texts seen on import page, so you can easily
1783 identify what they mean.
1786 Tabs display settings
1787 ---------------------
1789 .. config:option:: $cfg['TabsMode']
1792 :default: ``'both'``
1794 Defines whether the menu tabs contain ``'icons'``, ``'text'`` or ``'both'``.
1796 .. config:option:: $cfg['ActionLinksMode']
1799 :default: ``'both'``
1801 If set to ``icons``, will display icons instead of text for db and table
1802 properties links (like :guilabel:`Browse`, :guilabel:`Select`,
1803 :guilabel:`Insert`, ...). Can be set to ``'both'``
1804 if you want icons AND text. When set to ``text``, will only show text.
1806 .. config:option:: $cfg['PropertiesNumColumns']
1811 How many columns will be utilized to display the tables on the database
1812 property view? When setting this to a value larger than 1, the type of the
1813 database will be omitted for more display space.
1815 .. config:option:: $cfg['DefaultTabServer']
1818 :default: ``'index.php'``
1820 Defines the tab displayed by default on server view. Possible values:
1822 * ``main.php`` (recommended for multi-user setups)
1823 * ``server_databases.php``,
1824 * ``server_status.php``
1825 * ``server_variables.php``
1826 * ``server_privileges.php``
1828 .. config:option:: $cfg['DefaultTabDatabase']
1831 :default: ``'db_structure.php'``
1833 Defines the tab displayed by default on database view. Possible
1836 * ``db_structure.php``
1838 * ``db_search.php``.
1840 .. config:option:: $cfg['DefaultTabTable']
1843 :default: ``'sql.php'``
1845 Defines the tab displayed by default on table view. Possible values:
1847 * ``tbl_structure.php``
1849 * ``tbl_select.php``
1850 * ``tbl_change.php``
1856 .. config:option:: $cfg['PDFPageSizes']
1859 :default: ``array('A3', 'A4', 'A5', 'letter', 'legal')``
1861 Array of possible paper sizes for creating PDF pages.
1863 You should never need to change this.
1865 .. config:option:: $cfg['PDFDefaultPageSize']
1870 Default page size to use when creating PDF pages. Valid values are any
1871 listed in :config:option:`$cfg['PDFPageSizes']`.
1876 .. config:option:: $cfg['DefaultLang']
1881 Defines the default language to use, if not browser-defined or user-
1882 defined. The corresponding language file needs to be in
1883 locale/*code*/LC\_MESSAGES/phpmyadmin.mo.
1885 .. config:option:: $cfg['DefaultConnectionCollation']
1888 :default: ``'utf8_general_ci'``
1890 Defines the default connection collation to use, if not user-defined.
1891 See the `MySQL documentation <http://dev.mysql.com/doc/mysql/en
1892 /charset-charsets.html>`_ for list of possible values. This setting is
1893 ignored when connected to Drizzle server.
1895 .. config:option:: $cfg['Lang']
1900 Force language to use. The corresponding language file needs to be in
1901 locale/*code*/LC\_MESSAGES/phpmyadmin.mo.
1903 .. config:option:: $cfg['FilterLanguages']
1908 Limit list of available languages to those matching the given regular
1909 expression. For example if you want only Czech and English, you should
1910 set filter to ``'^(cs|en)'``.
1912 .. config:option:: $cfg['RecodingEngine']
1915 :default: ``'auto'``
1917 You can select here which functions will be used for character set
1918 conversion. Possible values are:
1920 * auto - automatically use available one (first is tested iconv, then
1922 * iconv - use iconv or libiconv functions
1923 * recode - use recode\_string function
1924 * mb - use mbstring extension
1925 * none - disable encoding conversion
1927 Enabled charset conversion activates a pull-down menu in the Export
1928 and Import pages, to choose the character set when exporting a file.
1929 The default value in this menu comes from
1930 :config:option:`$cfg['Export']['charset']` and :config:option:`$cfg['Import']['charset']`.
1932 .. config:option:: $cfg['IconvExtraParams']
1935 :default: ``'//TRANSLIT'``
1937 Specify some parameters for iconv used in charset conversion. See
1938 `iconv documentation <http://www.gnu.org/software/libiconv/documentati
1939 on/libiconv/iconv_open.3.html>`_ for details. By default
1940 ``//TRANSLIT`` is used, so that invalid characters will be
1943 .. config:option:: $cfg['AvailableCharsets']
1946 :default: array(..._
1948 Available character sets for MySQL conversion. You can add your own
1949 (any of supported by recode/iconv) or remove these which you don't
1950 use. Character sets will be shown in same order as here listed, so if
1951 you frequently use some of these move them to the top.
1956 .. config:option:: $cfg['OBGzip']
1958 :type: string/boolean
1959 :default: ``'auto'``
1961 Defines whether to use GZip output buffering for increased speed in
1962 :term:`HTTP` transfers. Set to
1963 true/false for enabling/disabling. When set to 'auto' (string),
1964 phpMyAdmin tries to enable output buffering and will automatically
1965 disable it if your browser has some problems with buffering. IE6 with
1966 a certain patch is known to cause data corruption when having enabled
1969 .. config:option:: $cfg['TrustedProxies']
1974 Lists proxies and HTTP headers which are trusted for
1975 :config:option:`$cfg['Servers'][$i]['AllowDeny']['order']`. This list is by
1976 default empty, you need to fill in some trusted proxy servers if you
1977 want to use rules for IP addresses behind proxy.
1979 The following example specifies that phpMyAdmin should trust a
1980 HTTP\_X\_FORWARDED\_FOR (``X -Forwarded-For``) header coming from the proxy
1985 $cfg['TrustedProxies'] = array('1.2.3.4' => 'HTTP_X_FORWARDED_FOR');
1987 The :config:option:`$cfg['Servers'][$i]['AllowDeny']['rules']` directive uses the
1988 client's IP address as usual.
1990 .. config:option:: $cfg['GD2Available']
1993 :default: ``'auto'``
1995 Specifies whether GD >= 2 is available. If yes it can be used for MIME
1996 transformations. Possible values are:
1998 * auto - automatically detect
1999 * yes - GD 2 functions can be used
2000 * no - GD 2 function cannot be used
2002 .. config:option:: $cfg['CheckConfigurationPermissions']
2007 We normally check the permissions on the configuration file to ensure
2008 it's not world writable. However, phpMyAdmin could be installed on a
2009 NTFS filesystem mounted on a non-Windows server, in which case the
2010 permissions seems wrong but in fact cannot be detected. In this case a
2011 sysadmin would set this parameter to ``false``.
2013 .. config:option:: $cfg['LinkLengthLimit']
2018 Limit for length of :term:`URL` in links. When length would be above this
2019 limit, it is replaced by form with button. This is required as some web
2020 servers (:term:`IIS`) have problems with long :term:`URL` .
2022 .. config:option:: $cfg['CSPAllow']
2027 Additional string to include in allowed script and image sources in Content
2028 Security Policy header.
2030 This can be useful when you want to include some external javascript files
2031 in :file:`config.footer.inc.php` or :file:`config.header.inc.php`, which
2032 would be normally not allowed by Content Security Policy.
2034 To allow some sites, just list them within the string:
2038 $cfg['CSPAllow'] = 'example.com example.net';
2040 .. versionadded:: 4.0.4
2042 .. config:option:: $cfg['DisableMultiTableMaintenance']
2047 In the database Structure page, it's possible to mark some tables then
2048 choose an operation like optimizing for many tables. This can slow
2049 down a server; therefore, setting this to ``true`` prevents this kind
2050 of multiple maintenance operation.
2055 .. config:option:: $cfg['NaviWidth']
2060 Navigation panel width in pixels. See
2061 :file:`themes/themename/layout.inc.php`.
2063 .. config:option:: $cfg['NaviBackground']
2065 :type: string [CSS color for background]
2068 .. config:option:: $cfg['MainBackground']
2070 :type: string [CSS color for background]
2073 The background styles used for both the frames. See
2074 :file:`themes/themename/layout.inc.php`.
2076 .. config:option:: $cfg['NaviPointerBackground']
2078 :type: string [CSS color for background]
2081 .. config:option:: $cfg['NaviPointerColor']
2083 :type: string [CSS color]
2086 The style used for the pointer in the navigation panel. See
2087 :file:`themes/themename/layout.inc.php`.
2089 .. config:option:: $cfg['Border']
2094 The size of a table's border. See :file:`themes/themename/layout.inc.php`.
2096 .. config:option:: $cfg['ThBackground']
2098 :type: string [CSS color for background]
2101 .. config:option:: $cfg['ThColor']
2103 :type: string [CSS color]
2106 The style used for table headers. See
2107 :file:`themes/themename/layout.inc.php`.
2110 .. config:option:: $cfg['BgOne']
2112 :type: string [CSS color]
2115 The color (HTML) #1 for table rows. See
2116 :file:`themes/themename/layout.inc.php`.
2119 .. config:option:: $cfg['BgTwo']
2121 :type: string [CSS color]
2124 The color (HTML) #2 for table rows. See
2125 :file:`themes/themename/layout.inc.php`.
2127 .. config:option:: $cfg['BrowsePointerBackground']
2129 :type: string [CSS color]
2132 .. config:option:: $cfg['BrowsePointerColor']
2134 :type: string [CSS color]
2137 .. config:option:: $cfg['BrowseMarkerBackground']
2139 :type: string [CSS color]
2142 .. config:option:: $cfg['BrowseMarkerColor']
2144 :type: string [CSS color]
2147 The colors (HTML) uses for the pointer and the marker in browse mode.
2148 The former feature highlights the row over which your mouse is passing
2149 and the latter lets you visually mark/unmark rows by clicking on the
2150 corresponding checkbox. Highlighting / marking a column is done by
2151 hovering over / clicking the column's header (outside of the text).
2152 See :file:`themes/themename/layout.inc.php`.
2154 .. config:option:: $cfg['FontFamily']
2159 You put here a valid CSS font family value, for example ``arial, sans-
2160 serif``. See :file:`themes/themename/layout.inc.php`.
2162 .. config:option:: $cfg['FontFamilyFixed']
2167 You put here a valid CSS font family value, for example ``monospace``.
2168 This one is used in textarea. See :file:`themes/themename/layout.inc.php`.
2170 Design customization
2171 --------------------
2173 .. config:option:: $cfg['NavigationTreePointerEnable']
2178 A value of ``true`` activates the navi pointer.
2180 .. config:option:: $cfg['BrowsePointerEnable']
2185 Whether to activate the browse pointer or not.
2187 .. config:option:: $cfg['BrowseMarkerEnable']
2192 Whether to activate the browse marker or not.
2194 .. config:option:: $cfg['LimitChars']
2199 Maximum number of characters shown in any non-numeric field on browse
2200 view. Can be turned off by a toggle button on the browse page.
2202 .. config:option:: $cfg['RowActionLinks']
2205 :default: ``'left'``
2207 Defines the place where table row links (Edit, Copy, Delete) would be
2208 put when tables contents are displayed (you may have them displayed at
2209 the left side, right side, both sides or nowhere). "left" and "right"
2210 are parsed as "top" and "bottom" with vertical display mode.
2212 .. config:option:: $cfg['DefaultDisplay']
2215 :default: ``'horizonta'``
2217 There are 3 display modes: horizontal, horizontalflipped and vertical.
2218 Define which one is displayed by default. The first mode displays each
2219 row on a horizontal line, the second rotates the headers by 90
2220 degrees, so you can use descriptive headers even though columns only
2221 contain small values and still print them out. The vertical mode sorts
2222 each row on a vertical lineup.
2224 .. config:option:: $cfg['RememberSorting']
2229 If enabled, remember the sorting of each table when browsing them.
2231 .. config:option:: $cfg['HeaderFlipType']
2234 :default: ``'auto'``
2236 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
2237 'css' the rotation of the header for horizontalflipped is done via
2238 CSS. The CSS transformation currently works only in Internet
2239 Explorer.If set to 'fake' PHP does the transformation for you, but of
2240 course this does not look as good as CSS. The 'auto' option enables
2241 CSS transformation when browser supports it and use PHP based one
2244 .. config:option:: $cfg['ShowBrowseComments']
2249 .. config:option:: $cfg['ShowPropertyComments']
2254 By setting the corresponding variable to ``true`` you can enable the
2255 display of column comments in Browse or Property display. In browse
2256 mode, the comments are shown inside the header. In property mode,
2257 comments are displayed using a CSS-formatted dashed-line below the
2258 name of the column. The comment is shown as a tool-tip for that
2264 .. config:option:: $cfg['CharEditing']
2267 :default: ``'input'``
2269 Defines which type of editing controls should be used for CHAR and
2270 VARCHAR columns. Possible values are:
2272 * input - this allows to limit size of text to size of columns in MySQL,
2273 but has problems with newlines in columns
2274 * textarea - no problems with newlines in columns, but also no length
2277 .. config:option:: $cfg['MinSizeForInputField']
2282 Defines the minimum size for input fields generated for CHAR and
2285 .. config:option:: $cfg['MaxSizeForInputField']
2290 Defines the maximum size for input fields generated for CHAR and
2293 .. config:option:: $cfg['TextareaCols']
2298 .. config:option:: $cfg['TextareaRows']
2303 .. config:option:: $cfg['CharTextareaCols']
2308 .. config:option:: $cfg['CharTextareaRows']
2313 Number of columns and rows for the textareas. This value will be
2314 emphasized (\*2) for :term:`SQL` query
2315 textareas and (\*1.25) for :term:`SQL`
2316 textareas inside the query window.
2318 The Char\* values are used for CHAR
2319 and VARCHAR editing (if configured via :config:option:`$cfg['CharEditing']`).
2321 .. config:option:: $cfg['LongtextDoubleTextarea']
2326 Defines whether textarea for LONGTEXT columns should have double size.
2328 .. config:option:: $cfg['TextareaAutoSelect']
2333 Defines if the whole textarea of the query box will be selected on
2337 SQL query box settings
2338 ----------------------
2340 .. config:option:: $cfg['SQLQuery']['Edit']
2345 Whether to display an edit link to change a query in any SQL Query
2348 .. config:option:: $cfg['SQLQuery']['Explain']
2353 Whether to display a link to explain a SELECT query in any SQL Query
2356 .. config:option:: $cfg['SQLQuery']['ShowAsPHP']
2361 Whether to display a link to wrap a query in PHP code in any SQL Query
2364 .. config:option:: $cfg['SQLQuery']['Validate']
2369 Whether to display a link to validate a query in any SQL Query box.
2371 .. seealso:: :config:option:`$cfg['SQLValidator']`
2373 .. config:option:: $cfg['SQLQuery']['Refresh']
2378 Whether to display a link to refresh a query in any SQL Query box.
2380 Web server upload/save/import directories
2381 -----------------------------------------
2383 .. config:option:: $cfg['UploadDir']
2388 The name of the directory where :term:`SQL` files have been uploaded by
2389 other means than phpMyAdmin (for example, ftp). Those files are available
2390 under a drop-down box when you click the database or table name, then the
2394 you want different directory for each user, %u will be replaced with
2397 Please note that the file names must have the suffix ".sql"
2398 (or ".sql.bz2" or ".sql.gz" if support for compressed formats is
2401 This feature is useful when your file is too big to be
2402 uploaded via :term:`HTTP`, or when file
2403 uploads are disabled in PHP.
2407 If PHP is running in safe mode, this directory must be owned by the same
2408 user as the owner of the phpMyAdmin scripts. See also :ref:`faq1_16` for
2411 .. config:option:: $cfg['SaveDir']
2416 The name of the directory where dumps can be saved.
2418 If you want different directory for each user, %u will be replaced with
2421 Please note that the directory must exist and has to be writable for
2422 the user running webserver.
2426 If PHP is running in safe mode, this directory must be owned by the same
2427 user as the owner of the phpMyAdmin scripts.
2429 .. config:option:: $cfg['TempDir']
2434 The name of the directory where temporary files can be stored.
2436 This is needed for importing ESRI Shapefiles, see :ref:`faq6_30` and to
2437 work around limitations of ``open_basedir`` for uploaded files, see
2440 If the directory where phpMyAdmin is installed is
2441 subject to an ``open_basedir`` restriction, you need to create a
2442 temporary directory in some directory accessible by the web server.
2443 However for security reasons, this directory should be outside the
2444 tree published by webserver. If you cannot avoid having this directory
2445 published by webserver, place at least an empty :file:`index.html` file
2446 there, so that directory listing is not possible.
2448 This directory should have as strict permissions as possible as the only
2449 user required to access this directory is the one who runs the webserver.
2450 If you have root privileges, simply make this user owner of this directory
2451 and make it accessible only by it:
2456 chown www-data:www-data tmp
2459 If you cannot change owner of the directory, you can achieve a similar
2460 setup using :term:`ACL`:
2465 setfacl -m "g:www-data:rwx" tmp
2466 setfacl -d -m "g:www-data:rwx" tmp
2468 If neither of above works for you, you can still make the directory
2469 :command:`chmod 777`, but it might impose risk of other users on system
2470 reading and writing data in this directory.
2472 Various display setting
2473 -----------------------
2475 .. config:option:: $cfg['ShowDisplayDirection']
2480 Defines whether or not type display direction option is shown when
2483 .. config:option:: $cfg['RepeatCells']
2488 Repeat the headers every X cells, or 0 to deactivate.
2490 .. config:option:: $cfg['EditInWindow']
2495 .. config:option:: $cfg['QueryWindowWidth']
2500 .. config:option:: $cfg['QueryWindowHeight']
2505 .. config:option:: $cfg['QueryHistoryDB']
2510 .. config:option:: $cfg['QueryWindowDefTab']
2515 .. config:option:: $cfg['QueryHistoryMax']
2520 All those variables affect the query window feature. A :term:`SQL` link or
2521 icon is always displayed in the navigation panel. If JavaScript is enabled
2522 in your browser, a click on this opens a distinct query window, which is a
2523 direct interface to enter :term:`SQL` queries. Otherwise, the right panel
2524 changes to display a query box.
2526 The size of this query window can be customized with
2527 :config:option:`$cfg['QueryWindowWidth']` and
2528 :config:option:`$cfg['QueryWindowHeight']` - both integers for the size in
2529 pixels. Note that normally, those parameters will be modified in
2530 :file:`layout.inc.php`` for the theme you are using.
2532 If :config:option:`$cfg['EditInWindow']` is set to true, a click on [Edit]
2533 from the results page (in the :guilabel:`Showing Rows` section) opens the
2534 query window and puts the current query inside it. If set to false,
2535 clicking on the link puts the :term:`SQL` query
2536 in the right panel's query box.
2538 If :config:option:`$cfg['QueryHistoryDB']` is set to ``true``, all your
2539 Queries are logged to a table, which has to be created by you (see
2540 :config:option:`$cfg['Servers'][$i]['history']`). If set to false, all your
2541 queries will be appended to the form, but only as long as your window is
2542 opened they remain saved.
2544 When using the JavaScript based query window, it will always get updated
2545 when you click on a new table/db to browse and will focus if you click on
2546 :guilabel:`Edit SQL` after using a query. You can suppress updating the
2547 query window by checking the box :guilabel:`Do not overwrite this query
2548 from outside the window` below the query textarea. Then you can browse
2549 tables/databases in the background without losing the contents of the
2550 textarea, so this is especially useful when composing a query with tables
2551 you first have to look in. The checkbox will get automatically checked
2552 whenever you change the contents of the textarea. Please uncheck the button
2553 whenever you definitely want the query window to get updated even though
2554 you have made alterations.
2556 If :config:option:`$cfg['QueryHistoryDB']` is set to ``true`` you can
2557 specify the amount of saved history items using
2558 :config:option:`$cfg['QueryHistoryMax']`.
2560 The query window also has a custom tabbed look to group the features.
2561 Using the variable :config:option:`$cfg['QueryWindowDefTab']` you can
2562 specify the default tab to be used when opening the query window. It can be
2563 set to either ``sql``, ``files``, ``history`` or ``full``.
2565 .. config:option:: $cfg['BrowseMIME']
2570 Enable :ref:`transformations`.
2572 .. config:option:: $cfg['MaxExactCount']
2577 For InnoDB tables, determines for how large tables phpMyAdmin should
2578 get the exact row count using ``SELECT COUNT``. If the approximate row
2579 count as returned by ``SHOW TABLE STATUS`` is smaller than this value,
2580 ``SELECT COUNT`` will be used, otherwise the approximate count will be
2583 .. config:option:: $cfg['MaxExactCountViews']
2588 For VIEWs, since obtaining the exact count could have an impact on
2589 performance, this value is the maximum to be displayed, using a
2590 ``SELECT COUNT ... LIMIT``. Setting this to 0 bypasses any row
2593 .. config:option:: $cfg['NaturalOrder']
2598 Sorts database and table names according to natural order (for
2599 example, t1, t2, t10). Currently implemented in the navigation panel
2600 and in Database view, for the table list.
2602 .. config:option:: $cfg['InitialSlidersState']
2605 :default: ``'closed'``
2607 If set to ``'closed'``, the visual sliders are initially in a closed
2608 state. A value of ``'open'`` does the reverse. To completely disable
2609 all visual sliders, use ``'disabled'``.
2611 .. config:option:: $cfg['UserprefsDisallow']
2616 Contains names of configuration options (keys in ``$cfg`` array) that
2617 users can't set through user preferences. For possible values, refer
2618 to :file:`libraries/config/user_preferences.forms.php`.
2620 .. config:option:: $cfg['UserprefsDeveloperTab']
2625 Activates in the user preferences a tab containing options for
2626 developers of phpMyAdmin.
2631 .. config:option:: $cfg['TitleTable']
2634 :default: ``'@HTTP_HOST@ / @VSERVER@ / @DATABASE@ / @TABLE@ | @PHPMYADMIN@'``
2636 .. config:option:: $cfg['TitleDatabase']
2639 :default: ``'@HTTP_HOST@ / @VSERVER@ / @DATABASE@ | @PHPMYADMIN@'``
2641 .. config:option:: $cfg['TitleServer']
2644 :default: ``'@HTTP_HOST@ / @VSERVER@ | @PHPMYADMIN@'``
2646 .. config:option:: $cfg['TitleDefault']
2649 :default: ``'@HTTP_HOST@ | @PHPMYADMIN@'``
2651 Allows you to specify window's title bar. You can use :ref:`faq6_27`.
2653 Theme manager settings
2654 ----------------------
2656 .. config:option:: $cfg['ThemePath']
2659 :default: ``'./themes'``
2661 If theme manager is active, use this as the path of the subdirectory
2662 containing all the themes.
2664 .. config:option:: $cfg['ThemeManager']
2669 Enables user-selectable themes. See :ref:`faqthemes`.
2671 .. config:option:: $cfg['ThemeDefault']
2674 :default: ``'pmahomme'``
2676 The default theme (a subdirectory under :config:option:`$cfg['ThemePath']`).
2678 .. config:option:: $cfg['ThemePerServer']
2683 Whether to allow different theme for each server.
2688 .. config:option:: $cfg['DefaultQueryTable']
2691 :default: ``'SELECT * FROM @TABLE@ WHERE 1'``
2693 .. config:option:: $cfg['DefaultQueryDatabase']
2698 Default queries that will be displayed in query boxes when user didn't
2699 specify any. You can use standard :ref:`faq6_27`.
2701 SQL validator settings
2702 ----------------------
2704 .. config:option:: $cfg['SQLValidator']
2707 :default: array(...)
2711 .. config:option:: $cfg['SQLValidator']['use']
2716 phpMyAdmin now supports use of the `Mimer SQL Validator
2717 <http://developer.mimer.com/validator/index.htm>`_ service, as originally
2718 published on `Slashdot
2719 <http://developers.slashdot.org/article.pl?sid=02/02/19/1720246>`_. For
2720 help in setting up your system to use the service, see the
2721 :ref:`faqsqlvalidator`.
2723 .. config:option:: $cfg['SQLValidator']['username']
2728 .. config:option:: $cfg['SQLValidator']['password']
2733 The SOAP service allows you to log in with ``anonymous`` and any password,
2734 so we use those by default. Instead, if you have an account with them, you
2735 can put your login details here, and it will be used in place of the
2741 .. config:option:: $cfg['DefaultFunctions']
2744 :default: array(...)
2746 Functions selected by default when inserting/changing row, Functions
2747 are defined for meta types as (FUNC\_NUMBER, FUNC\_DATE, FUNC\_CHAR,
2748 FUNC\_SPATIAL, FUNC\_UUID) and for ``first_timestamp``, which is used
2749 for first timestamp column in table.
2757 These settings might have huge effect on performance or security.
2759 .. config:option:: $cfg['DBG']
2762 :default: array(...)
2764 .. config:option:: $cfg['DBG']['sql']
2769 Enable logging queries and execution times to be
2770 displayed in the bottom of main page (right frame).
2772 .. config:option:: $cfg['DBG']['demo']
2777 Enable to let server present itself as demo server.
2778 This is used for <http://demo.phpmyadmin.net/>.
2780 .. config:option:: $cfg['Error_Handler']['display']
2785 Whether to display errors from PHP or not.
2787 .. config:option:: $cfg['RowActionType']
2790 :default: ``'both'``
2792 Whether to display icons or text or both icons and text in table row action
2793 segment. Value can be either of ``'icons'``, ``'text'`` or ``'both'``.