| blob | 3941532f2f1c3c8cb061fe2cb2c330511c51f2ee |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 </li>
63 <li>You need GD2 support in PHP to display inline
65 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
198 provided for those who prefer a graphical installation. Creating a
200 still a quick way to get started and needed for some advanced features.
201 <ul><li>To manually create the file, simply use your text editor to
204 file) in the main (top-level) phpMyAdmin directory (the one
208 default value is okay for a particular setting, there is no
210 few directives to get going, a simple configuration may look
211 like this:
212 <pre>
213 <?php
214 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
216 $i=0;
217 $i++;
218 $cfg['Servers'][$i]['auth_type'] = 'cookie';
219 ?>
220 </pre>
221 Or, if you prefer to not be prompted every time you log in:
222 <pre>
223 <?php
225 $i=0;
226 $i++;
227 $cfg['Servers'][$i]['user'] = 'root';
228 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
229 ?>
230 </pre>
231 For a full explanation of possible configuration values, see the
237 directory. This is a security measure. On a Linux/Unix system you
238 can use the following commands:
239 <pre>
240 cd phpMyAdmin
241 mkdir config # create directory for saving
242 chmod o+rw config # give it world writable permissions
243 </pre>
244 And to edit an existing configuration, copy it over first:
245 <pre>
246 cp config.inc.php config/ # copy current configuration for editing
247 chmod o+w config/config.inc.php # give it world writable permissions
248 </pre>
249 On other platforms, simply create the folder and ensure that your
258 the webserver does not have the proper permissions you may see the
260 config/</tt> directory exists and has the proper permissions -
262 and upload (via FTP or some similar means) to the proper location.<br /><br />
264 Once the file has been saved, it must be moved out of the <tt>
265 config/</tt> directory and the permissions must be reset, again
266 as a security measure:
267 <pre>
268 mv config/config.inc.php . # move file to current directory
269 chmod o-rw config.inc.php # remove world read and write permissions
270 rm -rf config # remove not needed directory
271 </pre>
272 Now the file is ready to be used. You can choose to review or edit
273 the file with your favorite editor, if you prefer to set some
274 advanced options which the setup script does not provide.</li></ul></li>
275 <li>If you are using the
277 protect the phpMyAdmin installation directory because using
278 config does not require a user to
279 enter a password to access the phpMyAdmin installation. Use of an alternate
280 authentication method is recommended, for example with
288 in your browser. phpMyAdmin should now display a welcome screen
289 and your databases, or a login dialog if using
291 authentication mode.</li>
293 webserver configuration. For Apache you can use supplied .htaccess file
294 in that folder, for other webservers, you should configure this yourself.
295 Such configuration prevents from possible path exposure and cross side
296 scripting vulnerabilities that might happen to be found in that code.</li>
297 </ol>
301 <p> For a whole set of new features (bookmarks, comments,
304 transformation, etc.) you need to create a set of special tables. Those
305 tables can be located in your own database, or in a central database for a
306 multi-user installation (this database would then be accessed by the
307 controluser, so no other user should have rights to it).</p>
316 installation.</p>
321 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
322 that you may need special (administrator) privileges to create the database
323 and tables, and that the script may need some tuning, depending on the
324 database name.</p>
329 section</a>. You will also need to have a controluser with the proper rights
336 unpacked one. Configuration files from very old versions (2.3.0 or before) may
337 require some tweaking as some options have been changed or removed.
339 statement that you might find near the end of your configuration file.</p>
343 is version-specific.</p>
346 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
347 you should run the SQL script found in
354 where you want to give users access to their own database and don't want
355 them to play around with others.<br />
356 Nevertheless be aware that MS Internet Explorer seems to be really buggy
358 in this area!<br />
361 that your user/password pair are not in clear in the configuration file.
362 </li>
365 authentication modes are more secure: the MySQL login information does
366 not need to be set in the phpMyAdmin configuration file (except possibly
368 However, keep in mind that the password travels in plain text, unless
369 you are using the HTTPS protocol.<br />
370 In cookie mode, the password is stored, encrypted with the blowfish
371 algorithm, in a temporary cookie.</li>
374 your MySQL server is previous to 4.1.2, or is running with
384 file under the
386 $cfg['Servers'][$i]['controluser']</a></tt> and
391 only an example: use something else in your file!</b> Input these
392 statements from the phpMyAdmin SQL Query window or mysql command–line
393 client.<br />
395 if it's not the same as the MySQL server's one.
397 <pre>
398 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
399 GRANT SELECT (
400 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
401 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
402 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
403 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
404 Execute_priv, Repl_slave_priv, Repl_client_priv
405 ) ON mysql.user TO 'pma'@'localhost';
406 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
407 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
408 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
409 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
411 If you are using an old MySQL version (below 4.0.2), please replace
412 the first GRANT SELECT query by this one:
414 <pre>
415 GRANT SELECT (
416 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
417 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
418 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
419 ) ON mysql.user TO 'pma'@'localhost';</pre>
421 ... and if you want to use the many new relation and bookmark features:
423 <pre>
425 </pre>
429 Of course, the above queries only work if your MySQL version supports
433 on a set of particular databases. Normally you shouldn't give global
434 privileges to an ordinary user, unless you understand the impact of those
435 privileges (for example, you are creating a superuser).<br />
439 <pre>
440 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
441 </pre>
443 What the user may now do is controlled entirely by the MySQL user
444 management system.<br />
446 authentication mode, you don't need to fill the user/password fields
448 array.</li>
449 </ul>
454 method and allows you to log in as any valid MySQL user.</li>
455 <li>Is supported with most PHP configurations. For
468 mode.</li>
469 </ul>
473 <ul><li>You can use this method as a replacement for the
475 (for example, if you're running
477 <li>Obviously, the user must enable cookies in the browser, but this is
478 now a requirement for all authentication modes.</li>
479 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
480 with the same username.</li>
481 <li>If you want to log in to arbitrary server see
486 not required.</li>
487 </ul>
491 <ul><li>This mode is a convenient way of using credentials from another
492 application to authenticate to phpMyAdmin.</li>
493 <li>The other application has to store login information into
494 session data.</li>
496 section.</li>
497 </ul>
500 <ul><li>This mode is the less secure one because it requires you to fill the
502 $cfg['Servers'][$i]['user']</a> and
504 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
505 can read your config.inc.php can discover your username and password).
506 <br />
513 is an entry explaining how to protect your configuration file.</li>
514 <li>For additional security in this mode, you may wish to consider the Host
515 authentication
517 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
519 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
520 directives.</li>
521 <li>Unlike cookie and http, does not require a user to log in when first
522 loading the phpMyAdmin site. This is by design but could allow any
523 user to access your installation. Use of some restriction method is
525 HTTP-AUTH directive or disallowing incoming HTTP requests at
526 one’s router or firewall will suffice (both of which
527 are beyond the scope of this manual but easily searchable with Google).</li>
528 </ul>
530 <!-- CONFIGURATION -->
534 users:</span> PHP does not seem to like
538 before saving a script you have modified.</p>
543 section to create one. This file only needs to contain the parameters you want to
544 change from their corresponding default value in
547 <p> The parameters which relate to design (like colors) are placed in
550 your site specific code to be included on start and end of each page.</p>
554 (with full path) to your phpMyAdmin installation's directory.
557 some web servers are case–sensitive.
560 Starting with version 2.3.0, it is advisable to try leaving this
561 blank. In most cases phpMyAdmin automatically detects the proper
562 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
563 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
564 A good test is to browse a table, edit a row and save it. There should
565 be an error message if phpMyAdmin is having trouble auto–detecting
566 the correct value. If you get an error that this must be set or if
567 the autodetect code fails to detect your path, please post a bug
568 report on our bug tracker so we can improve the code.</dd>
572 with master / foreign – tables (see
574 <br />
575 If you tried to set this up and it does not work for you, have a look on
577 use it. You will find a link that will analyze why those features have
578 been disabled.<br />
579 If you do not want to use those features set this variable to
583 <dd>A warning is displayed on the main page if Suhosin is detected.
585 from appearing.</dd>
589 domain to call phpMyAdmin inside a frame, and is a potential security
590 hole allowing cross-frame scripting attacks.</dd>
594 algorithm to encrypt the password.<br />
596 passphrase of your choice. It will be used internally by the blowfish
597 algorithm: you won’t be prompted for this passphrase. The maximum
602 MySQL servers. Therefore, a
604 been added which contains the login information for the different servers.
605 The first
607 contains the hostname of the first server, the second
609 the hostname of the second server, etc. In
611 server definition, however you can put as many as you need in
613 have to define all settings, just those you need to change).</dd>
617 $i-th MySQL-server. E.g. localhost.</dd>
622 ignores this port number and connects with the socket, so if you want
623 to connect to a port different from the default port, use
626 </dd>
630 To determine the correct socket, check your MySQL configuration or, using the
632 Among the resulting information displayed will be the socket used.</dd>
635 <dd>Whether to enable SSL for connection to MySQL server.
636 </dd>
639 <dd>What type connection to use with the MySQL server. Your options are
641 is nearly guaranteed to be available on all MySQL servers, while
642 sockets are not supported on some platforms.<br /><br />
644 To use the socket mode, your MySQL server must be on the same machine
645 as the Web server.</dd>
648 <dd>What php MySQL extension to use for the connection. Valid options are:
649 <br /><br />
652 The classic MySQL extension. This is the recommended and default
653 method at this time.<br /><br />
656 The improved MySQL extension. This extension became available
657 with php 5.0.0 and is the recommended way to connect to a server
661 <dd>Whether to use a compressed protocol for the MySQL server connection
662 or not (experimental).<br />
668 </dt>
670 all relational features (see
672 and, for a MySQL server previous to 4.1.2 or running with
675 authentication mode).<br /><br />
678 cookie authentication modes (or 'config'
679 authentication mode since phpMyAdmin 2.2.1), you need to supply the
684 This account is used to check what databases the user will see at
685 login.<br />
689 In phpMyAdmin versions before 2.2.5, those were called
693 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
694 <dd>Whether config or cookie or
696 should be used for this server.
698 is the plain old way: username and password are stored in
700 <li>'cookie' authentication mode
702 2.2.3 allows you to log in as any valid MySQL user with the
703 help of cookies. Username and password are stored in
704 cookies during the session and password is deleted when it
705 ends. This can also allow you to log in in arbitrary server if
706 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
707 </li>
708 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
709 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
710 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
711 <li>'signon' authentication mode
713 as introduced in 2.10.0 allows you to log in from prepared PHP
714 session data. This is useful for implementing single signon
715 from another application. Sample way how to seed session is in
721 </ul>
724 for more information.
725 </dd>
729 </dt>
730 <dd>
731 When using auth_type = 'config', this is the user/password-pair
732 which phpMyAdmin will use to connect to the
733 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
734 cookie authentication is used and should be empty.</dd>
736 <span
738 </dt>
739 <dd>
740 Allow attempt to log in without password when a login with password
741 fails. This can be used together with http authentication, when
742 authentication is done some other way and phpMyAdmin gets user name
743 from auth and uses empty password for connecting to MySQL. Password
744 login is still tried first, but as fallback, no password method is
745 tried.</dd>
748 </dt>
749 <dd>
750 If set to a (an array of) database name(s), only this (these) database(s)
751 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
752 database(s) name(s) may contain MySQL wildcards characters
756 This setting is an efficient way to lower the server load since the
757 latter does not need to send MySQL requests to build the available
759 privileges rules of the MySQL database server</span>. If set, it just
760 means only these databases will be displayed but
762 <br /><br />
764 An example of using more that one database:
766 <br /><br />
768 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
769 databases in the left frame, so that you can individually arrange your databases.<br />
770 If you want to have certain databases at the top, but don't care about the others, you do not
771 need to specify all other databases. Use:
773 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
774 order.</dd>
777 </dt>
778 <dd>Regular expression for hiding some databases. This only hides them
779 from listing, but a user is still able to access them (using, for example,
780 the SQL query area). To limit access, use the MySQL privilege system.
781 <br /><br />
786 More information on regular expressions can be found in the
788 PCRE pattern syntax</a> portion of the PHP reference manual.
789 </dd>
792 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
793 this string will be displayed instead of the hostname in the pull-down
794 menu on the main page. This can be useful if you want to show only
795 certain databases on your system, for example. For HTTP auth, all
796 non-US-ASCII characters will be stripped.</dd>
800 </dt>
801 <dd>The name of the database containing the linked-tables infrastructure.
802 <br /><br />
805 section in this document to see the benefits of this infrastructure,
806 and for a quick way of creating this database and the needed tables.
807 <br /><br />
809 If you are the only user of this phpMyAdmin installation, you can
810 use your current database to store those special tables; in this
811 case, just put your current database name in
813 set this parameter to the name of your central database containing
814 the linked-tables infrastructure.</dd>
818 </dt>
820 useful for queries you often run.<br /><br />
822 To allow the usage of this functionality:
824 <li>enter the table name in
826 </ul>
827 </dd>
831 </dt>
833 which field is a key in another table (a foreign key). phpMyAdmin
834 currently uses this to
835 <ul><li>make clickable, when you browse the master table, the data values
836 that point to the foreign table;</li>
838 when browsing the master table, if you move the mouse to a column
839 containing a foreign key (use also the 'table_info' table);<br />
842 <li>in edit/insert mode, display a drop-down list of possible foreign
846 <li>display links on the table properties page, to check referential
847 integrity (display missing foreign keys) for each described key;
848 </li>
852 schema of your database (also uses the table_coords table).</li>
853 </ul>
855 The keys can be numeric or character.<br /><br />
857 To allow the usage of this functionality:
860 infrastructure</li>
861 <li>put the relation table name in
863 <li>now as normal user open phpMyAdmin and for each one of your
864 tables where you want to use this feature, click
866 </li>
867 </ul>
871 future development of the cross-db relations.
872 </dd>
876 </dt>
877 <dd>
878 Since release 2.3.0 you can describe, in a special 'table_info'
879 table, which field is to be displayed as a tool-tip when moving the
880 cursor over the corresponding key.<br />
881 This configuration variable will hold the name of this special
882 table. To allow the usage of this functionality:
884 <li>put the table name in
886 <li>then for each table where you want to use this feature,
888 to choose the field.</li>
889 </ul>
891 </dd>
895 </dt>
898 the relations between your tables. To do this it needs two tables
903 schema output).<br /><br />
907 To allow the usage of this functionality:
910 infrastructure</li>
911 <li>put the correct table names in
914 </ul>
917 </dd>
921 </dt>
923 Since release 2.3.0 you can store comments to describe each column for
925 <br /><br />
927 Starting with release 2.5.0, comments are consequently used on the table
928 property pages and table browse view, showing up as tool-tips above the
929 column name (properties page) or embedded within the header of table in
930 browse view. They can also be shown in a table dump. Please see the
931 relevant configuration directives later on.<br /><br />
933 Also new in release 2.5.0 is a MIME-transformation system which is also
935 Transformations</a> for further information. To use the
936 MIME-transformation system, your column_info table has to have the three
937 new fields 'mimetype', 'transformation', 'transformation_options'.
938 <br /><br />
940 To allow the usage of this functionality:
942 infrastructure</li>
943 <li>put the table name in
947 <pre>
948 ALTER TABLE `pma_column_comments`
949 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
950 ADD `transformation` VARCHAR( 255 ) NOT NULL,
951 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
952 </pre>
955 renamed from<br />
958 </ul>
959 </dd>
963 </dt>
966 all queries you entered manually into the phpMyAdmin interface. If you
967 don't want to use a table-based history, you can use the JavaScript-based
968 history. Using that, all your history items are deleted when closing the
969 window.<br /><br />
971 Using
973 you can specify an amount of history items you want to have on hold. On
974 every login, this list gets cut to the maximum amount.<br /><br />
976 The query history is only available if JavaScript is enabled in your
977 browser.<br /><br />
979 To allow the usage of this functionality:
982 infrastructure</li>
984 </li>
985 </ul>
986 </dd>
990 </dt>
992 to visually manage the relations.
993 <br /><br />
995 To allow the usage of this functionality:
998 infrastructure</li>
1000 </li>
1001 </ul>
1002 </dd>
1005 </dt>
1007 column_info table got enhanced with three new fields. If the above variable
1009 latest table structure available. If not, it will emit a warning to the
1010 superuser.<br /><br />
1012 You can disable this checking behavior by setting the variable to false,
1013 which should offer a performance increase.<br /><br />
1015 Recommended to set to FALSE, when you are sure, your table structure is
1016 up to date.</dd>
1018 boolean</dt>
1019 <dd>Whether to allow root access. This is just simplification of rules below.
1020 </dd>
1023 </dt>
1025 authentication is disabled.<br /><br />
1028 all deny rules followed by allow rules. Access is allowed by default. Any
1029 client which does not match a Deny command or does match an Allow command
1030 will be allowed access to the server. <br /><br />
1033 applies all allow rules followed by deny rules. Access is denied by
1034 default. Any client which does not match an Allow directive or does
1035 match a Deny directive will be denied access to the server.<br /><br />
1037 If your rule order is set to 'explicit', the authentication is
1038 performed in a similar fashion to rule order 'deny,allow', with the
1042 and was available in Apache by specifying allow and deny rules without
1043 setting any order.<br /><br />
1045 Please also see <a
1047 address behind proxies.
1048 </dd>
1050 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1051 </dt>
1052 <dd>The general format for the rules is as such:
1054 <pre>
1056 </pre>
1061 well (please note that those containing SERVER_ADDRESS might not be
1062 available on all webservers):
1063 <pre>
1069 </pre>
1071 Having an empty rule list is equivalent to either using
1077 following work:<br />
1079 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1080 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1081 But the following does not work:<br />
1084 </dd>
1085 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1086 <dd>Name of session which will be used for signon authentication method.
1087 </dd>
1089 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1090 </dd>
1092 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1093 </dd>
1096 <dd>If you have more than one server configured, you can set
1098 that server when phpMyAdmin is started, or set it to 0 to be given a
1099 list of servers without logging in.<br />
1101 MUST be set to that server.</dd>
1104 <dd>The maximum number of database names to be displayed in the
1105 navigation frame and the database list.</dd>
1108 <dd>The maximum number of table names to be displayed in the
1109 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1110 when in Light mode.</dd>
1113 <dd>The maximum number of characters when a SQL query is displayed. The
1114 default limit of 1000 should be correct to avoid the display of tons
1115 of hexadecimal codes that represent BLOBs, but some users have real
1116 SQL queries that are longer than 1000 characters. Also, if a query's
1117 length exceeds this limit, this query is not saved in the history.</dd>
1120 <dd>Defines whether to use GZip output buffering for increased
1122 Set to true/false for enabling/disabling. When set to 'auto' (string),
1123 phpMyAdmin tries to enable output buffering and will automatically disable
1124 it if your browser has some problems with buffering. IE6 with a certain patch
1125 is known to cause data corruption when having enabled buffering.</dd>
1128 <dd>Whether persistent connections should be used or not (mysql_connect or
1129 mysql_pconnect).</dd>
1135 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1136 to zero, no time limit is imposed.<br />
1137 This setting is used while importing/exporting dump files but has no
1138 effect when PHP is running in safe mode.</dd>
1141 <dd>Set the number of bytes a script is allowed to allocate. If number set
1142 to zero, no limit is imposed.<br />
1143 This setting is used while importing/exporting dump files but has no
1144 effect when PHP is running in safe mode.<br />
1148 <dd>Mark used tables and make it possible to show databases with locked
1153 generated by phpMyAdmin should be displayed or not.</dd>
1156 <dd>Defines whether normal users (non-administrator) are allowed to
1157 delete their own database or not. If set as FALSE, the link "Drop
1159 mydatabase" will be rejected. Quite practical for
1161 customers.<br />
1162 Please note that this limitation of SQL queries is not as strict as
1163 when using MySQL privileges. This is due to nature of SQL queries
1164 which might be quite complicated. So this choice should be viewed as
1165 help to avoid accidental dropping rather than strict privilege
1166 limitation.</dd>
1170 displayed when you're about to lose data.</dd>
1173 <dd>Define whether the previous login should be recalled or not in cookie
1174 authentication mode.</dd>
1181 means that it will be kept for existing session. This is recommended
1182 for not trusted environments.</dd>
1185 <dd>If enabled (default), logout deletes cookies for all servers,
1186 otherwise only for current one. Setting this to false makes it easy to
1187 forget to log out from other server, when you are using more of
1188 them.</dd>
1194 <dd>Define whether phpMyAdmin will continue executing a multi-query
1195 statement if one of the queries fails. Default is to abort execution.</dd>
1198 <dd>Define whether phpMyAdmin will output the results of each query of a
1199 multi-query statement embedded into the
1204 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1205 <br /><br />
1208 MySQL servers behind the firewall where your
1210 </dd>
1213 <dd>Defines whether to use a select-based menu and display only the current
1214 tables in the left frame (smaller page). Only in Non-Lightmode you can
1215 use the feature to display nested folders using
1217 </dd>
1220 <dd>In light mode, defines whether to display the names of databases (in the
1221 selector) using a tree, see also
1223 </dd>
1226 <dd>The string used to separate the parts of the database name when showing
1227 them in a tree.</dd>
1230 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1231 This means if you have tables like 'first__second__third' this will be
1233 If set to FALSE or empty, the feature is disabled. NOTE: You should
1234 not use this separator at the beginning or end of a
1235 table name or multiple times after another without any other
1236 characters in between.</dd>
1239 <dd>Defines how many sublevels should be displayed when splitting
1240 up tables by the above separator.</dd>
1243 <dd>Defines whether to display table comment as tool-tip in left frame or
1244 not.</dd>
1247 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1248 comment and the real name. That means that if you have a table called
1249 'user0001' and add the comment 'MyName' on it, you will see the name
1250 'MyName' used consequently in the left frame and the tool-tip shows
1251 the real name of the DB.</dd>
1254 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1256 When setting this to 'nested', the Alias of the Tablename is only used
1257 to split/nest the tables according to the
1259 directive. So only the folder is called like the Alias, the tablename itself
1260 stays the real tablename.</dd>
1263 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1266 <dd>Enter URL where logo in the navigation frame will point to.
1267 For use especially with self made theme which changes this.
1276 <dd>Defines whether or not to display a server choice at the top of the left frame.
1277 Defaults to FALSE.</dd>
1279 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1280 Defaults to FALSE (drop-down).</dd>
1282 <dd>Defines whether to display database choice in light navigation frame as links
1283 instead of in a drop-down. Defaults to 'auto' - on main page list is
1284 shown, when database is selected, only drop down is displayed.</dd>
1286 <dd>Defines whether or not to display space usage and statistics about databases
1287 and tables.<br />
1288 Note that statistics requires at least MySQL 3.23.3 and that, at this
1289 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1292 <dd>Defines whether to display detailed server information on main page.
1293 You can additionally hide more information by using
1295 </dd>
1300 </dt>
1303 not at the starting main (right) frame. This setting
1304 does not check MySQL commands entered directly.<br /><br />
1306 Please note that to block the usage of phpinfo() in scripts, you
1313 hard coded password value in the configuration file, end users can't
1314 be allowed to change their passwords.</dd>
1317 <dd>Defines whether to suggest a database name on the
1322 content.</dd>
1325 <dd>Defines whether navigation bar buttons and the right panel top menu
1326 contain text or symbols only. A value of TRUE displays icons, FALSE
1327 displays text and 'both' displays both icons and text.</dd>
1330 <dd>Defines whether a user should be displayed a
1334 <dd>Number of rows displayed when browsing a result set. If the result set
1341 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1345 from editing when browsing a table's content. Valid values are:
1350 </ul>
1351 </dd>
1354 <dd>Defines whether or not MySQL functions fields should be initially
1355 displayed in edit/insert mode. Since version 2.10, the user can
1356 toggle this setting from the interface.
1357 </dd>
1360 <dd>Defines which type of editing controls should be used for CHAR and
1361 VARCHAR fields. Possible values are:
1362 <ul><li>input - this allows to limit size of text to size of field in
1363 MySQL, but has problems with newlines in fields</li>
1364 <li>textarea - no problems with newlines in fields, but also no
1365 length limitations</li>
1366 </ul>
1367 Default is old behavior so input.</dd>
1373 <dd>If there are fewer items than this in the set of foreign keys, then a
1374 drop-down box of foreign keys is presented, in the style described by the
1376 setting.</dd>
1379 <dd>For the foreign key drop-down fields, there are several methods of
1380 display, offering both the key and value data. The contents of the
1381 array should be one or both of the following strings:
1387 </dt>
1388 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1389 creating a dump file</dd>
1392 </dt>
1393 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1394 compressed exports. This doesn't affect smaller dumps and allows users to
1395 create larger dumps that won't otherwise fit in memory due to php
1396 memory limit. Produced files contain more GZip/BZip2 headers, but all
1397 normal programs handle this correctly.</dd>
1401 mainframe.</dd>
1405 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1410 <dd>How many columns will be utilized to display the tables on the
1411 database property view? Default is 1 column. When setting this to a
1412 value larger than 1, the type of the database will be omitted for more
1413 display space.</dd>
1417 <dd>Defines the tab displayed by default on server view. Possible
1424 <dd>Defines the tab displayed by default on database view. Possible
1429 <dd>Defines the tab displayed by default on table view. Possible
1436 points to the MySQL documentation (type depends
1437 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1438 generated.<br />
1440 for more information about MySQL manuals and their types.</dd>
1443 <dd>Type of MySQL documentation:
1449 </ul>
1450 </dd>
1453 <dd>Defines the default language to use, if not browser-defined or
1454 user-defined.<br />
1456 this setting.</dd>
1459 <dd>Defines the default connection collation to use, if not
1460 user-defined.<br />
1465 <dd>Force: always use this language (must be defined in the
1469 <dd>Limit list of available languages to those matching the given regular
1470 expression. For example if you want only Czech and English, you should
1474 <dd>Default character set to use for recoding of MySQL queries. This must be
1475 enabled and it's described by
1477 option.<br />
1478 You can give here any character set which is in
1480 array and this is just default choice, user can select any of them.</dd>
1483 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1484 support (compiled in or module) in PHP to allow MySQL queries recoding
1485 and used language file must have it enabled (by default only these
1486 which are in Unicode, just to avoid losing some characters).<br /><br />
1489 in the Export page, to choose the character set when exporting a file.
1490 </dd>
1493 <dd>You can select here which functions will be used for character set
1494 conversion. Possible values are:
1495 <ul><li>auto - automatically use available one (first is tested
1496 iconv, then recode)</li>
1499 </ul>
1500 Default is auto.</dd>
1503 <dd>Specify some parameters for iconv used in charset conversion. See
1506 used, so that invalid characters will be transliterated.</dd>
1509 <dd>Available character sets for MySQL conversion. You can add your own (any of
1510 supported by recode/iconv) or remove these which you don't use.
1511 Character sets will be shown in same order as here listed, so if you
1512 frequently use some of these move them to the top.</dd>
1517 default empty, you need to fill in some trusted proxy servers if you
1518 want to use rules for IP addresses behind proxy.<br /><br />
1520 The following example specifies that phpMyAdmin should trust a
1522 <pre>
1523 $cfg['TrustedProxies'] =
1525 </pre>
1526 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1527 client's IP address as usual.
1528 </dd>
1532 MIME transformations.<br />
1533 Possible values are:
1534 <ul><li>auto - automatically detect, this is a bit expensive
1536 according to your server real possibilities</li>
1539 </ul>
1540 Default is auto.
1541 </dd>
1545 </dd>
1547 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1548 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1549 </dt>
1550 <dd>The background styles used for both the frames.
1553 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1555 <dd>The style used for the pointer in the navi frame.
1559 <dd>The color used for the database name in the navi frame.
1568 </dd>
1572 <dd>The style used for table headers. See
1577 </dd>
1581 </dd>
1583 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1585 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1587 </dt>
1589 The former feature highlights the row over which your mouse is passing
1590 and the latter lets you visually mark/unmark rows by clicking on
1591 them.<br />
1596 <dd>You put here a valid CSS font family value, for example
1601 <dd>You put here a valid CSS font family value, for example
1615 </dt>
1617 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1619 The Char* values are used for CHAR and VARCHAR editing (if configured
1623 </dt>
1627 </dt>
1628 <dd>Defines if the whole textarea of the query box will be selected on
1629 click.</dd>
1632 </dt>
1633 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1634 editing.</dd>
1637 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1638 Can be turned off by a toggle button on the browse page.</dd>
1642 </dt>
1643 <dd>Defines the place where modify and delete links would be put when
1644 tables contents are displayed (you may have them displayed both at the
1645 left and at the right).
1651 </dt>
1653 Define which one is displayed by default. The first mode displays each
1654 row on a horizontal line, the second rotates the headers by 90
1655 degrees, so you can use descriptive headers even though fields only
1656 contain small values and still print them out. The vertical mode sorts
1657 each row on a vertical lineup.<br /><br />
1659 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1660 the rotation of the header for horizontalflipped is done via CSS. If
1661 set to 'fake' PHP does the transformation for you, but of course this
1662 does not look as good as CSS.</dd>
1666 string or integer</dt>
1667 <dd>When editing/creating new columns in a table all fields normally get
1668 lined up one field a line. (default: 'horizontal'). If you set this to
1669 'vertical' you can have each field lined up vertically beneath each
1670 other. You can save up a lot of place on the horizontal direction and
1671 no longer have to scroll. If you set this to integer, editing of fewer
1672 columns will appear in 'vertical' mode, while editing of more fields
1673 still in 'horizontal' mode. This way you can still effectively edit
1674 large number of fields, while having full view on few of them.</dd>
1678 </dt>
1680 display of column comments in Browse or Property display. In browse
1681 mode, the comments are shown inside the header. In property mode,
1682 comments are displayed using a CSS-formatted dashed-line below the
1683 name of the field. The comment is shown as a tool-tip for that field.
1684 </dd>
1696 <dd>Whether to display a link to validate a query in any SQL Query box.
1703 <dd>
1704 The name of the directory where
1706 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1707 are available under a drop-down box when you click the database or
1708 table name, then the Import tab.
1709 <br /><br />
1711 If you want different directory for each user, %u will be replaced
1712 with username.<br /><br />
1716 compressed formats is enabled).<br /><br />
1718 This feature is useful when your file is too big to be uploaded via
1720 uploads are disabled in PHP.<br /><br />
1722 Please note that if PHP is running in safe mode, this directory must
1723 be owned by the same user as the owner of the phpMyAdmin scripts.
1724 <br /><br />
1728 alternatives.
1729 </dd>
1732 <dd>
1733 The name of the directory where dumps can be saved.<br /><br />
1735 If you want different directory for each user, %u will be replaced
1736 with username.<br /><br />
1738 Please note that the directory must exist and has to be writable
1739 for the user running the webserver.<br /><br />
1741 Please note that if PHP is running in safe mode, this directory must
1742 be owned by the same user as the owner of the phpMyAdmin scripts.
1743 </dd>
1746 <dd>
1747 The name of the directory where temporary files can be stored.
1748 <br /><br />
1750 This is needed for native MS Excel export, see
1756 <br /><br />
1758 If the directory where phpMyAdmin is installed is subject to an
1760 temporary directory in some directory accessible by the web
1761 server. However for security reasons, this directory should be outside
1762 the tree published by webserver. If you cannot avoid having this
1763 directory published by webserver, place at least an empty
1765 possible.
1766 <br /><br />
1768 This directory should have as strict permissions as possible as the only
1769 user required to access this directory is the one who runs the
1770 webserver. If you have root privileges, simply make this user owner of
1771 this directory and make it accessible only by it:
1772 <br /><br />
1774 <pre>
1775 chown www-data:www-data tmp
1776 chmod 700 tmp
1777 </pre>
1779 If you cannot change owner of the directory, you can achieve a similar
1782 <pre>
1783 chmod 700 tmp
1784 setfacl -m "g:www-data:rwx" tmp
1785 setfacl -d -m "g:www-data:rwx" tmp
1786 </pre>
1788 If neither of above works for you, you can still make the directory
1790 system reading and writing data in this directory.
1791 </dd>
1794 <dd>
1795 In this array are defined default parameters for export, names of
1796 items are similar to texts seen on export page, so you can easily
1797 identify what they mean.
1798 </dd>
1801 <dd>
1802 In this array are defined default parameters for import, names of
1803 items are similar to texts seen on import page, so you can easily
1804 identify what they mean.
1805 </dd>
1808 <dd>
1809 Repeat the headers every X cells, or 0 to deactivate.
1810 </dd>
1818 </dt>
1819 <dd>
1820 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1821 or icon is always displayed on the left panel. If JavaScript is enabled in
1822 your browser, a click on this opens a distinct query window, which is
1823 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1824 changes to display a query box.<br /><br />
1826 The size of this query window can be customized with
1828 - both integers for the size in pixels. Note that normally, those
1830 theme you are using.<br /><br />
1834 opens the query window and puts the current query
1835 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1836 query in the right panel's query box.
1837 <br /><br />
1838 The usage of the JavaScript query window is recommended if you have a
1839 JavaScript enabled browser. Basic functions are used to exchange quite
1840 a few variables, so most 4th generation browsers should be capable to
1841 use that feature. It currently is only tested with Internet Explorer 6
1842 and Mozilla 1.x.
1843 <br /><br />
1845 to a table, which has to be created by you (see <a
1847 all your queries will be appended to the form, but only as long as
1848 your window is opened they remain saved.
1849 <br /><br />
1850 When using the JavaScript based query window, it will always get
1851 updated when you click on a new table/db to browse and will focus if
1852 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1853 the query window by checking the box "Do not overwrite this query from
1854 outside the window" below the query textarea. Then you can browse
1855 tables/databases in the background without losing the contents of the
1856 textarea, so this is especially useful when composing a query with
1857 tables you first have to look in. The checkbox will get automatically
1858 checked whenever you change the contents of the textarea. Please
1859 uncheck the button whenever you definitely want the query window to
1860 get updated even though you have made alterations.
1861 <br /><br />
1864 <br /><br />
1865 The query window also has a custom tabbed look to group the features.
1867 default tab to be used when opening the query window. It can be set to
1868 either 'sql', 'files', 'history' or 'full'.</dd>
1874 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1876 If the approximate row count as returned by
1879 count will be used.
1880 </dd>
1882 <dd>For VIEWs, since obtaining the exact count could have an
1883 impact on performance, this value is the maximum to be displayed, using
1885 any row counting.
1886 </dd>
1890 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1892 page. By clicking on the button 'toggle scratchboard' on the page
1893 where you edit x/y coordinates of those elements you can activate a
1894 scratchboard where all your elements are placed. By clicking on an
1895 element, you can move them around in the pre-defined area and the x/y
1896 coordinates will get updated dynamically. Likewise, when entering a
1897 new position directly into the input field, the new position in the
1898 scratchboard changes after your cursor leaves the input field.<br />
1899 You have to click on the 'OK'-button below the tables to save the new
1900 positions. If you want to place a new element, first add it to the
1901 table of elements and then you can drag the new element around.<br />
1902 By changing the paper size and the orientation you can change the size
1903 of the scratchboard as well. You can do so by just changing the
1904 dropdown field below, and the scratchboard will resize automatically,
1905 without interfering with the current placement of the elements.<br />
1906 If ever an element gets out of range you can either enlarge the paper
1907 size or click on the 'reset' button to place all elements below each
1908 other.<br />
1910 get this control to work. The basic Drag&Drop script functionality
1911 was kindly borrowed from www.youngpup.net and is underlying so
1912 specific license.</dd>
1915 <dd>Sorts database and table names according to natural order (for example,
1916 t1, t2, t10). Currently implemented in the left panel (Light mode)
1917 and in Database view, for the table list.</dd>
1923 <dd>Allows you to specify window's title bar. Following magic string can
1924 be used to get special values:
1925 <dl>
1931 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1940 </dl>
1941 </dd>
1951 </dd>
1954 <dd>If theme manager is active, use this as the path of the subdirectory
1955 containing all the themes.</dd>
1969 </dt>
1970 <dd>Default queries that will be displayed in query boxes when user didn't
1971 specify any. Use %d for database name, %t for table name and %f for a
1972 comma separated list of field names. Note that %t and %f are only
1976 <dd>
1977 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
1978 default we use HTML to format the query, but you can disable this by
1980 </dd>
1983 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1984 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1985 query inside a bracket is indented. By changing
1988 specifies the units of the indent amount that you specified. This is
1989 used via stylesheets.</dd>
1992 <dd>This array is used to define the colours for each type of element of
1993 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1995 If you specify an empty string for the color of a class, it is ignored
1996 in creating the stylesheet.
1997 You should not alter the class names, only the colour strings.<br />
2018 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2022 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2023 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2024 </ul>
2025 </dd>
2029 <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,
2030 as originally published on
2032 <br />
2033 For help in setting up your system to use the service, see the
2035 </dd>
2039 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2040 and any password, so we use those by default. Instead, if
2041 you have an account with them, you can put your login details
2042 here, and it will be used in place of the anonymous login.</dd>
2043 </dl>
2044 </dd>
2047 <dd><b>DEVELOPERS ONLY!</b></dd>
2050 <dd><b>DEVELOPERS ONLY!</b><br />
2051 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2052 the code.<br />
2053 For help in setting up your system to this, see the
2057 <dd><b>DEVELOPERS ONLY!</b><br />
2058 Enable profiling support for phpMyAdmin. This will append a chunk of data
2059 to the end of every page displayed in the main window with profiling
2060 statistics for that page.<br />
2061 You may need to increase the maximum execution time for this to
2062 complete successfully.<i>Profiling was removed from the code for
2063 version 2.9.0 due to licensing issues.</i></dd>
2065 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2066 <dd><b>DEVELOPERS ONLY!</b><br />
2067 When profiling data is displayed, this variable controls the threshold of
2068 display for any profiling data, based on the average time each time has
2069 taken. If it is over the threshold it is displayed, otherwise it is not
2070 displayed. This takes a value in milliseconds. In most cases you don't need
2071 to edit this.</dd>
2074 <dd>All possible types of a MySQL column. In most cases you don't need to
2075 edit this.</dd>
2078 <dd>Possible attributes for fields. In most cases you don't need to edit
2079 this.</dd>
2082 <dd>A list of functions MySQL supports. In most cases you don't need to
2083 edit this.</dd>
2086 <dd>Mapping of column types to meta types used for preferring displayed
2087 functions. In most cases you don't need to edit this.</dd>
2090 <dd>Functions preferred for column meta types as defined in
2091 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2092 to edit this.</dd>
2095 <dd>Functions selected by default when inserting/changing row, Functions
2096 are defined for meta types from
2098 <code>first_timestamp</code>, which is used for first timestamp column
2099 in table.</dd>
2102 <dd>Operators available for search operations on numeric and date fields.
2103 </dd>
2106 <dd>Operators available for search operations on character fields.
2107 Note that we put <code>LIKE</code> by default instead of
2108 <code>LIKE %...%</code>, to avoid unintended performance problems
2109 in case of huge tables.</dd>
2112 <dd>Operators available for search operations on enum fields.</dd>
2115 <dd>Additional operators available for search operations when the
2116 field can be null.</dd>
2118 </dl>
2120 <!-- TRANSFORMATIONS -->
2126 </ol>
2130 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2132 section</a> on how to do so.</p>
2134 <p> You can apply different transformations to the contents of each field. The
2135 transformation will take the content of each field and transform it with
2136 certain rules defined in the selected transformation.</p>
2138 <p> Say you have a field 'filename' which contains a filename. Normally you would
2139 see in phpMyAdmin only this filename. Using transformations you can transform
2140 that filename into a HTML link, so you can click inside of the phpMyAdmin
2141 structure on the field's link and will see the file displayed in a new browser
2142 window. Using transformation options you can also specify strings to
2143 append/prepend to a string or the format you want the output stored in.</p>
2145 <p> For a general overview of all available transformations and their options,
2146 you can consult your
2147 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2148 installation.</p>
2150 <p> For a tutorial on how to effectively use transformations, see our
2152 the official phpMyAdmin homepage.</p>
2156 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2157 clicking on the 'Structure' link for a table). There click on
2158 "Change" (or change icon) and there you will see three new fields at
2159 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2160 'Transformation options'.</p>
2162 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2163 that corresponds to the column's contents. Please note that
2164 transformations are inactive as long as no MIME-type is selected.</li>
2166 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2167 hopefully growing amount of pre-defined transformations. See below for information on
2168 how to build your own transformation.<br />
2170 There are global transformations and mimetype-bound transformations. Global transformations
2171 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2172 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2173 transformations which operate on the main mimetype (like 'image'), which will most likely
2174 take the subtype into regard, and those who only operate on a
2175 specific subtype (like 'image/jpeg').<br />
2177 You can use transformations on mimetypes for which the function was not defined for. There
2178 is no security check for you selected the right transformation, so take care of what the
2179 output will be like.</li>
2181 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2182 transform-function specific options here. Usually the transforms can operate with default
2183 options, but it is generally a good idea to look up the overview to see which options are
2184 necessary.<br />
2186 Much like the ENUM/SET-Fields, you have to split up several options using the format
2187 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2188 parsed as an array, leaving the first value the first element in the array, and so
2189 forth.<br />
2191 If you want to specify a MIME character set you can define it in the transformation_options.
2192 You have to put that outside of the pre-defined options of the specific mime-transform,
2194 for which you can specify 2 options and you want to append a character set, enter "'first
2195 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2197 </ul>
2201 <p> All mimetypes and their transformations are defined through single files in
2202 the directory 'libraries/transformations/'.</p>
2204 <p> They are stored in files to ease up customization and easy adding of new
2205 transformations.</p>
2207 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2208 always work. It makes no sense to apply a transformation to a mimetype, the
2209 transform-function doesn't know to handle.</p>
2211 <p> One can, however, use empty mime-types and global transformations which should work
2212 for many mimetypes. You can also use transforms on a different mimetype they where built
2213 for, but pay attention to option usage as well as what the transformation does to your
2214 field.</p>
2216 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2217 any other transform function and provides some basic functions.</p>
2219 <p> There are 5 possible file names:</p>
2221 <ol><li>A mimetype+subtype transform:<br /><br />
2223 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2225 Please not that mimetype and subtype are separated via '_', which shall
2226 not be contained in their names. The transform function/filename may
2227 contain only characters which cause no problems in the file system as
2228 well as the PHP function naming convention.<br /><br />
2230 The transform function will the be called
2231 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2233 <b>Example:</b><br /><br />
2235 <tt>text_html__formatted.inc.php</tt><br />
2236 <tt>PMA_transform_text_html__formatted()</tt></li>
2238 <li>A mimetype (w/o subtype) transform:<br /><br />
2240 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2242 Please note that there are no single '_' characters.
2243 The transform function/filename may contain only characters which cause
2244 no problems in the file system as well as the PHP function naming
2245 convention.<br /><br />
2247 The transform function will the be called
2248 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2250 <b>Example:</b><br /><br />
2252 <tt>text__formatted.inc.php</tt><br />
2253 <tt>PMA_transform_text__formatted()</tt></li>
2255 <li>A mimetype+subtype without specific transform function<br /><br />
2257 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2259 Please note that there are no '__' characters in the filename. Do not
2260 use special characters in the filename causing problems with the file
2261 system.<br /><br />
2263 No transformation function is defined in the file itself.<br /><br />
2265 <b>Example:</b><br /><br />
2267 <tt>text_plain.inc.php</tt><br />
2268 (No function)</li>
2270 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2272 <tt>[mimetype].inc.php</tt><br /><br />
2274 Please note that there are no '_' characters in the filename. Do not use
2275 special characters in the filename causing problems with the file system.
2276 <br /><br />
2278 No transformation function is defined in the file itself.<br /><br />
2280 <b>Example:</b><br /><br />
2282 <tt>text.inc.php</tt><br />
2283 (No function)</li>
2285 <li>A global transform function with no specific mimetype<br /><br />
2287 <tt>global__[transform].inc.php</tt><br /><br />
2289 The transform function will the be called
2290 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2292 <b>Example:</b><br /><br />
2294 <tt>global__formatted</tt><br />
2295 <tt>PMA_transform_global__formatted()</tt></li>
2296 </ol>
2298 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2299 transform function.</p>
2301 <p> All filenames containing no '__' in themselves are not shown as valid transform
2302 functions in the dropdown.</p>
2304 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2305 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2306 without a transform function. Also note the introduction of a function description in
2307 the language files. For each function a $strTransformation_[filename without .inc.php]
2308 has to exist.</p>
2310 <p> You can use the template generator to generate new functions and entries in the
2311 language file.</p>
2313 <p> To create a new transform function please see
2314 <tt>libraries/transformations/template_generator.sh</tt>.
2315 To create a new, empty mimetype please see
2316 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2318 <p> A transform function always gets passed three variables:</p>
2320 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2321 you want to transform.</li>
2322 <li><b>$options</b> - Contains any user-passed options to a transform function
2323 as an array.</li>
2324 <li><b>$meta</b> - Contains an object with field information to your column.
2325 The data is drawn from the output of the
2327 function. This means, all object properties described on the
2329 available in this variable and can be used to transform a field accordingly
2330 to unsigned/zerofill/not_null/... properties.<br />
2331 The $meta->mimetype variable contains the original MIME-type of the
2332 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2333 </ol>
2335 <!-- FAQ -->
2342 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2346 </ol>
2348 <p> Please have a look at our
2350 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2351 features and or interface.</p>
2357 action is required or phpMyAdmin sends a blank page or a page full of
2358 cryptic characters to my browser, what can I do?</a></h4>
2360 <p> There are some known PHP bugs with output buffering and compression.<br />
2362 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2363 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2364 configuration file.<br />
2365 Furthermore, we know about such problems connected to the release
2366 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2367 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2372 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2373 See also the
2375 entry about PHP bugs with output buffering.<br />
2376 If your server keeps crashing, please ask for help in the various Apache
2377 support groups.</p>
2381 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2382 script: I'm always displayed the login screen.</a></h4>
2384 <p> This is a known PHP bug (see this
2386 official PHP bug database. It means there is and won't be any phpMyAdmin
2387 fix against it because there is no way to code a fix.</p>
2393 application misbehaved by not returning a complete set of
2395 </h4>
2397 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2398 Have a look at the last message in this
2400 official PHP bug database.</p>
2405 and/or many error messages with the
2407 mode.</a></h4>
2409 <p> This is a known problem with the PHP
2411 filter: it's not so stable. Please use instead the cookie authentication mode.
2412 </p>
2417 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2418 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2419 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2420 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2421 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2426 work.</a></h4>
2428 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2429 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2430 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2431 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2432 We faced PHP crashes when trying to download a dump with MS Internet
2433 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2434 this case you should switch to the release version of PHP 4.2.0.</p>
2438 an error about safe mode being in effect.</a></h4>
2440 <p> Your uploaded file is saved by PHP in the "upload dir", as
2441 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2442 the system default is <i>/tmp</i>).<br />
2443 We recommend the following setup for Apache servers running in safe mode,
2444 to enable uploads of files while being reasonably secure:</p>
2446 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2447 <li>give ownership to the Apache server's user.group:
2448 <tt>chown apache.apache /tmp/php</tt></li>
2449 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2450 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2451 <li>restart Apache</li>
2452 </ul>
2456 general file uploads don't work on my system and uploaded files have a
2457 <tt>Content-Type:</tt> header in the first line.</a></h4>
2459 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2460 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2461 So the problem is that this package has a serious bug that was corrected
2462 ages ago in PHP (2001-01-28: see
2464 for more details). The problem is that the bugged package is still
2465 available though it was corrected (see
2467 for more details).<br />
2468 So please download
2469 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2470 and the problem should go away.<br />
2471 And that fixes the \r\n problem with file uploads!</p>
2475 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2476 I'm using the Apache server.</a></h4>
2478 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2479 your <i>httpd.conf</i>:</p>
2483 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2487 uploading a file from the query box.</a></h4>
2489 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2490 restrictions. However you need to create temporary directory and
2492 The uploaded files will be moved there, and after execution of your
2498 <p> The MySQL manual explains how to
2500 reset the permissions</a>.</p>
2505 execute a bookmark.</a></h4>
2507 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2508 cannot access the uploaded query.</p>
2513 submit a query from the convenient text area.</a></h4>
2515 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2516 and try to increase it.</p>
2520 </h4>
2522 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2523 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2524 names to align with current standards.</p>
2529 </h4>
2531 <p> Starting with version 2.7.0, the import engine has been re–written and these
2532 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2533 to take advantage of the new import features.</p>
2535 <p> The first things to check (or ask your host provider to check) are the
2536 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2537 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2538 All of these three settings limit the maximum size of data that can be
2539 submitted and handled by PHP. One user also said that post_max_size
2540 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2542 There exist several workarounds if your upload is too big or your
2543 hosting provider is unwilling to change the settings:</p>
2546 feature. This allows one to
2547 upload a file to the server via scp, ftp, or your favorite file transfer
2548 method. PhpMyAdmin is then able to import the files from the temporary
2550 section</a> of this document.</li>
2552 BigDump</a>) to split the files before uploading. We cannot support this
2553 or any third party applications, but are aware of users having success
2554 with it.</li>
2555 <li>If you have shell (command line) access, use MySQL to import the files
2556 directly. You can do this by issuing the "source" command from
2557 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2558 </ul>
2562 support?</a></h4>
2564 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2565 fully supported. Please note that the older your MySQL version is, the more
2566 limitations you will have to face.<br />
2567 phpMyAdmin may connect to your MySQL server using php's classic
2570 is available in php 5.0.<br />
2571 Either way, the developers of both extensions recommend to use the classic
2572 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2573 When compiling php, we strongly recommend that you manually link the MySQL
2574 extension of your choice to a MySQL client library of at least the same
2575 minor version since the one that is bundled with some php distributions is
2578 If your webserver is running on a windows system, you might want to try
2579 MySQL's
2581 instead of the MySQL / MySQLi extensions that are bundled with the official
2582 php Win32 builds.
2583 <br />
2584 MySQL 5.1 is not yet supported.</p>
2588 message, "Client does not support authentication protocol requested
2589 by server; consider upgrading MySQL client"</a></h5>
2591 <p> You tried to access MySQL with an old MySQL client library. The version of
2592 your MySQL client library can be checked in your phpinfo() output.
2593 In general, it should have at least the same minor version as your server
2597 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2598 changed the authentication hash and your PHP is trying to use the old method.
2600 with the proper client library to match your MySQL installation. Your
2601 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2602 More information (and several workarounds) are located in the
2604 </p>
2608 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2609 capital letter in its name it is changed to lowercase as it should. But
2610 if I try to DROP this table MySQL is unable to find the corresponding
2611 file.</a></h4>
2613 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2614 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2615 directive.</p>
2619 script seems not to know the font face I'm using!</a></h4>
2621 <p> The "FPDF" library we're using for this feature requires some
2622 special files to use font faces.<br />
2624 these files.</p>
2628 check PHP Configuration".</a></h4>
2630 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2631 "MySQL extension". This extension may be part of the PHP
2632 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2633 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2634 to load the extension but failed.<br /><br />
2636 Usually, the problem is solved by installing a software package called
2637 "PHP-MySQL" or something similar.</p>
2642 and I cannot log in using cookie auth.</a></h4>
2644 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2648 so I cannot upload.</a></h4>
2650 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2651 parameter is not set to "on".</p>
2655 a new table the table and field names are changed to lowercase!</a></h4>
2657 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2658 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2659 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2660 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2661 directory and add the following line to the group [mysqld]:</p>
2663 <pre>set-variable = lower_case_table_names=0</pre>
2665 <p> Next, save the file and restart the MySQL service. You can always check the
2666 value of this directive using the query</p>
2668 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2672 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2675 </p>
2679 and I get problems, such as undefined variables when I run a
2682 <p> A tip from Jose Fandos: put a comment on the following two lines
2683 in httpd.conf, like this:</p>
2685 <pre>
2686 # mod_gzip_item_include file \.php$
2688 </pre>
2690 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2691 PHP scripts. Of course you have to restart Apache.</p>
2696 I get the error "No input file specified" when trying to
2697 run phpMyAdmin.</a></h4>
2699 <p> This is a permission problem. Right-click on the phpmyadmin folder
2700 and choose properties. Under the tab Security, click on "Add"
2701 and select the user "IUSR_machine" from the list. Now set his
2702 permissions and it should work.</p>
2706 db_structure.php with plenty of tables).</a></h4>
2709 GZIP output buffering is enabled. If you turn off it (by
2711 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2712 PHP 5.0.0.</p>
2716 message 'Errorcode: 13'. What does this mean?</a></h4>
2718 <p> This can happen due to a MySQL bug when having database / table names with
2719 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2720 To fix this, turn off this directive, convert all database and table names
2721 to lower case and turn it on again. Alternatively, there's a bug-fix
2722 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2726 and the fields are duplicated.</a></h4>
2728 <p> It is possible to configure Apache in such a way that PHP has problems
2729 interpreting .php files.</p>
2731 <p> The problems occur when two different (and conflicting) set of directives
2732 are used:</p>
2734 <pre>
2735 SetOutputFilter PHP
2736 SetInputFilter PHP
2737 </pre>
2739 <p> and</p>
2741 <pre>AddType application/x-httpd-php .php</pre>
2743 <p> In the case we saw, one set of directives was in
2744 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2745 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2746 The recommended way is with <tt>AddType</tt>, so just comment out
2747 the first set of lines and restart Apache:</p>
2749 <pre>
2750 #SetOutputFilter PHP
2751 #SetInputFilter PHP
2752 </pre>
2757 <p> This problem is known to happen when the server is running Turck MMCache
2758 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2763 <p> Yes.<br />
2764 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2765 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2766 <tt>error_reporting</tt> settings.
2767 </p>
2770 <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>
2772 <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>
2775 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2776 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2777 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2778 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2779 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2780 enabled.) Click <tt>OK</tt>.</li>
2781 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2782 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2783 </ol>
2787 PHP 5.0.4 on 64-bit systems?</a></h4>
2789 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2790 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2796 http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script. For <tt>server</tt> you use the server number which refers to
2797 the order of the server paragraph in <tt>config.inc.php</tt>.
2798 Table and script parts are optional. If you want
2799 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2800 some configuration. Following lines apply only for <a
2802 that you have enabled some features within global configuration. You need
2803 <code>Options FollowSymLinks</code> and <code>AllowOverride
2804 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2805 you need mod_rewrite to be enabled. Then you just need to create following
2806 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2807 (don't forget to change directory name inside of it):</p>
2809 <pre>
2810 RewriteEngine On
2811 RewriteBase /path_to_phpMyAdmin
2812 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2813 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2814 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2815 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2816 </pre>
2819 <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>
2821 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2822 following rewrite rule:</p>
2824 <pre>
2825 RewriteEngine On
2826 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2827 </pre>
2831 </h4>
2832 <p>
2833 There can be many explanations to this and a look at your server's
2834 error log file might give a clue.
2835 </p>
2839 password encryption in cookie auth doesn't work.</a></h4>
2841 <p> If your cluster consist of different architectures, PHP code used for
2842 encryption/decryption won't work correct. This is caused by use of
2843 pack/unpack functions in code. Only solution is to use mcrypt extension
2844 which works fine in this case.</p>
2849 <p> Yes but the default configuration values of Suhosin are known to cause
2850 problems with some operations, for example editing a table with many
2851 columns and no primary key. Tuning information is available at
2853 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2854 although the parameter names have changed (<tt>suhosin</tt> instead
2856 <tt>SuhosinDisableWarning</tt> directive</a>.
2857 </p>
2863 headers already sent by ..." is displayed, what's the problem?</a></h4>
2865 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2866 (I.E. no blank lines, no spaces, no characters...) neither before the
2867 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2868 tag at the end. We also got a report from a user under IIS, that used
2869 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2870 contained an end-of-line character (hex 0A) at the end; removing this character
2871 cleared his errors.</p>
2876 <p> Either there is an error with your PHP setup or your username/password is
2877 wrong. Try to make a small script which uses mysql_connect and see if it
2878 works. If it doesn't, it may be you haven't even compiled MySQL support
2879 into PHP.</p>
2883 connect to local MySQL server through socket '/tmp/mysql.sock'
2884 (111) ..." is displayed. What can I do?</a></h4>
2886 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2888 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2889 In your <i>php.ini</i> you will find a line</p>
2891 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2893 <p> change it to</p>
2895 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2897 <p> Then restart apache and it will work.</p>
2899 <p> Here is a fix suggested by Brad Ummer:</p>
2901 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2902 To do this, telnet to your server and go to the MySQL bin directory. In
2903 this directory there should be a file named <i>mysqladmin</i>. Type
2904 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2905 info about your MySQL server, including the socket
2906 (<i>/tmp/mysql.sock</i>, for example).</li>
2907 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2908 phpMyAdmin, you need to complete the socket information in the
2909 <i>config.inc.php</i>.<br />
2910 For example:
2912 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2913 <br /><br />
2915 Please also make sure that the permissions of this file allow to be readable
2916 by your webserver (i.e. '0755').</li>
2917 </ul>
2919 <p> Have also a look at the
2921 corresponding section of the MySQL documentation</a>.</p>
2925 what can I do?</a></h4>
2928 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2929 sometime.<br />
2930 Also have a look at your PHP version number: if it contains "4.0b..."
2931 it means you're running a beta version of PHP. That's not a so good idea,
2932 please upgrade to a plain revision.</p>
2936 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2937 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2939 <p> Check the value you set for the
2941 directive in the phpMyAdmin configuration file.</p>
2945 password: YES)"-error when trying to access a MySQL-Server on a
2946 host which is port-forwarded for my localhost.</a></h4>
2948 <p> When you are using a port on your localhost, which you redirect via
2949 port-forwarding to another host, MySQL is not resolving the localhost
2950 as expected.<br />
2951 Erik Wasser explains: The solution is: if your host is "localhost"
2952 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2953 connection for speeding up things. And that doesn't work in this configuration
2954 with port forwarding.<br />
2960 <p> Themes are configured with
2964 <br />
2966 should not delete the directory "original" or its underlying
2967 structure, because this is the system theme used by phpMyAdmin.
2968 "original" contains all images and styles, for backwards
2969 compatibility and for all themes that would not include images or css-files.
2970 <br /><br />
2973 is enabled, you can select your favorite theme on the main page. Your
2974 selected theme will be stored in a cookie.<br /><br /></p>
2976 <p> To create a theme:</p>
2978 <ul><li>make a new subdirectory (for example "your_theme_name") under
2980 (by default <tt>themes</tt>)</li>
2981 <li>copy the files and directories from "original" to
2982 "your_theme_name"</li>
2983 <li>edit the css-files in "your_theme_name/css"</li>
2984 <li>put your new images in "your_theme_name/img"</li>
2985 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2986 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2987 contain your chosen theme name, that will be visible in user interface</li>
2988 <li>make a new screenshot of your theme and save it under
2989 "your_theme_name/screen.png"</li>
2990 </ul>
2992 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2993 theme verbose name, theme generation and theme version. These versions and
2994 generations are enumerated from 1 and do not have any direct dependence on
2995 phpMyAdmin version. Themes within same generation should be backwards
2996 compatible - theme with version 2 should work in phpMyAdmin requiring
2997 version 1. Themes with different generation are incompatible.</p>
2999 <p> If you do not want to use your own symbols and buttons, remove the
3000 directory "img" in "your_theme_name". phpMyAdmin will
3001 use the default icons and buttons (from the system-theme "original").
3002 </p>
3006 what can I do?</a></h4>
3008 <p> Here are a few points to check:</p>
3010 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3012 directive empty. See also
3014 </li>
3015 <li>Maybe you have a broken PHP installation or you need to upgrade
3016 your Zend Optimizer. See
3018 http://bugs.php.net/bug.php?id=31134</a>.
3019 </li>
3020 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3021 set to the default (200) or another low value, you could get this
3022 error if your table has a high number of columns. Adjust this setting
3023 accordingly. (Thanks to Klaus Dorninger for the hint).
3024 </li>
3025 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3026 of ";" will cause this error. Replace it with "&;".
3027 </li>
3029 you might want to increase
3031 </li>
3032 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3033 </li>
3034 </ul>
3041 who logged out can not log in again in with the same nick.</a></h4>
3043 <p> This is related to the authentication mechanism (protocol) used by
3044 phpMyAdmin. To bypass this problem: just close all the opened
3045 browser windows and then go back to phpMyAdmin. You should be able to
3046 log in again.</p>
3050 limit error or a time limit error.</a></h4>
3052 <p> Compressed dumps are built in memory and because of this are limited to
3053 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3054 using
3056 (enabled by default). Zip exports can not be handled this way, so if you need
3057 Zip files for larger dump, you have to use another way.</p>
3061 or alter a table.</a></h4>
3063 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3067 bundled with the MySQL server distribution.</a></h4>
3069 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3071 <pre>
3072 -- MySQL dump 8.22
3073 --
3074 -- Host: localhost Database: database
3075 ---------------------------------------------------------
3076 -- Server version 3.23.54
3077 </pre>
3079 <p> The invalid part of the code is the horizontal line made of dashes that
3080 appears once in every dump created with mysqldump. If you want to run your
3081 dump you have to turn it into valid MySQL. This means, you have to add a
3082 whitespace after the first two dashes of the line or add a # before it:
3083 <br />
3084 <code>
3085 -- -------------------------------------------------------<br />
3086 </code>
3087 or<br />
3088 <code>
3089 #---------------------------------------------------------
3090 </code>
3091 </p>
3098 <p> Please note that you should not use the separating string multiple times
3099 without any characters between them, or at the beginning/end of your table
3100 name. If you have to, think about using another TableSeparator or disabling
3101 that feature</p>
3106 <p> In Relation view, being able to choose a table in another database,
3107 or having more than one index field in the foreign key.<br /><br/>
3108 In Query-by-example (Query), automatic generation of the query
3109 LEFT JOIN from the foreign table.<br /><br/>
3110 </p>
3114 I get series of errors like "Warning: unable to parse url". How
3115 can this be fixed?</a></h4>
3116 <p>
3117 Your table neither have a primary key nor an unique one, so we must use a
3118 long expression to identify this row. This causes problems to parse_url
3119 function. The workaround is to create a primary or unique key.
3120 <br />
3121 </p>
3125 a MIME-Transformation onto!</a></h4>
3127 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3128 nested forms can be put inside the table where phpMyAdmin displays the results.
3129 You can, however, use any form inside of a table if keep the parent
3130 form-container with the target to tbl_row_delete.php and just put your own
3131 input-elements inside. If you use a custom submit input field, the form will
3132 submit itself to the displaying page again, where you can validate the
3133 $HTTP_POST_VARS in a transformation.
3135 For a tutorial on how to effectively use transformations, see our
3137 on the official phpMyAdmin-homepage.</p>
3141 MySQL server</a></h4>
3143 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3146 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3147 the quote-character (") is interpreted as an identifier quote character and
3148 not as a string quote character, which makes many internal phpMyAdmin
3150 statements. There is no workaround to this behaviour. News to this item will
3151 be posted in Bug report
3152 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3153 </p>
3157 more that one column with the same value
3158 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3159 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3161 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3162 can use it for the Edit and Delete links.</p>
3167 <p> phpMyAdmin uses a quick method to get the row count, and this method
3168 only returns an approximate count in the case of InnoDB tables. See
3170 a way to modify those results, but
3171 this could have a serious impact on performance.</p>
3176 <p> The number of records in queries containing COUNT and GROUP BY is
3177 not correctly calculated. Also, sorting results of a query like
3182 containing an hyphen.
3183 </a></h4>
3184 <p>
3185 The tests I have made with current MySQL 4.1.11 API shows that the
3186 API does not accept this syntax for the USE command. Enclosing the
3187 db name with backquotes works. For further confusion, no backquotes
3188 are needed with command-line mysql.
3189 </p>
3192 <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>
3193 <p>
3194 This has been a known limitation of phpMyAdmin since the beginning and
3195 it's not likely to be solved in the future.
3196 </p>
3198 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3201 <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
3202 need to install it for each customer.
3203 </a></h4>
3204 <p>
3205 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3206 your users. The development of this feature was kindly sponsored by
3207 NetCologne GmbH.
3208 This requires a properly setup MySQL user management and phpMyAdmin
3209 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3211 </p>
3215 access.
3216 </a></h4>
3217 <p>
3218 This depends on your system.<br />
3219 If you're running a server which cannot be accessed by other people, it's
3220 sufficient to use the directory protection bundled with your webserver
3222 If other people have telnet access to your server, you should use
3223 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3224 <br /><br />
3225 Suggestions:
3226 </p>
3227 <ul>
3228 <li>
3230 </li>
3231 <li>
3232 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3233 is a user whose password is only known to you, and apache is the
3234 group under which Apache runs.
3235 </li>
3236 <li>
3237 You should use PHP safe mode, to protect from other users that try
3239 </li>
3240 </ul>
3245 </a></h4>
3246 <p>
3251 </p>
3254 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3255 authentication.
3256 </a></h4>
3260 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3261 and/or
3263 are wrong.</li>
3265 <li>You have already setup a security mechanism for the
3266 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3267 phpMyAdmin's authentication, so remove it.</li>
3268 </ul>
3275 and put the privileges you want. For example,
3277 would let a user create/manage his/her database(s).</p>
3282 <p> If you have existing rules from an old .htaccess file, you can take them
3285 be a major benefit here if your installation is suited to using it. Then
3286 you can just add those updated lines into the
3290 <p> If you want a pre-made sample, you can try this fragment. It stops the
3291 'root' user from logging in from any networks other than the private
3294 <pre>
3295 //block root from logging in except from the private networks
3296 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3297 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3298 'deny root from all',
3299 'allow root from localhost',
3303 );
3304 </pre>
3309 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3310 different than the one set in your
3312 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3313 while a domain name is defined in the config file.</p>
3318 <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>
3324 when trying to create a table with more than 14 fields.
3325 </a></h4>
3326 <p>
3327 We could reproduce this problem only under Win98/98SE. Testing under
3328 WinNT4 or Win2K, we could easily create more than 60 fields.
3329 <br />
3330 A workaround is to create a smaller number of fields, then come back to
3331 your table properties and add the other fields.
3332 </p>
3336 <p>
3337 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3338 with each script/website that use forms.<br />
3339 Upgrade or downgrade your Xitami server.
3340 </p>
3343 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3344 <p>
3345 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3346 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3347 don't seem to work.<br />
3349 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3350 the user's temporary directory, so they must be moved before closing
3351 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3354 </p>
3358 Explorer never stores the cookies.
3359 </a></h4>
3360 <p>
3361 MS Internet Explorer seems to be really buggy about cookies, at least till
3363 in this area!
3364 <br />
3365 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3366 work!
3367 </p>
3371 rows.
3372 </a></h4>
3373 <p>
3375 </p>
3378 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3379 when trying to modify a row in a table with many fields, or with a text field
3380 </a></h4>
3381 <p>
3382 Your table neither have a primary key nor an unique one, so we must use a
3383 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
3384 those browsers, and this not happen in Netscape, for example. The
3385 workaround is to create a primary or unique key, or use another browser.
3386 <br />
3387 </p>
3391 page.
3392 </a></h4>
3393 <p>
3394 Some browsers support right-clicking into the frame you want to refresh,
3395 just do this in the right frame.<br />
3396 </p>
3400 query box.
3401 </a></h4>
3402 <p>
3403 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3404 Mozilla versions.<br />
3405 </p>
3409 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3410 </a></h4>
3411 <p>
3412 This is a Mozilla bug (see bug #26882 at
3414 </p>
3419 </a></h4>
3420 <p>
3421 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3422 data in octet-stream mode. Since we can't detect the specific Netscape
3423 version, we cannot workaround this bug.
3424 </p>
3428 wrong.</a></h4>
3430 <p> Please ensure that you have set your browser's character set to the one of the
3431 language file you have selected on phpMyAdmin's start page.
3432 Alternatively, you can try the auto detection mode that is supported by the
3433 recent versions of the most browsers.</p>
3436 <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
3439 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3440 Netscape and Mozilla do not have this problem.</p>
3443 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3444 I cannot manage two servers: I log in to the first one, then the other one,
3445 but if I switch back to the first, I have to log in on each operation.</a></h4>
3451 but nothing happens after that, only a blank screen.</a></h4>
3454 bug in Opera6, because it is not able to interpret frameset definitions
3455 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3456 Opera7 at least.</p>
3465 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3470 address and you are starting
3472 containing a domain name, or the reverse situation.</li>
3473 <li>Security settings in IE and/or Microsoft Security Center are
3474 too high, thus blocking scripts execution.</li>
3475 <li>The Windows Firewall is blocking Apache and MySQL. You must
3479 </ul>
3482 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3483 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3484 installed in their Firefox is causing the problem.</p>
3491 </a></h4>
3492 <p>
3493 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3494 specifying a wrong field-type.<br />
3495 Common errors include:
3496 </p>
3497 <ul>
3500 </ul>
3501 <p>
3502 Also, look at the syntax chapter in the MySQL manual to confirm that your
3503 syntax is correct.
3504 </p>
3508 phpMyAdmin generates only one index with those 2 fields.
3509 </a></h4>
3510 <p>
3512 index. If you want two indexes, create the first one when creating the
3513 table, save, then display the table properties and click the Index link to
3514 create the other index.
3515 </p>
3519 <p>
3520 Since version 2.2.3, you have a checkbox for each field that can be null.
3522 field's value. Since version 2.5.5, you have to use the checkbox to get
3524 a literal NULL in the field, and not a NULL value (this works in PHP4).
3525 </p>
3530 <p> Click on a database or table name in the left frame, the properties will be
3532 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3533 statements that can be used to recreate your database/table.
3534 <br /><br />
3536 transmit the resulting dump to your station. Depending on your PHP
3537 configuration, you will see options to compress the dump. See also the
3539 configuration variable.<br /><br />
3542 this document.</p>
3547 </a></h4>
3549 <p> Click on a database name in the left frame, the properties will be
3551 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3553 the path to your dump filename, or use the Browse button. Then click Go.
3554 <br /><br />
3556 that you upgrade to take advantage of the new features.
3557 <br /><br />
3559 in this document.
3560 </p>
3565 <p> Here is an example with the tables persons, towns and countries, all
3567 table, create it as explained in the configuration section. Then create the
3568 example tables:</p>
3570 <pre>
3571 CREATE TABLE REL_countries (
3572 country_code char(1) NOT NULL default '',
3573 description varchar(10) NOT NULL default '',
3574 PRIMARY KEY (country_code)
3575 ) TYPE=MyISAM;
3577 INSERT INTO REL_countries VALUES ('C', 'Canada');
3579 CREATE TABLE REL_persons (
3580 id tinyint(4) NOT NULL auto_increment,
3581 person_name varchar(32) NOT NULL default '',
3583 country_code char(1) NOT NULL default '',
3584 PRIMARY KEY (id)
3585 ) TYPE=MyISAM;
3587 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3588 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3590 CREATE TABLE REL_towns (
3592 description varchar(30) NOT NULL default '',
3593 PRIMARY KEY (town_code)
3594 ) TYPE=MyISAM;
3596 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3597 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3598 </pre>
3604 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3608 </ul>
3616 <li>In the fields row, choose persons.person_name and click the
3618 <li>Do the same for towns.description and countries.descriptions in the
3621 the correct joins have been generated</li>
3623 </ul>
3627 <p>
3628 Starting from the previous example, create the pma_table_info as explained
3629 in the configuration section, then browse your persons table,
3630 and move the mouse over a town code or country code.
3631 <br /><br />
3632 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3633 enables: drop-down list of possible values.
3634 </p>
3637 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3638 <p>
3641 <br /><br />
3642 Then you need to think about your schema layout. Which tables will go on
3643 which pages?
3644 </p>
3645 <ul>
3651 page and click Go. If you like, you
3653 linked tables onto the new page.</li>
3654 <li>Select the name of the new page (making sure the Edit radio button
3655 is selected) and click Go.</li>
3657 Coordinates are relative; your diagram will
3658 be automatically scaled to fit the page. When initially placing tables
3659 on the page, just pick any coordinates -- say, 50x50. After clicking
3661 position the element correctly.</li>
3663 first be sure to click the Save
3664 button beneath the list of tables and coordinates, to save any changes
3665 you made there. Then scroll all the way down, select the
3667 you want, and click Go.</li>
3668 <li>Internet Explorer for Windows may suggest an incorrect filename when
3673 browsers on Windows, do not have this problem.</li>
3674 </ul>
3678 columns!</a></h4>
3680 <p> No, it's MySQL that is doing
3686 underscores in the database name?</a></h4>
3688 <p> If you do not put a backslash before the underscore, this is a wildcard
3691 john2db ...<br /><br />
3693 If you put a backslash before the underscore, it means that the database
3694 name will have a real underscore.</p>
3698 statistics pages?</a></h4>
3709 if it already exists during the import. It does NOT drop the table after
3710 your export, it only affects the import file.</li>
3712 Otherwise, you may get an error if the table name exists but has a
3713 different structure.</li>
3715 (if any) will be included in backup.</li>
3717 field and table names formed with special characters are protected.</li>
3719 types set in the pmadb in the dump as
3721 </li>
3722 </ul>
3727 command, for better documentation (but resulting file is bigger).</li>
3729 once the INSERT verb and the table name.</li>
3732 </li>
3734 more info is provided in the
3736 but basically with this selected, invalid values are adjusted and
3737 inserted rather than causing the entire statement to fail.</li>
3738 </ul>
3742 in its name.</a></h4>
3745 is the normal way to reference a database and table name. Worse, MySQL
3746 will usually let you create a database with a dot, but then you cannot
3747 work with it, nor delete it.</p>
3760 for usage.<br />
3761 On a more recent pear version, I had problems with the state of Net_DIME
3762 being beta, so this single command
3764 needed modules.<br />
3765 If you use the Validator, you should be aware that any
3767 submit will be stored anonymously (database/table/column names,
3768 strings, numbers replaced with generic values). The Mimer
3771 We utilize it as free SOAP service.</p>
3775 it, but MySQL says "BLOB column '...' used in key specification without
3778 <p> The right way to do this, is to create the field without any indexes,
3780 dialog. On this page, you will be able to choose your BLOB field, and
3781 set a size to the index, which is the condition to create an index on
3782 a BLOB field.</p>
3786 editing fields?</a></h4>
3788 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3789 with many editing fields (table structure changes, row editing, etc.)
3790 (must be enabled in configuration - see.
3792 You can also have a look at the directive
3794 ('vertical') and see if this eases up editing for you.</p>
3798 WTF is this feature then useful for?</a></h4>
3800 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3801 on them. Otherwise you could just put a comment on the field. Because entering
3802 your own mimetype will cause serious syntax checking issues and validation,
3803 this introduces a high-risk false-user-input situation. Instead you have to
3804 initialize mimetypes using functions or empty mimetype definitions.<br />
3805 Plus, you have a whole overview of available mimetypes. Who knows all those
3806 mimetypes by heart so he/she can enter it at will?</p>
3810 can't I see any bookmarks below the query box? What is this variable for?
3811 </a></h4>
3813 <p> Any query you have executed can be stored as a bookmark on the page where the
3814 results are displayed. You will find a button labeled 'Bookmark this query'
3815 just at the end of the page.<br />
3816 As soon as you have stored a bookmark, it is related to the database you run
3817 the query on. You can now access a bookmark dropdown on each page, the query
3818 box appears on for that database.<br /><br />
3820 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3824 aware of that you HAVE to create a valid query, otherwise your query won't be
3825 even able to be stored in the database.<br />
3827 for your query will remain the way it is, but will be stripped of the /**/
3828 chars. So you can use:<br /><br />
3832 which will be expanded to<br /><br />
3836 in your query, where VARIABLE is the string you entered in the input box. If
3837 an empty string is provided, no replacements are made.<br /><br />
3839 A more complex example. Say you have stored this query:<br /><br />
3841 <br /><br />
3844 the full query will be:<br /><br />
3847 <br /><br />
3851 spaces inserted there
3852 will be later also inserted as spaces in your query and may lead to unexpected
3853 results especially when
3855 Your initial query which is going to be stored as a bookmark has to yield at
3856 least one result row so
3857 you can store the bookmark. You may have that to work around using well
3861 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3862 include exported table?</a></h4>
3864 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3865 document should look like following one (assuming you have table
3868 <pre>
3869 \documentclass{article} % or any class you want
3870 \usepackage{longtable} % for displaying table
3871 \begin{document} % start of document
3872 \include{table} % including exported table
3873 \end{document} % end of document
3874 </pre>
3878 access them.
3879 </a></h4>
3882 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3883 enable users to see all the database names.
3886 So if your users do not need those privileges, you can remove them and their
3887 databases list will shorten.</p>
3891 possible values for a field, based on some foreign table?</a></h4>
3893 <p> You have to setup appropriate links between the tables, and also
3897 foreign table, a drop-down list of values will be available.
3898 You will see two lists of values, the first list containing the key
3899 and the display field, the second list containing the display field
3900 and the key. The reason for this is to be able to type the first
3901 letter of either the key or the display field.<br /><br />
3903 For 200 values or more, a distinct window will appear, to browse foreign
3904 key values and choose one.</p>
3908 automatically when entering Browse mode for a table?</a></h4>
3910 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3911 </p>
3915 Excel files, how can I enable that?</a></h4>
3917 <p> Current version does support direct export to Microsoft Excel and Word
3918 versions 2000 and newer. If you need export older versions, you can use
3920 which works out of the box or you can
3922 several problems, most important are limitation of cell content to 255
3923 chars and no support for charsets, so think carefully whether you want to
3924 enable this.</b>. For enabling this you need to set
3928 module Spreadsheet_Excel_Writer into php include path. The
3929 installation can be done by following command:</p>
3931 <pre>
3932 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3933 </pre>
3935 <p> First part of switches set we want to install beta version of that module
3936 (no stable version available yet) and then we tell pear we want to satisfy
3937 dependencies.</p>
3939 <p> If you are running in PHP safe mode, you will have to set
3942 modules are located, for example:</p>
3944 <pre>
3945 safe_mode_include_dir = /usr/local/lib/php
3946 </pre>
3950 <pre>
3951 cd phpMyAdmin
3952 mkdir tmp
3953 chmod o+rwx tmp
3954 </pre>
3958 what happens to my column comments stored in pmadb?</a></h4>
3960 <p> Automatic migration of a table's pmadb-style column comments to the native
3961 ones is done whenever you enter Structure page for this table.</p>
3968 <p> Our Bug Tracker is located at
3970 under the Bugs section.<br /><br />
3972 But please first discuss your bug with other users:<br />
3978 existing language, where do I start?</a></h4>
3980 <p> Always use the current SVN version of your language file.
3982 don't know how to get the SVN version, please ask one of the developers.
3983 <br />
3984 Please note that we try not to use HTML entities like &eacute; in
3985 the translations, since we define the right character set in the file.
3986 With HTML entities, the text on JavaScript messages would not
3987 display correctly.
3988 However there are some entities that need to be there, for quotes
3989 ,non-breakable spaces, ampersands, less than, greater than.<br />
3990 You can then put your translations, as a zip file to avoid losing special
3991 characters, on the sourceforge.net translation tracker.<br />
3992 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3993 list, because this is where we ask for translations of new messages.</p>
3997 phpMyAdmin. How should I proceed?</a></h4>
4002 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4003 </li>
4005 <li>generate patch with your changes:
4007 </li>
4010 tracker of the phpMyAdmin project</a>.
4011 </li>
4012 </ol>
4014 <p> Write access to the SVN tree is granted only to experienced developers who
4015 have already contributed something useful to phpMyAdmin.<br />
4021 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4023 <p> Please refer to
4024 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4025 </p>
4027 <!-- DEVELOPERS -->
4030 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4031 great features have been written by other people and you too can help to
4032 make phpMyAdmin a useful tool.</p>
4034 <p> If you're planning to contribute source, please read the following
4035 information:</p>
4041 it free from other code.<br />
4042 Commonly used functions should be added to
4045 <li>Obviously, you're free to use whatever coding style you want. But
4046 please try to keep your code as simple as possible: beginners are
4047 using phpMyAdmin as an example application.<br />
4048 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4049 compliant on one hand, they fit the
4052 coding standards</a>
4053 on the other hand. Please pay attention to this.</li>
4054 <li>Please try to keep up the file-naming conventions. Table-related stuff
4057 <li>Please don't use verbose strings in your code, instead add the string
4062 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4063 better debug and profile their code.<br />
4064 Please see the
4066 options for more information.<br />
4067 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4068 lost during its re-entry into Earth's atmosphere and in memory of the
4069 brave men and women who gave their lives for the people of Earth.</li>
4070 </ul>
4072 <!-- CREDITS -->
4075 <pre>
4076 phpMyAdmin - Credits
4077 ====================
4079 CREDITS, in chronological order
4080 -------------------------------
4083 * creator of the phpmyadmin project
4087 * multi-language version
4088 * various fixes and improvements
4090 * current project maintainer
4093 * started SourceForge phpMyAdmin project in March 2001
4094 * sync'ed different existing CVS trees with new features and bugfixes
4095 * multi-language improvements, dynamic language selection
4096 * current project maintainer
4097 * many bugfixes and improvements
4100 * rewrote and optimized javascript, DHTML and DOM stuff
4101 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4102 generate XHTML1.0 and CSS2 compliant codes
4103 * improved the language detection system
4104 * many bugfixes and improvements
4107 * database maintenance controls
4108 * table type code
4110 * DB-based configuration (Not completed)
4113 * many bugfixes and improvements
4116 * bookmarks feature
4117 * multiple dump feature
4118 * gzip dump feature
4119 * zip dump feature
4122 * various fixes
4123 * moderator of the phpMyAdmin former users forum at phpwizard.net
4129 * rewrote and fix dump code
4130 * bugfixes
4133 * rewrote dump code for PHP4
4134 * mySQL table statistics
4135 * bugfixes
4138 * main author of the version 2.1.0.1
4139 * bugfixes
4143 * abstract database interface (PMA_DBI) with MySQLi support
4144 * privileges administration
4146 * various features and fixes
4147 * German language file updates
4150 * automatic joins in QBE
4151 * links column in printview
4152 * Relation view
4155 * enhanced index creation/display feature
4156 * feature to use a different charset for HTML than for MySQL
4157 * improvements of export feature
4158 * various features and fixes
4159 * Czech language file updates
4162 (http://sf.net/projects/phpmysqlformgen/)
4163 * suggested the patch for multiple table printviews
4166 * built the patch for vertical display of table rows
4167 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4168 * Improvement of column/db comments
4169 * (MIME)-Transformations for columns
4170 * Use custom alias names for Databases in left frame
4171 * hierarchical/nested table display
4172 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4173 * new icon sets
4174 * vertical display of column properties page
4175 * some bugfixes, features, support, German language additions
4178 * japanese kanji encoding conversion feature
4181 * the Cookie authentication mode
4184 * table relation-links feature
4187 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4188 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4189 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4195 * phpMyAdmin logo (until June 2004)
4198 * blowfish library from the Horde project
4201 * mysqli support
4202 * many bugfixes and improvements
4205 * redesign for 2.6.0
4206 * phpMyAdmin sailboat logo (June 2004)
4209 * Representation at conferences
4212 * interface improvements
4213 * various bugfixes
4215 - Ivan A Kirillov
4216 * new relations Designer
4218 And also to the following people who have contributed minor changes,
4219 enhancements, bugfixes or support for a new language since version 2.1.0:
4221 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4222 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4223 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4224 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4226 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4227 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4228 Luís V., Martijn W. van der Lee,
4229 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4233 Original Credits of Version 2.1.0
4234 ---------------------------------
4236 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4237 to create a web-based interface to MySQL using PHP3. Although I have not
4238 used any of his source-code, there are some concepts I've borrowed from
4239 him. phpMyAdmin was created because Peter told me he wasn't going to
4240 further develop his (great) tool.
4241 Thanks go to
4243 code for the check when dropping a table or database. He also suggested
4244 that you should be able to specify the primary key on tbl_create.php3. To
4245 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4246 well as a bug-report. Plus many smaller improvements.
4248 were introduced in 1.3.0 (including quite significant ones like the
4249 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4250 bug-fixes and help.
4252 language-independent by outsourcing the strings to a separate file. He
4253 also contributed the French translation.
4255 tbl_select.php3, a feature to display only some fields from a table.
4257 functions in tbl_change.php3. He also added the
4260 servers and is a regular contributor for bug-fixes.
4262 features for 2.0.6.
4263 The following people have contributed minor changes, enhancements, bugfixes
4264 or support for a new language:
4265 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4266 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4267 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4268 G. Wieggers.
4270 And thanks to everyone else who sent me email with suggestions, bug-reports
4271 and or just some feedback.
4272 </pre>
4278 <ul>
4280 - the default name of Apache's directory-level configuration file.</li>
4284 - a software application that enables a user to display and interact with
4285 text, images, and other information typically located on a web page at a
4286 website on the World Wide Web.</li>
4288 - a free software/open source data compression algorithm and program
4289 developed by Julian Seward.</li>
4291 - an important World Wide Web technology that enables a client web browser
4292 to request data from a program executed on the Web server.</li>
4294 - a log or record of changes made to a project.</li>
4296 - a computer system that accesses a (remote) service on another computer
4297 by some kind of network.</li>
4299 - a set of data values of a particular simple type, one for each row of
4300 the table.</li>
4302 - a packet of information sent by a server to a World Wide Web browser
4303 and then sent back by the browser each time it accesses that server.</li>
4305 - Comma-seperated values</li>
4308 - an organized collection of data.</li>
4311 - a PHP module that extends PHP with additional functionality.</li>
4313 - a list of commonly asked question and there answers.</li>
4315 - one part of divided data/columns.</li>
4317 - a field or group of fields in a database record that point to a key
4318 field or group of fields forming a key of another database record in some
4319 (usually different) table.</li>
4321 - the free PDF library</li>
4323 GD Graphics Library</a> - a library by Thomas Boutell and others for
4324 dynamically manipulating images.</li>
4327 - gzip is short for GNU zip, a GNU free software file compression
4328 program.</li>
4330 - any machine connected to a computer network, a node that has a hostname.</li>
4332 - the unique name by which a network attached device is known on a network.</li>
4334 (HyperText Transfer Protocol)</a>
4335 - the primary method used to transfer or convey information on the World
4336 Wide Web.</li>
4339 additional security measures.</li>
4340 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4341 - a set of Internet-based services for servers using Microsoft Windows.</li>
4343 - a feature that allows quick access to the rows in a table.</li>
4345 - a data-oriented protocol used by source and destination hosts for
4346 communicating data across a packet-switched internetwork.</li>
4348 - a unique number that devices use in order to identify and communicate
4349 with each other on a network utilizing the Internet Protocol standard.</li>
4351 (Internet Server Application Programming Interface)</a>
4352 - the API of Internet Information Services (IIS).</li>
4354 - a business or organization that offers users access to the Internet and related services.</li>
4356 - a most commonly used standard method of lossy compression for
4357 photographic images.</li>
4363 - line of personal computers is designed, developed, manufactured, and
4364 marketed by Apple Computer.</li>
4365 <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>
4366 - the operating system which is included with all currently shipping Apple
4367 Macintosh computers in the consumer and professional markets.</li>
4369 - a cryptographic library.</li>
4371 - the MCrypt PHP extension.</li>
4372 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4373 - an Internet Standard for the format of e-mail.</li>
4375 - some sort of extension for the Apache Webserver.</li>
4377 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4378 Management System (DBMS).</li>
4380 - the improved MySQL client PHP extension.</li>
4382 - the MySQL client PHP extension.</li>
4384 - open standard for office documents.</li>
4385 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4386 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4388 (Portable Document Format)</a>
4389 - a file format developed by Adobe Systems for representing two
4390 dimensional documents in a device independent and resolution independent
4391 format.</li>
4393 - the PHP Extension and Application Repository.</li>
4395 - the perl-compatible regular expression functions for PHP</li>
4397 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4398 programming language used mainly for developing server-side applications
4399 and dynamic web content, and more recently, a broader range of software
4400 applications.</li>
4402 - a connection through which data is sent and received.</li>
4404 - Request for Comments (RFC) documents are a series of memoranda
4405 encompassing new research, innovations, and methodologies applicable to
4406 Internet technologies.</li>
4410 - represents a single, implicitly structured data item in a table.</li>
4412 - a computer system that provides services to other computing
4413 systems over a network.</li>
4414 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4415 - handlers for different table types</li>
4417 - a form of inter-process communication.</li>
4419 Sockets Layer)</a>
4420 - a cryptographic protocol which provides secure communication on the Internet.</li>
4422 - Structured Query Language</li>
4424 - a set of data elements (cells) that is organized, defined and stored as
4425 horizontal rows and vertical columns where each item can be uniquely
4426 identified by a label or key or by it?s position in relation to other items.</li>
4429 - a type of archive file format: the Tape ARchive format.</li>
4431 - one of the core protocols of the Internet protocol suite.</li>
4435 - a sequence of characters, conforming to a standardized format, that is
4436 used for referring to resources, such as documents and images on the
4437 Internet, by their location.</li>
4439 - A computer (program) that is responsible for accepting HTTP requests
4440 from clients and serving them Web pages.</li>
4442 - a W3C-recommended general-purpose markup language for creating
4443 special-purpose markup languages, capable of describing many different
4444 kinds of data.</li>
4446 - a popular data compression and archival format.</li>
4448 - an open-source, cross-platform data compression library by Jean-loup
4449 Gailly and Mark Adler.</li>
4450 </ul>
4460 </body>
4461 </html>