| blob | 8155183517a73e4f8b82352d02d7496aff80c464 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.2.3
22 Documentation
23 </h1>
24 </div>
26 <!-- TOP MENU -->
41 </ul>
46 phpMyAdmin homepage</a></li>
48 SourceForge phpMyAdmin project page</a></li>
50 Official phpMyAdmin wiki</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
56 <li>Documentation version:
58 </li>
59 </ul>
61 <!-- REQUIREMENTS -->
68 and the Standard PHP Library (SPL) extension.
69 </li>
72 currently default), you should install mbstring and ctype
73 extensions.
74 </li>
75 <li>You need GD2 support in PHP to display inline
77 original aspect ratio</li>
83 load pages significantly slower.
84 </li>
85 </ul>
86 </li>
89 </ul>
91 <!-- INTRODUCTION -->
94 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
95 a single database. To accomplish the latter you'll need a properly set up
96 MySQL user who can read/write only the desired database. It's up to you to
97 look up the appropriate part in the MySQL manual.
98 </p>
103 <li>create, copy, drop, rename and alter databases, tables, fields and
104 indexes</li>
105 <li>maintenance server, databases and tables, with proposals on server
106 configuration</li>
107 <li>execute, edit and bookmark any
109 batch-queries</li>
112 </li>
119 OpenDocument Text and Spreadsheet,
121 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
122 </li>
126 <li>using Query-by-example (QBE), create complex queries automatically
127 connecting required tables</li>
129 your Database layout</li>
131 <li>transform stored data into any format using a set of predefined
132 functions, like displaying BLOB-data as image or download-link
133 </li>
139 </li>
140 </ul>
143 <p> Many people have difficulty
144 understanding the concept of user management with regards to phpMyAdmin. When
145 a user logs in to phpMyAdmin, that username and password are passed directly
146 to MySQL. phpMyAdmin does no account management on its own (other than
147 allowing one to manipulate the MySQL user account information); all users
148 must be valid MySQL users.</p>
157 <!-- INSTALLATION -->
165 </ol>
168 phpMyAdmin does not apply any special security methods to the MySQL database
169 server. It is still the system administrator's job to grant permissions on
171 be used for this.
172 </p>
180 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
181 before uploading them to your server, as PHP seems not to like
186 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
187 Downloads page. Some kits contain only the English messages,
188 others contain all languages in UTF-8 format (this should be fine
189 in most situations), others contain all
190 languages and all character sets. We'll assume you chose a kit whose
192 </li>
193 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
195 document root. If you don't have direct access to your document root,
196 put the files in a directory on your local machine, and, after step 4,
197 transfer the directory on your web server using, for example, ftp.</li>
198 <li>Ensure that all the scripts have the appropriate owner (if PHP is
199 running in safe mode, having some scripts with an owner different
200 from the owner of other scripts will be a
205 <li>Now you must configure your installation. There are two methods that
206 can be used. Traditionally, users have hand-edited a copy of
208 provided for those who prefer a graphical installation. Creating a
209 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
210 <ul><li>To manually create the file, simply use your text editor to
213 file) in the main (top-level) phpMyAdmin directory (the one
217 default value is okay for a particular setting, there is no
219 few directives to get going, a simple configuration may look
220 like this:
221 <pre>
222 <?php
223 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
225 $i=0;
226 $i++;
227 $cfg['Servers'][$i]['auth_type'] = 'cookie';
228 ?>
229 </pre>
230 Or, if you prefer to not be prompted every time you log in:
231 <pre>
232 <?php
234 $i=0;
235 $i++;
236 $cfg['Servers'][$i]['user'] = 'root';
237 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
238 $cfg['Servers'][$i]['auth_type'] = 'config';
239 ?>
240 </pre>
241 For a full explanation of possible configuration values, see the
247 directory. This is a security measure. On a Linux/Unix system you
248 can use the following commands:
249 <pre>
250 cd phpMyAdmin
251 mkdir config # create directory for saving
252 chmod o+rw config # give it world writable permissions
253 </pre>
254 And to edit an existing configuration, copy it over first:
255 <pre>
256 cp config.inc.php config/ # copy current configuration for editing
257 chmod o+w config/config.inc.php # give it world writable permissions
258 </pre>
259 On other platforms, simply create the folder and ensure that your
268 the webserver does not have the proper permissions you may see the
270 config/</tt> directory exists and has the proper permissions -
272 and upload (via FTP or some similar means) to the proper location.<br /><br />
274 Once the file has been saved, it must be moved out of the <tt>
275 config/</tt> directory and the permissions must be reset, again
276 as a security measure:
277 <pre>
278 mv config/config.inc.php . # move file to current directory
279 chmod o-rw config.inc.php # remove world read and write permissions
280 rm -rf config # remove not needed directory
281 </pre>
282 Now the file is ready to be used. You can choose to review or edit
283 the file with your favorite editor, if you prefer to set some
284 advanced options which the setup script does not provide.</li></ul></li>
285 <li>If you are using the
287 protect the phpMyAdmin installation directory because using
288 config does not require a user to
289 enter a password to access the phpMyAdmin installation. Use of an alternate
290 authentication method is recommended, for example with
298 in your browser. phpMyAdmin should now display a welcome screen
299 and your databases, or a login dialog if using
301 authentication mode.</li>
304 Apache you can use supplied .htaccess file in that folder, for other
305 webservers, you should configure this yourself. Such configuration
306 prevents from possible path exposure and cross side scripting
307 vulnerabilities that might happen to be found in that code.</li>
308 <li>
309 It is generally good idea to protect public phpMyAdmin installation
310 against access by robots as they usually can not do anything good
312 your webserver or limit access by web server configuration. You can
315 </li>
316 </ol>
320 <p> For a whole set of new features (bookmarks, comments,
323 transformation, etc.) you need to create a set of special tables. Those
324 tables can be located in your own database, or in a central database for a
325 multi-user installation (this database would then be accessed by the
326 controluser, so no other user should have rights to it).</p>
336 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
337 that you may need special (administrator) privileges to create the database
338 and tables, and that the script may need some tuning, depending on the
339 database name.</p>
344 section</a>. You will also need to have a controluser with the proper rights
351 unpacked one. Configuration files from old versions may
352 require some tweaking as some options have been changed or removed; in
354 so you better remove it from your file and just use the default one.
356 statement that you might find near the end of your configuration file.</p>
360 is version-specific.</p>
363 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
364 you should run the SQL script found in
371 where you want to give users access to their own database and don't want
372 them to play around with others.<br />
373 Nevertheless be aware that MS Internet Explorer seems to be really buggy
375 in this area!<br />
378 that your user/password pair are not in clear in the configuration file.
379 </li>
382 authentication modes are more secure: the MySQL login information does
383 not need to be set in the phpMyAdmin configuration file (except possibly
385 However, keep in mind that the password travels in plain text, unless
386 you are using the HTTPS protocol.<br />
387 In cookie mode, the password is stored, encrypted with the blowfish
388 algorithm, in a temporary cookie.</li>
400 file under the
402 $cfg['Servers'][$i]['controluser']</a></tt> and
407 only an example: use something else in your file!</b> Input these
408 statements from the phpMyAdmin SQL Query window or mysql command–line
409 client.<br />
411 if it's not the same as the MySQL server's one.
413 <pre>
414 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
415 GRANT SELECT (
416 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
417 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
418 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
419 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
420 Execute_priv, Repl_slave_priv, Repl_client_priv
421 ) ON mysql.user TO 'pma'@'localhost';
422 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
423 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
424 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
425 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
427 If you want to use the many new relation and bookmark features:
429 <pre>
431 </pre>
437 on a set of particular databases. Normally you shouldn't give global
438 privileges to an ordinary user, unless you understand the impact of those
439 privileges (for example, you are creating a superuser).<br />
443 <pre>
444 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
445 </pre>
447 What the user may now do is controlled entirely by the MySQL user
448 management system.<br />
450 authentication mode, you don't need to fill the user/password fields
452 array.</li>
453 </ul>
458 method and allows you to log in as any valid MySQL user.</li>
459 <li>Is supported with most PHP configurations. For
472 mode.</li>
473 </ul>
477 <ul><li>You can use this method as a replacement for the
479 (for example, if you're running
481 <li>Obviously, the user must enable cookies in the browser, but this is
482 now a requirement for all authentication modes.</li>
483 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
484 with the same username.</li>
485 <li>If you want to log in to arbitrary server see
490 not required.</li>
491 </ul>
495 <ul><li>This mode is a convenient way of using credentials from another
496 application to authenticate to phpMyAdmin.</li>
497 <li>The other application has to store login information into
498 session data.</li>
500 section.</li>
501 </ul>
504 <ul><li>This mode is the less secure one because it requires you to fill the
506 $cfg['Servers'][$i]['user']</a> and
508 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
509 can read your config.inc.php can discover your username and password).
510 <br />
517 is an entry explaining how to protect your configuration file.</li>
518 <li>For additional security in this mode, you may wish to consider the Host
519 authentication
521 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
523 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
524 directives.</li>
525 <li>Unlike cookie and http, does not require a user to log in when first
526 loading the phpMyAdmin site. This is by design but could allow any
527 user to access your installation. Use of some restriction method is
529 HTTP-AUTH directive or disallowing incoming HTTP requests at
530 one’s router or firewall will suffice (both of which
531 are beyond the scope of this manual but easily searchable with Google).</li>
532 </ul>
534 <p>
535 The Swekey is a low cost authentication USB key that can be used in
536 web applications.<br /><br />
537 When Swekey authentication is activated, phpMyAdmin requires the
538 users's Swekey to be plugged before entering the login page (currently
539 supported for cookie authentication mode only). Swekey Authentication is
540 disabled by default.<br /><br />
542 </p>
543 <pre>
544 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
545 </pre>
546 <p>
548 each user with their Swekey Id. It is important to place this file outside
549 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
551 users' information.<br /><br />
552 If you want to purchase a Swekey please visit
554 since this link provides funding for phpMyAdmin.
555 </p>
556 <!-- CONFIGURATION -->
560 users:</span> PHP does not seem to like
564 before saving a script you have modified.</p>
569 section to create one. This file only needs to contain the parameters you want to
570 change from their corresponding default value in
573 <p> The parameters which relate to design (like colors) are placed in
576 your site specific code to be included on start and end of each page.</p>
580 (with full path) to your phpMyAdmin installation's directory.
583 some web servers are case–sensitive.
586 Starting with version 2.3.0, it is advisable to try leaving this
587 blank. In most cases phpMyAdmin automatically detects the proper
588 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
589 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
590 A good test is to browse a table, edit a row and save it. There should
591 be an error message if phpMyAdmin is having trouble auto–detecting
592 the correct value. If you get an error that this must be set or if
593 the autodetect code fails to detect your path, please post a bug
594 report on our bug tracker so we can improve the code.</dd>
598 with master / foreign – tables (see
600 <br />
601 If you tried to set this up and it does not work for you, have a look on
603 use it. You will find a link that will analyze why those features have
604 been disabled.<br />
605 If you do not want to use those features set this variable to
609 <dd>A warning is displayed on the main page if Suhosin is detected.
611 from appearing.</dd>
614 <dd>Disable the default warning that is displayed if mcrypt is missing for
615 cookie authentication.
617 from appearing.</dd>
621 domain to call phpMyAdmin inside a frame, and is a potential security
622 hole allowing cross-frame scripting attacks.</dd>
626 algorithm to encrypt the password.<br />
628 passphrase of your choice. It will be used internally by the blowfish
629 algorithm: you won’t be prompted for this passphrase. The maximum
632 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
633 makes a bit weaker security as this generated secret is stored in
634 session and furthermore it makes impossible to recall user name from
635 cookie.</dd>
639 MySQL servers. Therefore, a
641 been added which contains the login information for the different servers.
642 The first
644 contains the hostname of the first server, the second
646 the hostname of the second server, etc. In
648 server definition, however you can put as many as you need in
650 have to define all settings, just those you need to change).</dd>
654 $i-th MySQL-server. E.g. localhost.</dd>
659 ignores this port number and connects with the socket, so if you want
660 to connect to a port different from the default port, use
663 </dd>
667 To determine the correct socket, check your MySQL configuration or, using the
669 Among the resulting information displayed will be the socket used.</dd>
672 <dd>Whether to enable SSL for connection to MySQL server.
673 </dd>
676 <dd>What type connection to use with the MySQL server. Your options are
678 is nearly guaranteed to be available on all MySQL servers, while
679 sockets are not supported on some platforms.<br /><br />
681 To use the socket mode, your MySQL server must be on the same machine
682 as the Web server.</dd>
685 <dd>What php MySQL extension to use for the connection. Valid options are:
686 <br /><br />
689 The classic MySQL extension. This is the recommended and default
690 method at this time.<br /><br />
693 The improved MySQL extension. This extension became available
694 with php 5.0.0 and is the recommended way to connect to a server
698 <dd>Whether to use a compressed protocol for the MySQL server connection
699 or not (experimental).<br />
705 </dt>
707 all relational features (see
709 and, for a MySQL server previous to 4.1.2 or running with
712 authentication mode).<br /><br />
715 cookie authentication modes (or 'config'
716 authentication mode since phpMyAdmin 2.2.1), you need to supply the
721 This account is used to check what databases the user will see at
722 login.<br />
726 In phpMyAdmin versions before 2.2.5, those were called
730 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
731 <dd>Whether config or cookie or
733 should be used for this server.
735 is the plain old way: username and password are stored in
737 <li>'cookie' authentication mode
739 2.2.3 allows you to log in as any valid MySQL user with the
740 help of cookies. Username and password are stored in
741 cookies during the session and password is deleted when it
742 ends. This can also allow you to log in in arbitrary server if
743 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
744 </li>
745 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
746 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
747 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
748 <li>'signon' authentication mode
750 as introduced in 2.10.0 allows you to log in from prepared PHP
751 session data. This is useful for implementing single signon
752 from another application. Sample way how to seed session is in
758 </ul>
761 for more information.
762 </dd>
764 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
765 </dt>
766 <dd>
768 names for hardware authentication. Leave empty to deactivate this feature.
769 </dd>
773 </dt>
774 <dd>
775 When using auth_type = 'config', this is the user/password-pair
776 which phpMyAdmin will use to connect to the
777 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
778 cookie authentication is used and should be empty.</dd>
780 <span
782 </dt>
783 <dd>
784 Allow attempt to log in without password when a login with password
785 fails. This can be used together with http authentication, when
786 authentication is done some other way and phpMyAdmin gets user name
787 from auth and uses empty password for connecting to MySQL. Password
788 login is still tried first, but as fallback, no password method is
789 tried.</dd>
792 </dt>
793 <dd>
794 If set to a (an array of) database name(s), only this (these) database(s)
795 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
796 database(s) name(s) may contain MySQL wildcards characters
800 This setting is an efficient way to lower the server load since the
801 latter does not need to send MySQL requests to build the available
803 privileges rules of the MySQL database server</span>. If set, it just
804 means only these databases will be displayed but
806 <br /><br />
808 An example of using more that one database:
810 <br /><br />
812 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
813 databases in the left frame, so that you can individually arrange your databases.<br />
814 If you want to have certain databases at the top, but don't care about the others, you do not
815 need to specify all other databases. Use:
817 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
818 order.</dd>
821 </dt>
822 <dd>Regular expression for hiding some databases. This only hides them
823 from listing, but a user is still able to access them (using, for example,
824 the SQL query area). To limit access, use the MySQL privilege system.
825 <br /><br />
830 More information on regular expressions can be found in the
832 PCRE pattern syntax</a> portion of the PHP reference manual.
833 </dd>
836 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
837 this string will be displayed instead of the hostname in the pull-down
838 menu on the main page. This can be useful if you want to show only
839 certain databases on your system, for example. For HTTP auth, all
840 non-US-ASCII characters will be stripped.</dd>
844 </dt>
845 <dd>The name of the database containing the linked-tables infrastructure.
846 <br /><br />
849 section in this document to see the benefits of this infrastructure,
850 and for a quick way of creating this database and the needed tables.
851 <br /><br />
853 If you are the only user of this phpMyAdmin installation, you can
854 use your current database to store those special tables; in this
855 case, just put your current database name in
857 set this parameter to the name of your central database containing
858 the linked-tables infrastructure.</dd>
862 </dt>
864 useful for queries you often run.<br /><br />
866 To allow the usage of this functionality:
868 <li>enter the table name in
870 </ul>
871 </dd>
875 </dt>
877 which field is a key in another table (a foreign key). phpMyAdmin
878 currently uses this to
879 <ul><li>make clickable, when you browse the master table, the data values
880 that point to the foreign table;</li>
882 when browsing the master table, if you move the mouse to a column
883 containing a foreign key (use also the 'table_info' table);<br />
886 <li>in edit/insert mode, display a drop-down list of possible foreign
890 <li>display links on the table properties page, to check referential
891 integrity (display missing foreign keys) for each described key;
892 </li>
896 schema of your database (also uses the table_coords table).</li>
897 </ul>
899 The keys can be numeric or character.<br /><br />
901 To allow the usage of this functionality:
904 infrastructure</li>
905 <li>put the relation table name in
907 <li>now as normal user open phpMyAdmin and for each one of your
908 tables where you want to use this feature, click
910 </li>
911 </ul>
915 future development of the cross-db relations.
916 </dd>
920 </dt>
921 <dd>
922 Since release 2.3.0 you can describe, in a special 'table_info'
923 table, which field is to be displayed as a tool-tip when moving the
924 cursor over the corresponding key.<br />
925 This configuration variable will hold the name of this special
926 table. To allow the usage of this functionality:
928 <li>put the table name in
930 <li>then for each table where you want to use this feature,
932 to choose the field.</li>
933 </ul>
935 </dd>
939 </dt>
942 the relations between your tables. To do this it needs two tables
947 schema output).<br /><br />
951 To allow the usage of this functionality:
954 infrastructure</li>
955 <li>put the correct table names in
958 </ul>
961 </dd>
965 </dt>
967 Since release 2.3.0 you can store comments to describe each column for
969 <br /><br />
971 Starting with release 2.5.0, comments are consequently used on the table
972 property pages and table browse view, showing up as tool-tips above the
973 column name (properties page) or embedded within the header of table in
974 browse view. They can also be shown in a table dump. Please see the
975 relevant configuration directives later on.<br /><br />
977 Also new in release 2.5.0 is a MIME-transformation system which is also
979 Transformations</a> for further information. To use the
980 MIME-transformation system, your column_info table has to have the three
981 new fields 'mimetype', 'transformation', 'transformation_options'.
982 <br /><br />
984 To allow the usage of this functionality:
986 infrastructure</li>
987 <li>put the table name in
991 <pre>
992 ALTER TABLE `pma_column_comments`
993 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
994 ADD `transformation` VARCHAR( 255 ) NOT NULL,
995 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
996 </pre>
999 renamed from<br />
1002 </ul>
1003 </dd>
1007 </dt>
1010 all queries you entered manually into the phpMyAdmin interface. If you
1011 don't want to use a table-based history, you can use the JavaScript-based
1012 history. Using that, all your history items are deleted when closing the
1013 window.<br /><br />
1015 Using
1017 you can specify an amount of history items you want to have on hold. On
1018 every login, this list gets cut to the maximum amount.<br /><br />
1020 The query history is only available if JavaScript is enabled in your
1021 browser.<br /><br />
1023 To allow the usage of this functionality:
1026 infrastructure</li>
1028 </li>
1029 </ul>
1030 </dd>
1034 </dt>
1036 to visually manage the relations.
1037 <br /><br />
1039 To allow the usage of this functionality:
1042 infrastructure</li>
1044 </li>
1045 </ul>
1046 </dd>
1049 </dt>
1051 column_info table got enhanced with three new fields. If the above variable
1053 latest table structure available. If not, it will emit a warning to the
1054 superuser.<br /><br />
1056 You can disable this checking behavior by setting the variable to false,
1057 which should offer a performance increase.<br /><br />
1059 Recommended to set to FALSE, when you are sure, your table structure is
1060 up to date.</dd>
1062 boolean</dt>
1063 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1064 </dd>
1066 boolean</dt>
1067 <dd>Whether to allow logins without a password. The default
1069 to a MySQL server with was left with an empty password for root or
1070 on which an anonymous (blank) user is defined.
1071 </dd>
1074 </dt>
1076 authentication is disabled.<br /><br />
1079 all deny rules followed by allow rules. Access is allowed by default. Any
1080 client which does not match a Deny command or does match an Allow command
1081 will be allowed access to the server. <br /><br />
1084 applies all allow rules followed by deny rules. Access is denied by
1085 default. Any client which does not match an Allow directive or does
1086 match a Deny directive will be denied access to the server.<br /><br />
1088 If your rule order is set to 'explicit', the authentication is
1089 performed in a similar fashion to rule order 'deny,allow', with the
1093 and was available in Apache by specifying allow and deny rules without
1094 setting any order.<br /><br />
1096 Please also see <a
1098 address behind proxies.
1099 </dd>
1101 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1102 </dt>
1103 <dd>The general format for the rules is as such:
1105 <pre>
1107 </pre>
1112 well (please note that those containing SERVER_ADDRESS might not be
1113 available on all webservers):
1114 <pre>
1120 </pre>
1122 Having an empty rule list is equivalent to either using
1128 following work:<br />
1130 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1131 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1132 But the following does not work:<br />
1135 Also IPv6 addresses are not supported.
1136 </dd>
1138 <dd>Disable using <tt>INFORMATION_SCHEMA</tt> to retrieve information (use <tt>SHOW</tt> commands instead), because of speed issues when many databases are present. Currently used in some parts of the code, more to come.
1139 </dd>
1140 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1142 DATABASES</tt> command used to fetch the name of available databases will
1143 probably be too slow, so it can be replaced by faster commands (see
1145 </dd>
1147 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1148 </dd>
1149 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1150 <dd>Name of session which will be used for signon authentication method.
1151 </dd>
1153 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1154 </dd>
1156 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1157 </dd>
1160 <dd>If you have more than one server configured, you can set
1162 that server when phpMyAdmin is started, or set it to 0 to be given a
1163 list of servers without logging in.<br />
1165 MUST be set to that server.</dd>
1168 <dd>The maximum number of database names to be displayed in the
1169 navigation frame and the database list.</dd>
1172 <dd>The maximum number of table names to be displayed in the
1173 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1174 when in Light mode.</dd>
1177 <dd>The maximum number of characters when a SQL query is displayed. The
1178 default limit of 1000 should be correct to avoid the display of tons
1179 of hexadecimal codes that represent BLOBs, but some users have real
1180 SQL queries that are longer than 1000 characters. Also, if a query's
1181 length exceeds this limit, this query is not saved in the history.</dd>
1184 <dd>Defines whether to use GZip output buffering for increased
1186 Set to true/false for enabling/disabling. When set to 'auto' (string),
1187 phpMyAdmin tries to enable output buffering and will automatically disable
1188 it if your browser has some problems with buffering. IE6 with a certain patch
1189 is known to cause data corruption when having enabled buffering.</dd>
1192 <dd>Whether persistent connections should be used or not (mysql_connect or
1193 mysql_pconnect).</dd>
1199 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1200 to zero, no time limit is imposed.<br />
1201 This setting is used while importing/exporting dump files but has no
1202 effect when PHP is running in safe mode.</dd>
1205 <dd>Set the number of bytes a script is allowed to allocate. If set
1206 to zero, no limit is imposed.<br />
1207 This setting is used while importing/exporting dump files and at some
1208 other places in phpMyAdmin so you definitely don't want to put here
1209 a too low value. It has no effect when PHP is running in safe mode.<br />
1210 You can also use any string as in php.ini, eg. '16M'. Ensure
1214 <dd>Mark used tables and make it possible to show databases with locked
1219 generated by phpMyAdmin should be displayed or not.</dd>
1222 <dd>Defines whether normal users (non-administrator) are allowed to
1223 delete their own database or not. If set as FALSE, the link "Drop
1225 mydatabase" will be rejected. Quite practical for
1227 customers.<br />
1228 Please note that this limitation of SQL queries is not as strict as
1229 when using MySQL privileges. This is due to nature of SQL queries
1230 which might be quite complicated. So this choice should be viewed as
1231 help to avoid accidental dropping rather than strict privilege
1232 limitation.</dd>
1236 displayed when you're about to lose data.</dd>
1239 <dd>Define whether the previous login should be recalled or not in cookie
1240 authentication mode.<br /><br />
1242 This is automatically disabled if you do not have configured
1244 </dd>
1247 <dd>Define how long is login cookie valid. Please note that php
1248 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1249 might limit session validity and if session is lost, login cookie is
1251 at least as high is $cfg['LoginCookieValidity'] is set.</dd>
1255 means that it will be kept for existing session. This is recommended
1256 for not trusted environments.</dd>
1259 <dd>If enabled (default), logout deletes cookies for all servers,
1260 otherwise only for current one. Setting this to false makes it easy to
1261 forget to log out from other server, when you are using more of
1262 them.</dd>
1268 <dd>Define whether phpMyAdmin will continue executing a multi-query
1269 statement if one of the queries fails. Default is to abort execution.</dd>
1272 <dd>Define whether phpMyAdmin will output the results of each query of a
1273 multi-query statement embedded into the
1278 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1279 <br /><br />
1282 MySQL servers behind the firewall where your
1284 </dd>
1287 <dd>Defines whether to use a select-based menu and display only the current
1288 tables in the left frame (smaller page). Only in Non-Lightmode you can
1289 use the feature to display nested folders using
1291 </dd>
1294 <dd>In light mode, defines whether to display the names of databases (in the
1295 selector) using a tree, see also
1297 </dd>
1300 string or array</dt>
1301 <dd>The string used to separate the parts of the database name when showing
1302 them in a tree. Alternatively you can specify more strings in an array
1303 and all of them will be used as a separator.</dd>
1306 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1307 This means if you have tables like 'first__second__third' this will be
1309 If set to FALSE or empty, the feature is disabled. NOTE: You should
1310 not use this separator at the beginning or end of a
1311 table name or multiple times after another without any other
1312 characters in between.</dd>
1315 <dd>Defines how many sublevels should be displayed when splitting
1316 up tables by the above separator.</dd>
1319 <dd>Defines whether to display table comment as tool-tip in left frame or
1320 not.</dd>
1323 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1324 comment and the real name. That means that if you have a table called
1325 'user0001' and add the comment 'MyName' on it, you will see the name
1326 'MyName' used consequently in the left frame and the tool-tip shows
1327 the real name of the DB.</dd>
1330 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1332 When setting this to 'nested', the Alias of the Tablename is only used
1333 to split/nest the tables according to the
1335 directive. So only the folder is called like the Alias, the tablename itself
1336 stays the real tablename.</dd>
1339 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1342 <dd>Enter URL where logo in the navigation frame will point to.
1343 For use especially with self made theme which changes this.
1352 <dd>Defines whether or not to display a server choice at the top of the left frame.
1353 Defaults to FALSE.</dd>
1355 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1356 Defaults to FALSE (drop-down).</dd>
1358 <dd>Defines whether to display database choice in light navigation frame as links
1359 instead of in a drop-down. Defaults to 'auto' - on main page list is
1360 shown, when database is selected, only drop down is displayed.</dd>
1363 <dd>Defines the tab displayed by default when clicking the small
1364 icon next to each table name in the navigation panel. Possible
1370 <dd>Defines whether or not to display space usage and statistics about databases
1371 and tables.<br />
1372 Note that statistics requires at least MySQL 3.23.3 and that, at this
1373 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1376 <dd>Defines whether to display detailed server information on main page.
1377 You can additionally hide more information by using
1379 </dd>
1384 </dt>
1387 not at the starting main (right) frame. This setting
1388 does not check MySQL commands entered directly.<br /><br />
1390 Please note that to block the usage of phpinfo() in scripts, you
1397 hard coded password value in the configuration file, end users can't
1398 be allowed to change their passwords.</dd>
1401 <dd>Defines whether to suggest a database name on the
1405 <dd>Defines whether navigation bar buttons and the right panel top menu
1406 contain text or symbols only. A value of TRUE displays icons, FALSE
1407 displays text and 'both' displays both icons and text.</dd>
1410 <dd>Defines whether a user should be displayed a
1414 <dd>Number of rows displayed when browsing a result set. If the result set
1421 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1425 from editing when browsing a table's content. Valid values are:
1430 </ul>
1431 </dd>
1434 <dd>Defines whether or not MySQL functions fields should be initially
1435 displayed in edit/insert mode. Since version 2.10, the user can
1436 toggle this setting from the interface.
1437 </dd>
1440 <dd>Defines which type of editing controls should be used for CHAR and
1441 VARCHAR fields. Possible values are:
1442 <ul><li>input - this allows to limit size of text to size of field in
1443 MySQL, but has problems with newlines in fields</li>
1444 <li>textarea - no problems with newlines in fields, but also no
1445 length limitations</li>
1446 </ul>
1447 Default is old behavior so input.</dd>
1453 <dd>If there are fewer items than this in the set of foreign keys, then a
1454 drop-down box of foreign keys is presented, in the style described by the
1456 setting.</dd>
1459 <dd>For the foreign key drop-down fields, there are several methods of
1460 display, offering both the key and value data. The contents of the
1461 array should be one or both of the following strings:
1467 </dt>
1468 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1469 creating a dump file</dd>
1472 </dt>
1473 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1474 compressed exports. This doesn't affect smaller dumps and allows users to
1475 create larger dumps that won't otherwise fit in memory due to php
1476 memory limit. Produced files contain more GZip/BZip2 headers, but all
1477 normal programs handle this correctly.</dd>
1481 mainframe.</dd>
1485 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1490 <dd>How many columns will be utilized to display the tables on the
1491 database property view? Default is 1 column. When setting this to a
1492 value larger than 1, the type of the database will be omitted for more
1493 display space.</dd>
1497 <dd>Defines the tab displayed by default on server view. Possible
1504 <dd>Defines the tab displayed by default on database view. Possible
1509 <dd>Defines the tab displayed by default on table view. Possible
1516 points to the MySQL documentation (type depends
1517 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1518 generated.<br />
1520 for more information about MySQL manuals and their types.</dd>
1523 <dd>Type of MySQL documentation:
1529 </ul>
1530 </dd>
1533 <dd>Defines the default language to use, if not browser-defined or
1534 user-defined.<br />
1536 this setting.</dd>
1539 <dd>Defines the default connection collation to use, if not
1540 user-defined.<br />
1545 <dd>Force: always use this language (must be defined in the
1549 <dd>Limit list of available languages to those matching the given regular
1550 expression. For example if you want only Czech and English, you should
1554 <dd>Default character set to use for recoding of MySQL queries. This must be
1555 enabled and it's described by
1557 option.<br />
1558 You can give here any character set which is in
1560 array and this is just default choice, user can select any of them.</dd>
1563 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1564 support (compiled in or module) in PHP to allow MySQL queries recoding
1565 and used language file must have it enabled (by default only these
1566 which are in Unicode, just to avoid losing some characters).<br /><br />
1569 in the Export and Import pages, to choose the character set when
1570 exporting a file. The default value in this menu comes from
1572 </dd>
1575 <dd>You can select here which functions will be used for character set
1576 conversion. Possible values are:
1577 <ul><li>auto - automatically use available one (first is tested
1578 iconv, then recode)</li>
1581 </ul>
1582 Default is auto.</dd>
1585 <dd>Specify some parameters for iconv used in charset conversion. See
1588 used, so that invalid characters will be transliterated.</dd>
1591 <dd>Available character sets for MySQL conversion. You can add your own (any of
1592 supported by recode/iconv) or remove these which you don't use.
1593 Character sets will be shown in same order as here listed, so if you
1594 frequently use some of these move them to the top.</dd>
1599 default empty, you need to fill in some trusted proxy servers if you
1600 want to use rules for IP addresses behind proxy.<br /><br />
1602 The following example specifies that phpMyAdmin should trust a
1604 <pre>
1605 $cfg['TrustedProxies'] =
1607 </pre>
1608 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1609 client's IP address as usual.
1610 </dd>
1614 MIME transformations.<br />
1615 Possible values are:
1616 <ul><li>auto - automatically detect, this is a bit expensive
1618 according to your server real possibilities</li>
1621 </ul>
1622 Default is auto.
1623 </dd>
1626 <dd>
1627 We normally check the permissions on the configuration file to ensure
1628 it's not world writable. However, phpMyAdmin could be installed on
1629 a NTFS filesystem mounted on a non-Windows server, in which case the
1630 permissions seems wrong but in fact cannot be detected. In this case
1632 </dd>
1636 </dd>
1638 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1639 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1640 </dt>
1641 <dd>The background styles used for both the frames.
1644 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1646 <dd>The style used for the pointer in the navi frame.
1650 </dt>
1651 <dd>The color used for the database name in the navi frame.
1660 </dd>
1664 <dd>The style used for table headers. See
1669 </dd>
1673 </dd>
1675 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1677 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1679 </dt>
1681 The former feature highlights the row over which your mouse is passing
1682 and the latter lets you visually mark/unmark rows by clicking on
1683 them.<br />
1688 <dd>You put here a valid CSS font family value, for example
1693 <dd>You put here a valid CSS font family value, for example
1707 </dt>
1709 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1711 The Char* values are used for CHAR and VARCHAR editing (if configured
1715 </dt>
1719 </dt>
1720 <dd>Defines if the whole textarea of the query box will be selected on
1721 click.</dd>
1724 </dt>
1725 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1726 editing.</dd>
1729 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1730 Can be turned off by a toggle button on the browse page.</dd>
1734 </dt>
1735 <dd>Defines the place where modify and delete links would be put when
1736 tables contents are displayed (you may have them displayed both at the
1737 left and at the right).
1743 </dt>
1745 Define which one is displayed by default. The first mode displays each
1746 row on a horizontal line, the second rotates the headers by 90
1747 degrees, so you can use descriptive headers even though fields only
1748 contain small values and still print them out. The vertical mode sorts
1749 each row on a vertical lineup.<br /><br />
1751 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1752 the rotation of the header for horizontalflipped is done via CSS. If
1753 set to 'fake' PHP does the transformation for you, but of course this
1754 does not look as good as CSS.</dd>
1758 string or integer</dt>
1759 <dd>When editing/creating new columns in a table all fields normally get
1760 lined up one field a line. (default: 'horizontal'). If you set this to
1761 'vertical' you can have each field lined up vertically beneath each
1762 other. You can save up a lot of place on the horizontal direction and
1763 no longer have to scroll. If you set this to integer, editing of fewer
1764 columns will appear in 'vertical' mode, while editing of more fields
1765 still in 'horizontal' mode. This way you can still effectively edit
1766 large number of fields, while having full view on few of them.</dd>
1770 </dt>
1772 display of column comments in Browse or Property display. In browse
1773 mode, the comments are shown inside the header. In property mode,
1774 comments are displayed using a CSS-formatted dashed-line below the
1775 name of the field. The comment is shown as a tool-tip for that field.
1776 </dd>
1788 <dd>Whether to display a link to validate a query in any SQL Query box.
1795 <dd>
1796 The name of the directory where
1798 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1799 are available under a drop-down box when you click the database or
1800 table name, then the Import tab.
1801 <br /><br />
1803 If you want different directory for each user, %u will be replaced
1804 with username.<br /><br />
1808 compressed formats is enabled).<br /><br />
1810 This feature is useful when your file is too big to be uploaded via
1812 uploads are disabled in PHP.<br /><br />
1814 Please note that if PHP is running in safe mode, this directory must
1815 be owned by the same user as the owner of the phpMyAdmin scripts.
1816 <br /><br />
1820 alternatives.
1821 </dd>
1824 <dd>
1825 The name of the directory where dumps can be saved.<br /><br />
1827 If you want different directory for each user, %u will be replaced
1828 with username.<br /><br />
1830 Please note that the directory must exist and has to be writable for
1831 the user running webserver.<br /><br />
1833 Please note that if PHP is running in safe mode, this directory must
1834 be owned by the same user as the owner of the phpMyAdmin scripts.
1835 </dd>
1838 <dd>
1839 The name of the directory where temporary files can be stored.
1840 <br /><br />
1842 This is needed for native MS Excel export, see
1848 <br /><br />
1850 If the directory where phpMyAdmin is installed is subject to an
1852 temporary directory in some directory accessible by the web
1853 server. However for security reasons, this directory should be outside
1854 the tree published by webserver. If you cannot avoid having this
1855 directory published by webserver, place at least an empty
1857 possible.
1858 <br /><br />
1860 This directory should have as strict permissions as possible as the only
1861 user required to access this directory is the one who runs the
1862 webserver. If you have root privileges, simply make this user owner of
1863 this directory and make it accessible only by it:
1864 <br /><br />
1866 <pre>
1867 chown www-data:www-data tmp
1868 chmod 700 tmp
1869 </pre>
1871 If you cannot change owner of the directory, you can achieve a similar
1874 <pre>
1875 chmod 700 tmp
1876 setfacl -m "g:www-data:rwx" tmp
1877 setfacl -d -m "g:www-data:rwx" tmp
1878 </pre>
1880 If neither of above works for you, you can still make the directory
1882 system reading and writing data in this directory.
1883 </dd>
1886 <dd>
1887 In this array are defined default parameters for export, names of
1888 items are similar to texts seen on export page, so you can easily
1889 identify what they mean.
1890 </dd>
1893 <dd>
1894 In this array are defined default parameters for import, names of
1895 items are similar to texts seen on import page, so you can easily
1896 identify what they mean.
1897 </dd>
1900 <dd>
1901 Repeat the headers every X cells, or 0 to deactivate.
1902 </dd>
1910 </dt>
1911 <dd>
1912 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1913 or icon is always displayed on the left panel. If JavaScript is enabled in
1914 your browser, a click on this opens a distinct query window, which is
1915 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1916 changes to display a query box.<br /><br />
1918 The size of this query window can be customized with
1920 - both integers for the size in pixels. Note that normally, those
1922 theme you are using.<br /><br />
1926 opens the query window and puts the current query
1927 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1928 query in the right panel's query box.
1929 <br /><br />
1930 The usage of the JavaScript query window is recommended if you have a
1931 JavaScript enabled browser. Basic functions are used to exchange quite
1932 a few variables, so most 4th generation browsers should be capable to
1933 use that feature. It currently is only tested with Internet Explorer 6
1934 and Mozilla 1.x.
1935 <br /><br />
1937 to a table, which has to be created by you (see <a
1939 all your queries will be appended to the form, but only as long as
1940 your window is opened they remain saved.
1941 <br /><br />
1942 When using the JavaScript based query window, it will always get
1943 updated when you click on a new table/db to browse and will focus if
1944 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1945 the query window by checking the box "Do not overwrite this query from
1946 outside the window" below the query textarea. Then you can browse
1947 tables/databases in the background without losing the contents of the
1948 textarea, so this is especially useful when composing a query with
1949 tables you first have to look in. The checkbox will get automatically
1950 checked whenever you change the contents of the textarea. Please
1951 uncheck the button whenever you definitely want the query window to
1952 get updated even though you have made alterations.
1953 <br /><br />
1956 <br /><br />
1957 The query window also has a custom tabbed look to group the features.
1959 default tab to be used when opening the query window. It can be set to
1960 either 'sql', 'files', 'history' or 'full'.</dd>
1966 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1968 If the approximate row count as returned by
1971 count will be used.
1972 </dd>
1974 <dd>For VIEWs, since obtaining the exact count could have an
1975 impact on performance, this value is the maximum to be displayed, using
1977 any row counting.
1978 </dd>
1982 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1984 page. By clicking on the button 'toggle scratchboard' on the page
1985 where you edit x/y coordinates of those elements you can activate a
1986 scratchboard where all your elements are placed. By clicking on an
1987 element, you can move them around in the pre-defined area and the x/y
1988 coordinates will get updated dynamically. Likewise, when entering a
1989 new position directly into the input field, the new position in the
1990 scratchboard changes after your cursor leaves the input field.<br />
1991 You have to click on the 'OK'-button below the tables to save the new
1992 positions. If you want to place a new element, first add it to the
1993 table of elements and then you can drag the new element around.<br />
1994 By changing the paper size and the orientation you can change the size
1995 of the scratchboard as well. You can do so by just changing the
1996 dropdown field below, and the scratchboard will resize automatically,
1997 without interfering with the current placement of the elements.<br />
1998 If ever an element gets out of range you can either enlarge the paper
1999 size or click on the 'reset' button to place all elements below each
2000 other.<br />
2002 get this control to work. The basic Drag&Drop script functionality
2003 was kindly borrowed from www.youngpup.net and is underlying so
2004 specific license.</dd>
2007 <dd>Sorts database and table names according to natural order (for example,
2008 t1, t2, t10). Currently implemented in the left panel (Light mode)
2009 and in Database view, for the table list.</dd>
2020 <dd>Allows you to specify window's title bar. Following magic string can
2021 be used to get special values:
2022 <dl>
2028 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2037 </dl>
2038 </dd>
2048 </dd>
2051 <dd>If theme manager is active, use this as the path of the subdirectory
2052 containing all the themes.</dd>
2066 </dt>
2067 <dd>Default queries that will be displayed in query boxes when user didn't
2068 specify any. Use %d for database name, %t for table name and %f for a
2069 comma separated list of field names. Note that %t and %f are only
2073 <dd>
2074 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
2075 default we use HTML to format the query, but you can disable this by
2077 </dd>
2080 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2081 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2082 query inside a bracket is indented. By changing
2085 specifies the units of the indent amount that you specified. This is
2086 used via stylesheets.</dd>
2089 <dd>This array is used to define the colours for each type of element of
2090 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2092 If you specify an empty string for the color of a class, it is ignored
2093 in creating the stylesheet.
2094 You should not alter the class names, only the colour strings.<br />
2115 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2119 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2120 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2121 </ul>
2122 </dd>
2126 <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,
2127 as originally published on
2129 <br />
2130 For help in setting up your system to use the service, see the
2132 </dd>
2136 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2137 and any password, so we use those by default. Instead, if
2138 you have an account with them, you can put your login details
2139 here, and it will be used in place of the anonymous login.</dd>
2140 </dl>
2141 </dd>
2144 <dd><b>DEVELOPERS ONLY!</b></dd>
2147 <dd><b>DEVELOPERS ONLY!</b><br />
2148 Enable logging queries and execution times to be displayed in the bottom
2149 of main page (right frame).</dd>
2152 <dd><b>DEVELOPERS ONLY!</b><br />
2153 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2154 the code.<br />
2155 For help in setting up your system to this, see the
2159 <dd><b>DEVELOPERS ONLY!</b><br />
2160 Enable profiling support for phpMyAdmin. This will append a chunk of data
2161 to the end of every page displayed in the main window with profiling
2162 statistics for that page.<br />
2163 You may need to increase the maximum execution time for this to
2164 complete successfully.<i>Profiling was removed from the code for
2165 version 2.9.0 due to licensing issues.</i></dd>
2167 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2168 <dd><b>DEVELOPERS ONLY!</b><br />
2169 When profiling data is displayed, this variable controls the threshold of
2170 display for any profiling data, based on the average time each time has
2171 taken. If it is over the threshold it is displayed, otherwise it is not
2172 displayed. This takes a value in milliseconds. In most cases you don't need
2173 to edit this.</dd>
2176 <dd>All possible types of a MySQL column. In most cases you don't need to
2177 edit this.</dd>
2180 <dd>Possible attributes for fields. In most cases you don't need to edit
2181 this.</dd>
2184 <dd>A list of functions MySQL supports. In most cases you don't need to
2185 edit this.</dd>
2188 <dd>Mapping of column types to meta types used for preferring displayed
2189 functions. In most cases you don't need to edit this.</dd>
2192 <dd>Functions preferred for column meta types as defined in
2193 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2194 to edit this.</dd>
2197 <dd>Functions selected by default when inserting/changing row, Functions
2198 are defined for meta types from
2200 <code>first_timestamp</code>, which is used for first timestamp column
2201 in table.</dd>
2204 <dd>Operators available for search operations on numeric and date fields.
2205 </dd>
2208 <dd>Operators available for search operations on character fields.
2209 Note that we put <code>LIKE</code> by default instead of
2210 <code>LIKE %...%</code>, to avoid unintended performance problems
2211 in case of huge tables.</dd>
2214 <dd>Operators available for search operations on enum fields.</dd>
2217 <dd>Additional operators available for search operations when the
2218 field can be null.</dd>
2220 </dl>
2222 <!-- TRANSFORMATIONS -->
2228 </ol>
2232 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2234 section</a> on how to do so.</p>
2236 <p> You can apply different transformations to the contents of each field. The
2237 transformation will take the content of each field and transform it with
2238 certain rules defined in the selected transformation.</p>
2240 <p> Say you have a field 'filename' which contains a filename. Normally you would
2241 see in phpMyAdmin only this filename. Using transformations you can transform
2242 that filename into a HTML link, so you can click inside of the phpMyAdmin
2243 structure on the field's link and will see the file displayed in a new browser
2244 window. Using transformation options you can also specify strings to
2245 append/prepend to a string or the format you want the output stored in.</p>
2247 <p> For a general overview of all available transformations and their options,
2248 you can consult your
2249 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2250 installation.</p>
2252 <p> For a tutorial on how to effectively use transformations, see our
2254 the official phpMyAdmin homepage.</p>
2258 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2259 clicking on the 'Structure' link for a table). There click on
2260 "Change" (or change icon) and there you will see three new fields at
2261 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2262 'Transformation options'.</p>
2264 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2265 that corresponds to the column's contents. Please note that
2266 transformations are inactive as long as no MIME-type is selected.</li>
2268 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2269 hopefully growing amount of pre-defined transformations. See below for information on
2270 how to build your own transformation.<br />
2272 There are global transformations and mimetype-bound transformations. Global transformations
2273 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2274 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2275 transformations which operate on the main mimetype (like 'image'), which will most likely
2276 take the subtype into regard, and those who only operate on a
2277 specific subtype (like 'image/jpeg').<br />
2279 You can use transformations on mimetypes for which the function was not defined for. There
2280 is no security check for you selected the right transformation, so take care of what the
2281 output will be like.</li>
2283 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2284 transform-function specific options here. Usually the transforms can operate with default
2285 options, but it is generally a good idea to look up the overview to see which options are
2286 necessary.<br />
2288 Much like the ENUM/SET-Fields, you have to split up several options using the format
2289 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2290 parsed as an array, leaving the first value the first element in the array, and so
2291 forth.<br />
2293 If you want to specify a MIME character set you can define it in the transformation_options.
2294 You have to put that outside of the pre-defined options of the specific mime-transform,
2296 for which you can specify 2 options and you want to append a character set, enter "'first
2297 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2299 </ul>
2303 <p> All mimetypes and their transformations are defined through single files in
2304 the directory 'libraries/transformations/'.</p>
2306 <p> They are stored in files to ease up customization and easy adding of new
2307 transformations.</p>
2309 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2310 always work. It makes no sense to apply a transformation to a mimetype, the
2311 transform-function doesn't know to handle.</p>
2313 <p> One can, however, use empty mime-types and global transformations which should work
2314 for many mimetypes. You can also use transforms on a different mimetype they where built
2315 for, but pay attention to option usage as well as what the transformation does to your
2316 field.</p>
2318 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2319 any other transform function and provides some basic functions.</p>
2321 <p> There are 5 possible file names:</p>
2323 <ol><li>A mimetype+subtype transform:<br /><br />
2325 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2327 Please not that mimetype and subtype are separated via '_', which shall
2328 not be contained in their names. The transform function/filename may
2329 contain only characters which cause no problems in the file system as
2330 well as the PHP function naming convention.<br /><br />
2332 The transform function will the be called
2333 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2335 <b>Example:</b><br /><br />
2337 <tt>text_html__formatted.inc.php</tt><br />
2338 <tt>PMA_transform_text_html__formatted()</tt></li>
2340 <li>A mimetype (w/o subtype) transform:<br /><br />
2342 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2344 Please note that there are no single '_' characters.
2345 The transform function/filename may contain only characters which cause
2346 no problems in the file system as well as the PHP function naming
2347 convention.<br /><br />
2349 The transform function will the be called
2350 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2352 <b>Example:</b><br /><br />
2354 <tt>text__formatted.inc.php</tt><br />
2355 <tt>PMA_transform_text__formatted()</tt></li>
2357 <li>A mimetype+subtype without specific transform function<br /><br />
2359 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2361 Please note that there are no '__' characters in the filename. Do not
2362 use special characters in the filename causing problems with the file
2363 system.<br /><br />
2365 No transformation function is defined in the file itself.<br /><br />
2367 <b>Example:</b><br /><br />
2369 <tt>text_plain.inc.php</tt><br />
2370 (No function)</li>
2372 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2374 <tt>[mimetype].inc.php</tt><br /><br />
2376 Please note that there are no '_' characters in the filename. Do not use
2377 special characters in the filename causing problems with the file system.
2378 <br /><br />
2380 No transformation function is defined in the file itself.<br /><br />
2382 <b>Example:</b><br /><br />
2384 <tt>text.inc.php</tt><br />
2385 (No function)</li>
2387 <li>A global transform function with no specific mimetype<br /><br />
2389 <tt>global__[transform].inc.php</tt><br /><br />
2391 The transform function will the be called
2392 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2394 <b>Example:</b><br /><br />
2396 <tt>global__formatted</tt><br />
2397 <tt>PMA_transform_global__formatted()</tt></li>
2398 </ol>
2400 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2401 transform function.</p>
2403 <p> All filenames containing no '__' in themselves are not shown as valid transform
2404 functions in the dropdown.</p>
2406 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2407 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2408 without a transform function. Also note the introduction of a function description in
2409 the language files. For each function a $strTransformation_[filename without .inc.php]
2410 has to exist.</p>
2412 <p> You can use the template generator to generate new functions and entries in the
2413 language file.</p>
2415 <p> To create a new transform function please see
2416 <tt>libraries/transformations/template_generator.sh</tt>.
2417 To create a new, empty mimetype please see
2418 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2420 <p> A transform function always gets passed three variables:</p>
2422 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2423 you want to transform.</li>
2424 <li><b>$options</b> - Contains any user-passed options to a transform function
2425 as an array.</li>
2426 <li><b>$meta</b> - Contains an object with field information to your column.
2427 The data is drawn from the output of the
2429 function. This means, all object properties described on the
2431 available in this variable and can be used to transform a field accordingly
2432 to unsigned/zerofill/not_null/... properties.<br />
2433 The $meta->mimetype variable contains the original MIME-type of the
2434 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2435 </ol>
2437 <!-- FAQ -->
2444 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2448 </ol>
2450 <p> Please have a look at our
2452 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2453 features and or interface.</p>
2459 action is required or phpMyAdmin sends a blank page or a page full of
2460 cryptic characters to my browser, what can I do?</a></h4>
2462 <p> There are some known PHP bugs with output buffering and compression.<br />
2464 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2465 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2466 configuration file.<br />
2467 Furthermore, we know about such problems connected to the release
2468 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2469 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2474 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2475 See also the
2477 entry about PHP bugs with output buffering.<br />
2478 If your server keeps crashing, please ask for help in the various Apache
2479 support groups.</p>
2483 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2484 script: I'm always displayed the login screen.</a></h4>
2486 <p> This is a known PHP bug (see this
2488 official PHP bug database. It means there is and won't be any phpMyAdmin
2489 fix against it because there is no way to code a fix.</p>
2495 application misbehaved by not returning a complete set of
2497 </h4>
2499 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2500 Have a look at the last message in this
2502 official PHP bug database.</p>
2507 and/or many error messages with the
2509 mode.</a></h4>
2511 <p> This is a known problem with the PHP
2513 filter: it's not so stable. Please use instead the cookie authentication mode.
2514 </p>
2519 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2520 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2521 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2522 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2523 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2528 work.</a></h4>
2530 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2531 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2532 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2533 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2534 We faced PHP crashes when trying to download a dump with MS Internet
2535 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2536 this case you should switch to the release version of PHP 4.2.0.</p>
2540 an error about safe mode being in effect.</a></h4>
2542 <p> Your uploaded file is saved by PHP in the "upload dir", as
2543 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2544 the system default is <i>/tmp</i>).<br />
2545 We recommend the following setup for Apache servers running in safe mode,
2546 to enable uploads of files while being reasonably secure:</p>
2548 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2549 <li>give ownership to the Apache server's user.group:
2550 <tt>chown apache.apache /tmp/php</tt></li>
2551 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2552 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2553 <li>restart Apache</li>
2554 </ul>
2558 general file uploads don't work on my system and uploaded files have a
2559 <tt>Content-Type:</tt> header in the first line.</a></h4>
2561 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2562 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2563 So the problem is that this package has a serious bug that was corrected
2564 ages ago in PHP (2001-01-28: see
2566 for more details). The problem is that the bugged package is still
2567 available though it was corrected (see
2569 for more details).<br />
2570 So please download
2571 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2572 and the problem should go away.<br />
2573 And that fixes the \r\n problem with file uploads!</p>
2577 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2578 I'm using the Apache server.</a></h4>
2580 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2581 your <i>httpd.conf</i>:</p>
2585 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2589 uploading a file from the query box.</a></h4>
2591 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2592 restrictions. However you need to create temporary directory and
2594 The uploaded files will be moved there, and after execution of your
2600 <p> The MySQL manual explains how to
2602 reset the permissions</a>.</p>
2607 execute a bookmark.</a></h4>
2609 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2610 cannot access the uploaded query.</p>
2615 submit a query from the convenient text area.</a></h4>
2617 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2618 and try to increase it.</p>
2622 </h4>
2624 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2625 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2626 names to align with current standards.</p>
2631 </h4>
2633 <p> Starting with version 2.7.0, the import engine has been re–written and these
2634 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2635 to take advantage of the new import features.</p>
2637 <p> The first things to check (or ask your host provider to check) are the
2638 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2639 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2640 All of these three settings limit the maximum size of data that can be
2641 submitted and handled by PHP. One user also said that post_max_size
2642 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2644 There exist several workarounds if your upload is too big or your
2645 hosting provider is unwilling to change the settings:</p>
2648 feature. This allows one to
2649 upload a file to the server via scp, ftp, or your favorite file transfer
2650 method. PhpMyAdmin is then able to import the files from the temporary
2652 section</a> of this document.</li>
2654 BigDump</a>) to split the files before uploading. We cannot support this
2655 or any third party applications, but are aware of users having success
2656 with it.</li>
2657 <li>If you have shell (command line) access, use MySQL to import the files
2658 directly. You can do this by issuing the "source" command from
2659 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2660 </ul>
2664 support?</a></h4>
2666 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2667 fully supported. phpMyAdmin may connect to your MySQL server
2668 using PHP's classic
2671 is available in php 5.0.<br />
2672 Either way, the developers of both extensions recommend to use the classic
2673 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2674 When compiling php, we strongly recommend that you manually link the MySQL
2675 extension of your choice to a MySQL client library of at least the same
2676 minor version since the one that is bundled with some PHP distributions is
2679 If your webserver is running on a windows system, you might want to try
2680 MySQL's
2682 instead of the MySQL / MySQLi extensions that are bundled with the official
2683 php Win32 builds.</p>
2687 message, "Client does not support authentication protocol requested
2688 by server; consider upgrading MySQL client"</a></h5>
2690 <p> You tried to access MySQL with an old MySQL client library. The version of
2691 your MySQL client library can be checked in your phpinfo() output.
2692 In general, it should have at least the same minor version as your server
2696 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2697 changed the authentication hash and your PHP is trying to use the old method.
2699 with the proper client library to match your MySQL installation. Your
2700 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2701 More information (and several workarounds) are located in the
2703 </p>
2707 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2708 capital letter in its name it is changed to lowercase as it should. But
2709 if I try to DROP this table MySQL is unable to find the corresponding
2710 file.</a></h4>
2712 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2713 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2714 directive.</p>
2718 script seems not to know the font face I'm using!</a></h4>
2720 <p> The "FPDF" library we're using for this feature requires some
2721 special files to use font faces.<br />
2723 these files.</p>
2727 check PHP Configuration".</a></h4>
2729 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2730 "MySQL extension". This extension may be part of the PHP
2731 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2732 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2733 to load the extension but failed.<br /><br />
2735 Usually, the problem is solved by installing a software package called
2736 "PHP-MySQL" or something similar.</p>
2741 and I cannot log in using cookie auth.</a></h4>
2743 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2747 so I cannot upload.</a></h4>
2749 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2750 parameter is not set to "on".</p>
2754 a new table the table and field names are changed to lowercase!</a></h4>
2756 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2757 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2758 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2759 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2760 directory and add the following line to the group [mysqld]:</p>
2762 <pre>set-variable = lower_case_table_names=0</pre>
2764 <p> Next, save the file and restart the MySQL service. You can always check the
2765 value of this directive using the query</p>
2767 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2771 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2774 </p>
2778 and I get problems, such as undefined variables when I run a
2781 <p> A tip from Jose Fandos: put a comment on the following two lines
2782 in httpd.conf, like this:</p>
2784 <pre>
2785 # mod_gzip_item_include file \.php$
2787 </pre>
2789 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2790 PHP scripts. Of course you have to restart Apache.</p>
2795 I get the error "No input file specified" when trying to
2796 run phpMyAdmin.</a></h4>
2798 <p> This is a permission problem. Right-click on the phpmyadmin folder
2799 and choose properties. Under the tab Security, click on "Add"
2800 and select the user "IUSR_machine" from the list. Now set his
2801 permissions and it should work.</p>
2805 db_structure.php with plenty of tables).</a></h4>
2808 GZIP output buffering is enabled. If you turn off it (by
2810 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2811 PHP 5.0.0.</p>
2815 message 'Errorcode: 13'. What does this mean?</a></h4>
2817 <p> This can happen due to a MySQL bug when having database / table names with
2818 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2819 To fix this, turn off this directive, convert all database and table names
2820 to lower case and turn it on again. Alternatively, there's a bug-fix
2821 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2825 and the fields are duplicated.</a></h4>
2827 <p> It is possible to configure Apache in such a way that PHP has problems
2828 interpreting .php files.</p>
2830 <p> The problems occur when two different (and conflicting) set of directives
2831 are used:</p>
2833 <pre>
2834 SetOutputFilter PHP
2835 SetInputFilter PHP
2836 </pre>
2838 <p> and</p>
2840 <pre>AddType application/x-httpd-php .php</pre>
2842 <p> In the case we saw, one set of directives was in
2843 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2844 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2845 The recommended way is with <tt>AddType</tt>, so just comment out
2846 the first set of lines and restart Apache:</p>
2848 <pre>
2849 #SetOutputFilter PHP
2850 #SetInputFilter PHP
2851 </pre>
2856 <p> This problem is known to happen when the server is running Turck MMCache
2857 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2862 <p> Yes.<br />
2863 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2864 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2865 <tt>error_reporting</tt> settings.
2866 </p>
2869 <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>
2871 <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>
2874 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2875 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2876 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2877 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2878 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2879 enabled.) Click <tt>OK</tt>.</li>
2880 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2881 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2882 </ol>
2886 PHP 5.0.4 on 64-bit systems?</a></h4>
2888 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2889 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2895 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
2896 the order of the server paragraph in <tt>config.inc.php</tt>.
2897 Table and script parts are optional. If you want
2898 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2899 some configuration. Following lines apply only for <a
2901 that you have enabled some features within global configuration. You need
2902 <code>Options FollowSymLinks</code> and <code>AllowOverride
2903 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2904 you need mod_rewrite to be enabled. Then you just need to create following
2905 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2906 (don't forget to change directory name inside of it):</p>
2908 <pre>
2909 RewriteEngine On
2910 RewriteBase /path_to_phpMyAdmin
2911 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2912 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2913 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2914 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2915 </pre>
2918 <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>
2920 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2921 following rewrite rule:</p>
2923 <pre>
2924 RewriteEngine On
2925 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2926 </pre>
2930 </h4>
2931 <p>
2932 There can be many explanations to this and a look at your server's
2933 error log file might give a clue.
2934 </p>
2938 password encryption in cookie auth doesn't work.</a></h4>
2940 <p> If your cluster consist of different architectures, PHP code used for
2941 encryption/decryption won't work correct. This is caused by use of
2942 pack/unpack functions in code. Only solution is to use mcrypt extension
2943 which works fine in this case.</p>
2948 <p> Yes but the default configuration values of Suhosin are known to cause
2949 problems with some operations, for example editing a table with many
2950 columns and no primary key. Tuning information is available at
2952 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2953 although the parameter names have changed (<tt>suhosin</tt> instead
2955 <tt>SuhosinDisableWarning</tt> directive</a>.
2956 </p>
2960 but then my connection is redirected back to http. What can cause this
2961 behavior?</a></h4>
2963 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
2964 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>
2967 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
2969 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
2970 Example from the Apache 2.2 documentation:</p>
2971 <pre>
2972 ProxyPass /mirror/foo/ http://backend.example.com/
2973 ProxyPassReverse /mirror/foo/ http://backend.example.com/
2974 ProxyPassReverseCookieDomain backend.example.com public.example.com
2975 ProxyPassReverseCookiePath / /mirror/foo/
2976 </pre>
2978 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
2979 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
2980 This is not specific to phpmyadmin, it's just the behavior of Apache.
2981 </p>
2983 <pre>
2984 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
2985 ProxyPassReverse /mirror/foo/
2986 http://backend.example.com/%7Euser/phpmyadmin
2987 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
2988 </pre>
2990 <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>
2991 for more details.</p>
2995 privileges, I get an error about an unknown column.</a></h4>
2997 <p> The MySQL server's privilege tables are not up to date, you need to run
2998 the <tt>mysql_upgrade</tt> command on the server.</p>
3005 headers already sent by ..." is displayed, what's the problem?</a></h4>
3007 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3008 (I.E. no blank lines, no spaces, no characters...) neither before the
3009 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3010 tag at the end. We also got a report from a user under IIS, that used
3011 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3012 contained an end-of-line character (hex 0A) at the end; removing this character
3013 cleared his errors.</p>
3018 <p> Either there is an error with your PHP setup or your username/password is
3019 wrong. Try to make a small script which uses mysql_connect and see if it
3020 works. If it doesn't, it may be you haven't even compiled MySQL support
3021 into PHP.</p>
3025 connect to local MySQL server through socket '/tmp/mysql.sock'
3026 (111) ..." is displayed. What can I do?</a></h4>
3028 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3030 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3031 In your <i>php.ini</i> you will find a line</p>
3033 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3035 <p> change it to</p>
3037 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3039 <p> Then restart apache and it will work.</p>
3041 <p> Here is a fix suggested by Brad Ummer:</p>
3043 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3044 To do this, telnet to your server and go to the MySQL bin directory. In
3045 this directory there should be a file named <i>mysqladmin</i>. Type
3046 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3047 info about your MySQL server, including the socket
3048 (<i>/tmp/mysql.sock</i>, for example).</li>
3049 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3050 phpMyAdmin, you need to complete the socket information in the
3051 <i>config.inc.php</i>.<br />
3052 For example:
3054 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3055 <br /><br />
3057 Please also make sure that the permissions of this file allow to be readable
3058 by your webserver (i.e. '0755').</li>
3059 </ul>
3061 <p> Have also a look at the
3063 corresponding section of the MySQL documentation</a>.</p>
3067 what can I do?</a></h4>
3070 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3071 sometime.<br />
3072 Also have a look at your PHP version number: if it contains "4.0b..."
3073 it means you're running a beta version of PHP. That's not a so good idea,
3074 please upgrade to a plain revision.</p>
3078 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3079 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3081 <p> Check the value you set for the
3083 directive in the phpMyAdmin configuration file.</p>
3087 password: YES)"-error when trying to access a MySQL-Server on a
3088 host which is port-forwarded for my localhost.</a></h4>
3090 <p> When you are using a port on your localhost, which you redirect via
3091 port-forwarding to another host, MySQL is not resolving the localhost
3092 as expected.<br />
3093 Erik Wasser explains: The solution is: if your host is "localhost"
3094 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3095 connection for speeding up things. And that doesn't work in this configuration
3096 with port forwarding.<br />
3102 <p> Themes are configured with
3106 <br />
3108 should not delete the directory "original" or its underlying
3109 structure, because this is the system theme used by phpMyAdmin.
3110 "original" contains all images and styles, for backwards
3111 compatibility and for all themes that would not include images or css-files.
3112 <br /><br />
3115 is enabled, you can select your favorite theme on the main page. Your
3116 selected theme will be stored in a cookie.<br /><br /></p>
3118 <p> To create a theme:</p>
3120 <ul><li>make a new subdirectory (for example "your_theme_name") under
3122 (by default <tt>themes</tt>)</li>
3123 <li>copy the files and directories from "original" to
3124 "your_theme_name"</li>
3125 <li>edit the css-files in "your_theme_name/css"</li>
3126 <li>put your new images in "your_theme_name/img"</li>
3127 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3128 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3129 contain your chosen theme name, that will be visible in user interface</li>
3130 <li>make a new screenshot of your theme and save it under
3131 "your_theme_name/screen.png"</li>
3132 </ul>
3134 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3135 theme verbose name, theme generation and theme version. These versions and
3136 generations are enumerated from 1 and do not have any direct dependence on
3137 phpMyAdmin version. Themes within same generation should be backwards
3138 compatible - theme with version 2 should work in phpMyAdmin requiring
3139 version 1. Themes with different generation are incompatible.</p>
3141 <p> If you do not want to use your own symbols and buttons, remove the
3142 directory "img" in "your_theme_name". phpMyAdmin will
3143 use the default icons and buttons (from the system-theme "original").
3144 </p>
3148 what can I do?</a></h4>
3150 <p> Here are a few points to check:</p>
3152 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3154 directive empty. See also
3156 </li>
3157 <li>Maybe you have a broken PHP installation or you need to upgrade
3158 your Zend Optimizer. See
3160 http://bugs.php.net/bug.php?id=31134</a>.
3161 </li>
3162 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3163 set to the default (200) or another low value, you could get this
3164 error if your table has a high number of columns. Adjust this setting
3165 accordingly. (Thanks to Klaus Dorninger for the hint).
3166 </li>
3167 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3168 of ";" will cause this error. Replace it with "&;".
3169 </li>
3171 you might want to increase
3173 </li>
3174 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3175 </li>
3176 </ul>
3183 who logged out can not log in again in with the same nick.</a></h4>
3185 <p> This is related to the authentication mechanism (protocol) used by
3186 phpMyAdmin. To bypass this problem: just close all the opened
3187 browser windows and then go back to phpMyAdmin. You should be able to
3188 log in again.</p>
3192 limit error or a time limit error.</a></h4>
3194 <p> Compressed dumps are built in memory and because of this are limited to
3195 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3196 using
3198 (enabled by default). Zip exports can not be handled this way, so if you need
3199 Zip files for larger dump, you have to use another way.</p>
3203 when I rename a table or a column.</a></h4>
3205 <p> This is an InnoDB bug, see <a href="http://bugs.mysql.com/bug.php?id=21704">http://bugs.mysql.com/bug.php?id=21704</a>.</p>
3209 bundled with the MySQL server distribution.</a></h4>
3211 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3213 <pre>
3214 -- MySQL dump 8.22
3215 --
3216 -- Host: localhost Database: database
3217 ---------------------------------------------------------
3218 -- Server version 3.23.54
3219 </pre>
3221 <p> The invalid part of the code is the horizontal line made of dashes that
3222 appears once in every dump created with mysqldump. If you want to run your
3223 dump you have to turn it into valid MySQL. This means, you have to add a
3224 whitespace after the first two dashes of the line or add a # before it:
3225 <br />
3226 <code>
3227 -- -------------------------------------------------------<br />
3228 </code>
3229 or<br />
3230 <code>
3231 #---------------------------------------------------------
3232 </code>
3233 </p>
3240 <p> Please note that you should not use the separating string multiple times
3241 without any characters between them, or at the beginning/end of your table
3242 name. If you have to, think about using another TableSeparator or disabling
3243 that feature</p>
3248 <p> In Relation view, being able to choose a table in another database,
3249 or having more than one index field in the foreign key.<br /><br/>
3250 In Query-by-example (Query), automatic generation of the query
3251 LEFT JOIN from the foreign table.<br /><br/>
3252 </p>
3256 I get series of errors like "Warning: unable to parse url". How
3257 can this be fixed?</a></h4>
3258 <p>
3259 Your table neither have a primary key nor an unique one, so we must use a
3260 long expression to identify this row. This causes problems to parse_url
3261 function. The workaround is to create a primary or unique key.
3262 <br />
3263 </p>
3267 a MIME-Transformation onto!</a></h4>
3269 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3270 nested forms can be put inside the table where phpMyAdmin displays the results.
3271 You can, however, use any form inside of a table if keep the parent
3272 form-container with the target to tbl_row_delete.php and just put your own
3273 input-elements inside. If you use a custom submit input field, the form will
3274 submit itself to the displaying page again, where you can validate the
3275 $HTTP_POST_VARS in a transformation.
3277 For a tutorial on how to effectively use transformations, see our
3279 on the official phpMyAdmin-homepage.</p>
3283 MySQL server</a></h4>
3285 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3288 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3289 the quote-character (") is interpreted as an identifier quote character and
3290 not as a string quote character, which makes many internal phpMyAdmin
3292 statements. There is no workaround to this behaviour. News to this item will
3293 be posted in Bug report
3294 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3295 </p>
3299 more that one column with the same value
3300 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3301 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3303 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3304 can use it for the Edit and Delete links.</p>
3309 <p> phpMyAdmin uses a quick method to get the row count, and this method
3310 only returns an approximate count in the case of InnoDB tables. See
3312 a way to modify those results, but
3313 this could have a serious impact on performance.</p>
3318 <p> The number of records in queries containing COUNT and GROUP BY is
3319 not correctly calculated. Also, sorting results of a query like
3324 containing an hyphen.
3325 </a></h4>
3326 <p>
3327 The tests I have made with current MySQL 4.1.11 API shows that the
3328 API does not accept this syntax for the USE command. Enclosing the
3329 db name with backquotes works. For further confusion, no backquotes
3330 are needed with command-line mysql.
3331 </p>
3334 <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>
3335 <p>
3336 This has been a known limitation of phpMyAdmin since the beginning and
3337 it's not likely to be solved in the future.
3338 </p>
3340 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3343 <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
3344 need to install it for each customer.
3345 </a></h4>
3346 <p>
3347 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3348 your users. The development of this feature was kindly sponsored by
3349 NetCologne GmbH.
3350 This requires a properly setup MySQL user management and phpMyAdmin
3351 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3353 </p>
3357 access.
3358 </a></h4>
3359 <p>
3360 This depends on your system.<br />
3361 If you're running a server which cannot be accessed by other people, it's
3362 sufficient to use the directory protection bundled with your webserver
3364 If other people have telnet access to your server, you should use
3365 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3366 <br /><br />
3367 Suggestions:
3368 </p>
3369 <ul>
3370 <li>
3372 </li>
3373 <li>
3374 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3375 is a user whose password is only known to you, and apache is the
3376 group under which Apache runs.
3377 </li>
3378 <li>
3379 You should use PHP safe mode, to protect from other users that try
3381 </li>
3382 </ul>
3387 </a></h4>
3388 <p>
3393 </p>
3396 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3397 authentication.
3398 </a></h4>
3402 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3403 and/or
3405 are wrong.</li>
3407 <li>You have already setup a security mechanism for the
3408 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3409 phpMyAdmin's authentication, so remove it.</li>
3410 </ul>
3417 and put the privileges you want. For example,
3419 would let a user create/manage his/her database(s).</p>
3424 <p> If you have existing rules from an old .htaccess file, you can take them
3427 be a major benefit here if your installation is suited to using it. Then
3428 you can just add those updated lines into the
3432 <p> If you want a pre-made sample, you can try this fragment. It stops the
3433 'root' user from logging in from any networks other than the private
3436 <pre>
3437 //block root from logging in except from the private networks
3438 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3439 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3440 'deny root from all',
3441 'allow root from localhost',
3445 );
3446 </pre>
3451 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3452 different than the one set in your
3454 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3455 while a domain name is defined in the config file.</p>
3460 <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>
3466 when trying to create a table with more than 14 fields.
3467 </a></h4>
3468 <p>
3469 We could reproduce this problem only under Win98/98SE. Testing under
3470 WinNT4 or Win2K, we could easily create more than 60 fields.
3471 <br />
3472 A workaround is to create a smaller number of fields, then come back to
3473 your table properties and add the other fields.
3474 </p>
3478 <p>
3479 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3480 with each script/website that use forms.<br />
3481 Upgrade or downgrade your Xitami server.
3482 </p>
3485 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3486 <p>
3487 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3488 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3489 don't seem to work.<br />
3491 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3492 the user's temporary directory, so they must be moved before closing
3493 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3496 </p>
3500 Explorer never stores the cookies.
3501 </a></h4>
3502 <p>
3503 MS Internet Explorer seems to be really buggy about cookies, at least till
3505 in this area!
3506 <br />
3507 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3508 work!
3509 </p>
3513 rows.
3514 </a></h4>
3515 <p>
3517 </p>
3520 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3521 when trying to modify a row in a table with many fields, or with a text field
3522 </a></h4>
3523 <p>
3524 Your table neither have a primary key nor an unique one, so we must use a
3525 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
3526 those browsers, and this not happen in Netscape, for example. The
3527 workaround is to create a primary or unique key, or use another browser.
3528 <br />
3529 </p>
3533 page.
3534 </a></h4>
3535 <p>
3536 Some browsers support right-clicking into the frame you want to refresh,
3537 just do this in the right frame.<br />
3538 </p>
3542 query box.
3543 </a></h4>
3544 <p>
3545 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3546 Mozilla versions.<br />
3547 </p>
3551 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3552 </a></h4>
3553 <p>
3554 This is a Mozilla bug (see bug #26882 at
3556 </p>
3561 </a></h4>
3562 <p>
3563 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3564 data in octet-stream mode. Since we can't detect the specific Netscape
3565 version, we cannot workaround this bug.
3566 </p>
3570 wrong.</a></h4>
3572 <p> Please ensure that you have set your browser's character set to the one of the
3573 language file you have selected on phpMyAdmin's start page.
3574 Alternatively, you can try the auto detection mode that is supported by the
3575 recent versions of the most browsers.</p>
3578 <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
3581 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3582 Netscape and Mozilla do not have this problem.</p>
3585 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3586 I cannot manage two servers: I log in to the first one, then the other one,
3587 but if I switch back to the first, I have to log in on each operation.</a></h4>
3593 but nothing happens after that, only a blank screen.</a></h4>
3604 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3609 address and you are starting
3611 containing a domain name, or the reverse situation.</li>
3612 <li>Security settings in IE and/or Microsoft Security Center are
3613 too high, thus blocking scripts execution.</li>
3614 <li>The Windows Firewall is blocking Apache and MySQL. You must
3618 </ul>
3621 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3622 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3623 installed in their Firefox is causing the problem.</p>
3627 clause is generated when I browse a table.</a></h4>
3628 <p> This happens only when both of these conditions are met: using the
3637 </a></h4>
3638 <p>
3639 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3640 specifying a wrong field-type.<br />
3641 Common errors include:
3642 </p>
3643 <ul>
3646 </ul>
3647 <p>
3648 Also, look at the syntax chapter in the MySQL manual to confirm that your
3649 syntax is correct.
3650 </p>
3654 phpMyAdmin generates only one index with those two fields.
3655 </a></h4>
3656 <p>
3657 This is the way to create a multi-fields
3658 index. If you want two indexes, create the first one when creating the
3659 table, save, then display the table properties and click the Index link to
3660 create the other index.
3661 </p>
3665 <p>
3666 Since version 2.2.3, you have a checkbox for each field that can be null.
3668 field's value. Since version 2.5.5, you have to use the checkbox to get
3670 a literal NULL in the field, and not a NULL value (this works in PHP4).
3671 </p>
3676 <p> Click on a database or table name in the left frame, the properties will be
3678 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3679 statements that can be used to recreate your database/table.
3680 <br /><br />
3682 transmit the resulting dump to your station. Depending on your PHP
3683 configuration, you will see options to compress the dump. See also the
3685 configuration variable.<br /><br />
3688 this document.</p>
3693 </a></h4>
3695 <p> Click on a database name in the left frame, the properties will be
3697 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3699 the path to your dump filename, or use the Browse button. Then click Go.
3700 <br /><br />
3702 that you upgrade to take advantage of the new features.
3703 <br /><br />
3705 in this document.
3706 </p>
3711 <p> Here is an example with the tables persons, towns and countries, all
3713 table, create it as explained in the configuration section. Then create the
3714 example tables:</p>
3716 <pre>
3717 CREATE TABLE REL_countries (
3718 country_code char(1) NOT NULL default '',
3719 description varchar(10) NOT NULL default '',
3720 PRIMARY KEY (country_code)
3721 ) TYPE=MyISAM;
3723 INSERT INTO REL_countries VALUES ('C', 'Canada');
3725 CREATE TABLE REL_persons (
3726 id tinyint(4) NOT NULL auto_increment,
3727 person_name varchar(32) NOT NULL default '',
3729 country_code char(1) NOT NULL default '',
3730 PRIMARY KEY (id)
3731 ) TYPE=MyISAM;
3733 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3734 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3736 CREATE TABLE REL_towns (
3738 description varchar(30) NOT NULL default '',
3739 PRIMARY KEY (town_code)
3740 ) TYPE=MyISAM;
3742 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3743 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3744 </pre>
3750 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3754 </ul>
3762 <li>In the fields row, choose persons.person_name and click the
3764 <li>Do the same for towns.description and countries.descriptions in the
3767 the correct joins have been generated</li>
3769 </ul>
3773 <p>
3774 Starting from the previous example, create the pma_table_info as explained
3775 in the configuration section, then browse your persons table,
3776 and move the mouse over a town code or country code.
3777 <br /><br />
3778 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3779 enables: drop-down list of possible values.
3780 </p>
3783 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3784 <p>
3787 <br /><br />
3788 Then you need to think about your schema layout. Which tables will go on
3789 which pages?
3790 </p>
3791 <ul>
3797 page and click Go. If you like, you
3799 linked tables onto the new page.</li>
3800 <li>Select the name of the new page (making sure the Edit radio button
3801 is selected) and click Go.</li>
3803 Coordinates are relative; your diagram will
3804 be automatically scaled to fit the page. When initially placing tables
3805 on the page, just pick any coordinates -- say, 50x50. After clicking
3807 position the element correctly.</li>
3809 first be sure to click the Save
3810 button beneath the list of tables and coordinates, to save any changes
3811 you made there. Then scroll all the way down, select the
3813 you want, and click Go.</li>
3814 <li>Internet Explorer for Windows may suggest an incorrect filename when
3819 browsers on Windows, do not have this problem.</li>
3820 </ul>
3824 columns!</a></h4>
3826 <p> No, it's MySQL that is doing
3832 underscores in the database name?</a></h4>
3834 <p> If you do not put a backslash before the underscore, this is a wildcard
3837 john2db ...<br /><br />
3839 If you put a backslash before the underscore, it means that the database
3840 name will have a real underscore.</p>
3844 statistics pages?</a></h4>
3855 if it already exists during the import. It does NOT drop the table after
3856 your export, it only affects the import file.</li>
3858 Otherwise, you may get an error if the table name exists but has a
3859 different structure.</li>
3861 (if any) will be included in backup.</li>
3863 field and table names formed with special characters are protected.</li>
3865 types set in the pmadb in the dump as
3867 </li>
3868 </ul>
3873 command, for better documentation (but resulting file is bigger).</li>
3875 once the INSERT verb and the table name.</li>
3878 </li>
3880 more info is provided in the
3882 but basically with this selected, invalid values are adjusted and
3883 inserted rather than causing the entire statement to fail.</li>
3884 </ul>
3888 in its name.</a></h4>
3891 is the normal way to reference a database and table name. Worse, MySQL
3892 will usually let you create a database with a dot, but then you cannot
3893 work with it, nor delete it.</p>
3906 for usage.<br />
3907 On a more recent pear version, I had problems with the state of Net_DIME
3908 being beta, so this single command
3910 needed modules.<br />
3911 If you use the Validator, you should be aware that any
3913 submit will be stored anonymously (database/table/column names,
3914 strings, numbers replaced with generic values). The Mimer
3917 We utilize it as free SOAP service.</p>
3921 it, but MySQL says "BLOB column '...' used in key specification without
3924 <p> The right way to do this, is to create the field without any indexes,
3926 dialog. On this page, you will be able to choose your BLOB field, and
3927 set a size to the index, which is the condition to create an index on
3928 a BLOB field.</p>
3932 editing fields?</a></h4>
3934 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3935 with many editing fields (table structure changes, row editing, etc.)
3936 (must be enabled in configuration - see.
3938 You can also have a look at the directive
3940 ('vertical') and see if this eases up editing for you.</p>
3944 WTF is this feature then useful for?</a></h4>
3946 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3947 on them. Otherwise you could just put a comment on the field. Because entering
3948 your own mimetype will cause serious syntax checking issues and validation,
3949 this introduces a high-risk false-user-input situation. Instead you have to
3950 initialize mimetypes using functions or empty mimetype definitions.<br />
3951 Plus, you have a whole overview of available mimetypes. Who knows all those
3952 mimetypes by heart so he/she can enter it at will?</p>
3956 can't I see any bookmarks below the query box? What is this variable for?
3957 </a></h4>
3959 <p> Any query you have executed can be stored as a bookmark on the page where the
3960 results are displayed. You will find a button labeled 'Bookmark this query'
3961 just at the end of the page.<br />
3962 As soon as you have stored a bookmark, it is related to the database you run
3963 the query on. You can now access a bookmark dropdown on each page, the query
3964 box appears on for that database.<br /><br />
3966 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3970 aware of that you HAVE to create a valid query, otherwise your query won't be
3971 even able to be stored in the database.<br />
3973 for your query will remain the way it is, but will be stripped of the /**/
3974 chars. So you can use:<br /><br />
3978 which will be expanded to<br /><br />
3982 in your query, where VARIABLE is the string you entered in the input box. If
3983 an empty string is provided, no replacements are made.<br /><br />
3985 A more complex example. Say you have stored this query:<br /><br />
3987 <br /><br />
3990 the full query will be:<br /><br />
3993 <br /><br />
3997 spaces inserted there
3998 will be later also inserted as spaces in your query and may lead to unexpected
3999 results especially when
4001 Your initial query which is going to be stored as a bookmark has to yield at
4002 least one result row so
4003 you can store the bookmark. You may have that to work around using well
4007 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4008 include exported table?</a></h4>
4010 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4011 document should look like following one (assuming you have table
4014 <pre>
4015 \documentclass{article} % or any class you want
4016 \usepackage{longtable} % for displaying table
4017 \begin{document} % start of document
4018 \include{table} % including exported table
4019 \end{document} % end of document
4020 </pre>
4024 access them.
4025 </a></h4>
4028 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4029 enable users to see all the database names.
4032 So if your users do not need those privileges, you can remove them and their
4033 databases list will shorten.</p>
4037 possible values for a field, based on some foreign table?</a></h4>
4039 <p> You have to setup appropriate links between the tables, and also
4043 foreign table, a drop-down list of values will be available.
4044 You will see two lists of values, the first list containing the key
4045 and the display field, the second list containing the display field
4046 and the key. The reason for this is to be able to type the first
4047 letter of either the key or the display field.<br /><br />
4049 For 100 values or more, a distinct window will appear, to browse foreign
4050 key values and choose one. To change the default limit of 100, see
4051 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4055 automatically when entering Browse mode for a table?</a></h4>
4057 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4058 </p>
4062 Excel files, how can I enable that?</a></h4>
4064 <p> Current version does support direct export to Microsoft Excel and Word
4065 versions 2000 and newer. If you need export older versions, you can use
4067 which works out of the box or you can
4069 several problems, most important are limitation of cell content to 255
4070 chars and no support for charsets, so think carefully whether you want to
4071 enable this.</b>. For enabling this you need to set
4075 module Spreadsheet_Excel_Writer into php include path. The
4076 installation can be done by following command:</p>
4078 <pre>
4079 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
4080 </pre>
4082 <p> First part of switches set we want to install beta version of that module
4083 (no stable version available yet) and then we tell pear we want to satisfy
4084 dependencies.</p>
4086 <p> If you are running in PHP safe mode, you will have to set
4089 modules are located, for example:</p>
4091 <pre>
4092 safe_mode_include_dir = /usr/local/lib/php
4093 </pre>
4097 <pre>
4098 cd phpMyAdmin
4099 mkdir tmp
4100 chmod o+rwx tmp
4101 </pre>
4105 what happens to my column comments stored in pmadb?</a></h4>
4107 <p> Automatic migration of a table's pmadb-style column comments to the native
4108 ones is done whenever you enter Structure page for this table.</p>
4113 <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.</p>
4115 <ol>
4116 <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>
4117 <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>
4118 <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>
4119 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4120 <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>
4121 <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>
4122 </ol>
4129 <p> Our Bug Tracker is located at
4131 under the Bugs section.<br /><br />
4133 But please first discuss your bug with other users:<br />
4139 existing language, where do I start?</a></h4>
4141 <p> Always use the current SVN version of your language file.
4143 don't know how to get the SVN version, please ask one of the developers.
4144 <br />
4145 Please note that we try not to use HTML entities like &eacute; in
4146 the translations, since we define the right character set in the file.
4147 With HTML entities, the text on JavaScript messages would not
4148 display correctly.
4149 However there are some entities that need to be there, for quotes
4150 ,non-breakable spaces, ampersands, less than, greater than.<br />
4151 You can then put your translations, as a zip file to avoid losing special
4152 characters, on the sourceforge.net translation tracker.<br />
4153 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4154 list, because this is where we ask for translations of new messages.</p>
4158 phpMyAdmin. How should I proceed?</a></h4>
4163 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4164 </li>
4166 <li>generate patch with your changes:
4168 </li>
4171 tracker of the phpMyAdmin project</a>.
4172 </li>
4173 </ol>
4175 <p> Write access to the SVN tree is granted only to experienced developers who
4176 have already contributed something useful to phpMyAdmin.<br />
4182 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4184 <p> Please refer to
4185 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4186 </p>
4191 <p> If you use Apache web server, phpMyAdmin exports information about
4192 authentication to Apache environment and it can be used in Apache logs.
4193 Currently there are two variables available:
4194 </p>
4195 <dl>
4197 <dd>User name of currently active user (he does not have to be logged
4198 in).</dd>
4205 </dl>
4206 <p>
4208 </p>
4209 <pre>
4212 </pre>
4213 <p>
4214 You can then use any log analyzing tools to detect possible break in
4215 attempts.
4216 </p>
4218 <!-- DEVELOPERS -->
4221 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4222 great features have been written by other people and you too can help to
4223 make phpMyAdmin a useful tool.</p>
4225 <p> If you're planning to contribute source, please read the following
4226 information:</p>
4232 it free from other code.<br />
4233 Commonly used functions should be added to
4236 <li>Obviously, you're free to use whatever coding style you want. But
4237 please try to keep your code as simple as possible: beginners are
4238 using phpMyAdmin as an example application.<br />
4239 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4240 compliant on one hand, they fit the
4243 coding standards</a>
4244 on the other hand. Please pay attention to this.</li>
4245 <li>Please try to keep up the file-naming conventions. Table-related stuff
4248 <li>Please don't put message strings in your code, instead add the string
4253 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4254 better debug and profile their code.<br />
4255 Please see the
4257 options for more information.<br />
4258 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4259 lost during its re-entry into Earth's atmosphere and in memory of the
4260 brave men and women who gave their lives for the people of Earth.</li>
4261 </ul>
4265 <pre>
4277 This program is free software; you can redistribute it and/or modify
4278 it under the terms of the GNU General Public License version 2,
4279 as published by the Free Software Foundation.
4281 This program is distributed in the hope that it will be useful,
4282 but WITHOUT ANY WARRANTY; without even the implied warranty of
4283 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4284 GNU General Public License for more details.
4286 You should have received a copy of the GNU General Public License
4287 along with this program; if not, write to the Free Software
4289 </pre>
4291 <!-- CREDITS -->
4294 <pre>
4295 phpMyAdmin - Credits
4296 ====================
4298 CREDITS, in chronological order
4299 -------------------------------
4302 * creator of the phpmyadmin project
4306 * multi-language version
4307 * various fixes and improvements
4309 * current project maintainer
4312 * started SourceForge phpMyAdmin project in March 2001
4313 * sync'ed different existing CVS trees with new features and bugfixes
4314 * multi-language improvements, dynamic language selection
4315 * current project maintainer
4316 * many bugfixes and improvements
4319 * rewrote and optimized javascript, DHTML and DOM stuff
4320 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4321 generate XHTML1.0 and CSS2 compliant codes
4322 * improved the language detection system
4323 * many bugfixes and improvements
4326 * database maintenance controls
4327 * table type code
4329 * DB-based configuration (Not completed)
4332 * many bugfixes and improvements
4335 * bookmarks feature
4336 * multiple dump feature
4337 * gzip dump feature
4338 * zip dump feature
4341 * various fixes
4342 * moderator of the phpMyAdmin former users forum at phpwizard.net
4348 * rewrote and fix dump code
4349 * bugfixes
4352 * rewrote dump code for PHP4
4353 * mySQL table statistics
4354 * bugfixes
4357 * main author of the version 2.1.0.1
4358 * bugfixes
4362 * abstract database interface (PMA_DBI) with MySQLi support
4363 * privileges administration
4365 * various features and fixes
4366 * German language file updates
4369 * automatic joins in QBE
4370 * links column in printview
4371 * Relation view
4374 * enhanced index creation/display feature
4375 * feature to use a different charset for HTML than for MySQL
4376 * improvements of export feature
4377 * various features and fixes
4378 * Czech language file updates
4381 (http://sf.net/projects/phpmysqlformgen/)
4382 * suggested the patch for multiple table printviews
4385 * built the patch for vertical display of table rows
4386 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4387 * Improvement of column/db comments
4388 * (MIME)-Transformations for columns
4389 * Use custom alias names for Databases in left frame
4390 * hierarchical/nested table display
4391 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4392 * new icon sets
4393 * vertical display of column properties page
4394 * some bugfixes, features, support, German language additions
4397 * japanese kanji encoding conversion feature
4400 * the Cookie authentication mode
4403 * table relation-links feature
4406 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4407 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4408 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4414 * phpMyAdmin logo (until June 2004)
4417 * blowfish library from the Horde project
4420 * mysqli support
4421 * many bugfixes and improvements
4424 * redesign for 2.6.0
4425 * phpMyAdmin sailboat logo (June 2004)
4428 * Representation at conferences
4431 * interface improvements
4432 * various bugfixes
4434 - Ivan A Kirillov
4435 * new relations Designer
4437 - Raj Kissu Rajandran (Google Summer of Code 2008)
4438 * BLOBstreaming support
4440 - Piotr Przybylski (Google Summer of Code 2008)
4441 * improved setup script
4443 And also to the following people who have contributed minor changes,
4444 enhancements, bugfixes or support for a new language since version 2.1.0:
4446 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4447 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4448 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4449 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4451 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4452 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4453 Luís V., Martijn W. van der Lee,
4454 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4458 Original Credits of Version 2.1.0
4459 ---------------------------------
4461 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4462 to create a web-based interface to MySQL using PHP3. Although I have not
4463 used any of his source-code, there are some concepts I've borrowed from
4464 him. phpMyAdmin was created because Peter told me he wasn't going to
4465 further develop his (great) tool.
4466 Thanks go to
4468 code for the check when dropping a table or database. He also suggested
4469 that you should be able to specify the primary key on tbl_create.php3. To
4470 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4471 well as a bug-report. Plus many smaller improvements.
4473 were introduced in 1.3.0 (including quite significant ones like the
4474 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4475 bug-fixes and help.
4477 language-independent by outsourcing the strings to a separate file. He
4478 also contributed the French translation.
4480 tbl_select.php3, a feature to display only some fields from a table.
4482 functions in tbl_change.php3. He also added the
4485 servers and is a regular contributor for bug-fixes.
4487 features for 2.0.6.
4488 The following people have contributed minor changes, enhancements, bugfixes
4489 or support for a new language:
4490 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4491 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4492 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4493 G. Wieggers.
4495 And thanks to everyone else who sent me email with suggestions, bug-reports
4496 and or just some feedback.
4497 </pre>
4503 <ul>
4505 - the default name of Apache's directory-level configuration file.</li>
4509 - a software application that enables a user to display and interact with
4510 text, images, and other information typically located on a web page at a
4511 website on the World Wide Web.</li>
4513 - a free software/open source data compression algorithm and program
4514 developed by Julian Seward.</li>
4516 - an important World Wide Web technology that enables a client web browser
4517 to request data from a program executed on the Web server.</li>
4519 - a log or record of changes made to a project.</li>
4521 - a computer system that accesses a (remote) service on another computer
4522 by some kind of network.</li>
4524 - a set of data values of a particular simple type, one for each row of
4525 the table.</li>
4527 - a packet of information sent by a server to a World Wide Web browser
4528 and then sent back by the browser each time it accesses that server.</li>
4530 - Comma-separated values</li>
4533 - an organized collection of data.</li>
4536 - a PHP module that extends PHP with additional functionality.</li>
4538 - a list of commonly asked question and there answers.</li>
4540 - one part of divided data/columns.</li>
4542 - a field or group of fields in a database record that point to a key
4543 field or group of fields forming a key of another database record in some
4544 (usually different) table.</li>
4546 - the free PDF library</li>
4548 GD Graphics Library</a> - a library by Thomas Boutell and others for
4549 dynamically manipulating images.</li>
4552 - gzip is short for GNU zip, a GNU free software file compression
4553 program.</li>
4555 - any machine connected to a computer network, a node that has a hostname.</li>
4557 - the unique name by which a network attached device is known on a network.</li>
4559 (HyperText Transfer Protocol)</a>
4560 - the primary method used to transfer or convey information on the World
4561 Wide Web.</li>
4564 additional security measures.</li>
4565 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4566 - a set of Internet-based services for servers using Microsoft Windows.</li>
4568 - a feature that allows quick access to the rows in a table.</li>
4570 - a data-oriented protocol used by source and destination hosts for
4571 communicating data across a packet-switched internetwork.</li>
4573 - a unique number that devices use in order to identify and communicate
4574 with each other on a network utilizing the Internet Protocol standard.</li>
4576 (Internet Server Application Programming Interface)</a>
4577 - the API of Internet Information Services (IIS).</li>
4579 - a business or organization that offers users access to the Internet and related services.</li>
4581 - a most commonly used standard method of lossy compression for
4582 photographic images.</li>
4588 - line of personal computers is designed, developed, manufactured, and
4589 marketed by Apple Computer.</li>
4590 <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>
4591 - the operating system which is included with all currently shipping Apple
4592 Macintosh computers in the consumer and professional markets.</li>
4594 - a cryptographic library.</li>
4596 - the MCrypt PHP extension.</li>
4597 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4598 - an Internet Standard for the format of e-mail.</li>
4600 - some sort of extension for the Apache Webserver.</li>
4602 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4603 Management System (DBMS).</li>
4605 - the improved MySQL client PHP extension.</li>
4607 - the MySQL client PHP extension.</li>
4609 - open standard for office documents.</li>
4610 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4611 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4613 (Portable Document Format)</a>
4614 - a file format developed by Adobe Systems for representing two
4615 dimensional documents in a device independent and resolution independent
4616 format.</li>
4618 - the PHP Extension and Application Repository.</li>
4620 - the perl-compatible regular expression functions for PHP</li>
4622 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4623 programming language used mainly for developing server-side applications
4624 and dynamic web content, and more recently, a broader range of software
4625 applications.</li>
4627 - a connection through which data is sent and received.</li>
4629 - Request for Comments (RFC) documents are a series of memoranda
4630 encompassing new research, innovations, and methodologies applicable to
4631 Internet technologies.</li>
4635 - represents a single, implicitly structured data item in a table.</li>
4637 - a computer system that provides services to other computing
4638 systems over a network.</li>
4639 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4640 - handlers for different table types</li>
4642 - a form of inter-process communication.</li>
4644 Sockets Layer)</a>
4645 - a cryptographic protocol which provides secure communication on the Internet.</li>
4647 - Structured Query Language</li>
4649 - a set of data elements (cells) that is organized, defined and stored as
4650 horizontal rows and vertical columns where each item can be uniquely
4651 identified by a label or key or by it?s position in relation to other items.</li>
4654 - a type of archive file format: the Tape ARchive format.</li>
4656 - one of the core protocols of the Internet protocol suite.</li>
4660 - a sequence of characters, conforming to a standardized format, that is
4661 used for referring to resources, such as documents and images on the
4662 Internet, by their location.</li>
4664 - A computer (program) that is responsible for accepting HTTP requests
4665 from clients and serving them Web pages.</li>
4667 - a W3C-recommended general-purpose markup language for creating
4668 special-purpose markup languages, capable of describing many different
4669 kinds of data.</li>
4671 - a popular data compression and archival format.</li>
4673 - an open-source, cross-platform data compression library by Jean-loup
4674 Gailly and Mark Adler.</li>
4675 </ul>
4676 </div>
4680 <li>Copyright © 2003 - 2009 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
4683 <li class="last">Valid <a href="http://validator.w3.org/check/referer">HTML</a> and <a href="http://jigsaw.w3.org/css-validator/check/referer">CSS</a></li>
4684 </ul>
4685 </body>
4686 </html>