| blob | c99c3de858e446ac339a45cfe4247ac5acea6797 |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 and the Standard PHP Library (SPL) extension.
63 </li>
65 <li>You need GD2 support in PHP to display inline
67 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
198 provided for those who prefer a graphical installation. Creating a
199 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
200 <ul><li>To manually create the file, simply use your text editor to
203 file) in the main (top-level) phpMyAdmin directory (the one
207 default value is okay for a particular setting, there is no
209 few directives to get going, a simple configuration may look
210 like this:
211 <pre>
212 <?php
213 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
215 $i=0;
216 $i++;
217 $cfg['Servers'][$i]['auth_type'] = 'cookie';
218 ?>
219 </pre>
220 Or, if you prefer to not be prompted every time you log in:
221 <pre>
222 <?php
224 $i=0;
225 $i++;
226 $cfg['Servers'][$i]['user'] = 'root';
227 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
228 ?>
229 </pre>
230 For a full explanation of possible configuration values, see the
236 directory. This is a security measure. On a Linux/Unix system you
237 can use the following commands:
238 <pre>
239 cd phpMyAdmin
240 mkdir config # create directory for saving
241 chmod o+rw config # give it world writable permissions
242 </pre>
243 And to edit an existing configuration, copy it over first:
244 <pre>
245 cp config.inc.php config/ # copy current configuration for editing
246 chmod o+w config/config.inc.php # give it world writable permissions
247 </pre>
248 On other platforms, simply create the folder and ensure that your
257 the webserver does not have the proper permissions you may see the
259 config/</tt> directory exists and has the proper permissions -
261 and upload (via FTP or some similar means) to the proper location.<br /><br />
263 Once the file has been saved, it must be moved out of the <tt>
264 config/</tt> directory and the permissions must be reset, again
265 as a security measure:
266 <pre>
267 mv config/config.inc.php . # move file to current directory
268 chmod o-rw config.inc.php # remove world read and write permissions
269 </pre>
270 Now the file is ready to be used. You can choose to review or edit
271 the file with your favorite editor, if you prefer to set some
272 advanced options which the setup script does not provide.</li></ul></li>
273 <li>If you are using the
275 protect the phpMyAdmin installation directory because using
276 config does not require a user to
277 enter a password to access the phpMyAdmin installation. Use of an alternate
278 authentication method is recommended, for example with
286 in your browser. phpMyAdmin should now display a welcome screen
287 and your databases, or a login dialog if using
289 authentication mode.</li>
291 webserver configuration. For Apache you can use supplied .htaccess file
292 in that folder, for other webservers, you should configure this yourself.
293 Such configuration prevents from possible path exposure and cross side
294 scripting vulnerabilities that might happen to be found in that code.</li>
295 </ol>
299 <p> For a whole set of new features (bookmarks, comments,
302 transformation, etc.) you need to create a set of special tables. Those
303 tables can be located in your own database, or in a central database for a
304 multi-user installation (this database would then be accessed by the
305 controluser, so no other user should have rights to it).</p>
315 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
316 that you may need special (administrator) privileges to create the database
317 and tables, and that the script may need some tuning, depending on the
318 database name.</p>
323 section</a>. You will also need to have a controluser with the proper rights
330 unpacked one. Configuration files from very old versions (2.3.0 or before) may
331 require some tweaking as some options have been changed or removed.
333 statement that you might find near the end of your configuration file.</p>
337 is version-specific.</p>
340 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
341 you should run the SQL script found in
348 where you want to give users access to their own database and don't want
349 them to play around with others.<br />
350 Nevertheless be aware that MS Internet Explorer seems to be really buggy
352 in this area!<br />
355 that your user/password pair are not in clear in the configuration file.
356 </li>
359 authentication modes are more secure: the MySQL login information does
360 not need to be set in the phpMyAdmin configuration file (except possibly
362 However, keep in mind that the password travels in plain text, unless
363 you are using the HTTPS protocol.<br />
364 In cookie mode, the password is stored, encrypted with the blowfish
365 algorithm, in a temporary cookie.</li>
377 file under the
379 $cfg['Servers'][$i]['controluser']</a></tt> and
384 only an example: use something else in your file!</b> Input these
385 statements from the phpMyAdmin SQL Query window or mysql command–line
386 client.<br />
388 if it's not the same as the MySQL server's one.
390 <pre>
391 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
392 GRANT SELECT (
393 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
394 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
395 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
396 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
397 Execute_priv, Repl_slave_priv, Repl_client_priv
398 ) ON mysql.user TO 'pma'@'localhost';
399 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
400 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
401 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
402 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
404 If you want to use the many new relation and bookmark features:
406 <pre>
408 </pre>
414 on a set of particular databases. Normally you shouldn't give global
415 privileges to an ordinary user, unless you understand the impact of those
416 privileges (for example, you are creating a superuser).<br />
420 <pre>
421 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
422 </pre>
424 What the user may now do is controlled entirely by the MySQL user
425 management system.<br />
427 authentication mode, you don't need to fill the user/password fields
429 array.</li>
430 </ul>
435 method and allows you to log in as any valid MySQL user.</li>
436 <li>Is supported with most PHP configurations. For
449 mode.</li>
450 </ul>
454 <ul><li>You can use this method as a replacement for the
456 (for example, if you're running
458 <li>Obviously, the user must enable cookies in the browser, but this is
459 now a requirement for all authentication modes.</li>
460 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
461 with the same username.</li>
462 <li>If you want to log in to arbitrary server see
467 not required.</li>
468 </ul>
472 <ul><li>This mode is a convenient way of using credentials from another
473 application to authenticate to phpMyAdmin.</li>
474 <li>The other application has to store login information into
475 session data.</li>
477 section.</li>
478 </ul>
481 <ul><li>This mode is the less secure one because it requires you to fill the
483 $cfg['Servers'][$i]['user']</a> and
485 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
486 can read your config.inc.php can discover your username and password).
487 <br />
494 is an entry explaining how to protect your configuration file.</li>
495 <li>For additional security in this mode, you may wish to consider the Host
496 authentication
498 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
500 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
501 directives.</li>
502 <li>Unlike cookie and http, does not require a user to log in when first
503 loading the phpMyAdmin site. This is by design but could allow any
504 user to access your installation. Use of some restriction method is
506 HTTP-AUTH directive or disallowing incoming HTTP requests at
507 one’s router or firewall will suffice (both of which
508 are beyond the scope of this manual but easily searchable with Google).</li>
509 </ul>
511 <p>
512 The Swekey is a low cost authentication USB key that can be used in
513 web applications.<br /><br />
514 When Swekey authentication is activated, phpMyAdmin requires the
515 users's Swekey to be plugged before entering the login page (currently
516 supported for cookie authentication mode only). Swekey Authentication is
517 disabled by default.<br /><br />
519 </p>
520 <pre>
521 $cfg['Servers'][$i]['auth_swekey_config'] = './swekey.conf';
522 </pre>
523 <p>
525 each user with their Swekey Id. A self documented sample file is provided
527 users' information.<br /><br />
528 If you want to purchase a Swekey please visit
530 since this link provides funding for phpMyAdmin.
531 </p>
532 <!-- CONFIGURATION -->
536 users:</span> PHP does not seem to like
540 before saving a script you have modified.</p>
545 section to create one. This file only needs to contain the parameters you want to
546 change from their corresponding default value in
549 <p> The parameters which relate to design (like colors) are placed in
552 your site specific code to be included on start and end of each page.</p>
556 (with full path) to your phpMyAdmin installation's directory.
559 some web servers are case–sensitive.
562 Starting with version 2.3.0, it is advisable to try leaving this
563 blank. In most cases phpMyAdmin automatically detects the proper
564 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
565 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
566 A good test is to browse a table, edit a row and save it. There should
567 be an error message if phpMyAdmin is having trouble auto–detecting
568 the correct value. If you get an error that this must be set or if
569 the autodetect code fails to detect your path, please post a bug
570 report on our bug tracker so we can improve the code.</dd>
574 with master / foreign – tables (see
576 <br />
577 If you tried to set this up and it does not work for you, have a look on
579 use it. You will find a link that will analyze why those features have
580 been disabled.<br />
581 If you do not want to use those features set this variable to
585 <dd>A warning is displayed on the main page if Suhosin is detected.
587 from appearing.</dd>
591 domain to call phpMyAdmin inside a frame, and is a potential security
592 hole allowing cross-frame scripting attacks.</dd>
596 algorithm to encrypt the password.<br />
598 passphrase of your choice. It will be used internally by the blowfish
599 algorithm: you won’t be prompted for this passphrase. The maximum
602 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
603 makes a bit weaker security as this generated secret is stored in
604 session and furthermore it makes impossible to recall user name from
605 cookie.</dd>
609 MySQL servers. Therefore, a
611 been added which contains the login information for the different servers.
612 The first
614 contains the hostname of the first server, the second
616 the hostname of the second server, etc. In
618 server definition, however you can put as many as you need in
620 have to define all settings, just those you need to change).</dd>
624 $i-th MySQL-server. E.g. localhost.</dd>
629 ignores this port number and connects with the socket, so if you want
630 to connect to a port different from the default port, use
633 </dd>
637 To determine the correct socket, check your MySQL configuration or, using the
639 Among the resulting information displayed will be the socket used.</dd>
642 <dd>Whether to enable SSL for connection to MySQL server.
643 </dd>
646 <dd>What type connection to use with the MySQL server. Your options are
648 is nearly guaranteed to be available on all MySQL servers, while
649 sockets are not supported on some platforms.<br /><br />
651 To use the socket mode, your MySQL server must be on the same machine
652 as the Web server.</dd>
655 <dd>What php MySQL extension to use for the connection. Valid options are:
656 <br /><br />
659 The classic MySQL extension. This is the recommended and default
660 method at this time.<br /><br />
663 The improved MySQL extension. This extension became available
664 with php 5.0.0 and is the recommended way to connect to a server
668 <dd>Whether to use a compressed protocol for the MySQL server connection
669 or not (experimental).<br />
675 </dt>
677 all relational features (see
679 and, for a MySQL server previous to 4.1.2 or running with
682 authentication mode).<br /><br />
685 cookie authentication modes (or 'config'
686 authentication mode since phpMyAdmin 2.2.1), you need to supply the
691 This account is used to check what databases the user will see at
692 login.<br />
696 In phpMyAdmin versions before 2.2.5, those were called
700 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
701 <dd>Whether config or cookie or
703 should be used for this server.
705 is the plain old way: username and password are stored in
707 <li>'cookie' authentication mode
709 2.2.3 allows you to log in as any valid MySQL user with the
710 help of cookies. Username and password are stored in
711 cookies during the session and password is deleted when it
712 ends. This can also allow you to log in in arbitrary server if
713 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
714 </li>
715 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
716 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
717 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
718 <li>'signon' authentication mode
720 as introduced in 2.10.0 allows you to log in from prepared PHP
721 session data. This is useful for implementing single signon
722 from another application. Sample way how to seed session is in
728 </ul>
731 for more information.
732 </dd>
734 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
735 </dt>
736 <dd>
738 names for hardware authentication. Leave empty to deactivate this feature.
739 </dd>
743 </dt>
744 <dd>
745 When using auth_type = 'config', this is the user/password-pair
746 which phpMyAdmin will use to connect to the
747 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
748 cookie authentication is used and should be empty.</dd>
750 <span
752 </dt>
753 <dd>
754 Allow attempt to log in without password when a login with password
755 fails. This can be used together with http authentication, when
756 authentication is done some other way and phpMyAdmin gets user name
757 from auth and uses empty password for connecting to MySQL. Password
758 login is still tried first, but as fallback, no password method is
759 tried.</dd>
762 </dt>
763 <dd>
764 If set to a (an array of) database name(s), only this (these) database(s)
765 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
766 database(s) name(s) may contain MySQL wildcards characters
770 This setting is an efficient way to lower the server load since the
771 latter does not need to send MySQL requests to build the available
773 privileges rules of the MySQL database server</span>. If set, it just
774 means only these databases will be displayed but
776 <br /><br />
778 An example of using more that one database:
780 <br /><br />
782 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
783 databases in the left frame, so that you can individually arrange your databases.<br />
784 If you want to have certain databases at the top, but don't care about the others, you do not
785 need to specify all other databases. Use:
787 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
788 order.</dd>
791 </dt>
792 <dd>Regular expression for hiding some databases. This only hides them
793 from listing, but a user is still able to access them (using, for example,
794 the SQL query area). To limit access, use the MySQL privilege system.
795 <br /><br />
800 More information on regular expressions can be found in the
802 PCRE pattern syntax</a> portion of the PHP reference manual.
803 </dd>
806 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
807 this string will be displayed instead of the hostname in the pull-down
808 menu on the main page. This can be useful if you want to show only
809 certain databases on your system, for example. For HTTP auth, all
810 non-US-ASCII characters will be stripped.</dd>
814 </dt>
815 <dd>The name of the database containing the linked-tables infrastructure.
816 <br /><br />
819 section in this document to see the benefits of this infrastructure,
820 and for a quick way of creating this database and the needed tables.
821 <br /><br />
823 If you are the only user of this phpMyAdmin installation, you can
824 use your current database to store those special tables; in this
825 case, just put your current database name in
827 set this parameter to the name of your central database containing
828 the linked-tables infrastructure.</dd>
832 </dt>
834 useful for queries you often run.<br /><br />
836 To allow the usage of this functionality:
838 <li>enter the table name in
840 </ul>
841 </dd>
845 </dt>
847 which field is a key in another table (a foreign key). phpMyAdmin
848 currently uses this to
849 <ul><li>make clickable, when you browse the master table, the data values
850 that point to the foreign table;</li>
852 when browsing the master table, if you move the mouse to a column
853 containing a foreign key (use also the 'table_info' table);<br />
856 <li>in edit/insert mode, display a drop-down list of possible foreign
860 <li>display links on the table properties page, to check referential
861 integrity (display missing foreign keys) for each described key;
862 </li>
866 schema of your database (also uses the table_coords table).</li>
867 </ul>
869 The keys can be numeric or character.<br /><br />
871 To allow the usage of this functionality:
874 infrastructure</li>
875 <li>put the relation table name in
877 <li>now as normal user open phpMyAdmin and for each one of your
878 tables where you want to use this feature, click
880 </li>
881 </ul>
885 future development of the cross-db relations.
886 </dd>
890 </dt>
891 <dd>
892 Since release 2.3.0 you can describe, in a special 'table_info'
893 table, which field is to be displayed as a tool-tip when moving the
894 cursor over the corresponding key.<br />
895 This configuration variable will hold the name of this special
896 table. To allow the usage of this functionality:
898 <li>put the table name in
900 <li>then for each table where you want to use this feature,
902 to choose the field.</li>
903 </ul>
905 </dd>
909 </dt>
912 the relations between your tables. To do this it needs two tables
917 schema output).<br /><br />
921 To allow the usage of this functionality:
924 infrastructure</li>
925 <li>put the correct table names in
928 </ul>
931 </dd>
935 </dt>
937 Since release 2.3.0 you can store comments to describe each column for
939 <br /><br />
941 Starting with release 2.5.0, comments are consequently used on the table
942 property pages and table browse view, showing up as tool-tips above the
943 column name (properties page) or embedded within the header of table in
944 browse view. They can also be shown in a table dump. Please see the
945 relevant configuration directives later on.<br /><br />
947 Also new in release 2.5.0 is a MIME-transformation system which is also
949 Transformations</a> for further information. To use the
950 MIME-transformation system, your column_info table has to have the three
951 new fields 'mimetype', 'transformation', 'transformation_options'.
952 <br /><br />
954 To allow the usage of this functionality:
956 infrastructure</li>
957 <li>put the table name in
961 <pre>
962 ALTER TABLE `pma_column_comments`
963 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
964 ADD `transformation` VARCHAR( 255 ) NOT NULL,
965 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
966 </pre>
969 renamed from<br />
972 </ul>
973 </dd>
977 </dt>
980 all queries you entered manually into the phpMyAdmin interface. If you
981 don't want to use a table-based history, you can use the JavaScript-based
982 history. Using that, all your history items are deleted when closing the
983 window.<br /><br />
985 Using
987 you can specify an amount of history items you want to have on hold. On
988 every login, this list gets cut to the maximum amount.<br /><br />
990 The query history is only available if JavaScript is enabled in your
991 browser.<br /><br />
993 To allow the usage of this functionality:
996 infrastructure</li>
998 </li>
999 </ul>
1000 </dd>
1004 </dt>
1006 to visually manage the relations.
1007 <br /><br />
1009 To allow the usage of this functionality:
1012 infrastructure</li>
1014 </li>
1015 </ul>
1016 </dd>
1019 </dt>
1021 column_info table got enhanced with three new fields. If the above variable
1023 latest table structure available. If not, it will emit a warning to the
1024 superuser.<br /><br />
1026 You can disable this checking behavior by setting the variable to false,
1027 which should offer a performance increase.<br /><br />
1029 Recommended to set to FALSE, when you are sure, your table structure is
1030 up to date.</dd>
1032 boolean</dt>
1033 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1034 </dd>
1035 <dt><span id="cfg_Servers_AllowNoPasswordRoot">$cfg['Servers'][$i]['AllowNoPasswordRoot']</span>
1036 boolean</dt>
1037 <dd>Whether to allow access to root user without password. The default
1039 to a MySQL server with was left with an empty password for root.
1040 </dd>
1043 </dt>
1045 authentication is disabled.<br /><br />
1048 all deny rules followed by allow rules. Access is allowed by default. Any
1049 client which does not match a Deny command or does match an Allow command
1050 will be allowed access to the server. <br /><br />
1053 applies all allow rules followed by deny rules. Access is denied by
1054 default. Any client which does not match an Allow directive or does
1055 match a Deny directive will be denied access to the server.<br /><br />
1057 If your rule order is set to 'explicit', the authentication is
1058 performed in a similar fashion to rule order 'deny,allow', with the
1062 and was available in Apache by specifying allow and deny rules without
1063 setting any order.<br /><br />
1065 Please also see <a
1067 address behind proxies.
1068 </dd>
1070 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1071 </dt>
1072 <dd>The general format for the rules is as such:
1074 <pre>
1076 </pre>
1081 well (please note that those containing SERVER_ADDRESS might not be
1082 available on all webservers):
1083 <pre>
1089 </pre>
1091 Having an empty rule list is equivalent to either using
1097 following work:<br />
1099 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1100 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1101 But the following does not work:<br />
1104 </dd>
1105 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1106 <dd>Name of session which will be used for signon authentication method.
1107 </dd>
1109 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1110 </dd>
1112 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1113 </dd>
1116 <dd>If you have more than one server configured, you can set
1118 that server when phpMyAdmin is started, or set it to 0 to be given a
1119 list of servers without logging in.<br />
1121 MUST be set to that server.</dd>
1124 <dd>The maximum number of database names to be displayed in the
1125 navigation frame and the database list.</dd>
1128 <dd>The maximum number of table names to be displayed in the
1129 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1130 when in Light mode.</dd>
1133 <dd>The maximum number of characters when a SQL query is displayed. The
1134 default limit of 1000 should be correct to avoid the display of tons
1135 of hexadecimal codes that represent BLOBs, but some users have real
1136 SQL queries that are longer than 1000 characters. Also, if a query's
1137 length exceeds this limit, this query is not saved in the history.</dd>
1140 <dd>Defines whether to use GZip output buffering for increased
1142 Set to true/false for enabling/disabling. When set to 'auto' (string),
1143 phpMyAdmin tries to enable output buffering and will automatically disable
1144 it if your browser has some problems with buffering. IE6 with a certain patch
1145 is known to cause data corruption when having enabled buffering.</dd>
1148 <dd>Whether persistent connections should be used or not (mysql_connect or
1149 mysql_pconnect).</dd>
1155 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1156 to zero, no time limit is imposed.<br />
1157 This setting is used while importing/exporting dump files but has no
1158 effect when PHP is running in safe mode.</dd>
1161 <dd>Set the number of bytes a script is allowed to allocate. If number set
1162 to zero, no limit is imposed.<br />
1163 This setting is used while importing/exporting dump files but has no
1164 effect when PHP is running in safe mode.<br />
1168 <dd>Mark used tables and make it possible to show databases with locked
1173 generated by phpMyAdmin should be displayed or not.</dd>
1176 <dd>Defines whether normal users (non-administrator) are allowed to
1177 delete their own database or not. If set as FALSE, the link "Drop
1179 mydatabase" will be rejected. Quite practical for
1181 customers.<br />
1182 Please note that this limitation of SQL queries is not as strict as
1183 when using MySQL privileges. This is due to nature of SQL queries
1184 which might be quite complicated. So this choice should be viewed as
1185 help to avoid accidental dropping rather than strict privilege
1186 limitation.</dd>
1190 displayed when you're about to lose data.</dd>
1193 <dd>Define whether the previous login should be recalled or not in cookie
1194 authentication mode.<br /><br />
1196 This is automatically diabled if you do not have configured
1198 </dd>
1205 means that it will be kept for existing session. This is recommended
1206 for not trusted environments.</dd>
1209 <dd>If enabled (default), logout deletes cookies for all servers,
1210 otherwise only for current one. Setting this to false makes it easy to
1211 forget to log out from other server, when you are using more of
1212 them.</dd>
1218 <dd>Define whether phpMyAdmin will continue executing a multi-query
1219 statement if one of the queries fails. Default is to abort execution.</dd>
1222 <dd>Define whether phpMyAdmin will output the results of each query of a
1223 multi-query statement embedded into the
1228 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1229 <br /><br />
1232 MySQL servers behind the firewall where your
1234 </dd>
1237 <dd>Defines whether to use a select-based menu and display only the current
1238 tables in the left frame (smaller page). Only in Non-Lightmode you can
1239 use the feature to display nested folders using
1241 </dd>
1244 <dd>In light mode, defines whether to display the names of databases (in the
1245 selector) using a tree, see also
1247 </dd>
1250 <dd>The string used to separate the parts of the database name when showing
1251 them in a tree.</dd>
1254 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1255 This means if you have tables like 'first__second__third' this will be
1257 If set to FALSE or empty, the feature is disabled. NOTE: You should
1258 not use this separator at the beginning or end of a
1259 table name or multiple times after another without any other
1260 characters in between.</dd>
1263 <dd>Defines how many sublevels should be displayed when splitting
1264 up tables by the above separator.</dd>
1267 <dd>Defines whether to display table comment as tool-tip in left frame or
1268 not.</dd>
1271 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1272 comment and the real name. That means that if you have a table called
1273 'user0001' and add the comment 'MyName' on it, you will see the name
1274 'MyName' used consequently in the left frame and the tool-tip shows
1275 the real name of the DB.</dd>
1278 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1280 When setting this to 'nested', the Alias of the Tablename is only used
1281 to split/nest the tables according to the
1283 directive. So only the folder is called like the Alias, the tablename itself
1284 stays the real tablename.</dd>
1287 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1290 <dd>Enter URL where logo in the navigation frame will point to.
1291 For use especially with self made theme which changes this.
1300 <dd>Defines whether or not to display a server choice at the top of the left frame.
1301 Defaults to FALSE.</dd>
1303 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1304 Defaults to FALSE (drop-down).</dd>
1306 <dd>Defines whether to display database choice in light navigation frame as links
1307 instead of in a drop-down. Defaults to 'auto' - on main page list is
1308 shown, when database is selected, only drop down is displayed.</dd>
1311 <dd>Defines the tab displayed by default when clicking the small
1312 icon next to each table name in the navigation panel. Possible
1318 <dd>Defines whether or not to display space usage and statistics about databases
1319 and tables.<br />
1320 Note that statistics requires at least MySQL 3.23.3 and that, at this
1321 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1324 <dd>Defines whether to display detailed server information on main page.
1325 You can additionally hide more information by using
1327 </dd>
1332 </dt>
1335 not at the starting main (right) frame. This setting
1336 does not check MySQL commands entered directly.<br /><br />
1338 Please note that to block the usage of phpinfo() in scripts, you
1345 hard coded password value in the configuration file, end users can't
1346 be allowed to change their passwords.</dd>
1349 <dd>Defines whether to suggest a database name on the
1353 <dd>Defines whether navigation bar buttons and the right panel top menu
1354 contain text or symbols only. A value of TRUE displays icons, FALSE
1355 displays text and 'both' displays both icons and text.</dd>
1358 <dd>Defines whether a user should be displayed a
1362 <dd>Number of rows displayed when browsing a result set. If the result set
1369 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1373 from editing when browsing a table's content. Valid values are:
1378 </ul>
1379 </dd>
1382 <dd>Defines whether or not MySQL functions fields should be initially
1383 displayed in edit/insert mode. Since version 2.10, the user can
1384 toggle this setting from the interface.
1385 </dd>
1388 <dd>Defines which type of editing controls should be used for CHAR and
1389 VARCHAR fields. Possible values are:
1390 <ul><li>input - this allows to limit size of text to size of field in
1391 MySQL, but has problems with newlines in fields</li>
1392 <li>textarea - no problems with newlines in fields, but also no
1393 length limitations</li>
1394 </ul>
1395 Default is old behavior so input.</dd>
1401 <dd>If there are fewer items than this in the set of foreign keys, then a
1402 drop-down box of foreign keys is presented, in the style described by the
1404 setting.</dd>
1407 <dd>For the foreign key drop-down fields, there are several methods of
1408 display, offering both the key and value data. The contents of the
1409 array should be one or both of the following strings:
1415 </dt>
1416 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1417 creating a dump file</dd>
1420 </dt>
1421 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1422 compressed exports. This doesn't affect smaller dumps and allows users to
1423 create larger dumps that won't otherwise fit in memory due to php
1424 memory limit. Produced files contain more GZip/BZip2 headers, but all
1425 normal programs handle this correctly.</dd>
1429 mainframe.</dd>
1433 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1438 <dd>How many columns will be utilized to display the tables on the
1439 database property view? Default is 1 column. When setting this to a
1440 value larger than 1, the type of the database will be omitted for more
1441 display space.</dd>
1445 <dd>Defines the tab displayed by default on server view. Possible
1452 <dd>Defines the tab displayed by default on database view. Possible
1457 <dd>Defines the tab displayed by default on table view. Possible
1464 points to the MySQL documentation (type depends
1465 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1466 generated.<br />
1468 for more information about MySQL manuals and their types.</dd>
1471 <dd>Type of MySQL documentation:
1477 </ul>
1478 </dd>
1481 <dd>Defines the default language to use, if not browser-defined or
1482 user-defined.<br />
1484 this setting.</dd>
1487 <dd>Defines the default connection collation to use, if not
1488 user-defined.<br />
1493 <dd>Force: always use this language (must be defined in the
1497 <dd>Limit list of available languages to those matching the given regular
1498 expression. For example if you want only Czech and English, you should
1502 <dd>Default character set to use for recoding of MySQL queries. This must be
1503 enabled and it's described by
1505 option.<br />
1506 You can give here any character set which is in
1508 array and this is just default choice, user can select any of them.</dd>
1511 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1512 support (compiled in or module) in PHP to allow MySQL queries recoding
1513 and used language file must have it enabled (by default only these
1514 which are in Unicode, just to avoid losing some characters).<br /><br />
1517 in the Export page, to choose the character set when exporting a file.
1519 </dd>
1522 <dd>You can select here which functions will be used for character set
1523 conversion. Possible values are:
1524 <ul><li>auto - automatically use available one (first is tested
1525 iconv, then recode)</li>
1528 </ul>
1529 Default is auto.</dd>
1532 <dd>Specify some parameters for iconv used in charset conversion. See
1535 used, so that invalid characters will be transliterated.</dd>
1538 <dd>Available character sets for MySQL conversion. You can add your own (any of
1539 supported by recode/iconv) or remove these which you don't use.
1540 Character sets will be shown in same order as here listed, so if you
1541 frequently use some of these move them to the top.</dd>
1546 default empty, you need to fill in some trusted proxy servers if you
1547 want to use rules for IP addresses behind proxy.<br /><br />
1549 The following example specifies that phpMyAdmin should trust a
1551 <pre>
1552 $cfg['TrustedProxies'] =
1554 </pre>
1555 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1556 client's IP address as usual.
1557 </dd>
1561 MIME transformations.<br />
1562 Possible values are:
1563 <ul><li>auto - automatically detect, this is a bit expensive
1565 according to your server real possibilities</li>
1568 </ul>
1569 Default is auto.
1570 </dd>
1573 <dd>
1574 We normally check the permissions on the configuration file to ensure
1575 it's not world writable. However, phpMyAdmin could be installed on
1576 a NTFS filesystem mounted on a non-Windows server, in which case the
1577 permissions seems wrong but in fact cannot be detected. In this case
1579 </dd>
1583 </dd>
1585 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1586 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1587 </dt>
1588 <dd>The background styles used for both the frames.
1591 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1593 <dd>The style used for the pointer in the navi frame.
1597 </dt>
1598 <dd>The color used for the database name in the navi frame.
1607 </dd>
1611 <dd>The style used for table headers. See
1616 </dd>
1620 </dd>
1622 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1624 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1626 </dt>
1628 The former feature highlights the row over which your mouse is passing
1629 and the latter lets you visually mark/unmark rows by clicking on
1630 them.<br />
1635 <dd>You put here a valid CSS font family value, for example
1640 <dd>You put here a valid CSS font family value, for example
1654 </dt>
1656 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1658 The Char* values are used for CHAR and VARCHAR editing (if configured
1662 </dt>
1666 </dt>
1667 <dd>Defines if the whole textarea of the query box will be selected on
1668 click.</dd>
1671 </dt>
1672 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1673 editing.</dd>
1676 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1677 Can be turned off by a toggle button on the browse page.</dd>
1681 </dt>
1682 <dd>Defines the place where modify and delete links would be put when
1683 tables contents are displayed (you may have them displayed both at the
1684 left and at the right).
1690 </dt>
1692 Define which one is displayed by default. The first mode displays each
1693 row on a horizontal line, the second rotates the headers by 90
1694 degrees, so you can use descriptive headers even though fields only
1695 contain small values and still print them out. The vertical mode sorts
1696 each row on a vertical lineup.<br /><br />
1698 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1699 the rotation of the header for horizontalflipped is done via CSS. If
1700 set to 'fake' PHP does the transformation for you, but of course this
1701 does not look as good as CSS.</dd>
1705 string or integer</dt>
1706 <dd>When editing/creating new columns in a table all fields normally get
1707 lined up one field a line. (default: 'horizontal'). If you set this to
1708 'vertical' you can have each field lined up vertically beneath each
1709 other. You can save up a lot of place on the horizontal direction and
1710 no longer have to scroll. If you set this to integer, editing of fewer
1711 columns will appear in 'vertical' mode, while editing of more fields
1712 still in 'horizontal' mode. This way you can still effectively edit
1713 large number of fields, while having full view on few of them.</dd>
1717 </dt>
1719 display of column comments in Browse or Property display. In browse
1720 mode, the comments are shown inside the header. In property mode,
1721 comments are displayed using a CSS-formatted dashed-line below the
1722 name of the field. The comment is shown as a tool-tip for that field.
1723 </dd>
1735 <dd>Whether to display a link to validate a query in any SQL Query box.
1742 <dd>
1743 The name of the directory where
1745 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1746 are available under a drop-down box when you click the database or
1747 table name, then the Import tab.
1748 <br /><br />
1750 If you want different directory for each user, %u will be replaced
1751 with username.<br /><br />
1755 compressed formats is enabled).<br /><br />
1757 This feature is useful when your file is too big to be uploaded via
1759 uploads are disabled in PHP.<br /><br />
1761 Please note that if PHP is running in safe mode, this directory must
1762 be owned by the same user as the owner of the phpMyAdmin scripts.
1763 <br /><br />
1767 alternatives.
1768 </dd>
1771 <dd>
1772 The name of the directory where dumps can be saved.<br /><br />
1774 If you want different directory for each user, %u will be replaced
1775 with username.<br /><br />
1777 Please note that the directory must exist and has to be writable for
1778 the user running webserver.<br /><br />
1780 Please note that if PHP is running in safe mode, this directory must
1781 be owned by the same user as the owner of the phpMyAdmin scripts.
1782 </dd>
1785 <dd>
1786 The name of the directory where temporary files can be stored.
1787 <br /><br />
1789 This is needed for native MS Excel export, see
1795 <br /><br />
1797 If the directory where phpMyAdmin is installed is subject to an
1799 temporary directory in some directory accessible by the web
1800 server. However for security reasons, this directory should be outside
1801 the tree published by webserver. If you cannot avoid having this
1802 directory published by webserver, place at least an empty
1804 possible.
1805 <br /><br />
1807 This directory should have as strict permissions as possible as the only
1808 user required to access this directory is the one who runs the
1809 webserver. If you have root privileges, simply make this user owner of
1810 this directory and make it accessible only by it:
1811 <br /><br />
1813 <pre>
1814 chown www-data:www-data tmp
1815 chmod 700 tmp
1816 </pre>
1818 If you cannot change owner of the directory, you can achieve a similar
1821 <pre>
1822 chmod 700 tmp
1823 setfacl -m "g:www-data:rwx" tmp
1824 setfacl -d -m "g:www-data:rwx" tmp
1825 </pre>
1827 If neither of above works for you, you can still make the directory
1829 system reading and writing data in this directory.
1830 </dd>
1833 <dd>
1834 In this array are defined default parameters for export, names of
1835 items are similar to texts seen on export page, so you can easily
1836 identify what they mean.
1837 </dd>
1840 <dd>
1841 In this array are defined default parameters for import, names of
1842 items are similar to texts seen on import page, so you can easily
1843 identify what they mean.
1844 </dd>
1847 <dd>
1848 Repeat the headers every X cells, or 0 to deactivate.
1849 </dd>
1857 </dt>
1858 <dd>
1859 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1860 or icon is always displayed on the left panel. If JavaScript is enabled in
1861 your browser, a click on this opens a distinct query window, which is
1862 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1863 changes to display a query box.<br /><br />
1865 The size of this query window can be customized with
1867 - both integers for the size in pixels. Note that normally, those
1869 theme you are using.<br /><br />
1873 opens the query window and puts the current query
1874 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1875 query in the right panel's query box.
1876 <br /><br />
1877 The usage of the JavaScript query window is recommended if you have a
1878 JavaScript enabled browser. Basic functions are used to exchange quite
1879 a few variables, so most 4th generation browsers should be capable to
1880 use that feature. It currently is only tested with Internet Explorer 6
1881 and Mozilla 1.x.
1882 <br /><br />
1884 to a table, which has to be created by you (see <a
1886 all your queries will be appended to the form, but only as long as
1887 your window is opened they remain saved.
1888 <br /><br />
1889 When using the JavaScript based query window, it will always get
1890 updated when you click on a new table/db to browse and will focus if
1891 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1892 the query window by checking the box "Do not overwrite this query from
1893 outside the window" below the query textarea. Then you can browse
1894 tables/databases in the background without losing the contents of the
1895 textarea, so this is especially useful when composing a query with
1896 tables you first have to look in. The checkbox will get automatically
1897 checked whenever you change the contents of the textarea. Please
1898 uncheck the button whenever you definitely want the query window to
1899 get updated even though you have made alterations.
1900 <br /><br />
1903 <br /><br />
1904 The query window also has a custom tabbed look to group the features.
1906 default tab to be used when opening the query window. It can be set to
1907 either 'sql', 'files', 'history' or 'full'.</dd>
1913 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1915 If the approximate row count as returned by
1918 count will be used.
1919 </dd>
1921 <dd>For VIEWs, since obtaining the exact count could have an
1922 impact on performance, this value is the maximum to be displayed, using
1924 any row counting.
1925 </dd>
1929 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1931 page. By clicking on the button 'toggle scratchboard' on the page
1932 where you edit x/y coordinates of those elements you can activate a
1933 scratchboard where all your elements are placed. By clicking on an
1934 element, you can move them around in the pre-defined area and the x/y
1935 coordinates will get updated dynamically. Likewise, when entering a
1936 new position directly into the input field, the new position in the
1937 scratchboard changes after your cursor leaves the input field.<br />
1938 You have to click on the 'OK'-button below the tables to save the new
1939 positions. If you want to place a new element, first add it to the
1940 table of elements and then you can drag the new element around.<br />
1941 By changing the paper size and the orientation you can change the size
1942 of the scratchboard as well. You can do so by just changing the
1943 dropdown field below, and the scratchboard will resize automatically,
1944 without interfering with the current placement of the elements.<br />
1945 If ever an element gets out of range you can either enlarge the paper
1946 size or click on the 'reset' button to place all elements below each
1947 other.<br />
1949 get this control to work. The basic Drag&Drop script functionality
1950 was kindly borrowed from www.youngpup.net and is underlying so
1951 specific license.</dd>
1954 <dd>Sorts database and table names according to natural order (for example,
1955 t1, t2, t10). Currently implemented in the left panel (Light mode)
1956 and in Database view, for the table list.</dd>
1960 closed state. A value of 'open' does the reverse.</dd>
1966 <dd>Allows you to specify window's title bar. Following magic string can
1967 be used to get special values:
1968 <dl>
1974 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1983 </dl>
1984 </dd>
1994 </dd>
1997 <dd>If theme manager is active, use this as the path of the subdirectory
1998 containing all the themes.</dd>
2012 </dt>
2013 <dd>Default queries that will be displayed in query boxes when user didn't
2014 specify any. Use %d for database name, %t for table name and %f for a
2015 comma separated list of field names. Note that %t and %f are only
2019 <dd>
2020 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
2021 default we use HTML to format the query, but you can disable this by
2023 </dd>
2026 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2027 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2028 query inside a bracket is indented. By changing
2031 specifies the units of the indent amount that you specified. This is
2032 used via stylesheets.</dd>
2035 <dd>This array is used to define the colours for each type of element of
2036 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2038 If you specify an empty string for the color of a class, it is ignored
2039 in creating the stylesheet.
2040 You should not alter the class names, only the colour strings.<br />
2061 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2065 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2066 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2067 </ul>
2068 </dd>
2072 <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,
2073 as originally published on
2075 <br />
2076 For help in setting up your system to use the service, see the
2078 </dd>
2082 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2083 and any password, so we use those by default. Instead, if
2084 you have an account with them, you can put your login details
2085 here, and it will be used in place of the anonymous login.</dd>
2086 </dl>
2087 </dd>
2090 <dd><b>DEVELOPERS ONLY!</b></dd>
2093 <dd><b>DEVELOPERS ONLY!</b><br />
2094 Enable logging queries and execution times to be displayed in the bottom
2095 of main page (right frame).</dd>
2098 <dd><b>DEVELOPERS ONLY!</b><br />
2099 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2100 the code.<br />
2101 For help in setting up your system to this, see the
2105 <dd><b>DEVELOPERS ONLY!</b><br />
2106 Enable profiling support for phpMyAdmin. This will append a chunk of data
2107 to the end of every page displayed in the main window with profiling
2108 statistics for that page.<br />
2109 You may need to increase the maximum execution time for this to
2110 complete successfully.<i>Profiling was removed from the code for
2111 version 2.9.0 due to licensing issues.</i></dd>
2113 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2114 <dd><b>DEVELOPERS ONLY!</b><br />
2115 When profiling data is displayed, this variable controls the threshold of
2116 display for any profiling data, based on the average time each time has
2117 taken. If it is over the threshold it is displayed, otherwise it is not
2118 displayed. This takes a value in milliseconds. In most cases you don't need
2119 to edit this.</dd>
2122 <dd>All possible types of a MySQL column. In most cases you don't need to
2123 edit this.</dd>
2126 <dd>Possible attributes for fields. In most cases you don't need to edit
2127 this.</dd>
2130 <dd>A list of functions MySQL supports. In most cases you don't need to
2131 edit this.</dd>
2134 <dd>Mapping of column types to meta types used for preferring displayed
2135 functions. In most cases you don't need to edit this.</dd>
2138 <dd>Functions preferred for column meta types as defined in
2139 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2140 to edit this.</dd>
2143 <dd>Functions selected by default when inserting/changing row, Functions
2144 are defined for meta types from
2146 <code>first_timestamp</code>, which is used for first timestamp column
2147 in table.</dd>
2150 <dd>Operators available for search operations on numeric and date fields.
2151 </dd>
2154 <dd>Operators available for search operations on character fields.
2155 Note that we put <code>LIKE</code> by default instead of
2156 <code>LIKE %...%</code>, to avoid unintended performance problems
2157 in case of huge tables.</dd>
2160 <dd>Operators available for search operations on enum fields.</dd>
2163 <dd>Additional operators available for search operations when the
2164 field can be null.</dd>
2166 </dl>
2168 <!-- TRANSFORMATIONS -->
2174 </ol>
2178 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2180 section</a> on how to do so.</p>
2182 <p> You can apply different transformations to the contents of each field. The
2183 transformation will take the content of each field and transform it with
2184 certain rules defined in the selected transformation.</p>
2186 <p> Say you have a field 'filename' which contains a filename. Normally you would
2187 see in phpMyAdmin only this filename. Using transformations you can transform
2188 that filename into a HTML link, so you can click inside of the phpMyAdmin
2189 structure on the field's link and will see the file displayed in a new browser
2190 window. Using transformation options you can also specify strings to
2191 append/prepend to a string or the format you want the output stored in.</p>
2193 <p> For a general overview of all available transformations and their options,
2194 you can consult your
2195 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2196 installation.</p>
2198 <p> For a tutorial on how to effectively use transformations, see our
2200 the official phpMyAdmin homepage.</p>
2204 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2205 clicking on the 'Structure' link for a table). There click on
2206 "Change" (or change icon) and there you will see three new fields at
2207 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2208 'Transformation options'.</p>
2210 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2211 that corresponds to the column's contents. Please note that
2212 transformations are inactive as long as no MIME-type is selected.</li>
2214 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2215 hopefully growing amount of pre-defined transformations. See below for information on
2216 how to build your own transformation.<br />
2218 There are global transformations and mimetype-bound transformations. Global transformations
2219 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2220 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2221 transformations which operate on the main mimetype (like 'image'), which will most likely
2222 take the subtype into regard, and those who only operate on a
2223 specific subtype (like 'image/jpeg').<br />
2225 You can use transformations on mimetypes for which the function was not defined for. There
2226 is no security check for you selected the right transformation, so take care of what the
2227 output will be like.</li>
2229 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2230 transform-function specific options here. Usually the transforms can operate with default
2231 options, but it is generally a good idea to look up the overview to see which options are
2232 necessary.<br />
2234 Much like the ENUM/SET-Fields, you have to split up several options using the format
2235 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2236 parsed as an array, leaving the first value the first element in the array, and so
2237 forth.<br />
2239 If you want to specify a MIME character set you can define it in the transformation_options.
2240 You have to put that outside of the pre-defined options of the specific mime-transform,
2242 for which you can specify 2 options and you want to append a character set, enter "'first
2243 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2245 </ul>
2249 <p> All mimetypes and their transformations are defined through single files in
2250 the directory 'libraries/transformations/'.</p>
2252 <p> They are stored in files to ease up customization and easy adding of new
2253 transformations.</p>
2255 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2256 always work. It makes no sense to apply a transformation to a mimetype, the
2257 transform-function doesn't know to handle.</p>
2259 <p> One can, however, use empty mime-types and global transformations which should work
2260 for many mimetypes. You can also use transforms on a different mimetype they where built
2261 for, but pay attention to option usage as well as what the transformation does to your
2262 field.</p>
2264 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2265 any other transform function and provides some basic functions.</p>
2267 <p> There are 5 possible file names:</p>
2269 <ol><li>A mimetype+subtype transform:<br /><br />
2271 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2273 Please not that mimetype and subtype are separated via '_', which shall
2274 not be contained in their names. The transform function/filename may
2275 contain only characters which cause no problems in the file system as
2276 well as the PHP function naming convention.<br /><br />
2278 The transform function will the be called
2279 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2281 <b>Example:</b><br /><br />
2283 <tt>text_html__formatted.inc.php</tt><br />
2284 <tt>PMA_transform_text_html__formatted()</tt></li>
2286 <li>A mimetype (w/o subtype) transform:<br /><br />
2288 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2290 Please note that there are no single '_' characters.
2291 The transform function/filename may contain only characters which cause
2292 no problems in the file system as well as the PHP function naming
2293 convention.<br /><br />
2295 The transform function will the be called
2296 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2298 <b>Example:</b><br /><br />
2300 <tt>text__formatted.inc.php</tt><br />
2301 <tt>PMA_transform_text__formatted()</tt></li>
2303 <li>A mimetype+subtype without specific transform function<br /><br />
2305 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2307 Please note that there are no '__' characters in the filename. Do not
2308 use special characters in the filename causing problems with the file
2309 system.<br /><br />
2311 No transformation function is defined in the file itself.<br /><br />
2313 <b>Example:</b><br /><br />
2315 <tt>text_plain.inc.php</tt><br />
2316 (No function)</li>
2318 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2320 <tt>[mimetype].inc.php</tt><br /><br />
2322 Please note that there are no '_' characters in the filename. Do not use
2323 special characters in the filename causing problems with the file system.
2324 <br /><br />
2326 No transformation function is defined in the file itself.<br /><br />
2328 <b>Example:</b><br /><br />
2330 <tt>text.inc.php</tt><br />
2331 (No function)</li>
2333 <li>A global transform function with no specific mimetype<br /><br />
2335 <tt>global__[transform].inc.php</tt><br /><br />
2337 The transform function will the be called
2338 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2340 <b>Example:</b><br /><br />
2342 <tt>global__formatted</tt><br />
2343 <tt>PMA_transform_global__formatted()</tt></li>
2344 </ol>
2346 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2347 transform function.</p>
2349 <p> All filenames containing no '__' in themselves are not shown as valid transform
2350 functions in the dropdown.</p>
2352 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2353 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2354 without a transform function. Also note the introduction of a function description in
2355 the language files. For each function a $strTransformation_[filename without .inc.php]
2356 has to exist.</p>
2358 <p> You can use the template generator to generate new functions and entries in the
2359 language file.</p>
2361 <p> To create a new transform function please see
2362 <tt>libraries/transformations/template_generator.sh</tt>.
2363 To create a new, empty mimetype please see
2364 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2366 <p> A transform function always gets passed three variables:</p>
2368 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2369 you want to transform.</li>
2370 <li><b>$options</b> - Contains any user-passed options to a transform function
2371 as an array.</li>
2372 <li><b>$meta</b> - Contains an object with field information to your column.
2373 The data is drawn from the output of the
2375 function. This means, all object properties described on the
2377 available in this variable and can be used to transform a field accordingly
2378 to unsigned/zerofill/not_null/... properties.<br />
2379 The $meta->mimetype variable contains the original MIME-type of the
2380 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2381 </ol>
2383 <!-- FAQ -->
2390 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2394 </ol>
2396 <p> Please have a look at our
2398 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2399 features and or interface.</p>
2405 action is required or phpMyAdmin sends a blank page or a page full of
2406 cryptic characters to my browser, what can I do?</a></h4>
2408 <p> There are some known PHP bugs with output buffering and compression.<br />
2410 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2411 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2412 configuration file.<br />
2413 Furthermore, we know about such problems connected to the release
2414 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2415 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2420 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2421 See also the
2423 entry about PHP bugs with output buffering.<br />
2424 If your server keeps crashing, please ask for help in the various Apache
2425 support groups.</p>
2429 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2430 script: I'm always displayed the login screen.</a></h4>
2432 <p> This is a known PHP bug (see this
2434 official PHP bug database. It means there is and won't be any phpMyAdmin
2435 fix against it because there is no way to code a fix.</p>
2441 application misbehaved by not returning a complete set of
2443 </h4>
2445 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2446 Have a look at the last message in this
2448 official PHP bug database.</p>
2453 and/or many error messages with the
2455 mode.</a></h4>
2457 <p> This is a known problem with the PHP
2459 filter: it's not so stable. Please use instead the cookie authentication mode.
2460 </p>
2465 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2466 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2467 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2468 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2469 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2474 work.</a></h4>
2476 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2477 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2478 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2479 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2480 We faced PHP crashes when trying to download a dump with MS Internet
2481 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2482 this case you should switch to the release version of PHP 4.2.0.</p>
2486 an error about safe mode being in effect.</a></h4>
2488 <p> Your uploaded file is saved by PHP in the "upload dir", as
2489 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2490 the system default is <i>/tmp</i>).<br />
2491 We recommend the following setup for Apache servers running in safe mode,
2492 to enable uploads of files while being reasonably secure:</p>
2494 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2495 <li>give ownership to the Apache server's user.group:
2496 <tt>chown apache.apache /tmp/php</tt></li>
2497 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2498 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2499 <li>restart Apache</li>
2500 </ul>
2504 general file uploads don't work on my system and uploaded files have a
2505 <tt>Content-Type:</tt> header in the first line.</a></h4>
2507 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2508 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2509 So the problem is that this package has a serious bug that was corrected
2510 ages ago in PHP (2001-01-28: see
2512 for more details). The problem is that the bugged package is still
2513 available though it was corrected (see
2515 for more details).<br />
2516 So please download
2517 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2518 and the problem should go away.<br />
2519 And that fixes the \r\n problem with file uploads!</p>
2523 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2524 I'm using the Apache server.</a></h4>
2526 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2527 your <i>httpd.conf</i>:</p>
2531 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2535 uploading a file from the query box.</a></h4>
2537 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2538 restrictions. However you need to create temporary directory and
2540 The uploaded files will be moved there, and after execution of your
2546 <p> The MySQL manual explains how to
2548 reset the permissions</a>.</p>
2553 execute a bookmark.</a></h4>
2555 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2556 cannot access the uploaded query.</p>
2561 submit a query from the convenient text area.</a></h4>
2563 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2564 and try to increase it.</p>
2568 </h4>
2570 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2571 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2572 names to align with current standards.</p>
2577 </h4>
2579 <p> Starting with version 2.7.0, the import engine has been re–written and these
2580 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2581 to take advantage of the new import features.</p>
2583 <p> The first things to check (or ask your host provider to check) are the
2584 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2585 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2586 All of these three settings limit the maximum size of data that can be
2587 submitted and handled by PHP. One user also said that post_max_size
2588 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2590 There exist several workarounds if your upload is too big or your
2591 hosting provider is unwilling to change the settings:</p>
2594 feature. This allows one to
2595 upload a file to the server via scp, ftp, or your favorite file transfer
2596 method. PhpMyAdmin is then able to import the files from the temporary
2598 section</a> of this document.</li>
2600 BigDump</a>) to split the files before uploading. We cannot support this
2601 or any third party applications, but are aware of users having success
2602 with it.</li>
2603 <li>If you have shell (command line) access, use MySQL to import the files
2604 directly. You can do this by issuing the "source" command from
2605 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2606 </ul>
2610 support?</a></h4>
2612 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2613 fully supported. phpMyAdmin may connect to your MySQL server
2614 using PHP's classic
2617 is available in php 5.0.<br />
2618 Either way, the developers of both extensions recommend to use the classic
2619 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2620 When compiling php, we strongly recommend that you manually link the MySQL
2621 extension of your choice to a MySQL client library of at least the same
2622 minor version since the one that is bundled with some PHP distributions is
2625 If your webserver is running on a windows system, you might want to try
2626 MySQL's
2628 instead of the MySQL / MySQLi extensions that are bundled with the official
2629 php Win32 builds.</p>
2633 message, "Client does not support authentication protocol requested
2634 by server; consider upgrading MySQL client"</a></h5>
2636 <p> You tried to access MySQL with an old MySQL client library. The version of
2637 your MySQL client library can be checked in your phpinfo() output.
2638 In general, it should have at least the same minor version as your server
2642 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2643 changed the authentication hash and your PHP is trying to use the old method.
2645 with the proper client library to match your MySQL installation. Your
2646 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2647 More information (and several workarounds) are located in the
2649 </p>
2653 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2654 capital letter in its name it is changed to lowercase as it should. But
2655 if I try to DROP this table MySQL is unable to find the corresponding
2656 file.</a></h4>
2658 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2659 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2660 directive.</p>
2664 script seems not to know the font face I'm using!</a></h4>
2666 <p> The "FPDF" library we're using for this feature requires some
2667 special files to use font faces.<br />
2669 these files.</p>
2673 check PHP Configuration".</a></h4>
2675 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2676 "MySQL extension". This extension may be part of the PHP
2677 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2678 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2679 to load the extension but failed.<br /><br />
2681 Usually, the problem is solved by installing a software package called
2682 "PHP-MySQL" or something similar.</p>
2687 and I cannot log in using cookie auth.</a></h4>
2689 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2693 so I cannot upload.</a></h4>
2695 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2696 parameter is not set to "on".</p>
2700 a new table the table and field names are changed to lowercase!</a></h4>
2702 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2703 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2704 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2705 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2706 directory and add the following line to the group [mysqld]:</p>
2708 <pre>set-variable = lower_case_table_names=0</pre>
2710 <p> Next, save the file and restart the MySQL service. You can always check the
2711 value of this directive using the query</p>
2713 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2717 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2720 </p>
2724 and I get problems, such as undefined variables when I run a
2727 <p> A tip from Jose Fandos: put a comment on the following two lines
2728 in httpd.conf, like this:</p>
2730 <pre>
2731 # mod_gzip_item_include file \.php$
2733 </pre>
2735 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2736 PHP scripts. Of course you have to restart Apache.</p>
2741 I get the error "No input file specified" when trying to
2742 run phpMyAdmin.</a></h4>
2744 <p> This is a permission problem. Right-click on the phpmyadmin folder
2745 and choose properties. Under the tab Security, click on "Add"
2746 and select the user "IUSR_machine" from the list. Now set his
2747 permissions and it should work.</p>
2751 db_structure.php with plenty of tables).</a></h4>
2754 GZIP output buffering is enabled. If you turn off it (by
2756 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2757 PHP 5.0.0.</p>
2761 message 'Errorcode: 13'. What does this mean?</a></h4>
2763 <p> This can happen due to a MySQL bug when having database / table names with
2764 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2765 To fix this, turn off this directive, convert all database and table names
2766 to lower case and turn it on again. Alternatively, there's a bug-fix
2767 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2771 and the fields are duplicated.</a></h4>
2773 <p> It is possible to configure Apache in such a way that PHP has problems
2774 interpreting .php files.</p>
2776 <p> The problems occur when two different (and conflicting) set of directives
2777 are used:</p>
2779 <pre>
2780 SetOutputFilter PHP
2781 SetInputFilter PHP
2782 </pre>
2784 <p> and</p>
2786 <pre>AddType application/x-httpd-php .php</pre>
2788 <p> In the case we saw, one set of directives was in
2789 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2790 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2791 The recommended way is with <tt>AddType</tt>, so just comment out
2792 the first set of lines and restart Apache:</p>
2794 <pre>
2795 #SetOutputFilter PHP
2796 #SetInputFilter PHP
2797 </pre>
2802 <p> This problem is known to happen when the server is running Turck MMCache
2803 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2808 <p> Yes.<br />
2809 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2810 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2811 <tt>error_reporting</tt> settings.
2812 </p>
2815 <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>
2817 <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>
2820 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2821 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2822 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2823 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2824 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2825 enabled.) Click <tt>OK</tt>.</li>
2826 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2827 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2828 </ol>
2832 PHP 5.0.4 on 64-bit systems?</a></h4>
2834 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2835 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2841 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
2842 the order of the server paragraph in <tt>config.inc.php</tt>.
2843 Table and script parts are optional. If you want
2844 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2845 some configuration. Following lines apply only for <a
2847 that you have enabled some features within global configuration. You need
2848 <code>Options FollowSymLinks</code> and <code>AllowOverride
2849 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2850 you need mod_rewrite to be enabled. Then you just need to create following
2851 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2852 (don't forget to change directory name inside of it):</p>
2854 <pre>
2855 RewriteEngine On
2856 RewriteBase /path_to_phpMyAdmin
2857 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2858 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2859 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2860 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2861 </pre>
2864 <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>
2866 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2867 following rewrite rule:</p>
2869 <pre>
2870 RewriteEngine On
2871 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2872 </pre>
2876 </h4>
2877 <p>
2878 There can be many explanations to this and a look at your server's
2879 error log file might give a clue.
2880 </p>
2884 password encryption in cookie auth doesn't work.</a></h4>
2886 <p> If your cluster consist of different architectures, PHP code used for
2887 encryption/decryption won't work correct. This is caused by use of
2888 pack/unpack functions in code. Only solution is to use mcrypt extension
2889 which works fine in this case.</p>
2894 <p> Yes but the default configuration values of Suhosin are known to cause
2895 problems with some operations, for example editing a table with many
2896 columns and no primary key. Tuning information is available at
2898 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2899 although the parameter names have changed (<tt>suhosin</tt> instead
2901 <tt>SuhosinDisableWarning</tt> directive</a>.
2902 </p>
2908 headers already sent by ..." is displayed, what's the problem?</a></h4>
2910 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2911 (I.E. no blank lines, no spaces, no characters...) neither before the
2912 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2913 tag at the end. We also got a report from a user under IIS, that used
2914 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2915 contained an end-of-line character (hex 0A) at the end; removing this character
2916 cleared his errors.</p>
2921 <p> Either there is an error with your PHP setup or your username/password is
2922 wrong. Try to make a small script which uses mysql_connect and see if it
2923 works. If it doesn't, it may be you haven't even compiled MySQL support
2924 into PHP.</p>
2928 connect to local MySQL server through socket '/tmp/mysql.sock'
2929 (111) ..." is displayed. What can I do?</a></h4>
2931 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2933 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2934 In your <i>php.ini</i> you will find a line</p>
2936 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2938 <p> change it to</p>
2940 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2942 <p> Then restart apache and it will work.</p>
2944 <p> Here is a fix suggested by Brad Ummer:</p>
2946 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2947 To do this, telnet to your server and go to the MySQL bin directory. In
2948 this directory there should be a file named <i>mysqladmin</i>. Type
2949 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2950 info about your MySQL server, including the socket
2951 (<i>/tmp/mysql.sock</i>, for example).</li>
2952 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2953 phpMyAdmin, you need to complete the socket information in the
2954 <i>config.inc.php</i>.<br />
2955 For example:
2957 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2958 <br /><br />
2960 Please also make sure that the permissions of this file allow to be readable
2961 by your webserver (i.e. '0755').</li>
2962 </ul>
2964 <p> Have also a look at the
2966 corresponding section of the MySQL documentation</a>.</p>
2970 what can I do?</a></h4>
2973 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2974 sometime.<br />
2975 Also have a look at your PHP version number: if it contains "4.0b..."
2976 it means you're running a beta version of PHP. That's not a so good idea,
2977 please upgrade to a plain revision.</p>
2981 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2982 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2984 <p> Check the value you set for the
2986 directive in the phpMyAdmin configuration file.</p>
2990 password: YES)"-error when trying to access a MySQL-Server on a
2991 host which is port-forwarded for my localhost.</a></h4>
2993 <p> When you are using a port on your localhost, which you redirect via
2994 port-forwarding to another host, MySQL is not resolving the localhost
2995 as expected.<br />
2996 Erik Wasser explains: The solution is: if your host is "localhost"
2997 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2998 connection for speeding up things. And that doesn't work in this configuration
2999 with port forwarding.<br />
3005 <p> Themes are configured with
3009 <br />
3011 should not delete the directory "original" or its underlying
3012 structure, because this is the system theme used by phpMyAdmin.
3013 "original" contains all images and styles, for backwards
3014 compatibility and for all themes that would not include images or css-files.
3015 <br /><br />
3018 is enabled, you can select your favorite theme on the main page. Your
3019 selected theme will be stored in a cookie.<br /><br /></p>
3021 <p> To create a theme:</p>
3023 <ul><li>make a new subdirectory (for example "your_theme_name") under
3025 (by default <tt>themes</tt>)</li>
3026 <li>copy the files and directories from "original" to
3027 "your_theme_name"</li>
3028 <li>edit the css-files in "your_theme_name/css"</li>
3029 <li>put your new images in "your_theme_name/img"</li>
3030 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3031 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3032 contain your chosen theme name, that will be visible in user interface</li>
3033 <li>make a new screenshot of your theme and save it under
3034 "your_theme_name/screen.png"</li>
3035 </ul>
3037 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3038 theme verbose name, theme generation and theme version. These versions and
3039 generations are enumerated from 1 and do not have any direct dependence on
3040 phpMyAdmin version. Themes within same generation should be backwards
3041 compatible - theme with version 2 should work in phpMyAdmin requiring
3042 version 1. Themes with different generation are incompatible.</p>
3044 <p> If you do not want to use your own symbols and buttons, remove the
3045 directory "img" in "your_theme_name". phpMyAdmin will
3046 use the default icons and buttons (from the system-theme "original").
3047 </p>
3051 what can I do?</a></h4>
3053 <p> Here are a few points to check:</p>
3055 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3057 directive empty. See also
3059 </li>
3060 <li>Maybe you have a broken PHP installation or you need to upgrade
3061 your Zend Optimizer. See
3063 http://bugs.php.net/bug.php?id=31134</a>.
3064 </li>
3065 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3066 set to the default (200) or another low value, you could get this
3067 error if your table has a high number of columns. Adjust this setting
3068 accordingly. (Thanks to Klaus Dorninger for the hint).
3069 </li>
3070 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3071 of ";" will cause this error. Replace it with "&;".
3072 </li>
3074 you might want to increase
3076 </li>
3077 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3078 </li>
3079 </ul>
3086 who logged out can not log in again in with the same nick.</a></h4>
3088 <p> This is related to the authentication mechanism (protocol) used by
3089 phpMyAdmin. To bypass this problem: just close all the opened
3090 browser windows and then go back to phpMyAdmin. You should be able to
3091 log in again.</p>
3095 limit error or a time limit error.</a></h4>
3097 <p> Compressed dumps are built in memory and because of this are limited to
3098 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3099 using
3101 (enabled by default). Zip exports can not be handled this way, so if you need
3102 Zip files for larger dump, you have to use another way.</p>
3106 or alter a table.</a></h4>
3108 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3112 bundled with the MySQL server distribution.</a></h4>
3114 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3116 <pre>
3117 -- MySQL dump 8.22
3118 --
3119 -- Host: localhost Database: database
3120 ---------------------------------------------------------
3121 -- Server version 3.23.54
3122 </pre>
3124 <p> The invalid part of the code is the horizontal line made of dashes that
3125 appears once in every dump created with mysqldump. If you want to run your
3126 dump you have to turn it into valid MySQL. This means, you have to add a
3127 whitespace after the first two dashes of the line or add a # before it:
3128 <br />
3129 <code>
3130 -- -------------------------------------------------------<br />
3131 </code>
3132 or<br />
3133 <code>
3134 #---------------------------------------------------------
3135 </code>
3136 </p>
3143 <p> Please note that you should not use the separating string multiple times
3144 without any characters between them, or at the beginning/end of your table
3145 name. If you have to, think about using another TableSeparator or disabling
3146 that feature</p>
3151 <p> In Relation view, being able to choose a table in another database,
3152 or having more than one index field in the foreign key.<br /><br/>
3153 In Query-by-example (Query), automatic generation of the query
3154 LEFT JOIN from the foreign table.<br /><br/>
3155 </p>
3159 I get series of errors like "Warning: unable to parse url". How
3160 can this be fixed?</a></h4>
3161 <p>
3162 Your table neither have a primary key nor an unique one, so we must use a
3163 long expression to identify this row. This causes problems to parse_url
3164 function. The workaround is to create a primary or unique key.
3165 <br />
3166 </p>
3170 a MIME-Transformation onto!</a></h4>
3172 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3173 nested forms can be put inside the table where phpMyAdmin displays the results.
3174 You can, however, use any form inside of a table if keep the parent
3175 form-container with the target to tbl_row_delete.php and just put your own
3176 input-elements inside. If you use a custom submit input field, the form will
3177 submit itself to the displaying page again, where you can validate the
3178 $HTTP_POST_VARS in a transformation.
3180 For a tutorial on how to effectively use transformations, see our
3182 on the official phpMyAdmin-homepage.</p>
3186 MySQL server</a></h4>
3188 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3191 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3192 the quote-character (") is interpreted as an identifier quote character and
3193 not as a string quote character, which makes many internal phpMyAdmin
3195 statements. There is no workaround to this behaviour. News to this item will
3196 be posted in Bug report
3197 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3198 </p>
3202 more that one column with the same value
3203 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3204 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3206 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3207 can use it for the Edit and Delete links.</p>
3212 <p> phpMyAdmin uses a quick method to get the row count, and this method
3213 only returns an approximate count in the case of InnoDB tables. See
3215 a way to modify those results, but
3216 this could have a serious impact on performance.</p>
3221 <p> The number of records in queries containing COUNT and GROUP BY is
3222 not correctly calculated. Also, sorting results of a query like
3227 containing an hyphen.
3228 </a></h4>
3229 <p>
3230 The tests I have made with current MySQL 4.1.11 API shows that the
3231 API does not accept this syntax for the USE command. Enclosing the
3232 db name with backquotes works. For further confusion, no backquotes
3233 are needed with command-line mysql.
3234 </p>
3237 <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>
3238 <p>
3239 This has been a known limitation of phpMyAdmin since the beginning and
3240 it's not likely to be solved in the future.
3241 </p>
3243 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3246 <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
3247 need to install it for each customer.
3248 </a></h4>
3249 <p>
3250 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3251 your users. The development of this feature was kindly sponsored by
3252 NetCologne GmbH.
3253 This requires a properly setup MySQL user management and phpMyAdmin
3254 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3256 </p>
3260 access.
3261 </a></h4>
3262 <p>
3263 This depends on your system.<br />
3264 If you're running a server which cannot be accessed by other people, it's
3265 sufficient to use the directory protection bundled with your webserver
3267 If other people have telnet access to your server, you should use
3268 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3269 <br /><br />
3270 Suggestions:
3271 </p>
3272 <ul>
3273 <li>
3275 </li>
3276 <li>
3277 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3278 is a user whose password is only known to you, and apache is the
3279 group under which Apache runs.
3280 </li>
3281 <li>
3282 You should use PHP safe mode, to protect from other users that try
3284 </li>
3285 </ul>
3290 </a></h4>
3291 <p>
3296 </p>
3299 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3300 authentication.
3301 </a></h4>
3305 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3306 and/or
3308 are wrong.</li>
3310 <li>You have already setup a security mechanism for the
3311 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3312 phpMyAdmin's authentication, so remove it.</li>
3313 </ul>
3320 and put the privileges you want. For example,
3322 would let a user create/manage his/her database(s).</p>
3327 <p> If you have existing rules from an old .htaccess file, you can take them
3330 be a major benefit here if your installation is suited to using it. Then
3331 you can just add those updated lines into the
3335 <p> If you want a pre-made sample, you can try this fragment. It stops the
3336 'root' user from logging in from any networks other than the private
3339 <pre>
3340 //block root from logging in except from the private networks
3341 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3342 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3343 'deny root from all',
3344 'allow root from localhost',
3348 );
3349 </pre>
3354 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3355 different than the one set in your
3357 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3358 while a domain name is defined in the config file.</p>
3363 <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>
3369 when trying to create a table with more than 14 fields.
3370 </a></h4>
3371 <p>
3372 We could reproduce this problem only under Win98/98SE. Testing under
3373 WinNT4 or Win2K, we could easily create more than 60 fields.
3374 <br />
3375 A workaround is to create a smaller number of fields, then come back to
3376 your table properties and add the other fields.
3377 </p>
3381 <p>
3382 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3383 with each script/website that use forms.<br />
3384 Upgrade or downgrade your Xitami server.
3385 </p>
3388 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3389 <p>
3390 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3391 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3392 don't seem to work.<br />
3394 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3395 the user's temporary directory, so they must be moved before closing
3396 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3399 </p>
3403 Explorer never stores the cookies.
3404 </a></h4>
3405 <p>
3406 MS Internet Explorer seems to be really buggy about cookies, at least till
3408 in this area!
3409 <br />
3410 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3411 work!
3412 </p>
3416 rows.
3417 </a></h4>
3418 <p>
3420 </p>
3423 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3424 when trying to modify a row in a table with many fields, or with a text field
3425 </a></h4>
3426 <p>
3427 Your table neither have a primary key nor an unique one, so we must use a
3428 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
3429 those browsers, and this not happen in Netscape, for example. The
3430 workaround is to create a primary or unique key, or use another browser.
3431 <br />
3432 </p>
3436 page.
3437 </a></h4>
3438 <p>
3439 Some browsers support right-clicking into the frame you want to refresh,
3440 just do this in the right frame.<br />
3441 </p>
3445 query box.
3446 </a></h4>
3447 <p>
3448 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3449 Mozilla versions.<br />
3450 </p>
3454 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3455 </a></h4>
3456 <p>
3457 This is a Mozilla bug (see bug #26882 at
3459 </p>
3464 </a></h4>
3465 <p>
3466 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3467 data in octet-stream mode. Since we can't detect the specific Netscape
3468 version, we cannot workaround this bug.
3469 </p>
3473 wrong.</a></h4>
3475 <p> Please ensure that you have set your browser's character set to the one of the
3476 language file you have selected on phpMyAdmin's start page.
3477 Alternatively, you can try the auto detection mode that is supported by the
3478 recent versions of the most browsers.</p>
3481 <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
3484 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3485 Netscape and Mozilla do not have this problem.</p>
3488 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3489 I cannot manage two servers: I log in to the first one, then the other one,
3490 but if I switch back to the first, I have to log in on each operation.</a></h4>
3496 but nothing happens after that, only a blank screen.</a></h4>
3499 bug in Opera6, because it is not able to interpret frameset definitions
3500 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3501 Opera7 at least.</p>
3510 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3515 address and you are starting
3517 containing a domain name, or the reverse situation.</li>
3518 <li>Security settings in IE and/or Microsoft Security Center are
3519 too high, thus blocking scripts execution.</li>
3520 <li>The Windows Firewall is blocking Apache and MySQL. You must
3524 </ul>
3527 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3528 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3529 installed in their Firefox is causing the problem.</p>
3536 </a></h4>
3537 <p>
3538 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3539 specifying a wrong field-type.<br />
3540 Common errors include:
3541 </p>
3542 <ul>
3545 </ul>
3546 <p>
3547 Also, look at the syntax chapter in the MySQL manual to confirm that your
3548 syntax is correct.
3549 </p>
3553 phpMyAdmin generates only one index with those 2 fields.
3554 </a></h4>
3555 <p>
3557 index. If you want two indexes, create the first one when creating the
3558 table, save, then display the table properties and click the Index link to
3559 create the other index.
3560 </p>
3564 <p>
3565 Since version 2.2.3, you have a checkbox for each field that can be null.
3567 field's value. Since version 2.5.5, you have to use the checkbox to get
3569 a literal NULL in the field, and not a NULL value (this works in PHP4).
3570 </p>
3575 <p> Click on a database or table name in the left frame, the properties will be
3577 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3578 statements that can be used to recreate your database/table.
3579 <br /><br />
3581 transmit the resulting dump to your station. Depending on your PHP
3582 configuration, you will see options to compress the dump. See also the
3584 configuration variable.<br /><br />
3587 this document.</p>
3592 </a></h4>
3594 <p> Click on a database name in the left frame, the properties will be
3596 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3598 the path to your dump filename, or use the Browse button. Then click Go.
3599 <br /><br />
3601 that you upgrade to take advantage of the new features.
3602 <br /><br />
3604 in this document.
3605 </p>
3610 <p> Here is an example with the tables persons, towns and countries, all
3612 table, create it as explained in the configuration section. Then create the
3613 example tables:</p>
3615 <pre>
3616 CREATE TABLE REL_countries (
3617 country_code char(1) NOT NULL default '',
3618 description varchar(10) NOT NULL default '',
3619 PRIMARY KEY (country_code)
3620 ) TYPE=MyISAM;
3622 INSERT INTO REL_countries VALUES ('C', 'Canada');
3624 CREATE TABLE REL_persons (
3625 id tinyint(4) NOT NULL auto_increment,
3626 person_name varchar(32) NOT NULL default '',
3628 country_code char(1) NOT NULL default '',
3629 PRIMARY KEY (id)
3630 ) TYPE=MyISAM;
3632 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3633 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3635 CREATE TABLE REL_towns (
3637 description varchar(30) NOT NULL default '',
3638 PRIMARY KEY (town_code)
3639 ) TYPE=MyISAM;
3641 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3642 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3643 </pre>
3649 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3653 </ul>
3661 <li>In the fields row, choose persons.person_name and click the
3663 <li>Do the same for towns.description and countries.descriptions in the
3666 the correct joins have been generated</li>
3668 </ul>
3672 <p>
3673 Starting from the previous example, create the pma_table_info as explained
3674 in the configuration section, then browse your persons table,
3675 and move the mouse over a town code or country code.
3676 <br /><br />
3677 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3678 enables: drop-down list of possible values.
3679 </p>
3682 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3683 <p>
3686 <br /><br />
3687 Then you need to think about your schema layout. Which tables will go on
3688 which pages?
3689 </p>
3690 <ul>
3696 page and click Go. If you like, you
3698 linked tables onto the new page.</li>
3699 <li>Select the name of the new page (making sure the Edit radio button
3700 is selected) and click Go.</li>
3702 Coordinates are relative; your diagram will
3703 be automatically scaled to fit the page. When initially placing tables
3704 on the page, just pick any coordinates -- say, 50x50. After clicking
3706 position the element correctly.</li>
3708 first be sure to click the Save
3709 button beneath the list of tables and coordinates, to save any changes
3710 you made there. Then scroll all the way down, select the
3712 you want, and click Go.</li>
3713 <li>Internet Explorer for Windows may suggest an incorrect filename when
3718 browsers on Windows, do not have this problem.</li>
3719 </ul>
3723 columns!</a></h4>
3725 <p> No, it's MySQL that is doing
3731 underscores in the database name?</a></h4>
3733 <p> If you do not put a backslash before the underscore, this is a wildcard
3736 john2db ...<br /><br />
3738 If you put a backslash before the underscore, it means that the database
3739 name will have a real underscore.</p>
3743 statistics pages?</a></h4>
3754 if it already exists during the import. It does NOT drop the table after
3755 your export, it only affects the import file.</li>
3757 Otherwise, you may get an error if the table name exists but has a
3758 different structure.</li>
3760 (if any) will be included in backup.</li>
3762 field and table names formed with special characters are protected.</li>
3764 types set in the pmadb in the dump as
3766 </li>
3767 </ul>
3772 command, for better documentation (but resulting file is bigger).</li>
3774 once the INSERT verb and the table name.</li>
3777 </li>
3779 more info is provided in the
3781 but basically with this selected, invalid values are adjusted and
3782 inserted rather than causing the entire statement to fail.</li>
3783 </ul>
3787 in its name.</a></h4>
3790 is the normal way to reference a database and table name. Worse, MySQL
3791 will usually let you create a database with a dot, but then you cannot
3792 work with it, nor delete it.</p>
3805 for usage.<br />
3806 On a more recent pear version, I had problems with the state of Net_DIME
3807 being beta, so this single command
3809 needed modules.<br />
3810 If you use the Validator, you should be aware that any
3812 submit will be stored anonymously (database/table/column names,
3813 strings, numbers replaced with generic values). The Mimer
3816 We utilize it as free SOAP service.</p>
3820 it, but MySQL says "BLOB column '...' used in key specification without
3823 <p> The right way to do this, is to create the field without any indexes,
3825 dialog. On this page, you will be able to choose your BLOB field, and
3826 set a size to the index, which is the condition to create an index on
3827 a BLOB field.</p>
3831 editing fields?</a></h4>
3833 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3834 with many editing fields (table structure changes, row editing, etc.)
3835 (must be enabled in configuration - see.
3837 You can also have a look at the directive
3839 ('vertical') and see if this eases up editing for you.</p>
3843 WTF is this feature then useful for?</a></h4>
3845 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3846 on them. Otherwise you could just put a comment on the field. Because entering
3847 your own mimetype will cause serious syntax checking issues and validation,
3848 this introduces a high-risk false-user-input situation. Instead you have to
3849 initialize mimetypes using functions or empty mimetype definitions.<br />
3850 Plus, you have a whole overview of available mimetypes. Who knows all those
3851 mimetypes by heart so he/she can enter it at will?</p>
3855 can't I see any bookmarks below the query box? What is this variable for?
3856 </a></h4>
3858 <p> Any query you have executed can be stored as a bookmark on the page where the
3859 results are displayed. You will find a button labeled 'Bookmark this query'
3860 just at the end of the page.<br />
3861 As soon as you have stored a bookmark, it is related to the database you run
3862 the query on. You can now access a bookmark dropdown on each page, the query
3863 box appears on for that database.<br /><br />
3865 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3869 aware of that you HAVE to create a valid query, otherwise your query won't be
3870 even able to be stored in the database.<br />
3872 for your query will remain the way it is, but will be stripped of the /**/
3873 chars. So you can use:<br /><br />
3877 which will be expanded to<br /><br />
3881 in your query, where VARIABLE is the string you entered in the input box. If
3882 an empty string is provided, no replacements are made.<br /><br />
3884 A more complex example. Say you have stored this query:<br /><br />
3886 <br /><br />
3889 the full query will be:<br /><br />
3892 <br /><br />
3896 spaces inserted there
3897 will be later also inserted as spaces in your query and may lead to unexpected
3898 results especially when
3900 Your initial query which is going to be stored as a bookmark has to yield at
3901 least one result row so
3902 you can store the bookmark. You may have that to work around using well
3906 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3907 include exported table?</a></h4>
3909 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3910 document should look like following one (assuming you have table
3913 <pre>
3914 \documentclass{article} % or any class you want
3915 \usepackage{longtable} % for displaying table
3916 \begin{document} % start of document
3917 \include{table} % including exported table
3918 \end{document} % end of document
3919 </pre>
3923 access them.
3924 </a></h4>
3927 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3928 enable users to see all the database names.
3931 So if your users do not need those privileges, you can remove them and their
3932 databases list will shorten.</p>
3936 possible values for a field, based on some foreign table?</a></h4>
3938 <p> You have to setup appropriate links between the tables, and also
3942 foreign table, a drop-down list of values will be available.
3943 You will see two lists of values, the first list containing the key
3944 and the display field, the second list containing the display field
3945 and the key. The reason for this is to be able to type the first
3946 letter of either the key or the display field.<br /><br />
3948 For 200 values or more, a distinct window will appear, to browse foreign
3949 key values and choose one.</p>
3953 automatically when entering Browse mode for a table?</a></h4>
3955 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3956 </p>
3960 Excel files, how can I enable that?</a></h4>
3962 <p> Current version does support direct export to Microsoft Excel and Word
3963 versions 2000 and newer. If you need export older versions, you can use
3965 which works out of the box or you can
3967 several problems, most important are limitation of cell content to 255
3968 chars and no support for charsets, so think carefully whether you want to
3969 enable this.</b>. For enabling this you need to set
3973 module Spreadsheet_Excel_Writer into php include path. The
3974 installation can be done by following command:</p>
3976 <pre>
3977 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3978 </pre>
3980 <p> First part of switches set we want to install beta version of that module
3981 (no stable version available yet) and then we tell pear we want to satisfy
3982 dependencies.</p>
3984 <p> If you are running in PHP safe mode, you will have to set
3987 modules are located, for example:</p>
3989 <pre>
3990 safe_mode_include_dir = /usr/local/lib/php
3991 </pre>
3995 <pre>
3996 cd phpMyAdmin
3997 mkdir tmp
3998 chmod o+rwx tmp
3999 </pre>
4003 what happens to my column comments stored in pmadb?</a></h4>
4005 <p> Automatic migration of a table's pmadb-style column comments to the native
4006 ones is done whenever you enter Structure page for this table.</p>
4013 <p> Our Bug Tracker is located at
4015 under the Bugs section.<br /><br />
4017 But please first discuss your bug with other users:<br />
4023 existing language, where do I start?</a></h4>
4025 <p> Always use the current SVN version of your language file.
4027 don't know how to get the SVN version, please ask one of the developers.
4028 <br />
4029 Please note that we try not to use HTML entities like &eacute; in
4030 the translations, since we define the right character set in the file.
4031 With HTML entities, the text on JavaScript messages would not
4032 display correctly.
4033 However there are some entities that need to be there, for quotes
4034 ,non-breakable spaces, ampersands, less than, greater than.<br />
4035 You can then put your translations, as a zip file to avoid losing special
4036 characters, on the sourceforge.net translation tracker.<br />
4037 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4038 list, because this is where we ask for translations of new messages.</p>
4042 phpMyAdmin. How should I proceed?</a></h4>
4047 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4048 </li>
4050 <li>generate patch with your changes:
4052 </li>
4055 tracker of the phpMyAdmin project</a>.
4056 </li>
4057 </ol>
4059 <p> Write access to the SVN tree is granted only to experienced developers who
4060 have already contributed something useful to phpMyAdmin.<br />
4066 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4068 <p> Please refer to
4069 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4070 </p>
4072 <!-- DEVELOPERS -->
4075 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4076 great features have been written by other people and you too can help to
4077 make phpMyAdmin a useful tool.</p>
4079 <p> If you're planning to contribute source, please read the following
4080 information:</p>
4086 it free from other code.<br />
4087 Commonly used functions should be added to
4090 <li>Obviously, you're free to use whatever coding style you want. But
4091 please try to keep your code as simple as possible: beginners are
4092 using phpMyAdmin as an example application.<br />
4093 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4094 compliant on one hand, they fit the
4097 coding standards</a>
4098 on the other hand. Please pay attention to this.</li>
4099 <li>Please try to keep up the file-naming conventions. Table-related stuff
4102 <li>Please don't use verbose strings in your code, instead add the string
4107 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4108 better debug and profile their code.<br />
4109 Please see the
4111 options for more information.<br />
4112 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4113 lost during its re-entry into Earth's atmosphere and in memory of the
4114 brave men and women who gave their lives for the people of Earth.</li>
4115 </ul>
4117 <!-- CREDITS -->
4120 <pre>
4121 phpMyAdmin - Credits
4122 ====================
4124 CREDITS, in chronological order
4125 -------------------------------
4128 * creator of the phpmyadmin project
4132 * multi-language version
4133 * various fixes and improvements
4135 * current project maintainer
4138 * started SourceForge phpMyAdmin project in March 2001
4139 * sync'ed different existing CVS trees with new features and bugfixes
4140 * multi-language improvements, dynamic language selection
4141 * current project maintainer
4142 * many bugfixes and improvements
4145 * rewrote and optimized javascript, DHTML and DOM stuff
4146 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4147 generate XHTML1.0 and CSS2 compliant codes
4148 * improved the language detection system
4149 * many bugfixes and improvements
4152 * database maintenance controls
4153 * table type code
4155 * DB-based configuration (Not completed)
4158 * many bugfixes and improvements
4161 * bookmarks feature
4162 * multiple dump feature
4163 * gzip dump feature
4164 * zip dump feature
4167 * various fixes
4168 * moderator of the phpMyAdmin former users forum at phpwizard.net
4174 * rewrote and fix dump code
4175 * bugfixes
4178 * rewrote dump code for PHP4
4179 * mySQL table statistics
4180 * bugfixes
4183 * main author of the version 2.1.0.1
4184 * bugfixes
4188 * abstract database interface (PMA_DBI) with MySQLi support
4189 * privileges administration
4191 * various features and fixes
4192 * German language file updates
4195 * automatic joins in QBE
4196 * links column in printview
4197 * Relation view
4200 * enhanced index creation/display feature
4201 * feature to use a different charset for HTML than for MySQL
4202 * improvements of export feature
4203 * various features and fixes
4204 * Czech language file updates
4207 (http://sf.net/projects/phpmysqlformgen/)
4208 * suggested the patch for multiple table printviews
4211 * built the patch for vertical display of table rows
4212 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4213 * Improvement of column/db comments
4214 * (MIME)-Transformations for columns
4215 * Use custom alias names for Databases in left frame
4216 * hierarchical/nested table display
4217 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4218 * new icon sets
4219 * vertical display of column properties page
4220 * some bugfixes, features, support, German language additions
4223 * japanese kanji encoding conversion feature
4226 * the Cookie authentication mode
4229 * table relation-links feature
4232 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4233 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4234 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4240 * phpMyAdmin logo (until June 2004)
4243 * blowfish library from the Horde project
4246 * mysqli support
4247 * many bugfixes and improvements
4250 * redesign for 2.6.0
4251 * phpMyAdmin sailboat logo (June 2004)
4254 * Representation at conferences
4257 * interface improvements
4258 * various bugfixes
4260 - Ivan A Kirillov
4261 * new relations Designer
4263 - Raj Kissu Rajandran (Google Summer of Code 2008)
4264 * BLOBstreaming support
4266 - Piotr Przybylski (Google Summer of Code 2008)
4267 * improved setup script
4269 And also to the following people who have contributed minor changes,
4270 enhancements, bugfixes or support for a new language since version 2.1.0:
4272 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4273 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4274 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4275 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4277 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4278 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4279 Luís V., Martijn W. van der Lee,
4280 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4284 Original Credits of Version 2.1.0
4285 ---------------------------------
4287 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4288 to create a web-based interface to MySQL using PHP3. Although I have not
4289 used any of his source-code, there are some concepts I've borrowed from
4290 him. phpMyAdmin was created because Peter told me he wasn't going to
4291 further develop his (great) tool.
4292 Thanks go to
4294 code for the check when dropping a table or database. He also suggested
4295 that you should be able to specify the primary key on tbl_create.php3. To
4296 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4297 well as a bug-report. Plus many smaller improvements.
4299 were introduced in 1.3.0 (including quite significant ones like the
4300 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4301 bug-fixes and help.
4303 language-independent by outsourcing the strings to a separate file. He
4304 also contributed the French translation.
4306 tbl_select.php3, a feature to display only some fields from a table.
4308 functions in tbl_change.php3. He also added the
4311 servers and is a regular contributor for bug-fixes.
4313 features for 2.0.6.
4314 The following people have contributed minor changes, enhancements, bugfixes
4315 or support for a new language:
4316 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4317 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4318 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4319 G. Wieggers.
4321 And thanks to everyone else who sent me email with suggestions, bug-reports
4322 and or just some feedback.
4323 </pre>
4329 <ul>
4331 - the default name of Apache's directory-level configuration file.</li>
4335 - a software application that enables a user to display and interact with
4336 text, images, and other information typically located on a web page at a
4337 website on the World Wide Web.</li>
4339 - a free software/open source data compression algorithm and program
4340 developed by Julian Seward.</li>
4342 - an important World Wide Web technology that enables a client web browser
4343 to request data from a program executed on the Web server.</li>
4345 - a log or record of changes made to a project.</li>
4347 - a computer system that accesses a (remote) service on another computer
4348 by some kind of network.</li>
4350 - a set of data values of a particular simple type, one for each row of
4351 the table.</li>
4353 - a packet of information sent by a server to a World Wide Web browser
4354 and then sent back by the browser each time it accesses that server.</li>
4356 - Comma-separated values</li>
4359 - an organized collection of data.</li>
4362 - a PHP module that extends PHP with additional functionality.</li>
4364 - a list of commonly asked question and there answers.</li>
4366 - one part of divided data/columns.</li>
4368 - a field or group of fields in a database record that point to a key
4369 field or group of fields forming a key of another database record in some
4370 (usually different) table.</li>
4372 - the free PDF library</li>
4374 GD Graphics Library</a> - a library by Thomas Boutell and others for
4375 dynamically manipulating images.</li>
4378 - gzip is short for GNU zip, a GNU free software file compression
4379 program.</li>
4381 - any machine connected to a computer network, a node that has a hostname.</li>
4383 - the unique name by which a network attached device is known on a network.</li>
4385 (HyperText Transfer Protocol)</a>
4386 - the primary method used to transfer or convey information on the World
4387 Wide Web.</li>
4390 additional security measures.</li>
4391 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4392 - a set of Internet-based services for servers using Microsoft Windows.</li>
4394 - a feature that allows quick access to the rows in a table.</li>
4396 - a data-oriented protocol used by source and destination hosts for
4397 communicating data across a packet-switched internetwork.</li>
4399 - a unique number that devices use in order to identify and communicate
4400 with each other on a network utilizing the Internet Protocol standard.</li>
4402 (Internet Server Application Programming Interface)</a>
4403 - the API of Internet Information Services (IIS).</li>
4405 - a business or organization that offers users access to the Internet and related services.</li>
4407 - a most commonly used standard method of lossy compression for
4408 photographic images.</li>
4414 - line of personal computers is designed, developed, manufactured, and
4415 marketed by Apple Computer.</li>
4416 <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>
4417 - the operating system which is included with all currently shipping Apple
4418 Macintosh computers in the consumer and professional markets.</li>
4420 - a cryptographic library.</li>
4422 - the MCrypt PHP extension.</li>
4423 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4424 - an Internet Standard for the format of e-mail.</li>
4426 - some sort of extension for the Apache Webserver.</li>
4428 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4429 Management System (DBMS).</li>
4431 - the improved MySQL client PHP extension.</li>
4433 - the MySQL client PHP extension.</li>
4435 - open standard for office documents.</li>
4436 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4437 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4439 (Portable Document Format)</a>
4440 - a file format developed by Adobe Systems for representing two
4441 dimensional documents in a device independent and resolution independent
4442 format.</li>
4444 - the PHP Extension and Application Repository.</li>
4446 - the perl-compatible regular expression functions for PHP</li>
4448 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4449 programming language used mainly for developing server-side applications
4450 and dynamic web content, and more recently, a broader range of software
4451 applications.</li>
4453 - a connection through which data is sent and received.</li>
4455 - Request for Comments (RFC) documents are a series of memoranda
4456 encompassing new research, innovations, and methodologies applicable to
4457 Internet technologies.</li>
4461 - represents a single, implicitly structured data item in a table.</li>
4463 - a computer system that provides services to other computing
4464 systems over a network.</li>
4465 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4466 - handlers for different table types</li>
4468 - a form of inter-process communication.</li>
4470 Sockets Layer)</a>
4471 - a cryptographic protocol which provides secure communication on the Internet.</li>
4473 - Structured Query Language</li>
4475 - a set of data elements (cells) that is organized, defined and stored as
4476 horizontal rows and vertical columns where each item can be uniquely
4477 identified by a label or key or by it?s position in relation to other items.</li>
4480 - a type of archive file format: the Tape ARchive format.</li>
4482 - one of the core protocols of the Internet protocol suite.</li>
4486 - a sequence of characters, conforming to a standardized format, that is
4487 used for referring to resources, such as documents and images on the
4488 Internet, by their location.</li>
4490 - A computer (program) that is responsible for accepting HTTP requests
4491 from clients and serving them Web pages.</li>
4493 - a W3C-recommended general-purpose markup language for creating
4494 special-purpose markup languages, capable of describing many different
4495 kinds of data.</li>
4497 - a popular data compression and archival format.</li>
4499 - an open-source, cross-platform data compression library by Jean-loup
4500 Gailly and Mark Adler.</li>
4501 </ul>
4511 </body>
4512 </html>