| blob | 635066878d21c93b55e6e21f7cad44035817121a |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 </li>
63 <li>You need GD2 support in PHP to display inline
65 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
198 provided for those who prefer a graphical installation. Creating a
200 still a quick way to get started and needed for some advanced features.
201 <ul><li>To manually create the file, simply use your text editor to
204 file) in the main (top-level) phpMyAdmin directory (the one
208 default value is okay for a particular setting, there is no
210 few directives to get going, a simple configuration may look
211 like this:
212 <pre>
213 <?php
214 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
216 $i=0;
217 $i++;
218 $cfg['Servers'][$i]['auth_type'] = 'cookie';
219 ?>
220 </pre>
221 Or, if you prefer to not be prompted every time you log in:
222 <pre>
223 <?php
225 $i=0;
226 $i++;
227 $cfg['Servers'][$i]['user'] = 'root';
228 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
229 ?>
230 </pre>
231 For a full explanation of possible configuration values, see the
237 directory. This is a security measure. On a Linux/Unix system you
238 can use the following commands:
239 <pre>
240 cd phpMyAdmin
241 mkdir config # create directory for saving
242 chmod o+rw config # give it world writable permissions
243 </pre>
244 And to edit an existing configuration, copy it over first:
245 <pre>
246 cp config.inc.php config/ # copy current configuration for editing
247 chmod o+w config/config.inc.php # give it world writable permissions
248 </pre>
249 On other platforms, simply create the folder and ensure that your
258 the webserver does not have the proper permissions you may see the
260 config/</tt> directory exists and has the proper permissions -
262 and upload (via FTP or some similar means) to the proper location.<br /><br />
264 Once the file has been saved, it must be moved out of the <tt>
265 config/</tt> directory and the permissions must be reset, again
266 as a security measure:
267 <pre>
268 mv config/config.inc.php . # move file to current directory
269 chmod o-rw config.inc.php # remove world read and write permissions
270 </pre>
271 Now the file is ready to be used. You can choose to review or edit
272 the file with your favorite editor, if you prefer to set some
273 advanced options which the setup script does not provide.</li></ul></li>
274 <li>If you are using the
276 protect the phpMyAdmin installation directory because using
277 config does not require a user to
278 enter a password to access the phpMyAdmin installation. Use of an alternate
279 authentication method is recommended, for example with
287 in your browser. phpMyAdmin should now display a welcome screen
288 and your databases, or a login dialog if using
290 authentication mode.</li>
292 webserver configuration. For Apache you can use supplied .htaccess file
293 in that folder, for other webservers, you should configure this yourself.
294 Such configuration prevents from possible path exposure and cross side
295 scripting vulnerabilities that might happen to be found in that code.</li>
296 </ol>
300 <p> For a whole set of new features (bookmarks, comments,
303 transformation, etc.) you need to create a set of special tables. Those
304 tables can be located in your own database, or in a central database for a
305 multi-user installation (this database would then be accessed by the
306 controluser, so no other user should have rights to it).</p>
315 installation.</p>
320 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
321 that you may need special (administrator) privileges to create the database
322 and tables, and that the script may need some tuning, depending on the
323 database name.</p>
328 section</a>. You will also need to have a controluser with the proper rights
335 unpacked one. Configuration files from very old versions (2.3.0 or before) may
336 require some tweaking as some options have been changed or removed.
338 statement that you might find near the end of your configuration file.</p>
342 is version-specific.</p>
345 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
346 you should run the SQL script found in
353 where you want to give users access to their own database and don't want
354 them to play around with others.<br />
355 Nevertheless be aware that MS Internet Explorer seems to be really buggy
357 in this area!<br />
360 that your user/password pair are not in clear in the configuration file.
361 </li>
364 authentication modes are more secure: the MySQL login information does
365 not need to be set in the phpMyAdmin configuration file (except possibly
367 However, keep in mind that the password travels in plain text, unless
368 you are using the HTTPS protocol.<br />
369 In cookie mode, the password is stored, encrypted with the blowfish
370 algorithm, in a temporary cookie.</li>
373 your MySQL server is previous to 4.1.2, or is running with
383 file under the
385 $cfg['Servers'][$i]['controluser']</a></tt> and
390 only an example: use something else in your file!</b> Input these
391 statements from the phpMyAdmin SQL Query window or mysql command–line
392 client.<br />
394 if it's not the same as the MySQL server's one.
396 <pre>
397 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
398 GRANT SELECT (
399 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
400 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
401 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
402 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
403 Execute_priv, Repl_slave_priv, Repl_client_priv
404 ) ON mysql.user TO 'pma'@'localhost';
405 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
406 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
407 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
408 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
410 If you are using an old MySQL version (below 4.0.2), please replace
411 the first GRANT SELECT query by this one:
413 <pre>
414 GRANT SELECT (
415 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
416 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
417 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
418 ) ON mysql.user TO 'pma'@'localhost';</pre>
420 ... and if you want to use the many new relation and bookmark features:
422 <pre>
424 </pre>
428 Of course, the above queries only work if your MySQL version supports
432 on a set of particular databases. Normally you shouldn't give global
433 privileges to an ordinary user, unless you understand the impact of those
434 privileges (for example, you are creating a superuser).<br />
438 <pre>
439 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
440 </pre>
442 What the user may now do is controlled entirely by the MySQL user
443 management system.<br />
445 authentication mode, you don't need to fill the user/password fields
447 array.</li>
448 </ul>
453 method and allows you to log in as any valid MySQL user.</li>
454 <li>Is supported with most PHP configurations. For
467 mode.</li>
468 </ul>
472 <ul><li>You can use this method as a replacement for the
474 (for example, if you're running
476 <li>Obviously, the user must enable cookies in the browser, but this is
477 now a requirement for all authentication modes.</li>
478 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
479 with the same username.</li>
480 <li>If you want to log in to arbitrary server see
485 not required.</li>
486 </ul>
490 <ul><li>This mode is a convenient way of using credentials from another
491 application to authenticate to phpMyAdmin.</li>
492 <li>The other application has to store login information into
493 session data.</li>
495 section.</li>
496 </ul>
499 <ul><li>This mode is the less secure one because it requires you to fill the
501 $cfg['Servers'][$i]['user']</a> and
503 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
504 can read your config.inc.php can discover your username and password).
505 <br />
512 is an entry explaining how to protect your configuration file.</li>
513 <li>For additional security in this mode, you may wish to consider the Host
514 authentication
516 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
518 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
519 directives.</li>
520 <li>Unlike cookie and http, does not require a user to log in when first
521 loading the phpMyAdmin site. This is by design but could allow any
522 user to access your installation. Use of some restriction method is
524 HTTP-AUTH directive or disallowing incoming HTTP requests at
525 one’s router or firewall will suffice (both of which
526 are beyond the scope of this manual but easily searchable with Google).</li>
527 </ul>
529 <!-- CONFIGURATION -->
533 users:</span> PHP does not seem to like
537 before saving a script you have modified.</p>
542 section to create one. This file only needs to contain the parameters you want to
543 change from their corresponding default value in
546 <p> The parameters which relate to design (like colors) are placed in
549 your site specific code to be included on start and end of each page.</p>
553 (with full path) to your phpMyAdmin installation's directory.
556 some web servers are case–sensitive.
559 Starting with version 2.3.0, it is advisable to try leaving this
560 blank. In most cases phpMyAdmin automatically detects the proper
561 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
562 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
563 A good test is to browse a table, edit a row and save it. There should
564 be an error message if phpMyAdmin is having trouble auto–detecting
565 the correct value. If you get an error that this must be set or if
566 the autodetect code fails to detect your path, please post a bug
567 report on our bug tracker so we can improve the code.</dd>
571 with master / foreign – tables (see
573 <br />
574 If you tried to set this up and it does not work for you, have a look on
576 use it. You will find a link that will analyze why those features have
577 been disabled.<br />
578 If you do not want to use those features set this variable to
583 algorithm to encrypt the password.<br />
585 passphrase of your choice. It will be used internally by the blowfish
586 algorithm: you won’t be prompted for this passphrase. The maximum
591 MySQL servers. Therefore, a
593 been added which contains the login information for the different servers.
594 The first
596 contains the hostname of the first server, the second
598 the hostname of the second server, etc. In
600 server definition, however you can put as many as you need in
602 have to define all settings, just those you need to change).</dd>
606 $i-th MySQL-server. E.g. localhost.</dd>
611 ignores this port number and connects with the socket, so if you want
612 to connect to a port different from the default port, use
615 </dd>
619 To determine the correct socket, check your MySQL configuration or, using the
621 Among the resulting information displayed will be the socket used.</dd>
624 <dd>Whether to enable SSL for connection to MySQL server.
625 </dd>
628 <dd>What type connection to use with the MySQL server. Your options are
630 is nearly guaranteed to be available on all MySQL servers, while
631 sockets are not supported on some platforms.<br /><br />
633 To use the socket mode, your MySQL server must be on the same machine
634 as the Web server.</dd>
637 <dd>What php MySQL extension to use for the connection. Valid options are:
638 <br /><br />
641 The classic MySQL extension. This is the recommended and default
642 method at this time.<br /><br />
645 The improved MySQL extension. This extension became available
646 with php 5.0.0 and is the recommended way to connect to a server
650 <dd>Whether to use a compressed protocol for the MySQL server connection
651 or not (experimental).<br />
657 </dt>
659 all relational features (see
661 and, for a MySQL server previous to 4.1.2 or running with
664 authentication mode).<br /><br />
667 cookie authentication modes (or 'config'
668 authentication mode since phpMyAdmin 2.2.1), you need to supply the
673 This account is used to check what databases the user will see at
674 login.<br />
678 In phpMyAdmin versions before 2.2.5, those were called
682 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
683 <dd>Whether config or cookie or
685 should be used for this server.
687 is the plain old way: username and password are stored in
689 <li>'cookie' authentication mode
691 2.2.3 allows you to log in as any valid MySQL user with the
692 help of cookies. Username and password are stored in
693 cookies during the session and password is deleted when it
694 ends. This can also allow you to log in in arbitrary server if
695 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
696 </li>
697 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
698 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
699 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
700 <li>'signon' authentication mode
702 as introduced in 2.10.0 allows you to log in from prepared PHP
703 session data. This is useful for implementing single signon
704 from another application. Sample way how to seed session is in
710 </ul>
713 for more information.
714 </dd>
718 </dt>
719 <dd>
720 When using auth_type = 'config', this is the user/password-pair
721 which phpMyAdmin will use to connect to the
722 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
723 cookie authentication is used and should be empty.</dd>
725 <span
727 </dt>
728 <dd>
729 Allow attempt to log in without password when a login with password
730 fails. This can be used together with http authentication, when
731 authentication is done some other way and phpMyAdmin gets user name
732 from auth and uses empty password for connecting to MySQL. Password
733 login is still tried first, but as fallback, no password method is
734 tried.</dd>
737 </dt>
738 <dd>
739 If set to a (an array of) database name(s), only this (these) database(s)
740 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
741 database(s) name(s) may contain MySQL wildcards characters
745 This setting is an efficient way to lower the server load since the
746 latter does not need to send MySQL requests to build the available
748 privileges rules of the MySQL database server</span>. If set, it just
749 means only these databases will be displayed but
751 <br /><br />
753 An example of using more that one database:
755 <br /><br />
757 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
758 databases in the left frame, so that you can individually arrange your databases.<br />
759 If you want to have certain databases at the top, but don't care about the others, you do not
760 need to specify all other databases. Use:
762 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
763 order.</dd>
766 </dt>
767 <dd>Regular expression for hiding some databases. This only hides them
768 from listing, but a user is still able to access them (using, for example,
769 the SQL query area). To limit access, use the MySQL privilege system.
770 <br /><br />
775 More information on regular expressions can be found in the
777 PCRE pattern syntax</a> portion of the PHP reference manual.
778 </dd>
781 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
782 this string will be displayed instead of the hostname in the pull-down
783 menu on the main page. This can be useful if you want to show only
784 certain databases on your system, for example. For HTTP auth, all
785 non-US-ASCII characters will be stripped.</dd>
789 </dt>
790 <dd>The name of the database containing the linked-tables infrastructure.
791 <br /><br />
794 section in this document to see the benefits of this infrastructure,
795 and for a quick way of creating this database and the needed tables.
796 <br /><br />
798 If you are the only user of this phpMyAdmin installation, you can
799 use your current database to store those special tables; in this
800 case, just put your current database name in
802 set this parameter to the name of your central database containing
803 the linked-tables infrastructure.</dd>
807 </dt>
809 useful for queries you often run.<br /><br />
811 To allow the usage of this functionality:
813 <li>enter the table name in
815 </ul>
816 </dd>
820 </dt>
822 which field is a key in another table (a foreign key). phpMyAdmin
823 currently uses this to
824 <ul><li>make clickable, when you browse the master table, the data values
825 that point to the foreign table;</li>
827 when browsing the master table, if you move the mouse to a column
828 containing a foreign key (use also the 'table_info' table);<br />
831 <li>in edit/insert mode, display a drop-down list of possible foreign
835 <li>display links on the table properties page, to check referential
836 integrity (display missing foreign keys) for each described key;
837 </li>
841 schema of your database (also uses the table_coords table).</li>
842 </ul>
844 The keys can be numeric or character.<br /><br />
846 To allow the usage of this functionality:
849 infrastructure</li>
850 <li>put the relation table name in
852 <li>now as normal user open phpMyAdmin and for each one of your
853 tables where you want to use this feature, click
855 </li>
856 </ul>
860 future development of the cross-db relations.
861 </dd>
865 </dt>
866 <dd>
867 Since release 2.3.0 you can describe, in a special 'table_info'
868 table, which field is to be displayed as a tool-tip when moving the
869 cursor over the corresponding key.<br />
870 This configuration variable will hold the name of this special
871 table. To allow the usage of this functionality:
873 <li>put the table name in
875 <li>then for each table where you want to use this feature,
877 to choose the field.</li>
878 </ul>
880 </dd>
884 </dt>
887 the relations between your tables. To do this it needs two tables
892 schema output).<br /><br />
896 To allow the usage of this functionality:
899 infrastructure</li>
900 <li>put the correct table names in
903 </ul>
906 </dd>
910 </dt>
912 Since release 2.3.0 you can store comments to describe each column for
914 <br /><br />
916 Starting with release 2.5.0, comments are consequently used on the table
917 property pages and table browse view, showing up as tool-tips above the
918 column name (properties page) or embedded within the header of table in
919 browse view. They can also be shown in a table dump. Please see the
920 relevant configuration directives later on.<br /><br />
922 Also new in release 2.5.0 is a MIME-transformation system which is also
924 Transformations</a> for further information. To use the
925 MIME-transformation system, your column_info table has to have the three
926 new fields 'mimetype', 'transformation', 'transformation_options'.
927 <br /><br />
929 To allow the usage of this functionality:
931 infrastructure</li>
932 <li>put the table name in
936 <pre>
937 ALTER TABLE `pma_column_comments`
938 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
939 ADD `transformation` VARCHAR( 255 ) NOT NULL,
940 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
941 </pre>
944 renamed from<br />
947 </ul>
948 </dd>
952 </dt>
955 all queries you entered manually into the phpMyAdmin interface. If you
956 don't want to use a table-based history, you can use the JavaScript-based
957 history. Using that, all your history items are deleted when closing the
958 window.<br /><br />
960 Using
962 you can specify an amount of history items you want to have on hold. On
963 every login, this list gets cut to the maximum amount.<br /><br />
965 The query history is only available if JavaScript is enabled in your
966 browser.<br /><br />
968 To allow the usage of this functionality:
971 infrastructure</li>
973 </li>
974 </ul>
975 </dd>
979 </dt>
981 to visually manage the relations.
982 <br /><br />
984 To allow the usage of this functionality:
987 infrastructure</li>
989 </li>
990 </ul>
991 </dd>
994 </dt>
996 column_info table got enhanced with three new fields. If the above variable
998 latest table structure available. If not, it will emit a warning to the
999 superuser.<br /><br />
1001 You can disable this checking behavior by setting the variable to false,
1002 which should offer a performance increase.<br /><br />
1004 Recommended to set to FALSE, when you are sure, your table structure is
1005 up to date.</dd>
1007 boolean</dt>
1008 <dd>Whether to allow root access. This is just simplification of rules below.
1009 </dd>
1012 </dt>
1014 authentication is disabled.<br /><br />
1017 all deny rules followed by allow rules. Access is allowed by default. Any
1018 client which does not match a Deny command or does match an Allow command
1019 will be allowed access to the server. <br /><br />
1022 applies all allow rules followed by deny rules. Access is denied by
1023 default. Any client which does not match an Allow directive or does
1024 match a Deny directive will be denied access to the server.<br /><br />
1026 If your rule order is set to 'explicit', the authentication is
1027 performed in a similar fashion to rule order 'deny,allow', with the
1031 and was available in Apache by specifying allow and deny rules without
1032 setting any order.<br /><br />
1034 Please also see <a
1036 address behind proxies.
1037 </dd>
1039 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1040 </dt>
1041 <dd>The general format for the rules is as such:
1043 <pre>
1045 </pre>
1050 well (please note that those containing SERVER_ADDRESS might not be
1051 available on all webservers):
1052 <pre>
1058 </pre>
1060 Having an empty rule list is equivalent to either using
1066 following work:<br />
1068 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1069 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1070 But the following does not work:<br />
1073 </dd>
1074 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1075 <dd>Name of session which will be used for signon authentication method.
1076 </dd>
1078 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1079 </dd>
1081 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1082 </dd>
1085 <dd>If you have more than one server configured, you can set
1087 that server when phpMyAdmin is started, or set it to 0 to be given a
1088 list of servers without logging in.<br />
1090 MUST be set to that server.</dd>
1093 <dd>The maximum number of database names to be displayed in the
1094 navigation frame and the database list.</dd>
1097 <dd>The maximum number of table names to be displayed in the
1098 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1099 when in Light mode.</dd>
1102 <dd>The maximum number of characters when a SQL query is displayed. The
1103 default limit of 1000 should be correct to avoid the display of tons
1104 of hexadecimal codes that represent BLOBs, but some users have real
1108 <dd>Defines whether to use GZip output buffering for increased
1110 Set to true/false for enabling/disabling. When set to 'auto' (string),
1111 phpMyAdmin tries to enable output buffering and will automatically disable
1112 it if your browser has some problems with buffering. IE6 with a certain patch
1113 is known to cause data corruption when having enabled buffering.</dd>
1116 <dd>Whether persistent connections should be used or not (mysql_connect or
1117 mysql_pconnect).</dd>
1123 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1124 to zero, no time limit is imposed.<br />
1125 This setting is used while importing/exporting dump files but has no
1126 effect when PHP is running in safe mode.</dd>
1129 <dd>Set the number of bytes a script is allowed to allocate. If number set
1130 to zero, no limit is imposed.<br />
1131 This setting is used while importing/exporting dump files but has no
1132 effect when PHP is running in safe mode.<br />
1136 <dd>Mark used tables and make it possible to show databases with locked
1141 generated by phpMyAdmin should be displayed or not.</dd>
1144 <dd>Defines whether normal users (non-administrator) are allowed to
1145 delete their own database or not. If set as FALSE, the link "Drop
1147 mydatabase" will be rejected. Quite practical for
1149 customers.<br />
1150 Please note that this limitation of SQL queries is not as strict as
1151 when using MySQL privileges. This is due to nature of SQL queries
1152 which might be quite complicated. So this choice should be viewed as
1153 help to avoid accidental dropping rather than strict privilege
1154 limitation.</dd>
1158 displayed when you're about to lose data.</dd>
1161 <dd>Define whether the previous login should be recalled or not in cookie
1162 authentication mode.</dd>
1169 means that it will be kept for existing session. This is recommended
1170 for not trusted environments.</dd>
1173 <dd>If enabled (default), logout deletes cookies for all servers,
1174 otherwise only for current one. Setting this to false makes it easy to
1175 forget to log out from other server, when you are using more of
1176 them.</dd>
1182 <dd>Define whether phpMyAdmin will continue executing a multi-query
1183 statement if one of the queries fails. Default is to abort execution.</dd>
1186 <dd>Define whether phpMyAdmin will output the results of each query of a
1187 multi-query statement embedded into the
1192 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1193 <br /><br />
1196 MySQL servers behind the firewall where your
1198 </dd>
1201 <dd>Defines whether to use a select-based menu and display only the current
1202 tables in the left frame (smaller page). Only in Non-Lightmode you can
1203 use the feature to display nested folders using
1205 </dd>
1208 <dd>In light mode, defines whether to display the names of databases (in the
1209 selector) using a tree, see also
1211 </dd>
1214 <dd>The string used to separate the parts of the database name when showing
1215 them in a tree.</dd>
1218 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1219 This means if you have tables like 'first__second__third' this will be
1221 If set to FALSE or empty, the feature is disabled. NOTE: You should
1222 not use this separator at the beginning or end of a
1223 table name or multiple times after another without any other
1224 characters in between.</dd>
1227 <dd>Defines how many sublevels should be displayed when splitting
1228 up tables by the above separator.</dd>
1231 <dd>Defines whether to display table comment as tool-tip in left frame or
1232 not.</dd>
1235 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1236 comment and the real name. That means that if you have a table called
1237 'user0001' and add the comment 'MyName' on it, you will see the name
1238 'MyName' used consequently in the left frame and the tool-tip shows
1239 the real name of the DB.</dd>
1242 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1244 When setting this to 'nested', the Alias of the Tablename is only used
1245 to split/nest the tables according to the
1247 directive. So only the folder is called like the Alias, the tablename itself
1248 stays the real tablename.</dd>
1251 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1254 <dd>Enter URL where logo in the navigation frame will point to.
1255 For use especially with self made theme which changes this.
1264 <dd>Defines whether or not to display a server choice at the top of the left frame.
1265 Defaults to FALSE.</dd>
1267 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1268 Defaults to FALSE (drop-down).</dd>
1270 <dd>Defines whether to display database choice in light navigation frame as links
1271 instead of in a drop-down. Defaults to 'auto' - on main page list is
1272 shown, when database is selected, only drop down is displayed.</dd>
1274 <dd>Defines whether or not to display space usage and statistics about databases
1275 and tables.<br />
1276 Note that statistics requires at least MySQL 3.23.3 and that, at this
1277 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1280 <dd>Defines whether to display detailed server information on main page.
1281 You can additionally hide more information by using
1283 </dd>
1288 </dt>
1291 not at the starting main (right) frame. This setting
1292 does not check MySQL commands entered directly.<br /><br />
1294 Please note that to block the usage of phpinfo() in scripts, you
1301 hard coded password value in the configuration file, end users can't
1302 be allowed to change their passwords.</dd>
1305 <dd>Defines whether to suggest a database name on the
1310 content.</dd>
1313 <dd>Defines whether navigation bar buttons and the right panel top menu
1314 contain text or symbols only. A value of TRUE displays icons, FALSE
1315 displays text and 'both' displays both icons and text.</dd>
1318 <dd>Defines whether a user should be displayed a
1322 <dd>Number of rows displayed when browsing a result set. If the result set
1329 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1333 from editing when browsing a table's content. Valid values are:
1338 </ul>
1339 </dd>
1342 <dd>Defines whether or not MySQL functions fields should be initially
1343 displayed in edit/insert mode. Since version 2.10, the user can
1344 toggle this setting from the interface.
1345 </dd>
1348 <dd>Defines which type of editing controls should be used for CHAR and
1349 VARCHAR fields. Possible values are:
1350 <ul><li>input - this allows to limit size of text to size of field in
1351 MySQL, but has problems with newlines in fields</li>
1352 <li>textarea - no problems with newlines in fields, but also no
1353 length limitations</li>
1354 </ul>
1355 Default is old behavior so input.</dd>
1361 <dd>If there are fewer items than this in the set of foreign keys, then a
1362 drop-down box of foreign keys is presented, in the style described by the
1364 setting.</dd>
1367 <dd>For the foreign key drop-down fields, there are several methods of
1368 display, offering both the key and value data. The contents of the
1369 array should be one or both of the following strings:
1375 </dt>
1376 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1377 creating a dump file</dd>
1380 </dt>
1381 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1382 compressed exports. This doesn't affect smaller dumps and allows users to
1383 create larger dumps that won't otherwise fit in memory due to php
1384 memory limit. Produced files contain more GZip/BZip2 headers, but all
1385 normal programs handle this correctly.</dd>
1389 mainframe.</dd>
1393 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1398 <dd>How many columns will be utilized to display the tables on the
1399 database property view? Default is 1 column. When setting this to a
1400 value larger than 1, the type of the database will be omitted for more
1401 display space.</dd>
1405 <dd>Defines the tab displayed by default on server view. Possible
1412 <dd>Defines the tab displayed by default on database view. Possible
1417 <dd>Defines the tab displayed by default on table view. Possible
1424 points to the MySQL documentation (type depends
1425 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1426 generated.<br />
1428 for more information about MySQL manuals and their types.</dd>
1431 <dd>Type of MySQL documentation:
1437 </ul>
1438 </dd>
1441 <dd>Defines the default language to use, if not browser-defined or
1442 user-defined.<br />
1444 this setting.</dd>
1447 <dd>Defines the default connection collation to use, if not
1448 user-defined.<br />
1453 <dd>Force: always use this language (must be defined in the
1457 <dd>Limit list of available languages to those matching the given regular
1458 expression. For example if you want only Czech and English, you should
1462 <dd>Default character set to use for recoding of MySQL queries. This must be
1463 enabled and it's described by
1465 option.<br />
1466 You can give here any character set which is in
1468 array and this is just default choice, user can select any of them.</dd>
1471 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1472 support (compiled in or module) in PHP to allow MySQL queries recoding
1473 and used language file must have it enabled (by default only these
1474 which are in Unicode, just to avoid losing some characters).<br /><br />
1477 in the Export page, to choose the character set when exporting a file.
1478 </dd>
1481 <dd>You can select here which functions will be used for character set
1482 conversion. Possible values are:
1483 <ul><li>auto - automatically use available one (first is tested
1484 iconv, then recode)</li>
1487 </ul>
1488 Default is auto.</dd>
1491 <dd>Specify some parameters for iconv used in charset conversion. See
1494 used, so that invalid characters will be transliterated.</dd>
1497 <dd>Available character sets for MySQL conversion. You can add your own (any of
1498 supported by recode/iconv) or remove these which you don't use.
1499 Character sets will be shown in same order as here listed, so if you
1500 frequently use some of these move them to the top.</dd>
1505 default empty, you need to fill in some trusted proxy servers if you
1506 want to use rules for IP addresses behind proxy.<br /><br />
1508 The following example specifies that phpMyAdmin should trust a
1510 <pre>
1511 $cfg['TrustedProxies'] =
1513 </pre>
1514 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1515 client's IP address as usual.
1516 </dd>
1520 MIME transformations.<br />
1521 Possible values are:
1522 <ul><li>auto - automatically detect, this is a bit expensive
1524 according to your server real possibilities</li>
1527 </ul>
1528 Default is auto.
1529 </dd>
1533 </dd>
1535 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1536 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1537 </dt>
1538 <dd>The background styles used for both the frames.
1541 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1543 <dd>The style used for the pointer in the navi frame.
1547 <dd>The color used for the database name in the navi frame.
1556 </dd>
1560 <dd>The style used for table headers. See
1565 </dd>
1569 </dd>
1571 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1573 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1575 </dt>
1577 The former feature highlights the row over which your mouse is passing
1578 and the latter lets you visually mark/unmark rows by clicking on
1579 them.<br />
1584 <dd>You put here a valid CSS font family value, for example
1589 <dd>You put here a valid CSS font family value, for example
1603 </dt>
1605 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1607 The Char* values are used for CHAR and VARCHAR editing (if configured
1611 </dt>
1615 </dt>
1616 <dd>Defines if the whole textarea of the query box will be selected on
1617 click.</dd>
1620 </dt>
1621 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1622 editing.</dd>
1625 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1626 Can be turned off by a toggle button on the browse page.</dd>
1630 </dt>
1631 <dd>Defines the place where modify and delete links would be put when
1632 tables contents are displayed (you may have them displayed both at the
1633 left and at the right).
1639 </dt>
1641 Define which one is displayed by default. The first mode displays each
1642 row on a horizontal line, the second rotates the headers by 90
1643 degrees, so you can use descriptive headers even though fields only
1644 contain small values and still print them out. The vertical mode sorts
1645 each row on a vertical lineup.<br /><br />
1647 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1648 the rotation of the header for horizontalflipped is done via CSS. If
1649 set to 'fake' PHP does the transformation for you, but of course this
1650 does not look as good as CSS.</dd>
1654 string or integer</dt>
1655 <dd>When editing/creating new columns in a table all fields normally get
1656 lined up one field a line. (default: 'horizontal'). If you set this to
1657 'vertical' you can have each field lined up vertically beneath each
1658 other. You can save up a lot of place on the horizontal direction and
1659 no longer have to scroll. If you set this to integer, editing of fewer
1660 columns will appear in 'vertical' mode, while editing of more fields
1661 still in 'horizontal' mode. This way you can still effectively edit
1662 large number of fields, while having full view on few of them.</dd>
1666 </dt>
1668 display of column comments in Browse or Property display. In browse
1669 mode, the comments are shown inside the header. In property mode,
1670 comments are displayed using a CSS-formatted dashed-line below the
1671 name of the field. The comment is shown as a tool-tip for that field.
1672 </dd>
1684 <dd>Whether to display a link to validate a query in any SQL Query box.
1691 <dd>
1692 The name of the directory where
1694 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1695 are available under a drop-down box when you click the database or
1696 table name, then the Import tab.
1697 <br /><br />
1699 If you want different directory for each user, %u will be replaced
1700 with username.<br /><br />
1704 compressed formats is enabled).<br /><br />
1706 This feature is useful when your file is too big to be uploaded via
1708 uploads are disabled in PHP.<br /><br />
1710 Please note that if PHP is running in safe mode, this directory must
1711 be owned by the same user as the owner of the phpMyAdmin scripts.
1712 <br /><br />
1716 alternatives.
1717 </dd>
1720 <dd>
1721 The name of the directory where dumps can be saved.<br /><br />
1723 If you want different directory for each user, %u will be replaced
1724 with username.<br /><br />
1726 Please note that the directory must exist and has to be writable
1727 for the user running the webserver.<br /><br />
1729 Please note that if PHP is running in safe mode, this directory must
1730 be owned by the same user as the owner of the phpMyAdmin scripts.
1731 </dd>
1734 <dd>
1735 The name of the directory where temporary files can be stored.
1736 <br /><br />
1737 This is needed for native MS Excel export, see
1740 </dd>
1743 <dd>
1744 In this array are defined default parameters for export, names of
1745 items are similar to texts seen on export page, so you can easily
1746 identify what they mean.
1747 </dd>
1750 <dd>
1751 In this array are defined default parameters for import, names of
1752 items are similar to texts seen on import page, so you can easily
1753 identify what they mean.
1754 </dd>
1757 <dd>
1758 Repeat the headers every X cells, or 0 to deactivate.
1759 </dd>
1767 </dt>
1768 <dd>
1769 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1770 or icon is always displayed on the left panel. If JavaScript is enabled in
1771 your browser, a click on this opens a distinct query window, which is
1772 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1773 changes to display a query box.<br /><br />
1775 The size of this query window can be customized with
1777 - both integers for the size in pixels. Note that normally, those
1779 theme you are using.<br /><br />
1783 opens the query window and puts the current query
1784 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1785 query in the right panel's query box.
1786 <br /><br />
1787 The usage of the JavaScript query window is recommended if you have a
1788 JavaScript enabled browser. Basic functions are used to exchange quite
1789 a few variables, so most 4th generation browsers should be capable to
1790 use that feature. It currently is only tested with Internet Explorer 6
1791 and Mozilla 1.x.
1792 <br /><br />
1794 to a table, which has to be created by you (see <a
1796 all your queries will be appended to the form, but only as long as
1797 your window is opened they remain saved.
1798 <br /><br />
1799 When using the JavaScript based query window, it will always get
1800 updated when you click on a new table/db to browse and will focus if
1801 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1802 the query window by checking the box "Do not overwrite this query from
1803 outside the window" below the query textarea. Then you can browse
1804 tables/databases in the background without losing the contents of the
1805 textarea, so this is especially useful when composing a query with
1806 tables you first have to look in. The checkbox will get automatically
1807 checked whenever you change the contents of the textarea. Please
1808 uncheck the button whenever you definitely want the query window to
1809 get updated even though you have made alterations.
1810 <br /><br />
1813 <br /><br />
1814 The query window also has a custom tabbed look to group the features.
1816 default tab to be used when opening the query window. It can be set to
1817 either 'sql', 'files', 'history' or 'full'.</dd>
1823 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1825 If the approximate row count as returned by
1828 count will be used.
1829 </dd>
1831 <dd>For VIEWs, since obtaining the exact count could have an
1832 impact on performance, this value is the maximum to be displayed, using
1834 any row counting.
1835 </dd>
1839 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1841 page. By clicking on the button 'toggle scratchboard' on the page
1842 where you edit x/y coordinates of those elements you can activate a
1843 scratchboard where all your elements are placed. By clicking on an
1844 element, you can move them around in the pre-defined area and the x/y
1845 coordinates will get updated dynamically. Likewise, when entering a
1846 new position directly into the input field, the new position in the
1847 scratchboard changes after your cursor leaves the input field.<br />
1848 You have to click on the 'OK'-button below the tables to save the new
1849 positions. If you want to place a new element, first add it to the
1850 table of elements and then you can drag the new element around.<br />
1851 By changing the paper size and the orientation you can change the size
1852 of the scratchboard as well. You can do so by just changing the
1853 dropdown field below, and the scratchboard will resize automatically,
1854 without interfering with the current placement of the elements.<br />
1855 If ever an element gets out of range you can either enlarge the paper
1856 size or click on the 'reset' button to place all elements below each
1857 other.<br />
1859 get this control to work. The basic Drag&Drop script functionality
1860 was kindly borrowed from www.youngpup.net and is underlying so
1861 specific license.</dd>
1864 <dd>Sorts database and table names according to natural order (for example,
1865 t1, t2, t10). Currently implemented in the left panel (Light mode)
1866 and in Database view, for the table list.</dd>
1872 <dd>Allows you to specify window's title bar. Following magic string can
1873 be used to get special values:
1874 <dl>
1880 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1889 </dl>
1890 </dd>
1900 </dd>
1903 <dd>If theme manager is active, use this as the path of the subdirectory
1904 containing all the themes.</dd>
1918 </dt>
1919 <dd>Default queries that will be displayed in query boxes when user didn't
1920 specify any. Use %d for database name, %t for table name and %f for a
1921 comma separated list of field names. Note that %t and %f are only
1925 <dd>
1926 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
1927 default we use HTML to format the query, but you can disable this by
1929 </dd>
1932 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1933 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1934 query inside a bracket is indented. By changing
1937 specifies the units of the indent amount that you specified. This is
1938 used via stylesheets.</dd>
1941 <dd>This array is used to define the colours for each type of element of
1942 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1944 If you specify an empty string for the color of a class, it is ignored
1945 in creating the stylesheet.
1946 You should not alter the class names, only the colour strings.<br />
1967 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1971 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1972 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1973 </ul>
1974 </dd>
1978 <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,
1979 as originally published on
1981 <br />
1982 For help in setting up your system to use the service, see the
1984 </dd>
1988 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1989 and any password, so we use those by default. Instead, if
1990 you have an account with them, you can put your login details
1991 here, and it will be used in place of the anonymous login.</dd>
1992 </dl>
1993 </dd>
1996 <dd><b>DEVELOPERS ONLY!</b></dd>
1999 <dd><b>DEVELOPERS ONLY!</b><br />
2000 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2001 the code.<br />
2002 For help in setting up your system to this, see the
2006 <dd><b>DEVELOPERS ONLY!</b><br />
2007 Enable profiling support for phpMyAdmin. This will append a chunk of data
2008 to the end of every page displayed in the main window with profiling
2009 statistics for that page.<br />
2010 You may need to increase the maximum execution time for this to
2011 complete successfully.<i>Profiling was removed from the code for
2012 version 2.9.0 due to licensing issues.</i></dd>
2014 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2015 <dd><b>DEVELOPERS ONLY!</b><br />
2016 When profiling data is displayed, this variable controls the threshold of
2017 display for any profiling data, based on the average time each time has
2018 taken. If it is over the threshold it is displayed, otherwise it is not
2019 displayed. This takes a value in milliseconds. In most cases you don't need
2020 to edit this.</dd>
2023 <dd>All possible types of a MySQL column. In most cases you don't need to
2024 edit this.</dd>
2027 <dd>Possible attributes for fields. In most cases you don't need to edit
2028 this.</dd>
2031 <dd>A list of functions MySQL supports. In most cases you don't need to
2032 edit this.</dd>
2035 <dd>Mapping of column types to meta types used for preferring displayed
2036 functions. In most cases you don't need to edit this.</dd>
2039 <dd>Functions preferred for column meta types as defined in
2040 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2041 to edit this.</dd>
2044 <dd>Functions selected by default when inserting/changing row, Functions
2045 are defined for meta types from
2047 <code>first_timestamp</code>, which is used for first timestamp column
2048 in table.</dd>
2051 <dd>Operators available for search operations on numeric and date fields.
2052 </dd>
2055 <dd>Operators available for search operations on character fields.
2056 Note that we put <code>LIKE</code> by default instead of
2057 <code>LIKE %...%</code>, to avoid unintended performance problems
2058 in case of huge tables.</dd>
2061 <dd>Operators available for search operations on enum fields.</dd>
2064 <dd>Additional operators available for search operations when the
2065 field can be null.</dd>
2067 </dl>
2069 <!-- TRANSFORMATIONS -->
2075 </ol>
2079 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2081 section</a> on how to do so.</p>
2083 <p> You can apply different transformations to the contents of each field. The
2084 transformation will take the content of each field and transform it with
2085 certain rules defined in the selected transformation.</p>
2087 <p> Say you have a field 'filename' which contains a filename. Normally you would
2088 see in phpMyAdmin only this filename. Using transformations you can transform
2089 that filename into a HTML link, so you can click inside of the phpMyAdmin
2090 structure on the field's link and will see the file displayed in a new browser
2091 window. Using transformation options you can also specify strings to
2092 append/prepend to a string or the format you want the output stored in.</p>
2094 <p> For a general overview of all available transformations and their options,
2095 you can consult your
2096 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2097 installation.</p>
2099 <p> For a tutorial on how to effectively use transformations, see our
2101 the official phpMyAdmin homepage.</p>
2105 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2106 clicking on the 'Structure' link for a table). There click on
2107 "Change" (or change icon) and there you will see three new fields at
2108 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2109 'Transformation options'.</p>
2111 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2112 that corresponds to the column's contents. Please note that
2113 transformations are inactive as long as no MIME-type is selected.</li>
2115 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2116 hopefully growing amount of pre-defined transformations. See below for information on
2117 how to build your own transformation.<br />
2119 There are global transformations and mimetype-bound transformations. Global transformations
2120 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2121 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2122 transformations which operate on the main mimetype (like 'image'), which will most likely
2123 take the subtype into regard, and those who only operate on a
2124 specific subtype (like 'image/jpeg').<br />
2126 You can use transformations on mimetypes for which the function was not defined for. There
2127 is no security check for you selected the right transformation, so take care of what the
2128 output will be like.</li>
2130 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2131 transform-function specific options here. Usually the transforms can operate with default
2132 options, but it is generally a good idea to look up the overview to see which options are
2133 necessary.<br />
2135 Much like the ENUM/SET-Fields, you have to split up several options using the format
2136 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2137 parsed as an array, leaving the first value the first element in the array, and so
2138 forth.<br />
2140 If you want to specify a MIME character set you can define it in the transformation_options.
2141 You have to put that outside of the pre-defined options of the specific mime-transform,
2143 for which you can specify 2 options and you want to append a character set, enter "'first
2144 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2146 </ul>
2150 <p> All mimetypes and their transformations are defined through single files in
2151 the directory 'libraries/transformations/'.</p>
2153 <p> They are stored in files to ease up customization and easy adding of new
2154 transformations.</p>
2156 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2157 always work. It makes no sense to apply a transformation to a mimetype, the
2158 transform-function doesn't know to handle.</p>
2160 <p> One can, however, use empty mime-types and global transformations which should work
2161 for many mimetypes. You can also use transforms on a different mimetype they where built
2162 for, but pay attention to option usage as well as what the transformation does to your
2163 field.</p>
2165 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2166 any other transform function and provides some basic functions.</p>
2168 <p> There are 5 possible file names:</p>
2170 <ol><li>A mimetype+subtype transform:<br /><br />
2172 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2174 Please not that mimetype and subtype are separated via '_', which shall
2175 not be contained in their names. The transform function/filename may
2176 contain only characters which cause no problems in the file system as
2177 well as the PHP function naming convention.<br /><br />
2179 The transform function will the be called
2180 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2182 <b>Example:</b><br /><br />
2184 <tt>text_html__formatted.inc.php</tt><br />
2185 <tt>PMA_transform_text_html__formatted()</tt></li>
2187 <li>A mimetype (w/o subtype) transform:<br /><br />
2189 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2191 Please note that there are no single '_' characters.
2192 The transform function/filename may contain only characters which cause
2193 no problems in the file system as well as the PHP function naming
2194 convention.<br /><br />
2196 The transform function will the be called
2197 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2199 <b>Example:</b><br /><br />
2201 <tt>text__formatted.inc.php</tt><br />
2202 <tt>PMA_transform_text__formatted()</tt></li>
2204 <li>A mimetype+subtype without specific transform function<br /><br />
2206 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2208 Please note that there are no '__' characters in the filename. Do not
2209 use special characters in the filename causing problems with the file
2210 system.<br /><br />
2212 No transformation function is defined in the file itself.<br /><br />
2214 <b>Example:</b><br /><br />
2216 <tt>text_plain.inc.php</tt><br />
2217 (No function)</li>
2219 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2221 <tt>[mimetype].inc.php</tt><br /><br />
2223 Please note that there are no '_' characters in the filename. Do not use
2224 special characters in the filename causing problems with the file system.
2225 <br /><br />
2227 No transformation function is defined in the file itself.<br /><br />
2229 <b>Example:</b><br /><br />
2231 <tt>text.inc.php</tt><br />
2232 (No function)</li>
2234 <li>A global transform function with no specific mimetype<br /><br />
2236 <tt>global__[transform].inc.php</tt><br /><br />
2238 The transform function will the be called
2239 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2241 <b>Example:</b><br /><br />
2243 <tt>global__formatted</tt><br />
2244 <tt>PMA_transform_global__formatted()</tt></li>
2245 </ol>
2247 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2248 transform function.</p>
2250 <p> All filenames containing no '__' in themselves are not shown as valid transform
2251 functions in the dropdown.</p>
2253 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2254 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2255 without a transform function. Also note the introduction of a function description in
2256 the language files. For each function a $strTransformation_[filename without .inc.php]
2257 has to exist.</p>
2259 <p> You can use the template generator to generate new functions and entries in the
2260 language file.</p>
2262 <p> To create a new transform function please see
2263 <tt>libraries/transformations/template_generator.sh</tt>.
2264 To create a new, empty mimetype please see
2265 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2267 <p> A transform function always gets passed three variables:</p>
2269 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2270 you want to transform.</li>
2271 <li><b>$options</b> - Contains any user-passed options to a transform function
2272 as an array.</li>
2273 <li><b>$meta</b> - Contains an object with field information to your column.
2274 The data is drawn from the output of the
2276 function. This means, all object properties described on the
2278 available in this variable and can be used to transform a field accordingly
2279 to unsigned/zerofill/not_null/... properties.<br />
2280 The $meta->mimetype variable contains the original MIME-type of the
2281 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2282 </ol>
2284 <!-- FAQ -->
2291 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2295 </ol>
2297 <p> Please have a look at our
2299 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2300 features and or interface.</p>
2306 action is required or phpMyAdmin sends a blank page or a page full of
2307 cryptic characters to my browser, what can I do?</a></h4>
2309 <p> There are some known PHP bugs with output buffering and compression.<br />
2311 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2312 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2313 configuration file.<br />
2314 Furthermore, we know about such problems connected to the release
2315 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2316 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2321 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2322 See also the
2324 entry about PHP bugs with output buffering.<br />
2325 If your server keeps crashing, please ask for help in the various Apache
2326 support groups.</p>
2330 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2331 script: I'm always displayed the login screen.</a></h4>
2333 <p> This is a known PHP bug (see this
2335 official PHP bug database. It means there is and won't be any phpMyAdmin
2336 fix against it because there is no way to code a fix.</p>
2342 application misbehaved by not returning a complete set of
2344 </h4>
2346 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2347 Have a look at the last message in this
2349 official PHP bug database.</p>
2354 and/or many error messages with the
2356 mode.</a></h4>
2358 <p> This is a known problem with the PHP
2360 filter: it's not so stable. Please use instead the cookie authentication mode.
2361 </p>
2366 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2367 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2368 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2369 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2370 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2375 work.</a></h4>
2377 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2378 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2379 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2380 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2381 We faced PHP crashes when trying to download a dump with MS Internet
2382 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2383 this case you should switch to the release version of PHP 4.2.0.</p>
2387 an error about safe mode being in effect.</a></h4>
2389 <p> Your uploaded file is saved by PHP in the "upload dir", as
2390 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2391 the system default is <i>/tmp</i>).<br />
2392 We recommend the following setup for Apache servers running in safe mode,
2393 to enable uploads of files while being reasonably secure:</p>
2395 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2396 <li>give ownership to the Apache server's user.group:
2397 <tt>chown apache.apache /tmp/php</tt></li>
2398 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2399 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2400 <li>restart Apache</li>
2401 </ul>
2405 general file uploads don't work on my system and uploaded files have a
2406 <tt>Content-Type:</tt> header in the first line.</a></h4>
2408 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2409 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2410 So the problem is that this package has a serious bug that was corrected
2411 ages ago in PHP (2001-01-28: see
2413 for more details). The problem is that the bugged package is still
2414 available though it was corrected (see
2416 for more details).<br />
2417 So please download
2418 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2419 and the problem should go away.<br />
2420 And that fixes the \r\n problem with file uploads!</p>
2424 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2425 I'm using the Apache server.</a></h4>
2427 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2428 your <i>httpd.conf</i>:</p>
2432 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2436 uploading a file from the query box.</a></h4>
2438 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2439 restrictions. Assuming that the restriction allows you to open files in the
2440 current directory ('.'), all you have to do is create a 'tmp' directory
2441 under the phpMyAdmin install directory, with permissions 777 and the same
2442 owner as the owner of your phpMyAdmin directory. The uploaded files will
2443 be moved there, and after execution of your
2449 <p> The MySQL manual explains how to
2451 reset the permissions</a>.</p>
2456 execute a bookmark.</a></h4>
2458 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2459 cannot access the uploaded query.</p>
2464 submit a query from the convenient text area.</a></h4>
2466 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2467 and try to increase it.</p>
2471 </h4>
2473 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2474 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2475 names to align with current standards.</p>
2480 </h4>
2482 <p> Starting with version 2.7.0, the import engine has been re–written and these
2483 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2484 to take advantage of the new import features.</p>
2486 <p> The first things to check (or ask your host provider to check) are the
2487 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2488 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2489 All of these three settings limit the maximum size of data that can be
2490 submitted and handled by PHP. One user also said that post_max_size
2491 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2493 There exist several workarounds if your upload is too big or your
2494 hosting provider is unwilling to change the settings:</p>
2497 feature. This allows one to
2498 upload a file to the server via scp, ftp, or your favorite file transfer
2499 method. PhpMyAdmin is then able to import the files from the temporary
2501 section</a> of this document.</li>
2503 BigDump</a>) to split the files before uploading. We cannot support this
2504 or any third party applications, but are aware of users having success
2505 with it.</li>
2506 <li>If you have shell (command line) access, use MySQL to import the files
2507 directly. You can do this by issuing the "source" command from
2508 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2509 </ul>
2513 support?</a></h4>
2515 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2516 fully supported. Please note that the older your MySQL version is, the more
2517 limitations you will have to face.<br />
2518 phpMyAdmin may connect to your MySQL server using php's classic
2521 is available in php 5.0.<br />
2522 Either way, the developers of both extensions recommend to use the classic
2523 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2524 When compiling php, we strongly recommend that you manually link the MySQL
2525 extension of your choice to a MySQL client library of at least the same
2526 minor version since the one that is bundled with some php distributions is
2529 If your webserver is running on a windows system, you might want to try
2530 MySQL's
2532 instead of the MySQL / MySQLi extensions that are bundled with the official
2533 php Win32 builds.
2534 <br />
2535 MySQL 5.1 is not yet supported.</p>
2539 message, "Client does not support authentication protocol requested
2540 by server; consider upgrading MySQL client"</a></h5>
2542 <p> You tried to access MySQL with an old MySQL client library. The version of
2543 your MySQL client library can be checked in your phpinfo() output.
2544 In general, it should have at least the same minor version as your server
2548 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2549 changed the authentication hash and your PHP is trying to use the old method.
2551 with the proper client library to match your MySQL installation. Your
2552 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2553 More information (and several workarounds) are located in the
2555 </p>
2559 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2560 capital letter in its name it is changed to lowercase as it should. But
2561 if I try to DROP this table MySQL is unable to find the corresponding
2562 file.</a></h4>
2564 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2565 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2566 directive.</p>
2570 script seems not to know the font face I'm using!</a></h4>
2572 <p> The "FPDF" library we're using for this feature requires some
2573 special files to use font faces.<br />
2575 these files.</p>
2579 check PHP Configuration".</a></h4>
2581 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2582 "MySQL extension". This extension may be part of the PHP
2583 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2584 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2585 to load the extension but failed.<br /><br />
2587 Usually, the problem is solved by installing a software package called
2588 "PHP-MySQL" or something similar.</p>
2593 and I cannot log in using cookie auth.</a></h4>
2595 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2599 so I cannot upload.</a></h4>
2601 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2602 parameter is not set to "on".</p>
2606 a new table the table and field names are changed to lowercase!</a></h4>
2608 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2609 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2610 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2611 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2612 directory and add the following line to the group [mysqld]:</p>
2614 <pre>set-variable = lower_case_table_names=0</pre>
2616 <p> Next, save the file and restart the MySQL service. You can always check the
2617 value of this directive using the query</p>
2619 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2623 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2626 </p>
2630 and I get problems, such as undefined variables when I run a
2633 <p> A tip from Jose Fandos: put a comment on the following two lines
2634 in httpd.conf, like this:</p>
2636 <pre>
2637 # mod_gzip_item_include file \.php$
2639 </pre>
2641 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2642 PHP scripts. Of course you have to restart Apache.</p>
2647 I get the error "No input file specified" when trying to
2648 run phpMyAdmin.</a></h4>
2650 <p> This is a permission problem. Right-click on the phpmyadmin folder
2651 and choose properties. Under the tab Security, click on "Add"
2652 and select the user "IUSR_machine" from the list. Now set his
2653 permissions and it should work.</p>
2657 db_structure.php with plenty of tables).</a></h4>
2660 GZIP output buffering is enabled. If you turn off it (by
2662 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2663 PHP 5.0.0.</p>
2667 message 'Errorcode: 13'. What does this mean?</a></h4>
2669 <p> This can happen due to a MySQL bug when having database / table names with
2670 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2671 To fix this, turn off this directive, convert all database and table names
2672 to lower case and turn it on again. Alternatively, there's a bug-fix
2673 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2677 and the fields are duplicated.</a></h4>
2679 <p> It is possible to configure Apache in such a way that PHP has problems
2680 interpreting .php files.</p>
2682 <p> The problems occur when two different (and conflicting) set of directives
2683 are used:</p>
2685 <pre>
2686 SetOutputFilter PHP
2687 SetInputFilter PHP
2688 </pre>
2690 <p> and</p>
2692 <pre>AddType application/x-httpd-php .php</pre>
2694 <p> In the case we saw, one set of directives was in
2695 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2696 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2697 The recommended way is with <tt>AddType</tt>, so just comment out
2698 the first set of lines and restart Apache:</p>
2700 <pre>
2701 #SetOutputFilter PHP
2702 #SetInputFilter PHP
2703 </pre>
2708 <p> This problem is known to happen when the server is running Turck MMCache
2709 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2714 <p> Yes.<br />
2715 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2716 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2717 <tt>error_reporting</tt> settings.
2718 </p>
2721 <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>
2723 <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>
2726 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2727 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2728 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2729 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2730 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2731 enabled.) Click <tt>OK</tt>.</li>
2732 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2733 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2734 </ol>
2738 PHP 5.0.4 on 64-bit systems?</a></h4>
2740 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2741 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2747 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2748 Table and script parts are optional. If you want
2749 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2750 some configuration. Following lines apply only for <a
2752 that you have enabled some features within global configuration. You need
2753 <code>Options FollowSymLinks</code> and <code>AllowOverride
2754 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2755 you need mod_rewrite to be enabled. Then you just need to create following
2756 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2757 (don't forget to change directory name inside of it):</p>
2759 <pre>
2760 RewriteEngine On
2761 RewriteBase /path_to_phpMyAdmin
2762 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2763 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2764 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2765 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2766 </pre>
2769 <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>
2771 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2772 following rewrite rule:</p>
2774 <pre>
2775 RewriteEngine On
2776 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2777 </pre>
2781 </h4>
2782 <p>
2783 There can be many explanations to this and a look at your server's
2784 error log file might give a clue.
2785 </p>
2789 password encryption in cookie auth doesn't work.</a></h4>
2791 <p> If your cluster consist of different architectures, PHP code used for
2792 encryption/decryption won't work correct. This is caused by use of
2793 pack/unpack functions in code. Only solution is to use mcrypt extension
2794 which works fine in this case.</p>
2800 headers already sent by ..." is displayed, what's the problem?</a></h4>
2802 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2803 (I.E. no blank lines, no spaces, no characters...) neither before the
2804 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2805 tag at the end. We also got a report from a user under IIS, that used
2806 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2807 contained an end-of-line character (hex 0A) at the end; removing this character
2808 cleared his errors.</p>
2813 <p> Either there is an error with your PHP setup or your username/password is
2814 wrong. Try to make a small script which uses mysql_connect and see if it
2815 works. If it doesn't, it may be you haven't even compiled MySQL support
2816 into PHP.</p>
2820 connect to local MySQL server through socket '/tmp/mysql.sock'
2821 (111) ..." is displayed. What can I do?</a></h4>
2823 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2825 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2826 In your <i>php.ini</i> you will find a line</p>
2828 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2830 <p> change it to</p>
2832 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2834 <p> Then restart apache and it will work.</p>
2836 <p> Here is a fix suggested by Brad Ummer:</p>
2838 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2839 To do this, telnet to your server and go to the MySQL bin directory. In
2840 this directory there should be a file named <i>mysqladmin</i>. Type
2841 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2842 info about your MySQL server, including the socket
2843 (<i>/tmp/mysql.sock</i>, for example).</li>
2844 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2845 phpMyAdmin, you need to complete the socket information in the
2846 <i>config.inc.php</i>.<br />
2847 For example:
2849 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2850 <br /><br />
2852 Please also make sure that the permissions of this file allow to be readable
2853 by your webserver (i.e. '0755').</li>
2854 </ul>
2856 <p> Have also a look at the
2858 corresponding section of the MySQL documentation</a>.</p>
2862 what can I do?</a></h4>
2865 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2866 sometime.<br />
2867 Also have a look at your PHP version number: if it contains "4.0b..."
2868 it means you're running a beta version of PHP. That's not a so good idea,
2869 please upgrade to a plain revision.</p>
2873 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2874 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2876 <p> Check the value you set for the
2878 directive in the phpMyAdmin configuration file.</p>
2882 password: YES)"-error when trying to access a MySQL-Server on a
2883 host which is port-forwarded for my localhost.</a></h4>
2885 <p> When you are using a port on your localhost, which you redirect via
2886 port-forwarding to another host, MySQL is not resolving the localhost
2887 as expected.<br />
2888 Erik Wasser explains: The solution is: if your host is "localhost"
2889 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2890 connection for speeding up things. And that doesn't work in this configuration
2891 with port forwarding.<br />
2897 <p> Themes are configured with
2901 <br />
2903 should not delete the directory "original" or its underlying
2904 structure, because this is the system theme used by phpMyAdmin.
2905 "original" contains all images and styles, for backwards
2906 compatibility and for all themes that would not include images or css-files.
2907 <br /><br />
2910 is enabled, you can select your favorite theme on the main page. Your
2911 selected theme will be stored in a cookie.<br /><br /></p>
2913 <p> To create a theme:</p>
2915 <ul><li>make a new subdirectory (for example "your_theme_name") under
2917 (by default <tt>themes</tt>)</li>
2918 <li>copy the files and directories from "original" to
2919 "your_theme_name"</li>
2920 <li>edit the css-files in "your_theme_name/css"</li>
2921 <li>put your new images in "your_theme_name/img"</li>
2922 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2923 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2924 contain your chosen theme name, that will be visible in user interface</li>
2925 <li>make a new screenshot of your theme and save it under
2926 "your_theme_name/screen.png"</li>
2927 </ul>
2929 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2930 theme verbose name, theme generation and theme version. These versions and
2931 generations are enumerated from 1 and do not have any direct dependence on
2932 phpMyAdmin version. Themes within same generation should be backwards
2933 compatible - theme with version 2 should work in phpMyAdmin requiring
2934 version 1. Themes with different generation are incompatible.</p>
2936 <p> If you do not want to use your own symbols and buttons, remove the
2937 directory "img" in "your_theme_name". phpMyAdmin will
2938 use the default icons and buttons (from the system-theme "original").
2939 </p>
2943 what can I do?</a></h4>
2945 <p> Here are a few points to check:</p>
2947 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2949 directive empty. See also
2951 </li>
2952 <li>Maybe you have a broken PHP installation or you need to upgrade
2953 your Zend Optimizer. See
2955 http://bugs.php.net/bug.php?id=31134</a>.
2956 </li>
2957 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2958 set to the default (200) or another low value, you could get this
2959 error if your table has a high number of columns. Adjust this setting
2960 accordingly. (Thanks to Klaus Dorninger for the hint).
2961 </li>
2962 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2963 of ";" will cause this error. Replace it with "&;".
2964 </li>
2966 you might want to increase
2968 </li>
2969 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
2970 </li>
2971 </ul>
2978 who logged out can not log in again in with the same nick.</a></h4>
2980 <p> This is related to the authentication mechanism (protocol) used by
2981 phpMyAdmin. To bypass this problem: just close all the opened
2982 browser windows and then go back to phpMyAdmin. You should be able to
2983 log in again.</p>
2987 limit error or a time limit error.</a></h4>
2989 <p> Compressed dumps are built in memory and because of this are limited to
2990 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2991 using
2993 (enabled by default). Zip exports can not be handled this way, so if you need
2994 Zip files for larger dump, you have to use another way.</p>
2998 or alter a table.</a></h4>
3000 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3004 bundled with the MySQL server distribution.</a></h4>
3006 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3008 <pre>
3009 -- MySQL dump 8.22
3010 --
3011 -- Host: localhost Database: database
3012 ---------------------------------------------------------
3013 -- Server version 3.23.54
3014 </pre>
3016 <p> The invalid part of the code is the horizontal line made of dashes that
3017 appears once in every dump created with mysqldump. If you want to run your
3018 dump you have to turn it into valid MySQL. This means, you have to add a
3019 whitespace after the first two dashes of the line or add a # before it:
3020 <br />
3021 <code>
3022 -- -------------------------------------------------------<br />
3023 </code>
3024 or<br />
3025 <code>
3026 #---------------------------------------------------------
3027 </code>
3028 </p>
3035 <p> Please note that you should not use the separating string multiple times
3036 without any characters between them, or at the beginning/end of your table
3037 name. If you have to, think about using another TableSeparator or disabling
3038 that feature</p>
3043 <p> In Relation view, being able to choose a table in another database,
3044 or having more than one index field in the foreign key.<br /><br/>
3045 In Query-by-example (Query), automatic generation of the query
3046 LEFT JOIN from the foreign table.<br /><br/>
3047 </p>
3051 I get series of errors like "Warning: unable to parse url". How
3052 can this be fixed?</a></h4>
3053 <p>
3054 Your table neither have a primary key nor an unique one, so we must use a
3055 long expression to identify this row. This causes problems to parse_url
3056 function. The workaround is to create a primary or unique key.
3057 <br />
3058 </p>
3062 a MIME-Transformation onto!</a></h4>
3064 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3065 nested forms can be put inside the table where phpMyAdmin displays the results.
3066 You can, however, use any form inside of a table if keep the parent
3067 form-container with the target to tbl_row_delete.php and just put your own
3068 input-elements inside. If you use a custom submit input field, the form will
3069 submit itself to the displaying page again, where you can validate the
3070 $HTTP_POST_VARS in a transformation.
3072 For a tutorial on how to effectively use transformations, see our
3074 on the official phpMyAdmin-homepage.</p>
3078 MySQL server</a></h4>
3080 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3083 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3084 the quote-character (") is interpreted as an identifier quote character and
3085 not as a string quote character, which makes many internal phpMyAdmin
3087 statements. There is no workaround to this behaviour. News to this item will
3088 be posted in Bug report
3089 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3090 </p>
3094 more that one column with the same value
3095 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3096 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3098 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3099 can use it for the Edit and Delete links.</p>
3104 <p> phpMyAdmin uses a quick method to get the row count, and this method
3105 only returns an approximate count in the case of InnoDB tables. See
3107 a way to modify those results, but
3108 this could have a serious impact on performance.</p>
3113 <p> The number of records in queries containing COUNT and GROUP BY is
3114 not correctly calculated. Also, sorting results of a query like
3119 containing an hyphen.
3120 </a></h4>
3121 <p>
3122 The tests I have made with current MySQL 4.1.11 API shows that the
3123 API does not accept this syntax for the USE command. Enclosing the
3124 db name with backquotes works. For further confusion, no backquotes
3125 are needed with command-line mysql.
3126 </p>
3129 <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>
3130 <p>
3131 This has been a known limitation of phpMyAdmin since the beginning and
3132 it's not likely to be solved in the future.
3133 </p>
3135 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3138 <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
3139 need to install it for each customer.
3140 </a></h4>
3141 <p>
3142 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3143 your users. The development of this feature was kindly sponsored by
3144 NetCologne GmbH.
3145 This requires a properly setup MySQL user management and phpMyAdmin
3146 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3148 </p>
3152 access.
3153 </a></h4>
3154 <p>
3155 This depends on your system.<br />
3156 If you're running a server which cannot be accessed by other people, it's
3157 sufficient to use the directory protection bundled with your webserver
3159 If other people have telnet access to your server, you should use
3160 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3161 <br /><br />
3162 Suggestions:
3163 </p>
3164 <ul>
3165 <li>
3167 </li>
3168 <li>
3169 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3170 is a user whose password is only known to you, and apache is the
3171 group under which Apache runs.
3172 </li>
3173 <li>
3174 You should use PHP safe mode, to protect from other users that try
3176 </li>
3177 </ul>
3182 </a></h4>
3183 <p>
3188 </p>
3191 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3192 authentication.
3193 </a></h4>
3197 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3198 and/or
3200 are wrong.</li>
3202 <li>You have already setup a security mechanism for the
3203 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3204 phpMyAdmin's authentication, so remove it.</li>
3205 </ul>
3212 and put the privileges you want. For example,
3214 would let a user create/manage his/her database(s).</p>
3219 <p> If you have existing rules from an old .htaccess file, you can take them
3222 be a major benefit here if your installation is suited to using it. Then
3223 you can just add those updated lines into the
3227 <p> If you want a pre-made sample, you can try this fragment. It stops the
3228 'root' user from logging in from any networks other than the private
3231 <pre>
3232 //block root from logging in except from the private networks
3233 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3234 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3235 'deny root from all',
3236 'allow root from localhost',
3240 );
3241 </pre>
3246 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3247 different than the one set in your
3249 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3250 while a domain name is defined in the config file.</p>
3255 <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>
3261 when trying to create a table with more than 14 fields.
3262 </a></h4>
3263 <p>
3264 We could reproduce this problem only under Win98/98SE. Testing under
3265 WinNT4 or Win2K, we could easily create more than 60 fields.
3266 <br />
3267 A workaround is to create a smaller number of fields, then come back to
3268 your table properties and add the other fields.
3269 </p>
3273 <p>
3274 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3275 with each script/website that use forms.<br />
3276 Upgrade or downgrade your Xitami server.
3277 </p>
3280 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3281 <p>
3282 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3283 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3284 don't seem to work.<br />
3286 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3287 the user's temporary directory, so they must be moved before closing
3288 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3291 </p>
3295 Explorer never stores the cookies.
3296 </a></h4>
3297 <p>
3298 MS Internet Explorer seems to be really buggy about cookies, at least till
3300 in this area!
3301 <br />
3302 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3303 work!
3304 </p>
3308 rows.
3309 </a></h4>
3310 <p>
3312 </p>
3315 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3316 when trying to modify a row in a table with many fields, or with a text field
3317 </a></h4>
3318 <p>
3319 Your table neither have a primary key nor an unique one, so we must use a
3320 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
3321 those browsers, and this not happen in Netscape, for example. The
3322 workaround is to create a primary or unique key, or use another browser.
3323 <br />
3324 </p>
3328 page.
3329 </a></h4>
3330 <p>
3331 Some browsers support right-clicking into the frame you want to refresh,
3332 just do this in the right frame.<br />
3333 </p>
3337 query box.
3338 </a></h4>
3339 <p>
3340 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3341 Mozilla versions.<br />
3342 </p>
3346 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3347 </a></h4>
3348 <p>
3349 This is a Mozilla bug (see bug #26882 at
3351 </p>
3356 </a></h4>
3357 <p>
3358 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3359 data in octet-stream mode. Since we can't detect the specific Netscape
3360 version, we cannot workaround this bug.
3361 </p>
3365 wrong.</a></h4>
3367 <p> Please ensure that you have set your browser's character set to the one of the
3368 language file you have selected on phpMyAdmin's start page.
3369 Alternatively, you can try the auto detection mode that is supported by the
3370 recent versions of the most browsers.</p>
3373 <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
3376 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3377 Netscape and Mozilla do not have this problem.</p>
3380 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3381 I cannot manage two servers: I log in to the first one, then the other one,
3382 but if I switch back to the first, I have to log in on each operation.</a></h4>
3388 but nothing happens after that, only a blank screen.</a></h4>
3391 bug in Opera6, because it is not able to interpret frameset definitions
3392 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3393 Opera7 at least.</p>
3402 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3407 address and you are starting
3409 containing a domain name, or the reverse situation.</li>
3410 <li>Security settings in IE and/or Microsoft Security Center are
3411 too high, thus blocking scripts execution.</li>
3412 <li>The Windows Firewall is blocking Apache and MySQL. You must
3416 </ul>
3419 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3420 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3421 installed in their Firefox is causing the problem.</p>
3428 </a></h4>
3429 <p>
3430 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3431 specifying a wrong field-type.<br />
3432 Common errors include:
3433 </p>
3434 <ul>
3437 </ul>
3438 <p>
3439 Also, look at the syntax chapter in the MySQL manual to confirm that your
3440 syntax is correct.
3441 </p>
3445 phpMyAdmin generates only one index with those 2 fields.
3446 </a></h4>
3447 <p>
3449 index. If you want two indexes, create the first one when creating the
3450 table, save, then display the table properties and click the Index link to
3451 create the other index.
3452 </p>
3456 <p>
3457 Since version 2.2.3, you have a checkbox for each field that can be null.
3459 field's value. Since version 2.5.5, you have to use the checkbox to get
3461 a literal NULL in the field, and not a NULL value (this works in PHP4).
3462 </p>
3467 <p> Click on a database or table name in the left frame, the properties will be
3469 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3470 statements that can be used to recreate your database/table.
3471 <br /><br />
3473 transmit the resulting dump to your station. Depending on your PHP
3474 configuration, you will see options to compress the dump. See also the
3476 configuration variable.<br /><br />
3479 this document.</p>
3484 </a></h4>
3486 <p> Click on a database name in the left frame, the properties will be
3488 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3490 the path to your dump filename, or use the Browse button. Then click Go.
3491 <br /><br />
3493 that you upgrade to take advantage of the new features.
3494 <br /><br />
3496 in this document.
3497 </p>
3502 <p> Here is an example with the tables persons, towns and countries, all
3504 table, create it as explained in the configuration section. Then create the
3505 example tables:</p>
3507 <pre>
3508 CREATE TABLE REL_countries (
3509 country_code char(1) NOT NULL default '',
3510 description varchar(10) NOT NULL default '',
3511 PRIMARY KEY (country_code)
3512 ) TYPE=MyISAM;
3514 INSERT INTO REL_countries VALUES ('C', 'Canada');
3516 CREATE TABLE REL_persons (
3517 id tinyint(4) NOT NULL auto_increment,
3518 person_name varchar(32) NOT NULL default '',
3520 country_code char(1) NOT NULL default '',
3521 PRIMARY KEY (id)
3522 ) TYPE=MyISAM;
3524 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3525 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3527 CREATE TABLE REL_towns (
3529 description varchar(30) NOT NULL default '',
3530 PRIMARY KEY (town_code)
3531 ) TYPE=MyISAM;
3533 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3534 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3535 </pre>
3541 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3545 </ul>
3553 <li>In the fields row, choose persons.person_name and click the
3555 <li>Do the same for towns.description and countries.descriptions in the
3558 the correct joins have been generated</li>
3560 </ul>
3564 <p>
3565 Starting from the previous example, create the pma_table_info as explained
3566 in the configuration section, then browse your persons table,
3567 and move the mouse over a town code or country code.
3568 <br /><br />
3569 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3570 enables: drop-down list of possible values.
3571 </p>
3574 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3575 <p>
3578 <br /><br />
3579 Then you need to think about your schema layout. Which tables will go on
3580 which pages?
3581 </p>
3582 <ul>
3588 page and click Go. If you like, you
3590 linked tables onto the new page.</li>
3591 <li>Select the name of the new page (making sure the Edit radio button
3592 is selected) and click Go.</li>
3594 Coordinates are relative; your diagram will
3595 be automatically scaled to fit the page. When initially placing tables
3596 on the page, just pick any coordinates -- say, 50x50. After clicking
3598 position the element correctly.</li>
3600 first be sure to click the Save
3601 button beneath the list of tables and coordinates, to save any changes
3602 you made there. Then scroll all the way down, select the
3604 you want, and click Go.</li>
3605 <li>Internet Explorer for Windows may suggest an incorrect filename when
3610 browsers on Windows, do not have this problem.</li>
3611 </ul>
3615 columns!</a></h4>
3617 <p> No, it's MySQL that is doing
3623 underscores in the database name?</a></h4>
3625 <p> If you do not put a backslash before the underscore, this is a wildcard
3628 john2db ...<br /><br />
3630 If you put a backslash before the underscore, it means that the database
3631 name will have a real underscore.</p>
3635 statistics pages?</a></h4>
3646 if it already exists during the import. It does NOT drop the table after
3647 your export, it only affects the import file.</li>
3649 Otherwise, you may get an error if the table name exists but has a
3650 different structure.</li>
3652 (if any) will be included in backup.</li>
3654 field and table names formed with special characters are protected.</li>
3656 types set in the pmadb in the dump as
3658 </li>
3659 </ul>
3664 command, for better documentation (but resulting file is bigger).</li>
3666 once the INSERT verb and the table name.</li>
3669 </li>
3671 more info is provided in the
3673 but basically with this selected, invalid values are adjusted and
3674 inserted rather than causing the entire statement to fail.</li>
3675 </ul>
3679 in its name.</a></h4>
3682 is the normal way to reference a database and table name. Worse, MySQL
3683 will usually let you create a database with a dot, but then you cannot
3684 work with it, nor delete it.</p>
3697 for usage.<br />
3698 On a more recent pear version, I had problems with the state of Net_DIME
3699 being beta, so this single command
3701 needed modules.<br />
3702 If you use the Validator, you should be aware that any
3704 submit will be stored anonymously (database/table/column names,
3705 strings, numbers replaced with generic values). The Mimer
3708 We utilize it as free SOAP service.</p>
3712 it, but MySQL says "BLOB column '...' used in key specification without
3715 <p> The right way to do this, is to create the field without any indexes,
3717 dialog. On this page, you will be able to choose your BLOB field, and
3718 set a size to the index, which is the condition to create an index on
3719 a BLOB field.</p>
3723 editing fields?</a></h4>
3725 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3726 with many editing fields (table structure changes, row editing, etc.)
3727 (must be enabled in configuration - see.
3729 You can also have a look at the directive
3731 ('vertical') and see if this eases up editing for you.</p>
3735 WTF is this feature then useful for?</a></h4>
3737 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3738 on them. Otherwise you could just put a comment on the field. Because entering
3739 your own mimetype will cause serious syntax checking issues and validation,
3740 this introduces a high-risk false-user-input situation. Instead you have to
3741 initialize mimetypes using functions or empty mimetype definitions.<br />
3742 Plus, you have a whole overview of available mimetypes. Who knows all those
3743 mimetypes by heart so he/she can enter it at will?</p>
3747 can't I see any bookmarks below the query box? What is this variable for?
3748 </a></h4>
3750 <p> Any query you have executed can be stored as a bookmark on the page where the
3751 results are displayed. You will find a button labeled 'Bookmark this query'
3752 just at the end of the page.<br />
3753 As soon as you have stored a bookmark, it is related to the database you run
3754 the query on. You can now access a bookmark dropdown on each page, the query
3755 box appears on for that database.<br /><br />
3757 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3761 aware of that you HAVE to create a valid query, otherwise your query won't be
3762 even able to be stored in the database.<br />
3764 for your query will remain the way it is, but will be stripped of the /**/
3765 chars. So you can use:<br /><br />
3769 which will be expanded to<br /><br />
3773 in your query, where VARIABLE is the string you entered in the input box. If
3774 an empty string is provided, no replacements are made.<br /><br />
3776 A more complex example. Say you have stored this query:<br /><br />
3778 <br /><br />
3781 the full query will be:<br /><br />
3784 <br /><br />
3788 spaces inserted there
3789 will be later also inserted as spaces in your query and may lead to unexpected
3790 results especially when
3792 Your initial query which is going to be stored as a bookmark has to yield at
3793 least one result row so
3794 you can store the bookmark. You may have that to work around using well
3798 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3799 include exported table?</a></h4>
3801 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3802 document should look like following one (assuming you have table
3805 <pre>
3806 \documentclass{article} % or any class you want
3807 \usepackage{longtable} % for displaying table
3808 \begin{document} % start of document
3809 \include{table} % including exported table
3810 \end{document} % end of document
3811 </pre>
3815 access them.
3816 </a></h4>
3819 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3820 enable users to see all the database names.
3823 So if your users do not need those privileges, you can remove them and their
3824 databases list will shorten.</p>
3828 possible values for a field, based on some foreign table?</a></h4>
3830 <p> You have to setup appropriate links between the tables, and also
3834 foreign table, a drop-down list of values will be available.
3835 You will see two lists of values, the first list containing the key
3836 and the display field, the second list containing the display field
3837 and the key. The reason for this is to be able to type the first
3838 letter of either the key or the display field.<br /><br />
3840 For 200 values or more, a distinct window will appear, to browse foreign
3841 key values and choose one.</p>
3845 automatically when entering Browse mode for a table?</a></h4>
3847 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3848 </p>
3852 Excel files, how can I enable that?</a></h4>
3854 <p> Current version does support direct export to Microsoft Excel and Word
3855 versions 2000 and newer. If you need export older versions, you can use
3857 which works out of the box or you can
3859 several problems, most important are limitation of cell content to 255
3860 chars and no support for charsets, so think carefully whether you want to
3861 enable this.</b>. For enabling this you need to set
3865 module Spreadsheet_Excel_Writer into php include path. The
3866 installation can be done by following command:</p>
3868 <pre>
3869 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3870 </pre>
3872 <p> First part of switches set we want to install beta version of that module
3873 (no stable version available yet) and then we tell pear we want to satisfy
3874 dependencies.</p>
3876 <p> If you are running in PHP safe mode, you will have to set
3879 modules are located, for example:</p>
3881 <pre>
3882 safe_mode_include_dir = /usr/local/lib/php
3883 </pre>
3887 <pre>
3888 cd phpMyAdmin
3889 mkdir tmp
3890 chmod o+rwx tmp
3891 </pre>
3895 what happens to my column comments stored in pmadb?</a></h4>
3897 <p> Automatic migration of a table's pmadb-style column comments to the native
3898 ones is done whenever you enter Structure page for this table.</p>
3905 <p> Our Bug Tracker is located at
3907 under the Bugs section.<br /><br />
3909 But please first discuss your bug with other users:<br />
3915 existing language, where do I start?</a></h4>
3917 <p> Always use the current SVN version of your language file.
3919 don't know how to get the SVN version, please ask one of the developers.
3920 <br />
3921 Please note that we try not to use HTML entities like &eacute; in
3922 the translations, since we define the right character set in the file.
3923 With HTML entities, the text on JavaScript messages would not
3924 display correctly.
3925 However there are some entities that need to be there, for quotes
3926 ,non-breakable spaces, ampersands, less than, greater than.<br />
3927 You can then put your translations, as a zip file to avoid losing special
3928 characters, on the sourceforge.net translation tracker.<br />
3929 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3930 list, because this is where we ask for translations of new messages.</p>
3934 phpMyAdmin. How should I proceed?</a></h4>
3939 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
3940 </li>
3942 <li>generate patch with your changes:
3944 </li>
3947 tracker of the phpMyAdmin project</a>.
3948 </li>
3949 </ol>
3951 <p> Write access to the SVN tree is granted only to experienced developers who
3952 have already contributed something useful to phpMyAdmin.<br />
3958 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3960 <p> Please refer to
3961 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3962 </p>
3964 <!-- DEVELOPERS -->
3967 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3968 great features have been written by other people and you too can help to
3969 make phpMyAdmin a useful tool.</p>
3971 <p> If you're planning to contribute source, please read the following
3972 information:</p>
3978 it free from other code.<br />
3979 Commonly used functions should be added to
3982 <li>Obviously, you're free to use whatever coding style you want. But
3983 please try to keep your code as simple as possible: beginners are
3984 using phpMyAdmin as an example application.<br />
3985 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3986 compliant on one hand, they fit the
3989 coding standards</a>
3990 on the other hand. Please pay attention to this.</li>
3991 <li>Please try to keep up the file-naming conventions. Table-related stuff
3994 <li>Please don't use verbose strings in your code, instead add the string
3999 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4000 better debug and profile their code.<br />
4001 Please see the
4003 options for more information.<br />
4004 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4005 lost during its re-entry into Earth's atmosphere and in memory of the
4006 brave men and women who gave their lives for the people of Earth.</li>
4007 </ul>
4009 <!-- CREDITS -->
4012 <pre>
4013 phpMyAdmin - Credits
4014 ====================
4016 CREDITS, in chronological order
4017 -------------------------------
4020 * creator of the phpmyadmin project
4024 * multi-language version
4025 * various fixes and improvements
4027 * current project maintainer
4030 * started SourceForge phpMyAdmin project in March 2001
4031 * sync'ed different existing CVS trees with new features and bugfixes
4032 * multi-language improvements, dynamic language selection
4033 * current project maintainer
4034 * many bugfixes and improvements
4037 * rewrote and optimized javascript, DHTML and DOM stuff
4038 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4039 generate XHTML1.0 and CSS2 compliant codes
4040 * improved the language detection system
4041 * many bugfixes and improvements
4044 * database maintenance controls
4045 * table type code
4047 * DB-based configuration (Not completed)
4050 * many bugfixes and improvements
4053 * bookmarks feature
4054 * multiple dump feature
4055 * gzip dump feature
4056 * zip dump feature
4059 * various fixes
4060 * moderator of the phpMyAdmin former users forum at phpwizard.net
4066 * rewrote and fix dump code
4067 * bugfixes
4070 * rewrote dump code for PHP4
4071 * mySQL table statistics
4072 * bugfixes
4075 * main author of the version 2.1.0.1
4076 * bugfixes
4080 * abstract database interface (PMA_DBI) with MySQLi support
4081 * privileges administration
4083 * various features and fixes
4084 * German language file updates
4087 * automatic joins in QBE
4088 * links column in printview
4089 * Relation view
4092 * enhanced index creation/display feature
4093 * feature to use a different charset for HTML than for MySQL
4094 * improvements of export feature
4095 * various features and fixes
4096 * Czech language file updates
4099 (http://sf.net/projects/phpmysqlformgen/)
4100 * suggested the patch for multiple table printviews
4103 * built the patch for vertical display of table rows
4104 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4105 * Improvement of column/db comments
4106 * (MIME)-Transformations for columns
4107 * Use custom alias names for Databases in left frame
4108 * hierarchical/nested table display
4109 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4110 * new icon sets
4111 * vertical display of column properties page
4112 * some bugfixes, features, support, German language additions
4115 * japanese kanji encoding conversion feature
4118 * the Cookie authentication mode
4121 * table relation-links feature
4124 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4125 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4126 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4132 * phpMyAdmin logo (until June 2004)
4135 * blowfish library from the Horde project
4138 * mysqli support
4139 * many bugfixes and improvements
4142 * redesign for 2.6.0
4143 * phpMyAdmin sailboat logo (June 2004)
4146 * Representation at conferences
4149 * interface improvements
4150 * various bugfixes
4152 - Ivan A Kirillov
4153 * new relations Designer
4155 And also to the following people who have contributed minor changes,
4156 enhancements, bugfixes or support for a new language since version 2.1.0:
4158 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4159 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4160 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4161 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4163 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4164 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4165 Luís V., Martijn W. van der Lee,
4166 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4170 Original Credits of Version 2.1.0
4171 ---------------------------------
4173 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4174 to create a web-based interface to MySQL using PHP3. Although I have not
4175 used any of his source-code, there are some concepts I've borrowed from
4176 him. phpMyAdmin was created because Peter told me he wasn't going to
4177 further develop his (great) tool.
4178 Thanks go to
4180 code for the check when dropping a table or database. He also suggested
4181 that you should be able to specify the primary key on tbl_create.php3. To
4182 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4183 well as a bug-report. Plus many smaller improvements.
4185 were introduced in 1.3.0 (including quite significant ones like the
4186 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4187 bug-fixes and help.
4189 language-independent by outsourcing the strings to a separate file. He
4190 also contributed the French translation.
4192 tbl_select.php3, a feature to display only some fields from a table.
4194 functions in tbl_change.php3. He also added the
4197 servers and is a regular contributor for bug-fixes.
4199 features for 2.0.6.
4200 The following people have contributed minor changes, enhancements, bugfixes
4201 or support for a new language:
4202 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4203 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4204 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4205 G. Wieggers.
4207 And thanks to everyone else who sent me email with suggestions, bug-reports
4208 and or just some feedback.
4209 </pre>
4215 <ul>
4217 - the default name of Apache's directory-level configuration file.</li>
4221 - a software application that enables a user to display and interact with
4222 text, images, and other information typically located on a web page at a
4223 website on the World Wide Web.</li>
4225 - a free software/open source data compression algorithm and program
4226 developed by Julian Seward.</li>
4228 - an important World Wide Web technology that enables a client web browser
4229 to request data from a program executed on the Web server.</li>
4231 - a log or record of changes made to a project.</li>
4233 - a computer system that accesses a (remote) service on another computer
4234 by some kind of network.</li>
4236 - a set of data values of a particular simple type, one for each row of
4237 the table.</li>
4239 - a packet of information sent by a server to a World Wide Web browser
4240 and then sent back by the browser each time it accesses that server.</li>
4242 - Comma-seperated values</li>
4245 - an organized collection of data.</li>
4248 - a PHP module that extends PHP with additional functionality.</li>
4250 - a list of commonly asked question and there answers.</li>
4252 - one part of divided data/columns.</li>
4254 - a field or group of fields in a database record that point to a key
4255 field or group of fields forming a key of another database record in some
4256 (usually different) table.</li>
4258 - the free PDF library</li>
4260 GD Graphics Library</a> - a library by Thomas Boutell and others for
4261 dynamically manipulating images.</li>
4264 - gzip is short for GNU zip, a GNU free software file compression
4265 program.</li>
4267 - any machine connected to a computer network, a node that has a hostname.</li>
4269 - the unique name by which a network attached device is known on a network.</li>
4271 (HyperText Transfer Protocol)</a>
4272 - the primary method used to transfer or convey information on the World
4273 Wide Web.</li>
4276 additional security measures.</li>
4277 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4278 - a set of Internet-based services for servers using Microsoft Windows.</li>
4280 - a feature that allows quick access to the rows in a table.</li>
4282 - a data-oriented protocol used by source and destination hosts for
4283 communicating data across a packet-switched internetwork.</li>
4285 - a unique number that devices use in order to identify and communicate
4286 with each other on a network utilizing the Internet Protocol standard.</li>
4288 (Internet Server Application Programming Interface)</a>
4289 - the API of Internet Information Services (IIS).</li>
4291 - a business or organization that offers users access to the Internet and related services.</li>
4293 - a most commonly used standard method of lossy compression for
4294 photographic images.</li>
4300 - line of personal computers is designed, developed, manufactured, and
4301 marketed by Apple Computer.</li>
4302 <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>
4303 - the operating system which is included with all currently shipping Apple
4304 Macintosh computers in the consumer and professional markets.</li>
4306 - a cryptographic library.</li>
4308 - the MCrypt PHP extension.</li>
4309 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4310 - an Internet Standard for the format of e-mail.</li>
4312 - some sort of extension for the Apache Webserver.</li>
4314 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4315 Management System (DBMS).</li>
4317 - the improved MySQL client PHP extension.</li>
4319 - the MySQL client PHP extension.</li>
4321 - open standard for office documents.</li>
4322 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4323 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4325 (Portable Document Format)</a>
4326 - a file format developed by Adobe Systems for representing two
4327 dimensional documents in a device independent and resolution independent
4328 format.</li>
4330 - the PHP Extension and Application Repository.</li>
4332 - the perl-compatible regular expression functions for PHP</li>
4334 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4335 programming language used mainly for developing server-side applications
4336 and dynamic web content, and more recently, a broader range of software
4337 applications.</li>
4339 - a connection through which data is sent and received.</li>
4341 - Request for Comments (RFC) documents are a series of memoranda
4342 encompassing new research, innovations, and methodologies applicable to
4343 Internet technologies.</li>
4347 - represents a single, implicitly structured data item in a table.</li>
4349 - a computer system that provides services to other computing
4350 systems over a network.</li>
4351 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4352 - handlers for different table types</li>
4354 - a form of inter-process communication.</li>
4356 Sockets Layer)</a>
4357 - a cryptographic protocol which provides secure communication on the Internet.</li>
4359 - Structured Query Language</li>
4361 - a set of data elements (cells) that is organized, defined and stored as
4362 horizontal rows and vertical columns where each item can be uniquely
4363 identified by a label or key or by it?s position in relation to other items.</li>
4366 - a type of archive file format: the Tape ARchive format.</li>
4368 - one of the core protocols of the Internet protocol suite.</li>
4372 - a sequence of characters, conforming to a standardized format, that is
4373 used for referring to resources, such as documents and images on the
4374 Internet, by their location.</li>
4376 - A computer (program) that is responsible for accepting HTTP requests
4377 from clients and serving them Web pages.</li>
4379 - a W3C-recommended general-purpose markup language for creating
4380 special-purpose markup languages, capable of describing many different
4381 kinds of data.</li>
4383 - a popular data compression and archival format.</li>
4385 - an open-source, cross-platform data compression library by Jean-loup
4386 Gailly and Mark Adler.</li>
4387 </ul>
4397 </body>
4398 </html>