| blob | dc7e60ace82f65669a608ca86ffe6508dd3f8b7e |
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
197 config.inc.php, but now a wizard-style setup script is provided for
198 those who prefer a graphical installation. Creating a config.inc.php is
199 still a quick way to get started and needed for some advanced features.
200 <ul><li>To manually create the file, simply use your text editor to
203 file) in the main (top-level) phpMyAdmin directory (the one
207 default value is okay for a particular setting, there is no
209 few directives to get going, a simple configuration may look
210 like this:
211 <pre>
212 <?php
213 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
215 $i=0;
216 $i++;
217 $cfg['Servers'][$i]['auth_type'] = 'cookie';
218 ?>
219 </pre>
220 Or, if you prefer to not be prompted every time you log in:
221 <pre>
222 <?php
224 $i=0;
225 $i++;
226 $cfg['Servers'][$i]['user'] = 'root';
227 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
228 ?>
229 </pre>
230 For a full explanation of possible configuration values, see the
236 directory. This is a security measure. On a Linux/Unix system you
237 can use the following commands:
238 <pre>
239 cd phpMyAdmin
240 mkdir config # create directory for saving
241 chmod o+rw config # give it world writable permissions
242 </pre>
243 And to edit an existing configuration, copy it over first:
244 <pre>
245 cp config.inc.php config/ # copy current configuration for editing
246 chmod o+w config/config.inc.php # give it world writable permissions
247 </pre>
248 On other platforms, simply create the folder and ensure that your
257 the webserver does not have the proper permissions you may see the
259 config/</tt> directory exists and has the proper permissions -
261 and upload (via FTP or some similar means) to the proper location.<br /><br />
263 Once the file has been saved, it must be moved out of the <tt>
264 config/</tt> directory and the permissions must be reset, again
265 as a security measure:
266 <pre>
267 mv config/config.inc.php . # move file to current directory
268 chmod o-rw config.inc.php # remove world read and write permissions
269 </pre>
270 Now the file is ready to be used. You can choose to review or edit
271 the file with your favorite editor, if you prefer to set some
272 advanced options which the setup script does not provide.</li></ul></li>
273 <li>If you are using the
275 protect the phpMyAdmin installation directory because using
276 config does not require a user to
277 enter a password to access the phpMyAdmin installation. Use of an alternate
278 authentication method is recommended, for example with
286 in your browser. phpMyAdmin should now display a welcome screen
287 and your databases, or a login dialog if using
289 authentication mode.</li>
291 webserver configuration. For Apache you can use supplied .htaccess file
292 in that folder, for other webservers, you should configure this yourself.
293 Such configuration prevents from possible path exposure and cross side
294 scripting vulnerabilities that might happen to be found in that code.</li>
295 </ol>
299 <p> For a whole set of new features (bookmarks, comments,
302 transformation, etc.) you need to create a set of special tables. Those
303 tables can be located in your own database, or in a central database for a
304 multi-user installation (this database would then be accessed by the
305 controluser, so no other user should have rights to it).</p>
314 installation.</p>
319 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
320 that you may need special (administrator) privileges to create the database
321 and tables, and that the script may need some tuning, depending on the
322 database name.</p>
327 section</a>. You will also need to have a controluser with the proper rights
334 unpacked one. Configuration files from very old versions (2.3.0 or before) may
335 require some tweaking as some options have been changed or removed.</p>
339 is version-specific.</p>
342 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
343 you should run the SQL script found in
350 where you want to give users access to their own database and don't want
351 them to play around with others.<br />
352 Nevertheless be aware that MS Internet Explorer seems to be really buggy
354 in this area!<br />
357 that your user/password pair are not in clear in the configuration file.
358 </li>
361 authentication modes are more secure: the MySQL login information does
362 not need to be set in the phpMyAdmin configuration file (except possibly
364 However, keep in mind that the password travels in plain text, unless
365 you are using the HTTPS protocol.<br />
366 In cookie mode, the password is stored, encrypted with the blowfish
367 algorithm, in a temporary cookie.</li>
370 your MySQL server is previous to 4.1.2, or is running with
380 file under the
382 $cfg['Servers'][$i]['controluser']</a></tt> and
387 only an example: use something else in your file!</b> Input these
388 statements from the phpMyAdmin SQL Query window or mysql command–line
389 client.<br />
391 if it's not the same as the MySQL server's one.
393 <pre>
394 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
395 GRANT SELECT (
396 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
397 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
398 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
399 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
400 Execute_priv, Repl_slave_priv, Repl_client_priv
401 ) ON mysql.user TO 'pma'@'localhost';
402 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
403 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
404 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
405 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
407 If you are using an old MySQL version (below 4.0.2), please replace
408 the first GRANT SELECT query by this one:
410 <pre>
411 GRANT SELECT (
412 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
413 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
414 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
415 ) ON mysql.user TO 'pma'@'localhost';</pre>
417 ... and if you want to use the many new relation and bookmark features:
419 <pre>
421 </pre>
425 Of course, the above queries only work if your MySQL version supports
429 on a set of particular databases. Normally you shouldn't give global
430 privileges to an ordinary user, unless you understand the impact of those
431 privileges (for example, you are creating a superuser).<br />
435 <pre>
436 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
437 </pre>
439 What the user may now do is controlled entirely by the MySQL user
440 management system.<br />
442 authentication mode, you don't need to fill the user/password fields
444 array.</li>
445 </ul>
450 method and allows you to log in as any valid MySQL user.</li>
451 <li>Is supported with most PHP configurations. For
464 mode.</li>
465 </ul>
469 <ul><li>You can use this method as a replacement for the
471 (for example, if you're running
473 <li>Obviously, the user must enable cookies in the browser, but this is
474 now a requirement for all authentication modes.</li>
475 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
476 with the same username.</li>
477 <li>If you want to log in to arbitrary server see
482 not required.</li>
483 </ul>
487 <ul><li>This mode is a convenient way of using credentials from another
488 application to authenticate to phpMyAdmin.</li>
489 <li>The other application has to store login information into
490 session data.</li>
492 section.</li>
493 </ul>
496 <ul><li>This mode is the less secure one because it requires you to fill the
498 $cfg['Servers'][$i]['user']</a> and
500 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
501 can read your config.inc.php can discover your username and password).
502 <br />
509 is an entry explaining how to protect your configuration file.</li>
510 <li>For additional security in this mode, you may wish to consider the Host
511 authentication
513 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
515 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
516 directives.</li>
517 <li>Unlike cookie and http, does not require a user to log in when first
518 loading the phpMyAdmin site. This is by design but could allow any
519 user to access your installation. Use of some restriction method is
521 HTTP-AUTH directive or disallowing incoming HTTP requests at
522 one’s router or firewall will suffice (both of which
523 are beyond the scope of this manual but easily searchable with Google).</li>
524 </ul>
526 <!-- CONFIGURATION -->
530 users:</span> PHP does not seem to like
534 before saving a script you have modified.</p>
539 section to create one. This file only needs to contain the parameters you want to
540 change from their corresponding default value in
543 <p> The parameters which relate to design (like colors) are placed in
546 your site specific code to be included on start and end of each page.</p>
550 (with full path) to your phpMyAdmin installation's directory.
553 some web servers are case–sensitive.
556 Starting with version 2.3.0, it is advisable to try leaving this
557 blank. In most cases phpMyAdmin automatically detects the proper
558 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
559 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
560 A good test is to browse a table, edit a row and save it. There should
561 be an error message if phpMyAdmin is having trouble auto–detecting
562 the correct value. If you get an error that this must be set or if
563 the autodetect code fails to detect your path, please post a bug
564 report on our bug tracker so we can improve the code.</dd>
568 with master / foreign – tables (see
570 <br />
571 If you tried to set this up and it does not work for you, have a look on
573 use it. You will find a link that will analyze why those features have
574 been disabled.<br />
575 If you do not want to use those features set this variable to
580 algorithm to encrypt the password.<br />
582 passphrase of your choice. It will be used internally by the blowfish
583 algorithm: you won’t be prompted for this passphrase. The maximum
588 MySQL servers. Therefore, a
590 been added which contains the login information for the different servers.
591 The first
593 contains the hostname of the first server, the second
595 the hostname of the second server, etc. In
597 server definition, however you can put as many as you need in
599 have to define all settings, just those you need to change).</dd>
603 $i-th MySQL-server. E.g. localhost.</dd>
608 ignores this port number and connects with the socket, so if you want
609 to connect to a port different from the default port, use
612 </dd>
616 To determine the correct socket, check your MySQL configuration or, using the
618 Among the resulting information displayed will be the socket used.</dd>
621 <dd>Whether to enable SSL for connection to MySQL server.
622 </dd>
625 <dd>What type connection to use with the MySQL server. Your options are
627 is nearly guaranteed to be available on all MySQL servers, while
628 sockets are not supported on some platforms.<br /><br />
630 To use the socket mode, your MySQL server must be on the same machine
631 as the Web server.</dd>
634 <dd>What php MySQL extension to use for the connection. Valid options are:
635 <br /><br />
638 The classic MySQL extension. This is the recommended and default
639 method at this time.<br /><br />
642 The improved MySQL extension. This extension became available
643 with php 5.0.0 and is the recommended way to connect to a server
647 <dd>Whether to use a compressed protocol for the MySQL server connection
648 or not (experimental).<br />
654 </dt>
656 all relational features (see
658 and, for a MySQL server previous to 4.1.2 or running with
661 authentication mode).<br /><br />
664 cookie authentication modes (or 'config'
665 authentication mode since phpMyAdmin 2.2.1), you need to supply the
670 This account is used to check what databases the user will see at
671 login.<br />
675 In phpMyAdmin versions before 2.2.5, those were called
679 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
680 <dd>Whether config or cookie or
682 should be used for this server.
684 is the plain old way: username and password are stored in
686 <li>'cookie' authentication mode
688 2.2.3 allows you to log in as any valid MySQL user with the
689 help of cookies. Username and password are stored in
690 cookies during the session and password is deleted when it
691 ends. This can also allow you to log in in arbitrary server if
692 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
693 </li>
694 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
695 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
696 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
697 <li>'signon' authentication mode
699 as introduced in 2.10.0 allows you to log in from prepared PHP
700 session data. This is useful for implementing single signon
701 from another application. Sample way how to seed session is in
707 </ul>
710 for more information.
711 </dd>
715 </dt>
716 <dd>
717 When using auth_type = 'config', this is the user/password-pair
718 which phpMyAdmin will use to connect to the
719 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
720 cookie authentication is used and should be empty.</dd>
722 <span
724 </dt>
725 <dd>
726 Allow attempt to log in without password when a login with password
727 fails. This can be used together with http authentication, when
728 authentication is done some other way and phpMyAdmin gets user name
729 from auth and uses empty password for connecting to MySQL. Password
730 login is still tried first, but as fallback, no password method is
731 tried.</dd>
734 </dt>
735 <dd>
736 If set to a (an array of) database name(s), only this (these) database(s)
737 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
738 database(s) name(s) may contain MySQL wildcards characters
742 This setting is an efficient way to lower the server load since the
743 latter does not need to send MySQL requests to build the available
745 privileges rules of the MySQL database server</span>. If set, it just
746 means only these databases will be displayed but
748 <br /><br />
750 An example of using more that one database:
752 <br /><br />
754 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
755 databases in the left frame, so that you can individually arrange your databases.<br />
756 If you want to have certain databases at the top, but don't care about the others, you do not
757 need to specify all other databases. Use:
759 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
760 order.</dd>
763 </dt>
764 <dd>Regular expression for hiding some databases. This only hides them
765 from listing, but a user is still able to access them (using, for example,
766 the SQL query area). To limit access, use the MySQL privilege system.
767 <br /><br />
772 More information on regular expressions can be found in the
774 PCRE pattern syntax</a> portion of the PHP reference manual.
775 </dd>
778 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
779 this string will be displayed instead of the hostname in the pull-down
780 menu on the main page. This can be useful if you want to show only
781 certain databases on your system, for example. For HTTP auth, all
782 non-US-ASCII characters will be stripped.</dd>
786 </dt>
787 <dd>The name of the database containing the linked-tables infrastructure.
788 <br /><br />
791 section in this document to see the benefits of this infrastructure,
792 and for a quick way of creating this database and the needed tables.
793 <br /><br />
795 If you are the only user of this phpMyAdmin installation, you can
796 use your current database to store those special tables; in this
797 case, just put your current database name in
799 set this parameter to the name of your central database containing
800 the linked-tables infrastructure.</dd>
804 </dt>
806 useful for queries you often run.<br /><br />
808 To allow the usage of this functionality:
810 <li>enter the table name in
812 </ul>
813 </dd>
817 </dt>
819 which field is a key in another table (a foreign key). phpMyAdmin
820 currently uses this to
821 <ul><li>make clickable, when you browse the master table, the data values
822 that point to the foreign table;</li>
824 when browsing the master table, if you move the mouse to a column
825 containing a foreign key (use also the 'table_info' table);<br />
828 <li>in edit/insert mode, display a drop-down list of possible foreign
832 <li>display links on the table properties page, to check referential
833 integrity (display missing foreign keys) for each described key;
834 </li>
838 schema of your database (also uses the table_coords table).</li>
839 </ul>
841 The keys can be numeric or character.<br /><br />
843 To allow the usage of this functionality:
846 infrastructure</li>
847 <li>put the relation table name in
849 <li>now as normal user open phpMyAdmin and for each one of your
850 tables where you want to use this feature, click
852 </li>
853 </ul>
857 future development of the cross-db relations.
858 </dd>
862 </dt>
863 <dd>
864 Since release 2.3.0 you can describe, in a special 'table_info'
865 table, which field is to be displayed as a tool-tip when moving the
866 cursor over the corresponding key.<br />
867 This configuration variable will hold the name of this special
868 table. To allow the usage of this functionality:
870 <li>put the table name in
872 <li>then for each table where you want to use this feature,
874 to choose the field.</li>
875 </ul>
877 </dd>
881 </dt>
884 the relations between your tables. To do this it needs two tables
889 schema output).<br /><br />
893 To allow the usage of this functionality:
896 infrastructure</li>
897 <li>put the correct table names in
900 </ul>
903 </dd>
907 </dt>
909 Since release 2.3.0 you can store comments to describe each column for
911 <br /><br />
913 Starting with release 2.5.0, comments are consequently used on the table
914 property pages and table browse view, showing up as tool-tips above the
915 column name (properties page) or embedded within the header of table in
916 browse view. They can also be shown in a table dump. Please see the
917 relevant configuration directives later on.<br /><br />
919 Also new in release 2.5.0 is a MIME-transformation system which is also
921 Transformations</a> for further information. To use the
922 MIME-transformation system, your column_info table has to have the three
923 new fields 'mimetype', 'transformation', 'transformation_options'.
924 <br /><br />
926 To allow the usage of this functionality:
928 infrastructure</li>
929 <li>put the table name in
933 <pre>
934 ALTER TABLE `pma_column_comments`
935 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
936 ADD `transformation` VARCHAR( 255 ) NOT NULL,
937 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
938 </pre>
941 renamed from<br />
944 </ul>
945 </dd>
949 </dt>
952 all queries you entered manually into the phpMyAdmin interface. If you
953 don't want to use a table-based history, you can use the JavaScript-based
954 history. Using that, all your history items are deleted when closing the
955 window.<br /><br />
957 Using
959 you can specify an amount of history items you want to have on hold. On
960 every login, this list gets cut to the maximum amount.<br /><br />
962 The query history is only available if JavaScript is enabled in your
963 browser.<br /><br />
965 To allow the usage of this functionality:
968 infrastructure</li>
970 </li>
971 </ul>
972 </dd>
976 </dt>
978 to visually manage the relations.
979 <br /><br />
981 To allow the usage of this functionality:
984 infrastructure</li>
986 </li>
987 </ul>
988 </dd>
991 </dt>
993 column_info table got enhanced with three new fields. If the above variable
995 latest table structure available. If not, it will emit a warning to the
996 superuser.<br /><br />
998 You can disable this checking behavior by setting the variable to false,
999 which should offer a performance increase.<br /><br />
1001 Recommended to set to FALSE, when you are sure, your table structure is
1002 up to date.</dd>
1004 boolean</dt>
1005 <dd>Whether to allow root access. This is just simplification of rules below.
1006 </dd>
1009 </dt>
1011 authentication is disabled.<br /><br />
1014 all deny rules followed by allow rules. Access is allowed by default. Any
1015 client which does not match a Deny command or does match an Allow command
1016 will be allowed access to the server. <br /><br />
1019 applies all allow rules followed by deny rules. Access is denied by
1020 default. Any client which does not match an Allow directive or does
1021 match a Deny directive will be denied access to the server.<br /><br />
1023 If your rule order is set to 'explicit', the authentication is
1024 performed in a similar fashion to rule order 'deny,allow', with the
1028 and was available in Apache by specifying allow and deny rules without
1029 setting any order.<br /><br />
1031 Please also see <a
1033 address behind proxies.
1034 </dd>
1036 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1037 </dt>
1038 <dd>The general format for the rules is as such:
1040 <pre>
1042 </pre>
1047 well (please note that those containing SERVER_ADDRESS might not be
1048 available on all webservers):
1049 <pre>
1055 </pre>
1057 Having an empty rule list is equivalent to either using
1063 following work:<br />
1065 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1066 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1067 But the following does not work:<br />
1070 </dd>
1071 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1072 <dd>Name of session which will be used for signon authentication method.
1073 </dd>
1075 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1076 </dd>
1078 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1079 </dd>
1082 <dd>If you have more than one server configured, you can set
1084 that server when phpMyAdmin is started, or set it to 0 to be given a
1085 list of servers without logging in.<br />
1087 MUST be set to that server.</dd>
1090 <dd>Defines whether to use GZip output buffering for increased
1092 Set to true/false for enabling/disabling. When set to 'auto' (string),
1093 phpMyAdmin tries to enable output buffering and will automatically disable
1094 it if your browser has some problems with buffering. IE6 with a certain patch
1095 is known to cause data corruption when having enabled buffering.</dd>
1098 <dd>Whether persistent connections should be used or not (mysql_connect or
1099 mysql_pconnect).</dd>
1105 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1106 to zero, no time limit is imposed.<br />
1107 This setting is used while importing/exporting dump files but has no
1108 effect when PHP is running in safe mode.</dd>
1111 <dd>Set the number of bytes a script is allowed to allocate. If number set
1112 to zero, no limit is imposed.<br />
1113 This setting is used while importing/exporting dump files but has no
1114 effect when PHP is running in safe mode.<br />
1118 <dd>Mark used tables and make it possible to show databases with locked
1123 generated by phpMyAdmin should be displayed or not.</dd>
1126 <dd>Defines whether normal users (non-administrator) are allowed to
1127 delete their own database or not. If set as FALSE, the link "Drop
1129 mydatabase" will be rejected. Quite practical for
1131 customers.<br />
1132 Please note that this limitation of SQL queries is not as strict as
1133 when using MySQL privileges. This is due to nature of SQL queries
1134 which might be quite complicated. So this choice should be viewed as
1135 help to avoid accidental dropping rather than strict privilege
1136 limitation.</dd>
1140 displayed when you're about to lose data.</dd>
1143 <dd>Define whether the previous login should be recalled or not in cookie
1144 authentication mode.</dd>
1151 means that it will be kept for existing session. This is recommended
1152 for not trusted environments.</dd>
1155 <dd>If enabled (default), logout deletes cookies for all servers,
1156 otherwise only for current one. Setting this to false makes it easy to
1157 forget to log out from other server, when you are using more of
1158 them.</dd>
1164 <dd>Define whether phpMyAdmin will continue executing a multi-query
1165 statement if one of the queries fails. Default is to abort execution.</dd>
1168 <dd>Define whether phpMyAdmin will output the results of each query of a
1169 multi-query statement embedded into the
1174 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1175 <br /><br />
1178 MySQL servers behind the firewall where your
1180 </dd>
1183 <dd>Defines whether to use a select-based menu and display only the current
1184 tables in the left frame (smaller page). Only in Non-Lightmode you can
1185 use the feature to display nested folders using
1187 </dd>
1190 <dd>In light mode, defines whether to display the names of databases (in the
1191 selector) using a tree, see also
1193 </dd>
1196 <dd>The string used to separate the parts of the database name when showing
1197 them in a tree.</dd>
1200 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1201 This means if you have tables like 'first__second__third' this will be
1203 If set to FALSE or empty, the feature is disabled. NOTE: You should
1204 not use this separator at the beginning or end of a
1205 table name or multiple times after another without any other
1206 characters in between.</dd>
1209 <dd>Defines how many sublevels should be displayed when splitting
1210 up tables by the above separator.</dd>
1213 <dd>Defines whether to display table comment as tool-tip in left frame or
1214 not.</dd>
1217 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1218 comment and the real name. That means that if you have a table called
1219 'user0001' and add the comment 'MyName' on it, you will see the name
1220 'MyName' used consequently in the left frame and the tool-tip shows
1221 the real name of the DB.</dd>
1224 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1226 When setting this to 'nested', the Alias of the Tablename is only used
1227 to split/nest the tables according to the
1229 directive. So only the folder is called like the Alias, the tablename itself
1230 stays the real tablename.</dd>
1233 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1236 <dd>Enter URL where logo in the navigation frame will point to.
1237 For use especially with self made theme which changes this.
1245 <dd>Defines whether or not to display a server choice at the top of the left frame.
1246 Defaults to FALSE.</dd>
1248 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1249 Defaults to FALSE (drop-down).</dd>
1251 <dd>Defines whether to display database choice in light navigation frame as links
1252 instead of in a drop-down. Defaults to 'auto' - on main page list is
1253 shown, when database is selected, only drop down is displayed.</dd>
1255 <dd>Defines whether or not to display space usage and statistics about databases
1256 and tables.<br />
1257 Note that statistics requires at least MySQL 3.23.3 and that, at this
1258 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1261 <dd>Defines whether to display detailed server information on main page.
1262 You can additionally hide more information by using
1264 </dd>
1269 </dt>
1272 not at the starting main (right) frame. This setting
1273 does not check MySQL commands entered directly.<br /><br />
1275 Please note that to block the usage of phpinfo() in scripts, you
1282 hard coded password value in the configuration file, end users can't
1283 be allowed to change their passwords.</dd>
1286 <dd>Defines whether to suggest a database name on the
1291 content.</dd>
1294 <dd>Defines whether navigation bar buttons and the right panel top menu
1295 contain text or symbols only. A value of TRUE displays icons, FALSE
1296 displays text and 'both' displays both icons and text.</dd>
1299 <dd>Defines whether a user should be displayed a
1303 <dd>Number of rows displayed when browsing a result set. If the result set
1310 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1314 from editing when browsing a table's content. Valid values are:
1319 </ul>
1320 </dd>
1323 <dd>Defines whether or not MySQL functions fields should be initially
1324 displayed in edit/insert mode. Since version 2.10, the user can
1325 toggle this setting from the interface.
1326 </dd>
1329 <dd>Defines which type of editing controls should be used for CHAR and
1330 VARCHAR fields. Possible values are:
1331 <ul><li>input - this allows to limit size of text to size of field in
1332 MySQL, but has problems with newlines in fields</li>
1333 <li>textarea - no problems with newlines in fields, but also no
1334 length limitations</li>
1335 </ul>
1336 Default is old behavior so input.</dd>
1342 <dd>If there are fewer items than this in the set of foreign keys, then a
1343 drop-down box of foreign keys is presented, in the style described by the
1345 setting.</dd>
1348 <dd>For the foreign key drop-down fields, there are several methods of
1349 display, offering both the key and value data. The contents of the
1350 array should be one or both of the following strings:
1356 </dt>
1357 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1358 creating a dump file</dd>
1361 </dt>
1362 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1363 compressed exports. This doesn't affect smaller dumps and allows users to
1364 create larger dumps that won't otherwise fit in memory due to php
1365 memory limit. Produced files contain more GZip/BZip2 headers, but all
1366 normal programs handle this correctly.</dd>
1370 mainframe.</dd>
1374 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1379 <dd>How many columns will be utilized to display the tables on the
1380 database property view? Default is 1 column. When setting this to a
1381 value larger than 1, the type of the database will be omitted for more
1382 display space.</dd>
1386 <dd>Defines the tab displayed by default on server view. Possible
1393 <dd>Defines the tab displayed by default on database view. Possible
1398 <dd>Defines the tab displayed by default on table view. Possible
1405 points to the MySQL documentation (type depends
1406 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1407 generated.<br />
1409 for more information about MySQL manuals and their types.</dd>
1412 <dd>Type of MySQL documentation:
1418 </ul>
1419 </dd>
1422 <dd>Defines the default language to use, if not browser-defined or
1423 user-defined.<br />
1425 this setting.</dd>
1428 <dd>Defines the default connection collation to use, if not
1429 user-defined.<br />
1434 <dd>Force: always use this language (must be defined in the
1438 <dd>Limit list of available languages to those matching the given regular
1439 expression. For example if you want only Czech and English, you should
1443 <dd>Default character set to use for recoding of MySQL queries. This must be
1444 enabled and it's described by
1446 option.<br />
1447 You can give here any character set which is in
1449 array and this is just default choice, user can select any of them.</dd>
1452 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1453 support (compiled in or module) in PHP to allow MySQL queries recoding
1454 and used language file must have it enabled (by default only these
1455 which are in Unicode, just to avoid losing some characters).<br /><br />
1458 in the Export page, to choose the character set when exporting a file.
1459 </dd>
1462 <dd>You can select here which functions will be used for character set
1463 conversion. Possible values are:
1464 <ul><li>auto - automatically use available one (first is tested
1465 iconv, then recode)</li>
1468 </ul>
1469 Default is auto.</dd>
1472 <dd>Specify some parameters for iconv used in charset conversion. See
1475 used, so that invalid characters will be transliterated.</dd>
1478 <dd>Available character sets for MySQL conversion. You can add your own (any of
1479 supported by recode/iconv) or remove these which you don't use.
1480 Character sets will be shown in same order as here listed, so if you
1481 frequently use some of these move them to the top.</dd>
1486 default empty, you need to fill in some trusted proxy servers if you
1487 want to use rules for IP addresses behind proxy.<br /><br />
1489 The following example specifies that phpMyAdmin should trust a
1491 <pre>
1492 $cfg['TrustedProxies'] =
1494 </pre>
1495 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1496 client's IP address as usual.
1497 </dd>
1501 MIME transformations.<br />
1502 Possible values are:
1503 <ul><li>auto - automatically detect, this is a bit expensive
1505 according to your server real possibilities</li>
1508 </ul>
1509 Default is auto.
1510 </dd>
1514 </dd>
1516 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1517 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1518 </dt>
1519 <dd>The background styles used for both the frames.
1522 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1524 <dd>The style used for the pointer in the navi frame.
1533 </dd>
1537 <dd>The style used for table headers. See
1542 </dd>
1546 </dd>
1548 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1550 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1552 </dt>
1554 The former feature highlights the row over which your mouse is passing
1555 and the latter lets you visually mark/unmark rows by clicking on
1556 them.<br />
1561 <dd>You put here a valid CSS font family value, for example
1566 <dd>You put here a valid CSS font family value, for example
1580 </dt>
1582 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1584 The Char* values are used for CHAR and VARCHAR editing (if configured
1588 </dt>
1592 </dt>
1593 <dd>Defines if the whole textarea of the query box will be selected on
1594 click.</dd>
1597 </dt>
1598 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1599 editing.</dd>
1602 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1603 Can be turned off by a toggle button on the browse page.</dd>
1607 </dt>
1608 <dd>Defines the place where modify and delete links would be put when
1609 tables contents are displayed (you may have them displayed both at the
1610 left and at the right).
1616 </dt>
1618 Define which one is displayed by default. The first mode displays each
1619 row on a horizontal line, the second rotates the headers by 90
1620 degrees, so you can use descriptive headers even though fields only
1621 contain small values and still print them out. The vertical mode sorts
1622 each row on a vertical lineup.<br /><br />
1624 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1625 the rotation of the header for horizontalflipped is done via CSS. If
1626 set to 'fake' PHP does the transformation for you, but of course this
1627 does not look as good as CSS.</dd>
1631 string or integer</dt>
1632 <dd>When editing/creating new columns in a table all fields normally get
1633 lined up one field a line. (default: 'horizontal'). If you set this to
1634 'vertical' you can have each field lined up vertically beneath each
1635 other. You can save up a lot of place on the horizontal direction and
1636 no longer have to scroll. If you set this to integer, editing of fewer
1637 columns will appear in 'vertical' mode, while editing of more fields
1638 still in 'horizontal' mode. This way you can still effectively edit
1639 large number of fields, while having full view on few of them.</dd>
1643 </dt>
1645 display of column comments in Browse or Property display. In browse
1646 mode, the comments are shown inside the header. In property mode,
1647 comments are displayed using a CSS-formatted dashed-line below the
1648 name of the field. The comment is shown as a tool-tip for that field.
1649 </dd>
1661 <dd>Whether to display a link to validate a query in any SQL Query box.
1668 <dd>
1669 The name of the directory where
1671 <dd>
1672 The name of the directory where
1674 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1675 are available under a drop-down box when you click the database name,
1677 <br /><br />
1679 If you want different directory for each user, %u will be replaced
1680 with username.<br /><br />
1684 compressed formats is enabled).<br /><br />
1686 This feature is useful when your file is too big to be uploaded via
1688 uploads are disabled in PHP.<br /><br />
1690 Please note that if PHP is running in safe mode, this directory must
1691 be owned by the same user as the owner of the phpMyAdmin scripts.
1692 <br /><br />
1696 alternatives.
1697 </dd>
1700 <dd>
1701 The name of the directory where dumps can be saved.<br /><br />
1703 If you want different directory for each user, %u will be replaced
1704 with username.<br /><br />
1706 Please note that the directory has to be writable for user running
1707 webserver.<br /><br />
1709 Please note that if PHP is running in safe mode, this directory must
1710 be owned by the same user as the owner of the phpMyAdmin scripts.
1711 </dd>
1714 <dd>
1715 The name of the directory where temporary files can be stored.
1716 <br /><br />
1717 This is needed for native MS Excel export, see
1720 </dd>
1723 <dd>
1724 In this array are defined default parameters for export, names of
1725 items are similar to texts seen on export page, so you can easily
1726 identify what they mean.
1727 </dd>
1730 <dd>
1731 In this array are defined default parameters for import, names of
1732 items are similar to texts seen on import page, so you can easily
1733 identify what they mean.
1734 </dd>
1737 <dd>
1738 Repeat the headers every X cells, or 0 to deactivate.
1739 </dd>
1747 </dt>
1748 <dd>
1749 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1750 or icon is always displayed on the left panel. If JavaScript is enabled in
1751 your browser, a click on this opens a distinct query window, which is
1752 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1753 changes to display a query box.<br /><br />
1755 The size of this query window can be customized with
1757 - both integers for the size in pixels. Note that normally, those
1759 theme you are using.<br /><br />
1763 opens the query window and puts the current query
1764 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1765 query in the right panel's query box.
1766 <br /><br />
1767 The usage of the JavaScript query window is recommended if you have a
1768 JavaScript enabled browser. Basic functions are used to exchange quite
1769 a few variables, so most 4th generation browsers should be capable to
1770 use that feature. It currently is only tested with Internet Explorer 6
1771 and Mozilla 1.x.
1772 <br /><br />
1774 to a table, which has to be created by you (see <a
1776 all your queries will be appended to the form, but only as long as
1777 your window is opened they remain saved.
1778 <br /><br />
1779 When using the JavaScript based query window, it will always get
1780 updated when you click on a new table/db to browse and will focus if
1781 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1782 the query window by checking the box "Do not overwrite this query from
1783 outside the window" below the query textarea. Then you can browse
1784 tables/databases in the background without losing the contents of the
1785 textarea, so this is especially useful when composing a query with
1786 tables you first have to look in. The checkbox will get automatically
1787 checked whenever you change the contents of the textarea. Please
1788 uncheck the button whenever you definitely want the query window to
1789 get updated even though you have made alterations.
1790 <br /><br />
1793 <br /><br />
1794 The query window also has a custom tabbed look to group the features.
1796 default tab to be used when opening the query window. It can be set to
1797 either 'sql', 'files', 'history' or 'full'.</dd>
1803 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1805 If the approximate row count as returned by
1808 count will be used.
1809 </dd>
1811 <dd>For VIEWs, since obtaining the exact count could have an
1812 impact on performance, this value is the maximum to be displayed, using
1814 any row counting.
1815 </dd>
1819 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1821 page. By clicking on the button 'toggle scratchboard' on the page
1822 where you edit x/y coordinates of those elements you can activate a
1823 scratchboard where all your elements are placed. By clicking on an
1824 element, you can move them around in the pre-defined area and the x/y
1825 coordinates will get updated dynamically. Likewise, when entering a
1826 new position directly into the input field, the new position in the
1827 scratchboard changes after your cursor leaves the input field.<br />
1828 You have to click on the 'OK'-button below the tables to save the new
1829 positions. If you want to place a new element, first add it to the
1830 table of elements and then you can drag the new element around.<br />
1831 By changing the paper size and the orientation you can change the size
1832 of the scratchboard as well. You can do so by just changing the
1833 dropdown field below, and the scratchboard will resize automatically,
1834 without interfering with the current placement of the elements.<br />
1835 If ever an element gets out of range you can either enlarge the paper
1836 size or click on the 'reset' button to place all elements below each
1837 other.<br />
1839 get this control to work. The basic Drag&Drop script functionality
1840 was kindly borrowed from www.youngpup.net and is underlying so
1841 specific license.</dd>
1844 <dd>Sorts database and table names according to natural order (for example,
1845 t1, t2, t10). Currently implemented in the left panel (Light mode)
1846 and in Database view, for the table list.</dd>
1852 <dd>Allows you to specify window's title bar. Following magic string can
1853 be used to get special values:
1854 <dl>
1860 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1869 </dl>
1870 </dd>
1880 </dd>
1883 <dd>If theme manager is active, use this as the path of the subdirectory
1884 containing all the themes.</dd>
1898 </dt>
1899 <dd>Default queries that will be displayed in query boxes when user didn't
1900 specify any. Use %d for database name, %t for table name and %f for a
1901 comma separated list of field names. Note that %t and %f are only
1905 <dd>
1906 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
1907 default we use HTML to format the query, but you can disable this by
1909 </dd>
1912 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1913 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1914 query inside a bracket is indented. By changing
1917 specifies the units of the indent amount that you specified. This is
1918 used via stylesheets.</dd>
1921 <dd>This array is used to define the colours for each type of element of
1922 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1924 If you specify an empty string for the color of a class, it is ignored
1925 in creating the stylesheet.
1926 You should not alter the class names, only the colour strings.<br />
1947 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1951 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1952 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1953 </ul>
1954 </dd>
1958 <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,
1959 as originally published on
1961 <br />
1962 For help in setting up your system to use the service, see the
1964 </dd>
1968 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1969 and any password, so we use those by default. Instead, if
1970 you have an account with them, you can put your login details
1971 here, and it will be used in place of the anonymous login.</dd>
1972 </dl>
1973 </dd>
1976 <dd><b>DEVELOPERS ONLY!</b></dd>
1979 <dd><b>DEVELOPERS ONLY!</b><br />
1980 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1981 the code.<br />
1982 For help in setting up your system to this, see the
1986 <dd><b>DEVELOPERS ONLY!</b><br />
1987 Enable profiling support for phpMyAdmin. This will append a chunk of data
1988 to the end of every page displayed in the main window with profiling
1989 statistics for that page.<br />
1990 You may need to increase the maximum execution time for this to
1991 complete successfully.<i>Profiling was removed from the code for
1992 version 2.9.0 due to licensing issues.</i></dd>
1994 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
1995 <dd><b>DEVELOPERS ONLY!</b><br />
1996 When profiling data is displayed, this variable controls the threshold of
1997 display for any profiling data, based on the average time each time has
1998 taken. If it is over the threshold it is displayed, otherwise it is not
1999 displayed. This takes a value in milliseconds. In most cases you don't need
2000 to edit this.</dd>
2003 <dd>All possible types of a MySQL column. In most cases you don't need to
2004 edit this.</dd>
2007 <dd>Possible attributes for fields. In most cases you don't need to edit
2008 this.</dd>
2011 <dd>A list of functions MySQL supports. In most cases you don't need to
2012 edit this.</dd>
2015 <dd>Mapping of column types to meta types used for preferring displayed
2016 functions. In most cases you don't need to edit this.</dd>
2019 <dd>Functions preferred for column meta types as defined in
2020 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2021 to edit this.</dd>
2024 <dd>Functions selected by default when inserting/changing row, Functions
2025 are defined for meta types from
2027 <code>first_timestamp</code>, which is used for first timestamp column
2028 in table.</dd>
2031 <dd>Operators available for search operations on numeric and date fields.
2032 </dd>
2035 <dd>Operators available for search operations on character fields.
2036 Note that we put <code>LIKE</code> by default instead of
2037 <code>LIKE %...%</code>, to avoid unintended performance problems
2038 in case of huge tables.</dd>
2041 <dd>Operators available for search operations on enum fields.</dd>
2044 <dd>Additional operators available for search operations when the
2045 field can be null.</dd>
2047 </dl>
2049 <!-- TRANSFORMATIONS -->
2055 </ol>
2059 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2061 section</a> on how to do so.</p>
2063 <p> You can apply different transformations to the contents of each field. The
2064 transformation will take the content of each field and transform it with
2065 certain rules defined in the selected transformation.</p>
2067 <p> Say you have a field 'filename' which contains a filename. Normally you would
2068 see in phpMyAdmin only this filename. Using transformations you can transform
2069 that filename into a HTML link, so you can click inside of the phpMyAdmin
2070 structure on the field's link and will see the file displayed in a new browser
2071 window. Using transformation options you can also specify strings to
2072 append/prepend to a string or the format you want the output stored in.</p>
2074 <p> For a general overview of all available transformations and their options,
2075 you can consult your
2076 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2077 installation.</p>
2079 <p> For a tutorial on how to effectively use transformations, see our
2081 the official phpMyAdmin homepage.</p>
2085 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2086 clicking on the 'Structure' link for a table). There click on
2087 "Change" (or change icon) and there you will see three new fields at
2088 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2089 'Transformation options'.</p>
2091 <ul><li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
2092 empty or to use 'auto' [this feature is not yet available]. Please note that
2093 transformations are inactive as long as no MIME-type is selected.</li>
2095 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2096 hopefully growing amount of pre-defined transformations. See below for information on
2097 how to build your own transformation.<br />
2099 There are global transformations and mimetype-bound transformations. Global transformations
2100 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2101 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2102 transformations which operate on the main mimetype (like 'image'), which will most likely
2103 take the subtype into regard, and those who only operate on a
2104 specific subtype (like 'image/jpeg').<br />
2106 You can use transformations on mimetypes for which the function was not defined for. There
2107 is no security check for you selected the right transformation, so take care of what the
2108 output will be like.</li>
2110 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2111 transform-function specific options here. Usually the transforms can operate with default
2112 options, but it is generally a good idea to look up the overview to see which options are
2113 necessary.<br />
2115 Much like the ENUM/SET-Fields, you have to split up several options using the format
2116 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2117 parsed as an array, leaving the first value the first element in the array, and so
2118 forth.<br />
2120 If you want to specify a MIME character set you can define it in the transformation_options.
2121 You have to put that outside of the pre-defined options of the specific mime-transform,
2123 for which you can specify 2 options and you want to append a character set, enter "'first
2124 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2126 </ul>
2130 <p> All mimetypes and their transformations are defined through single files in
2131 the directory 'libraries/transformations/'.</p>
2133 <p> They are stored in files to ease up customization and easy adding of new
2134 transformations.</p>
2136 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2137 always work. It makes no sense to apply a transformation to a mimetype, the
2138 transform-function doesn't know to handle.</p>
2140 <p> One can, however, use empty mime-types and global transformations which should work
2141 for many mimetypes. You can also use transforms on a different mimetype they where built
2142 for, but pay attention to option usage as well as what the transformation does to your
2143 field.</p>
2145 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2146 any other transform function and provides some basic functions.</p>
2148 <p> There are 5 possible file names:</p>
2150 <ol><li>A mimetype+subtype transform:<br /><br />
2152 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2154 Please not that mimetype and subtype are separated via '_', which shall
2155 not be contained in their names. The transform function/filename may
2156 contain only characters which cause no problems in the file system as
2157 well as the PHP function naming convention.<br /><br />
2159 The transform function will the be called
2160 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2162 <b>Example:</b><br /><br />
2164 <tt>text_html__formatted.inc.php</tt><br />
2165 <tt>PMA_transform_text_html__formatted()</tt></li>
2167 <li>A mimetype (w/o subtype) transform:<br /><br />
2169 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2171 Please note that there are no single '_' characters.
2172 The transform function/filename may contain only characters which cause
2173 no problems in the file system as well as the PHP function naming
2174 convention.<br /><br />
2176 The transform function will the be called
2177 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2179 <b>Example:</b><br /><br />
2181 <tt>text__formatted.inc.php</tt><br />
2182 <tt>PMA_transform_text__formatted()</tt></li>
2184 <li>A mimetype+subtype without specific transform function<br /><br />
2186 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2188 Please note that there are no '__' characters in the filename. Do not
2189 use special characters in the filename causing problems with the file
2190 system.<br /><br />
2192 No transformation function is defined in the file itself.<br /><br />
2194 <b>Example:</b><br /><br />
2196 <tt>text_plain.inc.php</tt><br />
2197 (No function)</li>
2199 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2201 <tt>[mimetype].inc.php</tt><br /><br />
2203 Please note that there are no '_' characters in the filename. Do not use
2204 special characters in the filename causing problems with the file system.
2205 <br /><br />
2207 No transformation function is defined in the file itself.<br /><br />
2209 <b>Example:</b><br /><br />
2211 <tt>text.inc.php</tt><br />
2212 (No function)</li>
2214 <li>A global transform function with no specific mimetype<br /><br />
2216 <tt>global__[transform].inc.php</tt><br /><br />
2218 The transform function will the be called
2219 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2221 <b>Example:</b><br /><br />
2223 <tt>global__formatted</tt><br />
2224 <tt>PMA_transform_global__formatted()</tt></li>
2225 </ol>
2227 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2228 transform function.</p>
2230 <p> All filenames containing no '__' in themselves are not shown as valid transform
2231 functions in the dropdown.</p>
2233 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2234 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2235 without a transform function. Also note the introduction of a function description in
2236 the language files. For each function a $strTransformation_[filename without .inc.php]
2237 has to exist.</p>
2239 <p> You can use the template generator to generate new functions and entries in the
2240 language file.</p>
2242 <p> To create a new transform function please see
2243 <tt>libraries/transformations/template_generator.sh</tt>.
2244 To create a new, empty mimetype please see
2245 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2247 <p> A transform function always gets passed three variables:</p>
2249 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2250 you want to transform.</li>
2251 <li><b>$options</b> - Contains any user-passed options to a transform function
2252 as an array.</li>
2253 <li><b>$meta</b> - Contains an object with field information to your column.
2254 The data is drawn from the output of the
2256 function. This means, all object properties described on the
2258 available in this variable and can be used to transform a field accordingly
2259 to unsigned/zerofill/not_null/... properties.<br />
2260 The $meta->mimetype variable contains the original MIME-type of the
2261 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2262 </ol>
2264 <!-- FAQ -->
2271 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2275 </ol>
2277 <p> Please have a look at our
2279 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2280 features and or interface.</p>
2286 action is required or phpMyAdmin sends a blank page or a page full of
2287 cryptic characters to my browser, what can I do?</a></h4>
2289 <p> There are some known PHP bugs with output buffering and compression.<br />
2291 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2292 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2293 configuration file.<br />
2294 Furthermore, we know about such problems connected to the release
2295 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2296 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2301 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2302 See also the
2304 entry about PHP bugs with output buffering.<br />
2305 If your server keeps crashing, please ask for help in the various Apache
2306 support groups.</p>
2310 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2311 script: I'm always displayed the login screen.</a></h4>
2313 <p> This is a known PHP bug (see this
2315 official PHP bug database. It means there is and won't be any phpMyAdmin
2316 fix against it because there is no way to code a fix.</p>
2322 application misbehaved by not returning a complete set of
2324 </h4>
2326 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2327 Have a look at the last message in this
2329 official PHP bug database.</p>
2334 and/or many error messages with the
2336 mode.</a></h4>
2338 <p> This is a known problem with the PHP
2340 filter: it's not so stable. Please use instead the cookie authentication mode.
2341 </p>
2346 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2347 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2348 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2349 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2350 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2355 work.</a></h4>
2357 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2358 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2359 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2360 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2361 We faced PHP crashes when trying to download a dump with MS Internet
2362 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2363 this case you should switch to the release version of PHP 4.2.0.</p>
2367 an error about safe mode being in effect.</a></h4>
2369 <p> Your uploaded file is saved by PHP in the "upload dir", as
2370 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2371 the system default is <i>/tmp</i>).<br />
2372 We recommend the following setup for Apache servers running in safe mode,
2373 to enable uploads of files while being reasonably secure:</p>
2375 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2376 <li>give ownership to the Apache server's user.group:
2377 <tt>chown apache.apache /tmp/php</tt></li>
2378 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2379 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2380 <li>restart Apache</li>
2381 </ul>
2385 general file uploads don't work on my system and uploaded files have a
2386 <tt>Content-Type:</tt> header in the first line.</a></h4>
2388 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2389 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2390 So the problem is that this package has a serious bug that was corrected
2391 ages ago in PHP (2001-01-28: see
2393 for more details). The problem is that the bugged package is still
2394 available though it was corrected (see
2396 for more details).<br />
2397 So please download
2398 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2399 and the problem should go away.<br />
2400 And that fixes the \r\n problem with file uploads!</p>
2404 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2405 I'm using the Apache server.</a></h4>
2407 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2408 your <i>httpd.conf</i>:</p>
2412 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2416 uploading a file from the query box.</a></h4>
2418 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2419 restrictions. Assuming that the restriction allows you to open files in the
2420 current directory ('.'), all you have to do is create a 'tmp' directory
2421 under the phpMyAdmin install directory, with permissions 777 and the same
2422 owner as the owner of your phpMyAdmin directory. The uploaded files will
2423 be moved there, and after execution of your
2429 <p> The MySQL manual explains how to
2431 reset the permissions</a>.</p>
2436 execute a bookmark.</a></h4>
2438 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2439 cannot access the uploaded query.</p>
2444 submit a query from the convenient text area.</a></h4>
2446 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2447 and try to increase it.</p>
2451 </h4>
2453 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2454 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2455 names to align with current standards.</p>
2460 </h4>
2462 <p> Starting with version 2.7.0, the import engine has been re–written and these
2463 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2464 to take advantage of the new import features.</p>
2466 <p> The first things to check (or ask your host provider to check) are the
2467 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2468 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2469 All of these three settings limit the maximum size of data that can be
2470 submitted and handled by PHP. One user also said that post_max_size
2471 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2473 There exist several workarounds if your upload is too big or your
2474 hosting provider is unwilling to change the settings:</p>
2477 feature. This allows one to
2478 upload a file to the server via scp, ftp, or your favorite file transfer
2479 method. PhpMyAdmin is then able to import the files from the temporary
2481 section</a> of this document.</li>
2483 BigDump</a>) to split the files before uploading. We cannot support this
2484 or any third party applications, but are aware of users having success
2485 with it.</li>
2486 <li>If you have shell (command line) access, use MySQL to import the files
2487 directly. You can do this by issuing the "source" command from
2488 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2489 </ul>
2493 support?</a></h4>
2495 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2496 fully supported. Please note that the older your MySQL version is, the more
2497 limitations you will have to face.<br />
2498 phpMyAdmin may connect to your MySQL server using php's classic
2501 is available in php 5.0.<br />
2502 Either way, the developers of both extensions recommend to use the classic
2503 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2504 When compiling php, we strongly recommend that you manually link the MySQL
2505 extension of your choice to a MySQL client library of at least the same
2506 minor version since the one that is bundled with some php distributions is
2509 If your webserver is running on a windows system, you might want to try
2510 MySQL's
2512 instead of the MySQL / MySQLi extensions that are bundled with the official
2513 php Win32 builds.
2514 <br />
2515 MySQL 5.1 is not yet supported.</p>
2519 message, "Client does not support authentication protocol requested
2520 by server; consider upgrading MySQL client"</a></h5>
2522 <p> You tried to access MySQL with an old MySQL client library. The version of
2523 your MySQL client library can be checked in your phpinfo() output.
2524 In general, it should have at least the same minor version as your server
2528 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2529 changed the authentication hash and your PHP is trying to use the old method.
2531 with the proper client library to match your MySQL installation. Your
2532 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2533 More information (and several workarounds) are located in the
2535 </p>
2539 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2540 capital letter in its name it is changed to lowercase as it should. But
2541 if I try to DROP this table MySQL is unable to find the corresponding
2542 file.</a></h4>
2544 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2545 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2546 directive.</p>
2550 script seems not to know the font face I'm using!</a></h4>
2552 <p> The "FPDF" library we're using for this feature requires some
2553 special files to use font faces.<br />
2555 these files.</p>
2559 check PHP Configuration".</a></h4>
2561 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2562 "MySQL extension". This extension may be part of the PHP
2563 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2564 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2565 to load the extension but failed.<br /><br />
2567 Usually, the problem is solved by installing a software package called
2568 "PHP-MySQL" or something similar.</p>
2573 and I cannot log in using cookie auth.</a></h4>
2575 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2579 so I cannot upload.</a></h4>
2581 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2582 parameter is not set to "on".</p>
2586 a new table the table and field names are changed to lowercase!</a></h4>
2588 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2589 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2590 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2591 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2592 directory and add the following line to the group [mysqld]:</p>
2594 <pre>set-variable = lower_case_table_names=0</pre>
2596 <p> Next, save the file and restart the MySQL service. You can always check the
2597 value of this directive using the query</p>
2599 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2603 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2606 </p>
2610 and I get problems, such as undefined variables when I run a
2613 <p> A tip from Jose Fandos: put a comment on the following two lines
2614 in httpd.conf, like this:</p>
2616 <pre>
2617 # mod_gzip_item_include file \.php$
2619 </pre>
2621 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2622 PHP scripts. Of course you have to restart Apache.</p>
2627 I get the error "No input file specified" when trying to
2628 run phpMyAdmin.</a></h4>
2630 <p> This is a permission problem. Right-click on the phpmyadmin folder
2631 and choose properties. Under the tab Security, click on "Add"
2632 and select the user "IUSR_machine" from the list. Now set his
2633 permissions and it should work.</p>
2637 db_structure.php with plenty of tables).</a></h4>
2640 GZIP output buffering is enabled. If you turn off it (by
2642 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2643 PHP 5.0.0.</p>
2647 message 'Errorcode: 13'. What does this mean?</a></h4>
2649 <p> This can happen due to a MySQL bug when having database / table names with
2650 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2651 To fix this, turn off this directive, convert all database and table names
2652 to lower case and turn it on again. Alternatively, there's a bug-fix
2653 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2657 and the fields are duplicated.</a></h4>
2659 <p> It is possible to configure Apache in such a way that PHP has problems
2660 interpreting .php files.</p>
2662 <p> The problems occur when two different (and conflicting) set of directives
2663 are used:</p>
2665 <pre>
2666 SetOutputFilter PHP
2667 SetInputFilter PHP
2668 </pre>
2670 <p> and</p>
2672 <pre>AddType application/x-httpd-php .php</pre>
2674 <p> In the case we saw, one set of directives was in
2675 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2676 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2677 The recommended way is with <tt>AddType</tt>, so just comment out
2678 the first set of lines and restart Apache:</p>
2680 <pre>
2681 #SetOutputFilter PHP
2682 #SetInputFilter PHP
2683 </pre>
2688 <p> This problem is known to happen when the server is running Turck MMCache
2689 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2694 <p> Yes.<br />
2695 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2696 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2697 <tt>error_reporting</tt> settings.
2698 </p>
2701 <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>
2703 <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>
2706 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2707 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2708 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2709 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2710 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2711 enabled.) Click <tt>OK</tt>.</li>
2712 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2713 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2714 </ol>
2718 PHP 5.0.4 on 64-bit systems?</a></h4>
2720 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2721 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2727 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2728 Table and script parts are optional. If you want
2729 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2730 some configuration. Following lines apply only for <a
2732 that you have enabled some features within global configuration. You need
2733 <code>Options FollowSymLinks</code> and <code>AllowOverride
2734 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2735 you need mod_rewrite to be enabled. Then you just need to create following
2736 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2737 (don't forget to change directory name inside of it):</p>
2739 <pre>
2740 RewriteEngine On
2741 RewriteBase /path_to_phpMyAdmin
2742 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2743 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2744 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2745 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2746 </pre>
2749 <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>
2751 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2752 following rewrite rule:</p>
2754 <pre>
2755 RewriteEngine On
2756 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2757 </pre>
2761 </h4>
2762 <p>
2763 There can be many explanations to this and a look at your server's
2764 error log file might give a clue.
2765 </p>
2769 password encryption in cookie auth doesn't work.</a></h4>
2771 <p> If your cluster consist of different architectures, PHP code used for
2772 encryption/decryption won't work correct. This is caused by use of
2773 pack/unpack functions in code. Only solution is to use mcrypt extension
2774 which works fine in this case.</p>
2780 headers already sent by ..." is displayed, what's the problem?</a></h4>
2782 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2783 (I.E. no blank lines, no spaces, no characters...) neither before the
2784 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2785 tag at the end. We also got a report from a user under IIS, that used
2786 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2787 contained an end-of-line character (hex 0A) at the end; removing this character
2788 cleared his errors.</p>
2793 <p> Either there is an error with your PHP setup or your username/password is
2794 wrong. Try to make a small script which uses mysql_connect and see if it
2795 works. If it doesn't, it may be you haven't even compiled MySQL support
2796 into PHP.</p>
2800 connect to local MySQL server through socket '/tmp/mysql.sock'
2801 (111) ..." is displayed. What can I do?</a></h4>
2803 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2805 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2806 In your <i>php.ini</i> you will find a line</p>
2808 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2810 <p> change it to</p>
2812 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2814 <p> Then restart apache and it will work.</p>
2816 <p> Here is a fix suggested by Brad Ummer:</p>
2818 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2819 To do this, telnet to your server and go to the MySQL bin directory. In
2820 this directory there should be a file named <i>mysqladmin</i>. Type
2821 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2822 info about your MySQL server, including the socket
2823 (<i>/tmp/mysql.sock</i>, for example).</li>
2824 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2825 phpMyAdmin, you need to complete the socket information in the
2826 <i>config.inc.php</i>.<br />
2827 For example:
2829 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2830 <br /><br />
2832 Please also make sure that the permissions of this file allow to be readable
2833 by your webserver (i.e. '0755').</li>
2834 </ul>
2836 <p> Have also a look at the
2838 corresponding section of the MySQL documentation</a>.</p>
2842 what can I do?</a></h4>
2845 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2846 sometime.<br />
2847 Also have a look at your PHP version number: if it contains "4.0b..."
2848 it means you're running a beta version of PHP. That's not a so good idea,
2849 please upgrade to a plain revision.</p>
2853 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2854 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2856 <p> Check the value you set for the
2858 directive in the phpMyAdmin configuration file.</p>
2862 password: YES)"-error when trying to access a MySQL-Server on a
2863 host which is port-forwarded for my localhost.</a></h4>
2865 <p> When you are using a port on your localhost, which you redirect via
2866 port-forwarding to another host, MySQL is not resolving the localhost
2867 as expected.<br />
2868 Erik Wasser explains: The solution is: if your host is "localhost"
2869 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2870 connection for speeding up things. And that doesn't work in this configuration
2871 with port forwarding.<br />
2877 <p> Themes are configured with
2881 <br />
2883 should not delete the directory "original" or its underlying
2884 structure, because this is the system theme used by phpMyAdmin.
2885 "original" contains all images and styles, for backwards
2886 compatibility and for all themes that would not include images or css-files.
2887 <br /><br />
2890 is enabled, you can select your favorite theme on the main page. Your
2891 selected theme will be stored in a cookie.<br /><br /></p>
2893 <p> To create a theme:</p>
2895 <ul><li>make a new subdirectory (for example "your_theme_name") under
2897 (by default <tt>themes</tt>)</li>
2898 <li>copy the files and directories from "original" to
2899 "your_theme_name"</li>
2900 <li>edit the css-files in "your_theme_name/css"</li>
2901 <li>put your new images in "your_theme_name/img"</li>
2902 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2903 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2904 contain your chosen theme name, that will be visible in user interface</li>
2905 <li>make a new screenshot of your theme and save it under
2906 "your_theme_name/screen.png"</li>
2907 </ul>
2909 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2910 theme verbose name, theme generation and theme version. These versions and
2911 generations are enumerated from 1 and do not have any direct dependence on
2912 phpMyAdmin version. Themes within same generation should be backwards
2913 compatible - theme with version 2 should work in phpMyAdmin requiring
2914 version 1. Themes with different generation are incompatible.</p>
2916 <p> If you do not want to use your own symbols and buttons, remove the
2917 directory "img" in "your_theme_name". phpMyAdmin will
2918 use the default icons and buttons (from the system-theme "original").
2919 </p>
2923 what can I do?</a></h4>
2925 <p> Here are a few points to check:</p>
2927 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2929 directive empty. See also
2931 </li>
2932 <li>Maybe you have a broken PHP installation or you need to upgrade
2933 your Zend Optimizer. See
2935 http://bugs.php.net/bug.php?id=31134</a>.
2936 </li>
2937 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2938 set to the default (200) or another low value, you could get this
2939 error if your table has a high number of columns. Adjust this setting
2940 accordingly. (Thanks to Klaus Dorninger for the hint).
2941 </li>
2942 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2943 of ";" will cause this error. Replace it with "&;".
2944 </li>
2946 you might want to increase
2948 </li>
2949 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
2950 </li>
2951 </ul>
2958 who logged out can not log in again in with the same nick.</a></h4>
2960 <p> This is related to the authentication mechanism (protocol) used by
2961 phpMyAdmin. To bypass this problem: just close all the opened
2962 browser windows and then go back to phpMyAdmin. You should be able to
2963 log in again.</p>
2967 limit error or a time limit error.</a></h4>
2969 <p> Compressed dumps are built in memory and because of this are limited to
2970 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2971 using
2973 (enabled by default). Zip exports can not be handled this way, so if you need
2974 Zip files for larger dump, you have to use another way.</p>
2978 or alter a table.</a></h4>
2980 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
2984 bundled with the MySQL server distribution.</a></h4>
2986 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
2988 <pre>
2989 -- MySQL dump 8.22
2990 --
2991 -- Host: localhost Database: database
2992 ---------------------------------------------------------
2993 -- Server version 3.23.54
2994 </pre>
2996 <p> The invalid part of the code is the horizontal line made of dashes that
2997 appears once in every dump created with mysqldump. If you want to run your
2998 dump you have to turn it into valid MySQL. This means, you have to add a
2999 whitespace after the first two dashes of the line or add a # before it:
3000 <br />
3001 <code>
3002 -- -------------------------------------------------------<br />
3003 </code>
3004 or<br />
3005 <code>
3006 #---------------------------------------------------------
3007 </code>
3008 </p>
3015 <p> Please note that you should not use the separating string multiple times
3016 without any characters between them, or at the beginning/end of your table
3017 name. If you have to, think about using another TableSeparator or disabling
3018 that feature</p>
3023 <p> In Relation view, being able to choose a table in another database,
3024 or having more than one index field in the foreign key.<br /><br/>
3025 In Query-by-example (Query), automatic generation of the query
3026 LEFT JOIN from the foreign table.<br /><br/>
3027 </p>
3031 I get series of errors like "Warning: unable to parse url". How
3032 can this be fixed?</a></h4>
3033 <p>
3034 Your table neither have a primary key nor an unique one, so we must use a
3035 long expression to identify this row. This causes problems to parse_url
3036 function. The workaround is to create a primary or unique key.
3037 <br />
3038 </p>
3042 a MIME-Transformation onto!</a></h4>
3044 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3045 nested forms can be put inside the table where phpMyAdmin displays the results.
3046 You can, however, use any form inside of a table if keep the parent
3047 form-container with the target to tbl_row_delete.php and just put your own
3048 input-elements inside. If you use a custom submit input field, the form will
3049 submit itself to the displaying page again, where you can validate the
3050 $HTTP_POST_VARS in a transformation.
3052 For a tutorial on how to effectively use transformations, see our
3054 on the official phpMyAdmin-homepage.</p>
3058 MySQL server</a></h4>
3060 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3063 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3064 the quote-character (") is interpreted as an identifier quote character and
3065 not as a string quote character, which makes many internal phpMyAdmin
3067 statements. There is no workaround to this behaviour. News to this item will
3068 be posted in Bug report
3069 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3070 </p>
3074 more that one column with the same value
3075 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3076 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3078 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3079 can use it for the Edit and Delete links.</p>
3084 <p> phpMyAdmin uses a quick method to get the row count, and this method
3085 only returns an approximate count in the case of InnoDB tables. See
3087 a way to modify those results, but
3088 this could have a serious impact on performance.</p>
3093 <p> The number of records in queries containing COUNT and GROUP BY is
3094 not correctly calculated. Also, sorting results of a query like
3099 containing an hyphen.
3100 </a></h4>
3101 <p>
3102 The tests I have made with current MySQL 4.1.11 API shows that the
3103 API does not accept this syntax for the USE command. Enclosing the
3104 db name with backquotes works. For further confusion, no backquotes
3105 are needed with command-line mysql.
3106 </p>
3109 <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>
3110 <p>
3111 This has been a known limitation of phpMyAdmin since the beginning and
3112 it's not likely to be solved in the future.
3113 </p>
3115 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3118 <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
3119 need to install it for each customer.
3120 </a></h4>
3121 <p>
3122 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3123 your users. The development of this feature was kindly sponsored by
3124 NetCologne GmbH.
3125 This requires a properly setup MySQL user management and phpMyAdmin
3126 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3128 </p>
3132 access.
3133 </a></h4>
3134 <p>
3135 This depends on your system.<br />
3136 If you're running a server which cannot be accessed by other people, it's
3137 sufficient to use the directory protection bundled with your webserver
3139 If other people have telnet access to your server, you should use
3140 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3141 <br /><br />
3142 Suggestions:
3143 </p>
3144 <ul>
3145 <li>
3147 </li>
3148 <li>
3149 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3150 is a user whose password is only known to you, and apache is the
3151 group under which Apache runs.
3152 </li>
3153 <li>
3154 You should use PHP safe mode, to protect from other users that try
3156 </li>
3157 </ul>
3162 </a></h4>
3163 <p>
3168 </p>
3171 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3172 authentication.
3173 </a></h4>
3177 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3178 and/or
3180 are wrong.</li>
3182 <li>You have already setup a security mechanism for the
3183 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3184 phpMyAdmin's authentication, so remove it.</li>
3185 </ul>
3192 and put the privileges you want. For example,
3194 would let a user create/manage his/her database(s).</p>
3199 <p> If you have existing rules from an old .htaccess file, you can take them
3202 be a major benefit here if your installation is suited to using it. Then
3203 you can just add those updated lines into the
3207 <p> If you want a pre-made sample, you can try this fragment. It stops the
3208 'root' user from logging in from any networks other than the private
3211 <pre>
3212 //block root from logging in except from the private networks
3213 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3214 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3215 'deny root from all',
3216 'allow root from localhost',
3220 );
3221 </pre>
3226 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3227 different than the one set in your
3229 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3230 while a domain name is defined in the config file.</p>
3235 <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>
3241 when trying to create a table with more than 14 fields.
3242 </a></h4>
3243 <p>
3244 We could reproduce this problem only under Win98/98SE. Testing under
3245 WinNT4 or Win2K, we could easily create more than 60 fields.
3246 <br />
3247 A workaround is to create a smaller number of fields, then come back to
3248 your table properties and add the other fields.
3249 </p>
3253 <p>
3254 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3255 with each script/website that use forms.<br />
3256 Upgrade or downgrade your Xitami server.
3257 </p>
3260 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3261 <p>
3262 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3263 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3264 don't seem to work.<br />
3266 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3267 the user's temporary directory, so they must be moved before closing
3268 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3271 </p>
3275 Explorer never stores the cookies.
3276 </a></h4>
3277 <p>
3278 MS Internet Explorer seems to be really buggy about cookies, at least till
3280 in this area!
3281 <br />
3282 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3283 work!
3284 </p>
3288 rows.
3289 </a></h4>
3290 <p>
3292 </p>
3295 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3296 when trying to modify a row in a table with many fields, or with a text field
3297 </a></h4>
3298 <p>
3299 Your table neither have a primary key nor an unique one, so we must use a
3300 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
3301 those browsers, and this not happen in Netscape, for example. The
3302 workaround is to create a primary or unique key, or use another browser.
3303 <br />
3304 </p>
3308 page.
3309 </a></h4>
3310 <p>
3311 Some browsers support right-clicking into the frame you want to refresh,
3312 just do this in the right frame.<br />
3313 </p>
3317 query box.
3318 </a></h4>
3319 <p>
3320 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3321 Mozilla versions.<br />
3322 </p>
3326 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3327 </a></h4>
3328 <p>
3329 This is a Mozilla bug (see bug #26882 at
3331 </p>
3336 </a></h4>
3337 <p>
3338 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3339 data in octet-stream mode. Since we can't detect the specific Netscape
3340 version, we cannot workaround this bug.
3341 </p>
3345 wrong.</a></h4>
3347 <p> Please ensure that you have set your browser's character set to the one of the
3348 language file you have selected on phpMyAdmin's start page.
3349 Alternatively, you can try the auto detection mode that is supported by the
3350 recent versions of the most browsers.</p>
3353 <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
3356 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3357 Netscape and Mozilla do not have this problem.</p>
3360 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3361 I cannot manage two servers: I log in to the first one, then the other one,
3362 but if I switch back to the first, I have to log in on each operation.</a></h4>
3368 but nothing happens after that, only a blank screen.</a></h4>
3371 bug in Opera6, because it is not able to interpret frameset definitions
3372 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3373 Opera7 at least.</p>
3382 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3387 address and you are starting
3389 containing a domain name, or the reverse situation.</li>
3390 <li>Security settings in IE and/or Microsoft Security Center are
3391 too high, thus blocking scripts execution.</li>
3392 <li>The Windows Firewall is blocking Apache and MySQL. You must
3396 </ul>
3399 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3400 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3401 installed in their Firefox is causing the problem.</p>
3408 </a></h4>
3409 <p>
3410 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3411 specifying a wrong field-type.<br />
3412 Common errors include:
3413 </p>
3414 <ul>
3417 </ul>
3418 <p>
3419 Also, look at the syntax chapter in the MySQL manual to confirm that your
3420 syntax is correct.
3421 </p>
3425 phpMyAdmin generates only one index with those 2 fields.
3426 </a></h4>
3427 <p>
3429 index. If you want two indexes, create the first one when creating the
3430 table, save, then display the table properties and click the Index link to
3431 create the other index.
3432 </p>
3436 <p>
3437 Since version 2.2.3, you have a checkbox for each field that can be null.
3439 field's value. Since version 2.5.5, you have to use the checkbox to get
3441 a literal NULL in the field, and not a NULL value (this works in PHP4).
3442 </p>
3447 <p> Click on a database or table name in the left frame, the properties will be
3449 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3450 statements that can be used to recreate your database/table.
3451 <br /><br />
3453 transmit the resulting dump to your station. Depending on your PHP
3454 configuration, you will see options to compress the dump. See also the
3456 configuration variable.<br /><br />
3459 this document.</p>
3464 </a></h4>
3466 <p> Click on a database name in the left frame, the properties will be
3468 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3470 the path to your dump filename, or use the Browse button. Then click Go.
3471 <br /><br />
3473 that you upgrade to take advantage of the new features.
3474 <br /><br />
3476 in this document.
3477 </p>
3482 <p> Here is an example with the tables persons, towns and countries, all
3484 table, create it as explained in the configuration section. Then create the
3485 example tables:</p>
3487 <pre>
3488 CREATE TABLE REL_countries (
3489 country_code char(1) NOT NULL default '',
3490 description varchar(10) NOT NULL default '',
3491 PRIMARY KEY (country_code)
3492 ) TYPE=MyISAM;
3494 INSERT INTO REL_countries VALUES ('C', 'Canada');
3496 CREATE TABLE REL_persons (
3497 id tinyint(4) NOT NULL auto_increment,
3498 person_name varchar(32) NOT NULL default '',
3500 country_code char(1) NOT NULL default '',
3501 PRIMARY KEY (id)
3502 ) TYPE=MyISAM;
3504 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3505 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3507 CREATE TABLE REL_towns (
3509 description varchar(30) NOT NULL default '',
3510 PRIMARY KEY (town_code)
3511 ) TYPE=MyISAM;
3513 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3514 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3515 </pre>
3521 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3525 </ul>
3533 <li>In the fields row, choose persons.person_name and click the
3535 <li>Do the same for towns.description and countries.descriptions in the
3538 the correct joins have been generated</li>
3540 </ul>
3544 <p>
3545 Starting from the previous example, create the pma_table_info as explained
3546 in the configuration section, then browse your persons table,
3547 and move the mouse over a town code or country code.
3548 <br /><br />
3549 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3550 enables: drop-down list of possible values.
3551 </p>
3554 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3555 <p>
3558 <br /><br />
3559 Then you need to think about your schema layout. Which tables will go on
3560 which pages?
3561 </p>
3562 <ul>
3568 page and click Go. If you like, you
3570 linked tables onto the new page.</li>
3571 <li>Select the name of the new page (making sure the Edit radio button
3572 is selected) and click Go.</li>
3574 Coordinates are relative; your diagram will
3575 be automatically scaled to fit the page. When initially placing tables
3576 on the page, just pick any coordinates -- say, 50x50. After clicking
3578 position the element correctly.</li>
3580 first be sure to click the Save
3581 button beneath the list of tables and coordinates, to save any changes
3582 you made there. Then scroll all the way down, select the
3584 you want, and click Go.</li>
3585 <li>Internet Explorer for Windows may suggest an incorrect filename when
3590 browsers on Windows, do not have this problem.</li>
3591 </ul>
3595 columns!</a></h4>
3597 <p> No, it's MySQL that is doing
3603 underscores in the database name?</a></h4>
3605 <p> If you do not put a backslash before the underscore, this is a wildcard
3608 john2db ...<br /><br />
3610 If you put a backslash before the underscore, it means that the database
3611 name will have a real underscore.</p>
3615 statistics pages?</a></h4>
3626 if it already exists during the import. It does NOT drop the table after
3627 your export, it only affects the import file.</li>
3629 Otherwise, you may get an error if the table name exists but has a
3630 different structure.</li>
3632 (if any) will be included in backup.</li>
3634 field and table names formed with special characters are protected.</li>
3636 types set in the pmadb in the dump as
3638 </li>
3639 </ul>
3644 command, for better documentation (but resulting file is bigger).</li>
3646 once the INSERT verb and the table name.</li>
3649 </li>
3651 more info is provided in the
3653 but basically with this selected, invalid values are adjusted and
3654 inserted rather than causing the entire statement to fail.</li>
3655 </ul>
3659 in its name.</a></h4>
3662 is the normal way to reference a database and table name. Worse, MySQL
3663 will usually let you create a database with a dot, but then you cannot
3664 work with it, nor delete it.</p>
3677 for usage.<br />
3678 On a more recent pear version, I had problems with the state of Net_DIME
3679 being beta, so this single command
3681 needed modules.<br />
3682 If you use the Validator, you should be aware that any
3684 submit will be stored anonymously (database/table/column names,
3685 strings, numbers replaced with generic values). The Mimer
3688 We utilize it as free SOAP service.</p>
3692 it, but MySQL says "BLOB column '...' used in key specification without
3695 <p> The right way to do this, is to create the field without any indexes,
3697 dialog. On this page, you will be able to choose your BLOB field, and
3698 set a size to the index, which is the condition to create an index on
3699 a BLOB field.</p>
3703 editing fields?</a></h4>
3705 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3706 with many editing fields (table structure changes, row editing, etc.)
3707 (must be enabled in configuration - see.
3709 You can also have a look at the directive
3711 ('vertical') and see if this eases up editing for you.</p>
3715 WTF is this feature then useful for?</a></h4>
3717 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3718 on them. Otherwise you could just put a comment on the field. Because entering
3719 your own mimetype will cause serious syntax checking issues and validation,
3720 this introduces a high-risk false-user-input situation. Instead you have to
3721 initialize mimetypes using functions or empty mimetype definitions.<br />
3722 Plus, you have a whole overview of available mimetypes. Who knows all those
3723 mimetypes by heart so he/she can enter it at will?</p>
3727 can't I see any bookmarks below the query box? What is this variable for?
3728 </a></h4>
3730 <p> Any query you have executed can be stored as a bookmark on the page where the
3731 results are displayed. You will find a button labeled 'Bookmark this query'
3732 just at the end of the page.<br />
3733 As soon as you have stored a bookmark, it is related to the database you run
3734 the query on. You can now access a bookmark dropdown on each page, the query
3735 box appears on for that database.<br /><br />
3737 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3741 aware of that you HAVE to create a valid query, otherwise your query won't be
3742 even able to be stored in the database.<br />
3744 for your query will remain the way it is, but will be stripped of the /**/
3745 chars. So you can use:<br /><br />
3749 which will be expanded to<br /><br />
3753 in your query, where VARIABLE is the string you entered in the input box. If
3754 an empty string is provided, no replacements are made.<br /><br />
3756 A more complex example. Say you have stored this query:<br /><br />
3758 <br /><br />
3761 the full query will be:<br /><br />
3764 <br /><br />
3768 spaces inserted there
3769 will be later also inserted as spaces in your query and may lead to unexpected
3770 results especially when
3772 Your initial query which is going to be stored as a bookmark has to yield at
3773 least one result row so
3774 you can store the bookmark. You may have that to work around using well
3778 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3779 include exported table?</a></h4>
3781 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3782 document should look like following one (assuming you have table
3785 <pre>
3786 \documentclass{article} % or any class you want
3787 \usepackage{longtable} % for displaying table
3788 \begin{document} % start of document
3789 \include{table} % including exported table
3790 \end{document} % end of document
3791 </pre>
3795 access them.
3796 </a></h4>
3799 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3800 enable users to see all the database names.
3803 So if your users do not need those privileges, you can remove them and their
3804 databases list will shorten.</p>
3808 possible values for a field, based on some foreign table?</a></h4>
3810 <p> You have to setup appropriate links between the tables, and also
3814 foreign table, a drop-down list of values will be available.
3815 You will see two lists of values, the first list containing the key
3816 and the display field, the second list containing the display field
3817 and the key. The reason for this is to be able to type the first
3818 letter of either the key or the display field.<br /><br />
3820 For 200 values or more, a distinct window will appear, to browse foreign
3821 key values and choose one.</p>
3825 automatically when entering Browse mode for a table?</a></h4>
3827 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3828 </p>
3832 Excel files, how can I enable that?</a></h4>
3834 <p> Current version does support direct export to Microsoft Excel and Word
3835 versions 2000 and newer. If you need export older versions, you can use
3837 which works out of the box or you can
3839 several problems, most important are limitation of cell content to 255
3840 chars and no support for charsets, so think carefully whether you want to
3841 enable this.</b>. For enabling this you need to set
3845 module Spreadsheet_Excel_Writer into php include path. The
3846 installation can be done by following command:</p>
3848 <pre>
3849 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3850 </pre>
3852 <p> First part of switches set we want to install beta version of that module
3853 (no stable version available yet) and then we tell pear we want to satisfy
3854 dependencies.</p>
3856 <p> If you are running in PHP safe mode, you will have to set
3859 modules are located, for example:</p>
3861 <pre>
3862 safe_mode_include_dir = /usr/local/lib/php
3863 </pre>
3867 <pre>
3868 cd phpMyAdmin
3869 mkdir tmp
3870 chmod o+rwx tmp
3871 </pre>
3875 what happens to my column comments stored in pmadb?</a></h4>
3877 <p> Automatic migration of a table's pmadb-style column comments to the native
3878 ones is done whenever you enter Structure page for this table.</p>
3885 <p> Our Bug Tracker is located at
3887 under the Bugs section.<br /><br />
3889 But please first discuss your bug with other users:<br />
3895 existing language, where do I start?</a></h4>
3897 <p> Always use the current SVN version of your language file.
3899 don't know how to get the SVN version, please ask one of the developers.
3900 <br />
3901 Please note that we try not to use HTML entities like &eacute; in
3902 the translations, since we define the right character set in the file.
3903 With HTML entities, the text on JavaScript messages would not
3904 display correctly.
3905 However there are some entities that need to be there, for quotes
3906 ,non-breakable spaces, ampersands, less than, greater than.<br />
3907 You can then put your translations, as a zip file to avoid losing special
3908 characters, on the sourceforge.net translation tracker.<br />
3909 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3910 list, because this is where we ask for translations of new messages.</p>
3914 phpMyAdmin. How should I proceed?</a></h4>
3920 </li>
3922 <li>generate patch with your changes:
3924 </li>
3927 tracker of the phpMyAdmin project</a>.
3928 </li>
3929 </ol>
3931 <p> Write access to the SVN tree is granted only to experienced developers who
3932 have already contributed something useful to phpMyAdmin.<br />
3938 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3940 <p> Please refer to
3941 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3942 </p>
3944 <!-- DEVELOPERS -->
3947 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3948 great features have been written by other people and you too can help to
3949 make phpMyAdmin a useful tool.</p>
3951 <p> If you're planning to contribute source, please read the following
3952 information:</p>
3958 it free from other code.<br />
3959 Commonly used functions should be added to
3962 <li>Obviously, you're free to use whatever coding style you want. But
3963 please try to keep your code as simple as possible: beginners are
3964 using phpMyAdmin as an example application.<br />
3965 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3966 compliant on one hand, they fit the
3969 coding standards</a>
3970 on the other hand. Please pay attention to this.</li>
3971 <li>Please try to keep up the file-naming conventions. Table-related stuff
3974 <li>Please don't use verbose strings in your code, instead add the string
3979 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3980 better debug and profile their code.<br />
3981 Please see the
3983 options for more information.<br />
3984 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3985 lost during its re-entry into Earth's atmosphere and in memory of the
3986 brave men and women who gave their lives for the people of Earth.</li>
3987 </ul>
3989 <!-- CREDITS -->
3992 <pre>
3993 phpMyAdmin - Credits
3994 ====================
3996 CREDITS, in chronological order
3997 -------------------------------
4000 * creator of the phpmyadmin project
4004 * multi-language version
4005 * various fixes and improvements
4007 * current project maintainer
4010 * started SourceForge phpMyAdmin project in March 2001
4011 * sync'ed different existing CVS trees with new features and bugfixes
4012 * multi-language improvements, dynamic language selection
4013 * current project maintainer
4014 * many bugfixes and improvements
4017 * rewrote and optimized javascript, DHTML and DOM stuff
4018 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4019 generate XHTML1.0 and CSS2 compliant codes
4020 * improved the language detection system
4021 * many bugfixes and improvements
4024 * database maintenance controls
4025 * table type code
4027 * DB-based configuration (Not completed)
4030 * many bugfixes and improvements
4033 * bookmarks feature
4034 * multiple dump feature
4035 * gzip dump feature
4036 * zip dump feature
4039 * various fixes
4040 * moderator of the phpMyAdmin former users forum at phpwizard.net
4046 * rewrote and fix dump code
4047 * bugfixes
4050 * rewrote dump code for PHP4
4051 * mySQL table statistics
4052 * bugfixes
4055 * main author of the version 2.1.0.1
4056 * bugfixes
4060 * abstract database interface (PMA_DBI) with MySQLi support
4061 * privileges administration
4063 * various features and fixes
4064 * German language file updates
4067 * automatic joins in QBE
4068 * links column in printview
4069 * Relation view
4072 * enhanced index creation/display feature
4073 * feature to use a different charset for HTML than for MySQL
4074 * improvements of export feature
4075 * various features and fixes
4076 * Czech language file updates
4079 (http://sf.net/projects/phpmysqlformgen/)
4080 * suggested the patch for multiple table printviews
4083 * built the patch for vertical display of table rows
4084 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4085 * Improvement of column/db comments
4086 * (MIME)-Transformations for columns
4087 * Use custom alias names for Databases in left frame
4088 * hierarchical/nested table display
4089 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4090 * new icon sets
4091 * vertical display of column properties page
4092 * some bugfixes, features, support, German language additions
4095 * japanese kanji encoding conversion feature
4098 * the Cookie authentication mode
4101 * table relation-links feature
4104 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4105 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4106 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4112 * phpMyAdmin logo (until June 2004)
4115 * blowfish library from the Horde project
4118 * mysqli support
4119 * many bugfixes and improvements
4122 * redesign for 2.6.0
4123 * phpMyAdmin sailboat logo (June 2004)
4126 * Representation at conferences
4129 * interface improvements
4130 * various bugfixes
4132 - Ivan A Kirillov
4133 * new relations Designer
4135 And also to the following people who have contributed minor changes,
4136 enhancements, bugfixes or support for a new language since version 2.1.0:
4138 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4139 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4140 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4141 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4143 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4144 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4145 Luís V., Martijn W. van der Lee,
4146 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4150 Original Credits of Version 2.1.0
4151 ---------------------------------
4153 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4154 to create a web-based interface to MySQL using PHP3. Although I have not
4155 used any of his source-code, there are some concepts I've borrowed from
4156 him. phpMyAdmin was created because Peter told me he wasn't going to
4157 further develop his (great) tool.
4158 Thanks go to
4160 code for the check when dropping a table or database. He also suggested
4161 that you should be able to specify the primary key on tbl_create.php3. To
4162 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4163 well as a bug-report. Plus many smaller improvements.
4165 were introduced in 1.3.0 (including quite significant ones like the
4166 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4167 bug-fixes and help.
4169 language-independent by outsourcing the strings to a separate file. He
4170 also contributed the French translation.
4172 tbl_select.php3, a feature to display only some fields from a table.
4174 functions in tbl_change.php3. He also added the
4177 servers and is a regular contributor for bug-fixes.
4179 features for 2.0.6.
4180 The following people have contributed minor changes, enhancements, bugfixes
4181 or support for a new language:
4182 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4183 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4184 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4185 G. Wieggers.
4187 And thanks to everyone else who sent me email with suggestions, bug-reports
4188 and or just some feedback.
4189 </pre>
4195 <ul>
4197 - the default name of Apache's directory-level configuration file.</li>
4201 - a software application that enables a user to display and interact with
4202 text, images, and other information typically located on a web page at a
4203 website on the World Wide Web.</li>
4205 - a free software/open source data compression algorithm and program
4206 developed by Julian Seward.</li>
4208 - an important World Wide Web technology that enables a client web browser
4209 to request data from a program executed on the Web server.</li>
4211 - a log or record of changes made to a project.</li>
4213 - a computer system that accesses a (remote) service on another computer
4214 by some kind of network.</li>
4216 - a set of data values of a particular simple type, one for each row of
4217 the table.</li>
4219 - a packet of information sent by a server to a World Wide Web browser
4220 and then sent back by the browser each time it accesses that server.</li>
4222 - Comma-seperated values</li>
4225 - an organized collection of data.</li>
4228 - a PHP module that extends PHP with additional functionality.</li>
4230 - a list of commonly asked question and there answers.</li>
4232 - one part of divided data/columns.</li>
4234 - a field or group of fields in a database record that point to a key
4235 field or group of fields forming a key of another database record in some
4236 (usually different) table.</li>
4238 - the free PDF library</li>
4240 GD Graphics Library</a> - a library by Thomas Boutell and others for
4241 dynamically manipulating images.</li>
4244 - gzip is short for GNU zip, a GNU free software file compression
4245 program.</li>
4247 - any machine connected to a computer network, a node that has a hostname.</li>
4249 - the unique name by which a network attached device is known on a network.</li>
4251 (HyperText Transfer Protocol)</a>
4252 - the primary method used to transfer or convey information on the World
4253 Wide Web.</li>
4256 additional security measures.</li>
4257 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4258 - a set of Internet-based services for servers using Microsoft Windows.</li>
4260 - a feature that allows quick access to the rows in a table.</li>
4262 - a data-oriented protocol used by source and destination hosts for
4263 communicating data across a packet-switched internetwork.</li>
4265 - a unique number that devices use in order to identify and communicate
4266 with each other on a network utilizing the Internet Protocol standard.</li>
4268 (Internet Server Application Programming Interface)</a>
4269 - the API of Internet Information Services (IIS).</li>
4271 - a business or organization that offers users access to the Internet and related services.</li>
4273 - a most commonly used standard method of lossy compression for
4274 photographic images.</li>
4280 - line of personal computers is designed, developed, manufactured, and
4281 marketed by Apple Computer.</li>
4282 <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>
4283 - the operating system which is included with all currently shipping Apple
4284 Macintosh computers in the consumer and professional markets.</li>
4286 - a cryptographic library.</li>
4288 - the MCrypt PHP extension.</li>
4289 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4290 - an Internet Standard for the format of e-mail.</li>
4292 - some sort of extension for the Apache Webserver.</li>
4294 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4295 Management System (DBMS).</li>
4297 - the improved MySQL client PHP extension.</li>
4299 - the MySQL client PHP extension.</li>
4301 - open standard for office documents.</li>
4302 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4303 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4305 (Portable Document Format)</a>
4306 - a file format developed by Adobe Systems for representing two
4307 dimensional documents in a device independent and resolution independent
4308 format.</li>
4310 - the PHP Extension and Application Repository.</li>
4312 - the perl-compatible regular expression functions for PHP</li>
4314 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4315 programming language used mainly for developing server-side applications
4316 and dynamic web content, and more recently, a broader range of software
4317 applications.</li>
4319 - a connection through which data is sent and received.</li>
4321 - Request for Comments (RFC) documents are a series of memoranda
4322 encompassing new research, innovations, and methodologies applicable to
4323 Internet technologies.</li>
4327 - represents a single, implicitly structured data item in a table.</li>
4329 - a computer system that provides services to other computing
4330 systems over a network.</li>
4331 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4332 - handlers for different table types</li>
4334 - a form of inter-process communication.</li>
4336 Sockets Layer)</a>
4337 - a cryptographic protocol which provides secure communication on the Internet.</li>
4339 - Structured Query Language</li>
4341 - a set of data elements (cells) that is organized, defined and stored as
4342 horizontal rows and vertical columns where each item can be uniquely
4343 identified by a label or key or by it?s position in relation to other items.</li>
4346 - a type of archive file format: the Tape ARchive format.</li>
4348 - one of the core protocols of the Internet protocol suite.</li>
4352 - a sequence of characters, conforming to a standardized format, that is
4353 used for referring to resources, such as documents and images on the
4354 Internet, by their location.</li>
4356 - A computer (program) that is responsible for accepting HTTP requests
4357 from clients and serving them Web pages.</li>
4359 - a W3C-recommended general-purpose markup language for creating
4360 special-purpose markup languages, capable of describing many different
4361 kinds of data.</li>
4363 - a popular data compression and archival format.</li>
4365 - an open-source, cross-platform data compression library by Jean-loup
4366 Gailly and Mark Adler.</li>
4367 </ul>
4377 </body>
4378 </html>