| blob | 9e891cc39578075899dfb881f56b469843f56da8 |
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 rm -rf config # remove not needed directory
274 </pre>
275 Now the file is ready to be used. You can choose to review or edit
276 the file with your favorite editor, if you prefer to set some
277 advanced options which the setup script does not provide.</li></ul></li>
278 <li>If you are using the
280 protect the phpMyAdmin installation directory because using
281 config does not require a user to
282 enter a password to access the phpMyAdmin installation. Use of an alternate
283 authentication method is recommended, for example with
291 in your browser. phpMyAdmin should now display a welcome screen
292 and your databases, or a login dialog if using
294 authentication mode.</li>
296 webserver configuration. For Apache you can use supplied .htaccess file
297 in that folder, for other webservers, you should configure this yourself.
298 Such configuration prevents from possible path exposure and cross side
299 scripting vulnerabilities that might happen to be found in that code.</li>
300 </ol>
304 <p> For a whole set of new features (bookmarks, comments,
307 transformation, etc.) you need to create a set of special tables. Those
308 tables can be located in your own database, or in a central database for a
309 multi-user installation (this database would then be accessed by the
310 controluser, so no other user should have rights to it).</p>
320 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
321 that you may need special (administrator) privileges to create the database
322 and tables, and that the script may need some tuning, depending on the
323 database name.</p>
328 section</a>. You will also need to have a controluser with the proper rights
335 unpacked one. Configuration files from very old versions (2.3.0 or before) may
336 require some tweaking as some options have been changed or removed.
338 statement that you might find near the end of your configuration file.</p>
342 is version-specific.</p>
345 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
346 you should run the SQL script found in
353 where you want to give users access to their own database and don't want
354 them to play around with others.<br />
355 Nevertheless be aware that MS Internet Explorer seems to be really buggy
357 in this area!<br />
360 that your user/password pair are not in clear in the configuration file.
361 </li>
364 authentication modes are more secure: the MySQL login information does
365 not need to be set in the phpMyAdmin configuration file (except possibly
367 However, keep in mind that the password travels in plain text, unless
368 you are using the HTTPS protocol.<br />
369 In cookie mode, the password is stored, encrypted with the blowfish
370 algorithm, in a temporary cookie.</li>
382 file under the
384 $cfg['Servers'][$i]['controluser']</a></tt> and
389 only an example: use something else in your file!</b> Input these
390 statements from the phpMyAdmin SQL Query window or mysql command–line
391 client.<br />
393 if it's not the same as the MySQL server's one.
395 <pre>
396 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
397 GRANT SELECT (
398 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
399 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
400 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
401 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
402 Execute_priv, Repl_slave_priv, Repl_client_priv
403 ) ON mysql.user TO 'pma'@'localhost';
404 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
405 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
406 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
407 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
409 If you want to use the many new relation and bookmark features:
411 <pre>
413 </pre>
419 on a set of particular databases. Normally you shouldn't give global
420 privileges to an ordinary user, unless you understand the impact of those
421 privileges (for example, you are creating a superuser).<br />
425 <pre>
426 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
427 </pre>
429 What the user may now do is controlled entirely by the MySQL user
430 management system.<br />
432 authentication mode, you don't need to fill the user/password fields
434 array.</li>
435 </ul>
440 method and allows you to log in as any valid MySQL user.</li>
441 <li>Is supported with most PHP configurations. For
454 mode.</li>
455 </ul>
459 <ul><li>You can use this method as a replacement for the
461 (for example, if you're running
463 <li>Obviously, the user must enable cookies in the browser, but this is
464 now a requirement for all authentication modes.</li>
465 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
466 with the same username.</li>
467 <li>If you want to log in to arbitrary server see
472 not required.</li>
473 </ul>
477 <ul><li>This mode is a convenient way of using credentials from another
478 application to authenticate to phpMyAdmin.</li>
479 <li>The other application has to store login information into
480 session data.</li>
482 section.</li>
483 </ul>
486 <ul><li>This mode is the less secure one because it requires you to fill the
488 $cfg['Servers'][$i]['user']</a> and
490 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
491 can read your config.inc.php can discover your username and password).
492 <br />
499 is an entry explaining how to protect your configuration file.</li>
500 <li>For additional security in this mode, you may wish to consider the Host
501 authentication
503 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
505 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
506 directives.</li>
507 <li>Unlike cookie and http, does not require a user to log in when first
508 loading the phpMyAdmin site. This is by design but could allow any
509 user to access your installation. Use of some restriction method is
511 HTTP-AUTH directive or disallowing incoming HTTP requests at
512 one’s router or firewall will suffice (both of which
513 are beyond the scope of this manual but easily searchable with Google).</li>
514 </ul>
516 <p>
517 The Swekey is a low cost authentication USB key that can be used in
518 web applications.<br /><br />
519 When Swekey authentication is activated, phpMyAdmin requires the
520 users's Swekey to be plugged before entering the login page (currently
521 supported for cookie authentication mode only). Swekey Authentication is
522 disabled by default.<br /><br />
524 </p>
525 <pre>
526 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
527 </pre>
528 <p>
530 each user with their Swekey Id. It is important to place this file outside
531 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
533 users' information.<br /><br />
534 If you want to purchase a Swekey please visit
536 since this link provides funding for phpMyAdmin.
537 </p>
538 <!-- CONFIGURATION -->
542 users:</span> PHP does not seem to like
546 before saving a script you have modified.</p>
551 section to create one. This file only needs to contain the parameters you want to
552 change from their corresponding default value in
555 <p> The parameters which relate to design (like colors) are placed in
558 your site specific code to be included on start and end of each page.</p>
562 (with full path) to your phpMyAdmin installation's directory.
565 some web servers are case–sensitive.
568 Starting with version 2.3.0, it is advisable to try leaving this
569 blank. In most cases phpMyAdmin automatically detects the proper
570 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
571 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
572 A good test is to browse a table, edit a row and save it. There should
573 be an error message if phpMyAdmin is having trouble auto–detecting
574 the correct value. If you get an error that this must be set or if
575 the autodetect code fails to detect your path, please post a bug
576 report on our bug tracker so we can improve the code.</dd>
580 with master / foreign – tables (see
582 <br />
583 If you tried to set this up and it does not work for you, have a look on
585 use it. You will find a link that will analyze why those features have
586 been disabled.<br />
587 If you do not want to use those features set this variable to
591 <dd>A warning is displayed on the main page if Suhosin is detected.
593 from appearing.</dd>
597 domain to call phpMyAdmin inside a frame, and is a potential security
598 hole allowing cross-frame scripting attacks.</dd>
602 algorithm to encrypt the password.<br />
604 passphrase of your choice. It will be used internally by the blowfish
605 algorithm: you won’t be prompted for this passphrase. The maximum
608 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
609 makes a bit weaker security as this generated secret is stored in
610 session and furthermore it makes impossible to recall user name from
611 cookie.</dd>
615 MySQL servers. Therefore, a
617 been added which contains the login information for the different servers.
618 The first
620 contains the hostname of the first server, the second
622 the hostname of the second server, etc. In
624 server definition, however you can put as many as you need in
626 have to define all settings, just those you need to change).</dd>
630 $i-th MySQL-server. E.g. localhost.</dd>
635 ignores this port number and connects with the socket, so if you want
636 to connect to a port different from the default port, use
639 </dd>
643 To determine the correct socket, check your MySQL configuration or, using the
645 Among the resulting information displayed will be the socket used.</dd>
648 <dd>Whether to enable SSL for connection to MySQL server.
649 </dd>
652 <dd>What type connection to use with the MySQL server. Your options are
654 is nearly guaranteed to be available on all MySQL servers, while
655 sockets are not supported on some platforms.<br /><br />
657 To use the socket mode, your MySQL server must be on the same machine
658 as the Web server.</dd>
661 <dd>What php MySQL extension to use for the connection. Valid options are:
662 <br /><br />
665 The classic MySQL extension. This is the recommended and default
666 method at this time.<br /><br />
669 The improved MySQL extension. This extension became available
670 with php 5.0.0 and is the recommended way to connect to a server
674 <dd>Whether to use a compressed protocol for the MySQL server connection
675 or not (experimental).<br />
681 </dt>
683 all relational features (see
685 and, for a MySQL server previous to 4.1.2 or running with
688 authentication mode).<br /><br />
691 cookie authentication modes (or 'config'
692 authentication mode since phpMyAdmin 2.2.1), you need to supply the
697 This account is used to check what databases the user will see at
698 login.<br />
702 In phpMyAdmin versions before 2.2.5, those were called
706 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
707 <dd>Whether config or cookie or
709 should be used for this server.
711 is the plain old way: username and password are stored in
713 <li>'cookie' authentication mode
715 2.2.3 allows you to log in as any valid MySQL user with the
716 help of cookies. Username and password are stored in
717 cookies during the session and password is deleted when it
718 ends. This can also allow you to log in in arbitrary server if
719 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
720 </li>
721 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
722 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
723 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
724 <li>'signon' authentication mode
726 as introduced in 2.10.0 allows you to log in from prepared PHP
727 session data. This is useful for implementing single signon
728 from another application. Sample way how to seed session is in
734 </ul>
737 for more information.
738 </dd>
740 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
741 </dt>
742 <dd>
744 names for hardware authentication. Leave empty to deactivate this feature.
745 </dd>
749 </dt>
750 <dd>
751 When using auth_type = 'config', this is the user/password-pair
752 which phpMyAdmin will use to connect to the
753 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
754 cookie authentication is used and should be empty.</dd>
756 <span
758 </dt>
759 <dd>
760 Allow attempt to log in without password when a login with password
761 fails. This can be used together with http authentication, when
762 authentication is done some other way and phpMyAdmin gets user name
763 from auth and uses empty password for connecting to MySQL. Password
764 login is still tried first, but as fallback, no password method is
765 tried.</dd>
768 </dt>
769 <dd>
770 If set to a (an array of) database name(s), only this (these) database(s)
771 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
772 database(s) name(s) may contain MySQL wildcards characters
776 This setting is an efficient way to lower the server load since the
777 latter does not need to send MySQL requests to build the available
779 privileges rules of the MySQL database server</span>. If set, it just
780 means only these databases will be displayed but
782 <br /><br />
784 An example of using more that one database:
786 <br /><br />
788 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
789 databases in the left frame, so that you can individually arrange your databases.<br />
790 If you want to have certain databases at the top, but don't care about the others, you do not
791 need to specify all other databases. Use:
793 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
794 order.</dd>
797 </dt>
798 <dd>Regular expression for hiding some databases. This only hides them
799 from listing, but a user is still able to access them (using, for example,
800 the SQL query area). To limit access, use the MySQL privilege system.
801 <br /><br />
806 More information on regular expressions can be found in the
808 PCRE pattern syntax</a> portion of the PHP reference manual.
809 </dd>
812 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
813 this string will be displayed instead of the hostname in the pull-down
814 menu on the main page. This can be useful if you want to show only
815 certain databases on your system, for example. For HTTP auth, all
816 non-US-ASCII characters will be stripped.</dd>
820 </dt>
821 <dd>The name of the database containing the linked-tables infrastructure.
822 <br /><br />
825 section in this document to see the benefits of this infrastructure,
826 and for a quick way of creating this database and the needed tables.
827 <br /><br />
829 If you are the only user of this phpMyAdmin installation, you can
830 use your current database to store those special tables; in this
831 case, just put your current database name in
833 set this parameter to the name of your central database containing
834 the linked-tables infrastructure.</dd>
838 </dt>
840 useful for queries you often run.<br /><br />
842 To allow the usage of this functionality:
844 <li>enter the table name in
846 </ul>
847 </dd>
851 </dt>
853 which field is a key in another table (a foreign key). phpMyAdmin
854 currently uses this to
855 <ul><li>make clickable, when you browse the master table, the data values
856 that point to the foreign table;</li>
858 when browsing the master table, if you move the mouse to a column
859 containing a foreign key (use also the 'table_info' table);<br />
862 <li>in edit/insert mode, display a drop-down list of possible foreign
866 <li>display links on the table properties page, to check referential
867 integrity (display missing foreign keys) for each described key;
868 </li>
872 schema of your database (also uses the table_coords table).</li>
873 </ul>
875 The keys can be numeric or character.<br /><br />
877 To allow the usage of this functionality:
880 infrastructure</li>
881 <li>put the relation table name in
883 <li>now as normal user open phpMyAdmin and for each one of your
884 tables where you want to use this feature, click
886 </li>
887 </ul>
891 future development of the cross-db relations.
892 </dd>
896 </dt>
897 <dd>
898 Since release 2.3.0 you can describe, in a special 'table_info'
899 table, which field is to be displayed as a tool-tip when moving the
900 cursor over the corresponding key.<br />
901 This configuration variable will hold the name of this special
902 table. To allow the usage of this functionality:
904 <li>put the table name in
906 <li>then for each table where you want to use this feature,
908 to choose the field.</li>
909 </ul>
911 </dd>
915 </dt>
918 the relations between your tables. To do this it needs two tables
923 schema output).<br /><br />
927 To allow the usage of this functionality:
930 infrastructure</li>
931 <li>put the correct table names in
934 </ul>
937 </dd>
941 </dt>
943 Since release 2.3.0 you can store comments to describe each column for
945 <br /><br />
947 Starting with release 2.5.0, comments are consequently used on the table
948 property pages and table browse view, showing up as tool-tips above the
949 column name (properties page) or embedded within the header of table in
950 browse view. They can also be shown in a table dump. Please see the
951 relevant configuration directives later on.<br /><br />
953 Also new in release 2.5.0 is a MIME-transformation system which is also
955 Transformations</a> for further information. To use the
956 MIME-transformation system, your column_info table has to have the three
957 new fields 'mimetype', 'transformation', 'transformation_options'.
958 <br /><br />
960 To allow the usage of this functionality:
962 infrastructure</li>
963 <li>put the table name in
967 <pre>
968 ALTER TABLE `pma_column_comments`
969 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
970 ADD `transformation` VARCHAR( 255 ) NOT NULL,
971 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
972 </pre>
975 renamed from<br />
978 </ul>
979 </dd>
983 </dt>
986 all queries you entered manually into the phpMyAdmin interface. If you
987 don't want to use a table-based history, you can use the JavaScript-based
988 history. Using that, all your history items are deleted when closing the
989 window.<br /><br />
991 Using
993 you can specify an amount of history items you want to have on hold. On
994 every login, this list gets cut to the maximum amount.<br /><br />
996 The query history is only available if JavaScript is enabled in your
997 browser.<br /><br />
999 To allow the usage of this functionality:
1002 infrastructure</li>
1004 </li>
1005 </ul>
1006 </dd>
1010 </dt>
1012 to visually manage the relations.
1013 <br /><br />
1015 To allow the usage of this functionality:
1018 infrastructure</li>
1020 </li>
1021 </ul>
1022 </dd>
1025 </dt>
1027 column_info table got enhanced with three new fields. If the above variable
1029 latest table structure available. If not, it will emit a warning to the
1030 superuser.<br /><br />
1032 You can disable this checking behavior by setting the variable to false,
1033 which should offer a performance increase.<br /><br />
1035 Recommended to set to FALSE, when you are sure, your table structure is
1036 up to date.</dd>
1038 boolean</dt>
1039 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1040 </dd>
1041 <dt><span id="cfg_Servers_AllowNoPasswordRoot">$cfg['Servers'][$i]['AllowNoPasswordRoot']</span>
1042 boolean</dt>
1043 <dd>Whether to allow access to root user without password. The default
1045 to a MySQL server with was left with an empty password for root.
1046 </dd>
1049 </dt>
1051 authentication is disabled.<br /><br />
1054 all deny rules followed by allow rules. Access is allowed by default. Any
1055 client which does not match a Deny command or does match an Allow command
1056 will be allowed access to the server. <br /><br />
1059 applies all allow rules followed by deny rules. Access is denied by
1060 default. Any client which does not match an Allow directive or does
1061 match a Deny directive will be denied access to the server.<br /><br />
1063 If your rule order is set to 'explicit', the authentication is
1064 performed in a similar fashion to rule order 'deny,allow', with the
1068 and was available in Apache by specifying allow and deny rules without
1069 setting any order.<br /><br />
1071 Please also see <a
1073 address behind proxies.
1074 </dd>
1076 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1077 </dt>
1078 <dd>The general format for the rules is as such:
1080 <pre>
1082 </pre>
1087 well (please note that those containing SERVER_ADDRESS might not be
1088 available on all webservers):
1089 <pre>
1095 </pre>
1097 Having an empty rule list is equivalent to either using
1103 following work:<br />
1105 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1106 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1107 But the following does not work:<br />
1110 </dd>
1111 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1112 <dd>Name of session which will be used for signon authentication method.
1113 </dd>
1115 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1116 </dd>
1118 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1119 </dd>
1122 <dd>If you have more than one server configured, you can set
1124 that server when phpMyAdmin is started, or set it to 0 to be given a
1125 list of servers without logging in.<br />
1127 MUST be set to that server.</dd>
1130 <dd>The maximum number of database names to be displayed in the
1131 navigation frame and the database list.</dd>
1134 <dd>The maximum number of table names to be displayed in the
1135 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1136 when in Light mode.</dd>
1139 <dd>The maximum number of characters when a SQL query is displayed. The
1140 default limit of 1000 should be correct to avoid the display of tons
1141 of hexadecimal codes that represent BLOBs, but some users have real
1142 SQL queries that are longer than 1000 characters. Also, if a query's
1143 length exceeds this limit, this query is not saved in the history.</dd>
1146 <dd>Defines whether to use GZip output buffering for increased
1148 Set to true/false for enabling/disabling. When set to 'auto' (string),
1149 phpMyAdmin tries to enable output buffering and will automatically disable
1150 it if your browser has some problems with buffering. IE6 with a certain patch
1151 is known to cause data corruption when having enabled buffering.</dd>
1154 <dd>Whether persistent connections should be used or not (mysql_connect or
1155 mysql_pconnect).</dd>
1161 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1162 to zero, no time limit is imposed.<br />
1163 This setting is used while importing/exporting dump files but has no
1164 effect when PHP is running in safe mode.</dd>
1167 <dd>Set the number of bytes a script is allowed to allocate. If number set
1168 to zero, no limit is imposed.<br />
1169 This setting is used while importing/exporting dump files but has no
1170 effect when PHP is running in safe mode.<br />
1174 <dd>Mark used tables and make it possible to show databases with locked
1179 generated by phpMyAdmin should be displayed or not.</dd>
1182 <dd>Defines whether normal users (non-administrator) are allowed to
1183 delete their own database or not. If set as FALSE, the link "Drop
1185 mydatabase" will be rejected. Quite practical for
1187 customers.<br />
1188 Please note that this limitation of SQL queries is not as strict as
1189 when using MySQL privileges. This is due to nature of SQL queries
1190 which might be quite complicated. So this choice should be viewed as
1191 help to avoid accidental dropping rather than strict privilege
1192 limitation.</dd>
1196 displayed when you're about to lose data.</dd>
1199 <dd>Define whether the previous login should be recalled or not in cookie
1200 authentication mode.<br /><br />
1202 This is automatically disabled if you do not have configured
1204 </dd>
1211 means that it will be kept for existing session. This is recommended
1212 for not trusted environments.</dd>
1215 <dd>If enabled (default), logout deletes cookies for all servers,
1216 otherwise only for current one. Setting this to false makes it easy to
1217 forget to log out from other server, when you are using more of
1218 them.</dd>
1224 <dd>Define whether phpMyAdmin will continue executing a multi-query
1225 statement if one of the queries fails. Default is to abort execution.</dd>
1228 <dd>Define whether phpMyAdmin will output the results of each query of a
1229 multi-query statement embedded into the
1234 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1235 <br /><br />
1238 MySQL servers behind the firewall where your
1240 </dd>
1243 <dd>Defines whether to use a select-based menu and display only the current
1244 tables in the left frame (smaller page). Only in Non-Lightmode you can
1245 use the feature to display nested folders using
1247 </dd>
1250 <dd>In light mode, defines whether to display the names of databases (in the
1251 selector) using a tree, see also
1253 </dd>
1256 <dd>The string used to separate the parts of the database name when showing
1257 them in a tree.</dd>
1260 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1261 This means if you have tables like 'first__second__third' this will be
1263 If set to FALSE or empty, the feature is disabled. NOTE: You should
1264 not use this separator at the beginning or end of a
1265 table name or multiple times after another without any other
1266 characters in between.</dd>
1269 <dd>Defines how many sublevels should be displayed when splitting
1270 up tables by the above separator.</dd>
1273 <dd>Defines whether to display table comment as tool-tip in left frame or
1274 not.</dd>
1277 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1278 comment and the real name. That means that if you have a table called
1279 'user0001' and add the comment 'MyName' on it, you will see the name
1280 'MyName' used consequently in the left frame and the tool-tip shows
1281 the real name of the DB.</dd>
1284 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1286 When setting this to 'nested', the Alias of the Tablename is only used
1287 to split/nest the tables according to the
1289 directive. So only the folder is called like the Alias, the tablename itself
1290 stays the real tablename.</dd>
1293 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1296 <dd>Enter URL where logo in the navigation frame will point to.
1297 For use especially with self made theme which changes this.
1306 <dd>Defines whether or not to display a server choice at the top of the left frame.
1307 Defaults to FALSE.</dd>
1309 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1310 Defaults to FALSE (drop-down).</dd>
1312 <dd>Defines whether to display database choice in light navigation frame as links
1313 instead of in a drop-down. Defaults to 'auto' - on main page list is
1314 shown, when database is selected, only drop down is displayed.</dd>
1317 <dd>Defines the tab displayed by default when clicking the small
1318 icon next to each table name in the navigation panel. Possible
1324 <dd>Defines whether or not to display space usage and statistics about databases
1325 and tables.<br />
1326 Note that statistics requires at least MySQL 3.23.3 and that, at this
1327 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1330 <dd>Defines whether to display detailed server information on main page.
1331 You can additionally hide more information by using
1333 </dd>
1338 </dt>
1341 not at the starting main (right) frame. This setting
1342 does not check MySQL commands entered directly.<br /><br />
1344 Please note that to block the usage of phpinfo() in scripts, you
1351 hard coded password value in the configuration file, end users can't
1352 be allowed to change their passwords.</dd>
1355 <dd>Defines whether to suggest a database name on the
1359 <dd>Defines whether navigation bar buttons and the right panel top menu
1360 contain text or symbols only. A value of TRUE displays icons, FALSE
1361 displays text and 'both' displays both icons and text.</dd>
1364 <dd>Defines whether a user should be displayed a
1368 <dd>Number of rows displayed when browsing a result set. If the result set
1375 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1379 from editing when browsing a table's content. Valid values are:
1384 </ul>
1385 </dd>
1388 <dd>Defines whether or not MySQL functions fields should be initially
1389 displayed in edit/insert mode. Since version 2.10, the user can
1390 toggle this setting from the interface.
1391 </dd>
1394 <dd>Defines which type of editing controls should be used for CHAR and
1395 VARCHAR fields. Possible values are:
1396 <ul><li>input - this allows to limit size of text to size of field in
1397 MySQL, but has problems with newlines in fields</li>
1398 <li>textarea - no problems with newlines in fields, but also no
1399 length limitations</li>
1400 </ul>
1401 Default is old behavior so input.</dd>
1407 <dd>If there are fewer items than this in the set of foreign keys, then a
1408 drop-down box of foreign keys is presented, in the style described by the
1410 setting.</dd>
1413 <dd>For the foreign key drop-down fields, there are several methods of
1414 display, offering both the key and value data. The contents of the
1415 array should be one or both of the following strings:
1421 </dt>
1422 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1423 creating a dump file</dd>
1426 </dt>
1427 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1428 compressed exports. This doesn't affect smaller dumps and allows users to
1429 create larger dumps that won't otherwise fit in memory due to php
1430 memory limit. Produced files contain more GZip/BZip2 headers, but all
1431 normal programs handle this correctly.</dd>
1435 mainframe.</dd>
1439 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1444 <dd>How many columns will be utilized to display the tables on the
1445 database property view? Default is 1 column. When setting this to a
1446 value larger than 1, the type of the database will be omitted for more
1447 display space.</dd>
1451 <dd>Defines the tab displayed by default on server view. Possible
1458 <dd>Defines the tab displayed by default on database view. Possible
1463 <dd>Defines the tab displayed by default on table view. Possible
1470 points to the MySQL documentation (type depends
1471 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1472 generated.<br />
1474 for more information about MySQL manuals and their types.</dd>
1477 <dd>Type of MySQL documentation:
1483 </ul>
1484 </dd>
1487 <dd>Defines the default language to use, if not browser-defined or
1488 user-defined.<br />
1490 this setting.</dd>
1493 <dd>Defines the default connection collation to use, if not
1494 user-defined.<br />
1499 <dd>Force: always use this language (must be defined in the
1503 <dd>Limit list of available languages to those matching the given regular
1504 expression. For example if you want only Czech and English, you should
1508 <dd>Default character set to use for recoding of MySQL queries. This must be
1509 enabled and it's described by
1511 option.<br />
1512 You can give here any character set which is in
1514 array and this is just default choice, user can select any of them.</dd>
1517 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1518 support (compiled in or module) in PHP to allow MySQL queries recoding
1519 and used language file must have it enabled (by default only these
1520 which are in Unicode, just to avoid losing some characters).<br /><br />
1523 in the Export page, to choose the character set when exporting a file.
1525 </dd>
1528 <dd>You can select here which functions will be used for character set
1529 conversion. Possible values are:
1530 <ul><li>auto - automatically use available one (first is tested
1531 iconv, then recode)</li>
1534 </ul>
1535 Default is auto.</dd>
1538 <dd>Specify some parameters for iconv used in charset conversion. See
1541 used, so that invalid characters will be transliterated.</dd>
1544 <dd>Available character sets for MySQL conversion. You can add your own (any of
1545 supported by recode/iconv) or remove these which you don't use.
1546 Character sets will be shown in same order as here listed, so if you
1547 frequently use some of these move them to the top.</dd>
1552 default empty, you need to fill in some trusted proxy servers if you
1553 want to use rules for IP addresses behind proxy.<br /><br />
1555 The following example specifies that phpMyAdmin should trust a
1557 <pre>
1558 $cfg['TrustedProxies'] =
1560 </pre>
1561 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1562 client's IP address as usual.
1563 </dd>
1567 MIME transformations.<br />
1568 Possible values are:
1569 <ul><li>auto - automatically detect, this is a bit expensive
1571 according to your server real possibilities</li>
1574 </ul>
1575 Default is auto.
1576 </dd>
1579 <dd>
1580 We normally check the permissions on the configuration file to ensure
1581 it's not world writable. However, phpMyAdmin could be installed on
1582 a NTFS filesystem mounted on a non-Windows server, in which case the
1583 permissions seems wrong but in fact cannot be detected. In this case
1585 </dd>
1589 </dd>
1591 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1592 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1593 </dt>
1594 <dd>The background styles used for both the frames.
1597 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1599 <dd>The style used for the pointer in the navi frame.
1603 </dt>
1604 <dd>The color used for the database name in the navi frame.
1613 </dd>
1617 <dd>The style used for table headers. See
1622 </dd>
1626 </dd>
1628 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1630 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1632 </dt>
1634 The former feature highlights the row over which your mouse is passing
1635 and the latter lets you visually mark/unmark rows by clicking on
1636 them.<br />
1641 <dd>You put here a valid CSS font family value, for example
1646 <dd>You put here a valid CSS font family value, for example
1660 </dt>
1662 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1664 The Char* values are used for CHAR and VARCHAR editing (if configured
1668 </dt>
1672 </dt>
1673 <dd>Defines if the whole textarea of the query box will be selected on
1674 click.</dd>
1677 </dt>
1678 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1679 editing.</dd>
1682 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1683 Can be turned off by a toggle button on the browse page.</dd>
1687 </dt>
1688 <dd>Defines the place where modify and delete links would be put when
1689 tables contents are displayed (you may have them displayed both at the
1690 left and at the right).
1696 </dt>
1698 Define which one is displayed by default. The first mode displays each
1699 row on a horizontal line, the second rotates the headers by 90
1700 degrees, so you can use descriptive headers even though fields only
1701 contain small values and still print them out. The vertical mode sorts
1702 each row on a vertical lineup.<br /><br />
1704 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1705 the rotation of the header for horizontalflipped is done via CSS. If
1706 set to 'fake' PHP does the transformation for you, but of course this
1707 does not look as good as CSS.</dd>
1711 string or integer</dt>
1712 <dd>When editing/creating new columns in a table all fields normally get
1713 lined up one field a line. (default: 'horizontal'). If you set this to
1714 'vertical' you can have each field lined up vertically beneath each
1715 other. You can save up a lot of place on the horizontal direction and
1716 no longer have to scroll. If you set this to integer, editing of fewer
1717 columns will appear in 'vertical' mode, while editing of more fields
1718 still in 'horizontal' mode. This way you can still effectively edit
1719 large number of fields, while having full view on few of them.</dd>
1723 </dt>
1725 display of column comments in Browse or Property display. In browse
1726 mode, the comments are shown inside the header. In property mode,
1727 comments are displayed using a CSS-formatted dashed-line below the
1728 name of the field. The comment is shown as a tool-tip for that field.
1729 </dd>
1741 <dd>Whether to display a link to validate a query in any SQL Query box.
1748 <dd>
1749 The name of the directory where
1751 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1752 are available under a drop-down box when you click the database or
1753 table name, then the Import tab.
1754 <br /><br />
1756 If you want different directory for each user, %u will be replaced
1757 with username.<br /><br />
1761 compressed formats is enabled).<br /><br />
1763 This feature is useful when your file is too big to be uploaded via
1765 uploads are disabled in PHP.<br /><br />
1767 Please note that if PHP is running in safe mode, this directory must
1768 be owned by the same user as the owner of the phpMyAdmin scripts.
1769 <br /><br />
1773 alternatives.
1774 </dd>
1777 <dd>
1778 The name of the directory where dumps can be saved.<br /><br />
1780 If you want different directory for each user, %u will be replaced
1781 with username.<br /><br />
1783 Please note that the directory must exist and has to be writable for
1784 the user running webserver.<br /><br />
1786 Please note that if PHP is running in safe mode, this directory must
1787 be owned by the same user as the owner of the phpMyAdmin scripts.
1788 </dd>
1791 <dd>
1792 The name of the directory where temporary files can be stored.
1793 <br /><br />
1795 This is needed for native MS Excel export, see
1801 <br /><br />
1803 If the directory where phpMyAdmin is installed is subject to an
1805 temporary directory in some directory accessible by the web
1806 server. However for security reasons, this directory should be outside
1807 the tree published by webserver. If you cannot avoid having this
1808 directory published by webserver, place at least an empty
1810 possible.
1811 <br /><br />
1813 This directory should have as strict permissions as possible as the only
1814 user required to access this directory is the one who runs the
1815 webserver. If you have root privileges, simply make this user owner of
1816 this directory and make it accessible only by it:
1817 <br /><br />
1819 <pre>
1820 chown www-data:www-data tmp
1821 chmod 700 tmp
1822 </pre>
1824 If you cannot change owner of the directory, you can achieve a similar
1827 <pre>
1828 chmod 700 tmp
1829 setfacl -m "g:www-data:rwx" tmp
1830 setfacl -d -m "g:www-data:rwx" tmp
1831 </pre>
1833 If neither of above works for you, you can still make the directory
1835 system reading and writing data in this directory.
1836 </dd>
1839 <dd>
1840 In this array are defined default parameters for export, names of
1841 items are similar to texts seen on export page, so you can easily
1842 identify what they mean.
1843 </dd>
1846 <dd>
1847 In this array are defined default parameters for import, names of
1848 items are similar to texts seen on import page, so you can easily
1849 identify what they mean.
1850 </dd>
1853 <dd>
1854 Repeat the headers every X cells, or 0 to deactivate.
1855 </dd>
1863 </dt>
1864 <dd>
1865 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1866 or icon is always displayed on the left panel. If JavaScript is enabled in
1867 your browser, a click on this opens a distinct query window, which is
1868 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1869 changes to display a query box.<br /><br />
1871 The size of this query window can be customized with
1873 - both integers for the size in pixels. Note that normally, those
1875 theme you are using.<br /><br />
1879 opens the query window and puts the current query
1880 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1881 query in the right panel's query box.
1882 <br /><br />
1883 The usage of the JavaScript query window is recommended if you have a
1884 JavaScript enabled browser. Basic functions are used to exchange quite
1885 a few variables, so most 4th generation browsers should be capable to
1886 use that feature. It currently is only tested with Internet Explorer 6
1887 and Mozilla 1.x.
1888 <br /><br />
1890 to a table, which has to be created by you (see <a
1892 all your queries will be appended to the form, but only as long as
1893 your window is opened they remain saved.
1894 <br /><br />
1895 When using the JavaScript based query window, it will always get
1896 updated when you click on a new table/db to browse and will focus if
1897 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1898 the query window by checking the box "Do not overwrite this query from
1899 outside the window" below the query textarea. Then you can browse
1900 tables/databases in the background without losing the contents of the
1901 textarea, so this is especially useful when composing a query with
1902 tables you first have to look in. The checkbox will get automatically
1903 checked whenever you change the contents of the textarea. Please
1904 uncheck the button whenever you definitely want the query window to
1905 get updated even though you have made alterations.
1906 <br /><br />
1909 <br /><br />
1910 The query window also has a custom tabbed look to group the features.
1912 default tab to be used when opening the query window. It can be set to
1913 either 'sql', 'files', 'history' or 'full'.</dd>
1919 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1921 If the approximate row count as returned by
1924 count will be used.
1925 </dd>
1927 <dd>For VIEWs, since obtaining the exact count could have an
1928 impact on performance, this value is the maximum to be displayed, using
1930 any row counting.
1931 </dd>
1935 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1937 page. By clicking on the button 'toggle scratchboard' on the page
1938 where you edit x/y coordinates of those elements you can activate a
1939 scratchboard where all your elements are placed. By clicking on an
1940 element, you can move them around in the pre-defined area and the x/y
1941 coordinates will get updated dynamically. Likewise, when entering a
1942 new position directly into the input field, the new position in the
1943 scratchboard changes after your cursor leaves the input field.<br />
1944 You have to click on the 'OK'-button below the tables to save the new
1945 positions. If you want to place a new element, first add it to the
1946 table of elements and then you can drag the new element around.<br />
1947 By changing the paper size and the orientation you can change the size
1948 of the scratchboard as well. You can do so by just changing the
1949 dropdown field below, and the scratchboard will resize automatically,
1950 without interfering with the current placement of the elements.<br />
1951 If ever an element gets out of range you can either enlarge the paper
1952 size or click on the 'reset' button to place all elements below each
1953 other.<br />
1955 get this control to work. The basic Drag&Drop script functionality
1956 was kindly borrowed from www.youngpup.net and is underlying so
1957 specific license.</dd>
1960 <dd>Sorts database and table names according to natural order (for example,
1961 t1, t2, t10). Currently implemented in the left panel (Light mode)
1962 and in Database view, for the table list.</dd>
1966 closed state. A value of 'open' does the reverse.</dd>
1972 <dd>Allows you to specify window's title bar. Following magic string can
1973 be used to get special values:
1974 <dl>
1980 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1989 </dl>
1990 </dd>
2000 </dd>
2003 <dd>If theme manager is active, use this as the path of the subdirectory
2004 containing all the themes.</dd>
2018 </dt>
2019 <dd>Default queries that will be displayed in query boxes when user didn't
2020 specify any. Use %d for database name, %t for table name and %f for a
2021 comma separated list of field names. Note that %t and %f are only
2025 <dd>
2026 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
2027 default we use HTML to format the query, but you can disable this by
2029 </dd>
2032 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2033 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2034 query inside a bracket is indented. By changing
2037 specifies the units of the indent amount that you specified. This is
2038 used via stylesheets.</dd>
2041 <dd>This array is used to define the colours for each type of element of
2042 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2044 If you specify an empty string for the color of a class, it is ignored
2045 in creating the stylesheet.
2046 You should not alter the class names, only the colour strings.<br />
2067 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2071 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2072 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2073 </ul>
2074 </dd>
2078 <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,
2079 as originally published on
2081 <br />
2082 For help in setting up your system to use the service, see the
2084 </dd>
2088 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2089 and any password, so we use those by default. Instead, if
2090 you have an account with them, you can put your login details
2091 here, and it will be used in place of the anonymous login.</dd>
2092 </dl>
2093 </dd>
2096 <dd><b>DEVELOPERS ONLY!</b></dd>
2099 <dd><b>DEVELOPERS ONLY!</b><br />
2100 Enable logging queries and execution times to be displayed in the bottom
2101 of main page (right frame).</dd>
2104 <dd><b>DEVELOPERS ONLY!</b><br />
2105 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2106 the code.<br />
2107 For help in setting up your system to this, see the
2111 <dd><b>DEVELOPERS ONLY!</b><br />
2112 Enable profiling support for phpMyAdmin. This will append a chunk of data
2113 to the end of every page displayed in the main window with profiling
2114 statistics for that page.<br />
2115 You may need to increase the maximum execution time for this to
2116 complete successfully.<i>Profiling was removed from the code for
2117 version 2.9.0 due to licensing issues.</i></dd>
2119 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2120 <dd><b>DEVELOPERS ONLY!</b><br />
2121 When profiling data is displayed, this variable controls the threshold of
2122 display for any profiling data, based on the average time each time has
2123 taken. If it is over the threshold it is displayed, otherwise it is not
2124 displayed. This takes a value in milliseconds. In most cases you don't need
2125 to edit this.</dd>
2128 <dd>All possible types of a MySQL column. In most cases you don't need to
2129 edit this.</dd>
2132 <dd>Possible attributes for fields. In most cases you don't need to edit
2133 this.</dd>
2136 <dd>A list of functions MySQL supports. In most cases you don't need to
2137 edit this.</dd>
2140 <dd>Mapping of column types to meta types used for preferring displayed
2141 functions. In most cases you don't need to edit this.</dd>
2144 <dd>Functions preferred for column meta types as defined in
2145 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2146 to edit this.</dd>
2149 <dd>Functions selected by default when inserting/changing row, Functions
2150 are defined for meta types from
2152 <code>first_timestamp</code>, which is used for first timestamp column
2153 in table.</dd>
2156 <dd>Operators available for search operations on numeric and date fields.
2157 </dd>
2160 <dd>Operators available for search operations on character fields.
2161 Note that we put <code>LIKE</code> by default instead of
2162 <code>LIKE %...%</code>, to avoid unintended performance problems
2163 in case of huge tables.</dd>
2166 <dd>Operators available for search operations on enum fields.</dd>
2169 <dd>Additional operators available for search operations when the
2170 field can be null.</dd>
2172 </dl>
2174 <!-- TRANSFORMATIONS -->
2180 </ol>
2184 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2186 section</a> on how to do so.</p>
2188 <p> You can apply different transformations to the contents of each field. The
2189 transformation will take the content of each field and transform it with
2190 certain rules defined in the selected transformation.</p>
2192 <p> Say you have a field 'filename' which contains a filename. Normally you would
2193 see in phpMyAdmin only this filename. Using transformations you can transform
2194 that filename into a HTML link, so you can click inside of the phpMyAdmin
2195 structure on the field's link and will see the file displayed in a new browser
2196 window. Using transformation options you can also specify strings to
2197 append/prepend to a string or the format you want the output stored in.</p>
2199 <p> For a general overview of all available transformations and their options,
2200 you can consult your
2201 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2202 installation.</p>
2204 <p> For a tutorial on how to effectively use transformations, see our
2206 the official phpMyAdmin homepage.</p>
2210 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2211 clicking on the 'Structure' link for a table). There click on
2212 "Change" (or change icon) and there you will see three new fields at
2213 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2214 'Transformation options'.</p>
2216 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2217 that corresponds to the column's contents. Please note that
2218 transformations are inactive as long as no MIME-type is selected.</li>
2220 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2221 hopefully growing amount of pre-defined transformations. See below for information on
2222 how to build your own transformation.<br />
2224 There are global transformations and mimetype-bound transformations. Global transformations
2225 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2226 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2227 transformations which operate on the main mimetype (like 'image'), which will most likely
2228 take the subtype into regard, and those who only operate on a
2229 specific subtype (like 'image/jpeg').<br />
2231 You can use transformations on mimetypes for which the function was not defined for. There
2232 is no security check for you selected the right transformation, so take care of what the
2233 output will be like.</li>
2235 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2236 transform-function specific options here. Usually the transforms can operate with default
2237 options, but it is generally a good idea to look up the overview to see which options are
2238 necessary.<br />
2240 Much like the ENUM/SET-Fields, you have to split up several options using the format
2241 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2242 parsed as an array, leaving the first value the first element in the array, and so
2243 forth.<br />
2245 If you want to specify a MIME character set you can define it in the transformation_options.
2246 You have to put that outside of the pre-defined options of the specific mime-transform,
2248 for which you can specify 2 options and you want to append a character set, enter "'first
2249 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2251 </ul>
2255 <p> All mimetypes and their transformations are defined through single files in
2256 the directory 'libraries/transformations/'.</p>
2258 <p> They are stored in files to ease up customization and easy adding of new
2259 transformations.</p>
2261 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2262 always work. It makes no sense to apply a transformation to a mimetype, the
2263 transform-function doesn't know to handle.</p>
2265 <p> One can, however, use empty mime-types and global transformations which should work
2266 for many mimetypes. You can also use transforms on a different mimetype they where built
2267 for, but pay attention to option usage as well as what the transformation does to your
2268 field.</p>
2270 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2271 any other transform function and provides some basic functions.</p>
2273 <p> There are 5 possible file names:</p>
2275 <ol><li>A mimetype+subtype transform:<br /><br />
2277 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2279 Please not that mimetype and subtype are separated via '_', which shall
2280 not be contained in their names. The transform function/filename may
2281 contain only characters which cause no problems in the file system as
2282 well as the PHP function naming convention.<br /><br />
2284 The transform function will the be called
2285 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2287 <b>Example:</b><br /><br />
2289 <tt>text_html__formatted.inc.php</tt><br />
2290 <tt>PMA_transform_text_html__formatted()</tt></li>
2292 <li>A mimetype (w/o subtype) transform:<br /><br />
2294 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2296 Please note that there are no single '_' characters.
2297 The transform function/filename may contain only characters which cause
2298 no problems in the file system as well as the PHP function naming
2299 convention.<br /><br />
2301 The transform function will the be called
2302 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2304 <b>Example:</b><br /><br />
2306 <tt>text__formatted.inc.php</tt><br />
2307 <tt>PMA_transform_text__formatted()</tt></li>
2309 <li>A mimetype+subtype without specific transform function<br /><br />
2311 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2313 Please note that there are no '__' characters in the filename. Do not
2314 use special characters in the filename causing problems with the file
2315 system.<br /><br />
2317 No transformation function is defined in the file itself.<br /><br />
2319 <b>Example:</b><br /><br />
2321 <tt>text_plain.inc.php</tt><br />
2322 (No function)</li>
2324 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2326 <tt>[mimetype].inc.php</tt><br /><br />
2328 Please note that there are no '_' characters in the filename. Do not use
2329 special characters in the filename causing problems with the file system.
2330 <br /><br />
2332 No transformation function is defined in the file itself.<br /><br />
2334 <b>Example:</b><br /><br />
2336 <tt>text.inc.php</tt><br />
2337 (No function)</li>
2339 <li>A global transform function with no specific mimetype<br /><br />
2341 <tt>global__[transform].inc.php</tt><br /><br />
2343 The transform function will the be called
2344 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2346 <b>Example:</b><br /><br />
2348 <tt>global__formatted</tt><br />
2349 <tt>PMA_transform_global__formatted()</tt></li>
2350 </ol>
2352 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2353 transform function.</p>
2355 <p> All filenames containing no '__' in themselves are not shown as valid transform
2356 functions in the dropdown.</p>
2358 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2359 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2360 without a transform function. Also note the introduction of a function description in
2361 the language files. For each function a $strTransformation_[filename without .inc.php]
2362 has to exist.</p>
2364 <p> You can use the template generator to generate new functions and entries in the
2365 language file.</p>
2367 <p> To create a new transform function please see
2368 <tt>libraries/transformations/template_generator.sh</tt>.
2369 To create a new, empty mimetype please see
2370 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2372 <p> A transform function always gets passed three variables:</p>
2374 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2375 you want to transform.</li>
2376 <li><b>$options</b> - Contains any user-passed options to a transform function
2377 as an array.</li>
2378 <li><b>$meta</b> - Contains an object with field information to your column.
2379 The data is drawn from the output of the
2381 function. This means, all object properties described on the
2383 available in this variable and can be used to transform a field accordingly
2384 to unsigned/zerofill/not_null/... properties.<br />
2385 The $meta->mimetype variable contains the original MIME-type of the
2386 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2387 </ol>
2389 <!-- FAQ -->
2396 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2400 </ol>
2402 <p> Please have a look at our
2404 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2405 features and or interface.</p>
2411 action is required or phpMyAdmin sends a blank page or a page full of
2412 cryptic characters to my browser, what can I do?</a></h4>
2414 <p> There are some known PHP bugs with output buffering and compression.<br />
2416 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2417 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2418 configuration file.<br />
2419 Furthermore, we know about such problems connected to the release
2420 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2421 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2426 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2427 See also the
2429 entry about PHP bugs with output buffering.<br />
2430 If your server keeps crashing, please ask for help in the various Apache
2431 support groups.</p>
2435 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2436 script: I'm always displayed the login screen.</a></h4>
2438 <p> This is a known PHP bug (see this
2440 official PHP bug database. It means there is and won't be any phpMyAdmin
2441 fix against it because there is no way to code a fix.</p>
2447 application misbehaved by not returning a complete set of
2449 </h4>
2451 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2452 Have a look at the last message in this
2454 official PHP bug database.</p>
2459 and/or many error messages with the
2461 mode.</a></h4>
2463 <p> This is a known problem with the PHP
2465 filter: it's not so stable. Please use instead the cookie authentication mode.
2466 </p>
2471 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2472 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2473 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2474 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2475 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2480 work.</a></h4>
2482 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2483 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2484 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2485 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2486 We faced PHP crashes when trying to download a dump with MS Internet
2487 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2488 this case you should switch to the release version of PHP 4.2.0.</p>
2492 an error about safe mode being in effect.</a></h4>
2494 <p> Your uploaded file is saved by PHP in the "upload dir", as
2495 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2496 the system default is <i>/tmp</i>).<br />
2497 We recommend the following setup for Apache servers running in safe mode,
2498 to enable uploads of files while being reasonably secure:</p>
2500 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2501 <li>give ownership to the Apache server's user.group:
2502 <tt>chown apache.apache /tmp/php</tt></li>
2503 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2504 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2505 <li>restart Apache</li>
2506 </ul>
2510 general file uploads don't work on my system and uploaded files have a
2511 <tt>Content-Type:</tt> header in the first line.</a></h4>
2513 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2514 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2515 So the problem is that this package has a serious bug that was corrected
2516 ages ago in PHP (2001-01-28: see
2518 for more details). The problem is that the bugged package is still
2519 available though it was corrected (see
2521 for more details).<br />
2522 So please download
2523 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2524 and the problem should go away.<br />
2525 And that fixes the \r\n problem with file uploads!</p>
2529 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2530 I'm using the Apache server.</a></h4>
2532 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2533 your <i>httpd.conf</i>:</p>
2537 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2541 uploading a file from the query box.</a></h4>
2543 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2544 restrictions. However you need to create temporary directory and
2546 The uploaded files will be moved there, and after execution of your
2552 <p> The MySQL manual explains how to
2554 reset the permissions</a>.</p>
2559 execute a bookmark.</a></h4>
2561 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2562 cannot access the uploaded query.</p>
2567 submit a query from the convenient text area.</a></h4>
2569 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2570 and try to increase it.</p>
2574 </h4>
2576 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2577 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2578 names to align with current standards.</p>
2583 </h4>
2585 <p> Starting with version 2.7.0, the import engine has been re–written and these
2586 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2587 to take advantage of the new import features.</p>
2589 <p> The first things to check (or ask your host provider to check) are the
2590 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2591 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2592 All of these three settings limit the maximum size of data that can be
2593 submitted and handled by PHP. One user also said that post_max_size
2594 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2596 There exist several workarounds if your upload is too big or your
2597 hosting provider is unwilling to change the settings:</p>
2600 feature. This allows one to
2601 upload a file to the server via scp, ftp, or your favorite file transfer
2602 method. PhpMyAdmin is then able to import the files from the temporary
2604 section</a> of this document.</li>
2606 BigDump</a>) to split the files before uploading. We cannot support this
2607 or any third party applications, but are aware of users having success
2608 with it.</li>
2609 <li>If you have shell (command line) access, use MySQL to import the files
2610 directly. You can do this by issuing the "source" command from
2611 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2612 </ul>
2616 support?</a></h4>
2618 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2619 fully supported. phpMyAdmin may connect to your MySQL server
2620 using PHP's classic
2623 is available in php 5.0.<br />
2624 Either way, the developers of both extensions recommend to use the classic
2625 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2626 When compiling php, we strongly recommend that you manually link the MySQL
2627 extension of your choice to a MySQL client library of at least the same
2628 minor version since the one that is bundled with some PHP distributions is
2631 If your webserver is running on a windows system, you might want to try
2632 MySQL's
2634 instead of the MySQL / MySQLi extensions that are bundled with the official
2635 php Win32 builds.</p>
2639 message, "Client does not support authentication protocol requested
2640 by server; consider upgrading MySQL client"</a></h5>
2642 <p> You tried to access MySQL with an old MySQL client library. The version of
2643 your MySQL client library can be checked in your phpinfo() output.
2644 In general, it should have at least the same minor version as your server
2648 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2649 changed the authentication hash and your PHP is trying to use the old method.
2651 with the proper client library to match your MySQL installation. Your
2652 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2653 More information (and several workarounds) are located in the
2655 </p>
2659 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2660 capital letter in its name it is changed to lowercase as it should. But
2661 if I try to DROP this table MySQL is unable to find the corresponding
2662 file.</a></h4>
2664 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2665 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2666 directive.</p>
2670 script seems not to know the font face I'm using!</a></h4>
2672 <p> The "FPDF" library we're using for this feature requires some
2673 special files to use font faces.<br />
2675 these files.</p>
2679 check PHP Configuration".</a></h4>
2681 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2682 "MySQL extension". This extension may be part of the PHP
2683 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2684 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2685 to load the extension but failed.<br /><br />
2687 Usually, the problem is solved by installing a software package called
2688 "PHP-MySQL" or something similar.</p>
2693 and I cannot log in using cookie auth.</a></h4>
2695 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2699 so I cannot upload.</a></h4>
2701 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2702 parameter is not set to "on".</p>
2706 a new table the table and field names are changed to lowercase!</a></h4>
2708 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2709 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2710 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2711 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2712 directory and add the following line to the group [mysqld]:</p>
2714 <pre>set-variable = lower_case_table_names=0</pre>
2716 <p> Next, save the file and restart the MySQL service. You can always check the
2717 value of this directive using the query</p>
2719 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2723 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2726 </p>
2730 and I get problems, such as undefined variables when I run a
2733 <p> A tip from Jose Fandos: put a comment on the following two lines
2734 in httpd.conf, like this:</p>
2736 <pre>
2737 # mod_gzip_item_include file \.php$
2739 </pre>
2741 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2742 PHP scripts. Of course you have to restart Apache.</p>
2747 I get the error "No input file specified" when trying to
2748 run phpMyAdmin.</a></h4>
2750 <p> This is a permission problem. Right-click on the phpmyadmin folder
2751 and choose properties. Under the tab Security, click on "Add"
2752 and select the user "IUSR_machine" from the list. Now set his
2753 permissions and it should work.</p>
2757 db_structure.php with plenty of tables).</a></h4>
2760 GZIP output buffering is enabled. If you turn off it (by
2762 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2763 PHP 5.0.0.</p>
2767 message 'Errorcode: 13'. What does this mean?</a></h4>
2769 <p> This can happen due to a MySQL bug when having database / table names with
2770 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2771 To fix this, turn off this directive, convert all database and table names
2772 to lower case and turn it on again. Alternatively, there's a bug-fix
2773 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2777 and the fields are duplicated.</a></h4>
2779 <p> It is possible to configure Apache in such a way that PHP has problems
2780 interpreting .php files.</p>
2782 <p> The problems occur when two different (and conflicting) set of directives
2783 are used:</p>
2785 <pre>
2786 SetOutputFilter PHP
2787 SetInputFilter PHP
2788 </pre>
2790 <p> and</p>
2792 <pre>AddType application/x-httpd-php .php</pre>
2794 <p> In the case we saw, one set of directives was in
2795 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2796 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2797 The recommended way is with <tt>AddType</tt>, so just comment out
2798 the first set of lines and restart Apache:</p>
2800 <pre>
2801 #SetOutputFilter PHP
2802 #SetInputFilter PHP
2803 </pre>
2808 <p> This problem is known to happen when the server is running Turck MMCache
2809 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2814 <p> Yes.<br />
2815 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2816 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2817 <tt>error_reporting</tt> settings.
2818 </p>
2821 <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>
2823 <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>
2826 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2827 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2828 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2829 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2830 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2831 enabled.) Click <tt>OK</tt>.</li>
2832 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2833 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2834 </ol>
2838 PHP 5.0.4 on 64-bit systems?</a></h4>
2840 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2841 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2847 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
2848 the order of the server paragraph in <tt>config.inc.php</tt>.
2849 Table and script parts are optional. If you want
2850 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2851 some configuration. Following lines apply only for <a
2853 that you have enabled some features within global configuration. You need
2854 <code>Options FollowSymLinks</code> and <code>AllowOverride
2855 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2856 you need mod_rewrite to be enabled. Then you just need to create following
2857 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2858 (don't forget to change directory name inside of it):</p>
2860 <pre>
2861 RewriteEngine On
2862 RewriteBase /path_to_phpMyAdmin
2863 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2864 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2865 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2866 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2867 </pre>
2870 <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>
2872 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2873 following rewrite rule:</p>
2875 <pre>
2876 RewriteEngine On
2877 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2878 </pre>
2882 </h4>
2883 <p>
2884 There can be many explanations to this and a look at your server's
2885 error log file might give a clue.
2886 </p>
2890 password encryption in cookie auth doesn't work.</a></h4>
2892 <p> If your cluster consist of different architectures, PHP code used for
2893 encryption/decryption won't work correct. This is caused by use of
2894 pack/unpack functions in code. Only solution is to use mcrypt extension
2895 which works fine in this case.</p>
2900 <p> Yes but the default configuration values of Suhosin are known to cause
2901 problems with some operations, for example editing a table with many
2902 columns and no primary key. Tuning information is available at
2904 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2905 although the parameter names have changed (<tt>suhosin</tt> instead
2907 <tt>SuhosinDisableWarning</tt> directive</a>.
2908 </p>
2912 but then my connection is redirected back to http. What can cause this
2913 behavior?</a></h4>
2915 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
2916 in your Apache configuration. See <a href="http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions">http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions</a>.</p>
2919 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
2921 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
2922 Example from the Apache 2.2 documentation:</p>
2923 <pre>
2924 ProxyPass /mirror/foo/ http://backend.example.com/
2925 ProxyPassReverse /mirror/foo/ http://backend.example.com/
2926 ProxyPassReverseCookieDomain backend.example.com public.example.com
2927 ProxyPassReverseCookiePath / /mirror/foo/
2928 </pre>
2930 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
2931 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
2932 This is not specific to phpmyadmin, it's just the behavior of Apache.
2933 </p>
2935 <pre>
2936 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
2937 ProxyPassReverse /mirror/foo/
2938 http://backend.example.com/%7Euser/phpmyadmin
2939 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
2940 </pre>
2942 <p>See <a href="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html">http://httpd.apache.org/docs/2.2/mod/mod_proxy.html</a>
2943 for more details.</p>
2947 privileges, I get an error about an unknown column.</a></h4>
2949 <p> The MySQL server's privilege tables are not up to date, you need to run
2950 the <tt>mysql_upgrade</tt> command on the server.</p>
2956 headers already sent by ..." is displayed, what's the problem?</a></h4>
2958 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2959 (I.E. no blank lines, no spaces, no characters...) neither before the
2960 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2961 tag at the end. We also got a report from a user under IIS, that used
2962 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2963 contained an end-of-line character (hex 0A) at the end; removing this character
2964 cleared his errors.</p>
2969 <p> Either there is an error with your PHP setup or your username/password is
2970 wrong. Try to make a small script which uses mysql_connect and see if it
2971 works. If it doesn't, it may be you haven't even compiled MySQL support
2972 into PHP.</p>
2976 connect to local MySQL server through socket '/tmp/mysql.sock'
2977 (111) ..." is displayed. What can I do?</a></h4>
2979 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2981 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2982 In your <i>php.ini</i> you will find a line</p>
2984 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2986 <p> change it to</p>
2988 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2990 <p> Then restart apache and it will work.</p>
2992 <p> Here is a fix suggested by Brad Ummer:</p>
2994 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2995 To do this, telnet to your server and go to the MySQL bin directory. In
2996 this directory there should be a file named <i>mysqladmin</i>. Type
2997 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2998 info about your MySQL server, including the socket
2999 (<i>/tmp/mysql.sock</i>, for example).</li>
3000 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3001 phpMyAdmin, you need to complete the socket information in the
3002 <i>config.inc.php</i>.<br />
3003 For example:
3005 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3006 <br /><br />
3008 Please also make sure that the permissions of this file allow to be readable
3009 by your webserver (i.e. '0755').</li>
3010 </ul>
3012 <p> Have also a look at the
3014 corresponding section of the MySQL documentation</a>.</p>
3018 what can I do?</a></h4>
3021 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3022 sometime.<br />
3023 Also have a look at your PHP version number: if it contains "4.0b..."
3024 it means you're running a beta version of PHP. That's not a so good idea,
3025 please upgrade to a plain revision.</p>
3029 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3030 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3032 <p> Check the value you set for the
3034 directive in the phpMyAdmin configuration file.</p>
3038 password: YES)"-error when trying to access a MySQL-Server on a
3039 host which is port-forwarded for my localhost.</a></h4>
3041 <p> When you are using a port on your localhost, which you redirect via
3042 port-forwarding to another host, MySQL is not resolving the localhost
3043 as expected.<br />
3044 Erik Wasser explains: The solution is: if your host is "localhost"
3045 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3046 connection for speeding up things. And that doesn't work in this configuration
3047 with port forwarding.<br />
3053 <p> Themes are configured with
3057 <br />
3059 should not delete the directory "original" or its underlying
3060 structure, because this is the system theme used by phpMyAdmin.
3061 "original" contains all images and styles, for backwards
3062 compatibility and for all themes that would not include images or css-files.
3063 <br /><br />
3066 is enabled, you can select your favorite theme on the main page. Your
3067 selected theme will be stored in a cookie.<br /><br /></p>
3069 <p> To create a theme:</p>
3071 <ul><li>make a new subdirectory (for example "your_theme_name") under
3073 (by default <tt>themes</tt>)</li>
3074 <li>copy the files and directories from "original" to
3075 "your_theme_name"</li>
3076 <li>edit the css-files in "your_theme_name/css"</li>
3077 <li>put your new images in "your_theme_name/img"</li>
3078 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3079 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3080 contain your chosen theme name, that will be visible in user interface</li>
3081 <li>make a new screenshot of your theme and save it under
3082 "your_theme_name/screen.png"</li>
3083 </ul>
3085 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3086 theme verbose name, theme generation and theme version. These versions and
3087 generations are enumerated from 1 and do not have any direct dependence on
3088 phpMyAdmin version. Themes within same generation should be backwards
3089 compatible - theme with version 2 should work in phpMyAdmin requiring
3090 version 1. Themes with different generation are incompatible.</p>
3092 <p> If you do not want to use your own symbols and buttons, remove the
3093 directory "img" in "your_theme_name". phpMyAdmin will
3094 use the default icons and buttons (from the system-theme "original").
3095 </p>
3099 what can I do?</a></h4>
3101 <p> Here are a few points to check:</p>
3103 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3105 directive empty. See also
3107 </li>
3108 <li>Maybe you have a broken PHP installation or you need to upgrade
3109 your Zend Optimizer. See
3111 http://bugs.php.net/bug.php?id=31134</a>.
3112 </li>
3113 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3114 set to the default (200) or another low value, you could get this
3115 error if your table has a high number of columns. Adjust this setting
3116 accordingly. (Thanks to Klaus Dorninger for the hint).
3117 </li>
3118 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3119 of ";" will cause this error. Replace it with "&;".
3120 </li>
3122 you might want to increase
3124 </li>
3125 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3126 </li>
3127 </ul>
3134 who logged out can not log in again in with the same nick.</a></h4>
3136 <p> This is related to the authentication mechanism (protocol) used by
3137 phpMyAdmin. To bypass this problem: just close all the opened
3138 browser windows and then go back to phpMyAdmin. You should be able to
3139 log in again.</p>
3143 limit error or a time limit error.</a></h4>
3145 <p> Compressed dumps are built in memory and because of this are limited to
3146 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3147 using
3149 (enabled by default). Zip exports can not be handled this way, so if you need
3150 Zip files for larger dump, you have to use another way.</p>
3154 or alter a table.</a></h4>
3156 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3160 bundled with the MySQL server distribution.</a></h4>
3162 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3164 <pre>
3165 -- MySQL dump 8.22
3166 --
3167 -- Host: localhost Database: database
3168 ---------------------------------------------------------
3169 -- Server version 3.23.54
3170 </pre>
3172 <p> The invalid part of the code is the horizontal line made of dashes that
3173 appears once in every dump created with mysqldump. If you want to run your
3174 dump you have to turn it into valid MySQL. This means, you have to add a
3175 whitespace after the first two dashes of the line or add a # before it:
3176 <br />
3177 <code>
3178 -- -------------------------------------------------------<br />
3179 </code>
3180 or<br />
3181 <code>
3182 #---------------------------------------------------------
3183 </code>
3184 </p>
3191 <p> Please note that you should not use the separating string multiple times
3192 without any characters between them, or at the beginning/end of your table
3193 name. If you have to, think about using another TableSeparator or disabling
3194 that feature</p>
3199 <p> In Relation view, being able to choose a table in another database,
3200 or having more than one index field in the foreign key.<br /><br/>
3201 In Query-by-example (Query), automatic generation of the query
3202 LEFT JOIN from the foreign table.<br /><br/>
3203 </p>
3207 I get series of errors like "Warning: unable to parse url". How
3208 can this be fixed?</a></h4>
3209 <p>
3210 Your table neither have a primary key nor an unique one, so we must use a
3211 long expression to identify this row. This causes problems to parse_url
3212 function. The workaround is to create a primary or unique key.
3213 <br />
3214 </p>
3218 a MIME-Transformation onto!</a></h4>
3220 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3221 nested forms can be put inside the table where phpMyAdmin displays the results.
3222 You can, however, use any form inside of a table if keep the parent
3223 form-container with the target to tbl_row_delete.php and just put your own
3224 input-elements inside. If you use a custom submit input field, the form will
3225 submit itself to the displaying page again, where you can validate the
3226 $HTTP_POST_VARS in a transformation.
3228 For a tutorial on how to effectively use transformations, see our
3230 on the official phpMyAdmin-homepage.</p>
3234 MySQL server</a></h4>
3236 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3239 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3240 the quote-character (") is interpreted as an identifier quote character and
3241 not as a string quote character, which makes many internal phpMyAdmin
3243 statements. There is no workaround to this behaviour. News to this item will
3244 be posted in Bug report
3245 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3246 </p>
3250 more that one column with the same value
3251 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3252 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3254 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3255 can use it for the Edit and Delete links.</p>
3260 <p> phpMyAdmin uses a quick method to get the row count, and this method
3261 only returns an approximate count in the case of InnoDB tables. See
3263 a way to modify those results, but
3264 this could have a serious impact on performance.</p>
3269 <p> The number of records in queries containing COUNT and GROUP BY is
3270 not correctly calculated. Also, sorting results of a query like
3275 containing an hyphen.
3276 </a></h4>
3277 <p>
3278 The tests I have made with current MySQL 4.1.11 API shows that the
3279 API does not accept this syntax for the USE command. Enclosing the
3280 db name with backquotes works. For further confusion, no backquotes
3281 are needed with command-line mysql.
3282 </p>
3285 <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>
3286 <p>
3287 This has been a known limitation of phpMyAdmin since the beginning and
3288 it's not likely to be solved in the future.
3289 </p>
3291 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3294 <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
3295 need to install it for each customer.
3296 </a></h4>
3297 <p>
3298 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3299 your users. The development of this feature was kindly sponsored by
3300 NetCologne GmbH.
3301 This requires a properly setup MySQL user management and phpMyAdmin
3302 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3304 </p>
3308 access.
3309 </a></h4>
3310 <p>
3311 This depends on your system.<br />
3312 If you're running a server which cannot be accessed by other people, it's
3313 sufficient to use the directory protection bundled with your webserver
3315 If other people have telnet access to your server, you should use
3316 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3317 <br /><br />
3318 Suggestions:
3319 </p>
3320 <ul>
3321 <li>
3323 </li>
3324 <li>
3325 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3326 is a user whose password is only known to you, and apache is the
3327 group under which Apache runs.
3328 </li>
3329 <li>
3330 You should use PHP safe mode, to protect from other users that try
3332 </li>
3333 </ul>
3338 </a></h4>
3339 <p>
3344 </p>
3347 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3348 authentication.
3349 </a></h4>
3353 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3354 and/or
3356 are wrong.</li>
3358 <li>You have already setup a security mechanism for the
3359 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3360 phpMyAdmin's authentication, so remove it.</li>
3361 </ul>
3368 and put the privileges you want. For example,
3370 would let a user create/manage his/her database(s).</p>
3375 <p> If you have existing rules from an old .htaccess file, you can take them
3378 be a major benefit here if your installation is suited to using it. Then
3379 you can just add those updated lines into the
3383 <p> If you want a pre-made sample, you can try this fragment. It stops the
3384 'root' user from logging in from any networks other than the private
3387 <pre>
3388 //block root from logging in except from the private networks
3389 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3390 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3391 'deny root from all',
3392 'allow root from localhost',
3396 );
3397 </pre>
3402 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3403 different than the one set in your
3405 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3406 while a domain name is defined in the config file.</p>
3411 <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>
3417 when trying to create a table with more than 14 fields.
3418 </a></h4>
3419 <p>
3420 We could reproduce this problem only under Win98/98SE. Testing under
3421 WinNT4 or Win2K, we could easily create more than 60 fields.
3422 <br />
3423 A workaround is to create a smaller number of fields, then come back to
3424 your table properties and add the other fields.
3425 </p>
3429 <p>
3430 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3431 with each script/website that use forms.<br />
3432 Upgrade or downgrade your Xitami server.
3433 </p>
3436 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3437 <p>
3438 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3439 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3440 don't seem to work.<br />
3442 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3443 the user's temporary directory, so they must be moved before closing
3444 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3447 </p>
3451 Explorer never stores the cookies.
3452 </a></h4>
3453 <p>
3454 MS Internet Explorer seems to be really buggy about cookies, at least till
3456 in this area!
3457 <br />
3458 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3459 work!
3460 </p>
3464 rows.
3465 </a></h4>
3466 <p>
3468 </p>
3471 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3472 when trying to modify a row in a table with many fields, or with a text field
3473 </a></h4>
3474 <p>
3475 Your table neither have a primary key nor an unique one, so we must use a
3476 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
3477 those browsers, and this not happen in Netscape, for example. The
3478 workaround is to create a primary or unique key, or use another browser.
3479 <br />
3480 </p>
3484 page.
3485 </a></h4>
3486 <p>
3487 Some browsers support right-clicking into the frame you want to refresh,
3488 just do this in the right frame.<br />
3489 </p>
3493 query box.
3494 </a></h4>
3495 <p>
3496 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3497 Mozilla versions.<br />
3498 </p>
3502 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3503 </a></h4>
3504 <p>
3505 This is a Mozilla bug (see bug #26882 at
3507 </p>
3512 </a></h4>
3513 <p>
3514 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3515 data in octet-stream mode. Since we can't detect the specific Netscape
3516 version, we cannot workaround this bug.
3517 </p>
3521 wrong.</a></h4>
3523 <p> Please ensure that you have set your browser's character set to the one of the
3524 language file you have selected on phpMyAdmin's start page.
3525 Alternatively, you can try the auto detection mode that is supported by the
3526 recent versions of the most browsers.</p>
3529 <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
3532 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3533 Netscape and Mozilla do not have this problem.</p>
3536 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3537 I cannot manage two servers: I log in to the first one, then the other one,
3538 but if I switch back to the first, I have to log in on each operation.</a></h4>
3544 but nothing happens after that, only a blank screen.</a></h4>
3555 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3560 address and you are starting
3562 containing a domain name, or the reverse situation.</li>
3563 <li>Security settings in IE and/or Microsoft Security Center are
3564 too high, thus blocking scripts execution.</li>
3565 <li>The Windows Firewall is blocking Apache and MySQL. You must
3569 </ul>
3572 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3573 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3574 installed in their Firefox is causing the problem.</p>
3581 </a></h4>
3582 <p>
3583 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3584 specifying a wrong field-type.<br />
3585 Common errors include:
3586 </p>
3587 <ul>
3590 </ul>
3591 <p>
3592 Also, look at the syntax chapter in the MySQL manual to confirm that your
3593 syntax is correct.
3594 </p>
3598 phpMyAdmin generates only one index with those two fields.
3599 </a></h4>
3600 <p>
3601 This is the way to create a multi-fields
3602 index. If you want two indexes, create the first one when creating the
3603 table, save, then display the table properties and click the Index link to
3604 create the other index.
3605 </p>
3609 <p>
3610 Since version 2.2.3, you have a checkbox for each field that can be null.
3612 field's value. Since version 2.5.5, you have to use the checkbox to get
3614 a literal NULL in the field, and not a NULL value (this works in PHP4).
3615 </p>
3620 <p> Click on a database or table name in the left frame, the properties will be
3622 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3623 statements that can be used to recreate your database/table.
3624 <br /><br />
3626 transmit the resulting dump to your station. Depending on your PHP
3627 configuration, you will see options to compress the dump. See also the
3629 configuration variable.<br /><br />
3632 this document.</p>
3637 </a></h4>
3639 <p> Click on a database name in the left frame, the properties will be
3641 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3643 the path to your dump filename, or use the Browse button. Then click Go.
3644 <br /><br />
3646 that you upgrade to take advantage of the new features.
3647 <br /><br />
3649 in this document.
3650 </p>
3655 <p> Here is an example with the tables persons, towns and countries, all
3657 table, create it as explained in the configuration section. Then create the
3658 example tables:</p>
3660 <pre>
3661 CREATE TABLE REL_countries (
3662 country_code char(1) NOT NULL default '',
3663 description varchar(10) NOT NULL default '',
3664 PRIMARY KEY (country_code)
3665 ) TYPE=MyISAM;
3667 INSERT INTO REL_countries VALUES ('C', 'Canada');
3669 CREATE TABLE REL_persons (
3670 id tinyint(4) NOT NULL auto_increment,
3671 person_name varchar(32) NOT NULL default '',
3673 country_code char(1) NOT NULL default '',
3674 PRIMARY KEY (id)
3675 ) TYPE=MyISAM;
3677 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3678 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3680 CREATE TABLE REL_towns (
3682 description varchar(30) NOT NULL default '',
3683 PRIMARY KEY (town_code)
3684 ) TYPE=MyISAM;
3686 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3687 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3688 </pre>
3694 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3698 </ul>
3706 <li>In the fields row, choose persons.person_name and click the
3708 <li>Do the same for towns.description and countries.descriptions in the
3711 the correct joins have been generated</li>
3713 </ul>
3717 <p>
3718 Starting from the previous example, create the pma_table_info as explained
3719 in the configuration section, then browse your persons table,
3720 and move the mouse over a town code or country code.
3721 <br /><br />
3722 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3723 enables: drop-down list of possible values.
3724 </p>
3727 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3728 <p>
3731 <br /><br />
3732 Then you need to think about your schema layout. Which tables will go on
3733 which pages?
3734 </p>
3735 <ul>
3741 page and click Go. If you like, you
3743 linked tables onto the new page.</li>
3744 <li>Select the name of the new page (making sure the Edit radio button
3745 is selected) and click Go.</li>
3747 Coordinates are relative; your diagram will
3748 be automatically scaled to fit the page. When initially placing tables
3749 on the page, just pick any coordinates -- say, 50x50. After clicking
3751 position the element correctly.</li>
3753 first be sure to click the Save
3754 button beneath the list of tables and coordinates, to save any changes
3755 you made there. Then scroll all the way down, select the
3757 you want, and click Go.</li>
3758 <li>Internet Explorer for Windows may suggest an incorrect filename when
3763 browsers on Windows, do not have this problem.</li>
3764 </ul>
3768 columns!</a></h4>
3770 <p> No, it's MySQL that is doing
3776 underscores in the database name?</a></h4>
3778 <p> If you do not put a backslash before the underscore, this is a wildcard
3781 john2db ...<br /><br />
3783 If you put a backslash before the underscore, it means that the database
3784 name will have a real underscore.</p>
3788 statistics pages?</a></h4>
3799 if it already exists during the import. It does NOT drop the table after
3800 your export, it only affects the import file.</li>
3802 Otherwise, you may get an error if the table name exists but has a
3803 different structure.</li>
3805 (if any) will be included in backup.</li>
3807 field and table names formed with special characters are protected.</li>
3809 types set in the pmadb in the dump as
3811 </li>
3812 </ul>
3817 command, for better documentation (but resulting file is bigger).</li>
3819 once the INSERT verb and the table name.</li>
3822 </li>
3824 more info is provided in the
3826 but basically with this selected, invalid values are adjusted and
3827 inserted rather than causing the entire statement to fail.</li>
3828 </ul>
3832 in its name.</a></h4>
3835 is the normal way to reference a database and table name. Worse, MySQL
3836 will usually let you create a database with a dot, but then you cannot
3837 work with it, nor delete it.</p>
3850 for usage.<br />
3851 On a more recent pear version, I had problems with the state of Net_DIME
3852 being beta, so this single command
3854 needed modules.<br />
3855 If you use the Validator, you should be aware that any
3857 submit will be stored anonymously (database/table/column names,
3858 strings, numbers replaced with generic values). The Mimer
3861 We utilize it as free SOAP service.</p>
3865 it, but MySQL says "BLOB column '...' used in key specification without
3868 <p> The right way to do this, is to create the field without any indexes,
3870 dialog. On this page, you will be able to choose your BLOB field, and
3871 set a size to the index, which is the condition to create an index on
3872 a BLOB field.</p>
3876 editing fields?</a></h4>
3878 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3879 with many editing fields (table structure changes, row editing, etc.)
3880 (must be enabled in configuration - see.
3882 You can also have a look at the directive
3884 ('vertical') and see if this eases up editing for you.</p>
3888 WTF is this feature then useful for?</a></h4>
3890 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3891 on them. Otherwise you could just put a comment on the field. Because entering
3892 your own mimetype will cause serious syntax checking issues and validation,
3893 this introduces a high-risk false-user-input situation. Instead you have to
3894 initialize mimetypes using functions or empty mimetype definitions.<br />
3895 Plus, you have a whole overview of available mimetypes. Who knows all those
3896 mimetypes by heart so he/she can enter it at will?</p>
3900 can't I see any bookmarks below the query box? What is this variable for?
3901 </a></h4>
3903 <p> Any query you have executed can be stored as a bookmark on the page where the
3904 results are displayed. You will find a button labeled 'Bookmark this query'
3905 just at the end of the page.<br />
3906 As soon as you have stored a bookmark, it is related to the database you run
3907 the query on. You can now access a bookmark dropdown on each page, the query
3908 box appears on for that database.<br /><br />
3910 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3914 aware of that you HAVE to create a valid query, otherwise your query won't be
3915 even able to be stored in the database.<br />
3917 for your query will remain the way it is, but will be stripped of the /**/
3918 chars. So you can use:<br /><br />
3922 which will be expanded to<br /><br />
3926 in your query, where VARIABLE is the string you entered in the input box. If
3927 an empty string is provided, no replacements are made.<br /><br />
3929 A more complex example. Say you have stored this query:<br /><br />
3931 <br /><br />
3934 the full query will be:<br /><br />
3937 <br /><br />
3941 spaces inserted there
3942 will be later also inserted as spaces in your query and may lead to unexpected
3943 results especially when
3945 Your initial query which is going to be stored as a bookmark has to yield at
3946 least one result row so
3947 you can store the bookmark. You may have that to work around using well
3951 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3952 include exported table?</a></h4>
3954 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3955 document should look like following one (assuming you have table
3958 <pre>
3959 \documentclass{article} % or any class you want
3960 \usepackage{longtable} % for displaying table
3961 \begin{document} % start of document
3962 \include{table} % including exported table
3963 \end{document} % end of document
3964 </pre>
3968 access them.
3969 </a></h4>
3972 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3973 enable users to see all the database names.
3976 So if your users do not need those privileges, you can remove them and their
3977 databases list will shorten.</p>
3981 possible values for a field, based on some foreign table?</a></h4>
3983 <p> You have to setup appropriate links between the tables, and also
3987 foreign table, a drop-down list of values will be available.
3988 You will see two lists of values, the first list containing the key
3989 and the display field, the second list containing the display field
3990 and the key. The reason for this is to be able to type the first
3991 letter of either the key or the display field.<br /><br />
3993 For 100 values or more, a distinct window will appear, to browse foreign
3994 key values and choose one. To change the default limit of 100, see
3995 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
3999 automatically when entering Browse mode for a table?</a></h4>
4001 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4002 </p>
4006 Excel files, how can I enable that?</a></h4>
4008 <p> Current version does support direct export to Microsoft Excel and Word
4009 versions 2000 and newer. If you need export older versions, you can use
4011 which works out of the box or you can
4013 several problems, most important are limitation of cell content to 255
4014 chars and no support for charsets, so think carefully whether you want to
4015 enable this.</b>. For enabling this you need to set
4019 module Spreadsheet_Excel_Writer into php include path. The
4020 installation can be done by following command:</p>
4022 <pre>
4023 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
4024 </pre>
4026 <p> First part of switches set we want to install beta version of that module
4027 (no stable version available yet) and then we tell pear we want to satisfy
4028 dependencies.</p>
4030 <p> If you are running in PHP safe mode, you will have to set
4033 modules are located, for example:</p>
4035 <pre>
4036 safe_mode_include_dir = /usr/local/lib/php
4037 </pre>
4041 <pre>
4042 cd phpMyAdmin
4043 mkdir tmp
4044 chmod o+rwx tmp
4045 </pre>
4049 what happens to my column comments stored in pmadb?</a></h4>
4051 <p> Automatic migration of a table's pmadb-style column comments to the native
4052 ones is done whenever you enter Structure page for this table.</p>
4057 <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 />
4058 <ol>
4059 <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>
4060 <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>
4061 <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>
4062 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4063 <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>
4064 <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>
4065 </ol>
4066 </p>
4073 <p> Our Bug Tracker is located at
4075 under the Bugs section.<br /><br />
4077 But please first discuss your bug with other users:<br />
4083 existing language, where do I start?</a></h4>
4085 <p> Always use the current SVN version of your language file.
4087 don't know how to get the SVN version, please ask one of the developers.
4088 <br />
4089 Please note that we try not to use HTML entities like &eacute; in
4090 the translations, since we define the right character set in the file.
4091 With HTML entities, the text on JavaScript messages would not
4092 display correctly.
4093 However there are some entities that need to be there, for quotes
4094 ,non-breakable spaces, ampersands, less than, greater than.<br />
4095 You can then put your translations, as a zip file to avoid losing special
4096 characters, on the sourceforge.net translation tracker.<br />
4097 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4098 list, because this is where we ask for translations of new messages.</p>
4102 phpMyAdmin. How should I proceed?</a></h4>
4107 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4108 </li>
4110 <li>generate patch with your changes:
4112 </li>
4115 tracker of the phpMyAdmin project</a>.
4116 </li>
4117 </ol>
4119 <p> Write access to the SVN tree is granted only to experienced developers who
4120 have already contributed something useful to phpMyAdmin.<br />
4126 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4128 <p> Please refer to
4129 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4130 </p>
4132 <!-- DEVELOPERS -->
4135 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4136 great features have been written by other people and you too can help to
4137 make phpMyAdmin a useful tool.</p>
4139 <p> If you're planning to contribute source, please read the following
4140 information:</p>
4146 it free from other code.<br />
4147 Commonly used functions should be added to
4150 <li>Obviously, you're free to use whatever coding style you want. But
4151 please try to keep your code as simple as possible: beginners are
4152 using phpMyAdmin as an example application.<br />
4153 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4154 compliant on one hand, they fit the
4157 coding standards</a>
4158 on the other hand. Please pay attention to this.</li>
4159 <li>Please try to keep up the file-naming conventions. Table-related stuff
4162 <li>Please don't put message strings in your code, instead add the string
4167 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4168 better debug and profile their code.<br />
4169 Please see the
4171 options for more information.<br />
4172 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4173 lost during its re-entry into Earth's atmosphere and in memory of the
4174 brave men and women who gave their lives for the people of Earth.</li>
4175 </ul>
4177 <!-- CREDITS -->
4180 <pre>
4181 phpMyAdmin - Credits
4182 ====================
4184 CREDITS, in chronological order
4185 -------------------------------
4188 * creator of the phpmyadmin project
4192 * multi-language version
4193 * various fixes and improvements
4195 * current project maintainer
4198 * started SourceForge phpMyAdmin project in March 2001
4199 * sync'ed different existing CVS trees with new features and bugfixes
4200 * multi-language improvements, dynamic language selection
4201 * current project maintainer
4202 * many bugfixes and improvements
4205 * rewrote and optimized javascript, DHTML and DOM stuff
4206 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4207 generate XHTML1.0 and CSS2 compliant codes
4208 * improved the language detection system
4209 * many bugfixes and improvements
4212 * database maintenance controls
4213 * table type code
4215 * DB-based configuration (Not completed)
4218 * many bugfixes and improvements
4221 * bookmarks feature
4222 * multiple dump feature
4223 * gzip dump feature
4224 * zip dump feature
4227 * various fixes
4228 * moderator of the phpMyAdmin former users forum at phpwizard.net
4234 * rewrote and fix dump code
4235 * bugfixes
4238 * rewrote dump code for PHP4
4239 * mySQL table statistics
4240 * bugfixes
4243 * main author of the version 2.1.0.1
4244 * bugfixes
4248 * abstract database interface (PMA_DBI) with MySQLi support
4249 * privileges administration
4251 * various features and fixes
4252 * German language file updates
4255 * automatic joins in QBE
4256 * links column in printview
4257 * Relation view
4260 * enhanced index creation/display feature
4261 * feature to use a different charset for HTML than for MySQL
4262 * improvements of export feature
4263 * various features and fixes
4264 * Czech language file updates
4267 (http://sf.net/projects/phpmysqlformgen/)
4268 * suggested the patch for multiple table printviews
4271 * built the patch for vertical display of table rows
4272 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4273 * Improvement of column/db comments
4274 * (MIME)-Transformations for columns
4275 * Use custom alias names for Databases in left frame
4276 * hierarchical/nested table display
4277 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4278 * new icon sets
4279 * vertical display of column properties page
4280 * some bugfixes, features, support, German language additions
4283 * japanese kanji encoding conversion feature
4286 * the Cookie authentication mode
4289 * table relation-links feature
4292 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4293 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4294 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4300 * phpMyAdmin logo (until June 2004)
4303 * blowfish library from the Horde project
4306 * mysqli support
4307 * many bugfixes and improvements
4310 * redesign for 2.6.0
4311 * phpMyAdmin sailboat logo (June 2004)
4314 * Representation at conferences
4317 * interface improvements
4318 * various bugfixes
4320 - Ivan A Kirillov
4321 * new relations Designer
4323 - Raj Kissu Rajandran (Google Summer of Code 2008)
4324 * BLOBstreaming support
4326 - Piotr Przybylski (Google Summer of Code 2008)
4327 * improved setup script
4329 And also to the following people who have contributed minor changes,
4330 enhancements, bugfixes or support for a new language since version 2.1.0:
4332 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4333 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4334 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4335 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4337 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4338 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4339 Luís V., Martijn W. van der Lee,
4340 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4344 Original Credits of Version 2.1.0
4345 ---------------------------------
4347 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4348 to create a web-based interface to MySQL using PHP3. Although I have not
4349 used any of his source-code, there are some concepts I've borrowed from
4350 him. phpMyAdmin was created because Peter told me he wasn't going to
4351 further develop his (great) tool.
4352 Thanks go to
4354 code for the check when dropping a table or database. He also suggested
4355 that you should be able to specify the primary key on tbl_create.php3. To
4356 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4357 well as a bug-report. Plus many smaller improvements.
4359 were introduced in 1.3.0 (including quite significant ones like the
4360 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4361 bug-fixes and help.
4363 language-independent by outsourcing the strings to a separate file. He
4364 also contributed the French translation.
4366 tbl_select.php3, a feature to display only some fields from a table.
4368 functions in tbl_change.php3. He also added the
4371 servers and is a regular contributor for bug-fixes.
4373 features for 2.0.6.
4374 The following people have contributed minor changes, enhancements, bugfixes
4375 or support for a new language:
4376 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4377 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4378 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4379 G. Wieggers.
4381 And thanks to everyone else who sent me email with suggestions, bug-reports
4382 and or just some feedback.
4383 </pre>
4389 <ul>
4391 - the default name of Apache's directory-level configuration file.</li>
4395 - a software application that enables a user to display and interact with
4396 text, images, and other information typically located on a web page at a
4397 website on the World Wide Web.</li>
4399 - a free software/open source data compression algorithm and program
4400 developed by Julian Seward.</li>
4402 - an important World Wide Web technology that enables a client web browser
4403 to request data from a program executed on the Web server.</li>
4405 - a log or record of changes made to a project.</li>
4407 - a computer system that accesses a (remote) service on another computer
4408 by some kind of network.</li>
4410 - a set of data values of a particular simple type, one for each row of
4411 the table.</li>
4413 - a packet of information sent by a server to a World Wide Web browser
4414 and then sent back by the browser each time it accesses that server.</li>
4416 - Comma-separated values</li>
4419 - an organized collection of data.</li>
4422 - a PHP module that extends PHP with additional functionality.</li>
4424 - a list of commonly asked question and there answers.</li>
4426 - one part of divided data/columns.</li>
4428 - a field or group of fields in a database record that point to a key
4429 field or group of fields forming a key of another database record in some
4430 (usually different) table.</li>
4432 - the free PDF library</li>
4434 GD Graphics Library</a> - a library by Thomas Boutell and others for
4435 dynamically manipulating images.</li>
4438 - gzip is short for GNU zip, a GNU free software file compression
4439 program.</li>
4441 - any machine connected to a computer network, a node that has a hostname.</li>
4443 - the unique name by which a network attached device is known on a network.</li>
4445 (HyperText Transfer Protocol)</a>
4446 - the primary method used to transfer or convey information on the World
4447 Wide Web.</li>
4450 additional security measures.</li>
4451 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4452 - a set of Internet-based services for servers using Microsoft Windows.</li>
4454 - a feature that allows quick access to the rows in a table.</li>
4456 - a data-oriented protocol used by source and destination hosts for
4457 communicating data across a packet-switched internetwork.</li>
4459 - a unique number that devices use in order to identify and communicate
4460 with each other on a network utilizing the Internet Protocol standard.</li>
4462 (Internet Server Application Programming Interface)</a>
4463 - the API of Internet Information Services (IIS).</li>
4465 - a business or organization that offers users access to the Internet and related services.</li>
4467 - a most commonly used standard method of lossy compression for
4468 photographic images.</li>
4474 - line of personal computers is designed, developed, manufactured, and
4475 marketed by Apple Computer.</li>
4476 <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>
4477 - the operating system which is included with all currently shipping Apple
4478 Macintosh computers in the consumer and professional markets.</li>
4480 - a cryptographic library.</li>
4482 - the MCrypt PHP extension.</li>
4483 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4484 - an Internet Standard for the format of e-mail.</li>
4486 - some sort of extension for the Apache Webserver.</li>
4488 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4489 Management System (DBMS).</li>
4491 - the improved MySQL client PHP extension.</li>
4493 - the MySQL client PHP extension.</li>
4495 - open standard for office documents.</li>
4496 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4497 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4499 (Portable Document Format)</a>
4500 - a file format developed by Adobe Systems for representing two
4501 dimensional documents in a device independent and resolution independent
4502 format.</li>
4504 - the PHP Extension and Application Repository.</li>
4506 - the perl-compatible regular expression functions for PHP</li>
4508 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4509 programming language used mainly for developing server-side applications
4510 and dynamic web content, and more recently, a broader range of software
4511 applications.</li>
4513 - a connection through which data is sent and received.</li>
4515 - Request for Comments (RFC) documents are a series of memoranda
4516 encompassing new research, innovations, and methodologies applicable to
4517 Internet technologies.</li>
4521 - represents a single, implicitly structured data item in a table.</li>
4523 - a computer system that provides services to other computing
4524 systems over a network.</li>
4525 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4526 - handlers for different table types</li>
4528 - a form of inter-process communication.</li>
4530 Sockets Layer)</a>
4531 - a cryptographic protocol which provides secure communication on the Internet.</li>
4533 - Structured Query Language</li>
4535 - a set of data elements (cells) that is organized, defined and stored as
4536 horizontal rows and vertical columns where each item can be uniquely
4537 identified by a label or key or by it?s position in relation to other items.</li>
4540 - a type of archive file format: the Tape ARchive format.</li>
4542 - one of the core protocols of the Internet protocol suite.</li>
4546 - a sequence of characters, conforming to a standardized format, that is
4547 used for referring to resources, such as documents and images on the
4548 Internet, by their location.</li>
4550 - A computer (program) that is responsible for accepting HTTP requests
4551 from clients and serving them Web pages.</li>
4553 - a W3C-recommended general-purpose markup language for creating
4554 special-purpose markup languages, capable of describing many different
4555 kinds of data.</li>
4557 - a popular data compression and archival format.</li>
4559 - an open-source, cross-platform data compression library by Jean-loup
4560 Gailly and Mark Adler.</li>
4561 </ul>
4571 </body>
4572 </html>