| blob | c3ba43a58cfe4194b283999fb2c940fa83a367d8 |
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>
66 currently default), you should install mbstring and ctype
67 extensions.
68 </li>
69 <li>You need GD2 support in PHP to display inline
71 original aspect ratio</li>
77 load pages significantly slower.
78 </li>
79 </ul>
80 </li>
83 </ul>
85 <!-- INTRODUCTION -->
88 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
89 a single database. To accomplish the latter you'll need a properly set up
90 MySQL user who can read/write only the desired database. It's up to you to
91 look up the appropriate part in the MySQL manual.
92 </p>
97 <li>create, copy, drop, rename and alter databases, tables, fields and
98 indexes</li>
99 <li>maintenance server, databases and tables, with proposals on server
100 configuration</li>
101 <li>execute, edit and bookmark any
103 batch-queries</li>
106 </li>
113 OpenDocument Text and Spreadsheet,
115 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
116 </li>
120 <li>using Query-by-example (QBE), create complex queries automatically
121 connecting required tables</li>
123 your Database layout</li>
125 <li>transform stored data into any format using a set of predefined
126 functions, like displaying BLOB-data as image or download-link
127 </li>
133 </li>
134 </ul>
137 <p> Many people have difficulty
138 understanding the concept of user management with regards to phpMyAdmin. When
139 a user logs in to phpMyAdmin, that username and password are passed directly
140 to MySQL. phpMyAdmin does no account management on its own (other than
141 allowing one to manipulate the MySQL user account information); all users
142 must be valid MySQL users.</p>
151 <!-- INSTALLATION -->
159 </ol>
162 phpMyAdmin does not apply any special security methods to the MySQL database
163 server. It is still the system administrator's job to grant permissions on
165 be used for this.
166 </p>
174 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
175 before uploading them to your server, as PHP seems not to like
180 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
181 Downloads page. Some kits contain only the English messages,
182 others contain all languages in UTF-8 format (this should be fine
183 in most situations), others contain all
184 languages and all character sets. We'll assume you chose a kit whose
186 </li>
187 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
189 document root. If you don't have direct access to your document root,
190 put the files in a directory on your local machine, and, after step 4,
191 transfer the directory on your web server using, for example, ftp.</li>
192 <li>Ensure that all the scripts have the appropriate owner (if PHP is
193 running in safe mode, having some scripts with an owner different
194 from the owner of other scripts will be a
199 <li>Now you must configure your installation. There are two methods that
200 can be used. Traditionally, users have hand-edited a copy of
202 provided for those who prefer a graphical installation. Creating a
203 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
204 <ul><li>To manually create the file, simply use your text editor to
207 file) in the main (top-level) phpMyAdmin directory (the one
211 default value is okay for a particular setting, there is no
213 few directives to get going, a simple configuration may look
214 like this:
215 <pre>
216 <?php
217 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
219 $i=0;
220 $i++;
221 $cfg['Servers'][$i]['auth_type'] = 'cookie';
222 ?>
223 </pre>
224 Or, if you prefer to not be prompted every time you log in:
225 <pre>
226 <?php
228 $i=0;
229 $i++;
230 $cfg['Servers'][$i]['user'] = 'root';
231 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
232 ?>
233 </pre>
234 For a full explanation of possible configuration values, see the
240 directory. This is a security measure. On a Linux/Unix system you
241 can use the following commands:
242 <pre>
243 cd phpMyAdmin
244 mkdir config # create directory for saving
245 chmod o+rw config # give it world writable permissions
246 </pre>
247 And to edit an existing configuration, copy it over first:
248 <pre>
249 cp config.inc.php config/ # copy current configuration for editing
250 chmod o+w config/config.inc.php # give it world writable permissions
251 </pre>
252 On other platforms, simply create the folder and ensure that your
261 the webserver does not have the proper permissions you may see the
263 config/</tt> directory exists and has the proper permissions -
265 and upload (via FTP or some similar means) to the proper location.<br /><br />
267 Once the file has been saved, it must be moved out of the <tt>
268 config/</tt> directory and the permissions must be reset, again
269 as a security measure:
270 <pre>
271 mv config/config.inc.php . # move file to current directory
272 chmod o-rw config.inc.php # remove world read and write permissions
273 </pre>
274 Now the file is ready to be used. You can choose to review or edit
275 the file with your favorite editor, if you prefer to set some
276 advanced options which the setup script does not provide.</li></ul></li>
277 <li>If you are using the
279 protect the phpMyAdmin installation directory because using
280 config does not require a user to
281 enter a password to access the phpMyAdmin installation. Use of an alternate
282 authentication method is recommended, for example with
290 in your browser. phpMyAdmin should now display a welcome screen
291 and your databases, or a login dialog if using
293 authentication mode.</li>
295 webserver configuration. For Apache you can use supplied .htaccess file
296 in that folder, for other webservers, you should configure this yourself.
297 Such configuration prevents from possible path exposure and cross side
298 scripting vulnerabilities that might happen to be found in that code.</li>
299 </ol>
303 <p> For a whole set of new features (bookmarks, comments,
306 transformation, etc.) you need to create a set of special tables. Those
307 tables can be located in your own database, or in a central database for a
308 multi-user installation (this database would then be accessed by the
309 controluser, so no other user should have rights to it).</p>
319 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
320 that you may need special (administrator) privileges to create the database
321 and tables, and that the script may need some tuning, depending on the
322 database name.</p>
327 section</a>. You will also need to have a controluser with the proper rights
334 unpacked one. Configuration files from very old versions (2.3.0 or before) may
335 require some tweaking as some options have been changed or removed.
337 statement that you might find near the end of your configuration file.</p>
341 is version-specific.</p>
344 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
345 you should run the SQL script found in
352 where you want to give users access to their own database and don't want
353 them to play around with others.<br />
354 Nevertheless be aware that MS Internet Explorer seems to be really buggy
356 in this area!<br />
359 that your user/password pair are not in clear in the configuration file.
360 </li>
363 authentication modes are more secure: the MySQL login information does
364 not need to be set in the phpMyAdmin configuration file (except possibly
366 However, keep in mind that the password travels in plain text, unless
367 you are using the HTTPS protocol.<br />
368 In cookie mode, the password is stored, encrypted with the blowfish
369 algorithm, in a temporary cookie.</li>
381 file under the
383 $cfg['Servers'][$i]['controluser']</a></tt> and
388 only an example: use something else in your file!</b> Input these
389 statements from the phpMyAdmin SQL Query window or mysql command–line
390 client.<br />
392 if it's not the same as the MySQL server's one.
394 <pre>
395 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
396 GRANT SELECT (
397 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
398 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
399 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
400 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
401 Execute_priv, Repl_slave_priv, Repl_client_priv
402 ) ON mysql.user TO 'pma'@'localhost';
403 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
404 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
405 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
406 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
408 If you want to use the many new relation and bookmark features:
410 <pre>
412 </pre>
418 on a set of particular databases. Normally you shouldn't give global
419 privileges to an ordinary user, unless you understand the impact of those
420 privileges (for example, you are creating a superuser).<br />
424 <pre>
425 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
426 </pre>
428 What the user may now do is controlled entirely by the MySQL user
429 management system.<br />
431 authentication mode, you don't need to fill the user/password fields
433 array.</li>
434 </ul>
439 method and allows you to log in as any valid MySQL user.</li>
440 <li>Is supported with most PHP configurations. For
453 mode.</li>
454 </ul>
458 <ul><li>You can use this method as a replacement for the
460 (for example, if you're running
462 <li>Obviously, the user must enable cookies in the browser, but this is
463 now a requirement for all authentication modes.</li>
464 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
465 with the same username.</li>
466 <li>If you want to log in to arbitrary server see
471 not required.</li>
472 </ul>
476 <ul><li>This mode is a convenient way of using credentials from another
477 application to authenticate to phpMyAdmin.</li>
478 <li>The other application has to store login information into
479 session data.</li>
481 section.</li>
482 </ul>
485 <ul><li>This mode is the less secure one because it requires you to fill the
487 $cfg['Servers'][$i]['user']</a> and
489 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
490 can read your config.inc.php can discover your username and password).
491 <br />
498 is an entry explaining how to protect your configuration file.</li>
499 <li>For additional security in this mode, you may wish to consider the Host
500 authentication
502 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
504 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
505 directives.</li>
506 <li>Unlike cookie and http, does not require a user to log in when first
507 loading the phpMyAdmin site. This is by design but could allow any
508 user to access your installation. Use of some restriction method is
510 HTTP-AUTH directive or disallowing incoming HTTP requests at
511 one’s router or firewall will suffice (both of which
512 are beyond the scope of this manual but easily searchable with Google).</li>
513 </ul>
515 <p>
516 The Swekey is a low cost authentication USB key that can be used in
517 web applications.<br /><br />
518 When Swekey authentication is activated, phpMyAdmin requires the
519 users's Swekey to be plugged before entering the login page (currently
520 supported for cookie authentication mode only). Swekey Authentication is
521 disabled by default.<br /><br />
523 </p>
524 <pre>
525 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
526 </pre>
527 <p>
529 each user with their Swekey Id. It is important to place this file outside
530 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
532 users' information.<br /><br />
533 If you want to purchase a Swekey please visit
535 since this link provides funding for phpMyAdmin.
536 </p>
537 <!-- CONFIGURATION -->
541 users:</span> PHP does not seem to like
545 before saving a script you have modified.</p>
550 section to create one. This file only needs to contain the parameters you want to
551 change from their corresponding default value in
554 <p> The parameters which relate to design (like colors) are placed in
557 your site specific code to be included on start and end of each page.</p>
561 (with full path) to your phpMyAdmin installation's directory.
564 some web servers are case–sensitive.
567 Starting with version 2.3.0, it is advisable to try leaving this
568 blank. In most cases phpMyAdmin automatically detects the proper
569 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
570 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
571 A good test is to browse a table, edit a row and save it. There should
572 be an error message if phpMyAdmin is having trouble auto–detecting
573 the correct value. If you get an error that this must be set or if
574 the autodetect code fails to detect your path, please post a bug
575 report on our bug tracker so we can improve the code.</dd>
579 with master / foreign – tables (see
581 <br />
582 If you tried to set this up and it does not work for you, have a look on
584 use it. You will find a link that will analyze why those features have
585 been disabled.<br />
586 If you do not want to use those features set this variable to
590 <dd>A warning is displayed on the main page if Suhosin is detected.
592 from appearing.</dd>
596 domain to call phpMyAdmin inside a frame, and is a potential security
597 hole allowing cross-frame scripting attacks.</dd>
601 algorithm to encrypt the password.<br />
603 passphrase of your choice. It will be used internally by the blowfish
604 algorithm: you won’t be prompted for this passphrase. The maximum
607 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
608 makes a bit weaker security as this generated secret is stored in
609 session and furthermore it makes impossible to recall user name from
610 cookie.</dd>
614 MySQL servers. Therefore, a
616 been added which contains the login information for the different servers.
617 The first
619 contains the hostname of the first server, the second
621 the hostname of the second server, etc. In
623 server definition, however you can put as many as you need in
625 have to define all settings, just those you need to change).</dd>
629 $i-th MySQL-server. E.g. localhost.</dd>
634 ignores this port number and connects with the socket, so if you want
635 to connect to a port different from the default port, use
638 </dd>
642 To determine the correct socket, check your MySQL configuration or, using the
644 Among the resulting information displayed will be the socket used.</dd>
647 <dd>Whether to enable SSL for connection to MySQL server.
648 </dd>
651 <dd>What type connection to use with the MySQL server. Your options are
653 is nearly guaranteed to be available on all MySQL servers, while
654 sockets are not supported on some platforms.<br /><br />
656 To use the socket mode, your MySQL server must be on the same machine
657 as the Web server.</dd>
660 <dd>What php MySQL extension to use for the connection. Valid options are:
661 <br /><br />
664 The classic MySQL extension. This is the recommended and default
665 method at this time.<br /><br />
668 The improved MySQL extension. This extension became available
669 with php 5.0.0 and is the recommended way to connect to a server
673 <dd>Whether to use a compressed protocol for the MySQL server connection
674 or not (experimental).<br />
680 </dt>
682 all relational features (see
684 and, for a MySQL server previous to 4.1.2 or running with
687 authentication mode).<br /><br />
690 cookie authentication modes (or 'config'
691 authentication mode since phpMyAdmin 2.2.1), you need to supply the
696 This account is used to check what databases the user will see at
697 login.<br />
701 In phpMyAdmin versions before 2.2.5, those were called
705 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
706 <dd>Whether config or cookie or
708 should be used for this server.
710 is the plain old way: username and password are stored in
712 <li>'cookie' authentication mode
714 2.2.3 allows you to log in as any valid MySQL user with the
715 help of cookies. Username and password are stored in
716 cookies during the session and password is deleted when it
717 ends. This can also allow you to log in in arbitrary server if
718 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
719 </li>
720 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
721 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
722 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
723 <li>'signon' authentication mode
725 as introduced in 2.10.0 allows you to log in from prepared PHP
726 session data. This is useful for implementing single signon
727 from another application. Sample way how to seed session is in
733 </ul>
736 for more information.
737 </dd>
739 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
740 </dt>
741 <dd>
743 names for hardware authentication. Leave empty to deactivate this feature.
744 </dd>
748 </dt>
749 <dd>
750 When using auth_type = 'config', this is the user/password-pair
751 which phpMyAdmin will use to connect to the
752 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
753 cookie authentication is used and should be empty.</dd>
755 <span
757 </dt>
758 <dd>
759 Allow attempt to log in without password when a login with password
760 fails. This can be used together with http authentication, when
761 authentication is done some other way and phpMyAdmin gets user name
762 from auth and uses empty password for connecting to MySQL. Password
763 login is still tried first, but as fallback, no password method is
764 tried.</dd>
767 </dt>
768 <dd>
769 If set to a (an array of) database name(s), only this (these) database(s)
770 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
771 database(s) name(s) may contain MySQL wildcards characters
775 This setting is an efficient way to lower the server load since the
776 latter does not need to send MySQL requests to build the available
778 privileges rules of the MySQL database server</span>. If set, it just
779 means only these databases will be displayed but
781 <br /><br />
783 An example of using more that one database:
785 <br /><br />
787 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
788 databases in the left frame, so that you can individually arrange your databases.<br />
789 If you want to have certain databases at the top, but don't care about the others, you do not
790 need to specify all other databases. Use:
792 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
793 order.</dd>
796 </dt>
797 <dd>Regular expression for hiding some databases. This only hides them
798 from listing, but a user is still able to access them (using, for example,
799 the SQL query area). To limit access, use the MySQL privilege system.
800 <br /><br />
805 More information on regular expressions can be found in the
807 PCRE pattern syntax</a> portion of the PHP reference manual.
808 </dd>
811 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
812 this string will be displayed instead of the hostname in the pull-down
813 menu on the main page. This can be useful if you want to show only
814 certain databases on your system, for example. For HTTP auth, all
815 non-US-ASCII characters will be stripped.</dd>
819 </dt>
820 <dd>The name of the database containing the linked-tables infrastructure.
821 <br /><br />
824 section in this document to see the benefits of this infrastructure,
825 and for a quick way of creating this database and the needed tables.
826 <br /><br />
828 If you are the only user of this phpMyAdmin installation, you can
829 use your current database to store those special tables; in this
830 case, just put your current database name in
832 set this parameter to the name of your central database containing
833 the linked-tables infrastructure.</dd>
837 </dt>
839 useful for queries you often run.<br /><br />
841 To allow the usage of this functionality:
843 <li>enter the table name in
845 </ul>
846 </dd>
850 </dt>
852 which field is a key in another table (a foreign key). phpMyAdmin
853 currently uses this to
854 <ul><li>make clickable, when you browse the master table, the data values
855 that point to the foreign table;</li>
857 when browsing the master table, if you move the mouse to a column
858 containing a foreign key (use also the 'table_info' table);<br />
861 <li>in edit/insert mode, display a drop-down list of possible foreign
865 <li>display links on the table properties page, to check referential
866 integrity (display missing foreign keys) for each described key;
867 </li>
871 schema of your database (also uses the table_coords table).</li>
872 </ul>
874 The keys can be numeric or character.<br /><br />
876 To allow the usage of this functionality:
879 infrastructure</li>
880 <li>put the relation table name in
882 <li>now as normal user open phpMyAdmin and for each one of your
883 tables where you want to use this feature, click
885 </li>
886 </ul>
890 future development of the cross-db relations.
891 </dd>
895 </dt>
896 <dd>
897 Since release 2.3.0 you can describe, in a special 'table_info'
898 table, which field is to be displayed as a tool-tip when moving the
899 cursor over the corresponding key.<br />
900 This configuration variable will hold the name of this special
901 table. To allow the usage of this functionality:
903 <li>put the table name in
905 <li>then for each table where you want to use this feature,
907 to choose the field.</li>
908 </ul>
910 </dd>
914 </dt>
917 the relations between your tables. To do this it needs two tables
922 schema output).<br /><br />
926 To allow the usage of this functionality:
929 infrastructure</li>
930 <li>put the correct table names in
933 </ul>
936 </dd>
940 </dt>
942 Since release 2.3.0 you can store comments to describe each column for
944 <br /><br />
946 Starting with release 2.5.0, comments are consequently used on the table
947 property pages and table browse view, showing up as tool-tips above the
948 column name (properties page) or embedded within the header of table in
949 browse view. They can also be shown in a table dump. Please see the
950 relevant configuration directives later on.<br /><br />
952 Also new in release 2.5.0 is a MIME-transformation system which is also
954 Transformations</a> for further information. To use the
955 MIME-transformation system, your column_info table has to have the three
956 new fields 'mimetype', 'transformation', 'transformation_options'.
957 <br /><br />
959 To allow the usage of this functionality:
961 infrastructure</li>
962 <li>put the table name in
966 <pre>
967 ALTER TABLE `pma_column_comments`
968 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
969 ADD `transformation` VARCHAR( 255 ) NOT NULL,
970 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
971 </pre>
974 renamed from<br />
977 </ul>
978 </dd>
982 </dt>
985 all queries you entered manually into the phpMyAdmin interface. If you
986 don't want to use a table-based history, you can use the JavaScript-based
987 history. Using that, all your history items are deleted when closing the
988 window.<br /><br />
990 Using
992 you can specify an amount of history items you want to have on hold. On
993 every login, this list gets cut to the maximum amount.<br /><br />
995 The query history is only available if JavaScript is enabled in your
996 browser.<br /><br />
998 To allow the usage of this functionality:
1001 infrastructure</li>
1003 </li>
1004 </ul>
1005 </dd>
1009 </dt>
1011 to visually manage the relations.
1012 <br /><br />
1014 To allow the usage of this functionality:
1017 infrastructure</li>
1019 </li>
1020 </ul>
1021 </dd>
1024 </dt>
1026 column_info table got enhanced with three new fields. If the above variable
1028 latest table structure available. If not, it will emit a warning to the
1029 superuser.<br /><br />
1031 You can disable this checking behavior by setting the variable to false,
1032 which should offer a performance increase.<br /><br />
1034 Recommended to set to FALSE, when you are sure, your table structure is
1035 up to date.</dd>
1037 boolean</dt>
1038 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1039 </dd>
1040 <dt><span id="cfg_Servers_AllowNoPasswordRoot">$cfg['Servers'][$i]['AllowNoPasswordRoot']</span>
1041 boolean</dt>
1042 <dd>Whether to allow access to root user without password. The default
1044 to a MySQL server with was left with an empty password for root.
1045 </dd>
1048 </dt>
1050 authentication is disabled.<br /><br />
1053 all deny rules followed by allow rules. Access is allowed by default. Any
1054 client which does not match a Deny command or does match an Allow command
1055 will be allowed access to the server. <br /><br />
1058 applies all allow rules followed by deny rules. Access is denied by
1059 default. Any client which does not match an Allow directive or does
1060 match a Deny directive will be denied access to the server.<br /><br />
1062 If your rule order is set to 'explicit', the authentication is
1063 performed in a similar fashion to rule order 'deny,allow', with the
1067 and was available in Apache by specifying allow and deny rules without
1068 setting any order.<br /><br />
1070 Please also see <a
1072 address behind proxies.
1073 </dd>
1075 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1076 </dt>
1077 <dd>The general format for the rules is as such:
1079 <pre>
1081 </pre>
1086 well (please note that those containing SERVER_ADDRESS might not be
1087 available on all webservers):
1088 <pre>
1094 </pre>
1096 Having an empty rule list is equivalent to either using
1102 following work:<br />
1104 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1105 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1106 But the following does not work:<br />
1109 </dd>
1110 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1111 <dd>Name of session which will be used for signon authentication method.
1112 </dd>
1114 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1115 </dd>
1117 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1118 </dd>
1121 <dd>If you have more than one server configured, you can set
1123 that server when phpMyAdmin is started, or set it to 0 to be given a
1124 list of servers without logging in.<br />
1126 MUST be set to that server.</dd>
1129 <dd>The maximum number of database names to be displayed in the
1130 navigation frame and the database list.</dd>
1133 <dd>The maximum number of table names to be displayed in the
1134 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1135 when in Light mode.</dd>
1138 <dd>The maximum number of characters when a SQL query is displayed. The
1139 default limit of 1000 should be correct to avoid the display of tons
1140 of hexadecimal codes that represent BLOBs, but some users have real
1141 SQL queries that are longer than 1000 characters. Also, if a query's
1142 length exceeds this limit, this query is not saved in the history.</dd>
1145 <dd>Defines whether to use GZip output buffering for increased
1147 Set to true/false for enabling/disabling. When set to 'auto' (string),
1148 phpMyAdmin tries to enable output buffering and will automatically disable
1149 it if your browser has some problems with buffering. IE6 with a certain patch
1150 is known to cause data corruption when having enabled buffering.</dd>
1153 <dd>Whether persistent connections should be used or not (mysql_connect or
1154 mysql_pconnect).</dd>
1160 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1161 to zero, no time limit is imposed.<br />
1162 This setting is used while importing/exporting dump files but has no
1163 effect when PHP is running in safe mode.</dd>
1166 <dd>Set the number of bytes a script is allowed to allocate. If number set
1167 to zero, no limit is imposed.<br />
1168 This setting is used while importing/exporting dump files but has no
1169 effect when PHP is running in safe mode.<br />
1173 <dd>Mark used tables and make it possible to show databases with locked
1178 generated by phpMyAdmin should be displayed or not.</dd>
1181 <dd>Defines whether normal users (non-administrator) are allowed to
1182 delete their own database or not. If set as FALSE, the link "Drop
1184 mydatabase" will be rejected. Quite practical for
1186 customers.<br />
1187 Please note that this limitation of SQL queries is not as strict as
1188 when using MySQL privileges. This is due to nature of SQL queries
1189 which might be quite complicated. So this choice should be viewed as
1190 help to avoid accidental dropping rather than strict privilege
1191 limitation.</dd>
1195 displayed when you're about to lose data.</dd>
1198 <dd>Define whether the previous login should be recalled or not in cookie
1199 authentication mode.<br /><br />
1201 This is automatically diabled if you do not have configured
1203 </dd>
1210 means that it will be kept for existing session. This is recommended
1211 for not trusted environments.</dd>
1214 <dd>If enabled (default), logout deletes cookies for all servers,
1215 otherwise only for current one. Setting this to false makes it easy to
1216 forget to log out from other server, when you are using more of
1217 them.</dd>
1223 <dd>Define whether phpMyAdmin will continue executing a multi-query
1224 statement if one of the queries fails. Default is to abort execution.</dd>
1227 <dd>Define whether phpMyAdmin will output the results of each query of a
1228 multi-query statement embedded into the
1233 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1234 <br /><br />
1237 MySQL servers behind the firewall where your
1239 </dd>
1242 <dd>Defines whether to use a select-based menu and display only the current
1243 tables in the left frame (smaller page). Only in Non-Lightmode you can
1244 use the feature to display nested folders using
1246 </dd>
1249 <dd>In light mode, defines whether to display the names of databases (in the
1250 selector) using a tree, see also
1252 </dd>
1255 <dd>The string used to separate the parts of the database name when showing
1256 them in a tree.</dd>
1259 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1260 This means if you have tables like 'first__second__third' this will be
1262 If set to FALSE or empty, the feature is disabled. NOTE: You should
1263 not use this separator at the beginning or end of a
1264 table name or multiple times after another without any other
1265 characters in between.</dd>
1268 <dd>Defines how many sublevels should be displayed when splitting
1269 up tables by the above separator.</dd>
1272 <dd>Defines whether to display table comment as tool-tip in left frame or
1273 not.</dd>
1276 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1277 comment and the real name. That means that if you have a table called
1278 'user0001' and add the comment 'MyName' on it, you will see the name
1279 'MyName' used consequently in the left frame and the tool-tip shows
1280 the real name of the DB.</dd>
1283 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1285 When setting this to 'nested', the Alias of the Tablename is only used
1286 to split/nest the tables according to the
1288 directive. So only the folder is called like the Alias, the tablename itself
1289 stays the real tablename.</dd>
1292 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1295 <dd>Enter URL where logo in the navigation frame will point to.
1296 For use especially with self made theme which changes this.
1305 <dd>Defines whether or not to display a server choice at the top of the left frame.
1306 Defaults to FALSE.</dd>
1308 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1309 Defaults to FALSE (drop-down).</dd>
1311 <dd>Defines whether to display database choice in light navigation frame as links
1312 instead of in a drop-down. Defaults to 'auto' - on main page list is
1313 shown, when database is selected, only drop down is displayed.</dd>
1316 <dd>Defines the tab displayed by default when clicking the small
1317 icon next to each table name in the navigation panel. Possible
1323 <dd>Defines whether or not to display space usage and statistics about databases
1324 and tables.<br />
1325 Note that statistics requires at least MySQL 3.23.3 and that, at this
1326 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1329 <dd>Defines whether to display detailed server information on main page.
1330 You can additionally hide more information by using
1332 </dd>
1337 </dt>
1340 not at the starting main (right) frame. This setting
1341 does not check MySQL commands entered directly.<br /><br />
1343 Please note that to block the usage of phpinfo() in scripts, you
1350 hard coded password value in the configuration file, end users can't
1351 be allowed to change their passwords.</dd>
1354 <dd>Defines whether to suggest a database name on the
1358 <dd>Defines whether navigation bar buttons and the right panel top menu
1359 contain text or symbols only. A value of TRUE displays icons, FALSE
1360 displays text and 'both' displays both icons and text.</dd>
1363 <dd>Defines whether a user should be displayed a
1367 <dd>Number of rows displayed when browsing a result set. If the result set
1374 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1378 from editing when browsing a table's content. Valid values are:
1383 </ul>
1384 </dd>
1387 <dd>Defines whether or not MySQL functions fields should be initially
1388 displayed in edit/insert mode. Since version 2.10, the user can
1389 toggle this setting from the interface.
1390 </dd>
1393 <dd>Defines which type of editing controls should be used for CHAR and
1394 VARCHAR fields. Possible values are:
1395 <ul><li>input - this allows to limit size of text to size of field in
1396 MySQL, but has problems with newlines in fields</li>
1397 <li>textarea - no problems with newlines in fields, but also no
1398 length limitations</li>
1399 </ul>
1400 Default is old behavior so input.</dd>
1406 <dd>If there are fewer items than this in the set of foreign keys, then a
1407 drop-down box of foreign keys is presented, in the style described by the
1409 setting.</dd>
1412 <dd>For the foreign key drop-down fields, there are several methods of
1413 display, offering both the key and value data. The contents of the
1414 array should be one or both of the following strings:
1420 </dt>
1421 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1422 creating a dump file</dd>
1425 </dt>
1426 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1427 compressed exports. This doesn't affect smaller dumps and allows users to
1428 create larger dumps that won't otherwise fit in memory due to php
1429 memory limit. Produced files contain more GZip/BZip2 headers, but all
1430 normal programs handle this correctly.</dd>
1434 mainframe.</dd>
1438 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1443 <dd>How many columns will be utilized to display the tables on the
1444 database property view? Default is 1 column. When setting this to a
1445 value larger than 1, the type of the database will be omitted for more
1446 display space.</dd>
1450 <dd>Defines the tab displayed by default on server view. Possible
1457 <dd>Defines the tab displayed by default on database view. Possible
1462 <dd>Defines the tab displayed by default on table view. Possible
1469 points to the MySQL documentation (type depends
1470 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1471 generated.<br />
1473 for more information about MySQL manuals and their types.</dd>
1476 <dd>Type of MySQL documentation:
1482 </ul>
1483 </dd>
1486 <dd>Defines the default language to use, if not browser-defined or
1487 user-defined.<br />
1489 this setting.</dd>
1492 <dd>Defines the default connection collation to use, if not
1493 user-defined.<br />
1498 <dd>Force: always use this language (must be defined in the
1502 <dd>Limit list of available languages to those matching the given regular
1503 expression. For example if you want only Czech and English, you should
1507 <dd>Default character set to use for recoding of MySQL queries. This must be
1508 enabled and it's described by
1510 option.<br />
1511 You can give here any character set which is in
1513 array and this is just default choice, user can select any of them.</dd>
1516 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1517 support (compiled in or module) in PHP to allow MySQL queries recoding
1518 and used language file must have it enabled (by default only these
1519 which are in Unicode, just to avoid losing some characters).<br /><br />
1522 in the Export page, to choose the character set when exporting a file.
1524 </dd>
1527 <dd>You can select here which functions will be used for character set
1528 conversion. Possible values are:
1529 <ul><li>auto - automatically use available one (first is tested
1530 iconv, then recode)</li>
1533 </ul>
1534 Default is auto.</dd>
1537 <dd>Specify some parameters for iconv used in charset conversion. See
1540 used, so that invalid characters will be transliterated.</dd>
1543 <dd>Available character sets for MySQL conversion. You can add your own (any of
1544 supported by recode/iconv) or remove these which you don't use.
1545 Character sets will be shown in same order as here listed, so if you
1546 frequently use some of these move them to the top.</dd>
1551 default empty, you need to fill in some trusted proxy servers if you
1552 want to use rules for IP addresses behind proxy.<br /><br />
1554 The following example specifies that phpMyAdmin should trust a
1556 <pre>
1557 $cfg['TrustedProxies'] =
1559 </pre>
1560 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1561 client's IP address as usual.
1562 </dd>
1566 MIME transformations.<br />
1567 Possible values are:
1568 <ul><li>auto - automatically detect, this is a bit expensive
1570 according to your server real possibilities</li>
1573 </ul>
1574 Default is auto.
1575 </dd>
1578 <dd>
1579 We normally check the permissions on the configuration file to ensure
1580 it's not world writable. However, phpMyAdmin could be installed on
1581 a NTFS filesystem mounted on a non-Windows server, in which case the
1582 permissions seems wrong but in fact cannot be detected. In this case
1584 </dd>
1588 </dd>
1590 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1591 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1592 </dt>
1593 <dd>The background styles used for both the frames.
1596 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1598 <dd>The style used for the pointer in the navi frame.
1602 </dt>
1603 <dd>The color used for the database name in the navi frame.
1612 </dd>
1616 <dd>The style used for table headers. See
1621 </dd>
1625 </dd>
1627 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1629 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1631 </dt>
1633 The former feature highlights the row over which your mouse is passing
1634 and the latter lets you visually mark/unmark rows by clicking on
1635 them.<br />
1640 <dd>You put here a valid CSS font family value, for example
1645 <dd>You put here a valid CSS font family value, for example
1659 </dt>
1661 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1663 The Char* values are used for CHAR and VARCHAR editing (if configured
1667 </dt>
1671 </dt>
1672 <dd>Defines if the whole textarea of the query box will be selected on
1673 click.</dd>
1676 </dt>
1677 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1678 editing.</dd>
1681 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1682 Can be turned off by a toggle button on the browse page.</dd>
1686 </dt>
1687 <dd>Defines the place where modify and delete links would be put when
1688 tables contents are displayed (you may have them displayed both at the
1689 left and at the right).
1695 </dt>
1697 Define which one is displayed by default. The first mode displays each
1698 row on a horizontal line, the second rotates the headers by 90
1699 degrees, so you can use descriptive headers even though fields only
1700 contain small values and still print them out. The vertical mode sorts
1701 each row on a vertical lineup.<br /><br />
1703 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1704 the rotation of the header for horizontalflipped is done via CSS. If
1705 set to 'fake' PHP does the transformation for you, but of course this
1706 does not look as good as CSS.</dd>
1710 string or integer</dt>
1711 <dd>When editing/creating new columns in a table all fields normally get
1712 lined up one field a line. (default: 'horizontal'). If you set this to
1713 'vertical' you can have each field lined up vertically beneath each
1714 other. You can save up a lot of place on the horizontal direction and
1715 no longer have to scroll. If you set this to integer, editing of fewer
1716 columns will appear in 'vertical' mode, while editing of more fields
1717 still in 'horizontal' mode. This way you can still effectively edit
1718 large number of fields, while having full view on few of them.</dd>
1722 </dt>
1724 display of column comments in Browse or Property display. In browse
1725 mode, the comments are shown inside the header. In property mode,
1726 comments are displayed using a CSS-formatted dashed-line below the
1727 name of the field. The comment is shown as a tool-tip for that field.
1728 </dd>
1740 <dd>Whether to display a link to validate a query in any SQL Query box.
1747 <dd>
1748 The name of the directory where
1750 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1751 are available under a drop-down box when you click the database or
1752 table name, then the Import tab.
1753 <br /><br />
1755 If you want different directory for each user, %u will be replaced
1756 with username.<br /><br />
1760 compressed formats is enabled).<br /><br />
1762 This feature is useful when your file is too big to be uploaded via
1764 uploads are disabled in PHP.<br /><br />
1766 Please note that if PHP is running in safe mode, this directory must
1767 be owned by the same user as the owner of the phpMyAdmin scripts.
1768 <br /><br />
1772 alternatives.
1773 </dd>
1776 <dd>
1777 The name of the directory where dumps can be saved.<br /><br />
1779 If you want different directory for each user, %u will be replaced
1780 with username.<br /><br />
1782 Please note that the directory must exist and has to be writable for
1783 the user running webserver.<br /><br />
1785 Please note that if PHP is running in safe mode, this directory must
1786 be owned by the same user as the owner of the phpMyAdmin scripts.
1787 </dd>
1790 <dd>
1791 The name of the directory where temporary files can be stored.
1792 <br /><br />
1794 This is needed for native MS Excel export, see
1800 <br /><br />
1802 If the directory where phpMyAdmin is installed is subject to an
1804 temporary directory in some directory accessible by the web
1805 server. However for security reasons, this directory should be outside
1806 the tree published by webserver. If you cannot avoid having this
1807 directory published by webserver, place at least an empty
1809 possible.
1810 <br /><br />
1812 This directory should have as strict permissions as possible as the only
1813 user required to access this directory is the one who runs the
1814 webserver. If you have root privileges, simply make this user owner of
1815 this directory and make it accessible only by it:
1816 <br /><br />
1818 <pre>
1819 chown www-data:www-data tmp
1820 chmod 700 tmp
1821 </pre>
1823 If you cannot change owner of the directory, you can achieve a similar
1826 <pre>
1827 chmod 700 tmp
1828 setfacl -m "g:www-data:rwx" tmp
1829 setfacl -d -m "g:www-data:rwx" tmp
1830 </pre>
1832 If neither of above works for you, you can still make the directory
1834 system reading and writing data in this directory.
1835 </dd>
1838 <dd>
1839 In this array are defined default parameters for export, names of
1840 items are similar to texts seen on export page, so you can easily
1841 identify what they mean.
1842 </dd>
1845 <dd>
1846 In this array are defined default parameters for import, names of
1847 items are similar to texts seen on import page, so you can easily
1848 identify what they mean.
1849 </dd>
1852 <dd>
1853 Repeat the headers every X cells, or 0 to deactivate.
1854 </dd>
1862 </dt>
1863 <dd>
1864 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1865 or icon is always displayed on the left panel. If JavaScript is enabled in
1866 your browser, a click on this opens a distinct query window, which is
1867 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1868 changes to display a query box.<br /><br />
1870 The size of this query window can be customized with
1872 - both integers for the size in pixels. Note that normally, those
1874 theme you are using.<br /><br />
1878 opens the query window and puts the current query
1879 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1880 query in the right panel's query box.
1881 <br /><br />
1882 The usage of the JavaScript query window is recommended if you have a
1883 JavaScript enabled browser. Basic functions are used to exchange quite
1884 a few variables, so most 4th generation browsers should be capable to
1885 use that feature. It currently is only tested with Internet Explorer 6
1886 and Mozilla 1.x.
1887 <br /><br />
1889 to a table, which has to be created by you (see <a
1891 all your queries will be appended to the form, but only as long as
1892 your window is opened they remain saved.
1893 <br /><br />
1894 When using the JavaScript based query window, it will always get
1895 updated when you click on a new table/db to browse and will focus if
1896 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1897 the query window by checking the box "Do not overwrite this query from
1898 outside the window" below the query textarea. Then you can browse
1899 tables/databases in the background without losing the contents of the
1900 textarea, so this is especially useful when composing a query with
1901 tables you first have to look in. The checkbox will get automatically
1902 checked whenever you change the contents of the textarea. Please
1903 uncheck the button whenever you definitely want the query window to
1904 get updated even though you have made alterations.
1905 <br /><br />
1908 <br /><br />
1909 The query window also has a custom tabbed look to group the features.
1911 default tab to be used when opening the query window. It can be set to
1912 either 'sql', 'files', 'history' or 'full'.</dd>
1918 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1920 If the approximate row count as returned by
1923 count will be used.
1924 </dd>
1926 <dd>For VIEWs, since obtaining the exact count could have an
1927 impact on performance, this value is the maximum to be displayed, using
1929 any row counting.
1930 </dd>
1934 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1936 page. By clicking on the button 'toggle scratchboard' on the page
1937 where you edit x/y coordinates of those elements you can activate a
1938 scratchboard where all your elements are placed. By clicking on an
1939 element, you can move them around in the pre-defined area and the x/y
1940 coordinates will get updated dynamically. Likewise, when entering a
1941 new position directly into the input field, the new position in the
1942 scratchboard changes after your cursor leaves the input field.<br />
1943 You have to click on the 'OK'-button below the tables to save the new
1944 positions. If you want to place a new element, first add it to the
1945 table of elements and then you can drag the new element around.<br />
1946 By changing the paper size and the orientation you can change the size
1947 of the scratchboard as well. You can do so by just changing the
1948 dropdown field below, and the scratchboard will resize automatically,
1949 without interfering with the current placement of the elements.<br />
1950 If ever an element gets out of range you can either enlarge the paper
1951 size or click on the 'reset' button to place all elements below each
1952 other.<br />
1954 get this control to work. The basic Drag&Drop script functionality
1955 was kindly borrowed from www.youngpup.net and is underlying so
1956 specific license.</dd>
1959 <dd>Sorts database and table names according to natural order (for example,
1960 t1, t2, t10). Currently implemented in the left panel (Light mode)
1961 and in Database view, for the table list.</dd>
1965 closed state. A value of 'open' does the reverse.</dd>
1971 <dd>Allows you to specify window's title bar. Following magic string can
1972 be used to get special values:
1973 <dl>
1979 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1988 </dl>
1989 </dd>
1999 </dd>
2002 <dd>If theme manager is active, use this as the path of the subdirectory
2003 containing all the themes.</dd>
2017 </dt>
2018 <dd>Default queries that will be displayed in query boxes when user didn't
2019 specify any. Use %d for database name, %t for table name and %f for a
2020 comma separated list of field names. Note that %t and %f are only
2024 <dd>
2025 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
2026 default we use HTML to format the query, but you can disable this by
2028 </dd>
2031 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2032 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2033 query inside a bracket is indented. By changing
2036 specifies the units of the indent amount that you specified. This is
2037 used via stylesheets.</dd>
2040 <dd>This array is used to define the colours for each type of element of
2041 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2043 If you specify an empty string for the color of a class, it is ignored
2044 in creating the stylesheet.
2045 You should not alter the class names, only the colour strings.<br />
2066 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2070 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2071 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2072 </ul>
2073 </dd>
2077 <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,
2078 as originally published on
2080 <br />
2081 For help in setting up your system to use the service, see the
2083 </dd>
2087 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2088 and any password, so we use those by default. Instead, if
2089 you have an account with them, you can put your login details
2090 here, and it will be used in place of the anonymous login.</dd>
2091 </dl>
2092 </dd>
2095 <dd><b>DEVELOPERS ONLY!</b></dd>
2098 <dd><b>DEVELOPERS ONLY!</b><br />
2099 Enable logging queries and execution times to be displayed in the bottom
2100 of main page (right frame).</dd>
2103 <dd><b>DEVELOPERS ONLY!</b><br />
2104 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2105 the code.<br />
2106 For help in setting up your system to this, see the
2110 <dd><b>DEVELOPERS ONLY!</b><br />
2111 Enable profiling support for phpMyAdmin. This will append a chunk of data
2112 to the end of every page displayed in the main window with profiling
2113 statistics for that page.<br />
2114 You may need to increase the maximum execution time for this to
2115 complete successfully.<i>Profiling was removed from the code for
2116 version 2.9.0 due to licensing issues.</i></dd>
2118 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2119 <dd><b>DEVELOPERS ONLY!</b><br />
2120 When profiling data is displayed, this variable controls the threshold of
2121 display for any profiling data, based on the average time each time has
2122 taken. If it is over the threshold it is displayed, otherwise it is not
2123 displayed. This takes a value in milliseconds. In most cases you don't need
2124 to edit this.</dd>
2127 <dd>All possible types of a MySQL column. In most cases you don't need to
2128 edit this.</dd>
2131 <dd>Possible attributes for fields. In most cases you don't need to edit
2132 this.</dd>
2135 <dd>A list of functions MySQL supports. In most cases you don't need to
2136 edit this.</dd>
2139 <dd>Mapping of column types to meta types used for preferring displayed
2140 functions. In most cases you don't need to edit this.</dd>
2143 <dd>Functions preferred for column meta types as defined in
2144 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2145 to edit this.</dd>
2148 <dd>Functions selected by default when inserting/changing row, Functions
2149 are defined for meta types from
2151 <code>first_timestamp</code>, which is used for first timestamp column
2152 in table.</dd>
2155 <dd>Operators available for search operations on numeric and date fields.
2156 </dd>
2159 <dd>Operators available for search operations on character fields.
2160 Note that we put <code>LIKE</code> by default instead of
2161 <code>LIKE %...%</code>, to avoid unintended performance problems
2162 in case of huge tables.</dd>
2165 <dd>Operators available for search operations on enum fields.</dd>
2168 <dd>Additional operators available for search operations when the
2169 field can be null.</dd>
2171 </dl>
2173 <!-- TRANSFORMATIONS -->
2179 </ol>
2183 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2185 section</a> on how to do so.</p>
2187 <p> You can apply different transformations to the contents of each field. The
2188 transformation will take the content of each field and transform it with
2189 certain rules defined in the selected transformation.</p>
2191 <p> Say you have a field 'filename' which contains a filename. Normally you would
2192 see in phpMyAdmin only this filename. Using transformations you can transform
2193 that filename into a HTML link, so you can click inside of the phpMyAdmin
2194 structure on the field's link and will see the file displayed in a new browser
2195 window. Using transformation options you can also specify strings to
2196 append/prepend to a string or the format you want the output stored in.</p>
2198 <p> For a general overview of all available transformations and their options,
2199 you can consult your
2200 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2201 installation.</p>
2203 <p> For a tutorial on how to effectively use transformations, see our
2205 the official phpMyAdmin homepage.</p>
2209 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2210 clicking on the 'Structure' link for a table). There click on
2211 "Change" (or change icon) and there you will see three new fields at
2212 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2213 'Transformation options'.</p>
2215 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2216 that corresponds to the column's contents. Please note that
2217 transformations are inactive as long as no MIME-type is selected.</li>
2219 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2220 hopefully growing amount of pre-defined transformations. See below for information on
2221 how to build your own transformation.<br />
2223 There are global transformations and mimetype-bound transformations. Global transformations
2224 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2225 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2226 transformations which operate on the main mimetype (like 'image'), which will most likely
2227 take the subtype into regard, and those who only operate on a
2228 specific subtype (like 'image/jpeg').<br />
2230 You can use transformations on mimetypes for which the function was not defined for. There
2231 is no security check for you selected the right transformation, so take care of what the
2232 output will be like.</li>
2234 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2235 transform-function specific options here. Usually the transforms can operate with default
2236 options, but it is generally a good idea to look up the overview to see which options are
2237 necessary.<br />
2239 Much like the ENUM/SET-Fields, you have to split up several options using the format
2240 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2241 parsed as an array, leaving the first value the first element in the array, and so
2242 forth.<br />
2244 If you want to specify a MIME character set you can define it in the transformation_options.
2245 You have to put that outside of the pre-defined options of the specific mime-transform,
2247 for which you can specify 2 options and you want to append a character set, enter "'first
2248 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2250 </ul>
2254 <p> All mimetypes and their transformations are defined through single files in
2255 the directory 'libraries/transformations/'.</p>
2257 <p> They are stored in files to ease up customization and easy adding of new
2258 transformations.</p>
2260 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2261 always work. It makes no sense to apply a transformation to a mimetype, the
2262 transform-function doesn't know to handle.</p>
2264 <p> One can, however, use empty mime-types and global transformations which should work
2265 for many mimetypes. You can also use transforms on a different mimetype they where built
2266 for, but pay attention to option usage as well as what the transformation does to your
2267 field.</p>
2269 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2270 any other transform function and provides some basic functions.</p>
2272 <p> There are 5 possible file names:</p>
2274 <ol><li>A mimetype+subtype transform:<br /><br />
2276 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2278 Please not that mimetype and subtype are separated via '_', which shall
2279 not be contained in their names. The transform function/filename may
2280 contain only characters which cause no problems in the file system as
2281 well as the PHP function naming convention.<br /><br />
2283 The transform function will the be called
2284 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2286 <b>Example:</b><br /><br />
2288 <tt>text_html__formatted.inc.php</tt><br />
2289 <tt>PMA_transform_text_html__formatted()</tt></li>
2291 <li>A mimetype (w/o subtype) transform:<br /><br />
2293 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2295 Please note that there are no single '_' characters.
2296 The transform function/filename may contain only characters which cause
2297 no problems in the file system as well as the PHP function naming
2298 convention.<br /><br />
2300 The transform function will the be called
2301 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2303 <b>Example:</b><br /><br />
2305 <tt>text__formatted.inc.php</tt><br />
2306 <tt>PMA_transform_text__formatted()</tt></li>
2308 <li>A mimetype+subtype without specific transform function<br /><br />
2310 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2312 Please note that there are no '__' characters in the filename. Do not
2313 use special characters in the filename causing problems with the file
2314 system.<br /><br />
2316 No transformation function is defined in the file itself.<br /><br />
2318 <b>Example:</b><br /><br />
2320 <tt>text_plain.inc.php</tt><br />
2321 (No function)</li>
2323 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2325 <tt>[mimetype].inc.php</tt><br /><br />
2327 Please note that there are no '_' characters in the filename. Do not use
2328 special characters in the filename causing problems with the file system.
2329 <br /><br />
2331 No transformation function is defined in the file itself.<br /><br />
2333 <b>Example:</b><br /><br />
2335 <tt>text.inc.php</tt><br />
2336 (No function)</li>
2338 <li>A global transform function with no specific mimetype<br /><br />
2340 <tt>global__[transform].inc.php</tt><br /><br />
2342 The transform function will the be called
2343 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2345 <b>Example:</b><br /><br />
2347 <tt>global__formatted</tt><br />
2348 <tt>PMA_transform_global__formatted()</tt></li>
2349 </ol>
2351 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2352 transform function.</p>
2354 <p> All filenames containing no '__' in themselves are not shown as valid transform
2355 functions in the dropdown.</p>
2357 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2358 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2359 without a transform function. Also note the introduction of a function description in
2360 the language files. For each function a $strTransformation_[filename without .inc.php]
2361 has to exist.</p>
2363 <p> You can use the template generator to generate new functions and entries in the
2364 language file.</p>
2366 <p> To create a new transform function please see
2367 <tt>libraries/transformations/template_generator.sh</tt>.
2368 To create a new, empty mimetype please see
2369 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2371 <p> A transform function always gets passed three variables:</p>
2373 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2374 you want to transform.</li>
2375 <li><b>$options</b> - Contains any user-passed options to a transform function
2376 as an array.</li>
2377 <li><b>$meta</b> - Contains an object with field information to your column.
2378 The data is drawn from the output of the
2380 function. This means, all object properties described on the
2382 available in this variable and can be used to transform a field accordingly
2383 to unsigned/zerofill/not_null/... properties.<br />
2384 The $meta->mimetype variable contains the original MIME-type of the
2385 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2386 </ol>
2388 <!-- FAQ -->
2395 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2399 </ol>
2401 <p> Please have a look at our
2403 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2404 features and or interface.</p>
2410 action is required or phpMyAdmin sends a blank page or a page full of
2411 cryptic characters to my browser, what can I do?</a></h4>
2413 <p> There are some known PHP bugs with output buffering and compression.<br />
2415 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2416 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2417 configuration file.<br />
2418 Furthermore, we know about such problems connected to the release
2419 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2420 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2425 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2426 See also the
2428 entry about PHP bugs with output buffering.<br />
2429 If your server keeps crashing, please ask for help in the various Apache
2430 support groups.</p>
2434 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2435 script: I'm always displayed the login screen.</a></h4>
2437 <p> This is a known PHP bug (see this
2439 official PHP bug database. It means there is and won't be any phpMyAdmin
2440 fix against it because there is no way to code a fix.</p>
2446 application misbehaved by not returning a complete set of
2448 </h4>
2450 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2451 Have a look at the last message in this
2453 official PHP bug database.</p>
2458 and/or many error messages with the
2460 mode.</a></h4>
2462 <p> This is a known problem with the PHP
2464 filter: it's not so stable. Please use instead the cookie authentication mode.
2465 </p>
2470 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2471 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2472 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2473 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2474 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2479 work.</a></h4>
2481 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2482 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2483 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2484 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2485 We faced PHP crashes when trying to download a dump with MS Internet
2486 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2487 this case you should switch to the release version of PHP 4.2.0.</p>
2491 an error about safe mode being in effect.</a></h4>
2493 <p> Your uploaded file is saved by PHP in the "upload dir", as
2494 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2495 the system default is <i>/tmp</i>).<br />
2496 We recommend the following setup for Apache servers running in safe mode,
2497 to enable uploads of files while being reasonably secure:</p>
2499 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2500 <li>give ownership to the Apache server's user.group:
2501 <tt>chown apache.apache /tmp/php</tt></li>
2502 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2503 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2504 <li>restart Apache</li>
2505 </ul>
2509 general file uploads don't work on my system and uploaded files have a
2510 <tt>Content-Type:</tt> header in the first line.</a></h4>
2512 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2513 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2514 So the problem is that this package has a serious bug that was corrected
2515 ages ago in PHP (2001-01-28: see
2517 for more details). The problem is that the bugged package is still
2518 available though it was corrected (see
2520 for more details).<br />
2521 So please download
2522 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2523 and the problem should go away.<br />
2524 And that fixes the \r\n problem with file uploads!</p>
2528 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2529 I'm using the Apache server.</a></h4>
2531 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2532 your <i>httpd.conf</i>:</p>
2536 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2540 uploading a file from the query box.</a></h4>
2542 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2543 restrictions. However you need to create temporary directory and
2545 The uploaded files will be moved there, and after execution of your
2551 <p> The MySQL manual explains how to
2553 reset the permissions</a>.</p>
2558 execute a bookmark.</a></h4>
2560 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2561 cannot access the uploaded query.</p>
2566 submit a query from the convenient text area.</a></h4>
2568 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2569 and try to increase it.</p>
2573 </h4>
2575 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2576 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2577 names to align with current standards.</p>
2582 </h4>
2584 <p> Starting with version 2.7.0, the import engine has been re–written and these
2585 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2586 to take advantage of the new import features.</p>
2588 <p> The first things to check (or ask your host provider to check) are the
2589 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2590 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2591 All of these three settings limit the maximum size of data that can be
2592 submitted and handled by PHP. One user also said that post_max_size
2593 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2595 There exist several workarounds if your upload is too big or your
2596 hosting provider is unwilling to change the settings:</p>
2599 feature. This allows one to
2600 upload a file to the server via scp, ftp, or your favorite file transfer
2601 method. PhpMyAdmin is then able to import the files from the temporary
2603 section</a> of this document.</li>
2605 BigDump</a>) to split the files before uploading. We cannot support this
2606 or any third party applications, but are aware of users having success
2607 with it.</li>
2608 <li>If you have shell (command line) access, use MySQL to import the files
2609 directly. You can do this by issuing the "source" command from
2610 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2611 </ul>
2615 support?</a></h4>
2617 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2618 fully supported. phpMyAdmin may connect to your MySQL server
2619 using PHP's classic
2622 is available in php 5.0.<br />
2623 Either way, the developers of both extensions recommend to use the classic
2624 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2625 When compiling php, we strongly recommend that you manually link the MySQL
2626 extension of your choice to a MySQL client library of at least the same
2627 minor version since the one that is bundled with some PHP distributions is
2630 If your webserver is running on a windows system, you might want to try
2631 MySQL's
2633 instead of the MySQL / MySQLi extensions that are bundled with the official
2634 php Win32 builds.</p>
2638 message, "Client does not support authentication protocol requested
2639 by server; consider upgrading MySQL client"</a></h5>
2641 <p> You tried to access MySQL with an old MySQL client library. The version of
2642 your MySQL client library can be checked in your phpinfo() output.
2643 In general, it should have at least the same minor version as your server
2647 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2648 changed the authentication hash and your PHP is trying to use the old method.
2650 with the proper client library to match your MySQL installation. Your
2651 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2652 More information (and several workarounds) are located in the
2654 </p>
2658 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2659 capital letter in its name it is changed to lowercase as it should. But
2660 if I try to DROP this table MySQL is unable to find the corresponding
2661 file.</a></h4>
2663 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2664 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2665 directive.</p>
2669 script seems not to know the font face I'm using!</a></h4>
2671 <p> The "FPDF" library we're using for this feature requires some
2672 special files to use font faces.<br />
2674 these files.</p>
2678 check PHP Configuration".</a></h4>
2680 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2681 "MySQL extension". This extension may be part of the PHP
2682 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2683 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2684 to load the extension but failed.<br /><br />
2686 Usually, the problem is solved by installing a software package called
2687 "PHP-MySQL" or something similar.</p>
2692 and I cannot log in using cookie auth.</a></h4>
2694 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2698 so I cannot upload.</a></h4>
2700 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2701 parameter is not set to "on".</p>
2705 a new table the table and field names are changed to lowercase!</a></h4>
2707 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2708 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2709 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2710 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2711 directory and add the following line to the group [mysqld]:</p>
2713 <pre>set-variable = lower_case_table_names=0</pre>
2715 <p> Next, save the file and restart the MySQL service. You can always check the
2716 value of this directive using the query</p>
2718 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2722 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2725 </p>
2729 and I get problems, such as undefined variables when I run a
2732 <p> A tip from Jose Fandos: put a comment on the following two lines
2733 in httpd.conf, like this:</p>
2735 <pre>
2736 # mod_gzip_item_include file \.php$
2738 </pre>
2740 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2741 PHP scripts. Of course you have to restart Apache.</p>
2746 I get the error "No input file specified" when trying to
2747 run phpMyAdmin.</a></h4>
2749 <p> This is a permission problem. Right-click on the phpmyadmin folder
2750 and choose properties. Under the tab Security, click on "Add"
2751 and select the user "IUSR_machine" from the list. Now set his
2752 permissions and it should work.</p>
2756 db_structure.php with plenty of tables).</a></h4>
2759 GZIP output buffering is enabled. If you turn off it (by
2761 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2762 PHP 5.0.0.</p>
2766 message 'Errorcode: 13'. What does this mean?</a></h4>
2768 <p> This can happen due to a MySQL bug when having database / table names with
2769 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2770 To fix this, turn off this directive, convert all database and table names
2771 to lower case and turn it on again. Alternatively, there's a bug-fix
2772 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2776 and the fields are duplicated.</a></h4>
2778 <p> It is possible to configure Apache in such a way that PHP has problems
2779 interpreting .php files.</p>
2781 <p> The problems occur when two different (and conflicting) set of directives
2782 are used:</p>
2784 <pre>
2785 SetOutputFilter PHP
2786 SetInputFilter PHP
2787 </pre>
2789 <p> and</p>
2791 <pre>AddType application/x-httpd-php .php</pre>
2793 <p> In the case we saw, one set of directives was in
2794 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2795 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2796 The recommended way is with <tt>AddType</tt>, so just comment out
2797 the first set of lines and restart Apache:</p>
2799 <pre>
2800 #SetOutputFilter PHP
2801 #SetInputFilter PHP
2802 </pre>
2807 <p> This problem is known to happen when the server is running Turck MMCache
2808 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2813 <p> Yes.<br />
2814 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2815 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2816 <tt>error_reporting</tt> settings.
2817 </p>
2820 <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>
2822 <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>
2825 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2826 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2827 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2828 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2829 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2830 enabled.) Click <tt>OK</tt>.</li>
2831 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2832 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2833 </ol>
2837 PHP 5.0.4 on 64-bit systems?</a></h4>
2839 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2840 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2846 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
2847 the order of the server paragraph in <tt>config.inc.php</tt>.
2848 Table and script parts are optional. If you want
2849 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2850 some configuration. Following lines apply only for <a
2852 that you have enabled some features within global configuration. You need
2853 <code>Options FollowSymLinks</code> and <code>AllowOverride
2854 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2855 you need mod_rewrite to be enabled. Then you just need to create following
2856 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2857 (don't forget to change directory name inside of it):</p>
2859 <pre>
2860 RewriteEngine On
2861 RewriteBase /path_to_phpMyAdmin
2862 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2863 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2864 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2865 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2866 </pre>
2869 <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>
2871 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2872 following rewrite rule:</p>
2874 <pre>
2875 RewriteEngine On
2876 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2877 </pre>
2881 </h4>
2882 <p>
2883 There can be many explanations to this and a look at your server's
2884 error log file might give a clue.
2885 </p>
2889 password encryption in cookie auth doesn't work.</a></h4>
2891 <p> If your cluster consist of different architectures, PHP code used for
2892 encryption/decryption won't work correct. This is caused by use of
2893 pack/unpack functions in code. Only solution is to use mcrypt extension
2894 which works fine in this case.</p>
2899 <p> Yes but the default configuration values of Suhosin are known to cause
2900 problems with some operations, for example editing a table with many
2901 columns and no primary key. Tuning information is available at
2903 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2904 although the parameter names have changed (<tt>suhosin</tt> instead
2906 <tt>SuhosinDisableWarning</tt> directive</a>.
2907 </p>
2913 headers already sent by ..." is displayed, what's the problem?</a></h4>
2915 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2916 (I.E. no blank lines, no spaces, no characters...) neither before the
2917 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2918 tag at the end. We also got a report from a user under IIS, that used
2919 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2920 contained an end-of-line character (hex 0A) at the end; removing this character
2921 cleared his errors.</p>
2926 <p> Either there is an error with your PHP setup or your username/password is
2927 wrong. Try to make a small script which uses mysql_connect and see if it
2928 works. If it doesn't, it may be you haven't even compiled MySQL support
2929 into PHP.</p>
2933 connect to local MySQL server through socket '/tmp/mysql.sock'
2934 (111) ..." is displayed. What can I do?</a></h4>
2936 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2938 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2939 In your <i>php.ini</i> you will find a line</p>
2941 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2943 <p> change it to</p>
2945 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2947 <p> Then restart apache and it will work.</p>
2949 <p> Here is a fix suggested by Brad Ummer:</p>
2951 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2952 To do this, telnet to your server and go to the MySQL bin directory. In
2953 this directory there should be a file named <i>mysqladmin</i>. Type
2954 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2955 info about your MySQL server, including the socket
2956 (<i>/tmp/mysql.sock</i>, for example).</li>
2957 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2958 phpMyAdmin, you need to complete the socket information in the
2959 <i>config.inc.php</i>.<br />
2960 For example:
2962 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2963 <br /><br />
2965 Please also make sure that the permissions of this file allow to be readable
2966 by your webserver (i.e. '0755').</li>
2967 </ul>
2969 <p> Have also a look at the
2971 corresponding section of the MySQL documentation</a>.</p>
2975 what can I do?</a></h4>
2978 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2979 sometime.<br />
2980 Also have a look at your PHP version number: if it contains "4.0b..."
2981 it means you're running a beta version of PHP. That's not a so good idea,
2982 please upgrade to a plain revision.</p>
2986 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2987 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2989 <p> Check the value you set for the
2991 directive in the phpMyAdmin configuration file.</p>
2995 password: YES)"-error when trying to access a MySQL-Server on a
2996 host which is port-forwarded for my localhost.</a></h4>
2998 <p> When you are using a port on your localhost, which you redirect via
2999 port-forwarding to another host, MySQL is not resolving the localhost
3000 as expected.<br />
3001 Erik Wasser explains: The solution is: if your host is "localhost"
3002 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3003 connection for speeding up things. And that doesn't work in this configuration
3004 with port forwarding.<br />
3010 <p> Themes are configured with
3014 <br />
3016 should not delete the directory "original" or its underlying
3017 structure, because this is the system theme used by phpMyAdmin.
3018 "original" contains all images and styles, for backwards
3019 compatibility and for all themes that would not include images or css-files.
3020 <br /><br />
3023 is enabled, you can select your favorite theme on the main page. Your
3024 selected theme will be stored in a cookie.<br /><br /></p>
3026 <p> To create a theme:</p>
3028 <ul><li>make a new subdirectory (for example "your_theme_name") under
3030 (by default <tt>themes</tt>)</li>
3031 <li>copy the files and directories from "original" to
3032 "your_theme_name"</li>
3033 <li>edit the css-files in "your_theme_name/css"</li>
3034 <li>put your new images in "your_theme_name/img"</li>
3035 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3036 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3037 contain your chosen theme name, that will be visible in user interface</li>
3038 <li>make a new screenshot of your theme and save it under
3039 "your_theme_name/screen.png"</li>
3040 </ul>
3042 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3043 theme verbose name, theme generation and theme version. These versions and
3044 generations are enumerated from 1 and do not have any direct dependence on
3045 phpMyAdmin version. Themes within same generation should be backwards
3046 compatible - theme with version 2 should work in phpMyAdmin requiring
3047 version 1. Themes with different generation are incompatible.</p>
3049 <p> If you do not want to use your own symbols and buttons, remove the
3050 directory "img" in "your_theme_name". phpMyAdmin will
3051 use the default icons and buttons (from the system-theme "original").
3052 </p>
3056 what can I do?</a></h4>
3058 <p> Here are a few points to check:</p>
3060 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3062 directive empty. See also
3064 </li>
3065 <li>Maybe you have a broken PHP installation or you need to upgrade
3066 your Zend Optimizer. See
3068 http://bugs.php.net/bug.php?id=31134</a>.
3069 </li>
3070 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3071 set to the default (200) or another low value, you could get this
3072 error if your table has a high number of columns. Adjust this setting
3073 accordingly. (Thanks to Klaus Dorninger for the hint).
3074 </li>
3075 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3076 of ";" will cause this error. Replace it with "&;".
3077 </li>
3079 you might want to increase
3081 </li>
3082 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3083 </li>
3084 </ul>
3091 who logged out can not log in again in with the same nick.</a></h4>
3093 <p> This is related to the authentication mechanism (protocol) used by
3094 phpMyAdmin. To bypass this problem: just close all the opened
3095 browser windows and then go back to phpMyAdmin. You should be able to
3096 log in again.</p>
3100 limit error or a time limit error.</a></h4>
3102 <p> Compressed dumps are built in memory and because of this are limited to
3103 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3104 using
3106 (enabled by default). Zip exports can not be handled this way, so if you need
3107 Zip files for larger dump, you have to use another way.</p>
3111 or alter a table.</a></h4>
3113 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3117 bundled with the MySQL server distribution.</a></h4>
3119 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3121 <pre>
3122 -- MySQL dump 8.22
3123 --
3124 -- Host: localhost Database: database
3125 ---------------------------------------------------------
3126 -- Server version 3.23.54
3127 </pre>
3129 <p> The invalid part of the code is the horizontal line made of dashes that
3130 appears once in every dump created with mysqldump. If you want to run your
3131 dump you have to turn it into valid MySQL. This means, you have to add a
3132 whitespace after the first two dashes of the line or add a # before it:
3133 <br />
3134 <code>
3135 -- -------------------------------------------------------<br />
3136 </code>
3137 or<br />
3138 <code>
3139 #---------------------------------------------------------
3140 </code>
3141 </p>
3148 <p> Please note that you should not use the separating string multiple times
3149 without any characters between them, or at the beginning/end of your table
3150 name. If you have to, think about using another TableSeparator or disabling
3151 that feature</p>
3156 <p> In Relation view, being able to choose a table in another database,
3157 or having more than one index field in the foreign key.<br /><br/>
3158 In Query-by-example (Query), automatic generation of the query
3159 LEFT JOIN from the foreign table.<br /><br/>
3160 </p>
3164 I get series of errors like "Warning: unable to parse url". How
3165 can this be fixed?</a></h4>
3166 <p>
3167 Your table neither have a primary key nor an unique one, so we must use a
3168 long expression to identify this row. This causes problems to parse_url
3169 function. The workaround is to create a primary or unique key.
3170 <br />
3171 </p>
3175 a MIME-Transformation onto!</a></h4>
3177 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3178 nested forms can be put inside the table where phpMyAdmin displays the results.
3179 You can, however, use any form inside of a table if keep the parent
3180 form-container with the target to tbl_row_delete.php and just put your own
3181 input-elements inside. If you use a custom submit input field, the form will
3182 submit itself to the displaying page again, where you can validate the
3183 $HTTP_POST_VARS in a transformation.
3185 For a tutorial on how to effectively use transformations, see our
3187 on the official phpMyAdmin-homepage.</p>
3191 MySQL server</a></h4>
3193 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3196 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3197 the quote-character (") is interpreted as an identifier quote character and
3198 not as a string quote character, which makes many internal phpMyAdmin
3200 statements. There is no workaround to this behaviour. News to this item will
3201 be posted in Bug report
3202 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3203 </p>
3207 more that one column with the same value
3208 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3209 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3211 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3212 can use it for the Edit and Delete links.</p>
3217 <p> phpMyAdmin uses a quick method to get the row count, and this method
3218 only returns an approximate count in the case of InnoDB tables. See
3220 a way to modify those results, but
3221 this could have a serious impact on performance.</p>
3226 <p> The number of records in queries containing COUNT and GROUP BY is
3227 not correctly calculated. Also, sorting results of a query like
3232 containing an hyphen.
3233 </a></h4>
3234 <p>
3235 The tests I have made with current MySQL 4.1.11 API shows that the
3236 API does not accept this syntax for the USE command. Enclosing the
3237 db name with backquotes works. For further confusion, no backquotes
3238 are needed with command-line mysql.
3239 </p>
3242 <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>
3243 <p>
3244 This has been a known limitation of phpMyAdmin since the beginning and
3245 it's not likely to be solved in the future.
3246 </p>
3248 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3251 <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
3252 need to install it for each customer.
3253 </a></h4>
3254 <p>
3255 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3256 your users. The development of this feature was kindly sponsored by
3257 NetCologne GmbH.
3258 This requires a properly setup MySQL user management and phpMyAdmin
3259 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3261 </p>
3265 access.
3266 </a></h4>
3267 <p>
3268 This depends on your system.<br />
3269 If you're running a server which cannot be accessed by other people, it's
3270 sufficient to use the directory protection bundled with your webserver
3272 If other people have telnet access to your server, you should use
3273 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3274 <br /><br />
3275 Suggestions:
3276 </p>
3277 <ul>
3278 <li>
3280 </li>
3281 <li>
3282 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3283 is a user whose password is only known to you, and apache is the
3284 group under which Apache runs.
3285 </li>
3286 <li>
3287 You should use PHP safe mode, to protect from other users that try
3289 </li>
3290 </ul>
3295 </a></h4>
3296 <p>
3301 </p>
3304 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3305 authentication.
3306 </a></h4>
3310 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3311 and/or
3313 are wrong.</li>
3315 <li>You have already setup a security mechanism for the
3316 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3317 phpMyAdmin's authentication, so remove it.</li>
3318 </ul>
3325 and put the privileges you want. For example,
3327 would let a user create/manage his/her database(s).</p>
3332 <p> If you have existing rules from an old .htaccess file, you can take them
3335 be a major benefit here if your installation is suited to using it. Then
3336 you can just add those updated lines into the
3340 <p> If you want a pre-made sample, you can try this fragment. It stops the
3341 'root' user from logging in from any networks other than the private
3344 <pre>
3345 //block root from logging in except from the private networks
3346 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3347 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3348 'deny root from all',
3349 'allow root from localhost',
3353 );
3354 </pre>
3359 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3360 different than the one set in your
3362 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3363 while a domain name is defined in the config file.</p>
3368 <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>
3374 when trying to create a table with more than 14 fields.
3375 </a></h4>
3376 <p>
3377 We could reproduce this problem only under Win98/98SE. Testing under
3378 WinNT4 or Win2K, we could easily create more than 60 fields.
3379 <br />
3380 A workaround is to create a smaller number of fields, then come back to
3381 your table properties and add the other fields.
3382 </p>
3386 <p>
3387 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3388 with each script/website that use forms.<br />
3389 Upgrade or downgrade your Xitami server.
3390 </p>
3393 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3394 <p>
3395 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3396 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3397 don't seem to work.<br />
3399 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3400 the user's temporary directory, so they must be moved before closing
3401 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3404 </p>
3408 Explorer never stores the cookies.
3409 </a></h4>
3410 <p>
3411 MS Internet Explorer seems to be really buggy about cookies, at least till
3413 in this area!
3414 <br />
3415 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3416 work!
3417 </p>
3421 rows.
3422 </a></h4>
3423 <p>
3425 </p>
3428 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3429 when trying to modify a row in a table with many fields, or with a text field
3430 </a></h4>
3431 <p>
3432 Your table neither have a primary key nor an unique one, so we must use a
3433 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
3434 those browsers, and this not happen in Netscape, for example. The
3435 workaround is to create a primary or unique key, or use another browser.
3436 <br />
3437 </p>
3441 page.
3442 </a></h4>
3443 <p>
3444 Some browsers support right-clicking into the frame you want to refresh,
3445 just do this in the right frame.<br />
3446 </p>
3450 query box.
3451 </a></h4>
3452 <p>
3453 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3454 Mozilla versions.<br />
3455 </p>
3459 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3460 </a></h4>
3461 <p>
3462 This is a Mozilla bug (see bug #26882 at
3464 </p>
3469 </a></h4>
3470 <p>
3471 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3472 data in octet-stream mode. Since we can't detect the specific Netscape
3473 version, we cannot workaround this bug.
3474 </p>
3478 wrong.</a></h4>
3480 <p> Please ensure that you have set your browser's character set to the one of the
3481 language file you have selected on phpMyAdmin's start page.
3482 Alternatively, you can try the auto detection mode that is supported by the
3483 recent versions of the most browsers.</p>
3486 <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
3489 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3490 Netscape and Mozilla do not have this problem.</p>
3493 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3494 I cannot manage two servers: I log in to the first one, then the other one,
3495 but if I switch back to the first, I have to log in on each operation.</a></h4>
3501 but nothing happens after that, only a blank screen.</a></h4>
3512 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3517 address and you are starting
3519 containing a domain name, or the reverse situation.</li>
3520 <li>Security settings in IE and/or Microsoft Security Center are
3521 too high, thus blocking scripts execution.</li>
3522 <li>The Windows Firewall is blocking Apache and MySQL. You must
3526 </ul>
3529 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3530 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3531 installed in their Firefox is causing the problem.</p>
3538 </a></h4>
3539 <p>
3540 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3541 specifying a wrong field-type.<br />
3542 Common errors include:
3543 </p>
3544 <ul>
3547 </ul>
3548 <p>
3549 Also, look at the syntax chapter in the MySQL manual to confirm that your
3550 syntax is correct.
3551 </p>
3555 phpMyAdmin generates only one index with those two fields.
3556 </a></h4>
3557 <p>
3558 This is the way to create a multi-fields
3559 index. If you want two indexes, create the first one when creating the
3560 table, save, then display the table properties and click the Index link to
3561 create the other index.
3562 </p>
3566 <p>
3567 Since version 2.2.3, you have a checkbox for each field that can be null.
3569 field's value. Since version 2.5.5, you have to use the checkbox to get
3571 a literal NULL in the field, and not a NULL value (this works in PHP4).
3572 </p>
3577 <p> Click on a database or table name in the left frame, the properties will be
3579 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3580 statements that can be used to recreate your database/table.
3581 <br /><br />
3583 transmit the resulting dump to your station. Depending on your PHP
3584 configuration, you will see options to compress the dump. See also the
3586 configuration variable.<br /><br />
3589 this document.</p>
3594 </a></h4>
3596 <p> Click on a database name in the left frame, the properties will be
3598 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3600 the path to your dump filename, or use the Browse button. Then click Go.
3601 <br /><br />
3603 that you upgrade to take advantage of the new features.
3604 <br /><br />
3606 in this document.
3607 </p>
3612 <p> Here is an example with the tables persons, towns and countries, all
3614 table, create it as explained in the configuration section. Then create the
3615 example tables:</p>
3617 <pre>
3618 CREATE TABLE REL_countries (
3619 country_code char(1) NOT NULL default '',
3620 description varchar(10) NOT NULL default '',
3621 PRIMARY KEY (country_code)
3622 ) TYPE=MyISAM;
3624 INSERT INTO REL_countries VALUES ('C', 'Canada');
3626 CREATE TABLE REL_persons (
3627 id tinyint(4) NOT NULL auto_increment,
3628 person_name varchar(32) NOT NULL default '',
3630 country_code char(1) NOT NULL default '',
3631 PRIMARY KEY (id)
3632 ) TYPE=MyISAM;
3634 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3635 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3637 CREATE TABLE REL_towns (
3639 description varchar(30) NOT NULL default '',
3640 PRIMARY KEY (town_code)
3641 ) TYPE=MyISAM;
3643 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3644 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3645 </pre>
3651 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3655 </ul>
3663 <li>In the fields row, choose persons.person_name and click the
3665 <li>Do the same for towns.description and countries.descriptions in the
3668 the correct joins have been generated</li>
3670 </ul>
3674 <p>
3675 Starting from the previous example, create the pma_table_info as explained
3676 in the configuration section, then browse your persons table,
3677 and move the mouse over a town code or country code.
3678 <br /><br />
3679 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3680 enables: drop-down list of possible values.
3681 </p>
3684 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3685 <p>
3688 <br /><br />
3689 Then you need to think about your schema layout. Which tables will go on
3690 which pages?
3691 </p>
3692 <ul>
3698 page and click Go. If you like, you
3700 linked tables onto the new page.</li>
3701 <li>Select the name of the new page (making sure the Edit radio button
3702 is selected) and click Go.</li>
3704 Coordinates are relative; your diagram will
3705 be automatically scaled to fit the page. When initially placing tables
3706 on the page, just pick any coordinates -- say, 50x50. After clicking
3708 position the element correctly.</li>
3710 first be sure to click the Save
3711 button beneath the list of tables and coordinates, to save any changes
3712 you made there. Then scroll all the way down, select the
3714 you want, and click Go.</li>
3715 <li>Internet Explorer for Windows may suggest an incorrect filename when
3720 browsers on Windows, do not have this problem.</li>
3721 </ul>
3725 columns!</a></h4>
3727 <p> No, it's MySQL that is doing
3733 underscores in the database name?</a></h4>
3735 <p> If you do not put a backslash before the underscore, this is a wildcard
3738 john2db ...<br /><br />
3740 If you put a backslash before the underscore, it means that the database
3741 name will have a real underscore.</p>
3745 statistics pages?</a></h4>
3756 if it already exists during the import. It does NOT drop the table after
3757 your export, it only affects the import file.</li>
3759 Otherwise, you may get an error if the table name exists but has a
3760 different structure.</li>
3762 (if any) will be included in backup.</li>
3764 field and table names formed with special characters are protected.</li>
3766 types set in the pmadb in the dump as
3768 </li>
3769 </ul>
3774 command, for better documentation (but resulting file is bigger).</li>
3776 once the INSERT verb and the table name.</li>
3779 </li>
3781 more info is provided in the
3783 but basically with this selected, invalid values are adjusted and
3784 inserted rather than causing the entire statement to fail.</li>
3785 </ul>
3789 in its name.</a></h4>
3792 is the normal way to reference a database and table name. Worse, MySQL
3793 will usually let you create a database with a dot, but then you cannot
3794 work with it, nor delete it.</p>
3807 for usage.<br />
3808 On a more recent pear version, I had problems with the state of Net_DIME
3809 being beta, so this single command
3811 needed modules.<br />
3812 If you use the Validator, you should be aware that any
3814 submit will be stored anonymously (database/table/column names,
3815 strings, numbers replaced with generic values). The Mimer
3818 We utilize it as free SOAP service.</p>
3822 it, but MySQL says "BLOB column '...' used in key specification without
3825 <p> The right way to do this, is to create the field without any indexes,
3827 dialog. On this page, you will be able to choose your BLOB field, and
3828 set a size to the index, which is the condition to create an index on
3829 a BLOB field.</p>
3833 editing fields?</a></h4>
3835 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3836 with many editing fields (table structure changes, row editing, etc.)
3837 (must be enabled in configuration - see.
3839 You can also have a look at the directive
3841 ('vertical') and see if this eases up editing for you.</p>
3845 WTF is this feature then useful for?</a></h4>
3847 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3848 on them. Otherwise you could just put a comment on the field. Because entering
3849 your own mimetype will cause serious syntax checking issues and validation,
3850 this introduces a high-risk false-user-input situation. Instead you have to
3851 initialize mimetypes using functions or empty mimetype definitions.<br />
3852 Plus, you have a whole overview of available mimetypes. Who knows all those
3853 mimetypes by heart so he/she can enter it at will?</p>
3857 can't I see any bookmarks below the query box? What is this variable for?
3858 </a></h4>
3860 <p> Any query you have executed can be stored as a bookmark on the page where the
3861 results are displayed. You will find a button labeled 'Bookmark this query'
3862 just at the end of the page.<br />
3863 As soon as you have stored a bookmark, it is related to the database you run
3864 the query on. You can now access a bookmark dropdown on each page, the query
3865 box appears on for that database.<br /><br />
3867 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3871 aware of that you HAVE to create a valid query, otherwise your query won't be
3872 even able to be stored in the database.<br />
3874 for your query will remain the way it is, but will be stripped of the /**/
3875 chars. So you can use:<br /><br />
3879 which will be expanded to<br /><br />
3883 in your query, where VARIABLE is the string you entered in the input box. If
3884 an empty string is provided, no replacements are made.<br /><br />
3886 A more complex example. Say you have stored this query:<br /><br />
3888 <br /><br />
3891 the full query will be:<br /><br />
3894 <br /><br />
3898 spaces inserted there
3899 will be later also inserted as spaces in your query and may lead to unexpected
3900 results especially when
3902 Your initial query which is going to be stored as a bookmark has to yield at
3903 least one result row so
3904 you can store the bookmark. You may have that to work around using well
3908 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3909 include exported table?</a></h4>
3911 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3912 document should look like following one (assuming you have table
3915 <pre>
3916 \documentclass{article} % or any class you want
3917 \usepackage{longtable} % for displaying table
3918 \begin{document} % start of document
3919 \include{table} % including exported table
3920 \end{document} % end of document
3921 </pre>
3925 access them.
3926 </a></h4>
3929 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3930 enable users to see all the database names.
3933 So if your users do not need those privileges, you can remove them and their
3934 databases list will shorten.</p>
3938 possible values for a field, based on some foreign table?</a></h4>
3940 <p> You have to setup appropriate links between the tables, and also
3944 foreign table, a drop-down list of values will be available.
3945 You will see two lists of values, the first list containing the key
3946 and the display field, the second list containing the display field
3947 and the key. The reason for this is to be able to type the first
3948 letter of either the key or the display field.<br /><br />
3950 For 100 values or more, a distinct window will appear, to browse foreign
3951 key values and choose one. To change the default limit of 100, see
3952 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
3956 automatically when entering Browse mode for a table?</a></h4>
3958 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3959 </p>
3963 Excel files, how can I enable that?</a></h4>
3965 <p> Current version does support direct export to Microsoft Excel and Word
3966 versions 2000 and newer. If you need export older versions, you can use
3968 which works out of the box or you can
3970 several problems, most important are limitation of cell content to 255
3971 chars and no support for charsets, so think carefully whether you want to
3972 enable this.</b>. For enabling this you need to set
3976 module Spreadsheet_Excel_Writer into php include path. The
3977 installation can be done by following command:</p>
3979 <pre>
3980 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3981 </pre>
3983 <p> First part of switches set we want to install beta version of that module
3984 (no stable version available yet) and then we tell pear we want to satisfy
3985 dependencies.</p>
3987 <p> If you are running in PHP safe mode, you will have to set
3990 modules are located, for example:</p>
3992 <pre>
3993 safe_mode_include_dir = /usr/local/lib/php
3994 </pre>
3998 <pre>
3999 cd phpMyAdmin
4000 mkdir tmp
4001 chmod o+rwx tmp
4002 </pre>
4006 what happens to my column comments stored in pmadb?</a></h4>
4008 <p> Automatic migration of a table's pmadb-style column comments to the native
4009 ones is done whenever you enter Structure page for this table.</p>
4014 <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 />
4015 <ol>
4016 <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>
4017 <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>
4018 <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>
4020 <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>
4021 <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>
4022 </ol>
4023 </p>
4030 <p> Our Bug Tracker is located at
4032 under the Bugs section.<br /><br />
4034 But please first discuss your bug with other users:<br />
4040 existing language, where do I start?</a></h4>
4042 <p> Always use the current SVN version of your language file.
4044 don't know how to get the SVN version, please ask one of the developers.
4045 <br />
4046 Please note that we try not to use HTML entities like &eacute; in
4047 the translations, since we define the right character set in the file.
4048 With HTML entities, the text on JavaScript messages would not
4049 display correctly.
4050 However there are some entities that need to be there, for quotes
4051 ,non-breakable spaces, ampersands, less than, greater than.<br />
4052 You can then put your translations, as a zip file to avoid losing special
4053 characters, on the sourceforge.net translation tracker.<br />
4054 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4055 list, because this is where we ask for translations of new messages.</p>
4059 phpMyAdmin. How should I proceed?</a></h4>
4064 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4065 </li>
4067 <li>generate patch with your changes:
4069 </li>
4072 tracker of the phpMyAdmin project</a>.
4073 </li>
4074 </ol>
4076 <p> Write access to the SVN tree is granted only to experienced developers who
4077 have already contributed something useful to phpMyAdmin.<br />
4083 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4085 <p> Please refer to
4086 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4087 </p>
4089 <!-- DEVELOPERS -->
4092 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4093 great features have been written by other people and you too can help to
4094 make phpMyAdmin a useful tool.</p>
4096 <p> If you're planning to contribute source, please read the following
4097 information:</p>
4103 it free from other code.<br />
4104 Commonly used functions should be added to
4107 <li>Obviously, you're free to use whatever coding style you want. But
4108 please try to keep your code as simple as possible: beginners are
4109 using phpMyAdmin as an example application.<br />
4110 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4111 compliant on one hand, they fit the
4114 coding standards</a>
4115 on the other hand. Please pay attention to this.</li>
4116 <li>Please try to keep up the file-naming conventions. Table-related stuff
4119 <li>Please don't put message strings in your code, instead add the string
4124 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4125 better debug and profile their code.<br />
4126 Please see the
4128 options for more information.<br />
4129 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4130 lost during its re-entry into Earth's atmosphere and in memory of the
4131 brave men and women who gave their lives for the people of Earth.</li>
4132 </ul>
4134 <!-- CREDITS -->
4137 <pre>
4138 phpMyAdmin - Credits
4139 ====================
4141 CREDITS, in chronological order
4142 -------------------------------
4145 * creator of the phpmyadmin project
4149 * multi-language version
4150 * various fixes and improvements
4152 * current project maintainer
4155 * started SourceForge phpMyAdmin project in March 2001
4156 * sync'ed different existing CVS trees with new features and bugfixes
4157 * multi-language improvements, dynamic language selection
4158 * current project maintainer
4159 * many bugfixes and improvements
4162 * rewrote and optimized javascript, DHTML and DOM stuff
4163 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4164 generate XHTML1.0 and CSS2 compliant codes
4165 * improved the language detection system
4166 * many bugfixes and improvements
4169 * database maintenance controls
4170 * table type code
4172 * DB-based configuration (Not completed)
4175 * many bugfixes and improvements
4178 * bookmarks feature
4179 * multiple dump feature
4180 * gzip dump feature
4181 * zip dump feature
4184 * various fixes
4185 * moderator of the phpMyAdmin former users forum at phpwizard.net
4191 * rewrote and fix dump code
4192 * bugfixes
4195 * rewrote dump code for PHP4
4196 * mySQL table statistics
4197 * bugfixes
4200 * main author of the version 2.1.0.1
4201 * bugfixes
4205 * abstract database interface (PMA_DBI) with MySQLi support
4206 * privileges administration
4208 * various features and fixes
4209 * German language file updates
4212 * automatic joins in QBE
4213 * links column in printview
4214 * Relation view
4217 * enhanced index creation/display feature
4218 * feature to use a different charset for HTML than for MySQL
4219 * improvements of export feature
4220 * various features and fixes
4221 * Czech language file updates
4224 (http://sf.net/projects/phpmysqlformgen/)
4225 * suggested the patch for multiple table printviews
4228 * built the patch for vertical display of table rows
4229 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4230 * Improvement of column/db comments
4231 * (MIME)-Transformations for columns
4232 * Use custom alias names for Databases in left frame
4233 * hierarchical/nested table display
4234 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4235 * new icon sets
4236 * vertical display of column properties page
4237 * some bugfixes, features, support, German language additions
4240 * japanese kanji encoding conversion feature
4243 * the Cookie authentication mode
4246 * table relation-links feature
4249 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4250 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4251 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4257 * phpMyAdmin logo (until June 2004)
4260 * blowfish library from the Horde project
4263 * mysqli support
4264 * many bugfixes and improvements
4267 * redesign for 2.6.0
4268 * phpMyAdmin sailboat logo (June 2004)
4271 * Representation at conferences
4274 * interface improvements
4275 * various bugfixes
4277 - Ivan A Kirillov
4278 * new relations Designer
4280 - Raj Kissu Rajandran (Google Summer of Code 2008)
4281 * BLOBstreaming support
4283 - Piotr Przybylski (Google Summer of Code 2008)
4284 * improved setup script
4286 And also to the following people who have contributed minor changes,
4287 enhancements, bugfixes or support for a new language since version 2.1.0:
4289 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4290 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4291 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4292 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4294 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4295 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4296 Luís V., Martijn W. van der Lee,
4297 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4301 Original Credits of Version 2.1.0
4302 ---------------------------------
4304 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4305 to create a web-based interface to MySQL using PHP3. Although I have not
4306 used any of his source-code, there are some concepts I've borrowed from
4307 him. phpMyAdmin was created because Peter told me he wasn't going to
4308 further develop his (great) tool.
4309 Thanks go to
4311 code for the check when dropping a table or database. He also suggested
4312 that you should be able to specify the primary key on tbl_create.php3. To
4313 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4314 well as a bug-report. Plus many smaller improvements.
4316 were introduced in 1.3.0 (including quite significant ones like the
4317 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4318 bug-fixes and help.
4320 language-independent by outsourcing the strings to a separate file. He
4321 also contributed the French translation.
4323 tbl_select.php3, a feature to display only some fields from a table.
4325 functions in tbl_change.php3. He also added the
4328 servers and is a regular contributor for bug-fixes.
4330 features for 2.0.6.
4331 The following people have contributed minor changes, enhancements, bugfixes
4332 or support for a new language:
4333 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4334 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4335 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4336 G. Wieggers.
4338 And thanks to everyone else who sent me email with suggestions, bug-reports
4339 and or just some feedback.
4340 </pre>
4346 <ul>
4348 - the default name of Apache's directory-level configuration file.</li>
4352 - a software application that enables a user to display and interact with
4353 text, images, and other information typically located on a web page at a
4354 website on the World Wide Web.</li>
4356 - a free software/open source data compression algorithm and program
4357 developed by Julian Seward.</li>
4359 - an important World Wide Web technology that enables a client web browser
4360 to request data from a program executed on the Web server.</li>
4362 - a log or record of changes made to a project.</li>
4364 - a computer system that accesses a (remote) service on another computer
4365 by some kind of network.</li>
4367 - a set of data values of a particular simple type, one for each row of
4368 the table.</li>
4370 - a packet of information sent by a server to a World Wide Web browser
4371 and then sent back by the browser each time it accesses that server.</li>
4373 - Comma-separated values</li>
4376 - an organized collection of data.</li>
4379 - a PHP module that extends PHP with additional functionality.</li>
4381 - a list of commonly asked question and there answers.</li>
4383 - one part of divided data/columns.</li>
4385 - a field or group of fields in a database record that point to a key
4386 field or group of fields forming a key of another database record in some
4387 (usually different) table.</li>
4389 - the free PDF library</li>
4391 GD Graphics Library</a> - a library by Thomas Boutell and others for
4392 dynamically manipulating images.</li>
4395 - gzip is short for GNU zip, a GNU free software file compression
4396 program.</li>
4398 - any machine connected to a computer network, a node that has a hostname.</li>
4400 - the unique name by which a network attached device is known on a network.</li>
4402 (HyperText Transfer Protocol)</a>
4403 - the primary method used to transfer or convey information on the World
4404 Wide Web.</li>
4407 additional security measures.</li>
4408 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4409 - a set of Internet-based services for servers using Microsoft Windows.</li>
4411 - a feature that allows quick access to the rows in a table.</li>
4413 - a data-oriented protocol used by source and destination hosts for
4414 communicating data across a packet-switched internetwork.</li>
4416 - a unique number that devices use in order to identify and communicate
4417 with each other on a network utilizing the Internet Protocol standard.</li>
4419 (Internet Server Application Programming Interface)</a>
4420 - the API of Internet Information Services (IIS).</li>
4422 - a business or organization that offers users access to the Internet and related services.</li>
4424 - a most commonly used standard method of lossy compression for
4425 photographic images.</li>
4431 - line of personal computers is designed, developed, manufactured, and
4432 marketed by Apple Computer.</li>
4433 <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>
4434 - the operating system which is included with all currently shipping Apple
4435 Macintosh computers in the consumer and professional markets.</li>
4437 - a cryptographic library.</li>
4439 - the MCrypt PHP extension.</li>
4440 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4441 - an Internet Standard for the format of e-mail.</li>
4443 - some sort of extension for the Apache Webserver.</li>
4445 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4446 Management System (DBMS).</li>
4448 - the improved MySQL client PHP extension.</li>
4450 - the MySQL client PHP extension.</li>
4452 - open standard for office documents.</li>
4453 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4454 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4456 (Portable Document Format)</a>
4457 - a file format developed by Adobe Systems for representing two
4458 dimensional documents in a device independent and resolution independent
4459 format.</li>
4461 - the PHP Extension and Application Repository.</li>
4463 - the perl-compatible regular expression functions for PHP</li>
4465 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4466 programming language used mainly for developing server-side applications
4467 and dynamic web content, and more recently, a broader range of software
4468 applications.</li>
4470 - a connection through which data is sent and received.</li>
4472 - Request for Comments (RFC) documents are a series of memoranda
4473 encompassing new research, innovations, and methodologies applicable to
4474 Internet technologies.</li>
4478 - represents a single, implicitly structured data item in a table.</li>
4480 - a computer system that provides services to other computing
4481 systems over a network.</li>
4482 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4483 - handlers for different table types</li>
4485 - a form of inter-process communication.</li>
4487 Sockets Layer)</a>
4488 - a cryptographic protocol which provides secure communication on the Internet.</li>
4490 - Structured Query Language</li>
4492 - a set of data elements (cells) that is organized, defined and stored as
4493 horizontal rows and vertical columns where each item can be uniquely
4494 identified by a label or key or by it?s position in relation to other items.</li>
4497 - a type of archive file format: the Tape ARchive format.</li>
4499 - one of the core protocols of the Internet protocol suite.</li>
4503 - a sequence of characters, conforming to a standardized format, that is
4504 used for referring to resources, such as documents and images on the
4505 Internet, by their location.</li>
4507 - A computer (program) that is responsible for accepting HTTP requests
4508 from clients and serving them Web pages.</li>
4510 - a W3C-recommended general-purpose markup language for creating
4511 special-purpose markup languages, capable of describing many different
4512 kinds of data.</li>
4514 - a popular data compression and archival format.</li>
4516 - an open-source, cross-platform data compression library by Jean-loup
4517 Gailly and Mark Adler.</li>
4518 </ul>
4528 </body>
4529 </html>