| blob | 8be832c55eb522883d3459fccf250561e3038b5a |
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'] = '/etc/swekey.conf';
522 </pre>
523 <p>
525 each user with their Swekey Id. It is important to place this file outside
526 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
528 users' information.<br /><br />
529 If you want to purchase a Swekey please visit
531 since this link provides funding for phpMyAdmin.
532 </p>
533 <!-- CONFIGURATION -->
537 users:</span> PHP does not seem to like
541 before saving a script you have modified.</p>
546 section to create one. This file only needs to contain the parameters you want to
547 change from their corresponding default value in
550 <p> The parameters which relate to design (like colors) are placed in
553 your site specific code to be included on start and end of each page.</p>
557 (with full path) to your phpMyAdmin installation's directory.
560 some web servers are case–sensitive.
563 Starting with version 2.3.0, it is advisable to try leaving this
564 blank. In most cases phpMyAdmin automatically detects the proper
565 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
566 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
567 A good test is to browse a table, edit a row and save it. There should
568 be an error message if phpMyAdmin is having trouble auto–detecting
569 the correct value. If you get an error that this must be set or if
570 the autodetect code fails to detect your path, please post a bug
571 report on our bug tracker so we can improve the code.</dd>
575 with master / foreign – tables (see
577 <br />
578 If you tried to set this up and it does not work for you, have a look on
580 use it. You will find a link that will analyze why those features have
581 been disabled.<br />
582 If you do not want to use those features set this variable to
586 <dd>A warning is displayed on the main page if Suhosin is detected.
588 from appearing.</dd>
592 domain to call phpMyAdmin inside a frame, and is a potential security
593 hole allowing cross-frame scripting attacks.</dd>
597 algorithm to encrypt the password.<br />
599 passphrase of your choice. It will be used internally by the blowfish
600 algorithm: you won’t be prompted for this passphrase. The maximum
603 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
604 makes a bit weaker security as this generated secret is stored in
605 session and furthermore it makes impossible to recall user name from
606 cookie.</dd>
610 MySQL servers. Therefore, a
612 been added which contains the login information for the different servers.
613 The first
615 contains the hostname of the first server, the second
617 the hostname of the second server, etc. In
619 server definition, however you can put as many as you need in
621 have to define all settings, just those you need to change).</dd>
625 $i-th MySQL-server. E.g. localhost.</dd>
630 ignores this port number and connects with the socket, so if you want
631 to connect to a port different from the default port, use
634 </dd>
638 To determine the correct socket, check your MySQL configuration or, using the
640 Among the resulting information displayed will be the socket used.</dd>
643 <dd>Whether to enable SSL for connection to MySQL server.
644 </dd>
647 <dd>What type connection to use with the MySQL server. Your options are
649 is nearly guaranteed to be available on all MySQL servers, while
650 sockets are not supported on some platforms.<br /><br />
652 To use the socket mode, your MySQL server must be on the same machine
653 as the Web server.</dd>
656 <dd>What php MySQL extension to use for the connection. Valid options are:
657 <br /><br />
660 The classic MySQL extension. This is the recommended and default
661 method at this time.<br /><br />
664 The improved MySQL extension. This extension became available
665 with php 5.0.0 and is the recommended way to connect to a server
669 <dd>Whether to use a compressed protocol for the MySQL server connection
670 or not (experimental).<br />
676 </dt>
678 all relational features (see
680 and, for a MySQL server previous to 4.1.2 or running with
683 authentication mode).<br /><br />
686 cookie authentication modes (or 'config'
687 authentication mode since phpMyAdmin 2.2.1), you need to supply the
692 This account is used to check what databases the user will see at
693 login.<br />
697 In phpMyAdmin versions before 2.2.5, those were called
701 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
702 <dd>Whether config or cookie or
704 should be used for this server.
706 is the plain old way: username and password are stored in
708 <li>'cookie' authentication mode
710 2.2.3 allows you to log in as any valid MySQL user with the
711 help of cookies. Username and password are stored in
712 cookies during the session and password is deleted when it
713 ends. This can also allow you to log in in arbitrary server if
714 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
715 </li>
716 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
717 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
718 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
719 <li>'signon' authentication mode
721 as introduced in 2.10.0 allows you to log in from prepared PHP
722 session data. This is useful for implementing single signon
723 from another application. Sample way how to seed session is in
729 </ul>
732 for more information.
733 </dd>
735 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
736 </dt>
737 <dd>
739 names for hardware authentication. Leave empty to deactivate this feature.
740 </dd>
744 </dt>
745 <dd>
746 When using auth_type = 'config', this is the user/password-pair
747 which phpMyAdmin will use to connect to the
748 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
749 cookie authentication is used and should be empty.</dd>
751 <span
753 </dt>
754 <dd>
755 Allow attempt to log in without password when a login with password
756 fails. This can be used together with http authentication, when
757 authentication is done some other way and phpMyAdmin gets user name
758 from auth and uses empty password for connecting to MySQL. Password
759 login is still tried first, but as fallback, no password method is
760 tried.</dd>
763 </dt>
764 <dd>
765 If set to a (an array of) database name(s), only this (these) database(s)
766 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
767 database(s) name(s) may contain MySQL wildcards characters
771 This setting is an efficient way to lower the server load since the
772 latter does not need to send MySQL requests to build the available
774 privileges rules of the MySQL database server</span>. If set, it just
775 means only these databases will be displayed but
777 <br /><br />
779 An example of using more that one database:
781 <br /><br />
783 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
784 databases in the left frame, so that you can individually arrange your databases.<br />
785 If you want to have certain databases at the top, but don't care about the others, you do not
786 need to specify all other databases. Use:
788 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
789 order.</dd>
792 </dt>
793 <dd>Regular expression for hiding some databases. This only hides them
794 from listing, but a user is still able to access them (using, for example,
795 the SQL query area). To limit access, use the MySQL privilege system.
796 <br /><br />
801 More information on regular expressions can be found in the
803 PCRE pattern syntax</a> portion of the PHP reference manual.
804 </dd>
807 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
808 this string will be displayed instead of the hostname in the pull-down
809 menu on the main page. This can be useful if you want to show only
810 certain databases on your system, for example. For HTTP auth, all
811 non-US-ASCII characters will be stripped.</dd>
815 </dt>
816 <dd>The name of the database containing the linked-tables infrastructure.
817 <br /><br />
820 section in this document to see the benefits of this infrastructure,
821 and for a quick way of creating this database and the needed tables.
822 <br /><br />
824 If you are the only user of this phpMyAdmin installation, you can
825 use your current database to store those special tables; in this
826 case, just put your current database name in
828 set this parameter to the name of your central database containing
829 the linked-tables infrastructure.</dd>
833 </dt>
835 useful for queries you often run.<br /><br />
837 To allow the usage of this functionality:
839 <li>enter the table name in
841 </ul>
842 </dd>
846 </dt>
848 which field is a key in another table (a foreign key). phpMyAdmin
849 currently uses this to
850 <ul><li>make clickable, when you browse the master table, the data values
851 that point to the foreign table;</li>
853 when browsing the master table, if you move the mouse to a column
854 containing a foreign key (use also the 'table_info' table);<br />
857 <li>in edit/insert mode, display a drop-down list of possible foreign
861 <li>display links on the table properties page, to check referential
862 integrity (display missing foreign keys) for each described key;
863 </li>
867 schema of your database (also uses the table_coords table).</li>
868 </ul>
870 The keys can be numeric or character.<br /><br />
872 To allow the usage of this functionality:
875 infrastructure</li>
876 <li>put the relation table name in
878 <li>now as normal user open phpMyAdmin and for each one of your
879 tables where you want to use this feature, click
881 </li>
882 </ul>
886 future development of the cross-db relations.
887 </dd>
891 </dt>
892 <dd>
893 Since release 2.3.0 you can describe, in a special 'table_info'
894 table, which field is to be displayed as a tool-tip when moving the
895 cursor over the corresponding key.<br />
896 This configuration variable will hold the name of this special
897 table. To allow the usage of this functionality:
899 <li>put the table name in
901 <li>then for each table where you want to use this feature,
903 to choose the field.</li>
904 </ul>
906 </dd>
910 </dt>
913 the relations between your tables. To do this it needs two tables
918 schema output).<br /><br />
922 To allow the usage of this functionality:
925 infrastructure</li>
926 <li>put the correct table names in
929 </ul>
932 </dd>
936 </dt>
938 Since release 2.3.0 you can store comments to describe each column for
940 <br /><br />
942 Starting with release 2.5.0, comments are consequently used on the table
943 property pages and table browse view, showing up as tool-tips above the
944 column name (properties page) or embedded within the header of table in
945 browse view. They can also be shown in a table dump. Please see the
946 relevant configuration directives later on.<br /><br />
948 Also new in release 2.5.0 is a MIME-transformation system which is also
950 Transformations</a> for further information. To use the
951 MIME-transformation system, your column_info table has to have the three
952 new fields 'mimetype', 'transformation', 'transformation_options'.
953 <br /><br />
955 To allow the usage of this functionality:
957 infrastructure</li>
958 <li>put the table name in
962 <pre>
963 ALTER TABLE `pma_column_comments`
964 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
965 ADD `transformation` VARCHAR( 255 ) NOT NULL,
966 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
967 </pre>
970 renamed from<br />
973 </ul>
974 </dd>
978 </dt>
981 all queries you entered manually into the phpMyAdmin interface. If you
982 don't want to use a table-based history, you can use the JavaScript-based
983 history. Using that, all your history items are deleted when closing the
984 window.<br /><br />
986 Using
988 you can specify an amount of history items you want to have on hold. On
989 every login, this list gets cut to the maximum amount.<br /><br />
991 The query history is only available if JavaScript is enabled in your
992 browser.<br /><br />
994 To allow the usage of this functionality:
997 infrastructure</li>
999 </li>
1000 </ul>
1001 </dd>
1005 </dt>
1007 to visually manage the relations.
1008 <br /><br />
1010 To allow the usage of this functionality:
1013 infrastructure</li>
1015 </li>
1016 </ul>
1017 </dd>
1020 </dt>
1022 column_info table got enhanced with three new fields. If the above variable
1024 latest table structure available. If not, it will emit a warning to the
1025 superuser.<br /><br />
1027 You can disable this checking behavior by setting the variable to false,
1028 which should offer a performance increase.<br /><br />
1030 Recommended to set to FALSE, when you are sure, your table structure is
1031 up to date.</dd>
1033 boolean</dt>
1034 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1035 </dd>
1036 <dt><span id="cfg_Servers_AllowNoPasswordRoot">$cfg['Servers'][$i]['AllowNoPasswordRoot']</span>
1037 boolean</dt>
1038 <dd>Whether to allow access to root user without password. The default
1040 to a MySQL server with was left with an empty password for root.
1041 </dd>
1044 </dt>
1046 authentication is disabled.<br /><br />
1049 all deny rules followed by allow rules. Access is allowed by default. Any
1050 client which does not match a Deny command or does match an Allow command
1051 will be allowed access to the server. <br /><br />
1054 applies all allow rules followed by deny rules. Access is denied by
1055 default. Any client which does not match an Allow directive or does
1056 match a Deny directive will be denied access to the server.<br /><br />
1058 If your rule order is set to 'explicit', the authentication is
1059 performed in a similar fashion to rule order 'deny,allow', with the
1063 and was available in Apache by specifying allow and deny rules without
1064 setting any order.<br /><br />
1066 Please also see <a
1068 address behind proxies.
1069 </dd>
1071 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1072 </dt>
1073 <dd>The general format for the rules is as such:
1075 <pre>
1077 </pre>
1082 well (please note that those containing SERVER_ADDRESS might not be
1083 available on all webservers):
1084 <pre>
1090 </pre>
1092 Having an empty rule list is equivalent to either using
1098 following work:<br />
1100 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1101 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1102 But the following does not work:<br />
1105 </dd>
1106 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1107 <dd>Name of session which will be used for signon authentication method.
1108 </dd>
1110 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1111 </dd>
1113 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1114 </dd>
1117 <dd>If you have more than one server configured, you can set
1119 that server when phpMyAdmin is started, or set it to 0 to be given a
1120 list of servers without logging in.<br />
1122 MUST be set to that server.</dd>
1125 <dd>The maximum number of database names to be displayed in the
1126 navigation frame and the database list.</dd>
1129 <dd>The maximum number of table names to be displayed in the
1130 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1131 when in Light mode.</dd>
1134 <dd>The maximum number of characters when a SQL query is displayed. The
1135 default limit of 1000 should be correct to avoid the display of tons
1136 of hexadecimal codes that represent BLOBs, but some users have real
1137 SQL queries that are longer than 1000 characters. Also, if a query's
1138 length exceeds this limit, this query is not saved in the history.</dd>
1141 <dd>Defines whether to use GZip output buffering for increased
1143 Set to true/false for enabling/disabling. When set to 'auto' (string),
1144 phpMyAdmin tries to enable output buffering and will automatically disable
1145 it if your browser has some problems with buffering. IE6 with a certain patch
1146 is known to cause data corruption when having enabled buffering.</dd>
1149 <dd>Whether persistent connections should be used or not (mysql_connect or
1150 mysql_pconnect).</dd>
1156 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1157 to zero, no time limit is imposed.<br />
1158 This setting is used while importing/exporting dump files but has no
1159 effect when PHP is running in safe mode.</dd>
1162 <dd>Set the number of bytes a script is allowed to allocate. If number set
1163 to zero, no limit is imposed.<br />
1164 This setting is used while importing/exporting dump files but has no
1165 effect when PHP is running in safe mode.<br />
1169 <dd>Mark used tables and make it possible to show databases with locked
1174 generated by phpMyAdmin should be displayed or not.</dd>
1177 <dd>Defines whether normal users (non-administrator) are allowed to
1178 delete their own database or not. If set as FALSE, the link "Drop
1180 mydatabase" will be rejected. Quite practical for
1182 customers.<br />
1183 Please note that this limitation of SQL queries is not as strict as
1184 when using MySQL privileges. This is due to nature of SQL queries
1185 which might be quite complicated. So this choice should be viewed as
1186 help to avoid accidental dropping rather than strict privilege
1187 limitation.</dd>
1191 displayed when you're about to lose data.</dd>
1194 <dd>Define whether the previous login should be recalled or not in cookie
1195 authentication mode.<br /><br />
1197 This is automatically diabled if you do not have configured
1199 </dd>
1206 means that it will be kept for existing session. This is recommended
1207 for not trusted environments.</dd>
1210 <dd>If enabled (default), logout deletes cookies for all servers,
1211 otherwise only for current one. Setting this to false makes it easy to
1212 forget to log out from other server, when you are using more of
1213 them.</dd>
1219 <dd>Define whether phpMyAdmin will continue executing a multi-query
1220 statement if one of the queries fails. Default is to abort execution.</dd>
1223 <dd>Define whether phpMyAdmin will output the results of each query of a
1224 multi-query statement embedded into the
1229 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1230 <br /><br />
1233 MySQL servers behind the firewall where your
1235 </dd>
1238 <dd>Defines whether to use a select-based menu and display only the current
1239 tables in the left frame (smaller page). Only in Non-Lightmode you can
1240 use the feature to display nested folders using
1242 </dd>
1245 <dd>In light mode, defines whether to display the names of databases (in the
1246 selector) using a tree, see also
1248 </dd>
1251 <dd>The string used to separate the parts of the database name when showing
1252 them in a tree.</dd>
1255 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1256 This means if you have tables like 'first__second__third' this will be
1258 If set to FALSE or empty, the feature is disabled. NOTE: You should
1259 not use this separator at the beginning or end of a
1260 table name or multiple times after another without any other
1261 characters in between.</dd>
1264 <dd>Defines how many sublevels should be displayed when splitting
1265 up tables by the above separator.</dd>
1268 <dd>Defines whether to display table comment as tool-tip in left frame or
1269 not.</dd>
1272 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1273 comment and the real name. That means that if you have a table called
1274 'user0001' and add the comment 'MyName' on it, you will see the name
1275 'MyName' used consequently in the left frame and the tool-tip shows
1276 the real name of the DB.</dd>
1279 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1281 When setting this to 'nested', the Alias of the Tablename is only used
1282 to split/nest the tables according to the
1284 directive. So only the folder is called like the Alias, the tablename itself
1285 stays the real tablename.</dd>
1288 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1291 <dd>Enter URL where logo in the navigation frame will point to.
1292 For use especially with self made theme which changes this.
1301 <dd>Defines whether or not to display a server choice at the top of the left frame.
1302 Defaults to FALSE.</dd>
1304 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1305 Defaults to FALSE (drop-down).</dd>
1307 <dd>Defines whether to display database choice in light navigation frame as links
1308 instead of in a drop-down. Defaults to 'auto' - on main page list is
1309 shown, when database is selected, only drop down is displayed.</dd>
1312 <dd>Defines the tab displayed by default when clicking the small
1313 icon next to each table name in the navigation panel. Possible
1319 <dd>Defines whether or not to display space usage and statistics about databases
1320 and tables.<br />
1321 Note that statistics requires at least MySQL 3.23.3 and that, at this
1322 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1325 <dd>Defines whether to display detailed server information on main page.
1326 You can additionally hide more information by using
1328 </dd>
1333 </dt>
1336 not at the starting main (right) frame. This setting
1337 does not check MySQL commands entered directly.<br /><br />
1339 Please note that to block the usage of phpinfo() in scripts, you
1346 hard coded password value in the configuration file, end users can't
1347 be allowed to change their passwords.</dd>
1350 <dd>Defines whether to suggest a database name on the
1354 <dd>Defines whether navigation bar buttons and the right panel top menu
1355 contain text or symbols only. A value of TRUE displays icons, FALSE
1356 displays text and 'both' displays both icons and text.</dd>
1359 <dd>Defines whether a user should be displayed a
1363 <dd>Number of rows displayed when browsing a result set. If the result set
1370 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1374 from editing when browsing a table's content. Valid values are:
1379 </ul>
1380 </dd>
1383 <dd>Defines whether or not MySQL functions fields should be initially
1384 displayed in edit/insert mode. Since version 2.10, the user can
1385 toggle this setting from the interface.
1386 </dd>
1389 <dd>Defines which type of editing controls should be used for CHAR and
1390 VARCHAR fields. Possible values are:
1391 <ul><li>input - this allows to limit size of text to size of field in
1392 MySQL, but has problems with newlines in fields</li>
1393 <li>textarea - no problems with newlines in fields, but also no
1394 length limitations</li>
1395 </ul>
1396 Default is old behavior so input.</dd>
1402 <dd>If there are fewer items than this in the set of foreign keys, then a
1403 drop-down box of foreign keys is presented, in the style described by the
1405 setting.</dd>
1408 <dd>For the foreign key drop-down fields, there are several methods of
1409 display, offering both the key and value data. The contents of the
1410 array should be one or both of the following strings:
1416 </dt>
1417 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1418 creating a dump file</dd>
1421 </dt>
1422 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1423 compressed exports. This doesn't affect smaller dumps and allows users to
1424 create larger dumps that won't otherwise fit in memory due to php
1425 memory limit. Produced files contain more GZip/BZip2 headers, but all
1426 normal programs handle this correctly.</dd>
1430 mainframe.</dd>
1434 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1439 <dd>How many columns will be utilized to display the tables on the
1440 database property view? Default is 1 column. When setting this to a
1441 value larger than 1, the type of the database will be omitted for more
1442 display space.</dd>
1446 <dd>Defines the tab displayed by default on server view. Possible
1453 <dd>Defines the tab displayed by default on database view. Possible
1458 <dd>Defines the tab displayed by default on table view. Possible
1465 points to the MySQL documentation (type depends
1466 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1467 generated.<br />
1469 for more information about MySQL manuals and their types.</dd>
1472 <dd>Type of MySQL documentation:
1478 </ul>
1479 </dd>
1482 <dd>Defines the default language to use, if not browser-defined or
1483 user-defined.<br />
1485 this setting.</dd>
1488 <dd>Defines the default connection collation to use, if not
1489 user-defined.<br />
1494 <dd>Force: always use this language (must be defined in the
1498 <dd>Limit list of available languages to those matching the given regular
1499 expression. For example if you want only Czech and English, you should
1503 <dd>Default character set to use for recoding of MySQL queries. This must be
1504 enabled and it's described by
1506 option.<br />
1507 You can give here any character set which is in
1509 array and this is just default choice, user can select any of them.</dd>
1512 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1513 support (compiled in or module) in PHP to allow MySQL queries recoding
1514 and used language file must have it enabled (by default only these
1515 which are in Unicode, just to avoid losing some characters).<br /><br />
1518 in the Export page, to choose the character set when exporting a file.
1520 </dd>
1523 <dd>You can select here which functions will be used for character set
1524 conversion. Possible values are:
1525 <ul><li>auto - automatically use available one (first is tested
1526 iconv, then recode)</li>
1529 </ul>
1530 Default is auto.</dd>
1533 <dd>Specify some parameters for iconv used in charset conversion. See
1536 used, so that invalid characters will be transliterated.</dd>
1539 <dd>Available character sets for MySQL conversion. You can add your own (any of
1540 supported by recode/iconv) or remove these which you don't use.
1541 Character sets will be shown in same order as here listed, so if you
1542 frequently use some of these move them to the top.</dd>
1547 default empty, you need to fill in some trusted proxy servers if you
1548 want to use rules for IP addresses behind proxy.<br /><br />
1550 The following example specifies that phpMyAdmin should trust a
1552 <pre>
1553 $cfg['TrustedProxies'] =
1555 </pre>
1556 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1557 client's IP address as usual.
1558 </dd>
1562 MIME transformations.<br />
1563 Possible values are:
1564 <ul><li>auto - automatically detect, this is a bit expensive
1566 according to your server real possibilities</li>
1569 </ul>
1570 Default is auto.
1571 </dd>
1574 <dd>
1575 We normally check the permissions on the configuration file to ensure
1576 it's not world writable. However, phpMyAdmin could be installed on
1577 a NTFS filesystem mounted on a non-Windows server, in which case the
1578 permissions seems wrong but in fact cannot be detected. In this case
1580 </dd>
1584 </dd>
1586 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1587 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1588 </dt>
1589 <dd>The background styles used for both the frames.
1592 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1594 <dd>The style used for the pointer in the navi frame.
1598 </dt>
1599 <dd>The color used for the database name in the navi frame.
1608 </dd>
1612 <dd>The style used for table headers. See
1617 </dd>
1621 </dd>
1623 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1625 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1627 </dt>
1629 The former feature highlights the row over which your mouse is passing
1630 and the latter lets you visually mark/unmark rows by clicking on
1631 them.<br />
1636 <dd>You put here a valid CSS font family value, for example
1641 <dd>You put here a valid CSS font family value, for example
1655 </dt>
1657 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1659 The Char* values are used for CHAR and VARCHAR editing (if configured
1663 </dt>
1667 </dt>
1668 <dd>Defines if the whole textarea of the query box will be selected on
1669 click.</dd>
1672 </dt>
1673 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1674 editing.</dd>
1677 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1678 Can be turned off by a toggle button on the browse page.</dd>
1682 </dt>
1683 <dd>Defines the place where modify and delete links would be put when
1684 tables contents are displayed (you may have them displayed both at the
1685 left and at the right).
1691 </dt>
1693 Define which one is displayed by default. The first mode displays each
1694 row on a horizontal line, the second rotates the headers by 90
1695 degrees, so you can use descriptive headers even though fields only
1696 contain small values and still print them out. The vertical mode sorts
1697 each row on a vertical lineup.<br /><br />
1699 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1700 the rotation of the header for horizontalflipped is done via CSS. If
1701 set to 'fake' PHP does the transformation for you, but of course this
1702 does not look as good as CSS.</dd>
1706 string or integer</dt>
1707 <dd>When editing/creating new columns in a table all fields normally get
1708 lined up one field a line. (default: 'horizontal'). If you set this to
1709 'vertical' you can have each field lined up vertically beneath each
1710 other. You can save up a lot of place on the horizontal direction and
1711 no longer have to scroll. If you set this to integer, editing of fewer
1712 columns will appear in 'vertical' mode, while editing of more fields
1713 still in 'horizontal' mode. This way you can still effectively edit
1714 large number of fields, while having full view on few of them.</dd>
1718 </dt>
1720 display of column comments in Browse or Property display. In browse
1721 mode, the comments are shown inside the header. In property mode,
1722 comments are displayed using a CSS-formatted dashed-line below the
1723 name of the field. The comment is shown as a tool-tip for that field.
1724 </dd>
1736 <dd>Whether to display a link to validate a query in any SQL Query box.
1743 <dd>
1744 The name of the directory where
1746 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1747 are available under a drop-down box when you click the database or
1748 table name, then the Import tab.
1749 <br /><br />
1751 If you want different directory for each user, %u will be replaced
1752 with username.<br /><br />
1756 compressed formats is enabled).<br /><br />
1758 This feature is useful when your file is too big to be uploaded via
1760 uploads are disabled in PHP.<br /><br />
1762 Please note that if PHP is running in safe mode, this directory must
1763 be owned by the same user as the owner of the phpMyAdmin scripts.
1764 <br /><br />
1768 alternatives.
1769 </dd>
1772 <dd>
1773 The name of the directory where dumps can be saved.<br /><br />
1775 If you want different directory for each user, %u will be replaced
1776 with username.<br /><br />
1778 Please note that the directory must exist and has to be writable for
1779 the user running webserver.<br /><br />
1781 Please note that if PHP is running in safe mode, this directory must
1782 be owned by the same user as the owner of the phpMyAdmin scripts.
1783 </dd>
1786 <dd>
1787 The name of the directory where temporary files can be stored.
1788 <br /><br />
1790 This is needed for native MS Excel export, see
1796 <br /><br />
1798 If the directory where phpMyAdmin is installed is subject to an
1800 temporary directory in some directory accessible by the web
1801 server. However for security reasons, this directory should be outside
1802 the tree published by webserver. If you cannot avoid having this
1803 directory published by webserver, place at least an empty
1805 possible.
1806 <br /><br />
1808 This directory should have as strict permissions as possible as the only
1809 user required to access this directory is the one who runs the
1810 webserver. If you have root privileges, simply make this user owner of
1811 this directory and make it accessible only by it:
1812 <br /><br />
1814 <pre>
1815 chown www-data:www-data tmp
1816 chmod 700 tmp
1817 </pre>
1819 If you cannot change owner of the directory, you can achieve a similar
1822 <pre>
1823 chmod 700 tmp
1824 setfacl -m "g:www-data:rwx" tmp
1825 setfacl -d -m "g:www-data:rwx" tmp
1826 </pre>
1828 If neither of above works for you, you can still make the directory
1830 system reading and writing data in this directory.
1831 </dd>
1834 <dd>
1835 In this array are defined default parameters for export, names of
1836 items are similar to texts seen on export page, so you can easily
1837 identify what they mean.
1838 </dd>
1841 <dd>
1842 In this array are defined default parameters for import, names of
1843 items are similar to texts seen on import page, so you can easily
1844 identify what they mean.
1845 </dd>
1848 <dd>
1849 Repeat the headers every X cells, or 0 to deactivate.
1850 </dd>
1858 </dt>
1859 <dd>
1860 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1861 or icon is always displayed on the left panel. If JavaScript is enabled in
1862 your browser, a click on this opens a distinct query window, which is
1863 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1864 changes to display a query box.<br /><br />
1866 The size of this query window can be customized with
1868 - both integers for the size in pixels. Note that normally, those
1870 theme you are using.<br /><br />
1874 opens the query window and puts the current query
1875 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1876 query in the right panel's query box.
1877 <br /><br />
1878 The usage of the JavaScript query window is recommended if you have a
1879 JavaScript enabled browser. Basic functions are used to exchange quite
1880 a few variables, so most 4th generation browsers should be capable to
1881 use that feature. It currently is only tested with Internet Explorer 6
1882 and Mozilla 1.x.
1883 <br /><br />
1885 to a table, which has to be created by you (see <a
1887 all your queries will be appended to the form, but only as long as
1888 your window is opened they remain saved.
1889 <br /><br />
1890 When using the JavaScript based query window, it will always get
1891 updated when you click on a new table/db to browse and will focus if
1892 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1893 the query window by checking the box "Do not overwrite this query from
1894 outside the window" below the query textarea. Then you can browse
1895 tables/databases in the background without losing the contents of the
1896 textarea, so this is especially useful when composing a query with
1897 tables you first have to look in. The checkbox will get automatically
1898 checked whenever you change the contents of the textarea. Please
1899 uncheck the button whenever you definitely want the query window to
1900 get updated even though you have made alterations.
1901 <br /><br />
1904 <br /><br />
1905 The query window also has a custom tabbed look to group the features.
1907 default tab to be used when opening the query window. It can be set to
1908 either 'sql', 'files', 'history' or 'full'.</dd>
1914 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1916 If the approximate row count as returned by
1919 count will be used.
1920 </dd>
1922 <dd>For VIEWs, since obtaining the exact count could have an
1923 impact on performance, this value is the maximum to be displayed, using
1925 any row counting.
1926 </dd>
1930 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1932 page. By clicking on the button 'toggle scratchboard' on the page
1933 where you edit x/y coordinates of those elements you can activate a
1934 scratchboard where all your elements are placed. By clicking on an
1935 element, you can move them around in the pre-defined area and the x/y
1936 coordinates will get updated dynamically. Likewise, when entering a
1937 new position directly into the input field, the new position in the
1938 scratchboard changes after your cursor leaves the input field.<br />
1939 You have to click on the 'OK'-button below the tables to save the new
1940 positions. If you want to place a new element, first add it to the
1941 table of elements and then you can drag the new element around.<br />
1942 By changing the paper size and the orientation you can change the size
1943 of the scratchboard as well. You can do so by just changing the
1944 dropdown field below, and the scratchboard will resize automatically,
1945 without interfering with the current placement of the elements.<br />
1946 If ever an element gets out of range you can either enlarge the paper
1947 size or click on the 'reset' button to place all elements below each
1948 other.<br />
1950 get this control to work. The basic Drag&Drop script functionality
1951 was kindly borrowed from www.youngpup.net and is underlying so
1952 specific license.</dd>
1955 <dd>Sorts database and table names according to natural order (for example,
1956 t1, t2, t10). Currently implemented in the left panel (Light mode)
1957 and in Database view, for the table list.</dd>
1961 closed state. A value of 'open' does the reverse.</dd>
1967 <dd>Allows you to specify window's title bar. Following magic string can
1968 be used to get special values:
1969 <dl>
1975 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1984 </dl>
1985 </dd>
1995 </dd>
1998 <dd>If theme manager is active, use this as the path of the subdirectory
1999 containing all the themes.</dd>
2013 </dt>
2014 <dd>Default queries that will be displayed in query boxes when user didn't
2015 specify any. Use %d for database name, %t for table name and %f for a
2016 comma separated list of field names. Note that %t and %f are only
2020 <dd>
2021 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
2022 default we use HTML to format the query, but you can disable this by
2024 </dd>
2027 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2028 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2029 query inside a bracket is indented. By changing
2032 specifies the units of the indent amount that you specified. This is
2033 used via stylesheets.</dd>
2036 <dd>This array is used to define the colours for each type of element of
2037 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2039 If you specify an empty string for the color of a class, it is ignored
2040 in creating the stylesheet.
2041 You should not alter the class names, only the colour strings.<br />
2062 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2066 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2067 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2068 </ul>
2069 </dd>
2073 <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,
2074 as originally published on
2076 <br />
2077 For help in setting up your system to use the service, see the
2079 </dd>
2083 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2084 and any password, so we use those by default. Instead, if
2085 you have an account with them, you can put your login details
2086 here, and it will be used in place of the anonymous login.</dd>
2087 </dl>
2088 </dd>
2091 <dd><b>DEVELOPERS ONLY!</b></dd>
2094 <dd><b>DEVELOPERS ONLY!</b><br />
2095 Enable logging queries and execution times to be displayed in the bottom
2096 of main page (right frame).</dd>
2099 <dd><b>DEVELOPERS ONLY!</b><br />
2100 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2101 the code.<br />
2102 For help in setting up your system to this, see the
2106 <dd><b>DEVELOPERS ONLY!</b><br />
2107 Enable profiling support for phpMyAdmin. This will append a chunk of data
2108 to the end of every page displayed in the main window with profiling
2109 statistics for that page.<br />
2110 You may need to increase the maximum execution time for this to
2111 complete successfully.<i>Profiling was removed from the code for
2112 version 2.9.0 due to licensing issues.</i></dd>
2114 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2115 <dd><b>DEVELOPERS ONLY!</b><br />
2116 When profiling data is displayed, this variable controls the threshold of
2117 display for any profiling data, based on the average time each time has
2118 taken. If it is over the threshold it is displayed, otherwise it is not
2119 displayed. This takes a value in milliseconds. In most cases you don't need
2120 to edit this.</dd>
2123 <dd>All possible types of a MySQL column. In most cases you don't need to
2124 edit this.</dd>
2127 <dd>Possible attributes for fields. In most cases you don't need to edit
2128 this.</dd>
2131 <dd>A list of functions MySQL supports. In most cases you don't need to
2132 edit this.</dd>
2135 <dd>Mapping of column types to meta types used for preferring displayed
2136 functions. In most cases you don't need to edit this.</dd>
2139 <dd>Functions preferred for column meta types as defined in
2140 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2141 to edit this.</dd>
2144 <dd>Functions selected by default when inserting/changing row, Functions
2145 are defined for meta types from
2147 <code>first_timestamp</code>, which is used for first timestamp column
2148 in table.</dd>
2151 <dd>Operators available for search operations on numeric and date fields.
2152 </dd>
2155 <dd>Operators available for search operations on character fields.
2156 Note that we put <code>LIKE</code> by default instead of
2157 <code>LIKE %...%</code>, to avoid unintended performance problems
2158 in case of huge tables.</dd>
2161 <dd>Operators available for search operations on enum fields.</dd>
2164 <dd>Additional operators available for search operations when the
2165 field can be null.</dd>
2167 </dl>
2169 <!-- TRANSFORMATIONS -->
2175 </ol>
2179 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2181 section</a> on how to do so.</p>
2183 <p> You can apply different transformations to the contents of each field. The
2184 transformation will take the content of each field and transform it with
2185 certain rules defined in the selected transformation.</p>
2187 <p> Say you have a field 'filename' which contains a filename. Normally you would
2188 see in phpMyAdmin only this filename. Using transformations you can transform
2189 that filename into a HTML link, so you can click inside of the phpMyAdmin
2190 structure on the field's link and will see the file displayed in a new browser
2191 window. Using transformation options you can also specify strings to
2192 append/prepend to a string or the format you want the output stored in.</p>
2194 <p> For a general overview of all available transformations and their options,
2195 you can consult your
2196 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2197 installation.</p>
2199 <p> For a tutorial on how to effectively use transformations, see our
2201 the official phpMyAdmin homepage.</p>
2205 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2206 clicking on the 'Structure' link for a table). There click on
2207 "Change" (or change icon) and there you will see three new fields at
2208 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2209 'Transformation options'.</p>
2211 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2212 that corresponds to the column's contents. Please note that
2213 transformations are inactive as long as no MIME-type is selected.</li>
2215 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2216 hopefully growing amount of pre-defined transformations. See below for information on
2217 how to build your own transformation.<br />
2219 There are global transformations and mimetype-bound transformations. Global transformations
2220 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2221 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2222 transformations which operate on the main mimetype (like 'image'), which will most likely
2223 take the subtype into regard, and those who only operate on a
2224 specific subtype (like 'image/jpeg').<br />
2226 You can use transformations on mimetypes for which the function was not defined for. There
2227 is no security check for you selected the right transformation, so take care of what the
2228 output will be like.</li>
2230 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2231 transform-function specific options here. Usually the transforms can operate with default
2232 options, but it is generally a good idea to look up the overview to see which options are
2233 necessary.<br />
2235 Much like the ENUM/SET-Fields, you have to split up several options using the format
2236 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2237 parsed as an array, leaving the first value the first element in the array, and so
2238 forth.<br />
2240 If you want to specify a MIME character set you can define it in the transformation_options.
2241 You have to put that outside of the pre-defined options of the specific mime-transform,
2243 for which you can specify 2 options and you want to append a character set, enter "'first
2244 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2246 </ul>
2250 <p> All mimetypes and their transformations are defined through single files in
2251 the directory 'libraries/transformations/'.</p>
2253 <p> They are stored in files to ease up customization and easy adding of new
2254 transformations.</p>
2256 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2257 always work. It makes no sense to apply a transformation to a mimetype, the
2258 transform-function doesn't know to handle.</p>
2260 <p> One can, however, use empty mime-types and global transformations which should work
2261 for many mimetypes. You can also use transforms on a different mimetype they where built
2262 for, but pay attention to option usage as well as what the transformation does to your
2263 field.</p>
2265 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2266 any other transform function and provides some basic functions.</p>
2268 <p> There are 5 possible file names:</p>
2270 <ol><li>A mimetype+subtype transform:<br /><br />
2272 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2274 Please not that mimetype and subtype are separated via '_', which shall
2275 not be contained in their names. The transform function/filename may
2276 contain only characters which cause no problems in the file system as
2277 well as the PHP function naming convention.<br /><br />
2279 The transform function will the be called
2280 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2282 <b>Example:</b><br /><br />
2284 <tt>text_html__formatted.inc.php</tt><br />
2285 <tt>PMA_transform_text_html__formatted()</tt></li>
2287 <li>A mimetype (w/o subtype) transform:<br /><br />
2289 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2291 Please note that there are no single '_' characters.
2292 The transform function/filename may contain only characters which cause
2293 no problems in the file system as well as the PHP function naming
2294 convention.<br /><br />
2296 The transform function will the be called
2297 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2299 <b>Example:</b><br /><br />
2301 <tt>text__formatted.inc.php</tt><br />
2302 <tt>PMA_transform_text__formatted()</tt></li>
2304 <li>A mimetype+subtype without specific transform function<br /><br />
2306 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2308 Please note that there are no '__' characters in the filename. Do not
2309 use special characters in the filename causing problems with the file
2310 system.<br /><br />
2312 No transformation function is defined in the file itself.<br /><br />
2314 <b>Example:</b><br /><br />
2316 <tt>text_plain.inc.php</tt><br />
2317 (No function)</li>
2319 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2321 <tt>[mimetype].inc.php</tt><br /><br />
2323 Please note that there are no '_' characters in the filename. Do not use
2324 special characters in the filename causing problems with the file system.
2325 <br /><br />
2327 No transformation function is defined in the file itself.<br /><br />
2329 <b>Example:</b><br /><br />
2331 <tt>text.inc.php</tt><br />
2332 (No function)</li>
2334 <li>A global transform function with no specific mimetype<br /><br />
2336 <tt>global__[transform].inc.php</tt><br /><br />
2338 The transform function will the be called
2339 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2341 <b>Example:</b><br /><br />
2343 <tt>global__formatted</tt><br />
2344 <tt>PMA_transform_global__formatted()</tt></li>
2345 </ol>
2347 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2348 transform function.</p>
2350 <p> All filenames containing no '__' in themselves are not shown as valid transform
2351 functions in the dropdown.</p>
2353 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2354 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2355 without a transform function. Also note the introduction of a function description in
2356 the language files. For each function a $strTransformation_[filename without .inc.php]
2357 has to exist.</p>
2359 <p> You can use the template generator to generate new functions and entries in the
2360 language file.</p>
2362 <p> To create a new transform function please see
2363 <tt>libraries/transformations/template_generator.sh</tt>.
2364 To create a new, empty mimetype please see
2365 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2367 <p> A transform function always gets passed three variables:</p>
2369 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2370 you want to transform.</li>
2371 <li><b>$options</b> - Contains any user-passed options to a transform function
2372 as an array.</li>
2373 <li><b>$meta</b> - Contains an object with field information to your column.
2374 The data is drawn from the output of the
2376 function. This means, all object properties described on the
2378 available in this variable and can be used to transform a field accordingly
2379 to unsigned/zerofill/not_null/... properties.<br />
2380 The $meta->mimetype variable contains the original MIME-type of the
2381 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2382 </ol>
2384 <!-- FAQ -->
2391 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2395 </ol>
2397 <p> Please have a look at our
2399 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2400 features and or interface.</p>
2406 action is required or phpMyAdmin sends a blank page or a page full of
2407 cryptic characters to my browser, what can I do?</a></h4>
2409 <p> There are some known PHP bugs with output buffering and compression.<br />
2411 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2412 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2413 configuration file.<br />
2414 Furthermore, we know about such problems connected to the release
2415 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2416 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2421 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2422 See also the
2424 entry about PHP bugs with output buffering.<br />
2425 If your server keeps crashing, please ask for help in the various Apache
2426 support groups.</p>
2430 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2431 script: I'm always displayed the login screen.</a></h4>
2433 <p> This is a known PHP bug (see this
2435 official PHP bug database. It means there is and won't be any phpMyAdmin
2436 fix against it because there is no way to code a fix.</p>
2442 application misbehaved by not returning a complete set of
2444 </h4>
2446 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2447 Have a look at the last message in this
2449 official PHP bug database.</p>
2454 and/or many error messages with the
2456 mode.</a></h4>
2458 <p> This is a known problem with the PHP
2460 filter: it's not so stable. Please use instead the cookie authentication mode.
2461 </p>
2466 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2467 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2468 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2469 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2470 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2475 work.</a></h4>
2477 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2478 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2479 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2480 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2481 We faced PHP crashes when trying to download a dump with MS Internet
2482 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2483 this case you should switch to the release version of PHP 4.2.0.</p>
2487 an error about safe mode being in effect.</a></h4>
2489 <p> Your uploaded file is saved by PHP in the "upload dir", as
2490 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2491 the system default is <i>/tmp</i>).<br />
2492 We recommend the following setup for Apache servers running in safe mode,
2493 to enable uploads of files while being reasonably secure:</p>
2495 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2496 <li>give ownership to the Apache server's user.group:
2497 <tt>chown apache.apache /tmp/php</tt></li>
2498 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2499 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2500 <li>restart Apache</li>
2501 </ul>
2505 general file uploads don't work on my system and uploaded files have a
2506 <tt>Content-Type:</tt> header in the first line.</a></h4>
2508 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2509 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2510 So the problem is that this package has a serious bug that was corrected
2511 ages ago in PHP (2001-01-28: see
2513 for more details). The problem is that the bugged package is still
2514 available though it was corrected (see
2516 for more details).<br />
2517 So please download
2518 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2519 and the problem should go away.<br />
2520 And that fixes the \r\n problem with file uploads!</p>
2524 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2525 I'm using the Apache server.</a></h4>
2527 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2528 your <i>httpd.conf</i>:</p>
2532 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2536 uploading a file from the query box.</a></h4>
2538 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2539 restrictions. However you need to create temporary directory and
2541 The uploaded files will be moved there, and after execution of your
2547 <p> The MySQL manual explains how to
2549 reset the permissions</a>.</p>
2554 execute a bookmark.</a></h4>
2556 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2557 cannot access the uploaded query.</p>
2562 submit a query from the convenient text area.</a></h4>
2564 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2565 and try to increase it.</p>
2569 </h4>
2571 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2572 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2573 names to align with current standards.</p>
2578 </h4>
2580 <p> Starting with version 2.7.0, the import engine has been re–written and these
2581 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2582 to take advantage of the new import features.</p>
2584 <p> The first things to check (or ask your host provider to check) are the
2585 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2586 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2587 All of these three settings limit the maximum size of data that can be
2588 submitted and handled by PHP. One user also said that post_max_size
2589 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2591 There exist several workarounds if your upload is too big or your
2592 hosting provider is unwilling to change the settings:</p>
2595 feature. This allows one to
2596 upload a file to the server via scp, ftp, or your favorite file transfer
2597 method. PhpMyAdmin is then able to import the files from the temporary
2599 section</a> of this document.</li>
2601 BigDump</a>) to split the files before uploading. We cannot support this
2602 or any third party applications, but are aware of users having success
2603 with it.</li>
2604 <li>If you have shell (command line) access, use MySQL to import the files
2605 directly. You can do this by issuing the "source" command from
2606 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2607 </ul>
2611 support?</a></h4>
2613 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2614 fully supported. phpMyAdmin may connect to your MySQL server
2615 using PHP's classic
2618 is available in php 5.0.<br />
2619 Either way, the developers of both extensions recommend to use the classic
2620 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2621 When compiling php, we strongly recommend that you manually link the MySQL
2622 extension of your choice to a MySQL client library of at least the same
2623 minor version since the one that is bundled with some PHP distributions is
2626 If your webserver is running on a windows system, you might want to try
2627 MySQL's
2629 instead of the MySQL / MySQLi extensions that are bundled with the official
2630 php Win32 builds.</p>
2634 message, "Client does not support authentication protocol requested
2635 by server; consider upgrading MySQL client"</a></h5>
2637 <p> You tried to access MySQL with an old MySQL client library. The version of
2638 your MySQL client library can be checked in your phpinfo() output.
2639 In general, it should have at least the same minor version as your server
2643 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2644 changed the authentication hash and your PHP is trying to use the old method.
2646 with the proper client library to match your MySQL installation. Your
2647 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2648 More information (and several workarounds) are located in the
2650 </p>
2654 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2655 capital letter in its name it is changed to lowercase as it should. But
2656 if I try to DROP this table MySQL is unable to find the corresponding
2657 file.</a></h4>
2659 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2660 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2661 directive.</p>
2665 script seems not to know the font face I'm using!</a></h4>
2667 <p> The "FPDF" library we're using for this feature requires some
2668 special files to use font faces.<br />
2670 these files.</p>
2674 check PHP Configuration".</a></h4>
2676 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2677 "MySQL extension". This extension may be part of the PHP
2678 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2679 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2680 to load the extension but failed.<br /><br />
2682 Usually, the problem is solved by installing a software package called
2683 "PHP-MySQL" or something similar.</p>
2688 and I cannot log in using cookie auth.</a></h4>
2690 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2694 so I cannot upload.</a></h4>
2696 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2697 parameter is not set to "on".</p>
2701 a new table the table and field names are changed to lowercase!</a></h4>
2703 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2704 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2705 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2706 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2707 directory and add the following line to the group [mysqld]:</p>
2709 <pre>set-variable = lower_case_table_names=0</pre>
2711 <p> Next, save the file and restart the MySQL service. You can always check the
2712 value of this directive using the query</p>
2714 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2718 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2721 </p>
2725 and I get problems, such as undefined variables when I run a
2728 <p> A tip from Jose Fandos: put a comment on the following two lines
2729 in httpd.conf, like this:</p>
2731 <pre>
2732 # mod_gzip_item_include file \.php$
2734 </pre>
2736 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2737 PHP scripts. Of course you have to restart Apache.</p>
2742 I get the error "No input file specified" when trying to
2743 run phpMyAdmin.</a></h4>
2745 <p> This is a permission problem. Right-click on the phpmyadmin folder
2746 and choose properties. Under the tab Security, click on "Add"
2747 and select the user "IUSR_machine" from the list. Now set his
2748 permissions and it should work.</p>
2752 db_structure.php with plenty of tables).</a></h4>
2755 GZIP output buffering is enabled. If you turn off it (by
2757 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2758 PHP 5.0.0.</p>
2762 message 'Errorcode: 13'. What does this mean?</a></h4>
2764 <p> This can happen due to a MySQL bug when having database / table names with
2765 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2766 To fix this, turn off this directive, convert all database and table names
2767 to lower case and turn it on again. Alternatively, there's a bug-fix
2768 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2772 and the fields are duplicated.</a></h4>
2774 <p> It is possible to configure Apache in such a way that PHP has problems
2775 interpreting .php files.</p>
2777 <p> The problems occur when two different (and conflicting) set of directives
2778 are used:</p>
2780 <pre>
2781 SetOutputFilter PHP
2782 SetInputFilter PHP
2783 </pre>
2785 <p> and</p>
2787 <pre>AddType application/x-httpd-php .php</pre>
2789 <p> In the case we saw, one set of directives was in
2790 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2791 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2792 The recommended way is with <tt>AddType</tt>, so just comment out
2793 the first set of lines and restart Apache:</p>
2795 <pre>
2796 #SetOutputFilter PHP
2797 #SetInputFilter PHP
2798 </pre>
2803 <p> This problem is known to happen when the server is running Turck MMCache
2804 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2809 <p> Yes.<br />
2810 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2811 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2812 <tt>error_reporting</tt> settings.
2813 </p>
2816 <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>
2818 <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>
2821 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2822 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2823 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2824 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2825 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2826 enabled.) Click <tt>OK</tt>.</li>
2827 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2828 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2829 </ol>
2833 PHP 5.0.4 on 64-bit systems?</a></h4>
2835 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2836 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2842 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
2843 the order of the server paragraph in <tt>config.inc.php</tt>.
2844 Table and script parts are optional. If you want
2845 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2846 some configuration. Following lines apply only for <a
2848 that you have enabled some features within global configuration. You need
2849 <code>Options FollowSymLinks</code> and <code>AllowOverride
2850 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2851 you need mod_rewrite to be enabled. Then you just need to create following
2852 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2853 (don't forget to change directory name inside of it):</p>
2855 <pre>
2856 RewriteEngine On
2857 RewriteBase /path_to_phpMyAdmin
2858 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2859 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2860 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2861 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2862 </pre>
2865 <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>
2867 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2868 following rewrite rule:</p>
2870 <pre>
2871 RewriteEngine On
2872 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2873 </pre>
2877 </h4>
2878 <p>
2879 There can be many explanations to this and a look at your server's
2880 error log file might give a clue.
2881 </p>
2885 password encryption in cookie auth doesn't work.</a></h4>
2887 <p> If your cluster consist of different architectures, PHP code used for
2888 encryption/decryption won't work correct. This is caused by use of
2889 pack/unpack functions in code. Only solution is to use mcrypt extension
2890 which works fine in this case.</p>
2895 <p> Yes but the default configuration values of Suhosin are known to cause
2896 problems with some operations, for example editing a table with many
2897 columns and no primary key. Tuning information is available at
2899 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2900 although the parameter names have changed (<tt>suhosin</tt> instead
2902 <tt>SuhosinDisableWarning</tt> directive</a>.
2903 </p>
2909 headers already sent by ..." is displayed, what's the problem?</a></h4>
2911 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2912 (I.E. no blank lines, no spaces, no characters...) neither before the
2913 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2914 tag at the end. We also got a report from a user under IIS, that used
2915 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2916 contained an end-of-line character (hex 0A) at the end; removing this character
2917 cleared his errors.</p>
2922 <p> Either there is an error with your PHP setup or your username/password is
2923 wrong. Try to make a small script which uses mysql_connect and see if it
2924 works. If it doesn't, it may be you haven't even compiled MySQL support
2925 into PHP.</p>
2929 connect to local MySQL server through socket '/tmp/mysql.sock'
2930 (111) ..." is displayed. What can I do?</a></h4>
2932 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2934 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2935 In your <i>php.ini</i> you will find a line</p>
2937 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2939 <p> change it to</p>
2941 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2943 <p> Then restart apache and it will work.</p>
2945 <p> Here is a fix suggested by Brad Ummer:</p>
2947 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2948 To do this, telnet to your server and go to the MySQL bin directory. In
2949 this directory there should be a file named <i>mysqladmin</i>. Type
2950 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2951 info about your MySQL server, including the socket
2952 (<i>/tmp/mysql.sock</i>, for example).</li>
2953 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2954 phpMyAdmin, you need to complete the socket information in the
2955 <i>config.inc.php</i>.<br />
2956 For example:
2958 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2959 <br /><br />
2961 Please also make sure that the permissions of this file allow to be readable
2962 by your webserver (i.e. '0755').</li>
2963 </ul>
2965 <p> Have also a look at the
2967 corresponding section of the MySQL documentation</a>.</p>
2971 what can I do?</a></h4>
2974 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2975 sometime.<br />
2976 Also have a look at your PHP version number: if it contains "4.0b..."
2977 it means you're running a beta version of PHP. That's not a so good idea,
2978 please upgrade to a plain revision.</p>
2982 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2983 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2985 <p> Check the value you set for the
2987 directive in the phpMyAdmin configuration file.</p>
2991 password: YES)"-error when trying to access a MySQL-Server on a
2992 host which is port-forwarded for my localhost.</a></h4>
2994 <p> When you are using a port on your localhost, which you redirect via
2995 port-forwarding to another host, MySQL is not resolving the localhost
2996 as expected.<br />
2997 Erik Wasser explains: The solution is: if your host is "localhost"
2998 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2999 connection for speeding up things. And that doesn't work in this configuration
3000 with port forwarding.<br />
3006 <p> Themes are configured with
3010 <br />
3012 should not delete the directory "original" or its underlying
3013 structure, because this is the system theme used by phpMyAdmin.
3014 "original" contains all images and styles, for backwards
3015 compatibility and for all themes that would not include images or css-files.
3016 <br /><br />
3019 is enabled, you can select your favorite theme on the main page. Your
3020 selected theme will be stored in a cookie.<br /><br /></p>
3022 <p> To create a theme:</p>
3024 <ul><li>make a new subdirectory (for example "your_theme_name") under
3026 (by default <tt>themes</tt>)</li>
3027 <li>copy the files and directories from "original" to
3028 "your_theme_name"</li>
3029 <li>edit the css-files in "your_theme_name/css"</li>
3030 <li>put your new images in "your_theme_name/img"</li>
3031 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3032 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3033 contain your chosen theme name, that will be visible in user interface</li>
3034 <li>make a new screenshot of your theme and save it under
3035 "your_theme_name/screen.png"</li>
3036 </ul>
3038 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3039 theme verbose name, theme generation and theme version. These versions and
3040 generations are enumerated from 1 and do not have any direct dependence on
3041 phpMyAdmin version. Themes within same generation should be backwards
3042 compatible - theme with version 2 should work in phpMyAdmin requiring
3043 version 1. Themes with different generation are incompatible.</p>
3045 <p> If you do not want to use your own symbols and buttons, remove the
3046 directory "img" in "your_theme_name". phpMyAdmin will
3047 use the default icons and buttons (from the system-theme "original").
3048 </p>
3052 what can I do?</a></h4>
3054 <p> Here are a few points to check:</p>
3056 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3058 directive empty. See also
3060 </li>
3061 <li>Maybe you have a broken PHP installation or you need to upgrade
3062 your Zend Optimizer. See
3064 http://bugs.php.net/bug.php?id=31134</a>.
3065 </li>
3066 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3067 set to the default (200) or another low value, you could get this
3068 error if your table has a high number of columns. Adjust this setting
3069 accordingly. (Thanks to Klaus Dorninger for the hint).
3070 </li>
3071 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3072 of ";" will cause this error. Replace it with "&;".
3073 </li>
3075 you might want to increase
3077 </li>
3078 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3079 </li>
3080 </ul>
3087 who logged out can not log in again in with the same nick.</a></h4>
3089 <p> This is related to the authentication mechanism (protocol) used by
3090 phpMyAdmin. To bypass this problem: just close all the opened
3091 browser windows and then go back to phpMyAdmin. You should be able to
3092 log in again.</p>
3096 limit error or a time limit error.</a></h4>
3098 <p> Compressed dumps are built in memory and because of this are limited to
3099 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3100 using
3102 (enabled by default). Zip exports can not be handled this way, so if you need
3103 Zip files for larger dump, you have to use another way.</p>
3107 or alter a table.</a></h4>
3109 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3113 bundled with the MySQL server distribution.</a></h4>
3115 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3117 <pre>
3118 -- MySQL dump 8.22
3119 --
3120 -- Host: localhost Database: database
3121 ---------------------------------------------------------
3122 -- Server version 3.23.54
3123 </pre>
3125 <p> The invalid part of the code is the horizontal line made of dashes that
3126 appears once in every dump created with mysqldump. If you want to run your
3127 dump you have to turn it into valid MySQL. This means, you have to add a
3128 whitespace after the first two dashes of the line or add a # before it:
3129 <br />
3130 <code>
3131 -- -------------------------------------------------------<br />
3132 </code>
3133 or<br />
3134 <code>
3135 #---------------------------------------------------------
3136 </code>
3137 </p>
3144 <p> Please note that you should not use the separating string multiple times
3145 without any characters between them, or at the beginning/end of your table
3146 name. If you have to, think about using another TableSeparator or disabling
3147 that feature</p>
3152 <p> In Relation view, being able to choose a table in another database,
3153 or having more than one index field in the foreign key.<br /><br/>
3154 In Query-by-example (Query), automatic generation of the query
3155 LEFT JOIN from the foreign table.<br /><br/>
3156 </p>
3160 I get series of errors like "Warning: unable to parse url". How
3161 can this be fixed?</a></h4>
3162 <p>
3163 Your table neither have a primary key nor an unique one, so we must use a
3164 long expression to identify this row. This causes problems to parse_url
3165 function. The workaround is to create a primary or unique key.
3166 <br />
3167 </p>
3171 a MIME-Transformation onto!</a></h4>
3173 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3174 nested forms can be put inside the table where phpMyAdmin displays the results.
3175 You can, however, use any form inside of a table if keep the parent
3176 form-container with the target to tbl_row_delete.php and just put your own
3177 input-elements inside. If you use a custom submit input field, the form will
3178 submit itself to the displaying page again, where you can validate the
3179 $HTTP_POST_VARS in a transformation.
3181 For a tutorial on how to effectively use transformations, see our
3183 on the official phpMyAdmin-homepage.</p>
3187 MySQL server</a></h4>
3189 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3192 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3193 the quote-character (") is interpreted as an identifier quote character and
3194 not as a string quote character, which makes many internal phpMyAdmin
3196 statements. There is no workaround to this behaviour. News to this item will
3197 be posted in Bug report
3198 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3199 </p>
3203 more that one column with the same value
3204 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3205 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3207 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3208 can use it for the Edit and Delete links.</p>
3213 <p> phpMyAdmin uses a quick method to get the row count, and this method
3214 only returns an approximate count in the case of InnoDB tables. See
3216 a way to modify those results, but
3217 this could have a serious impact on performance.</p>
3222 <p> The number of records in queries containing COUNT and GROUP BY is
3223 not correctly calculated. Also, sorting results of a query like
3228 containing an hyphen.
3229 </a></h4>
3230 <p>
3231 The tests I have made with current MySQL 4.1.11 API shows that the
3232 API does not accept this syntax for the USE command. Enclosing the
3233 db name with backquotes works. For further confusion, no backquotes
3234 are needed with command-line mysql.
3235 </p>
3238 <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>
3239 <p>
3240 This has been a known limitation of phpMyAdmin since the beginning and
3241 it's not likely to be solved in the future.
3242 </p>
3244 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3247 <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
3248 need to install it for each customer.
3249 </a></h4>
3250 <p>
3251 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3252 your users. The development of this feature was kindly sponsored by
3253 NetCologne GmbH.
3254 This requires a properly setup MySQL user management and phpMyAdmin
3255 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3257 </p>
3261 access.
3262 </a></h4>
3263 <p>
3264 This depends on your system.<br />
3265 If you're running a server which cannot be accessed by other people, it's
3266 sufficient to use the directory protection bundled with your webserver
3268 If other people have telnet access to your server, you should use
3269 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3270 <br /><br />
3271 Suggestions:
3272 </p>
3273 <ul>
3274 <li>
3276 </li>
3277 <li>
3278 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3279 is a user whose password is only known to you, and apache is the
3280 group under which Apache runs.
3281 </li>
3282 <li>
3283 You should use PHP safe mode, to protect from other users that try
3285 </li>
3286 </ul>
3291 </a></h4>
3292 <p>
3297 </p>
3300 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3301 authentication.
3302 </a></h4>
3306 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3307 and/or
3309 are wrong.</li>
3311 <li>You have already setup a security mechanism for the
3312 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3313 phpMyAdmin's authentication, so remove it.</li>
3314 </ul>
3321 and put the privileges you want. For example,
3323 would let a user create/manage his/her database(s).</p>
3328 <p> If you have existing rules from an old .htaccess file, you can take them
3331 be a major benefit here if your installation is suited to using it. Then
3332 you can just add those updated lines into the
3336 <p> If you want a pre-made sample, you can try this fragment. It stops the
3337 'root' user from logging in from any networks other than the private
3340 <pre>
3341 //block root from logging in except from the private networks
3342 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3343 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3344 'deny root from all',
3345 'allow root from localhost',
3349 );
3350 </pre>
3355 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3356 different than the one set in your
3358 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3359 while a domain name is defined in the config file.</p>
3364 <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>
3370 when trying to create a table with more than 14 fields.
3371 </a></h4>
3372 <p>
3373 We could reproduce this problem only under Win98/98SE. Testing under
3374 WinNT4 or Win2K, we could easily create more than 60 fields.
3375 <br />
3376 A workaround is to create a smaller number of fields, then come back to
3377 your table properties and add the other fields.
3378 </p>
3382 <p>
3383 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3384 with each script/website that use forms.<br />
3385 Upgrade or downgrade your Xitami server.
3386 </p>
3389 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3390 <p>
3391 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3392 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3393 don't seem to work.<br />
3395 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3396 the user's temporary directory, so they must be moved before closing
3397 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3400 </p>
3404 Explorer never stores the cookies.
3405 </a></h4>
3406 <p>
3407 MS Internet Explorer seems to be really buggy about cookies, at least till
3409 in this area!
3410 <br />
3411 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3412 work!
3413 </p>
3417 rows.
3418 </a></h4>
3419 <p>
3421 </p>
3424 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3425 when trying to modify a row in a table with many fields, or with a text field
3426 </a></h4>
3427 <p>
3428 Your table neither have a primary key nor an unique one, so we must use a
3429 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
3430 those browsers, and this not happen in Netscape, for example. The
3431 workaround is to create a primary or unique key, or use another browser.
3432 <br />
3433 </p>
3437 page.
3438 </a></h4>
3439 <p>
3440 Some browsers support right-clicking into the frame you want to refresh,
3441 just do this in the right frame.<br />
3442 </p>
3446 query box.
3447 </a></h4>
3448 <p>
3449 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3450 Mozilla versions.<br />
3451 </p>
3455 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3456 </a></h4>
3457 <p>
3458 This is a Mozilla bug (see bug #26882 at
3460 </p>
3465 </a></h4>
3466 <p>
3467 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3468 data in octet-stream mode. Since we can't detect the specific Netscape
3469 version, we cannot workaround this bug.
3470 </p>
3474 wrong.</a></h4>
3476 <p> Please ensure that you have set your browser's character set to the one of the
3477 language file you have selected on phpMyAdmin's start page.
3478 Alternatively, you can try the auto detection mode that is supported by the
3479 recent versions of the most browsers.</p>
3482 <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
3485 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3486 Netscape and Mozilla do not have this problem.</p>
3489 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3490 I cannot manage two servers: I log in to the first one, then the other one,
3491 but if I switch back to the first, I have to log in on each operation.</a></h4>
3497 but nothing happens after that, only a blank screen.</a></h4>
3500 bug in Opera6, because it is not able to interpret frameset definitions
3501 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3502 Opera7 at least.</p>
3511 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3516 address and you are starting
3518 containing a domain name, or the reverse situation.</li>
3519 <li>Security settings in IE and/or Microsoft Security Center are
3520 too high, thus blocking scripts execution.</li>
3521 <li>The Windows Firewall is blocking Apache and MySQL. You must
3525 </ul>
3528 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3529 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3530 installed in their Firefox is causing the problem.</p>
3537 </a></h4>
3538 <p>
3539 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3540 specifying a wrong field-type.<br />
3541 Common errors include:
3542 </p>
3543 <ul>
3546 </ul>
3547 <p>
3548 Also, look at the syntax chapter in the MySQL manual to confirm that your
3549 syntax is correct.
3550 </p>
3554 phpMyAdmin generates only one index with those two fields.
3555 </a></h4>
3556 <p>
3557 This is the way to create a multi-fields
3558 index. If you want two indexes, create the first one when creating the
3559 table, save, then display the table properties and click the Index link to
3560 create the other index.
3561 </p>
3565 <p>
3566 Since version 2.2.3, you have a checkbox for each field that can be null.
3568 field's value. Since version 2.5.5, you have to use the checkbox to get
3570 a literal NULL in the field, and not a NULL value (this works in PHP4).
3571 </p>
3576 <p> Click on a database or table name in the left frame, the properties will be
3578 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3579 statements that can be used to recreate your database/table.
3580 <br /><br />
3582 transmit the resulting dump to your station. Depending on your PHP
3583 configuration, you will see options to compress the dump. See also the
3585 configuration variable.<br /><br />
3588 this document.</p>
3593 </a></h4>
3595 <p> Click on a database name in the left frame, the properties will be
3597 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3599 the path to your dump filename, or use the Browse button. Then click Go.
3600 <br /><br />
3602 that you upgrade to take advantage of the new features.
3603 <br /><br />
3605 in this document.
3606 </p>
3611 <p> Here is an example with the tables persons, towns and countries, all
3613 table, create it as explained in the configuration section. Then create the
3614 example tables:</p>
3616 <pre>
3617 CREATE TABLE REL_countries (
3618 country_code char(1) NOT NULL default '',
3619 description varchar(10) NOT NULL default '',
3620 PRIMARY KEY (country_code)
3621 ) TYPE=MyISAM;
3623 INSERT INTO REL_countries VALUES ('C', 'Canada');
3625 CREATE TABLE REL_persons (
3626 id tinyint(4) NOT NULL auto_increment,
3627 person_name varchar(32) NOT NULL default '',
3629 country_code char(1) NOT NULL default '',
3630 PRIMARY KEY (id)
3631 ) TYPE=MyISAM;
3633 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3634 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3636 CREATE TABLE REL_towns (
3638 description varchar(30) NOT NULL default '',
3639 PRIMARY KEY (town_code)
3640 ) TYPE=MyISAM;
3642 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3643 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3644 </pre>
3650 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3654 </ul>
3662 <li>In the fields row, choose persons.person_name and click the
3664 <li>Do the same for towns.description and countries.descriptions in the
3667 the correct joins have been generated</li>
3669 </ul>
3673 <p>
3674 Starting from the previous example, create the pma_table_info as explained
3675 in the configuration section, then browse your persons table,
3676 and move the mouse over a town code or country code.
3677 <br /><br />
3678 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3679 enables: drop-down list of possible values.
3680 </p>
3683 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3684 <p>
3687 <br /><br />
3688 Then you need to think about your schema layout. Which tables will go on
3689 which pages?
3690 </p>
3691 <ul>
3697 page and click Go. If you like, you
3699 linked tables onto the new page.</li>
3700 <li>Select the name of the new page (making sure the Edit radio button
3701 is selected) and click Go.</li>
3703 Coordinates are relative; your diagram will
3704 be automatically scaled to fit the page. When initially placing tables
3705 on the page, just pick any coordinates -- say, 50x50. After clicking
3707 position the element correctly.</li>
3709 first be sure to click the Save
3710 button beneath the list of tables and coordinates, to save any changes
3711 you made there. Then scroll all the way down, select the
3713 you want, and click Go.</li>
3714 <li>Internet Explorer for Windows may suggest an incorrect filename when
3719 browsers on Windows, do not have this problem.</li>
3720 </ul>
3724 columns!</a></h4>
3726 <p> No, it's MySQL that is doing
3732 underscores in the database name?</a></h4>
3734 <p> If you do not put a backslash before the underscore, this is a wildcard
3737 john2db ...<br /><br />
3739 If you put a backslash before the underscore, it means that the database
3740 name will have a real underscore.</p>
3744 statistics pages?</a></h4>
3755 if it already exists during the import. It does NOT drop the table after
3756 your export, it only affects the import file.</li>
3758 Otherwise, you may get an error if the table name exists but has a
3759 different structure.</li>
3761 (if any) will be included in backup.</li>
3763 field and table names formed with special characters are protected.</li>
3765 types set in the pmadb in the dump as
3767 </li>
3768 </ul>
3773 command, for better documentation (but resulting file is bigger).</li>
3775 once the INSERT verb and the table name.</li>
3778 </li>
3780 more info is provided in the
3782 but basically with this selected, invalid values are adjusted and
3783 inserted rather than causing the entire statement to fail.</li>
3784 </ul>
3788 in its name.</a></h4>
3791 is the normal way to reference a database and table name. Worse, MySQL
3792 will usually let you create a database with a dot, but then you cannot
3793 work with it, nor delete it.</p>
3806 for usage.<br />
3807 On a more recent pear version, I had problems with the state of Net_DIME
3808 being beta, so this single command
3810 needed modules.<br />
3811 If you use the Validator, you should be aware that any
3813 submit will be stored anonymously (database/table/column names,
3814 strings, numbers replaced with generic values). The Mimer
3817 We utilize it as free SOAP service.</p>
3821 it, but MySQL says "BLOB column '...' used in key specification without
3824 <p> The right way to do this, is to create the field without any indexes,
3826 dialog. On this page, you will be able to choose your BLOB field, and
3827 set a size to the index, which is the condition to create an index on
3828 a BLOB field.</p>
3832 editing fields?</a></h4>
3834 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3835 with many editing fields (table structure changes, row editing, etc.)
3836 (must be enabled in configuration - see.
3838 You can also have a look at the directive
3840 ('vertical') and see if this eases up editing for you.</p>
3844 WTF is this feature then useful for?</a></h4>
3846 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3847 on them. Otherwise you could just put a comment on the field. Because entering
3848 your own mimetype will cause serious syntax checking issues and validation,
3849 this introduces a high-risk false-user-input situation. Instead you have to
3850 initialize mimetypes using functions or empty mimetype definitions.<br />
3851 Plus, you have a whole overview of available mimetypes. Who knows all those
3852 mimetypes by heart so he/she can enter it at will?</p>
3856 can't I see any bookmarks below the query box? What is this variable for?
3857 </a></h4>
3859 <p> Any query you have executed can be stored as a bookmark on the page where the
3860 results are displayed. You will find a button labeled 'Bookmark this query'
3861 just at the end of the page.<br />
3862 As soon as you have stored a bookmark, it is related to the database you run
3863 the query on. You can now access a bookmark dropdown on each page, the query
3864 box appears on for that database.<br /><br />
3866 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3870 aware of that you HAVE to create a valid query, otherwise your query won't be
3871 even able to be stored in the database.<br />
3873 for your query will remain the way it is, but will be stripped of the /**/
3874 chars. So you can use:<br /><br />
3878 which will be expanded to<br /><br />
3882 in your query, where VARIABLE is the string you entered in the input box. If
3883 an empty string is provided, no replacements are made.<br /><br />
3885 A more complex example. Say you have stored this query:<br /><br />
3887 <br /><br />
3890 the full query will be:<br /><br />
3893 <br /><br />
3897 spaces inserted there
3898 will be later also inserted as spaces in your query and may lead to unexpected
3899 results especially when
3901 Your initial query which is going to be stored as a bookmark has to yield at
3902 least one result row so
3903 you can store the bookmark. You may have that to work around using well
3907 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3908 include exported table?</a></h4>
3910 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3911 document should look like following one (assuming you have table
3914 <pre>
3915 \documentclass{article} % or any class you want
3916 \usepackage{longtable} % for displaying table
3917 \begin{document} % start of document
3918 \include{table} % including exported table
3919 \end{document} % end of document
3920 </pre>
3924 access them.
3925 </a></h4>
3928 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3929 enable users to see all the database names.
3932 So if your users do not need those privileges, you can remove them and their
3933 databases list will shorten.</p>
3937 possible values for a field, based on some foreign table?</a></h4>
3939 <p> You have to setup appropriate links between the tables, and also
3943 foreign table, a drop-down list of values will be available.
3944 You will see two lists of values, the first list containing the key
3945 and the display field, the second list containing the display field
3946 and the key. The reason for this is to be able to type the first
3947 letter of either the key or the display field.<br /><br />
3949 For 100 values or more, a distinct window will appear, to browse foreign
3950 key values and choose one. To change the default limit of 100, see
3951 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
3955 automatically when entering Browse mode for a table?</a></h4>
3957 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3958 </p>
3962 Excel files, how can I enable that?</a></h4>
3964 <p> Current version does support direct export to Microsoft Excel and Word
3965 versions 2000 and newer. If you need export older versions, you can use
3967 which works out of the box or you can
3969 several problems, most important are limitation of cell content to 255
3970 chars and no support for charsets, so think carefully whether you want to
3971 enable this.</b>. For enabling this you need to set
3975 module Spreadsheet_Excel_Writer into php include path. The
3976 installation can be done by following command:</p>
3978 <pre>
3979 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3980 </pre>
3982 <p> First part of switches set we want to install beta version of that module
3983 (no stable version available yet) and then we tell pear we want to satisfy
3984 dependencies.</p>
3986 <p> If you are running in PHP safe mode, you will have to set
3989 modules are located, for example:</p>
3991 <pre>
3992 safe_mode_include_dir = /usr/local/lib/php
3993 </pre>
3997 <pre>
3998 cd phpMyAdmin
3999 mkdir tmp
4000 chmod o+rwx tmp
4001 </pre>
4005 what happens to my column comments stored in pmadb?</a></h4>
4007 <p> Automatic migration of a table's pmadb-style column comments to the native
4008 ones is done whenever you enter Structure page for this table.</p>
4013 <p> First, for general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. We currently support streaming if you are running MySQL 5.1 with the PBXT and PBMS storage engines.<br /><br />
4014 <ol>
4015 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of something like "localhost".</li>
4016 <li>A current limitation is that your first login via phpMyAdmin to a freshly-started server must be done with an account that has the SUPER privilege.</li>
4017 <li>On your target database, go to Operations and in the "BLOB Repository" section, click "Enable". This creates the PBMS system tables inside your database.</li>
4019 <li>When you insert or update a row in this table, put a checkmark on the "Upload to BLOB repository" optional choice; otherwise, the upload will be done directly in your column instead of the repository.</li>
4020 <li>Finally when you browse your table, you'll see in your column a link to stream your data, for example "View image". A header containing the correct MIME-type will be sent to your browser; this MIME-type was stored at upload time but in case it's incorrect, it's possible to edit it by clicking on the displayed MIME-type.</li>
4021 </ol>
4022 </p>
4029 <p> Our Bug Tracker is located at
4031 under the Bugs section.<br /><br />
4033 But please first discuss your bug with other users:<br />
4039 existing language, where do I start?</a></h4>
4041 <p> Always use the current SVN version of your language file.
4043 don't know how to get the SVN version, please ask one of the developers.
4044 <br />
4045 Please note that we try not to use HTML entities like &eacute; in
4046 the translations, since we define the right character set in the file.
4047 With HTML entities, the text on JavaScript messages would not
4048 display correctly.
4049 However there are some entities that need to be there, for quotes
4050 ,non-breakable spaces, ampersands, less than, greater than.<br />
4051 You can then put your translations, as a zip file to avoid losing special
4052 characters, on the sourceforge.net translation tracker.<br />
4053 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4054 list, because this is where we ask for translations of new messages.</p>
4058 phpMyAdmin. How should I proceed?</a></h4>
4063 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4064 </li>
4066 <li>generate patch with your changes:
4068 </li>
4071 tracker of the phpMyAdmin project</a>.
4072 </li>
4073 </ol>
4075 <p> Write access to the SVN tree is granted only to experienced developers who
4076 have already contributed something useful to phpMyAdmin.<br />
4082 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4084 <p> Please refer to
4085 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4086 </p>
4088 <!-- DEVELOPERS -->
4091 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4092 great features have been written by other people and you too can help to
4093 make phpMyAdmin a useful tool.</p>
4095 <p> If you're planning to contribute source, please read the following
4096 information:</p>
4102 it free from other code.<br />
4103 Commonly used functions should be added to
4106 <li>Obviously, you're free to use whatever coding style you want. But
4107 please try to keep your code as simple as possible: beginners are
4108 using phpMyAdmin as an example application.<br />
4109 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4110 compliant on one hand, they fit the
4113 coding standards</a>
4114 on the other hand. Please pay attention to this.</li>
4115 <li>Please try to keep up the file-naming conventions. Table-related stuff
4118 <li>Please don't put message strings in your code, instead add the string
4123 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4124 better debug and profile their code.<br />
4125 Please see the
4127 options for more information.<br />
4128 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4129 lost during its re-entry into Earth's atmosphere and in memory of the
4130 brave men and women who gave their lives for the people of Earth.</li>
4131 </ul>
4133 <!-- CREDITS -->
4136 <pre>
4137 phpMyAdmin - Credits
4138 ====================
4140 CREDITS, in chronological order
4141 -------------------------------
4144 * creator of the phpmyadmin project
4148 * multi-language version
4149 * various fixes and improvements
4151 * current project maintainer
4154 * started SourceForge phpMyAdmin project in March 2001
4155 * sync'ed different existing CVS trees with new features and bugfixes
4156 * multi-language improvements, dynamic language selection
4157 * current project maintainer
4158 * many bugfixes and improvements
4161 * rewrote and optimized javascript, DHTML and DOM stuff
4162 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4163 generate XHTML1.0 and CSS2 compliant codes
4164 * improved the language detection system
4165 * many bugfixes and improvements
4168 * database maintenance controls
4169 * table type code
4171 * DB-based configuration (Not completed)
4174 * many bugfixes and improvements
4177 * bookmarks feature
4178 * multiple dump feature
4179 * gzip dump feature
4180 * zip dump feature
4183 * various fixes
4184 * moderator of the phpMyAdmin former users forum at phpwizard.net
4190 * rewrote and fix dump code
4191 * bugfixes
4194 * rewrote dump code for PHP4
4195 * mySQL table statistics
4196 * bugfixes
4199 * main author of the version 2.1.0.1
4200 * bugfixes
4204 * abstract database interface (PMA_DBI) with MySQLi support
4205 * privileges administration
4207 * various features and fixes
4208 * German language file updates
4211 * automatic joins in QBE
4212 * links column in printview
4213 * Relation view
4216 * enhanced index creation/display feature
4217 * feature to use a different charset for HTML than for MySQL
4218 * improvements of export feature
4219 * various features and fixes
4220 * Czech language file updates
4223 (http://sf.net/projects/phpmysqlformgen/)
4224 * suggested the patch for multiple table printviews
4227 * built the patch for vertical display of table rows
4228 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4229 * Improvement of column/db comments
4230 * (MIME)-Transformations for columns
4231 * Use custom alias names for Databases in left frame
4232 * hierarchical/nested table display
4233 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4234 * new icon sets
4235 * vertical display of column properties page
4236 * some bugfixes, features, support, German language additions
4239 * japanese kanji encoding conversion feature
4242 * the Cookie authentication mode
4245 * table relation-links feature
4248 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4249 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4250 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4256 * phpMyAdmin logo (until June 2004)
4259 * blowfish library from the Horde project
4262 * mysqli support
4263 * many bugfixes and improvements
4266 * redesign for 2.6.0
4267 * phpMyAdmin sailboat logo (June 2004)
4270 * Representation at conferences
4273 * interface improvements
4274 * various bugfixes
4276 - Ivan A Kirillov
4277 * new relations Designer
4279 - Raj Kissu Rajandran (Google Summer of Code 2008)
4280 * BLOBstreaming support
4282 - Piotr Przybylski (Google Summer of Code 2008)
4283 * improved setup script
4285 And also to the following people who have contributed minor changes,
4286 enhancements, bugfixes or support for a new language since version 2.1.0:
4288 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4289 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4290 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4291 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4293 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4294 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4295 Luís V., Martijn W. van der Lee,
4296 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4300 Original Credits of Version 2.1.0
4301 ---------------------------------
4303 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4304 to create a web-based interface to MySQL using PHP3. Although I have not
4305 used any of his source-code, there are some concepts I've borrowed from
4306 him. phpMyAdmin was created because Peter told me he wasn't going to
4307 further develop his (great) tool.
4308 Thanks go to
4310 code for the check when dropping a table or database. He also suggested
4311 that you should be able to specify the primary key on tbl_create.php3. To
4312 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4313 well as a bug-report. Plus many smaller improvements.
4315 were introduced in 1.3.0 (including quite significant ones like the
4316 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4317 bug-fixes and help.
4319 language-independent by outsourcing the strings to a separate file. He
4320 also contributed the French translation.
4322 tbl_select.php3, a feature to display only some fields from a table.
4324 functions in tbl_change.php3. He also added the
4327 servers and is a regular contributor for bug-fixes.
4329 features for 2.0.6.
4330 The following people have contributed minor changes, enhancements, bugfixes
4331 or support for a new language:
4332 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4333 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4334 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4335 G. Wieggers.
4337 And thanks to everyone else who sent me email with suggestions, bug-reports
4338 and or just some feedback.
4339 </pre>
4345 <ul>
4347 - the default name of Apache's directory-level configuration file.</li>
4351 - a software application that enables a user to display and interact with
4352 text, images, and other information typically located on a web page at a
4353 website on the World Wide Web.</li>
4355 - a free software/open source data compression algorithm and program
4356 developed by Julian Seward.</li>
4358 - an important World Wide Web technology that enables a client web browser
4359 to request data from a program executed on the Web server.</li>
4361 - a log or record of changes made to a project.</li>
4363 - a computer system that accesses a (remote) service on another computer
4364 by some kind of network.</li>
4366 - a set of data values of a particular simple type, one for each row of
4367 the table.</li>
4369 - a packet of information sent by a server to a World Wide Web browser
4370 and then sent back by the browser each time it accesses that server.</li>
4372 - Comma-separated values</li>
4375 - an organized collection of data.</li>
4378 - a PHP module that extends PHP with additional functionality.</li>
4380 - a list of commonly asked question and there answers.</li>
4382 - one part of divided data/columns.</li>
4384 - a field or group of fields in a database record that point to a key
4385 field or group of fields forming a key of another database record in some
4386 (usually different) table.</li>
4388 - the free PDF library</li>
4390 GD Graphics Library</a> - a library by Thomas Boutell and others for
4391 dynamically manipulating images.</li>
4394 - gzip is short for GNU zip, a GNU free software file compression
4395 program.</li>
4397 - any machine connected to a computer network, a node that has a hostname.</li>
4399 - the unique name by which a network attached device is known on a network.</li>
4401 (HyperText Transfer Protocol)</a>
4402 - the primary method used to transfer or convey information on the World
4403 Wide Web.</li>
4406 additional security measures.</li>
4407 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4408 - a set of Internet-based services for servers using Microsoft Windows.</li>
4410 - a feature that allows quick access to the rows in a table.</li>
4412 - a data-oriented protocol used by source and destination hosts for
4413 communicating data across a packet-switched internetwork.</li>
4415 - a unique number that devices use in order to identify and communicate
4416 with each other on a network utilizing the Internet Protocol standard.</li>
4418 (Internet Server Application Programming Interface)</a>
4419 - the API of Internet Information Services (IIS).</li>
4421 - a business or organization that offers users access to the Internet and related services.</li>
4423 - a most commonly used standard method of lossy compression for
4424 photographic images.</li>
4430 - line of personal computers is designed, developed, manufactured, and
4431 marketed by Apple Computer.</li>
4432 <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>
4433 - the operating system which is included with all currently shipping Apple
4434 Macintosh computers in the consumer and professional markets.</li>
4436 - a cryptographic library.</li>
4438 - the MCrypt PHP extension.</li>
4439 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4440 - an Internet Standard for the format of e-mail.</li>
4442 - some sort of extension for the Apache Webserver.</li>
4444 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4445 Management System (DBMS).</li>
4447 - the improved MySQL client PHP extension.</li>
4449 - the MySQL client PHP extension.</li>
4451 - open standard for office documents.</li>
4452 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4453 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4455 (Portable Document Format)</a>
4456 - a file format developed by Adobe Systems for representing two
4457 dimensional documents in a device independent and resolution independent
4458 format.</li>
4460 - the PHP Extension and Application Repository.</li>
4462 - the perl-compatible regular expression functions for PHP</li>
4464 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4465 programming language used mainly for developing server-side applications
4466 and dynamic web content, and more recently, a broader range of software
4467 applications.</li>
4469 - a connection through which data is sent and received.</li>
4471 - Request for Comments (RFC) documents are a series of memoranda
4472 encompassing new research, innovations, and methodologies applicable to
4473 Internet technologies.</li>
4477 - represents a single, implicitly structured data item in a table.</li>
4479 - a computer system that provides services to other computing
4480 systems over a network.</li>
4481 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4482 - handlers for different table types</li>
4484 - a form of inter-process communication.</li>
4486 Sockets Layer)</a>
4487 - a cryptographic protocol which provides secure communication on the Internet.</li>
4489 - Structured Query Language</li>
4491 - a set of data elements (cells) that is organized, defined and stored as
4492 horizontal rows and vertical columns where each item can be uniquely
4493 identified by a label or key or by it?s position in relation to other items.</li>
4496 - a type of archive file format: the Tape ARchive format.</li>
4498 - one of the core protocols of the Internet protocol suite.</li>
4502 - a sequence of characters, conforming to a standardized format, that is
4503 used for referring to resources, such as documents and images on the
4504 Internet, by their location.</li>
4506 - A computer (program) that is responsible for accepting HTTP requests
4507 from clients and serving them Web pages.</li>
4509 - a W3C-recommended general-purpose markup language for creating
4510 special-purpose markup languages, capable of describing many different
4511 kinds of data.</li>
4513 - a popular data compression and archival format.</li>
4515 - an open-source, cross-platform data compression library by Jean-loup
4516 Gailly and Mark Adler.</li>
4517 </ul>
4527 </body>
4528 </html>