| blob | 04f022bf493c1fae1a61616a1f106af109efec27 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <head>
14 </head>
18 <h1>
20 3.5.0-beta2
21 Documentation
22 </h1>
23 </div>
25 <!-- TOP MENU -->
34 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
39 </ul>
44 phpMyAdmin homepage</a></li>
46 SourceForge phpMyAdmin project page</a></li>
48 Official phpMyAdmin wiki</a></li>
50 Git repositories on Github</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
56 </ul>
58 <!-- REQUIREMENTS -->
65 , the Standard PHP Library (SPL) extension and JSON support.
66 </li>
69 currently the default), you should install the mbstring and ctype
70 extensions.
71 </li>
72 <li>You need GD2 support in PHP to display inline
74 original aspect ratio</li>
80 load pages significantly slower.
81 </li>
84 <li>To support BLOB streaming, see PHP and MySQL requirements
87 <li>To support XML and Open Document Spreadsheet importing,
88 you need PHP 5.2.17 or newer and the
90 </ul>
91 </li>
94 </ul>
96 <!-- INTRODUCTION -->
99 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
100 a single database. To accomplish the latter you'll need a properly set up
101 MySQL user who can read/write only the desired database. It's up to you to
102 look up the appropriate part in the MySQL manual.
103 </p>
108 <li>create, copy, drop, rename and alter databases, tables, columns and
109 indexes</li>
110 <li>maintenance server, databases and tables, with proposals on server
111 configuration</li>
112 <li>execute, edit and bookmark any
114 batch-queries</li>
117 </li>
124 OpenDocument Text and Spreadsheet,
127 </li>
128 <li>import data and MySQL structures from OpenDocument spreadsheets, as well as <abbr title="Extensible Markup Language">XML</abbr>, <abbr title="Comma Separated Values">CSV</abbr>, and <abbr title="Server Query Language">SQL</abbr> files</li>
132 <li>using Query-by-example (QBE), create complex queries automatically
133 connecting required tables</li>
135 your Database layout</li>
137 <li>transform stored data into any format using a set of predefined
138 functions, like displaying BLOB-data as image or download-link
139 </li>
147 <li>communicate in <a href="http://www.phpmyadmin.net/home_page/translations.php">62 different languages</a>
148 </li>
149 <li>synchronize two databases residing on the same as well as remote servers
151 </li>
153 </ul>
156 <p> Many people have difficulty
157 understanding the concept of user management with regards to phpMyAdmin. When
158 a user logs in to phpMyAdmin, that username and password are passed directly
159 to MySQL. phpMyAdmin does no account management on its own (other than
160 allowing one to manipulate the MySQL user account information); all users
161 must be valid MySQL users.</p>
170 <!-- INSTALLATION -->
178 </ol>
181 phpMyAdmin does not apply any special security methods to the MySQL database
182 server. It is still the system administrator's job to grant permissions on
184 be used for this.
185 </p>
193 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
194 before uploading them to your server, as PHP seems not to like
199 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
200 Downloads page. Some kits contain only the English messages,
201 others contain all languages in UTF-8 format (this should be fine
202 in most situations), others contain all
203 languages and all character sets. We'll assume you chose a kit whose
205 </li>
206 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
208 document root. If you don't have direct access to your document root,
209 put the files in a directory on your local machine, and, after step 4,
210 transfer the directory on your web server using, for example, ftp.</li>
211 <li>Ensure that all the scripts have the appropriate owner (if PHP is
212 running in safe mode, having some scripts with an owner different
213 from the owner of other scripts will be a
218 <li>Now you must configure your installation. There are two methods that
219 can be used. Traditionally, users have hand-edited a copy of
221 provided for those who prefer a graphical installation. Creating a
222 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
223 <ul><li>To manually create the file, simply use your text editor to
226 file) in the main (top-level) phpMyAdmin directory (the one
230 default value is okay for a particular setting, there is no
232 few directives to get going, a simple configuration may look
233 like this:
234 <pre>
235 <?php
236 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
238 $i=0;
239 $i++;
240 $cfg['Servers'][$i]['auth_type'] = 'cookie';
241 ?>
242 </pre>
243 Or, if you prefer to not be prompted every time you log in:
244 <pre>
245 <?php
247 $i=0;
248 $i++;
249 $cfg['Servers'][$i]['user'] = 'root';
250 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
251 $cfg['Servers'][$i]['auth_type'] = 'config';
252 ?>
253 </pre>
254 For a full explanation of possible configuration values, see the
260 directory. This is a security measure. On a Linux/Unix system you
261 can use the following commands:
262 <pre>
263 cd phpMyAdmin
264 mkdir config # create directory for saving
265 chmod o+rw config # give it world writable permissions
266 </pre>
267 And to edit an existing configuration, copy it over first:
268 <pre>
269 cp config.inc.php config/ # copy current configuration for editing
270 chmod o+w config/config.inc.php # give it world writable permissions
271 </pre>
272 On other platforms, simply create the folder and ensure that your
281 the webserver does not have the proper permissions you may see the
283 config/</tt> directory exists and has the proper permissions -
285 and upload (via FTP or some similar means) to the proper location.<br /><br />
287 Once the file has been saved, it must be moved out of the <tt>
288 config/</tt> directory and the permissions must be reset, again
289 as a security measure:
290 <pre>
291 mv config/config.inc.php . # move file to current directory
292 chmod o-rw config.inc.php # remove world read and write permissions
293 rm -rf config # remove not needed directory
294 </pre>
295 Now the file is ready to be used. You can choose to review or edit
296 the file with your favorite editor, if you prefer to set some
297 advanced options which the setup script does not provide.</li></ul></li>
298 <li>If you are using the
300 protect the phpMyAdmin installation directory because using
301 config does not require a user to
302 enter a password to access the phpMyAdmin installation. Use of an alternate
303 authentication method is recommended, for example with
311 in your browser. phpMyAdmin should now display a welcome screen
312 and your databases, or a login dialog if using
314 authentication mode.</li>
317 Apache you can use supplied <a href="#glossary"><i>.htaccess</i></a> file in that folder, for other
318 webservers, you should configure this yourself. Such configuration
319 prevents from possible path exposure and cross side scripting
320 vulnerabilities that might happen to be found in that code.</li>
321 <li>
322 It is generally good idea to protect public phpMyAdmin installation
323 against access by robots as they usually can not do anything good
325 your webserver or limit access by web server configuration, see
327 </li>
328 </ol>
332 <p> For a whole set of new features (bookmarks, comments,
334 tracking mechanism,
336 transformation, etc.) you need to create a set of special tables. Those
337 tables can be located in your own database, or in a central database for a
338 multi-user installation (this database would then be accessed by the
339 controluser, so no other user should have rights to it).</p>
350 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
351 that you may need special (administrator) privileges to create the database
352 and tables, and that the script may need some tuning, depending on the
353 database name.</p>
358 section</a>. You will also need to have a controluser with the proper rights
365 unpacked one. Configuration files from old versions may
366 require some tweaking as some options have been changed or removed; in
368 so you better remove it from your file and just use the default one.
370 statement that you might find near the end of your configuration file.</p>
374 is version-specific.</p>
377 version 5.x or newer and if you use the phpMyAdmin configuration storage,
378 you should run the SQL script found in
385 where you want to give users access to their own database and don't want
386 them to play around with others.<br />
387 Nevertheless be aware that MS Internet Explorer seems to be really buggy
391 that your user/password pair are not in clear in the configuration file.
392 </li>
395 authentication modes are more secure: the MySQL login information does
396 not need to be set in the phpMyAdmin configuration file (except possibly
398 However, keep in mind that the password travels in plain text, unless
399 you are using the HTTPS protocol.<br />
400 In cookie mode, the password is stored, encrypted with the blowfish
401 algorithm, in a temporary cookie.</li>
413 file under the
415 $cfg['Servers'][$i]['controluser']</a></tt> and
420 only an example: use something else in your file!</b> Input these
421 statements from the phpMyAdmin SQL Query window or mysql command–line
422 client.<br />
424 if it's not the same as the MySQL server's one.
426 <pre>
427 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
428 GRANT SELECT (
429 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
430 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
431 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
432 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
433 Execute_priv, Repl_slave_priv, Repl_client_priv
434 ) ON mysql.user TO 'pma'@'localhost';
435 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
436 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
437 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
438 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
440 If you want to use the many new relation and bookmark features:
442 <pre>
444 </pre>
447 configuration storage</a> be set up).
448 <br /></li>
451 on a set of particular databases. Normally you shouldn't give global
452 privileges to an ordinary user, unless you understand the impact of those
453 privileges (for example, you are creating a superuser).<br />
457 <pre>
458 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
459 </pre>
461 What the user may now do is controlled entirely by the MySQL user
462 management system.<br />
464 authentication mode, you don't need to fill the user/password fields
466 array.</li>
467 </ul>
472 method and allows you to log in as any valid MySQL user.</li>
473 <li>Is supported with most PHP configurations. For
486 mode.</li>
487 </ul>
491 <ul><li>You can use this method as a replacement for the
493 (for example, if you're running
495 <li>Obviously, the user must enable cookies in the browser, but this is
496 now a requirement for all authentication modes.</li>
497 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
498 with the same username.</li>
499 <li>If you want to log in to arbitrary server see
504 not required.</li>
505 </ul>
509 <ul><li>This mode is a convenient way of using credentials from another
510 application to authenticate to phpMyAdmin.</li>
511 <li>The other application has to store login information into
512 session data.</li>
514 section.</li>
515 </ul>
518 <ul><li>This mode is the less secure one because it requires you to fill the
520 $cfg['Servers'][$i]['user']</a> and
522 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
523 can read your config.inc.php can discover your username and password).
524 <br />
531 is an entry explaining how to protect your configuration file.</li>
532 <li>For additional security in this mode, you may wish to consider the Host
533 authentication
535 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
537 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
538 directives.</li>
539 <li>Unlike cookie and http, does not require a user to log in when first
540 loading the phpMyAdmin site. This is by design but could allow any
541 user to access your installation. Use of some restriction method is
543 HTTP-AUTH directive or disallowing incoming HTTP requests at
544 one’s router or firewall will suffice (both of which
545 are beyond the scope of this manual but easily searchable with Google).</li>
546 </ul>
548 <p>
549 The Swekey is a low cost authentication USB key that can be used in
550 web applications.<br /><br />
551 When Swekey authentication is activated, phpMyAdmin requires the
552 users's Swekey to be plugged before entering the login page (currently
553 supported for cookie authentication mode only). Swekey Authentication is
554 disabled by default.<br /><br />
556 </p>
557 <pre>
558 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
559 </pre>
560 <p>
562 each user with their Swekey Id. It is important to place this file outside
563 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
565 users' information.<br /><br />
566 If you want to purchase a Swekey please visit
568 since this link provides funding for phpMyAdmin.
569 </p>
570 <!-- CONFIGURATION -->
574 users:</span> PHP does not seem to like
578 before saving a script you have modified.</p>
583 section to create one. This file only needs to contain the parameters you want to
584 change from their corresponding default value in
587 <p> The parameters which relate to design (like colors) are placed in
590 your site specific code to be included on start and end of each page.</p>
594 (with full path) to your phpMyAdmin installation's directory.
597 some web servers are case–sensitive.
600 Starting with version 2.3.0, it is advisable to try leaving this
601 blank. In most cases phpMyAdmin automatically detects the proper
602 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
603 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
604 A good test is to browse a table, edit a row and save it. There should
605 be an error message if phpMyAdmin is having trouble auto–detecting
606 the correct value. If you get an error that this must be set or if
607 the autodetect code fails to detect your path, please post a bug
608 report on our bug tracker so we can improve the code.</dd>
612 with master / foreign – tables (see
614 <br />
615 If you tried to set this up and it does not work for you, have a look on
617 use it. You will find a link that will analyze why those features have
618 been disabled.<br />
619 If you do not want to use those features set this variable to
623 <dd>A warning is displayed on the main page if Suhosin is detected.
625 from appearing.</dd>
628 <dd>Disable the default warning that is displayed if mcrypt is missing for
629 cookie authentication.
631 from appearing.</dd>
638 domain to call phpMyAdmin inside a frame, and is a potential security
639 hole allowing cross-frame scripting attacks.</dd>
643 algorithm to encrypt the password.<br />
645 passphrase of your choice. It will be used internally by the blowfish
646 algorithm: you won’t be prompted for this passphrase. There is
647 no maximum length for this secret.<br /><br />
649 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
650 makes a bit weaker security as this generated secret is stored in
651 session and furthermore it makes impossible to recall user name from
652 cookie.</dd>
656 MySQL servers. Therefore, a
658 been added which contains the login information for the different servers.
659 The first
661 contains the hostname of the first server, the second
663 the hostname of the second server, etc. In
665 server definition, however you can put as many as you need in
667 have to define all settings, just those you need to change).</dd>
671 $i-th MySQL-server. E.g. localhost.</dd>
676 ignores this port number and connects with the socket, so if you want
677 to connect to a port different from the default port, use
680 </dd>
684 To determine the correct socket, check your MySQL configuration or, using the
686 Among the resulting information displayed will be the socket used.</dd>
689 <dd>Whether to enable SSL for connection to MySQL server.
690 </dd>
693 <dd>What type connection to use with the MySQL server. Your options are
695 is nearly guaranteed to be available on all MySQL servers, while
696 sockets are not supported on some platforms.<br /><br />
698 To use the socket mode, your MySQL server must be on the same machine
699 as the Web server.</dd>
702 <dd>What php MySQL extension to use for the connection. Valid options are:
703 <br /><br />
706 The classic MySQL extension.<br /><br />
709 The improved MySQL extension. This extension became available
710 with PHP 5.0.0 and is the recommended way to connect to a server
714 <dd>Whether to use a compressed protocol for the MySQL server connection
715 or not (experimental).</dd>
719 </dt>
720 <dd>Permits to use an alternate host to hold the configuration storage
721 data.</dd>
726 </dt>
728 all relational features (see
730 and, for a MySQL server running with
733 authentication mode).<br /><br />
736 cookie authentication modes (or 'config'
737 authentication mode since phpMyAdmin 2.2.1), you need to supply the
742 This account is used to check what databases the user will see at
743 login.<br />
747 In phpMyAdmin versions before 2.2.5, those were called
751 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
752 <dd>Whether config or cookie or
754 should be used for this server.
756 is the plain old way: username and password are stored in
758 <li>'cookie' authentication mode
760 2.2.3 allows you to log in as any valid MySQL user with the
761 help of cookies. Username and password are stored in
762 cookies during the session and password is deleted when it
763 ends. This can also allow you to log in in arbitrary server if
764 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
765 </li>
766 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
767 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
768 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
769 <li>'signon' authentication mode
771 as introduced in 2.10.0 allows you to log in from prepared PHP
772 session data or using supplied PHP script. This is useful for implementing single signon
773 from another application.
779 You need to
785 </ul>
788 for more information.
789 </dd>
791 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
792 </dt>
793 <dd>
794 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
795 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
796 specified in your configuration, a string combined of "phpMyAdmin " and either
799 </dd>
801 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
802 </dt>
803 <dd>
805 names for hardware authentication. Leave empty to deactivate this feature.
806 </dd>
810 </dt>
811 <dd>
812 When using auth_type = 'config', this is the user/password-pair
813 which phpMyAdmin will use to connect to the
814 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
815 cookie authentication is used and should be empty.</dd>
817 <span
819 </dt>
820 <dd>
821 Allow attempt to log in without password when a login with password
822 fails. This can be used together with http authentication, when
823 authentication is done some other way and phpMyAdmin gets user name
824 from auth and uses empty password for connecting to MySQL. Password
825 login is still tried first, but as fallback, no password method is
826 tried.</dd>
829 </dt>
830 <dd>
831 If set to a (an array of) database name(s), only this (these) database(s)
832 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
833 database(s) name(s) may contain MySQL wildcards characters
837 This setting is an efficient way to lower the server load since the
838 latter does not need to send MySQL requests to build the available
840 privileges rules of the MySQL database server</span>. If set, it just
841 means only these databases will be displayed but
843 <br /><br />
845 An example of using more that one database:
847 <br /><br />
849 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
850 databases in the left frame, so that you can individually arrange your databases.<br />
851 If you want to have certain databases at the top, but don't care about the others, you do not
852 need to specify all other databases. Use:
854 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
855 order.</dd>
858 </dt>
859 <dd>Regular expression for hiding some databases from unprivileged users.
860 This only hides them
861 from listing, but a user is still able to access them (using, for example,
862 the SQL query area). To limit access, use the MySQL privilege system.
863 <br /><br />
868 More information on regular expressions can be found in the
870 PCRE pattern syntax</a> portion of the PHP reference manual.
871 </dd>
874 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
875 this string will be displayed instead of the hostname in the pull-down
876 menu on the main page. This can be useful if you want to show only
877 certain databases on your system, for example. For HTTP auth, all
878 non-US-ASCII characters will be stripped.</dd>
882 </dt>
883 <dd>The name of the database containing the phpMyAdmin configuration storage.
884 <br /><br />
887 section in this document to see the benefits of this feature,
888 and for a quick way of creating this database and the needed tables.
889 <br /><br />
891 If you are the only user of this phpMyAdmin installation, you can
892 use your current database to store those special tables; in this
893 case, just put your current database name in
895 set this parameter to the name of your central database containing
896 the phpMyAdmin configuration storage.</dd>
900 </dt>
902 useful for queries you often run.<br /><br />
904 To allow the usage of this functionality:
906 <li>enter the table name in
908 </ul>
909 </dd>
913 </dt>
915 which column is a key in another table (a foreign key). phpMyAdmin
916 currently uses this to
917 <ul><li>make clickable, when you browse the master table, the data values
918 that point to the foreign table;</li>
920 when browsing the master table, if you move the mouse to a column
921 containing a foreign key (use also the 'table_info' table);<br />
924 <li>in edit/insert mode, display a drop-down list of possible foreign
928 <li>display links on the table properties page, to check referential
929 integrity (display missing foreign keys) for each described key;
930 </li>
934 schema of your database (also uses the table_coords table).</li>
935 </ul>
937 The keys can be numeric or character.<br /><br />
939 To allow the usage of this functionality:
942 configuration storage</li>
943 <li>put the relation table name in
945 <li>now as normal user open phpMyAdmin and for each one of your
946 tables where you want to use this feature, click
948 columns.
949 </li>
950 </ul>
954 future development of the cross-db relations.
955 </dd>
959 </dt>
960 <dd>
961 Since release 2.3.0 you can describe, in a special 'table_info'
962 table, which column is to be displayed as a tool-tip when moving the
963 cursor over the corresponding key.<br />
964 This configuration variable will hold the name of this special
965 table. To allow the usage of this functionality:
967 <li>put the table name in
969 'pma_table_info')</li>
970 <li>then for each table where you want to use this feature,
972 to choose the column.</li>
973 </ul>
975 </dd>
979 </dt>
982 the relations between your tables. To do this it needs two tables
987 schema output).<br /><br />
991 To allow the usage of this functionality:
994 <li>put the correct table names in
997 </ul>
1000 </dd>
1004 </dt>
1006 Since release 2.3.0 you can store comments to describe each column for
1008 <br /><br />
1010 Starting with release 2.5.0, comments are consequently used on the table
1011 property pages and table browse view, showing up as tool-tips above the
1012 column name (properties page) or embedded within the header of table in
1013 browse view. They can also be shown in a table dump. Please see the
1014 relevant configuration directives later on.<br /><br />
1016 Also new in release 2.5.0 is a MIME-transformation system which is also
1018 Transformations</a> for further information. To use the
1019 MIME-transformation system, your column_info table has to have the three
1020 new columns 'mimetype', 'transformation', 'transformation_options'.
1021 <br /><br />
1023 To allow the usage of this functionality:
1025 <li>put the table name in
1027 'pma_column_info')</li>
1030 <pre>
1031 ALTER TABLE `pma_column_comments`
1032 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1033 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1034 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1035 </pre>
1038 renamed from<br />
1041 </ul>
1042 </dd>
1046 </dt>
1049 all queries you entered manually into the phpMyAdmin interface. If you
1050 don't want to use a table-based history, you can use the JavaScript-based
1051 history. Using that, all your history items are deleted when closing the
1052 window.<br /><br />
1054 Using
1056 you can specify an amount of history items you want to have on hold. On
1057 every login, this list gets cut to the maximum amount.<br /><br />
1059 The query history is only available if JavaScript is enabled in your
1060 browser.<br /><br />
1062 To allow the usage of this functionality:
1066 (e.g. 'pma_history')
1067 </li>
1068 </ul>
1069 </dd>
1073 </dt>
1074 <dd>
1075 Since release 3.5.0 you can show recently used tables in the left navigation frame.
1076 It helps you to jump across table directly, without the need to select the database,
1077 and then select the table. Using
1079 you can configure the maximum number of recent tables shown. When you select a table
1080 from the list, it will jump to the page specified in
1081 <a href="#cfg_LeftDefaultTabTable" class="configrule">$cfg['LeftDefaultTabTable']</a>.<br/><br/>
1083 Without configuring the storage, you can still access the recently used tables,
1084 but it will disappear after you logout.<br/><br/>
1086 To allow the usage of this functionality persistently:
1088 <ul>
1091 </ul>
1092 </dd>
1096 </dt>
1097 <dd>
1098 Since release 3.5.0 phpMyAdmin can be configured to remember several things
1099 (sorted column
1101 , column order, and column visibility from a database table) for browsing tables.
1102 Without configuring the storage, these features still can be used,
1103 but the values will disappear after you logout.<br/><br/>
1105 To allow the usage of these functionality persistently:
1107 <ul>
1109 <li>put the table name in <tt>$cfg['Servers'][$i]['table_uiprefs']</tt> (e.g. 'pma_table_uiprefs')</li>
1110 </ul>
1111 </dd>
1115 </dt>
1116 <dd>
1117 Since release 3.3.x a tracking mechanism is available.
1119 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1120 and data definition statements. After enabling it you can create versions of tables.
1121 <br/><br/>
1122 The creation of a version has two effects:
1124 <ul>
1126 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1127 </ul>
1129 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1130 For the report you can use filters, for example you can get a list of statements within a date range.
1131 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1132 In addition you can export the (filtered) report to a file or to a temporary database.
1133 <br/><br/>
1135 To allow the usage of this functionality:
1137 <ul>
1140 </ul>
1141 </dd>
1144 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1145 </dt>
1146 <dd>
1147 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1148 <br/><br/>
1149 If this is set to true and you create a table or view with
1151 <ul>
1154 </ul>
1156 and no version exists for it, the mechanism will
1157 create a version for you automatically.
1158 </dd>
1161 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1162 </dt>
1163 <dd>
1164 Defines the list of statements the auto-creation uses for new versions. Default value is
1165 <br/>
1167 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1168 CREATE INDEX,DROP INDEX,
1169 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1170 CREATE VIEW,ALTER VIEW,DROP VIEW,
1171 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1172 </dd>
1175 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1176 </dt>
1177 <dd>
1178 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1179 <br/><br/>
1180 </dd>
1184 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1185 </dt>
1186 <dd>
1187 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1188 <br/><br/>
1189 </dd>
1192 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1193 </dt>
1194 <dd>
1195 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1196 <br/><br/>
1197 </dd>
1201 </dt>
1202 <dd>
1203 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1204 and store them in the database.
1205 <br /><br />
1208 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1209 or, it is is unavailable, until the end of session.
1210 <br /><br />
1212 To allow the usage of this functionality:
1214 <ul>
1216 configuration storage</li>
1218 </ul>
1219 </dd>
1223 </dt>
1225 to visually manage the relations.
1226 <br /><br />
1228 To allow the usage of this functionality:
1231 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1232 </li>
1233 </ul>
1234 </dd>
1236 <dt><span id="cfg_Servers_MaxTableUiprefs">$cfg['Servers'][$i]['MaxTableUiprefs']</span> integer
1237 </dt>
1241 When tables are dropped or renamed, table_uiprefs may contain invalid
1242 data (referring to tables which no longer exist).<br />
1243 We only keep this number of newest rows in table_uiprefs and automatically delete older rows.</dd>
1246 </dt>
1248 column_info table got enhanced with three new columns. If the above variable
1250 latest table structure available. If not, it will emit a warning to the
1251 superuser.<br /><br />
1253 You can disable this checking behavior by setting the variable to false,
1254 which should offer a performance increase.<br /><br />
1256 Recommended to set to FALSE, when you are sure, your table structure is
1257 up to date.</dd>
1259 boolean</dt>
1260 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1261 </dd>
1263 boolean</dt>
1264 <dd>Whether to allow logins without a password. The default
1266 to a MySQL server with was left with an empty password for root or
1267 on which an anonymous (blank) user is defined.
1268 </dd>
1271 </dt>
1273 authorization is disabled.<br /><br />
1276 all deny rules followed by allow rules. Access is allowed by default. Any
1277 client which does not match a Deny command or does match an Allow command
1278 will be allowed access to the server. <br /><br />
1281 applies all allow rules followed by deny rules. Access is denied by
1282 default. Any client which does not match an Allow directive or does
1283 match a Deny directive will be denied access to the server.<br /><br />
1285 If your rule order is set to 'explicit', authorization is
1286 performed in a similar fashion to rule order 'deny,allow', with the
1290 and was available in Apache by specifying allow and deny rules without
1291 setting any order.<br /><br />
1293 Please also see <a
1295 address behind proxies.
1296 </dd>
1298 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1299 </dt>
1300 <dd>The general format for the rules is as such:
1302 <pre>
1304 </pre>
1309 well (please note that those containing SERVER_ADDRESS might not be
1310 available on all webservers):
1311 <pre>
1317 </pre>
1319 Having an empty rule list is equivalent to either using
1325 following work:<br />
1327 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1328 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1329 But the following does not work:<br />
1332 Also IPv6 addresses are not supported.
1333 </dd>
1335 <dd>Disable using <tt>INFORMATION_SCHEMA</tt> to retrieve information (use <tt>SHOW</tt> commands instead), because of speed issues when many databases are present. Currently used in some parts of the code, more to come.
1336 </dd>
1337 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1339 DATABASES</tt> command used to fetch the name of available databases will
1340 probably be too slow, so it can be replaced by faster commands (see
1342 </dd>
1344 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1345 </dd>
1347 <dd>Name of PHP script to be sourced and executed to obtain
1348 login credentials. This is alternative approach to session based single
1349 signon. The script needs to provide function
1351 password, accepting single parameter of existing username (can be empty).
1353 </dd>
1354 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1355 <dd>Name of session which will be used for signon authentication method.
1357 this is session which phpMyAdmin uses internally. Takes effect only if
1359 is not configured.
1360 </dd>
1362 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1363 </dd>
1365 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1366 </dd>
1369 <dd>If you have more than one server configured, you can set
1371 that server when phpMyAdmin is started, or set it to 0 to be given a
1372 list of servers without logging in.<br />
1374 MUST be set to that server.</dd>
1377 <dd>Defines whether to refresh only parts of certain pages using Ajax
1378 techniques. Applies only where a non-Ajax behavior is possible;
1379 for example, the Designer feature is Ajax-only so this directive
1380 does not apply to it.</dd>
1383 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1384 page.</dd>
1387 <dd>The maximum number of database names to be displayed in the
1388 navigation frame and the database list.</dd>
1391 <dd>The maximum number of table names to be displayed in the
1392 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1393 when in Light mode.</dd>
1399 <dd>The maximum number of characters when a SQL query is displayed. The
1400 default limit of 1000 should be correct to avoid the display of tons
1401 of hexadecimal codes that represent BLOBs, but some users have real
1402 SQL queries that are longer than 1000 characters. Also, if a query's
1403 length exceeds this limit, this query is not saved in the history.</dd>
1406 <dd>Defines whether to use GZip output buffering for increased
1408 Set to true/false for enabling/disabling. When set to 'auto' (string),
1409 phpMyAdmin tries to enable output buffering and will automatically disable
1410 it if your browser has some problems with buffering. IE6 with a certain patch
1411 is known to cause data corruption when having enabled buffering.</dd>
1414 <dd>Whether <a href="http://php.net/manual/en/features.persistent-connections.php">persistent connections</a>
1415 should be used or not. Works with following extensions:
1416 <ul>
1417 <li>mysql (<a href="http://php.net/manual/en/function.mysql-pconnect.php">mysql_pconnect</a>),</li>
1418 <li>mysqli (requires PHP 5.3.0 or newer, <a href="http://php.net/manual/en/mysqli.persistconns.php">more information</a>).</li>
1419 </ul></dd>
1425 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1426 to zero, no time limit is imposed.<br />
1427 This setting is used while importing/exporting dump files and in the
1428 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1435 <dd>Set the number of bytes a script is allowed to allocate. If set
1436 to zero, no limit is imposed.<br />
1437 This setting is used while importing/exporting dump files and at some
1438 other places in phpMyAdmin so you definitely don't want to put here
1439 a too low value. It has no effect when PHP is running in safe mode.<br />
1440 You can also use any string as in php.ini, eg. '16M'. Ensure
1444 <dd>Mark used tables and make it possible to show databases with locked
1449 generated by phpMyAdmin should be displayed or not.</dd>
1453 query box should be kept displayed after its submission.</dd>
1456 <dd>Defines whether normal users (non-administrator) are allowed to
1457 delete their own database or not. If set as FALSE, the link "Drop
1459 mydatabase" will be rejected. Quite practical for
1461 customers.<br />
1462 Please note that this limitation of SQL queries is not as strict as
1463 when using MySQL privileges. This is due to nature of SQL queries
1464 which might be quite complicated. So this choice should be viewed as
1465 help to avoid accidental dropping rather than strict privilege
1466 limitation.</dd>
1470 displayed when you're about to lose data.</dd>
1473 <dd>Define whether the previous login should be recalled or not in cookie
1474 authentication mode.<br /><br />
1476 This is automatically disabled if you do not have configured
1478 </dd>
1481 <dd>Define how long is login cookie valid. Please note that php
1482 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1483 might limit session validity and if session is lost, login cookie is
1485 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1489 means that it will be kept for existing session. This is recommended
1490 for not trusted environments.</dd>
1493 <dd>If enabled (default), logout deletes cookies for all servers,
1494 otherwise only for current one. Setting this to false makes it easy to
1495 forget to log out from other server, when you are using more of
1496 them.</dd>
1502 <dd>Define whether phpMyAdmin will continue executing a multi-query
1503 statement if one of the queries fails. Default is to abort execution.</dd>
1506 <dd>Define whether phpMyAdmin will output the results of each query of a
1507 multi-query statement embedded into the
1512 <dd>If enabled, allows you to log in to arbitrary servers using cookie auth and permits to specify servers of your choice in the Synchronize dialog.
1513 <br /><br />
1516 MySQL servers behind the firewall where your
1518 </dd>
1527 <dd>Defines whether to use a select-based menu and display only the current
1528 tables in the left frame (smaller page). Only in Non-Lightmode you can
1529 use the feature to display nested folders using
1531 </dd>
1534 <dd>Defines whether to display the names of databases (in the
1535 selector) using a tree, see also
1537 </dd>
1540 string or array</dt>
1541 <dd>The string used to separate the parts of the database name when showing
1542 them in a tree. Alternatively you can specify more strings in an array
1543 and all of them will be used as a separator.</dd>
1546 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1547 This means if you have tables like 'first__second__third' this will be
1549 If set to FALSE or empty, the feature is disabled. NOTE: You should
1550 not use this separator at the beginning or end of a
1551 table name or multiple times after another without any other
1552 characters in between.</dd>
1555 <dd>Defines how many sublevels should be displayed when splitting
1556 up tables by the above separator.</dd>
1559 <dd>The maximum number of recently used tables shown in the left navigation
1563 <dd>Defines whether to display table comment as tool-tip in left frame or
1564 not.</dd>
1567 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1568 comment and the real name. That means that if you have a table called
1569 'user0001' and add the comment 'MyName' on it, you will see the name
1570 'MyName' used consequently in the left frame and the tool-tip shows
1571 the real name of the DB.</dd>
1574 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1576 When setting this to 'nested', the Alias of the Tablename is only used
1577 to split/nest the tables according to the
1579 directive. So only the folder is called like the Alias, the tablename itself
1580 stays the real tablename.</dd>
1583 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1586 <dd>Enter URL where logo in the navigation frame will point to.
1587 For use especially with self made theme which changes this.
1596 integer</dt>
1597 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1598 list of tables in the left frame.
1603 <dd>Defines whether or not to display a server choice at the top of the left frame.
1604 Defaults to FALSE.</dd>
1606 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1607 Defaults to FALSE (drop-down).</dd>
1609 <dd>Defines whether to display database choice in light navigation frame as links
1610 instead of in a drop-down. Defaults to 'auto' - on main page list is
1611 shown, when database is selected, only drop down is displayed.</dd>
1614 <dd>Defines the tab displayed by default when clicking the small
1615 icon next to each table name in the navigation panel. Possible
1621 <dd>Defines whether or not to display space usage and statistics about databases
1622 and tables.<br />
1623 Note that statistics requires at least MySQL 3.23.3 and that, at this
1624 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1627 <dd>Defines whether to display detailed server information on main page.
1628 You can additionally hide more information by using
1630 </dd>
1635 </dt>
1638 not at the starting main (right) frame. This setting
1639 does not check MySQL commands entered directly.<br /><br />
1641 Please note that to block the usage of phpinfo() in scripts, you
1648 hard coded password value in the configuration file, end users can't
1649 be allowed to change their passwords.</dd>
1652 <dd>Defines whether to suggest a database name on the
1656 <dd>Defines whether navigation bar buttons and the right panel top menu
1657 contain text or symbols only. A value of TRUE displays icons, FALSE
1658 displays text and 'both' displays both icons and text.</dd>
1661 <dd>Defines whether a user should be displayed a
1665 issues while getting too many rows.</dd>
1668 <dd>Number of rows displayed when browsing a result set and no LIMIT
1669 clause is used. If the result set contains more rows, "Previous" and "Next" links will be shown.</dd>
1675 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1679 option is ticked by default.</dd>
1683 from editing when browsing a table's content. Valid values are:
1688 </ul>
1689 </dd>
1692 <dd>Defines whether or not MySQL functions fields should be initially
1693 displayed in edit/insert mode. Since version 2.10, the user can
1694 toggle this setting from the interface.
1695 </dd>
1698 <dd>Defines whether or not type fields should be initially
1699 displayed in edit/insert mode. The user can
1700 toggle this setting from the interface.
1701 </dd>
1704 <dd>Defines which type of editing controls should be used for CHAR and
1705 VARCHAR columns. Possible values are:
1706 <ul><li>input - this allows to limit size of text to size of columns in
1707 MySQL, but has problems with newlines in columns</li>
1708 <li>textarea - no problems with newlines in columns, but also no
1709 length limitations</li>
1710 </ul>
1711 Default is old behavior so input.</dd>
1714 <dd>Defines the minimum size for input fields generated for CHAR and
1715 VARCHAR columns.</dd>
1718 <dd>Defines the maximum size for input fields generated for CHAR and
1719 VARCHAR columns.</dd>
1725 <dd>If there are fewer items than this in the set of foreign keys, then a
1726 drop-down box of foreign keys is presented, in the style described by the
1728 setting.</dd>
1731 <dd>For the foreign key drop-down fields, there are several methods of
1732 display, offering both the key and value data. The contents of the
1733 array should be one or both of the following strings:
1739 </dt>
1740 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1741 creating a dump file</dd>
1744 </dt>
1745 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1746 compressed exports. This doesn't affect smaller dumps and allows users to
1747 create larger dumps that won't otherwise fit in memory due to php
1748 memory limit. Produced files contain more GZip/BZip2 headers, but all
1749 normal programs handle this correctly.</dd>
1753 mainframe.</dd>
1757 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1762 <dd>How many columns will be utilized to display the tables on the
1763 database property view? Default is 1 column. When setting this to a
1764 value larger than 1, the type of the database will be omitted for more
1765 display space.</dd>
1769 <dd>Defines the tab displayed by default on server view. Possible
1776 <dd>Defines the tab displayed by default on database view. Possible
1781 <dd>Defines the tab displayed by default on table view. Possible
1788 points to the MySQL documentation (type depends
1789 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1790 generated.<br />
1792 for more information about MySQL manuals and their types.</dd>
1795 <dd>Type of MySQL documentation:
1801 </ul>
1802 </dd>
1805 <dd>Defines the default language to use, if not browser-defined or
1806 user-defined.<br />
1807 The corresponding language file needs to be in
1809 </dd>
1812 <dd>Defines the default connection collation to use, if not
1813 user-defined.<br />
1815 documentation</a> for list of possible values. This setting is ignored when
1816 connected to Drizzle server.</dd>
1820 The corresponding language file needs to be in
1822 </dd>
1825 <dd>Limit list of available languages to those matching the given regular
1826 expression. For example if you want only Czech and English, you should
1830 <dd>You can select here which functions will be used for character set
1831 conversion. Possible values are:
1832 <ul><li>auto - automatically use available one (first is tested
1833 iconv, then recode)</li>
1837 </ul>
1838 Default is auto.</dd>
1839 <dd>
1840 Enabled charset conversion activates a pull-down menu
1841 in the Export and Import pages, to choose the character set when
1842 exporting a file. The default value in this menu comes from
1844 </dd>
1847 <dd>Specify some parameters for iconv used in charset conversion. See
1850 used, so that invalid characters will be transliterated.</dd>
1853 <dd>Available character sets for MySQL conversion. You can add your own (any of
1854 supported by recode/iconv) or remove these which you don't use.
1855 Character sets will be shown in same order as here listed, so if you
1856 frequently use some of these move them to the top.</dd>
1861 default empty, you need to fill in some trusted proxy servers if you
1862 want to use rules for IP addresses behind proxy.<br /><br />
1864 The following example specifies that phpMyAdmin should trust a
1866 <pre>
1867 $cfg['TrustedProxies'] =
1869 </pre>
1870 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1871 client's IP address as usual.
1872 </dd>
1876 MIME transformations.<br />
1877 Possible values are:
1881 </ul>
1882 Default is auto.
1883 </dd>
1886 <dd>
1887 We normally check the permissions on the configuration file to ensure
1888 it's not world writable. However, phpMyAdmin could be installed on
1889 a NTFS filesystem mounted on a non-Windows server, in which case the
1890 permissions seems wrong but in fact cannot be detected. In this case
1892 </dd>
1895 <dd>
1896 Limit for length of URL in links. When length would be above this limit, it
1897 is replaced by form with button.
1898 This is required as some web servers (IIS) have problems with long URLs.
1900 </dd>
1902 <dt
1904 <dd>
1905 In the database Structure page, it's possible to mark some tables then
1906 choose an operation like optimizing for many tables. This can slow down
1909 </dd>
1913 </dd>
1915 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1917 </dt>
1918 <dd>The background styles used for both the frames.
1921 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1923 <dd>The style used for the pointer in the navi frame.
1932 </dd>
1936 <dd>The style used for table headers. See
1941 </dd>
1945 </dd>
1947 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1949 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1951 </dt>
1953 The former feature highlights the row over which your mouse is passing
1954 and the latter lets you visually mark/unmark rows by clicking on
1955 them. Highlighting / marking a column is done by hovering over /
1956 clicking the column's header (outside of the text).<br />
1961 <dd>You put here a valid CSS font family value, for example
1966 <dd>You put here a valid CSS font family value, for example
1980 </dt>
1982 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1984 The Char* values are used for CHAR and VARCHAR editing (if configured
1988 </dt>
1992 </dt>
1993 <dd>Defines if the whole textarea of the query box will be selected on
1994 click.</dd>
1997 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1998 Can be turned off by a toggle button on the browse page.</dd>
2001 </dt>
2002 <dd>Defines the place where table row links (Edit, Copy,
2003 Delete) would be put when tables contents are displayed (you may
2004 have them displayed at the left side, right side, both sides or nowhere).
2010 Define which one is displayed by default. The first mode displays each
2011 row on a horizontal line, the second rotates the headers by 90
2012 degrees, so you can use descriptive headers even though columns only
2013 contain small values and still print them out. The vertical mode sorts
2014 each row on a vertical lineup.
2015 </dd>
2021 <dd>
2022 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
2023 'css' the rotation of the header for horizontalflipped is done via
2024 CSS. The CSS transformation currently works only in Internet
2025 Explorer.If set to 'fake' PHP does the transformation for you, but of
2026 course this does not look as good as CSS. The 'auto' option enables
2027 CSS transformation when browser supports it and use PHP based one
2028 otherwise.
2029 </dd>
2033 </dt>
2035 display of column comments in Browse or Property display. In browse
2036 mode, the comments are shown inside the header. In property mode,
2037 comments are displayed using a CSS-formatted dashed-line below the
2038 name of the column. The comment is shown as a tool-tip for that column.
2039 </dd>
2051 <dd>Whether to display a link to validate a query in any SQL Query box.
2058 <dd>
2059 The name of the directory where
2061 uploaded by other means than phpMyAdmin (for example, ftp). Those files
2062 are available under a drop-down box when you click the database or
2063 table name, then the Import tab.
2064 <br /><br />
2066 If you want different directory for each user, %u will be replaced
2067 with username.<br /><br />
2071 compressed formats is enabled).<br /><br />
2073 This feature is useful when your file is too big to be uploaded via
2075 uploads are disabled in PHP.<br /><br />
2077 Please note that if PHP is running in safe mode, this directory must
2078 be owned by the same user as the owner of the phpMyAdmin scripts.
2079 <br /><br />
2083 alternatives.
2084 </dd>
2087 <dd>
2088 The name of the directory where dumps can be saved.<br /><br />
2090 If you want different directory for each user, %u will be replaced
2091 with username.<br /><br />
2093 Please note that the directory must exist and has to be writable for
2094 the user running webserver.<br /><br />
2096 Please note that if PHP is running in safe mode, this directory must
2097 be owned by the same user as the owner of the phpMyAdmin scripts.
2098 </dd>
2101 <dd>
2102 The name of the directory where temporary files can be stored.
2103 <br /><br />
2105 This is needed for importing ESRI Shapefiles, see
2110 <br /><br />
2112 If the directory where phpMyAdmin is installed is subject to an
2114 temporary directory in some directory accessible by the web
2115 server. However for security reasons, this directory should be outside
2116 the tree published by webserver. If you cannot avoid having this
2117 directory published by webserver, place at least an empty
2119 possible.
2120 <br /><br />
2122 This directory should have as strict permissions as possible as the only
2123 user required to access this directory is the one who runs the
2124 webserver. If you have root privileges, simply make this user owner of
2125 this directory and make it accessible only by it:
2126 <br /><br />
2128 <pre>
2129 chown www-data:www-data tmp
2130 chmod 700 tmp
2131 </pre>
2133 If you cannot change owner of the directory, you can achieve a similar
2136 <pre>
2137 chmod 700 tmp
2138 setfacl -m "g:www-data:rwx" tmp
2139 setfacl -d -m "g:www-data:rwx" tmp
2140 </pre>
2142 If neither of above works for you, you can still make the directory
2144 system reading and writing data in this directory.
2145 </dd>
2148 <dd>
2149 In this array are defined default parameters for export, names of
2150 items are similar to texts seen on export page, so you can easily
2151 identify what they mean.
2152 </dd>
2155 <dd>
2156 Defines how the export form is displayed when it loads. Valid values are:
2157 <ul>
2160 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2161 </ul>
2162 </dd>
2165 <dd>
2166 In this array are defined default parameters for import, names of
2167 items are similar to texts seen on import page, so you can easily
2168 identify what they mean.
2169 </dd>
2172 <dd>
2173 Defines whether or not to save all edited cells at once in browse-mode.
2174 </dd>
2177 <dd>
2178 Defines whether or not type display direction option is shown
2179 when browsing a table.
2180 </dd>
2183 <dd>
2184 Repeat the headers every X cells, or 0 to deactivate.
2185 </dd>
2193 </dt>
2194 <dd>
2195 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2196 or icon is always displayed on the left panel. If JavaScript is enabled in
2197 your browser, a click on this opens a distinct query window, which is
2198 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2199 changes to display a query box.<br /><br />
2201 The size of this query window can be customized with
2203 - both integers for the size in pixels. Note that normally, those
2205 theme you are using.<br /><br />
2209 opens the query window and puts the current query
2210 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2211 query in the right panel's query box.
2212 <br /><br />
2213 The usage of the JavaScript query window is recommended if you have a
2214 JavaScript enabled browser. Basic functions are used to exchange quite
2215 a few variables, so most 4th generation browsers should be capable to
2216 use that feature. It currently is only tested with Internet Explorer 6
2217 and Mozilla 1.x.
2218 <br /><br />
2220 to a table, which has to be created by you (see <a
2222 all your queries will be appended to the form, but only as long as
2223 your window is opened they remain saved.
2224 <br /><br />
2225 When using the JavaScript based query window, it will always get
2226 updated when you click on a new table/db to browse and will focus if
2227 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2228 the query window by checking the box "Do not overwrite this query from
2229 outside the window" below the query textarea. Then you can browse
2230 tables/databases in the background without losing the contents of the
2231 textarea, so this is especially useful when composing a query with
2232 tables you first have to look in. The checkbox will get automatically
2233 checked whenever you change the contents of the textarea. Please
2234 uncheck the button whenever you definitely want the query window to
2235 get updated even though you have made alterations.
2236 <br /><br />
2239 <br /><br />
2240 The query window also has a custom tabbed look to group the features.
2242 default tab to be used when opening the query window. It can be set to
2243 either 'sql', 'files', 'history' or 'full'.</dd>
2249 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2251 If the approximate row count as returned by
2254 count will be used.
2255 </dd>
2257 <dd>For VIEWs, since obtaining the exact count could have an
2258 impact on performance, this value is the maximum to be displayed, using
2260 any row counting.
2261 </dd>
2264 <dd>Sorts database and table names according to natural order (for example,
2265 t1, t2, t10). Currently implemented in the left panel (Light mode)
2266 and in Database view, for the table list.</dd>
2275 that users can't set through user preferences. For possible values, refer
2279 <dd>Activates in the user preferences a tab containing options for
2280 developers of phpMyAdmin.</dd>
2286 <dd>Allows you to specify window's title bar. You can use
2288 </dd>
2298 </dd>
2301 <dd>If theme manager is active, use this as the path of the subdirectory
2302 containing all the themes.</dd>
2316 </dt>
2317 <dd>Default queries that will be displayed in query boxes when user didn't
2318 specify any. You can use standard
2320 </dd>
2323 <dd>
2324 The main use of the new <abbr title="structured query language">SQL</abbr> Parser is to pretty-print <abbr title="structured query language">SQL</abbr> queries. By
2325 default we use HTML to format the query, but you can disable this by
2327 </dd>
2330 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2331 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2332 query inside a bracket is indented. By changing
2335 specifies the units of the indent amount that you specified. This is
2336 used via stylesheets.</dd>
2339 <dd>This array is used to define the colours for each type of element of
2340 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2342 If you specify an empty string for the color of a class, it is ignored
2343 in creating the stylesheet.
2344 You should not alter the class names, only the colour strings.<br />
2365 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2369 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2370 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2371 </ul>
2372 </dd>
2376 <dd>phpMyAdmin now supports use of the <a href="http://developer.mimer.com/validator/index.htm">Mimer <abbr title="structured query language">SQL</abbr> Validator</a> service,
2377 as originally published on
2379 <br />
2380 For help in setting up your system to use the service, see the
2382 </dd>
2386 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2387 and any password, so we use those by default. Instead, if
2388 you have an account with them, you can put your login details
2389 here, and it will be used in place of the anonymous login.</dd>
2390 </dl>
2391 </dd>
2394 <dd><b>DEVELOPERS ONLY!</b></dd>
2397 <dd><b>DEVELOPERS ONLY!</b><br />
2398 Enable logging queries and execution times to be displayed in the bottom
2399 of main page (right frame).</dd>
2402 <dd>All possible types of a MySQL column. In most cases you don't need to
2403 edit this.</dd>
2406 <dd>Possible attributes for columns. In most cases you don't need to edit
2407 this.</dd>
2410 <dd>A list of functions MySQL supports. In most cases you don't need to
2411 edit this.</dd>
2414 <dd>Mapping of column types to meta types used for preferring displayed
2415 functions. In most cases you don't need to edit this.</dd>
2418 <dd>Functions preferred for column meta types as defined in
2419 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2420 to edit this.</dd>
2423 <dd>Functions selected by default when inserting/changing row, Functions
2424 are defined for meta types from
2426 <code>first_timestamp</code>, which is used for first timestamp column
2427 in table.</dd>
2429 </dl>
2431 <!-- TRANSFORMATIONS -->
2437 </ol>
2441 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2443 section</a> on how to do so.</p>
2445 <p> You can apply different transformations to the contents of each column. The
2446 transformation will take the content of each column and transform it with
2447 certain rules defined in the selected transformation.</p>
2449 <p> Say you have a column 'filename' which contains a filename. Normally you would
2450 see in phpMyAdmin only this filename. Using transformations you can transform
2451 that filename into a HTML link, so you can click inside of the phpMyAdmin
2452 structure on the column's link and will see the file displayed in a new browser
2453 window. Using transformation options you can also specify strings to
2454 append/prepend to a string or the format you want the output stored in.</p>
2456 <p> For a general overview of all available transformations and their options,
2457 you can consult your
2458 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2459 installation.</p>
2461 <p> For a tutorial on how to effectively use transformations, see our
2463 the official phpMyAdmin homepage.</p>
2467 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2468 clicking on the 'Structure' link for a table). There click on
2469 "Change" (or change icon) and there you will see three new
2470 fields at
2471 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2472 'Transformation options'.</p>
2474 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2475 that corresponds to the column's contents. Please note that
2476 transformations are inactive as long as no MIME-type is selected.</li>
2478 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2479 hopefully growing amount of pre-defined transformations. See below for information on
2480 how to build your own transformation.<br />
2482 There are global transformations and mimetype-bound transformations. Global transformations
2483 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2484 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2485 transformations which operate on the main mimetype (like 'image'), which will most likely
2486 take the subtype into regard, and those who only operate on a
2487 specific subtype (like 'image/jpeg').<br />
2489 You can use transformations on mimetypes for which the function was not defined for. There
2490 is no security check for you selected the right transformation, so take care of what the
2491 output will be like.</li>
2493 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2494 transform-function specific options here. Usually the transforms can operate with default
2495 options, but it is generally a good idea to look up the overview to see which options are
2496 necessary.<br />
2498 Much like the ENUM/SET-Fields, you have to split up several options using the format
2499 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2500 parsed as an array, leaving the first value the first element in the array, and so
2501 forth.<br />
2503 If you want to specify a MIME character set you can define it in the transformation_options.
2504 You have to put that outside of the pre-defined options of the specific mime-transform,
2506 for which you can specify 2 options and you want to append a character set, enter "'first
2507 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2509 </ul>
2513 <p> All mimetypes and their transformations are defined through single files in
2514 the directory 'libraries/transformations/'.</p>
2516 <p> They are stored in files to ease up customization and easy adding of new
2517 transformations.</p>
2519 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2520 always work. It makes no sense to apply a transformation to a mimetype the
2521 transform-function doesn't know to handle.</p>
2523 <p> One can, however, use empty mime-types and global transformations which should work
2524 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2525 for, but pay attention to option usage as well as what the transformation does to your
2526 column.</p>
2528 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2529 any other transform function and provides some basic functions.</p>
2531 <p> There are 5 possible file names:</p>
2533 <ol><li>A mimetype+subtype transform:<br /><br />
2535 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2537 Please not that mimetype and subtype are separated via '_', which shall
2538 not be contained in their names. The transform function/filename may
2539 contain only characters which cause no problems in the file system as
2540 well as the PHP function naming convention.<br /><br />
2542 The transform function will the be called
2543 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2545 <b>Example:</b><br /><br />
2547 <tt>text_html__formatted.inc.php</tt><br />
2548 <tt>PMA_transform_text_html__formatted()</tt></li>
2550 <li>A mimetype (w/o subtype) transform:<br /><br />
2552 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2554 Please note that there are no single '_' characters.
2555 The transform function/filename may contain only characters which cause
2556 no problems in the file system as well as the PHP function naming
2557 convention.<br /><br />
2559 The transform function will the be called
2560 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2562 <b>Example:</b><br /><br />
2564 <tt>text__formatted.inc.php</tt><br />
2565 <tt>PMA_transform_text__formatted()</tt></li>
2567 <li>A mimetype+subtype without specific transform function<br /><br />
2569 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2571 Please note that there are no '__' characters in the filename. Do not
2572 use special characters in the filename causing problems with the file
2573 system.<br /><br />
2575 No transformation function is defined in the file itself.<br /><br />
2577 <b>Example:</b><br /><br />
2579 <tt>text_plain.inc.php</tt><br />
2580 (No function)</li>
2582 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2584 <tt>[mimetype].inc.php</tt><br /><br />
2586 Please note that there are no '_' characters in the filename. Do not use
2587 special characters in the filename causing problems with the file system.
2588 <br /><br />
2590 No transformation function is defined in the file itself.<br /><br />
2592 <b>Example:</b><br /><br />
2594 <tt>text.inc.php</tt><br />
2595 (No function)</li>
2597 <li>A global transform function with no specific mimetype<br /><br />
2599 <tt>global__[transform].inc.php</tt><br /><br />
2601 The transform function will the be called
2602 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2604 <b>Example:</b><br /><br />
2606 <tt>global__formatted</tt><br />
2607 <tt>PMA_transform_global__formatted()</tt></li>
2608 </ol>
2610 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2611 transform function.</p>
2613 <p> All filenames containing no '__' in themselves are not shown as valid transform
2614 functions in the dropdown.</p>
2616 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2617 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2618 without a transform function.</p>
2620 <p> To create a new transform function please see
2621 <tt>libraries/transformations/template_generator.sh</tt>.
2622 To create a new, empty mimetype please see
2623 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2625 <p> A transform function always gets passed three variables:</p>
2627 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2628 you want to transform.</li>
2629 <li><b>$options</b> - Contains any user-passed options to a transform function
2630 as an array.</li>
2631 <li><b>$meta</b> - Contains an object with information about your column.
2632 The data is drawn from the output of the
2634 function. This means, all object properties described on the
2636 available in this variable and can be used to transform a column accordingly
2637 to unsigned/zerofill/not_null/... properties.<br />
2638 The $meta->mimetype variable contains the original MIME-type of the
2639 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2640 </ol>
2642 <p> Additionally you should also provide additional function to provide
2643 information about the transformation to the user. This function should
2644 have same name as transformation function just with appended
2645 <code>_info</code> suffix. This function accepts no parameters and returns
2646 array with information about the transformation. Currently following keys
2647 can be used:
2648 </p>
2649 <dl>
2650 <dt><code>info</code></dt>
2651 <dd>Long description of the transformation.</dd>
2652 </dl>
2654 <!-- FAQ -->
2661 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2666 </ol>
2668 <p> Please have a look at our
2670 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2671 features and or interface.</p>
2677 action is required or phpMyAdmin sends a blank page or a page full of
2678 cryptic characters to my browser, what can I do?</a></h4>
2681 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2682 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2683 configuration file.<br /></p>
2688 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2689 See also the
2691 entry about PHP bugs with output buffering.<br />
2692 If your server keeps crashing, please ask for help in the various Apache
2693 support groups.</p>
2702 application misbehaved by not returning a complete set of
2704 </h4>
2706 <p> You just forgot to read the <i>install.txt</i> file from the PHP distribution.
2707 Have a look at the last message in this
2709 official PHP bug database.</p>
2714 and/or many error messages with the
2717 <p> This is a known problem with the PHP
2719 filter: it's not so stable. Please use instead the cookie authentication mode.
2720 </p>
2725 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2726 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2727 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2728 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2729 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2734 work.</a></h4>
2736 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2737 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2738 or not, and so on). So, you must have Zlib/Bzip2
2739 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2743 an error about safe mode being in effect.</a></h4>
2745 <p> Your uploaded file is saved by PHP in the "upload dir", as
2746 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2747 the system default is <i>/tmp</i>).<br />
2748 We recommend the following setup for Apache servers running in safe mode,
2749 to enable uploads of files while being reasonably secure:</p>
2751 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2752 <li>give ownership to the Apache server's user.group:
2753 <tt>chown apache.apache /tmp/php</tt></li>
2754 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2755 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2756 <li>restart Apache</li>
2757 </ul>
2764 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2765 I'm using the Apache server.</a></h4>
2767 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2768 your <i>httpd.conf</i>:</p>
2772 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2776 uploading a file from the query box.</a></h4>
2778 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2779 restrictions. However you need to create temporary directory and
2781 The uploaded files will be moved there, and after execution of your
2787 <p> The MySQL manual explains how to
2789 reset the permissions</a>.</p>
2799 </h4>
2801 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2802 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2803 names to align with current standards.</p>
2808 </h4>
2810 <p> Starting with version 2.7.0, the import engine has been re–written and these
2811 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2812 to take advantage of the new import features.</p>
2814 <p> The first things to check (or ask your host provider to check) are the
2815 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2816 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2817 All of these three settings limit the maximum size of data that can be
2818 submitted and handled by PHP. One user also said that
2819 <tt>post_max_size</tt>
2820 and <tt>memory_limit</tt> need to be larger than <tt>upload_max_filesize</tt>.<br /> <br />
2822 There exist several workarounds if your upload is too big or your
2823 hosting provider is unwilling to change the settings:</p>
2826 feature. This allows one to
2827 upload a file to the server via scp, ftp, or your favorite file transfer
2828 method. PhpMyAdmin is then able to import the files from the temporary
2830 section</a> of this document.</li>
2832 BigDump</a>) to split the files before uploading. We cannot support this
2833 or any third party applications, but are aware of users having success
2834 with it.</li>
2835 <li>If you have shell (command line) access, use MySQL to import the files
2836 directly. You can do this by issuing the "source" command from
2837 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2838 </ul>
2842 support?</a></h4>
2844 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2845 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2846 connect to your MySQL server using PHP's classic
2849 is available in PHP 5.0. The latter one should be used unless you have a
2850 good reason not to do so.<br />
2851 When compiling PHP, we strongly recommend that you manually link the MySQL
2852 extension of your choice to a MySQL client library of at least the same
2853 minor version since the one that is bundled with some PHP distributions is
2857 (versions 5.1 and 5.2 were tested).<br /><br />
2859 </p>
2863 message, "Client does not support authentication protocol requested
2864 by server; consider upgrading MySQL client"</a></h5>
2866 <p> You tried to access MySQL with an old MySQL client library. The version of
2867 your MySQL client library can be checked in your phpinfo() output.
2868 In general, it should have at least the same minor version as your server
2872 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2873 changed the authentication hash and your PHP is trying to use the old method.
2875 with the proper client library to match your MySQL installation. Your
2876 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2877 More information (and several workarounds) are located in the
2879 </p>
2886 script seems not to know the font face I'm using!</a></h4>
2888 <p> The "FPDF" library we're using for this feature requires some
2889 special files to use font faces.<br />
2891 these files.</p>
2895 check PHP Configuration".</a></h4>
2897 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2898 "MySQL extension". This extension may be part of the PHP
2899 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2900 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2901 to load the extension but failed.<br /><br />
2903 Usually, the problem is solved by installing a software package called
2904 "PHP-MySQL" or something similar.</p>
2909 and I cannot log in using cookie auth.</a></h4>
2911 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2915 so I cannot upload.</a></h4>
2917 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2918 parameter is not set to "on".</p>
2922 a new table the table and column names are changed to lowercase!</a></h4>
2924 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2925 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2926 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2927 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2928 directory and add the following line to the group [mysqld]:</p>
2930 <pre>set-variable = lower_case_table_names=0</pre>
2932 <p> Next, save the file and restart the MySQL service. You can always check the
2933 value of this directive using the query</p>
2935 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2942 and I get problems, such as undefined variables when I run a
2945 <p> A tip from Jose Fandos: put a comment on the following two lines
2946 in httpd.conf, like this:</p>
2948 <pre>
2949 # mod_gzip_item_include file \.php$
2951 </pre>
2953 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2954 PHP scripts. Of course you have to restart Apache.</p>
2959 I get the error "No input file specified" when trying to
2960 run phpMyAdmin.</a></h4>
2962 <p> This is a permission problem. Right-click on the phpmyadmin folder
2963 and choose properties. Under the tab Security, click on "Add"
2964 and select the user "IUSR_machine" from the list. Now set his
2965 permissions and it should work.</p>
2969 db_structure.php with plenty of tables).</a></h4>
2972 GZIP output buffering is enabled. If you turn off it (by
2974 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2975 PHP 5.0.0.</p>
2979 message 'Errorcode: 13'. What does this mean?</a></h4>
2981 <p> This can happen due to a MySQL bug when having database / table names with
2982 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2983 To fix this, turn off this directive, convert all database and table names
2984 to lower case and turn it on again. Alternatively, there's a bug-fix
2985 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2989 and the columns are duplicated.</a></h4>
2991 <p> It is possible to configure Apache in such a way that PHP has problems
2992 interpreting .php files.</p>
2994 <p> The problems occur when two different (and conflicting) set of directives
2995 are used:</p>
2997 <pre>
2998 SetOutputFilter PHP
2999 SetInputFilter PHP
3000 </pre>
3002 <p> and</p>
3004 <pre>AddType application/x-httpd-php .php</pre>
3006 <p> In the case we saw, one set of directives was in
3007 <tt>/etc/httpd/conf/httpd.conf</tt>, while
3008 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
3009 The recommended way is with <tt>AddType</tt>, so just comment out
3010 the first set of lines and restart Apache:</p>
3012 <pre>
3013 #SetOutputFilter PHP
3014 #SetInputFilter PHP
3015 </pre>
3020 <p> This problem is known to happen when the server is running Turck MMCache
3021 but upgrading MMCache to version 2.3.21 solves the problem.</p>
3026 <p>Yes.</p>
3027 <p>
3028 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
3029 is still maintained.
3030 </p>
3033 <a href="#faq1_32">1.32 Can I use <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication with <abbr title="Internet Information Services">IIS</abbr>?</a></h4>
3035 <p> Yes. This procedure was tested with phpMyAdmin 2.6.1, PHP 4.3.9 in <abbr title="Internet Server Application Programming Interface">ISAPI</abbr>
3038 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3039 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3040 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3041 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3042 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3043 enabled.) Click <tt>OK</tt>.</li>
3044 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3045 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3046 </ol>
3055 http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script. For <tt>server</tt> you use the server number which refers to
3056 the order of the server paragraph in <tt>config.inc.php</tt>.
3057 Table and script parts are optional. If you want
3058 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3059 some configuration. Following lines apply only for <a
3061 that you have enabled some features within global configuration. You need
3062 <code>Options FollowSymLinks</code> and <code>AllowOverride
3063 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3064 you need mod_rewrite to be enabled. Then you just need to create following
3066 (don't forget to change directory name inside of it):</p>
3068 <pre>
3069 RewriteEngine On
3070 RewriteBase /path_to_phpMyAdmin
3071 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3072 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3073 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3074 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3075 </pre>
3078 <a href="#faq1_35">1.35 Can I use <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication with Apache <abbr title="Common Gateway Interface">CGI</abbr>?</a></h4>
3080 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3081 following rewrite rule:</p>
3083 <pre>
3084 RewriteEngine On
3085 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3086 </pre>
3090 </h4>
3091 <p>
3092 There can be many explanations to this and a look at your server's
3093 error log file might give a clue.
3094 </p>
3098 password encryption in cookie auth doesn't work.</a></h4>
3100 <p> If your cluster consist of different architectures, PHP code used for
3101 encryption/decryption won't work correct. This is caused by use of
3102 pack/unpack functions in code. Only solution is to use mcrypt extension
3103 which works fine in this case.</p>
3108 <p> Yes but the default configuration values of Suhosin are known to cause
3109 problems with some operations, for example editing a table with many
3110 columns and no primary key or with textual primary key.
3111 </p>
3112 <p>
3113 Suhosin configuration might lead to malfunction in some cases and it can
3114 not be fully avoided as phpMyAdmin is kind of application which needs to
3115 transfer big amounts of columns in single HTTP request, what is something
3116 what Suhosin tries to prevent. Generally all
3117 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3118 <code>suhosin.get.*</code> directives can have negative effect on
3119 phpMyAdmin usability. You can always find in your error logs which limit
3120 did cause dropping of variable, so you can diagnose the problem and adjust
3121 matching configuration variable.
3122 </p>
3123 <p>
3124 The default values for most Suhosin configuration options will work in most
3125 scenarios, however you might want to adjust at least following parameters:
3126 </p>
3128 <ul>
3129 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_vars">suhosin.request.max_vars</a> should be increased (eg. 2048)</li>
3130 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_vars">suhosin.post.max_vars</a> should be increased (eg. 2048)</li>
3131 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_array_index_length">suhosin.request.max_array_index_length</a> should be increased (eg. 256)</li>
3132 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_array_index_length">suhosin.post.max_array_index_length</a> should be increased (eg. 256)</li>
3133 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_totalname_length">suhosin.request.max_totalname_length</a> should be increased (eg. 8192)</li>
3134 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_totalname_length">suhosin.post.max_totalname_length</a> should be increased (eg. 8192)</li>
3135 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.get.max_value_length">suhosin.get.max_value_length</a> should be increased (eg. 1024)</li>
3136 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.sql.bailout_on_error">suhosin.sql.bailout_on_error</a> needs to be disabled (the default)</li>
3137 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#logging_configuration">suhosin.log.*</a> should not include SQL, otherwise you get big slowdown</li>
3138 </ul>
3140 <p>
3142 <tt>SuhosinDisableWarning</tt> directive</a>.
3143 </p>
3147 but then my connection is redirected back to http. What can cause this
3148 behavior?</a></h4>
3150 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3151 in your Apache configuration. See <a href="http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions">http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions</a>.</p>
3154 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3156 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3157 Example from the Apache 2.2 documentation:</p>
3158 <pre>
3159 ProxyPass /mirror/foo/ http://backend.example.com/
3160 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3161 ProxyPassReverseCookieDomain backend.example.com public.example.com
3162 ProxyPassReverseCookiePath / /mirror/foo/
3163 </pre>
3165 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3166 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3167 This is not specific to phpmyadmin, it's just the behavior of Apache.
3168 </p>
3170 <pre>
3171 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3172 ProxyPassReverse /mirror/foo/
3173 http://backend.example.com/%7Euser/phpmyadmin
3174 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3175 </pre>
3177 <p>See <a href="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html">http://httpd.apache.org/docs/2.2/mod/mod_proxy.html</a>
3178 for more details.</p>
3182 privileges, I get an error about an unknown column.</a></h4>
3184 <p> The MySQL server's privilege tables are not up to date, you need to run
3185 the <tt>mysql_upgrade</tt> command on the server.</p>
3191 based on user agent field. This is quite easy to circumvent, but could prevent at least
3192 some robots accessing your installation.</p>
3194 <pre>
3195 RewriteEngine on
3197 # Allow only GET and POST verbs
3198 RewriteCond %{REQUEST_METHOD} !^(GET|POST)$ [NC,OR]
3200 # Ban Typical Vulnerability Scanners and others
3201 # Kick out Script Kiddies
3202 RewriteCond %{HTTP_USER_AGENT} ^(java|curl|wget).* [NC,OR]
3203 RewriteCond %{HTTP_USER_AGENT} ^.*(libwww-perl|curl|wget|python|nikto|wkito|pikto|scan|acunetix).* [NC,OR]
3204 RewriteCond %{HTTP_USER_AGENT} ^.*(winhttp|HTTrack|clshttp|archiver|loader|email|harvest|extract|grab|miner).* [NC,OR]
3206 # Ban Search Engines, Crawlers to your administrative panel
3207 # No reasons to access from bots
3208 # Ultimately Better than the useless robots.txt
3209 # Did google respect robots.txt?
3210 # Try google: intitle:phpMyAdmin intext:"Welcome to phpMyAdmin *.*.*" intext:"Log in" -wiki -forum -forums -questions intext:"Cookies must be enabled"
3211 RewriteCond %{HTTP_USER_AGENT} ^.*(AdsBot-Google|ia_archiver|Scooter|Ask.Jeeves|Baiduspider|Exabot|FAST.Enterprise.Crawler|FAST-WebCrawler|www\.neomo\.de|Gigabot|Mediapartners-Google|Google.Desktop|Feedfetcher-Google|Googlebot|heise-IT-Markt-Crawler|heritrix|ibm.com\cs/crawler|ICCrawler|ichiro|MJ12bot|MetagerBot|msnbot-NewsBlogs|msnbot|msnbot-media|NG-Search|lucene.apache.org|NutchCVS|OmniExplorer_Bot|online.link.validator|psbot0|Seekbot|Sensis.Web.Crawler|SEO.search.Crawler|Seoma.\[SEO.Crawler\]|SEOsearch|Snappy|www.urltrends.com|www.tkl.iis.u-tokyo.ac.jp/~crawler|SynooBot|crawleradmin.t-info@telekom.de|TurnitinBot|voyager|W3.SiteSearch.Crawler|W3C-checklink|W3C_Validator|www.WISEnutbot.com|yacybot|Yahoo-MMCrawler|Yahoo\!.DE.Slurp|Yahoo\!.Slurp|YahooSeeker).* [NC]
3212 RewriteRule .* - [F]
3213 </pre>
3221 headers already sent by ..." is displayed, what's the problem?</a></h4>
3223 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3224 (I.E. no blank lines, no spaces, no characters...) neither before the
3225 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3226 tag at the end. We also got a report from a user under IIS, that used
3227 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3228 contained an end-of-line character (hex 0A) at the end; removing this character
3229 cleared his errors.</p>
3234 <p> Either there is an error with your PHP setup or your username/password is
3235 wrong. Try to make a small script which uses mysql_connect and see if it
3236 works. If it doesn't, it may be you haven't even compiled MySQL support
3237 into PHP.</p>
3241 connect to local MySQL server through socket '/tmp/mysql.sock'
3242 (111) ..." is displayed. What can I do?</a></h4>
3244 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3246 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3247 In your <i>php.ini</i> you will find a line</p>
3249 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3251 <p> change it to</p>
3253 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3255 <p> Then restart apache and it will work.</p>
3257 <p> Here is a fix suggested by Brad Ummer:</p>
3259 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3260 To do this, telnet to your server and go to the MySQL bin directory. In
3261 this directory there should be a file named <i>mysqladmin</i>. Type
3262 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3263 info about your MySQL server, including the socket
3264 (<i>/tmp/mysql.sock</i>, for example).</li>
3265 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3266 phpMyAdmin, you need to complete the socket information in the
3267 <i>config.inc.php</i>.<br />
3268 For example:
3270 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3271 <br /><br />
3273 Please also make sure that the permissions of this file allow to be readable
3274 by your webserver (i.e. '0755').</li>
3275 </ul>
3277 <p> Have also a look at the
3279 corresponding section of the MySQL documentation</a>.</p>
3283 what can I do?</a></h4>
3286 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3287 sometime.<br />
3288 Also have a look at your PHP version number: if it contains "b" or "alpha"
3289 it means you're running a testing version of PHP. That's not a so good idea,
3290 please upgrade to a plain revision.</p>
3294 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3295 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3297 <p> Check the value you set for the
3299 directive in the phpMyAdmin configuration file.</p>
3303 password: YES)"-error when trying to access a MySQL-Server on a
3304 host which is port-forwarded for my localhost.</a></h4>
3306 <p> When you are using a port on your localhost, which you redirect via
3307 port-forwarding to another host, MySQL is not resolving the localhost
3308 as expected.<br />
3309 Erik Wasser explains: The solution is: if your host is "localhost"
3310 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3311 connection for speeding up things. And that doesn't work in this configuration
3312 with port forwarding.<br />
3318 <p> Themes are configured with
3322 <br />
3324 should not delete the directory "original" or its underlying
3325 structure, because this is the system theme used by phpMyAdmin.
3326 "original" contains all images and styles, for backwards
3327 compatibility and for all themes that would not include images or css-files.
3328 <br /><br />
3331 is enabled, you can select your favorite theme on the main page. Your
3332 selected theme will be stored in a cookie.<br /><br /></p>
3334 <p> To create a theme:</p>
3336 <ul><li>make a new subdirectory (for example "your_theme_name") under
3338 (by default <tt>themes</tt>)</li>
3339 <li>copy the files and directories from "original" to
3340 "your_theme_name"</li>
3341 <li>edit the css-files in "your_theme_name/css"</li>
3342 <li>put your new images in "your_theme_name/img"</li>
3343 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3344 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3345 contain your chosen theme name, that will be visible in user interface</li>
3346 <li>make a new screenshot of your theme and save it under
3347 "your_theme_name/screen.png"</li>
3348 </ul>
3350 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3351 theme verbose name, theme generation and theme version. These versions and
3352 generations are enumerated from 1 and do not have any direct dependence on
3353 phpMyAdmin version. Themes within same generation should be backwards
3354 compatible - theme with version 2 should work in phpMyAdmin requiring
3355 version 1. Themes with different generation are incompatible.</p>
3357 <p> If you do not want to use your own symbols and buttons, remove the
3358 directory "img" in "your_theme_name". phpMyAdmin will
3359 use the default icons and buttons (from the system-theme "original").
3360 </p>
3364 what can I do?</a></h4>
3366 <p> Here are a few points to check:</p>
3368 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3370 directive empty. See also
3372 </li>
3373 <li>Maybe you have a broken PHP installation or you need to upgrade
3374 your Zend Optimizer. See
3376 http://bugs.php.net/bug.php?id=31134</a>.
3377 </li>
3378 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3379 set to the default (200) or another low value, you could get this
3380 error if your table has a high number of columns. Adjust this setting
3381 accordingly. (Thanks to Klaus Dorninger for the hint).
3382 </li>
3383 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3384 of ";" will cause this error. Replace it with "&;".
3385 </li>
3387 you might want to increase
3389 </li>
3390 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3391 </li>
3392 </ul>
3397 <p> To be able to see a progress bar during your uploads, your server must
3400 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3401 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3408 who logged out can not log in again in with the same nick.</a></h4>
3410 <p> This is related to the authentication mechanism (protocol) used by
3411 phpMyAdmin. To bypass this problem: just close all the opened
3412 browser windows and then go back to phpMyAdmin. You should be able to
3413 log in again.</p>
3417 limit error or a time limit error.</a></h4>
3419 <p> Compressed dumps are built in memory and because of this are limited to
3420 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3421 using
3423 (enabled by default). Zip exports can not be handled this way, so if you need
3424 Zip files for larger dump, you have to use another way.</p>
3428 when I rename a table or a column.</a></h4>
3430 <p> This is an InnoDB bug, see <a href="http://bugs.mysql.com/bug.php?id=21704">http://bugs.mysql.com/bug.php?id=21704</a>.</p>
3434 bundled with the MySQL server distribution.</a></h4>
3436 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3438 <pre>
3439 -- MySQL dump 8.22
3440 --
3441 -- Host: localhost Database: database
3442 ---------------------------------------------------------
3443 -- Server version 3.23.54
3444 </pre>
3446 <p> The invalid part of the code is the horizontal line made of dashes that
3447 appears once in every dump created with mysqldump. If you want to run your
3448 dump you have to turn it into valid MySQL. This means, you have to add a
3449 whitespace after the first two dashes of the line or add a # before it:
3450 <br />
3451 <code>
3452 -- -------------------------------------------------------<br />
3453 </code>
3454 or<br />
3455 <code>
3456 #---------------------------------------------------------
3457 </code>
3458 </p>
3465 <p> Please note that you should not use the separating string multiple times
3466 without any characters between them, or at the beginning/end of your table
3467 name. If you have to, think about using another TableSeparator or disabling
3468 that feature</p>
3473 <p> In Relation view, being able to choose a table in another database,
3474 or having more than one index column in the foreign key.<br /><br/>
3475 In Query-by-example (Query), automatic generation of the query
3476 LEFT JOIN from the foreign table.<br /><br/>
3477 </p>
3481 I get series of errors like "Warning: unable to parse url". How
3482 can this be fixed?</a></h4>
3483 <p>
3484 Your table neither have a primary key nor an unique one, so we must use a
3485 long expression to identify this row. This causes problems to parse_url
3486 function. The workaround is to create a primary or unique key.
3487 <br />
3488 </p>
3492 a MIME-Transformation onto!</a></h4>
3494 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3495 nested forms can be put inside the table where phpMyAdmin displays the results.
3496 You can, however, use any form inside of a table if keep the parent
3497 form-container with the target to tbl_row_delete.php and just put your own
3498 input-elements inside. If you use a custom submit input field, the form will
3499 submit itself to the displaying page again, where you can validate the
3500 $HTTP_POST_VARS in a transformation.
3502 For a tutorial on how to effectively use transformations, see our
3504 on the official phpMyAdmin-homepage.</p>
3508 MySQL server</a></h4>
3510 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3513 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3514 the quote-character (") is interpreted as an identifier quote character and
3515 not as a string quote character, which makes many internal phpMyAdmin
3517 statements. There is no workaround to this behaviour. News to this item will
3518 be posted in Bug report
3519 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3520 </p>
3524 more that one column with the same value
3525 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3526 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3528 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3529 can use it for the Edit and Delete links.</p>
3534 <p> phpMyAdmin uses a quick method to get the row count, and this method
3535 only returns an approximate count in the case of InnoDB tables. See
3537 a way to modify those results, but
3538 this could have a serious impact on performance.</p>
3545 containing an hyphen.
3546 </a></h4>
3547 <p>
3548 The tests I have made with MySQL 5.1.49 shows that the
3549 API does not accept this syntax for the USE command.
3550 </p>
3553 <a href="#faq3_14">3.14 I am not able to browse a table when I don't have the right to SELECT one of the columns.</a></h4>
3554 <p>
3555 This has been a known limitation of phpMyAdmin since the beginning and
3556 it's not likely to be solved in the future.
3557 </p>
3559 <!-- Begin: Excel import limitations -->
3570 <!-- End: Excel import limitations -->
3571 <!-- Begin: CSV import limitations -->
3574 <a href="#faq3_18">3.18 When I import a CSV file that contains multiple tables, they are lumped together into a single table.</a></h4>
3575 <p>
3576 There is no reliable way to differentiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3577 </p>
3579 <!-- End: CSV import limitations -->
3580 <!-- Begin: Import type-detection limitations -->
3583 <a href="#faq3_19">3.19 When I import a file and have phpMyAdmin determine the appropriate data structure it only uses int, decimal, and varchar types.</a></h4>
3584 <p>
3585 Currently, the import type-detection system can only assign these MySQL types to columns. In future, more will likely be added but for the time being
3586 you will have to edit the structure to your liking post-import.
3587 <br /><br />
3588 Also, you should note the fact that phpMyAdmin will use the size of the largest item in any given column as the column size for the appropriate type. If you
3589 know you will be adding larger items to that column then you should manually adjust the column sizes accordingly. This is done for the sake of efficiency.
3590 </p>
3592 <!-- End: Import type-detection limitations -->
3594 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3597 <a href="#faq4_1">4.1 I'm an <abbr title="Internet service provider">ISP</abbr>. Can I setup one central copy of phpMyAdmin or do I
3598 need to install it for each customer.
3599 </a></h4>
3600 <p>
3601 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3602 your users. The development of this feature was kindly sponsored by
3603 NetCologne GmbH.
3604 This requires a properly setup MySQL user management and phpMyAdmin
3605 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3607 </p>
3611 access.
3612 </a></h4>
3613 <p>
3614 This depends on your system.<br />
3615 If you're running a server which cannot be accessed by other people, it's
3616 sufficient to use the directory protection bundled with your webserver
3618 If other people have telnet access to your server, you should use
3619 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3620 <br /><br />
3621 Suggestions:
3622 </p>
3623 <ul>
3624 <li>
3626 </li>
3627 <li>
3628 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3629 is a user whose password is only known to you, and apache is the
3630 group under which Apache runs.
3631 </li>
3632 <li>
3633 Follow security recommendations for PHP and your webserver.
3634 </li>
3635 </ul>
3640 </a></h4>
3641 <p>
3646 </p>
3649 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3650 authentication.
3651 </a></h4>
3655 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3656 and/or
3658 are wrong.</li>
3660 <li>You have already setup a security mechanism for the
3661 phpMyAdmin-directory, eg. a <a href="#glossary"><i>.htaccess</i></a> file. This would interfere with
3662 phpMyAdmin's authentication, so remove it.</li>
3663 </ul>
3670 and put the privileges you want. For example,
3672 would let a user create/manage his/her database(s).</p>
3677 <p> If you have existing rules from an old <a href="#glossary"><i>.htaccess</i></a> file, you can take them
3680 be a major benefit here if your installation is suited to using it. Then
3681 you can just add those updated lines into the
3685 <p> If you want a pre-made sample, you can try this fragment. It stops the
3686 'root' user from logging in from any networks other than the private
3689 <pre>
3690 //block root from logging in except from the private networks
3691 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3692 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3693 'deny root from all',
3694 'allow root from localhost',
3698 );
3699 </pre>
3704 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3705 different than the one set in your
3707 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3708 while a domain name is defined in the config file.</p>
3713 <p>When starting phpMyAdmin, you can use the <tt>db</tt>, <tt>pma_username</tt>, <tt>pma_password</tt> and <tt>server</tt> parameters. This last one can contain either the numeric host index (from <tt>$i</tt> of the configuration file) or one of the host names present in the configuration file. Using <tt>pma_username</tt> and <tt>pma_password</tt> has been tested along with the usage of 'cookie' <tt>auth_type</tt>.</p>
3719 when trying to create a table with more than 14 columns.
3720 </a></h4>
3721 <p>
3722 We could reproduce this problem only under Win98/98SE. Testing under
3723 WinNT4 or Win2K, we could easily create more than 60 columns.
3724 <br />
3725 A workaround is to create a smaller number of columns, then come back to
3726 your table properties and add the other columns.
3727 </p>
3731 <p>
3732 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3733 with each script/website that use forms.<br />
3734 Upgrade or downgrade your Xitami server.
3735 </p>
3738 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3739 <p>
3740 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3741 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3742 don't seem to work.<br />
3744 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3745 the user's temporary directory, so they must be moved before closing
3746 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3749 </p>
3753 Explorer never stores the cookies.
3754 </a></h4>
3755 <p>
3756 MS Internet Explorer seems to be really buggy about cookies, at least till
3757 version 6.
3758 </p>
3762 rows.
3763 </a></h4>
3764 <p>
3766 </p>
3769 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3770 when trying to modify a row in a table with many columns, or with a text
3771 column
3772 </a></h4>
3773 <p>
3774 Your table neither have a primary key nor an unique one, so we must use a
3775 long <abbr title="Uniform Resource Locator">URL</abbr> to identify this row. There is a limit on the length of the <abbr title="Uniform Resource Locator">URL</abbr> in
3776 those browsers, and this not happen in Netscape, for example. The
3777 workaround is to create a primary or unique key, or use another browser.
3778 <br />
3779 </p>
3783 page.
3784 </a></h4>
3785 <p>
3786 Some browsers support right-clicking into the frame you want to refresh,
3787 just do this in the right frame.<br />
3788 </p>
3792 query box.
3793 </a></h4>
3794 <p>
3795 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3796 Mozilla versions.<br />
3797 </p>
3801 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3802 </a></h4>
3803 <p>
3804 This is a Mozilla bug (see bug #26882 at
3806 </p>
3811 </a></h4>
3812 <p>
3813 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3814 data in octet-stream mode. Since we can't detect the specific Netscape
3815 version, we cannot workaround this bug.
3816 </p>
3820 wrong.</a></h4>
3822 <p> Please ensure that you have set your browser's character set to the one of the
3823 language file you have selected on phpMyAdmin's start page.
3824 Alternatively, you can try the auto detection mode that is supported by the
3825 recent versions of the most browsers.</p>
3828 <a href="#faq5_12">5.12 <acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X: Safari browser changes special characters to
3831 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3832 Netscape and Mozilla do not have this problem.</p>
3835 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3836 I cannot manage two servers: I log in to the first one, then the other one,
3837 but if I switch back to the first, I have to log in on each operation.</a></h4>
3843 but nothing happens after that, only a blank screen.</a></h4>
3854 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3859 address and you are starting
3861 containing a domain name, or the reverse situation.</li>
3862 <li>Security settings in IE and/or Microsoft Security Center are
3863 too high, thus blocking scripts execution.</li>
3864 <li>The Windows Firewall is blocking Apache and MySQL. You must
3868 </ul>
3871 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3872 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3873 installed in their Firefox is causing the problem.</p>
3877 clause is generated when I browse a table.</a></h4>
3878 <p> This happens only when both of these conditions are met: using the
3885 <p> Issues have been reported with some combinations of browser extensions.
3886 To troubleshoot, disable all extensions then clear your browser cache
3887 to see if the problem goes away.</p>
3894 </a></h4>
3895 <p>
3896 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3897 specifying a wrong column-type.<br />
3898 Common errors include:
3899 </p>
3900 <ul>
3903 </ul>
3904 <p>
3905 Also, look at the syntax chapter in the MySQL manual to confirm that your
3906 syntax is correct.
3907 </p>
3911 columns and
3912 phpMyAdmin generates only one index with those two columns.
3913 </a></h4>
3914 <p>
3915 This is the way to create a multi-columns
3916 index. If you want two indexes, create the first one when creating the
3917 table, save, then display the table properties and click the Index link to
3918 create the other index.
3919 </p>
3923 <p>
3924 Since version 2.2.3, you have a checkbox for each column that can be null.
3926 column's value. Since version 2.5.5, you have to use the checkbox to get
3928 a literal NULL in the column, and not a NULL value (this works in PHP4).
3929 </p>
3934 <p> Click on a database or table name in the left frame, the properties will be
3936 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3937 statements that can be used to recreate your database/table.
3938 <br /><br />
3940 transmit the resulting dump to your station. Depending on your PHP
3941 configuration, you will see options to compress the dump. See also the
3943 configuration variable.<br /><br />
3946 this document.</p>
3951 </a></h4>
3953 <p> Click on a database name in the left frame, the properties will be
3955 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3957 the path to your dump filename, or use the Browse button. Then click Go.
3958 <br /><br />
3960 that you upgrade to take advantage of the new features.
3961 <br /><br />
3963 in this document.
3964 </p>
3969 <p> Here is an example with the tables persons, towns and countries, all
3971 table, create it as explained in the configuration section. Then create the
3972 example tables:</p>
3974 <pre>
3975 CREATE TABLE REL_countries (
3976 country_code char(1) NOT NULL default '',
3977 description varchar(10) NOT NULL default '',
3978 PRIMARY KEY (country_code)
3979 ) TYPE=MyISAM;
3981 INSERT INTO REL_countries VALUES ('C', 'Canada');
3983 CREATE TABLE REL_persons (
3984 id tinyint(4) NOT NULL auto_increment,
3985 person_name varchar(32) NOT NULL default '',
3987 country_code char(1) NOT NULL default '',
3988 PRIMARY KEY (id)
3989 ) TYPE=MyISAM;
3991 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3992 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3994 CREATE TABLE REL_towns (
3996 description varchar(30) NOT NULL default '',
3997 PRIMARY KEY (town_code)
3998 ) TYPE=MyISAM;
4000 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
4001 INSERT INTO REL_towns VALUES ('M', 'Montréal');
4002 </pre>
4008 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
4012 </ul>
4020 <li>In the columns row, choose persons.person_name and click the
4022 <li>Do the same for towns.description and countries.descriptions in the
4025 the correct joins have been generated</li>
4027 </ul>
4031 <p>
4032 Starting from the previous example, create the pma_table_info as explained
4033 in the configuration section, then browse your persons table,
4034 and move the mouse over a town code or country code.
4035 <br /><br />
4036 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
4037 enables: drop-down list of possible values.
4038 </p>
4041 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
4042 <p>
4045 <br /><br />
4046 Then you need to think about your schema layout. Which tables will go on
4047 which pages?
4048 </p>
4049 <ul>
4055 page and click Go. If you like, you
4057 linked tables onto the new page.</li>
4058 <li>Select the name of the new page (making sure the Edit radio button
4059 is selected) and click Go.</li>
4061 Coordinates are relative; your diagram will
4062 be automatically scaled to fit the page. When initially placing tables
4063 on the page, just pick any coordinates -- say, 50x50. After clicking
4065 position the element correctly.</li>
4067 first be sure to click the Save
4068 button beneath the list of tables and coordinates, to save any changes
4069 you made there. Then scroll all the way down, select the
4071 you want, and click Go.</li>
4072 <li>Internet Explorer for Windows may suggest an incorrect filename when
4077 browsers on Windows, do not have this problem.</li>
4078 </ul>
4082 columns!</a></h4>
4084 <p> No, it's MySQL that is doing
4090 underscores in the database name?</a></h4>
4092 <p> If you do not put a backslash before the underscore, this is a wildcard
4095 john2db ...<br /><br />
4097 If you put a backslash before the underscore, it means that the database
4098 name will have a real underscore.</p>
4102 statistics pages?</a></h4>
4113 if it already exists during the import. It does NOT drop the table after
4114 your export, it only affects the import file.</li>
4116 Otherwise, you may get an error if the table name exists but has a
4117 different structure.</li>
4119 (if any) will be included in backup.</li>
4121 column and table names formed with special characters are protected.</li>
4123 types set in the pmadb in the dump as
4125 </li>
4126 </ul>
4131 command, for better documentation (but resulting file is bigger).</li>
4133 once the INSERT verb and the table name.</li>
4136 </li>
4138 more info is provided in the
4140 but basically with this selected, invalid values are adjusted and
4141 inserted rather than causing the entire statement to fail.</li>
4142 </ul>
4146 in its name.</a></h4>
4149 is the normal way to reference a database and table name. Worse, MySQL
4150 will usually let you create a database with a dot, but then you cannot
4151 work with it, nor delete it.</p>
4157 <p>
4158 To use SQL Validator, you need PHP with
4164 module.
4165 </p>
4167 <p>
4173 usage.
4174 </p>
4176 <p>
4177 If you use the Validator, you should be aware that any
4179 submit will be stored anonymously (database/table/column names,
4180 strings, numbers replaced with generic values). The Mimer
4183 We utilize it as free SOAP service.
4184 </p>
4188 it, but MySQL says "BLOB column '...' used in key specification without
4191 <p> The right way to do this, is to create the column without any indexes,
4193 dialog. On this page, you will be able to choose your BLOB column, and
4194 set a size to the index, which is the condition to create an index on
4195 a BLOB column.</p>
4199 editing fields?</a></h4>
4201 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4202 with many editing fields (table structure changes, row editing, etc.).</p>
4206 WTF is this feature then useful for?</a></h4>
4208 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4209 on them. Otherwise you could just put a comment on the column. Because entering
4210 your own mimetype will cause serious syntax checking issues and validation,
4211 this introduces a high-risk false-user-input situation. Instead you have to
4212 initialize mimetypes using functions or empty mimetype definitions.<br />
4213 Plus, you have a whole overview of available mimetypes. Who knows all those
4214 mimetypes by heart so he/she can enter it at will?</p>
4218 can't I see any bookmarks below the query box? What is this variable for?
4219 </a></h4>
4221 <p> Any query you have executed can be stored as a bookmark on the page where the
4222 results are displayed. You will find a button labeled 'Bookmark this query'
4223 just at the end of the page.<br />
4224 As soon as you have stored a bookmark, it is related to the database you run
4225 the query on. You can now access a bookmark dropdown on each page, the query
4226 box appears on for that database.<br /><br />
4228 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4232 aware of that you HAVE to create a valid query, otherwise your query won't be
4233 even able to be stored in the database.<br />
4235 for your query will remain the way it is, but will be stripped of the /**/
4236 chars. So you can use:<br /><br />
4240 which will be expanded to<br /><br />
4244 in your query, where VARIABLE is the string you entered in the input box. If
4245 an empty string is provided, no replacements are made.<br /><br />
4247 A more complex example. Say you have stored this query:<br /><br />
4249 <br /><br />
4252 the full query will be:<br /><br />
4255 <br /><br />
4257 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4259 spaces inserted there
4260 will be later also inserted as spaces in your query and may lead to unexpected
4261 results especially when
4263 Your initial query which is going to be stored as a bookmark has to yield at
4264 least one result row so
4265 you can store the bookmark. You may have that to work around using well
4269 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4270 include exported table?</a></h4>
4272 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4273 document should look like following one (assuming you have table
4276 <pre>
4277 \documentclass{article} % or any class you want
4278 \usepackage{longtable} % for displaying table
4279 \begin{document} % start of document
4280 \include{table} % including exported table
4281 \end{document} % end of document
4282 </pre>
4286 access them.
4287 </a></h4>
4289 <p> You have one of these global privileges: CREATE
4290 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4291 enable users to see all the database names.
4294 So if your users do not need those privileges, you can remove them and their
4295 databases list will shorten.</p>
4299 possible values for a column, based on some foreign table?</a></h4>
4301 <p> You have to setup appropriate links between the tables, and also
4305 foreign table, a drop-down list of values will be available.
4306 You will see two lists of values, the first list containing the key
4307 and the display column, the second list containing the display column
4308 and the key. The reason for this is to be able to type the first
4309 letter of either the key or the display column.<br /><br />
4311 For 100 values or more, a distinct window will appear, to browse foreign
4312 key values and choose one. To change the default limit of 100, see
4313 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4317 automatically when entering Browse mode for a table?</a></h4>
4319 <p> Yes. If a bookmark has the same label as a table name and it's not a public bookmark, it will be executed.
4320 </p>
4325 <p> You can use
4327 which works out of the box.<br />
4328 Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel
4329 version 97 and newer was dropped.
4330 </p>
4334 what happens to my column comments stored in pmadb?</a></h4>
4336 <p> Automatic migration of a table's pmadb-style column comments to the native
4337 ones is done whenever you enter Structure page for this table.</p>
4342 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4343 <ul>
4346 later)</li>
4349 </ul>
4353 <ol>
4354 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4355 <li>Ensure that your target table is under the <tt>PBXT</tt> storage engine and has a <tt>LONGBLOB</tt> column (which must be nullable if you want to remove the BLOB reference from it).</li>
4356 <li>When you insert or update a row in this table, put a checkmark on the "Upload to BLOB repository" optional choice; otherwise, the upload will be done directly in your LONGBLOB column instead of the repository.</li>
4357 <li>Finally when you browse your table, you'll see in your column a link to stream your data, for example "View image". A header containing the correct MIME-type will be sent to your browser; this MIME-type was stored at upload time.</li>
4358 </ol>
4363 <p> Click the first row of the range, hold the shift key and click the last row of the range. This works everywhere you see rows, for example in Browse mode or on the Structure page.</p>
4369 <p>
4370 In all places where phpMyAdmin accepts format strings, you can use
4373 expanded variables depend on a context (for example, if you haven't chosen a
4374 table, you can not get the table name), but the following variables can be used:
4375 </p>
4376 <dl>
4382 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4393 </dl>
4398 <p>
4399 By clicking on the button 'toggle scratchboard' on the page
4400 where you edit x/y coordinates of those elements you can activate a
4401 scratchboard where all your elements are placed. By clicking on an
4402 element, you can move them around in the pre-defined area and the x/y
4403 coordinates will get updated dynamically. Likewise, when entering a
4404 new position directly into the input field, the new position in the
4405 scratchboard changes after your cursor leaves the input field.
4406 </p>
4407 <p>
4408 You have to click on the 'OK'-button below the tables to save the new
4409 positions. If you want to place a new element, first add it to the
4410 table of elements and then you can drag the new element around.
4411 </p>
4412 <p>
4413 By changing the paper size and the orientation you can change the size
4414 of the scratchboard as well. You can do so by just changing the
4415 dropdown field below, and the scratchboard will resize automatically,
4416 without interfering with the current placement of the elements.
4417 </p>
4418 <p>
4419 If ever an element gets out of range you can either enlarge the paper
4420 size or click on the 'reset' button to place all elements below each
4421 other.
4422 </p>
4427 <p> Not every table can be put to the chart. Only tables with one, two or three columns can be visualised as a chart. Moreover the table must be in a special format for chart script to understand it. Currently supported formats can be found in the <a href="http://wiki.phpmyadmin.net/pma/Charts#Data_formats_for_query_results_chart">wiki</a>.</p>
4432 <p>
4433 An ESRI Shapefile is actually a set of several files, where .shp file contains
4434 geometry data and .dbf file contains data related to those geometry data.
4435 To read data from .dbf file you need to have PHP compiled with the dBase extension
4436 (--enable-dbase). Otherwise only geometry data will be imported.
4437 </p>
4440 <ul>
4441 <li>
4442 <p>
4443 Configure upload directory with
4445 .shp and .dbf files with the same filename and chose the .shp file from the import page.
4446 </p>
4447 </li>
4448 <li>
4449 <p>
4450 Create a Zip archive with .shp and .dbf files and import it. For this to work,
4453 </p>
4456 <pre>
4457 cd phpMyAdmin
4458 mkdir tmp
4459 chmod o+rwx tmp
4460 </pre>
4461 </li>
4462 </ul>
4468 <img src="themes/original/img/pmd/help_relation.png" width="100" height="100" alt="[relation icon]" /><br />
4469 The display column is shown in pink. To set/unset a column as the display column, click the "Choose column to display" icon, then click on the appropriate column name.</p>
4474 <p> The Zoom search feature is an alternative to table search feature. It allows you to explore
4475 a table by representing its data in a scatter plot. You can locate this feature by selecting
4476 a table and clicking the 'Search' tab. One of the sub-tabs in the 'Table Search' page is
4477 'Zoom Search'. <br/><br/>
4481 for example, id and town_code. The id values will be represented on one axis and town_code
4482 values on the other axis. Each row will be represented as a point in a scatter plot based
4483 on its id and town_code. You can include two additional search criteria apart from the two
4484 fields to display.<br/><br/>
4486 You can choose which field should be displayed as label for each point. If a display
4489 You can also select the maximum number of rows you want to be displayed in the plot by
4490 specifing it in the 'Max rows to plot' field. Once you have decided over your criteria,
4491 click 'Go' to display the plot.<br/><br/>
4493 After the plot is generated, you can use the mousewheel to zoom in and out of the plot.
4494 In addition, panning feature is enabled to navigate through the plot. You can zoom-in to
4495 a certail level of detail and use panning to locate your area of interest. Clicking on a
4496 point opens a dialogue box, displaying field values of the data row represented by the point.
4497 You can edit the values if required and click on submit to issue an update query. Basic
4498 instructions on how to use can be viewed by clicking the 'How to use?' link located just above
4499 the plot.</p>
4506 <p> Our Bug Tracker is located at
4508 under the Bugs section.<br /><br />
4510 But please first discuss your bug with other users:<br />
4512 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4513 </p>
4517 existing language, where do I start?</a></h4>
4519 <p> Always use latest Git version of the po file to translate. You can optionally
4521 server</a> where you can also get the latest po files and merge them
4522 with your translations. For creating a new translation simply use
4526 to do this) or ask on the mailing list to add the translation to the web
4527 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4528 </p>
4529 <p>
4530 Please note that we try not to use HTML entities like &eacute; in
4531 the translations, since we define the right character set in the file.
4532 With HTML entities, the text on JavaScript messages would not
4533 display correctly.
4534 However there are some entities that need to be there: quotes,
4535 non-breakable spaces, ampersands, less than, greater than.
4536 </p>
4537 <p>
4538 You can then put your translations, as a zip file to avoid losing special
4539 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4540 </p>
4541 <p>
4542 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4543 list, because this is where we ask for translations of new messages.
4544 </p>
4546 <p>
4547 Documentation is being translated using po4a and gettext (see
4549 for existing translations). To start, checkout
4550 <a href="http://github.com/phpmyadmin/localized_docs/tree/master/po"><code>localized_docs/po</code></a>
4551 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4552 and translate it online. If your language is missing, just contact
4554 you prefer to directly translate the po files, please put updated ones into our
4555 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4556 </p>
4560 phpMyAdmin. How should I proceed?</a></h4>
4562 <p>We welcome every contribution to the development of phpMyAdmin.
4563 You can check out all the possibilities to contribute in the
4564 <a href="http://www.phpmyadmin.net/home_page/improve.php">contribute section on our website</a>.
4565 </p>
4570 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4572 <p> Please refer to
4573 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4574 </p>
4579 <p> If you use Apache web server, phpMyAdmin exports information about
4580 authentication to the Apache environment and it can be used in Apache logs.
4581 Currently there are two variables available:
4582 </p>
4583 <dl>
4585 <dd>User name of currently active user (he does not have to be logged
4586 in).</dd>
4593 </dl>
4594 <p>
4596 </p>
4597 <pre>
4600 </pre>
4601 <p>
4602 You can then use any log analyzing tools to detect possible break-in
4603 attempts.
4604 </p>
4610 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4611 It allows you to connect to local as well as remote servers. This requires you to enter
4612 server host name, username, password, port and the name of the database. Therefore you can
4613 now synchronize your databases placed on the same server or some remote server.
4614 </p>
4616 <p>
4617 This feature is helpful for developers who need to replicate their
4618 database’s structure as well as data. Moreover, this feature not only
4619 helps replication but also facilitates the user to keep his/her database
4620 in sync with another database. Other than the full database, certain
4621 tables of the databases can also be synchronized.
4622 </p>
4624 <p>
4625 You need to fill in the host name of the server, the username and
4626 password of an user account already there in MySQL. Port is by default
4627 populated with 3306 (MySQL default port). Then the name of the database
4628 should be mentioned at the end. All the information other than the port
4629 needs to be filled explicitly for the source as well as target servers.
4630 </p>
4632 <p>
4633 After successfully passing through the authentication phase, the source and
4634 target database table names will be displayed. It will be a tabular
4635 representation.
4636 </p>
4638 <p>
4639 On the left, are listed the source database table names. Some of the
4641 are only present in source database and they need to be added to the
4642 target database in order to synchronize the target database. The tables
4644 target database.
4645 </p>
4647 <p>
4648 On the right, are listed the target database table names. There are few
4650 means that these tables are to be created in target database in order to
4651 synchronize target database with source database. Some table names
4653 only present in target database and they will remain unchanged in the
4654 target database. The column in the middle shows the difference between
4655 the source and target corresponding tables.
4656 </p>
4658 <p>
4660 letters, indicating that either Structure or Data are not up to date. By
4661 clicking on them, they will turn grey, what means that they will be synchronized.
4662 </p>
4666 tables?</a></h4>
4668 <p>
4669 Yes. This aspect of synchronization is currently limited to small tables, and they
4670 must have a primary key.
4671 </p>
4673 <!-- DEVELOPERS -->
4676 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4677 great features have been written by other people and you too can help to
4678 make phpMyAdmin a useful tool.</p>
4680 <p>You can check out all the possibilities to contribute in the
4681 <a href="http://www.phpmyadmin.net/home_page/improve.php">contribute section on our website</a>.
4682 </p>
4686 <pre>
4697 </pre>
4699 <p>
4700 This program is free software; you can redistribute it and/or modify
4701 it under the terms of the GNU General Public License version 2,
4702 as published by the Free Software Foundation.
4703 </p>
4705 <p>
4706 This program is distributed in the hope that it will be useful,
4707 but WITHOUT ANY WARRANTY; without even the implied warranty of
4708 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4709 GNU General Public License for more details.
4710 </p>
4712 <p>
4713 You should have received a copy of the GNU General Public License
4714 along with this program. If not, see <a href="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</a>.
4715 </p>
4717 <!-- CREDITS -->
4722 <ul>
4725 <ul>
4728 </ul></li>
4731 <ul>
4736 </ul></li>
4739 <ul>
4744 </ul></li>
4747 <ul>
4749 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4750 generate XHTML1.0 and CSS2 compliant codes</li>
4753 </ul></li>
4756 <ul>
4764 </ul></li>
4767 <ul>
4772 </ul></li>
4775 <ul>
4778 </ul></li>
4781 <ul>
4783 </ul></li>
4786 <ul>
4789 </ul></li>
4792 <ul>
4796 </ul></li>
4799 <ul>
4802 </ul></li>
4805 <ul>
4812 </ul></li>
4815 <ul>
4819 </ul></li>
4822 <ul>
4828 </ul></li>
4831 (http://sf.net/projects/phpmysqlformgen/)
4832 <ul>
4834 </ul></li>
4837 <ul>
4839 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4844 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4848 </ul></li>
4851 <ul>
4853 </ul></li>
4856 <ul>
4858 </ul></li>
4861 <ul>
4863 </ul></li>
4866 <ul>
4867 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4868 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4869 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4870 </ul></li>
4873 <ul>
4875 </ul></li>
4878 <ul>
4880 </ul></li>
4883 <ul>
4885 </ul></li>
4888 <ul>
4891 </ul></li>
4893 <li>Nicola Asuni (Tecnick.com)
4894 <ul>
4897 </ul></li>
4900 <ul>
4903 </ul></li>
4906 <ul>
4908 </ul></li>
4911 <ul>
4914 </ul></li>
4916 <li>Ivan A Kirillov
4917 <ul>
4919 </ul></li>
4922 <ul>
4924 </ul></li>
4927 <ul>
4931 </ul></li>
4934 <ul>
4936 </ul></li>
4939 <ul>
4941 </ul></li>
4944 <ul>
4946 </ul></li>
4949 <ul>
4951 </ul></li>
4954 <ul>
4956 </ul></li>
4959 <ul>
4963 </ul></li>
4966 <ul>
4968 </ul></li>
4971 <ul>
4973 </ul></li>
4975 <li>Barrie Leslie
4976 <ul>
4978 </ul></li>
4981 <ul>
4983 </ul></li>
4986 <ul>
4989 </ul></li>
4991 </ul>
4993 <p>
4994 And also to the following people who have contributed minor changes,
4995 enhancements, bugfixes or support for a new language since version 2.1.0:
4996 </p>
4998 <p>
4999 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
5000 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
5001 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
5002 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
5004 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
5005 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
5006 Luís V., Martijn W. van der Lee,
5007 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
5009 </p>
5014 <p>
5015 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
5016 to create a web-based interface to MySQL using PHP3. Although I have not
5017 used any of his source-code, there are some concepts I've borrowed from
5018 him. phpMyAdmin was created because Peter told me he wasn't going to
5019 further develop his (great) tool.
5020 </p>
5021 <p>
5022 Thanks go to
5023 </p>
5024 <ul>
5026 code for the check when dropping a table or database. He also suggested
5027 that you should be able to specify the primary key on tbl_create.php3. To
5028 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
5029 well as a bug-report. Plus many smaller improvements.
5030 </li>
5032 were introduced in 1.3.0 (including quite significant ones like the
5033 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
5034 bug-fixes and help.
5035 </li>
5037 language-independent by outsourcing the strings to a separate file. He
5038 also contributed the French translation.
5039 </li>
5041 tbl_select.php3, a feature to display only some columns from a table.
5042 </li>
5044 functions in tbl_change.php3. He also added the
5046 </li>
5048 servers and is a regular contributor for bug-fixes.
5049 </li>
5051 features for 2.0.6.
5052 </li>
5053 </ul>
5054 <p>
5055 The following people have contributed minor changes, enhancements, bugfixes
5056 or support for a new language:
5057 </p>
5058 <p>
5059 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
5060 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
5061 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
5062 G. Wieggers.
5063 </p>
5064 <p>
5065 And thanks to everyone else who sent me email with suggestions, bug-reports
5066 and or just some feedback.
5067 </p>
5073 <ul>
5075 - the default name of Apache's directory-level configuration file.</li>
5079 - a software application that enables a user to display and interact with
5080 text, images, and other information typically located on a web page at a
5081 website on the World Wide Web.</li>
5083 - a free software/open source data compression algorithm and program
5084 developed by Julian Seward.</li>
5086 - an important World Wide Web technology that enables a client web browser
5087 to request data from a program executed on the Web server.</li>
5089 - a log or record of changes made to a project.</li>
5091 - a computer system that accesses a (remote) service on another computer
5092 by some kind of network.</li>
5094 - a set of data values of a particular simple type, one for each row of
5095 the table.</li>
5097 - a packet of information sent by a server to a World Wide Web browser
5098 and then sent back by the browser each time it accesses that server.</li>
5100 - Comma-separated values</li>
5103 - an organized collection of data.</li>
5106 - a PHP module that extends PHP with additional functionality.</li>
5108 - a list of commonly asked question and there answers.</li>
5110 - one part of divided data/columns.</li>
5112 - a column or group of columns in a database row that point to a key
5113 column or group of columns forming a key of another database row in some
5114 (usually different) table.</li>
5116 - the free PDF library</li>
5118 GD Graphics Library</a> - a library by Thomas Boutell and others for
5119 dynamically manipulating images.</li>
5122 - gzip is short for GNU zip, a GNU free software file compression
5123 program.</li>
5125 - any machine connected to a computer network, a node that has a hostname.</li>
5127 - the unique name by which a network attached device is known on a network.</li>
5129 (HyperText Transfer Protocol)</a>
5130 - the primary method used to transfer or convey information on the World
5131 Wide Web.</li>
5134 additional security measures.</li>
5135 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5136 - a set of Internet-based services for servers using Microsoft Windows.</li>
5138 - a feature that allows quick access to the rows in a table.</li>
5140 - a data-oriented protocol used by source and destination hosts for
5141 communicating data across a packet-switched internetwork.</li>
5143 - a unique number that devices use in order to identify and communicate
5144 with each other on a network utilizing the Internet Protocol standard.</li>
5146 (Internet Server Application Programming Interface)</a>
5147 - the API of Internet Information Services (IIS).</li>
5149 - a business or organization that offers users access to the Internet and related services.</li>
5151 - a most commonly used standard method of lossy compression for
5152 photographic images.</li>
5158 - line of personal computers is designed, developed, manufactured, and
5159 marketed by Apple Computer.</li>
5160 <li><a id="glossar_mac_os_x" href="http://www.wikipedia.org/wiki/Mac_OS_X"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>
5161 - the operating system which is included with all currently shipping Apple
5162 Macintosh computers in the consumer and professional markets.</li>
5164 - a cryptographic library.</li>
5166 - the MCrypt PHP extension.</li>
5167 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5168 - an Internet Standard for the format of e-mail.</li>
5170 - some sort of extension for the Apache Webserver.</li>
5172 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5173 Management System (DBMS).</li>
5175 - the improved MySQL client PHP extension.</li>
5177 - the MySQL client PHP extension.</li>
5179 - open standard for office documents.</li>
5180 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5181 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5183 (Portable Document Format)</a>
5184 - a file format developed by Adobe Systems for representing two
5185 dimensional documents in a device independent and resolution independent
5186 format.</li>
5188 - the PHP Extension and Application Repository.</li>
5190 - the perl-compatible regular expression functions for PHP</li>
5192 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5193 programming language used mainly for developing server-side applications
5194 and dynamic web content, and more recently, a broader range of software
5195 applications.</li>
5197 - a connection through which data is sent and received.</li>
5199 - Request for Comments (RFC) documents are a series of memoranda
5200 encompassing new research, innovations, and methodologies applicable to
5201 Internet technologies.</li>
5205 - represents a single, implicitly structured data item in a table.</li>
5207 - a computer system that provides services to other computing
5208 systems over a network.</li>
5209 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5210 - handlers for different table types</li>
5212 - a form of inter-process communication.</li>
5214 Sockets Layer)</a>
5215 - a cryptographic protocol which provides secure communication on the Internet.</li>
5217 - a subroutine available to applications accessing a relational database system</li>
5219 - Structured Query Language</li>
5221 - a set of data elements (cells) that is organized, defined and stored as
5222 horizontal rows and vertical columns where each item can be uniquely
5223 identified by a label or key or by it?s position in relation to other items.</li>
5226 - a type of archive file format: the Tape ARchive format.</li>
5228 - one of the core protocols of the Internet protocol suite.</li>
5230 - a procedural code that is automatically executed in response to
5231 certain events on a particular table or view in a database</li>
5235 - a sequence of characters, conforming to a standardized format, that is
5236 used for referring to resources, such as documents and images on the
5237 Internet, by their location.</li>
5239 - A computer (program) that is responsible for accepting HTTP requests
5240 from clients and serving them Web pages.</li>
5242 - a W3C-recommended general-purpose markup language for creating
5243 special-purpose markup languages, capable of describing many different
5244 kinds of data.</li>
5246 - a popular data compression and archival format.</li>
5248 - an open-source, cross-platform data compression library by Jean-loup
5249 Gailly and Mark Adler.</li>
5250 </ul>
5251 </div>
5254 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5257 <li class="last">Valid <a href="http://validator.w3.org/check/referer">HTML</a> and <a href="http://jigsaw.w3.org/css-validator/check/referer">CSS</a></li>
5258 </ul>
5260 </body>
5261 </html>