| blob | d945f9529dd38b0d17322240986b8c84ee3adf55 |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 </li>
63 <li>You need GD2 support in PHP to display inline
65 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
198 provided for those who prefer a graphical installation. Creating a
200 still a quick way to get started and needed for some advanced features.
201 <ul><li>To manually create the file, simply use your text editor to
204 file) in the main (top-level) phpMyAdmin directory (the one
208 default value is okay for a particular setting, there is no
210 few directives to get going, a simple configuration may look
211 like this:
212 <pre>
213 <?php
214 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
216 $i=0;
217 $i++;
218 $cfg['Servers'][$i]['auth_type'] = 'cookie';
219 ?>
220 </pre>
221 Or, if you prefer to not be prompted every time you log in:
222 <pre>
223 <?php
225 $i=0;
226 $i++;
227 $cfg['Servers'][$i]['user'] = 'root';
228 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
229 ?>
230 </pre>
231 For a full explanation of possible configuration values, see the
237 directory. This is a security measure. On a Linux/Unix system you
238 can use the following commands:
239 <pre>
240 cd phpMyAdmin
241 mkdir config # create directory for saving
242 chmod o+rw config # give it world writable permissions
243 </pre>
244 And to edit an existing configuration, copy it over first:
245 <pre>
246 cp config.inc.php config/ # copy current configuration for editing
247 chmod o+w config/config.inc.php # give it world writable permissions
248 </pre>
249 On other platforms, simply create the folder and ensure that your
258 the webserver does not have the proper permissions you may see the
260 config/</tt> directory exists and has the proper permissions -
262 and upload (via FTP or some similar means) to the proper location.<br /><br />
264 Once the file has been saved, it must be moved out of the <tt>
265 config/</tt> directory and the permissions must be reset, again
266 as a security measure:
267 <pre>
268 mv config/config.inc.php . # move file to current directory
269 chmod o-rw config.inc.php # remove world read and write permissions
270 </pre>
271 Now the file is ready to be used. You can choose to review or edit
272 the file with your favorite editor, if you prefer to set some
273 advanced options which the setup script does not provide.</li></ul></li>
274 <li>If you are using the
276 protect the phpMyAdmin installation directory because using
277 config does not require a user to
278 enter a password to access the phpMyAdmin installation. Use of an alternate
279 authentication method is recommended, for example with
287 in your browser. phpMyAdmin should now display a welcome screen
288 and your databases, or a login dialog if using
290 authentication mode.</li>
292 webserver configuration. For Apache you can use supplied .htaccess file
293 in that folder, for other webservers, you should configure this yourself.
294 Such configuration prevents from possible path exposure and cross side
295 scripting vulnerabilities that might happen to be found in that code.</li>
296 </ol>
300 <p> For a whole set of new features (bookmarks, comments,
303 transformation, etc.) you need to create a set of special tables. Those
304 tables can be located in your own database, or in a central database for a
305 multi-user installation (this database would then be accessed by the
306 controluser, so no other user should have rights to it).</p>
315 installation.</p>
320 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
321 that you may need special (administrator) privileges to create the database
322 and tables, and that the script may need some tuning, depending on the
323 database name.</p>
328 section</a>. You will also need to have a controluser with the proper rights
335 unpacked one. Configuration files from very old versions (2.3.0 or before) may
336 require some tweaking as some options have been changed or removed.
338 statement that you might find near the end of your configuration file.</p>
342 is version-specific.</p>
345 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
346 you should run the SQL script found in
353 where you want to give users access to their own database and don't want
354 them to play around with others.<br />
355 Nevertheless be aware that MS Internet Explorer seems to be really buggy
357 in this area!<br />
360 that your user/password pair are not in clear in the configuration file.
361 </li>
364 authentication modes are more secure: the MySQL login information does
365 not need to be set in the phpMyAdmin configuration file (except possibly
367 However, keep in mind that the password travels in plain text, unless
368 you are using the HTTPS protocol.<br />
369 In cookie mode, the password is stored, encrypted with the blowfish
370 algorithm, in a temporary cookie.</li>
373 your MySQL server is previous to 4.1.2, or is running with
383 file under the
385 $cfg['Servers'][$i]['controluser']</a></tt> and
390 only an example: use something else in your file!</b> Input these
391 statements from the phpMyAdmin SQL Query window or mysql command–line
392 client.<br />
394 if it's not the same as the MySQL server's one.
396 <pre>
397 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
398 GRANT SELECT (
399 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
400 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
401 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
402 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
403 Execute_priv, Repl_slave_priv, Repl_client_priv
404 ) ON mysql.user TO 'pma'@'localhost';
405 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
406 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
407 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
408 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
410 If you are using an old MySQL version (below 4.0.2), please replace
411 the first GRANT SELECT query by this one:
413 <pre>
414 GRANT SELECT (
415 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
416 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
417 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
418 ) ON mysql.user TO 'pma'@'localhost';</pre>
420 ... and if you want to use the many new relation and bookmark features:
422 <pre>
424 </pre>
428 Of course, the above queries only work if your MySQL version supports
432 on a set of particular databases. Normally you shouldn't give global
433 privileges to an ordinary user, unless you understand the impact of those
434 privileges (for example, you are creating a superuser).<br />
438 <pre>
439 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
440 </pre>
442 What the user may now do is controlled entirely by the MySQL user
443 management system.<br />
445 authentication mode, you don't need to fill the user/password fields
447 array.</li>
448 </ul>
453 method and allows you to log in as any valid MySQL user.</li>
454 <li>Is supported with most PHP configurations. For
467 mode.</li>
468 </ul>
472 <ul><li>You can use this method as a replacement for the
474 (for example, if you're running
476 <li>Obviously, the user must enable cookies in the browser, but this is
477 now a requirement for all authentication modes.</li>
478 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
479 with the same username.</li>
480 <li>If you want to log in to arbitrary server see
485 not required.</li>
486 </ul>
490 <ul><li>This mode is a convenient way of using credentials from another
491 application to authenticate to phpMyAdmin.</li>
492 <li>The other application has to store login information into
493 session data.</li>
495 section.</li>
496 </ul>
499 <ul><li>This mode is the less secure one because it requires you to fill the
501 $cfg['Servers'][$i]['user']</a> and
503 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
504 can read your config.inc.php can discover your username and password).
505 <br />
512 is an entry explaining how to protect your configuration file.</li>
513 <li>For additional security in this mode, you may wish to consider the Host
514 authentication
516 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
518 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
519 directives.</li>
520 <li>Unlike cookie and http, does not require a user to log in when first
521 loading the phpMyAdmin site. This is by design but could allow any
522 user to access your installation. Use of some restriction method is
524 HTTP-AUTH directive or disallowing incoming HTTP requests at
525 one’s router or firewall will suffice (both of which
526 are beyond the scope of this manual but easily searchable with Google).</li>
527 </ul>
529 <!-- CONFIGURATION -->
533 users:</span> PHP does not seem to like
537 before saving a script you have modified.</p>
542 section to create one. This file only needs to contain the parameters you want to
543 change from their corresponding default value in
546 <p> The parameters which relate to design (like colors) are placed in
549 your site specific code to be included on start and end of each page.</p>
553 (with full path) to your phpMyAdmin installation's directory.
556 some web servers are case–sensitive.
559 Starting with version 2.3.0, it is advisable to try leaving this
560 blank. In most cases phpMyAdmin automatically detects the proper
561 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
562 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
563 A good test is to browse a table, edit a row and save it. There should
564 be an error message if phpMyAdmin is having trouble auto–detecting
565 the correct value. If you get an error that this must be set or if
566 the autodetect code fails to detect your path, please post a bug
567 report on our bug tracker so we can improve the code.</dd>
571 with master / foreign – tables (see
573 <br />
574 If you tried to set this up and it does not work for you, have a look on
576 use it. You will find a link that will analyze why those features have
577 been disabled.<br />
578 If you do not want to use those features set this variable to
582 <dd>A warning is displayed on the main page if Suhosin is detected.
584 from appearing.</dd>
588 domain to call phpMyAdmin inside a frame, and is a potential security
589 hole allowing cross-frame scripting attacks.</dd>
593 algorithm to encrypt the password.<br />
595 passphrase of your choice. It will be used internally by the blowfish
596 algorithm: you won’t be prompted for this passphrase. The maximum
601 MySQL servers. Therefore, a
603 been added which contains the login information for the different servers.
604 The first
606 contains the hostname of the first server, the second
608 the hostname of the second server, etc. In
610 server definition, however you can put as many as you need in
612 have to define all settings, just those you need to change).</dd>
616 $i-th MySQL-server. E.g. localhost.</dd>
621 ignores this port number and connects with the socket, so if you want
622 to connect to a port different from the default port, use
625 </dd>
629 To determine the correct socket, check your MySQL configuration or, using the
631 Among the resulting information displayed will be the socket used.</dd>
634 <dd>Whether to enable SSL for connection to MySQL server.
635 </dd>
638 <dd>What type connection to use with the MySQL server. Your options are
640 is nearly guaranteed to be available on all MySQL servers, while
641 sockets are not supported on some platforms.<br /><br />
643 To use the socket mode, your MySQL server must be on the same machine
644 as the Web server.</dd>
647 <dd>What php MySQL extension to use for the connection. Valid options are:
648 <br /><br />
651 The classic MySQL extension. This is the recommended and default
652 method at this time.<br /><br />
655 The improved MySQL extension. This extension became available
656 with php 5.0.0 and is the recommended way to connect to a server
660 <dd>Whether to use a compressed protocol for the MySQL server connection
661 or not (experimental).<br />
667 </dt>
669 all relational features (see
671 and, for a MySQL server previous to 4.1.2 or running with
674 authentication mode).<br /><br />
677 cookie authentication modes (or 'config'
678 authentication mode since phpMyAdmin 2.2.1), you need to supply the
683 This account is used to check what databases the user will see at
684 login.<br />
688 In phpMyAdmin versions before 2.2.5, those were called
692 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
693 <dd>Whether config or cookie or
695 should be used for this server.
697 is the plain old way: username and password are stored in
699 <li>'cookie' authentication mode
701 2.2.3 allows you to log in as any valid MySQL user with the
702 help of cookies. Username and password are stored in
703 cookies during the session and password is deleted when it
704 ends. This can also allow you to log in in arbitrary server if
705 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
706 </li>
707 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
708 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
709 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
710 <li>'signon' authentication mode
712 as introduced in 2.10.0 allows you to log in from prepared PHP
713 session data. This is useful for implementing single signon
714 from another application. Sample way how to seed session is in
720 </ul>
723 for more information.
724 </dd>
728 </dt>
729 <dd>
730 When using auth_type = 'config', this is the user/password-pair
731 which phpMyAdmin will use to connect to the
732 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
733 cookie authentication is used and should be empty.</dd>
735 <span
737 </dt>
738 <dd>
739 Allow attempt to log in without password when a login with password
740 fails. This can be used together with http authentication, when
741 authentication is done some other way and phpMyAdmin gets user name
742 from auth and uses empty password for connecting to MySQL. Password
743 login is still tried first, but as fallback, no password method is
744 tried.</dd>
747 </dt>
748 <dd>
749 If set to a (an array of) database name(s), only this (these) database(s)
750 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
751 database(s) name(s) may contain MySQL wildcards characters
755 This setting is an efficient way to lower the server load since the
756 latter does not need to send MySQL requests to build the available
758 privileges rules of the MySQL database server</span>. If set, it just
759 means only these databases will be displayed but
761 <br /><br />
763 An example of using more that one database:
765 <br /><br />
767 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
768 databases in the left frame, so that you can individually arrange your databases.<br />
769 If you want to have certain databases at the top, but don't care about the others, you do not
770 need to specify all other databases. Use:
772 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
773 order.</dd>
776 </dt>
777 <dd>Regular expression for hiding some databases. This only hides them
778 from listing, but a user is still able to access them (using, for example,
779 the SQL query area). To limit access, use the MySQL privilege system.
780 <br /><br />
785 More information on regular expressions can be found in the
787 PCRE pattern syntax</a> portion of the PHP reference manual.
788 </dd>
791 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
792 this string will be displayed instead of the hostname in the pull-down
793 menu on the main page. This can be useful if you want to show only
794 certain databases on your system, for example. For HTTP auth, all
795 non-US-ASCII characters will be stripped.</dd>
799 </dt>
800 <dd>The name of the database containing the linked-tables infrastructure.
801 <br /><br />
804 section in this document to see the benefits of this infrastructure,
805 and for a quick way of creating this database and the needed tables.
806 <br /><br />
808 If you are the only user of this phpMyAdmin installation, you can
809 use your current database to store those special tables; in this
810 case, just put your current database name in
812 set this parameter to the name of your central database containing
813 the linked-tables infrastructure.</dd>
817 </dt>
819 useful for queries you often run.<br /><br />
821 To allow the usage of this functionality:
823 <li>enter the table name in
825 </ul>
826 </dd>
830 </dt>
832 which field is a key in another table (a foreign key). phpMyAdmin
833 currently uses this to
834 <ul><li>make clickable, when you browse the master table, the data values
835 that point to the foreign table;</li>
837 when browsing the master table, if you move the mouse to a column
838 containing a foreign key (use also the 'table_info' table);<br />
841 <li>in edit/insert mode, display a drop-down list of possible foreign
845 <li>display links on the table properties page, to check referential
846 integrity (display missing foreign keys) for each described key;
847 </li>
851 schema of your database (also uses the table_coords table).</li>
852 </ul>
854 The keys can be numeric or character.<br /><br />
856 To allow the usage of this functionality:
859 infrastructure</li>
860 <li>put the relation table name in
862 <li>now as normal user open phpMyAdmin and for each one of your
863 tables where you want to use this feature, click
865 </li>
866 </ul>
870 future development of the cross-db relations.
871 </dd>
875 </dt>
876 <dd>
877 Since release 2.3.0 you can describe, in a special 'table_info'
878 table, which field is to be displayed as a tool-tip when moving the
879 cursor over the corresponding key.<br />
880 This configuration variable will hold the name of this special
881 table. To allow the usage of this functionality:
883 <li>put the table name in
885 <li>then for each table where you want to use this feature,
887 to choose the field.</li>
888 </ul>
890 </dd>
894 </dt>
897 the relations between your tables. To do this it needs two tables
902 schema output).<br /><br />
906 To allow the usage of this functionality:
909 infrastructure</li>
910 <li>put the correct table names in
913 </ul>
916 </dd>
920 </dt>
922 Since release 2.3.0 you can store comments to describe each column for
924 <br /><br />
926 Starting with release 2.5.0, comments are consequently used on the table
927 property pages and table browse view, showing up as tool-tips above the
928 column name (properties page) or embedded within the header of table in
929 browse view. They can also be shown in a table dump. Please see the
930 relevant configuration directives later on.<br /><br />
932 Also new in release 2.5.0 is a MIME-transformation system which is also
934 Transformations</a> for further information. To use the
935 MIME-transformation system, your column_info table has to have the three
936 new fields 'mimetype', 'transformation', 'transformation_options'.
937 <br /><br />
939 To allow the usage of this functionality:
941 infrastructure</li>
942 <li>put the table name in
946 <pre>
947 ALTER TABLE `pma_column_comments`
948 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
949 ADD `transformation` VARCHAR( 255 ) NOT NULL,
950 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
951 </pre>
954 renamed from<br />
957 </ul>
958 </dd>
962 </dt>
965 all queries you entered manually into the phpMyAdmin interface. If you
966 don't want to use a table-based history, you can use the JavaScript-based
967 history. Using that, all your history items are deleted when closing the
968 window.<br /><br />
970 Using
972 you can specify an amount of history items you want to have on hold. On
973 every login, this list gets cut to the maximum amount.<br /><br />
975 The query history is only available if JavaScript is enabled in your
976 browser.<br /><br />
978 To allow the usage of this functionality:
981 infrastructure</li>
983 </li>
984 </ul>
985 </dd>
989 </dt>
991 to visually manage the relations.
992 <br /><br />
994 To allow the usage of this functionality:
997 infrastructure</li>
999 </li>
1000 </ul>
1001 </dd>
1004 </dt>
1006 column_info table got enhanced with three new fields. If the above variable
1008 latest table structure available. If not, it will emit a warning to the
1009 superuser.<br /><br />
1011 You can disable this checking behavior by setting the variable to false,
1012 which should offer a performance increase.<br /><br />
1014 Recommended to set to FALSE, when you are sure, your table structure is
1015 up to date.</dd>
1017 boolean</dt>
1018 <dd>Whether to allow root access. This is just simplification of rules below.
1019 </dd>
1022 </dt>
1024 authentication is disabled.<br /><br />
1027 all deny rules followed by allow rules. Access is allowed by default. Any
1028 client which does not match a Deny command or does match an Allow command
1029 will be allowed access to the server. <br /><br />
1032 applies all allow rules followed by deny rules. Access is denied by
1033 default. Any client which does not match an Allow directive or does
1034 match a Deny directive will be denied access to the server.<br /><br />
1036 If your rule order is set to 'explicit', the authentication is
1037 performed in a similar fashion to rule order 'deny,allow', with the
1041 and was available in Apache by specifying allow and deny rules without
1042 setting any order.<br /><br />
1044 Please also see <a
1046 address behind proxies.
1047 </dd>
1049 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1050 </dt>
1051 <dd>The general format for the rules is as such:
1053 <pre>
1055 </pre>
1060 well (please note that those containing SERVER_ADDRESS might not be
1061 available on all webservers):
1062 <pre>
1068 </pre>
1070 Having an empty rule list is equivalent to either using
1076 following work:<br />
1078 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1079 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1080 But the following does not work:<br />
1083 </dd>
1084 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1085 <dd>Name of session which will be used for signon authentication method.
1086 </dd>
1088 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1089 </dd>
1091 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1092 </dd>
1095 <dd>If you have more than one server configured, you can set
1097 that server when phpMyAdmin is started, or set it to 0 to be given a
1098 list of servers without logging in.<br />
1100 MUST be set to that server.</dd>
1103 <dd>The maximum number of database names to be displayed in the
1104 navigation frame and the database list.</dd>
1107 <dd>The maximum number of table names to be displayed in the
1108 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1109 when in Light mode.</dd>
1112 <dd>The maximum number of characters when a SQL query is displayed. The
1113 default limit of 1000 should be correct to avoid the display of tons
1114 of hexadecimal codes that represent BLOBs, but some users have real
1115 SQL queries that are longer than 1000 characters. Also, if a query's
1116 length exceeds this limit, this query is not saved in the history.</dd>
1119 <dd>Defines whether to use GZip output buffering for increased
1121 Set to true/false for enabling/disabling. When set to 'auto' (string),
1122 phpMyAdmin tries to enable output buffering and will automatically disable
1123 it if your browser has some problems with buffering. IE6 with a certain patch
1124 is known to cause data corruption when having enabled buffering.</dd>
1127 <dd>Whether persistent connections should be used or not (mysql_connect or
1128 mysql_pconnect).</dd>
1134 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1135 to zero, no time limit is imposed.<br />
1136 This setting is used while importing/exporting dump files but has no
1137 effect when PHP is running in safe mode.</dd>
1140 <dd>Set the number of bytes a script is allowed to allocate. If number set
1141 to zero, no limit is imposed.<br />
1142 This setting is used while importing/exporting dump files but has no
1143 effect when PHP is running in safe mode.<br />
1147 <dd>Mark used tables and make it possible to show databases with locked
1152 generated by phpMyAdmin should be displayed or not.</dd>
1155 <dd>Defines whether normal users (non-administrator) are allowed to
1156 delete their own database or not. If set as FALSE, the link "Drop
1158 mydatabase" will be rejected. Quite practical for
1160 customers.<br />
1161 Please note that this limitation of SQL queries is not as strict as
1162 when using MySQL privileges. This is due to nature of SQL queries
1163 which might be quite complicated. So this choice should be viewed as
1164 help to avoid accidental dropping rather than strict privilege
1165 limitation.</dd>
1169 displayed when you're about to lose data.</dd>
1172 <dd>Define whether the previous login should be recalled or not in cookie
1173 authentication mode.</dd>
1180 means that it will be kept for existing session. This is recommended
1181 for not trusted environments.</dd>
1184 <dd>If enabled (default), logout deletes cookies for all servers,
1185 otherwise only for current one. Setting this to false makes it easy to
1186 forget to log out from other server, when you are using more of
1187 them.</dd>
1193 <dd>Define whether phpMyAdmin will continue executing a multi-query
1194 statement if one of the queries fails. Default is to abort execution.</dd>
1197 <dd>Define whether phpMyAdmin will output the results of each query of a
1198 multi-query statement embedded into the
1203 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1204 <br /><br />
1207 MySQL servers behind the firewall where your
1209 </dd>
1212 <dd>Defines whether to use a select-based menu and display only the current
1213 tables in the left frame (smaller page). Only in Non-Lightmode you can
1214 use the feature to display nested folders using
1216 </dd>
1219 <dd>In light mode, defines whether to display the names of databases (in the
1220 selector) using a tree, see also
1222 </dd>
1225 <dd>The string used to separate the parts of the database name when showing
1226 them in a tree.</dd>
1229 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1230 This means if you have tables like 'first__second__third' this will be
1232 If set to FALSE or empty, the feature is disabled. NOTE: You should
1233 not use this separator at the beginning or end of a
1234 table name or multiple times after another without any other
1235 characters in between.</dd>
1238 <dd>Defines how many sublevels should be displayed when splitting
1239 up tables by the above separator.</dd>
1242 <dd>Defines whether to display table comment as tool-tip in left frame or
1243 not.</dd>
1246 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1247 comment and the real name. That means that if you have a table called
1248 'user0001' and add the comment 'MyName' on it, you will see the name
1249 'MyName' used consequently in the left frame and the tool-tip shows
1250 the real name of the DB.</dd>
1253 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1255 When setting this to 'nested', the Alias of the Tablename is only used
1256 to split/nest the tables according to the
1258 directive. So only the folder is called like the Alias, the tablename itself
1259 stays the real tablename.</dd>
1262 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1265 <dd>Enter URL where logo in the navigation frame will point to.
1266 For use especially with self made theme which changes this.
1275 <dd>Defines whether or not to display a server choice at the top of the left frame.
1276 Defaults to FALSE.</dd>
1278 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1279 Defaults to FALSE (drop-down).</dd>
1281 <dd>Defines whether to display database choice in light navigation frame as links
1282 instead of in a drop-down. Defaults to 'auto' - on main page list is
1283 shown, when database is selected, only drop down is displayed.</dd>
1285 <dd>Defines whether or not to display space usage and statistics about databases
1286 and tables.<br />
1287 Note that statistics requires at least MySQL 3.23.3 and that, at this
1288 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1291 <dd>Defines whether to display detailed server information on main page.
1292 You can additionally hide more information by using
1294 </dd>
1299 </dt>
1302 not at the starting main (right) frame. This setting
1303 does not check MySQL commands entered directly.<br /><br />
1305 Please note that to block the usage of phpinfo() in scripts, you
1312 hard coded password value in the configuration file, end users can't
1313 be allowed to change their passwords.</dd>
1316 <dd>Defines whether to suggest a database name on the
1321 content.</dd>
1324 <dd>Defines whether navigation bar buttons and the right panel top menu
1325 contain text or symbols only. A value of TRUE displays icons, FALSE
1326 displays text and 'both' displays both icons and text.</dd>
1329 <dd>Defines whether a user should be displayed a
1333 <dd>Number of rows displayed when browsing a result set. If the result set
1340 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1344 from editing when browsing a table's content. Valid values are:
1349 </ul>
1350 </dd>
1353 <dd>Defines whether or not MySQL functions fields should be initially
1354 displayed in edit/insert mode. Since version 2.10, the user can
1355 toggle this setting from the interface.
1356 </dd>
1359 <dd>Defines which type of editing controls should be used for CHAR and
1360 VARCHAR fields. Possible values are:
1361 <ul><li>input - this allows to limit size of text to size of field in
1362 MySQL, but has problems with newlines in fields</li>
1363 <li>textarea - no problems with newlines in fields, but also no
1364 length limitations</li>
1365 </ul>
1366 Default is old behavior so input.</dd>
1372 <dd>If there are fewer items than this in the set of foreign keys, then a
1373 drop-down box of foreign keys is presented, in the style described by the
1375 setting.</dd>
1378 <dd>For the foreign key drop-down fields, there are several methods of
1379 display, offering both the key and value data. The contents of the
1380 array should be one or both of the following strings:
1386 </dt>
1387 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1388 creating a dump file</dd>
1391 </dt>
1392 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1393 compressed exports. This doesn't affect smaller dumps and allows users to
1394 create larger dumps that won't otherwise fit in memory due to php
1395 memory limit. Produced files contain more GZip/BZip2 headers, but all
1396 normal programs handle this correctly.</dd>
1400 mainframe.</dd>
1404 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1409 <dd>How many columns will be utilized to display the tables on the
1410 database property view? Default is 1 column. When setting this to a
1411 value larger than 1, the type of the database will be omitted for more
1412 display space.</dd>
1416 <dd>Defines the tab displayed by default on server view. Possible
1423 <dd>Defines the tab displayed by default on database view. Possible
1428 <dd>Defines the tab displayed by default on table view. Possible
1435 points to the MySQL documentation (type depends
1436 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1437 generated.<br />
1439 for more information about MySQL manuals and their types.</dd>
1442 <dd>Type of MySQL documentation:
1448 </ul>
1449 </dd>
1452 <dd>Defines the default language to use, if not browser-defined or
1453 user-defined.<br />
1455 this setting.</dd>
1458 <dd>Defines the default connection collation to use, if not
1459 user-defined.<br />
1464 <dd>Force: always use this language (must be defined in the
1468 <dd>Limit list of available languages to those matching the given regular
1469 expression. For example if you want only Czech and English, you should
1473 <dd>Default character set to use for recoding of MySQL queries. This must be
1474 enabled and it's described by
1476 option.<br />
1477 You can give here any character set which is in
1479 array and this is just default choice, user can select any of them.</dd>
1482 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1483 support (compiled in or module) in PHP to allow MySQL queries recoding
1484 and used language file must have it enabled (by default only these
1485 which are in Unicode, just to avoid losing some characters).<br /><br />
1488 in the Export page, to choose the character set when exporting a file.
1489 </dd>
1492 <dd>You can select here which functions will be used for character set
1493 conversion. Possible values are:
1494 <ul><li>auto - automatically use available one (first is tested
1495 iconv, then recode)</li>
1498 </ul>
1499 Default is auto.</dd>
1502 <dd>Specify some parameters for iconv used in charset conversion. See
1505 used, so that invalid characters will be transliterated.</dd>
1508 <dd>Available character sets for MySQL conversion. You can add your own (any of
1509 supported by recode/iconv) or remove these which you don't use.
1510 Character sets will be shown in same order as here listed, so if you
1511 frequently use some of these move them to the top.</dd>
1516 default empty, you need to fill in some trusted proxy servers if you
1517 want to use rules for IP addresses behind proxy.<br /><br />
1519 The following example specifies that phpMyAdmin should trust a
1521 <pre>
1522 $cfg['TrustedProxies'] =
1524 </pre>
1525 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1526 client's IP address as usual.
1527 </dd>
1531 MIME transformations.<br />
1532 Possible values are:
1533 <ul><li>auto - automatically detect, this is a bit expensive
1535 according to your server real possibilities</li>
1538 </ul>
1539 Default is auto.
1540 </dd>
1544 </dd>
1546 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1547 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1548 </dt>
1549 <dd>The background styles used for both the frames.
1552 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1554 <dd>The style used for the pointer in the navi frame.
1558 <dd>The color used for the database name in the navi frame.
1567 </dd>
1571 <dd>The style used for table headers. See
1576 </dd>
1580 </dd>
1582 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1584 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1586 </dt>
1588 The former feature highlights the row over which your mouse is passing
1589 and the latter lets you visually mark/unmark rows by clicking on
1590 them.<br />
1595 <dd>You put here a valid CSS font family value, for example
1600 <dd>You put here a valid CSS font family value, for example
1614 </dt>
1616 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1618 The Char* values are used for CHAR and VARCHAR editing (if configured
1622 </dt>
1626 </dt>
1627 <dd>Defines if the whole textarea of the query box will be selected on
1628 click.</dd>
1631 </dt>
1632 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1633 editing.</dd>
1636 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1637 Can be turned off by a toggle button on the browse page.</dd>
1641 </dt>
1642 <dd>Defines the place where modify and delete links would be put when
1643 tables contents are displayed (you may have them displayed both at the
1644 left and at the right).
1650 </dt>
1652 Define which one is displayed by default. The first mode displays each
1653 row on a horizontal line, the second rotates the headers by 90
1654 degrees, so you can use descriptive headers even though fields only
1655 contain small values and still print them out. The vertical mode sorts
1656 each row on a vertical lineup.<br /><br />
1658 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1659 the rotation of the header for horizontalflipped is done via CSS. If
1660 set to 'fake' PHP does the transformation for you, but of course this
1661 does not look as good as CSS.</dd>
1665 string or integer</dt>
1666 <dd>When editing/creating new columns in a table all fields normally get
1667 lined up one field a line. (default: 'horizontal'). If you set this to
1668 'vertical' you can have each field lined up vertically beneath each
1669 other. You can save up a lot of place on the horizontal direction and
1670 no longer have to scroll. If you set this to integer, editing of fewer
1671 columns will appear in 'vertical' mode, while editing of more fields
1672 still in 'horizontal' mode. This way you can still effectively edit
1673 large number of fields, while having full view on few of them.</dd>
1677 </dt>
1679 display of column comments in Browse or Property display. In browse
1680 mode, the comments are shown inside the header. In property mode,
1681 comments are displayed using a CSS-formatted dashed-line below the
1682 name of the field. The comment is shown as a tool-tip for that field.
1683 </dd>
1695 <dd>Whether to display a link to validate a query in any SQL Query box.
1702 <dd>
1703 The name of the directory where
1705 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1706 are available under a drop-down box when you click the database or
1707 table name, then the Import tab.
1708 <br /><br />
1710 If you want different directory for each user, %u will be replaced
1711 with username.<br /><br />
1715 compressed formats is enabled).<br /><br />
1717 This feature is useful when your file is too big to be uploaded via
1719 uploads are disabled in PHP.<br /><br />
1721 Please note that if PHP is running in safe mode, this directory must
1722 be owned by the same user as the owner of the phpMyAdmin scripts.
1723 <br /><br />
1727 alternatives.
1728 </dd>
1731 <dd>
1732 The name of the directory where dumps can be saved.<br /><br />
1734 If you want different directory for each user, %u will be replaced
1735 with username.<br /><br />
1737 Please note that the directory must exist and has to be writable
1738 for the user running the webserver.<br /><br />
1740 Please note that if PHP is running in safe mode, this directory must
1741 be owned by the same user as the owner of the phpMyAdmin scripts.
1742 </dd>
1745 <dd>
1746 The name of the directory where temporary files can be stored.
1747 <br /><br />
1749 This is needed for native MS Excel export, see
1755 <br /><br />
1757 If the directory where phpMyAdmin is installed is subject to an
1759 temporary directory in some directory accessible by the web
1760 server. However for security reasons, this directory should be outside
1761 the tree published by webserver. If you cannot avoid having this
1762 directory published by webserver, place at least an empty
1764 possible.
1765 <br /><br />
1767 This directory should have as strict permissions as possible as the only
1768 user required to access this directory is the one who runs the
1769 webserver. If you have root privileges, simply make this user owner of
1770 this directory and make it accessible only by it:
1771 <br /><br />
1773 <pre>
1774 chown www-data:www-data tmp
1775 chmod 700 tmp
1776 </pre>
1778 If you cannot change owner of the directory, you can achieve a similar
1781 <pre>
1782 chmod 700 tmp
1783 setfacl -m "g:www-data:rwx" tmp
1784 setfacl -d -m "g:www-data:rwx" tmp
1785 </pre>
1787 If neither of above works for you, you can still make the directory
1789 system reading and writing data in this directory.
1790 </dd>
1793 <dd>
1794 In this array are defined default parameters for export, names of
1795 items are similar to texts seen on export page, so you can easily
1796 identify what they mean.
1797 </dd>
1800 <dd>
1801 In this array are defined default parameters for import, names of
1802 items are similar to texts seen on import page, so you can easily
1803 identify what they mean.
1804 </dd>
1807 <dd>
1808 Repeat the headers every X cells, or 0 to deactivate.
1809 </dd>
1817 </dt>
1818 <dd>
1819 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1820 or icon is always displayed on the left panel. If JavaScript is enabled in
1821 your browser, a click on this opens a distinct query window, which is
1822 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1823 changes to display a query box.<br /><br />
1825 The size of this query window can be customized with
1827 - both integers for the size in pixels. Note that normally, those
1829 theme you are using.<br /><br />
1833 opens the query window and puts the current query
1834 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1835 query in the right panel's query box.
1836 <br /><br />
1837 The usage of the JavaScript query window is recommended if you have a
1838 JavaScript enabled browser. Basic functions are used to exchange quite
1839 a few variables, so most 4th generation browsers should be capable to
1840 use that feature. It currently is only tested with Internet Explorer 6
1841 and Mozilla 1.x.
1842 <br /><br />
1844 to a table, which has to be created by you (see <a
1846 all your queries will be appended to the form, but only as long as
1847 your window is opened they remain saved.
1848 <br /><br />
1849 When using the JavaScript based query window, it will always get
1850 updated when you click on a new table/db to browse and will focus if
1851 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1852 the query window by checking the box "Do not overwrite this query from
1853 outside the window" below the query textarea. Then you can browse
1854 tables/databases in the background without losing the contents of the
1855 textarea, so this is especially useful when composing a query with
1856 tables you first have to look in. The checkbox will get automatically
1857 checked whenever you change the contents of the textarea. Please
1858 uncheck the button whenever you definitely want the query window to
1859 get updated even though you have made alterations.
1860 <br /><br />
1863 <br /><br />
1864 The query window also has a custom tabbed look to group the features.
1866 default tab to be used when opening the query window. It can be set to
1867 either 'sql', 'files', 'history' or 'full'.</dd>
1873 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1875 If the approximate row count as returned by
1878 count will be used.
1879 </dd>
1881 <dd>For VIEWs, since obtaining the exact count could have an
1882 impact on performance, this value is the maximum to be displayed, using
1884 any row counting.
1885 </dd>
1889 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1891 page. By clicking on the button 'toggle scratchboard' on the page
1892 where you edit x/y coordinates of those elements you can activate a
1893 scratchboard where all your elements are placed. By clicking on an
1894 element, you can move them around in the pre-defined area and the x/y
1895 coordinates will get updated dynamically. Likewise, when entering a
1896 new position directly into the input field, the new position in the
1897 scratchboard changes after your cursor leaves the input field.<br />
1898 You have to click on the 'OK'-button below the tables to save the new
1899 positions. If you want to place a new element, first add it to the
1900 table of elements and then you can drag the new element around.<br />
1901 By changing the paper size and the orientation you can change the size
1902 of the scratchboard as well. You can do so by just changing the
1903 dropdown field below, and the scratchboard will resize automatically,
1904 without interfering with the current placement of the elements.<br />
1905 If ever an element gets out of range you can either enlarge the paper
1906 size or click on the 'reset' button to place all elements below each
1907 other.<br />
1909 get this control to work. The basic Drag&Drop script functionality
1910 was kindly borrowed from www.youngpup.net and is underlying so
1911 specific license.</dd>
1914 <dd>Sorts database and table names according to natural order (for example,
1915 t1, t2, t10). Currently implemented in the left panel (Light mode)
1916 and in Database view, for the table list.</dd>
1922 <dd>Allows you to specify window's title bar. Following magic string can
1923 be used to get special values:
1924 <dl>
1930 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1939 </dl>
1940 </dd>
1950 </dd>
1953 <dd>If theme manager is active, use this as the path of the subdirectory
1954 containing all the themes.</dd>
1968 </dt>
1969 <dd>Default queries that will be displayed in query boxes when user didn't
1970 specify any. Use %d for database name, %t for table name and %f for a
1971 comma separated list of field names. Note that %t and %f are only
1975 <dd>
1976 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
1977 default we use HTML to format the query, but you can disable this by
1979 </dd>
1982 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1983 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1984 query inside a bracket is indented. By changing
1987 specifies the units of the indent amount that you specified. This is
1988 used via stylesheets.</dd>
1991 <dd>This array is used to define the colours for each type of element of
1992 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1994 If you specify an empty string for the color of a class, it is ignored
1995 in creating the stylesheet.
1996 You should not alter the class names, only the colour strings.<br />
2017 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2021 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2022 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2023 </ul>
2024 </dd>
2028 <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,
2029 as originally published on
2031 <br />
2032 For help in setting up your system to use the service, see the
2034 </dd>
2038 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2039 and any password, so we use those by default. Instead, if
2040 you have an account with them, you can put your login details
2041 here, and it will be used in place of the anonymous login.</dd>
2042 </dl>
2043 </dd>
2046 <dd><b>DEVELOPERS ONLY!</b></dd>
2049 <dd><b>DEVELOPERS ONLY!</b><br />
2050 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2051 the code.<br />
2052 For help in setting up your system to this, see the
2056 <dd><b>DEVELOPERS ONLY!</b><br />
2057 Enable profiling support for phpMyAdmin. This will append a chunk of data
2058 to the end of every page displayed in the main window with profiling
2059 statistics for that page.<br />
2060 You may need to increase the maximum execution time for this to
2061 complete successfully.<i>Profiling was removed from the code for
2062 version 2.9.0 due to licensing issues.</i></dd>
2064 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2065 <dd><b>DEVELOPERS ONLY!</b><br />
2066 When profiling data is displayed, this variable controls the threshold of
2067 display for any profiling data, based on the average time each time has
2068 taken. If it is over the threshold it is displayed, otherwise it is not
2069 displayed. This takes a value in milliseconds. In most cases you don't need
2070 to edit this.</dd>
2073 <dd>All possible types of a MySQL column. In most cases you don't need to
2074 edit this.</dd>
2077 <dd>Possible attributes for fields. In most cases you don't need to edit
2078 this.</dd>
2081 <dd>A list of functions MySQL supports. In most cases you don't need to
2082 edit this.</dd>
2085 <dd>Mapping of column types to meta types used for preferring displayed
2086 functions. In most cases you don't need to edit this.</dd>
2089 <dd>Functions preferred for column meta types as defined in
2090 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2091 to edit this.</dd>
2094 <dd>Functions selected by default when inserting/changing row, Functions
2095 are defined for meta types from
2097 <code>first_timestamp</code>, which is used for first timestamp column
2098 in table.</dd>
2101 <dd>Operators available for search operations on numeric and date fields.
2102 </dd>
2105 <dd>Operators available for search operations on character fields.
2106 Note that we put <code>LIKE</code> by default instead of
2107 <code>LIKE %...%</code>, to avoid unintended performance problems
2108 in case of huge tables.</dd>
2111 <dd>Operators available for search operations on enum fields.</dd>
2114 <dd>Additional operators available for search operations when the
2115 field can be null.</dd>
2117 </dl>
2119 <!-- TRANSFORMATIONS -->
2125 </ol>
2129 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2131 section</a> on how to do so.</p>
2133 <p> You can apply different transformations to the contents of each field. The
2134 transformation will take the content of each field and transform it with
2135 certain rules defined in the selected transformation.</p>
2137 <p> Say you have a field 'filename' which contains a filename. Normally you would
2138 see in phpMyAdmin only this filename. Using transformations you can transform
2139 that filename into a HTML link, so you can click inside of the phpMyAdmin
2140 structure on the field's link and will see the file displayed in a new browser
2141 window. Using transformation options you can also specify strings to
2142 append/prepend to a string or the format you want the output stored in.</p>
2144 <p> For a general overview of all available transformations and their options,
2145 you can consult your
2146 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2147 installation.</p>
2149 <p> For a tutorial on how to effectively use transformations, see our
2151 the official phpMyAdmin homepage.</p>
2155 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2156 clicking on the 'Structure' link for a table). There click on
2157 "Change" (or change icon) and there you will see three new fields at
2158 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2159 'Transformation options'.</p>
2161 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2162 that corresponds to the column's contents. Please note that
2163 transformations are inactive as long as no MIME-type is selected.</li>
2165 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2166 hopefully growing amount of pre-defined transformations. See below for information on
2167 how to build your own transformation.<br />
2169 There are global transformations and mimetype-bound transformations. Global transformations
2170 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2171 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2172 transformations which operate on the main mimetype (like 'image'), which will most likely
2173 take the subtype into regard, and those who only operate on a
2174 specific subtype (like 'image/jpeg').<br />
2176 You can use transformations on mimetypes for which the function was not defined for. There
2177 is no security check for you selected the right transformation, so take care of what the
2178 output will be like.</li>
2180 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2181 transform-function specific options here. Usually the transforms can operate with default
2182 options, but it is generally a good idea to look up the overview to see which options are
2183 necessary.<br />
2185 Much like the ENUM/SET-Fields, you have to split up several options using the format
2186 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2187 parsed as an array, leaving the first value the first element in the array, and so
2188 forth.<br />
2190 If you want to specify a MIME character set you can define it in the transformation_options.
2191 You have to put that outside of the pre-defined options of the specific mime-transform,
2193 for which you can specify 2 options and you want to append a character set, enter "'first
2194 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2196 </ul>
2200 <p> All mimetypes and their transformations are defined through single files in
2201 the directory 'libraries/transformations/'.</p>
2203 <p> They are stored in files to ease up customization and easy adding of new
2204 transformations.</p>
2206 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2207 always work. It makes no sense to apply a transformation to a mimetype, the
2208 transform-function doesn't know to handle.</p>
2210 <p> One can, however, use empty mime-types and global transformations which should work
2211 for many mimetypes. You can also use transforms on a different mimetype they where built
2212 for, but pay attention to option usage as well as what the transformation does to your
2213 field.</p>
2215 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2216 any other transform function and provides some basic functions.</p>
2218 <p> There are 5 possible file names:</p>
2220 <ol><li>A mimetype+subtype transform:<br /><br />
2222 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2224 Please not that mimetype and subtype are separated via '_', which shall
2225 not be contained in their names. The transform function/filename may
2226 contain only characters which cause no problems in the file system as
2227 well as the PHP function naming convention.<br /><br />
2229 The transform function will the be called
2230 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2232 <b>Example:</b><br /><br />
2234 <tt>text_html__formatted.inc.php</tt><br />
2235 <tt>PMA_transform_text_html__formatted()</tt></li>
2237 <li>A mimetype (w/o subtype) transform:<br /><br />
2239 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2241 Please note that there are no single '_' characters.
2242 The transform function/filename may contain only characters which cause
2243 no problems in the file system as well as the PHP function naming
2244 convention.<br /><br />
2246 The transform function will the be called
2247 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2249 <b>Example:</b><br /><br />
2251 <tt>text__formatted.inc.php</tt><br />
2252 <tt>PMA_transform_text__formatted()</tt></li>
2254 <li>A mimetype+subtype without specific transform function<br /><br />
2256 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2258 Please note that there are no '__' characters in the filename. Do not
2259 use special characters in the filename causing problems with the file
2260 system.<br /><br />
2262 No transformation function is defined in the file itself.<br /><br />
2264 <b>Example:</b><br /><br />
2266 <tt>text_plain.inc.php</tt><br />
2267 (No function)</li>
2269 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2271 <tt>[mimetype].inc.php</tt><br /><br />
2273 Please note that there are no '_' characters in the filename. Do not use
2274 special characters in the filename causing problems with the file system.
2275 <br /><br />
2277 No transformation function is defined in the file itself.<br /><br />
2279 <b>Example:</b><br /><br />
2281 <tt>text.inc.php</tt><br />
2282 (No function)</li>
2284 <li>A global transform function with no specific mimetype<br /><br />
2286 <tt>global__[transform].inc.php</tt><br /><br />
2288 The transform function will the be called
2289 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2291 <b>Example:</b><br /><br />
2293 <tt>global__formatted</tt><br />
2294 <tt>PMA_transform_global__formatted()</tt></li>
2295 </ol>
2297 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2298 transform function.</p>
2300 <p> All filenames containing no '__' in themselves are not shown as valid transform
2301 functions in the dropdown.</p>
2303 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2304 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2305 without a transform function. Also note the introduction of a function description in
2306 the language files. For each function a $strTransformation_[filename without .inc.php]
2307 has to exist.</p>
2309 <p> You can use the template generator to generate new functions and entries in the
2310 language file.</p>
2312 <p> To create a new transform function please see
2313 <tt>libraries/transformations/template_generator.sh</tt>.
2314 To create a new, empty mimetype please see
2315 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2317 <p> A transform function always gets passed three variables:</p>
2319 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2320 you want to transform.</li>
2321 <li><b>$options</b> - Contains any user-passed options to a transform function
2322 as an array.</li>
2323 <li><b>$meta</b> - Contains an object with field information to your column.
2324 The data is drawn from the output of the
2326 function. This means, all object properties described on the
2328 available in this variable and can be used to transform a field accordingly
2329 to unsigned/zerofill/not_null/... properties.<br />
2330 The $meta->mimetype variable contains the original MIME-type of the
2331 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2332 </ol>
2334 <!-- FAQ -->
2341 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2345 </ol>
2347 <p> Please have a look at our
2349 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2350 features and or interface.</p>
2356 action is required or phpMyAdmin sends a blank page or a page full of
2357 cryptic characters to my browser, what can I do?</a></h4>
2359 <p> There are some known PHP bugs with output buffering and compression.<br />
2361 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2362 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2363 configuration file.<br />
2364 Furthermore, we know about such problems connected to the release
2365 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2366 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2371 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2372 See also the
2374 entry about PHP bugs with output buffering.<br />
2375 If your server keeps crashing, please ask for help in the various Apache
2376 support groups.</p>
2380 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2381 script: I'm always displayed the login screen.</a></h4>
2383 <p> This is a known PHP bug (see this
2385 official PHP bug database. It means there is and won't be any phpMyAdmin
2386 fix against it because there is no way to code a fix.</p>
2392 application misbehaved by not returning a complete set of
2394 </h4>
2396 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2397 Have a look at the last message in this
2399 official PHP bug database.</p>
2404 and/or many error messages with the
2406 mode.</a></h4>
2408 <p> This is a known problem with the PHP
2410 filter: it's not so stable. Please use instead the cookie authentication mode.
2411 </p>
2416 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2417 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2418 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2419 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2420 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2425 work.</a></h4>
2427 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2428 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2429 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2430 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2431 We faced PHP crashes when trying to download a dump with MS Internet
2432 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2433 this case you should switch to the release version of PHP 4.2.0.</p>
2437 an error about safe mode being in effect.</a></h4>
2439 <p> Your uploaded file is saved by PHP in the "upload dir", as
2440 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2441 the system default is <i>/tmp</i>).<br />
2442 We recommend the following setup for Apache servers running in safe mode,
2443 to enable uploads of files while being reasonably secure:</p>
2445 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2446 <li>give ownership to the Apache server's user.group:
2447 <tt>chown apache.apache /tmp/php</tt></li>
2448 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2449 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2450 <li>restart Apache</li>
2451 </ul>
2455 general file uploads don't work on my system and uploaded files have a
2456 <tt>Content-Type:</tt> header in the first line.</a></h4>
2458 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2459 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2460 So the problem is that this package has a serious bug that was corrected
2461 ages ago in PHP (2001-01-28: see
2463 for more details). The problem is that the bugged package is still
2464 available though it was corrected (see
2466 for more details).<br />
2467 So please download
2468 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2469 and the problem should go away.<br />
2470 And that fixes the \r\n problem with file uploads!</p>
2474 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2475 I'm using the Apache server.</a></h4>
2477 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2478 your <i>httpd.conf</i>:</p>
2482 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2486 uploading a file from the query box.</a></h4>
2488 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2489 restrictions. However you need to create temporary directory and
2491 The uploaded files will be moved there, and after execution of your
2497 <p> The MySQL manual explains how to
2499 reset the permissions</a>.</p>
2504 execute a bookmark.</a></h4>
2506 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2507 cannot access the uploaded query.</p>
2512 submit a query from the convenient text area.</a></h4>
2514 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2515 and try to increase it.</p>
2519 </h4>
2521 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2522 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2523 names to align with current standards.</p>
2528 </h4>
2530 <p> Starting with version 2.7.0, the import engine has been re–written and these
2531 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2532 to take advantage of the new import features.</p>
2534 <p> The first things to check (or ask your host provider to check) are the
2535 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2536 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2537 All of these three settings limit the maximum size of data that can be
2538 submitted and handled by PHP. One user also said that post_max_size
2539 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2541 There exist several workarounds if your upload is too big or your
2542 hosting provider is unwilling to change the settings:</p>
2545 feature. This allows one to
2546 upload a file to the server via scp, ftp, or your favorite file transfer
2547 method. PhpMyAdmin is then able to import the files from the temporary
2549 section</a> of this document.</li>
2551 BigDump</a>) to split the files before uploading. We cannot support this
2552 or any third party applications, but are aware of users having success
2553 with it.</li>
2554 <li>If you have shell (command line) access, use MySQL to import the files
2555 directly. You can do this by issuing the "source" command from
2556 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2557 </ul>
2561 support?</a></h4>
2563 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2564 fully supported. Please note that the older your MySQL version is, the more
2565 limitations you will have to face.<br />
2566 phpMyAdmin may connect to your MySQL server using php's classic
2569 is available in php 5.0.<br />
2570 Either way, the developers of both extensions recommend to use the classic
2571 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2572 When compiling php, we strongly recommend that you manually link the MySQL
2573 extension of your choice to a MySQL client library of at least the same
2574 minor version since the one that is bundled with some php distributions is
2577 If your webserver is running on a windows system, you might want to try
2578 MySQL's
2580 instead of the MySQL / MySQLi extensions that are bundled with the official
2581 php Win32 builds.
2582 <br />
2583 MySQL 5.1 is not yet supported.</p>
2587 message, "Client does not support authentication protocol requested
2588 by server; consider upgrading MySQL client"</a></h5>
2590 <p> You tried to access MySQL with an old MySQL client library. The version of
2591 your MySQL client library can be checked in your phpinfo() output.
2592 In general, it should have at least the same minor version as your server
2596 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2597 changed the authentication hash and your PHP is trying to use the old method.
2599 with the proper client library to match your MySQL installation. Your
2600 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2601 More information (and several workarounds) are located in the
2603 </p>
2607 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2608 capital letter in its name it is changed to lowercase as it should. But
2609 if I try to DROP this table MySQL is unable to find the corresponding
2610 file.</a></h4>
2612 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2613 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2614 directive.</p>
2618 script seems not to know the font face I'm using!</a></h4>
2620 <p> The "FPDF" library we're using for this feature requires some
2621 special files to use font faces.<br />
2623 these files.</p>
2627 check PHP Configuration".</a></h4>
2629 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2630 "MySQL extension". This extension may be part of the PHP
2631 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2632 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2633 to load the extension but failed.<br /><br />
2635 Usually, the problem is solved by installing a software package called
2636 "PHP-MySQL" or something similar.</p>
2641 and I cannot log in using cookie auth.</a></h4>
2643 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2647 so I cannot upload.</a></h4>
2649 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2650 parameter is not set to "on".</p>
2654 a new table the table and field names are changed to lowercase!</a></h4>
2656 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2657 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2658 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2659 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2660 directory and add the following line to the group [mysqld]:</p>
2662 <pre>set-variable = lower_case_table_names=0</pre>
2664 <p> Next, save the file and restart the MySQL service. You can always check the
2665 value of this directive using the query</p>
2667 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2671 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2674 </p>
2678 and I get problems, such as undefined variables when I run a
2681 <p> A tip from Jose Fandos: put a comment on the following two lines
2682 in httpd.conf, like this:</p>
2684 <pre>
2685 # mod_gzip_item_include file \.php$
2687 </pre>
2689 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2690 PHP scripts. Of course you have to restart Apache.</p>
2695 I get the error "No input file specified" when trying to
2696 run phpMyAdmin.</a></h4>
2698 <p> This is a permission problem. Right-click on the phpmyadmin folder
2699 and choose properties. Under the tab Security, click on "Add"
2700 and select the user "IUSR_machine" from the list. Now set his
2701 permissions and it should work.</p>
2705 db_structure.php with plenty of tables).</a></h4>
2708 GZIP output buffering is enabled. If you turn off it (by
2710 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2711 PHP 5.0.0.</p>
2715 message 'Errorcode: 13'. What does this mean?</a></h4>
2717 <p> This can happen due to a MySQL bug when having database / table names with
2718 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2719 To fix this, turn off this directive, convert all database and table names
2720 to lower case and turn it on again. Alternatively, there's a bug-fix
2721 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2725 and the fields are duplicated.</a></h4>
2727 <p> It is possible to configure Apache in such a way that PHP has problems
2728 interpreting .php files.</p>
2730 <p> The problems occur when two different (and conflicting) set of directives
2731 are used:</p>
2733 <pre>
2734 SetOutputFilter PHP
2735 SetInputFilter PHP
2736 </pre>
2738 <p> and</p>
2740 <pre>AddType application/x-httpd-php .php</pre>
2742 <p> In the case we saw, one set of directives was in
2743 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2744 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2745 The recommended way is with <tt>AddType</tt>, so just comment out
2746 the first set of lines and restart Apache:</p>
2748 <pre>
2749 #SetOutputFilter PHP
2750 #SetInputFilter PHP
2751 </pre>
2756 <p> This problem is known to happen when the server is running Turck MMCache
2757 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2762 <p> Yes.<br />
2763 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2764 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2765 <tt>error_reporting</tt> settings.
2766 </p>
2769 <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>
2771 <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>
2774 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2775 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2776 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2777 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2778 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2779 enabled.) Click <tt>OK</tt>.</li>
2780 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2781 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2782 </ol>
2786 PHP 5.0.4 on 64-bit systems?</a></h4>
2788 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2789 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2795 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
2796 the order of the server paragraph in <tt>config.inc.php</tt>.
2797 Table and script parts are optional. If you want
2798 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2799 some configuration. Following lines apply only for <a
2801 that you have enabled some features within global configuration. You need
2802 <code>Options FollowSymLinks</code> and <code>AllowOverride
2803 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2804 you need mod_rewrite to be enabled. Then you just need to create following
2805 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2806 (don't forget to change directory name inside of it):</p>
2808 <pre>
2809 RewriteEngine On
2810 RewriteBase /path_to_phpMyAdmin
2811 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2812 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2813 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2814 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2815 </pre>
2818 <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>
2820 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2821 following rewrite rule:</p>
2823 <pre>
2824 RewriteEngine On
2825 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2826 </pre>
2830 </h4>
2831 <p>
2832 There can be many explanations to this and a look at your server's
2833 error log file might give a clue.
2834 </p>
2838 password encryption in cookie auth doesn't work.</a></h4>
2840 <p> If your cluster consist of different architectures, PHP code used for
2841 encryption/decryption won't work correct. This is caused by use of
2842 pack/unpack functions in code. Only solution is to use mcrypt extension
2843 which works fine in this case.</p>
2848 <p> Yes but the default configuration values of Suhosin are known to cause
2849 problems with some operations, for example editing a table with many
2850 columns and no primary key. Tuning information is available at
2852 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2853 although the parameter names have changed (<tt>suhosin</tt> instead
2855 <tt>SuhosinDisableWarning</tt> directive</a>.
2856 </p>
2862 headers already sent by ..." is displayed, what's the problem?</a></h4>
2864 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2865 (I.E. no blank lines, no spaces, no characters...) neither before the
2866 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2867 tag at the end. We also got a report from a user under IIS, that used
2868 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2869 contained an end-of-line character (hex 0A) at the end; removing this character
2870 cleared his errors.</p>
2875 <p> Either there is an error with your PHP setup or your username/password is
2876 wrong. Try to make a small script which uses mysql_connect and see if it
2877 works. If it doesn't, it may be you haven't even compiled MySQL support
2878 into PHP.</p>
2882 connect to local MySQL server through socket '/tmp/mysql.sock'
2883 (111) ..." is displayed. What can I do?</a></h4>
2885 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2887 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2888 In your <i>php.ini</i> you will find a line</p>
2890 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2892 <p> change it to</p>
2894 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2896 <p> Then restart apache and it will work.</p>
2898 <p> Here is a fix suggested by Brad Ummer:</p>
2900 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2901 To do this, telnet to your server and go to the MySQL bin directory. In
2902 this directory there should be a file named <i>mysqladmin</i>. Type
2903 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2904 info about your MySQL server, including the socket
2905 (<i>/tmp/mysql.sock</i>, for example).</li>
2906 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2907 phpMyAdmin, you need to complete the socket information in the
2908 <i>config.inc.php</i>.<br />
2909 For example:
2911 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2912 <br /><br />
2914 Please also make sure that the permissions of this file allow to be readable
2915 by your webserver (i.e. '0755').</li>
2916 </ul>
2918 <p> Have also a look at the
2920 corresponding section of the MySQL documentation</a>.</p>
2924 what can I do?</a></h4>
2927 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2928 sometime.<br />
2929 Also have a look at your PHP version number: if it contains "4.0b..."
2930 it means you're running a beta version of PHP. That's not a so good idea,
2931 please upgrade to a plain revision.</p>
2935 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2936 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2938 <p> Check the value you set for the
2940 directive in the phpMyAdmin configuration file.</p>
2944 password: YES)"-error when trying to access a MySQL-Server on a
2945 host which is port-forwarded for my localhost.</a></h4>
2947 <p> When you are using a port on your localhost, which you redirect via
2948 port-forwarding to another host, MySQL is not resolving the localhost
2949 as expected.<br />
2950 Erik Wasser explains: The solution is: if your host is "localhost"
2951 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2952 connection for speeding up things. And that doesn't work in this configuration
2953 with port forwarding.<br />
2959 <p> Themes are configured with
2963 <br />
2965 should not delete the directory "original" or its underlying
2966 structure, because this is the system theme used by phpMyAdmin.
2967 "original" contains all images and styles, for backwards
2968 compatibility and for all themes that would not include images or css-files.
2969 <br /><br />
2972 is enabled, you can select your favorite theme on the main page. Your
2973 selected theme will be stored in a cookie.<br /><br /></p>
2975 <p> To create a theme:</p>
2977 <ul><li>make a new subdirectory (for example "your_theme_name") under
2979 (by default <tt>themes</tt>)</li>
2980 <li>copy the files and directories from "original" to
2981 "your_theme_name"</li>
2982 <li>edit the css-files in "your_theme_name/css"</li>
2983 <li>put your new images in "your_theme_name/img"</li>
2984 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2985 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2986 contain your chosen theme name, that will be visible in user interface</li>
2987 <li>make a new screenshot of your theme and save it under
2988 "your_theme_name/screen.png"</li>
2989 </ul>
2991 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2992 theme verbose name, theme generation and theme version. These versions and
2993 generations are enumerated from 1 and do not have any direct dependence on
2994 phpMyAdmin version. Themes within same generation should be backwards
2995 compatible - theme with version 2 should work in phpMyAdmin requiring
2996 version 1. Themes with different generation are incompatible.</p>
2998 <p> If you do not want to use your own symbols and buttons, remove the
2999 directory "img" in "your_theme_name". phpMyAdmin will
3000 use the default icons and buttons (from the system-theme "original").
3001 </p>
3005 what can I do?</a></h4>
3007 <p> Here are a few points to check:</p>
3009 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3011 directive empty. See also
3013 </li>
3014 <li>Maybe you have a broken PHP installation or you need to upgrade
3015 your Zend Optimizer. See
3017 http://bugs.php.net/bug.php?id=31134</a>.
3018 </li>
3019 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3020 set to the default (200) or another low value, you could get this
3021 error if your table has a high number of columns. Adjust this setting
3022 accordingly. (Thanks to Klaus Dorninger for the hint).
3023 </li>
3024 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3025 of ";" will cause this error. Replace it with "&;".
3026 </li>
3028 you might want to increase
3030 </li>
3031 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3032 </li>
3033 </ul>
3040 who logged out can not log in again in with the same nick.</a></h4>
3042 <p> This is related to the authentication mechanism (protocol) used by
3043 phpMyAdmin. To bypass this problem: just close all the opened
3044 browser windows and then go back to phpMyAdmin. You should be able to
3045 log in again.</p>
3049 limit error or a time limit error.</a></h4>
3051 <p> Compressed dumps are built in memory and because of this are limited to
3052 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3053 using
3055 (enabled by default). Zip exports can not be handled this way, so if you need
3056 Zip files for larger dump, you have to use another way.</p>
3060 or alter a table.</a></h4>
3062 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3066 bundled with the MySQL server distribution.</a></h4>
3068 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3070 <pre>
3071 -- MySQL dump 8.22
3072 --
3073 -- Host: localhost Database: database
3074 ---------------------------------------------------------
3075 -- Server version 3.23.54
3076 </pre>
3078 <p> The invalid part of the code is the horizontal line made of dashes that
3079 appears once in every dump created with mysqldump. If you want to run your
3080 dump you have to turn it into valid MySQL. This means, you have to add a
3081 whitespace after the first two dashes of the line or add a # before it:
3082 <br />
3083 <code>
3084 -- -------------------------------------------------------<br />
3085 </code>
3086 or<br />
3087 <code>
3088 #---------------------------------------------------------
3089 </code>
3090 </p>
3097 <p> Please note that you should not use the separating string multiple times
3098 without any characters between them, or at the beginning/end of your table
3099 name. If you have to, think about using another TableSeparator or disabling
3100 that feature</p>
3105 <p> In Relation view, being able to choose a table in another database,
3106 or having more than one index field in the foreign key.<br /><br/>
3107 In Query-by-example (Query), automatic generation of the query
3108 LEFT JOIN from the foreign table.<br /><br/>
3109 </p>
3113 I get series of errors like "Warning: unable to parse url". How
3114 can this be fixed?</a></h4>
3115 <p>
3116 Your table neither have a primary key nor an unique one, so we must use a
3117 long expression to identify this row. This causes problems to parse_url
3118 function. The workaround is to create a primary or unique key.
3119 <br />
3120 </p>
3124 a MIME-Transformation onto!</a></h4>
3126 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3127 nested forms can be put inside the table where phpMyAdmin displays the results.
3128 You can, however, use any form inside of a table if keep the parent
3129 form-container with the target to tbl_row_delete.php and just put your own
3130 input-elements inside. If you use a custom submit input field, the form will
3131 submit itself to the displaying page again, where you can validate the
3132 $HTTP_POST_VARS in a transformation.
3134 For a tutorial on how to effectively use transformations, see our
3136 on the official phpMyAdmin-homepage.</p>
3140 MySQL server</a></h4>
3142 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3145 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3146 the quote-character (") is interpreted as an identifier quote character and
3147 not as a string quote character, which makes many internal phpMyAdmin
3149 statements. There is no workaround to this behaviour. News to this item will
3150 be posted in Bug report
3151 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3152 </p>
3156 more that one column with the same value
3157 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3158 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3160 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3161 can use it for the Edit and Delete links.</p>
3166 <p> phpMyAdmin uses a quick method to get the row count, and this method
3167 only returns an approximate count in the case of InnoDB tables. See
3169 a way to modify those results, but
3170 this could have a serious impact on performance.</p>
3175 <p> The number of records in queries containing COUNT and GROUP BY is
3176 not correctly calculated. Also, sorting results of a query like
3181 containing an hyphen.
3182 </a></h4>
3183 <p>
3184 The tests I have made with current MySQL 4.1.11 API shows that the
3185 API does not accept this syntax for the USE command. Enclosing the
3186 db name with backquotes works. For further confusion, no backquotes
3187 are needed with command-line mysql.
3188 </p>
3191 <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>
3192 <p>
3193 This has been a known limitation of phpMyAdmin since the beginning and
3194 it's not likely to be solved in the future.
3195 </p>
3197 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3200 <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
3201 need to install it for each customer.
3202 </a></h4>
3203 <p>
3204 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3205 your users. The development of this feature was kindly sponsored by
3206 NetCologne GmbH.
3207 This requires a properly setup MySQL user management and phpMyAdmin
3208 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3210 </p>
3214 access.
3215 </a></h4>
3216 <p>
3217 This depends on your system.<br />
3218 If you're running a server which cannot be accessed by other people, it's
3219 sufficient to use the directory protection bundled with your webserver
3221 If other people have telnet access to your server, you should use
3222 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3223 <br /><br />
3224 Suggestions:
3225 </p>
3226 <ul>
3227 <li>
3229 </li>
3230 <li>
3231 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3232 is a user whose password is only known to you, and apache is the
3233 group under which Apache runs.
3234 </li>
3235 <li>
3236 You should use PHP safe mode, to protect from other users that try
3238 </li>
3239 </ul>
3244 </a></h4>
3245 <p>
3250 </p>
3253 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3254 authentication.
3255 </a></h4>
3259 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3260 and/or
3262 are wrong.</li>
3264 <li>You have already setup a security mechanism for the
3265 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3266 phpMyAdmin's authentication, so remove it.</li>
3267 </ul>
3274 and put the privileges you want. For example,
3276 would let a user create/manage his/her database(s).</p>
3281 <p> If you have existing rules from an old .htaccess file, you can take them
3284 be a major benefit here if your installation is suited to using it. Then
3285 you can just add those updated lines into the
3289 <p> If you want a pre-made sample, you can try this fragment. It stops the
3290 'root' user from logging in from any networks other than the private
3293 <pre>
3294 //block root from logging in except from the private networks
3295 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3296 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3297 'deny root from all',
3298 'allow root from localhost',
3302 );
3303 </pre>
3308 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3309 different than the one set in your
3311 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3312 while a domain name is defined in the config file.</p>
3317 <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>
3323 when trying to create a table with more than 14 fields.
3324 </a></h4>
3325 <p>
3326 We could reproduce this problem only under Win98/98SE. Testing under
3327 WinNT4 or Win2K, we could easily create more than 60 fields.
3328 <br />
3329 A workaround is to create a smaller number of fields, then come back to
3330 your table properties and add the other fields.
3331 </p>
3335 <p>
3336 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3337 with each script/website that use forms.<br />
3338 Upgrade or downgrade your Xitami server.
3339 </p>
3342 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3343 <p>
3344 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3345 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3346 don't seem to work.<br />
3348 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3349 the user's temporary directory, so they must be moved before closing
3350 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3353 </p>
3357 Explorer never stores the cookies.
3358 </a></h4>
3359 <p>
3360 MS Internet Explorer seems to be really buggy about cookies, at least till
3362 in this area!
3363 <br />
3364 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3365 work!
3366 </p>
3370 rows.
3371 </a></h4>
3372 <p>
3374 </p>
3377 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3378 when trying to modify a row in a table with many fields, or with a text field
3379 </a></h4>
3380 <p>
3381 Your table neither have a primary key nor an unique one, so we must use a
3382 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
3383 those browsers, and this not happen in Netscape, for example. The
3384 workaround is to create a primary or unique key, or use another browser.
3385 <br />
3386 </p>
3390 page.
3391 </a></h4>
3392 <p>
3393 Some browsers support right-clicking into the frame you want to refresh,
3394 just do this in the right frame.<br />
3395 </p>
3399 query box.
3400 </a></h4>
3401 <p>
3402 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3403 Mozilla versions.<br />
3404 </p>
3408 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3409 </a></h4>
3410 <p>
3411 This is a Mozilla bug (see bug #26882 at
3413 </p>
3418 </a></h4>
3419 <p>
3420 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3421 data in octet-stream mode. Since we can't detect the specific Netscape
3422 version, we cannot workaround this bug.
3423 </p>
3427 wrong.</a></h4>
3429 <p> Please ensure that you have set your browser's character set to the one of the
3430 language file you have selected on phpMyAdmin's start page.
3431 Alternatively, you can try the auto detection mode that is supported by the
3432 recent versions of the most browsers.</p>
3435 <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
3438 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3439 Netscape and Mozilla do not have this problem.</p>
3442 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3443 I cannot manage two servers: I log in to the first one, then the other one,
3444 but if I switch back to the first, I have to log in on each operation.</a></h4>
3450 but nothing happens after that, only a blank screen.</a></h4>
3453 bug in Opera6, because it is not able to interpret frameset definitions
3454 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3455 Opera7 at least.</p>
3464 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3469 address and you are starting
3471 containing a domain name, or the reverse situation.</li>
3472 <li>Security settings in IE and/or Microsoft Security Center are
3473 too high, thus blocking scripts execution.</li>
3474 <li>The Windows Firewall is blocking Apache and MySQL. You must
3478 </ul>
3481 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3482 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3483 installed in their Firefox is causing the problem.</p>
3490 </a></h4>
3491 <p>
3492 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3493 specifying a wrong field-type.<br />
3494 Common errors include:
3495 </p>
3496 <ul>
3499 </ul>
3500 <p>
3501 Also, look at the syntax chapter in the MySQL manual to confirm that your
3502 syntax is correct.
3503 </p>
3507 phpMyAdmin generates only one index with those 2 fields.
3508 </a></h4>
3509 <p>
3511 index. If you want two indexes, create the first one when creating the
3512 table, save, then display the table properties and click the Index link to
3513 create the other index.
3514 </p>
3518 <p>
3519 Since version 2.2.3, you have a checkbox for each field that can be null.
3521 field's value. Since version 2.5.5, you have to use the checkbox to get
3523 a literal NULL in the field, and not a NULL value (this works in PHP4).
3524 </p>
3529 <p> Click on a database or table name in the left frame, the properties will be
3531 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3532 statements that can be used to recreate your database/table.
3533 <br /><br />
3535 transmit the resulting dump to your station. Depending on your PHP
3536 configuration, you will see options to compress the dump. See also the
3538 configuration variable.<br /><br />
3541 this document.</p>
3546 </a></h4>
3548 <p> Click on a database name in the left frame, the properties will be
3550 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3552 the path to your dump filename, or use the Browse button. Then click Go.
3553 <br /><br />
3555 that you upgrade to take advantage of the new features.
3556 <br /><br />
3558 in this document.
3559 </p>
3564 <p> Here is an example with the tables persons, towns and countries, all
3566 table, create it as explained in the configuration section. Then create the
3567 example tables:</p>
3569 <pre>
3570 CREATE TABLE REL_countries (
3571 country_code char(1) NOT NULL default '',
3572 description varchar(10) NOT NULL default '',
3573 PRIMARY KEY (country_code)
3574 ) TYPE=MyISAM;
3576 INSERT INTO REL_countries VALUES ('C', 'Canada');
3578 CREATE TABLE REL_persons (
3579 id tinyint(4) NOT NULL auto_increment,
3580 person_name varchar(32) NOT NULL default '',
3582 country_code char(1) NOT NULL default '',
3583 PRIMARY KEY (id)
3584 ) TYPE=MyISAM;
3586 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3587 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3589 CREATE TABLE REL_towns (
3591 description varchar(30) NOT NULL default '',
3592 PRIMARY KEY (town_code)
3593 ) TYPE=MyISAM;
3595 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3596 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3597 </pre>
3603 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3607 </ul>
3615 <li>In the fields row, choose persons.person_name and click the
3617 <li>Do the same for towns.description and countries.descriptions in the
3620 the correct joins have been generated</li>
3622 </ul>
3626 <p>
3627 Starting from the previous example, create the pma_table_info as explained
3628 in the configuration section, then browse your persons table,
3629 and move the mouse over a town code or country code.
3630 <br /><br />
3631 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3632 enables: drop-down list of possible values.
3633 </p>
3636 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3637 <p>
3640 <br /><br />
3641 Then you need to think about your schema layout. Which tables will go on
3642 which pages?
3643 </p>
3644 <ul>
3650 page and click Go. If you like, you
3652 linked tables onto the new page.</li>
3653 <li>Select the name of the new page (making sure the Edit radio button
3654 is selected) and click Go.</li>
3656 Coordinates are relative; your diagram will
3657 be automatically scaled to fit the page. When initially placing tables
3658 on the page, just pick any coordinates -- say, 50x50. After clicking
3660 position the element correctly.</li>
3662 first be sure to click the Save
3663 button beneath the list of tables and coordinates, to save any changes
3664 you made there. Then scroll all the way down, select the
3666 you want, and click Go.</li>
3667 <li>Internet Explorer for Windows may suggest an incorrect filename when
3672 browsers on Windows, do not have this problem.</li>
3673 </ul>
3677 columns!</a></h4>
3679 <p> No, it's MySQL that is doing
3685 underscores in the database name?</a></h4>
3687 <p> If you do not put a backslash before the underscore, this is a wildcard
3690 john2db ...<br /><br />
3692 If you put a backslash before the underscore, it means that the database
3693 name will have a real underscore.</p>
3697 statistics pages?</a></h4>
3708 if it already exists during the import. It does NOT drop the table after
3709 your export, it only affects the import file.</li>
3711 Otherwise, you may get an error if the table name exists but has a
3712 different structure.</li>
3714 (if any) will be included in backup.</li>
3716 field and table names formed with special characters are protected.</li>
3718 types set in the pmadb in the dump as
3720 </li>
3721 </ul>
3726 command, for better documentation (but resulting file is bigger).</li>
3728 once the INSERT verb and the table name.</li>
3731 </li>
3733 more info is provided in the
3735 but basically with this selected, invalid values are adjusted and
3736 inserted rather than causing the entire statement to fail.</li>
3737 </ul>
3741 in its name.</a></h4>
3744 is the normal way to reference a database and table name. Worse, MySQL
3745 will usually let you create a database with a dot, but then you cannot
3746 work with it, nor delete it.</p>
3759 for usage.<br />
3760 On a more recent pear version, I had problems with the state of Net_DIME
3761 being beta, so this single command
3763 needed modules.<br />
3764 If you use the Validator, you should be aware that any
3766 submit will be stored anonymously (database/table/column names,
3767 strings, numbers replaced with generic values). The Mimer
3770 We utilize it as free SOAP service.</p>
3774 it, but MySQL says "BLOB column '...' used in key specification without
3777 <p> The right way to do this, is to create the field without any indexes,
3779 dialog. On this page, you will be able to choose your BLOB field, and
3780 set a size to the index, which is the condition to create an index on
3781 a BLOB field.</p>
3785 editing fields?</a></h4>
3787 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3788 with many editing fields (table structure changes, row editing, etc.)
3789 (must be enabled in configuration - see.
3791 You can also have a look at the directive
3793 ('vertical') and see if this eases up editing for you.</p>
3797 WTF is this feature then useful for?</a></h4>
3799 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3800 on them. Otherwise you could just put a comment on the field. Because entering
3801 your own mimetype will cause serious syntax checking issues and validation,
3802 this introduces a high-risk false-user-input situation. Instead you have to
3803 initialize mimetypes using functions or empty mimetype definitions.<br />
3804 Plus, you have a whole overview of available mimetypes. Who knows all those
3805 mimetypes by heart so he/she can enter it at will?</p>
3809 can't I see any bookmarks below the query box? What is this variable for?
3810 </a></h4>
3812 <p> Any query you have executed can be stored as a bookmark on the page where the
3813 results are displayed. You will find a button labeled 'Bookmark this query'
3814 just at the end of the page.<br />
3815 As soon as you have stored a bookmark, it is related to the database you run
3816 the query on. You can now access a bookmark dropdown on each page, the query
3817 box appears on for that database.<br /><br />
3819 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3823 aware of that you HAVE to create a valid query, otherwise your query won't be
3824 even able to be stored in the database.<br />
3826 for your query will remain the way it is, but will be stripped of the /**/
3827 chars. So you can use:<br /><br />
3831 which will be expanded to<br /><br />
3835 in your query, where VARIABLE is the string you entered in the input box. If
3836 an empty string is provided, no replacements are made.<br /><br />
3838 A more complex example. Say you have stored this query:<br /><br />
3840 <br /><br />
3843 the full query will be:<br /><br />
3846 <br /><br />
3850 spaces inserted there
3851 will be later also inserted as spaces in your query and may lead to unexpected
3852 results especially when
3854 Your initial query which is going to be stored as a bookmark has to yield at
3855 least one result row so
3856 you can store the bookmark. You may have that to work around using well
3860 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3861 include exported table?</a></h4>
3863 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3864 document should look like following one (assuming you have table
3867 <pre>
3868 \documentclass{article} % or any class you want
3869 \usepackage{longtable} % for displaying table
3870 \begin{document} % start of document
3871 \include{table} % including exported table
3872 \end{document} % end of document
3873 </pre>
3877 access them.
3878 </a></h4>
3881 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3882 enable users to see all the database names.
3885 So if your users do not need those privileges, you can remove them and their
3886 databases list will shorten.</p>
3890 possible values for a field, based on some foreign table?</a></h4>
3892 <p> You have to setup appropriate links between the tables, and also
3896 foreign table, a drop-down list of values will be available.
3897 You will see two lists of values, the first list containing the key
3898 and the display field, the second list containing the display field
3899 and the key. The reason for this is to be able to type the first
3900 letter of either the key or the display field.<br /><br />
3902 For 200 values or more, a distinct window will appear, to browse foreign
3903 key values and choose one.</p>
3907 automatically when entering Browse mode for a table?</a></h4>
3909 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3910 </p>
3914 Excel files, how can I enable that?</a></h4>
3916 <p> Current version does support direct export to Microsoft Excel and Word
3917 versions 2000 and newer. If you need export older versions, you can use
3919 which works out of the box or you can
3921 several problems, most important are limitation of cell content to 255
3922 chars and no support for charsets, so think carefully whether you want to
3923 enable this.</b>. For enabling this you need to set
3927 module Spreadsheet_Excel_Writer into php include path. The
3928 installation can be done by following command:</p>
3930 <pre>
3931 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3932 </pre>
3934 <p> First part of switches set we want to install beta version of that module
3935 (no stable version available yet) and then we tell pear we want to satisfy
3936 dependencies.</p>
3938 <p> If you are running in PHP safe mode, you will have to set
3941 modules are located, for example:</p>
3943 <pre>
3944 safe_mode_include_dir = /usr/local/lib/php
3945 </pre>
3949 <pre>
3950 cd phpMyAdmin
3951 mkdir tmp
3952 chmod o+rwx tmp
3953 </pre>
3957 what happens to my column comments stored in pmadb?</a></h4>
3959 <p> Automatic migration of a table's pmadb-style column comments to the native
3960 ones is done whenever you enter Structure page for this table.</p>
3967 <p> Our Bug Tracker is located at
3969 under the Bugs section.<br /><br />
3971 But please first discuss your bug with other users:<br />
3977 existing language, where do I start?</a></h4>
3979 <p> Always use the current SVN version of your language file.
3981 don't know how to get the SVN version, please ask one of the developers.
3982 <br />
3983 Please note that we try not to use HTML entities like &eacute; in
3984 the translations, since we define the right character set in the file.
3985 With HTML entities, the text on JavaScript messages would not
3986 display correctly.
3987 However there are some entities that need to be there, for quotes
3988 ,non-breakable spaces, ampersands, less than, greater than.<br />
3989 You can then put your translations, as a zip file to avoid losing special
3990 characters, on the sourceforge.net translation tracker.<br />
3991 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3992 list, because this is where we ask for translations of new messages.</p>
3996 phpMyAdmin. How should I proceed?</a></h4>
4001 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4002 </li>
4004 <li>generate patch with your changes:
4006 </li>
4009 tracker of the phpMyAdmin project</a>.
4010 </li>
4011 </ol>
4013 <p> Write access to the SVN tree is granted only to experienced developers who
4014 have already contributed something useful to phpMyAdmin.<br />
4020 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4022 <p> Please refer to
4023 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4024 </p>
4026 <!-- DEVELOPERS -->
4029 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4030 great features have been written by other people and you too can help to
4031 make phpMyAdmin a useful tool.</p>
4033 <p> If you're planning to contribute source, please read the following
4034 information:</p>
4040 it free from other code.<br />
4041 Commonly used functions should be added to
4044 <li>Obviously, you're free to use whatever coding style you want. But
4045 please try to keep your code as simple as possible: beginners are
4046 using phpMyAdmin as an example application.<br />
4047 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4048 compliant on one hand, they fit the
4051 coding standards</a>
4052 on the other hand. Please pay attention to this.</li>
4053 <li>Please try to keep up the file-naming conventions. Table-related stuff
4056 <li>Please don't use verbose strings in your code, instead add the string
4061 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4062 better debug and profile their code.<br />
4063 Please see the
4065 options for more information.<br />
4066 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4067 lost during its re-entry into Earth's atmosphere and in memory of the
4068 brave men and women who gave their lives for the people of Earth.</li>
4069 </ul>
4071 <!-- CREDITS -->
4074 <pre>
4075 phpMyAdmin - Credits
4076 ====================
4078 CREDITS, in chronological order
4079 -------------------------------
4082 * creator of the phpmyadmin project
4086 * multi-language version
4087 * various fixes and improvements
4089 * current project maintainer
4092 * started SourceForge phpMyAdmin project in March 2001
4093 * sync'ed different existing CVS trees with new features and bugfixes
4094 * multi-language improvements, dynamic language selection
4095 * current project maintainer
4096 * many bugfixes and improvements
4099 * rewrote and optimized javascript, DHTML and DOM stuff
4100 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4101 generate XHTML1.0 and CSS2 compliant codes
4102 * improved the language detection system
4103 * many bugfixes and improvements
4106 * database maintenance controls
4107 * table type code
4109 * DB-based configuration (Not completed)
4112 * many bugfixes and improvements
4115 * bookmarks feature
4116 * multiple dump feature
4117 * gzip dump feature
4118 * zip dump feature
4121 * various fixes
4122 * moderator of the phpMyAdmin former users forum at phpwizard.net
4128 * rewrote and fix dump code
4129 * bugfixes
4132 * rewrote dump code for PHP4
4133 * mySQL table statistics
4134 * bugfixes
4137 * main author of the version 2.1.0.1
4138 * bugfixes
4142 * abstract database interface (PMA_DBI) with MySQLi support
4143 * privileges administration
4145 * various features and fixes
4146 * German language file updates
4149 * automatic joins in QBE
4150 * links column in printview
4151 * Relation view
4154 * enhanced index creation/display feature
4155 * feature to use a different charset for HTML than for MySQL
4156 * improvements of export feature
4157 * various features and fixes
4158 * Czech language file updates
4161 (http://sf.net/projects/phpmysqlformgen/)
4162 * suggested the patch for multiple table printviews
4165 * built the patch for vertical display of table rows
4166 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4167 * Improvement of column/db comments
4168 * (MIME)-Transformations for columns
4169 * Use custom alias names for Databases in left frame
4170 * hierarchical/nested table display
4171 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4172 * new icon sets
4173 * vertical display of column properties page
4174 * some bugfixes, features, support, German language additions
4177 * japanese kanji encoding conversion feature
4180 * the Cookie authentication mode
4183 * table relation-links feature
4186 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4187 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4188 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4194 * phpMyAdmin logo (until June 2004)
4197 * blowfish library from the Horde project
4200 * mysqli support
4201 * many bugfixes and improvements
4204 * redesign for 2.6.0
4205 * phpMyAdmin sailboat logo (June 2004)
4208 * Representation at conferences
4211 * interface improvements
4212 * various bugfixes
4214 - Ivan A Kirillov
4215 * new relations Designer
4217 And also to the following people who have contributed minor changes,
4218 enhancements, bugfixes or support for a new language since version 2.1.0:
4220 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4221 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4222 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4223 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4225 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4226 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4227 Luís V., Martijn W. van der Lee,
4228 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4232 Original Credits of Version 2.1.0
4233 ---------------------------------
4235 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4236 to create a web-based interface to MySQL using PHP3. Although I have not
4237 used any of his source-code, there are some concepts I've borrowed from
4238 him. phpMyAdmin was created because Peter told me he wasn't going to
4239 further develop his (great) tool.
4240 Thanks go to
4242 code for the check when dropping a table or database. He also suggested
4243 that you should be able to specify the primary key on tbl_create.php3. To
4244 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4245 well as a bug-report. Plus many smaller improvements.
4247 were introduced in 1.3.0 (including quite significant ones like the
4248 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4249 bug-fixes and help.
4251 language-independent by outsourcing the strings to a separate file. He
4252 also contributed the French translation.
4254 tbl_select.php3, a feature to display only some fields from a table.
4256 functions in tbl_change.php3. He also added the
4259 servers and is a regular contributor for bug-fixes.
4261 features for 2.0.6.
4262 The following people have contributed minor changes, enhancements, bugfixes
4263 or support for a new language:
4264 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4265 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4266 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4267 G. Wieggers.
4269 And thanks to everyone else who sent me email with suggestions, bug-reports
4270 and or just some feedback.
4271 </pre>
4277 <ul>
4279 - the default name of Apache's directory-level configuration file.</li>
4283 - a software application that enables a user to display and interact with
4284 text, images, and other information typically located on a web page at a
4285 website on the World Wide Web.</li>
4287 - a free software/open source data compression algorithm and program
4288 developed by Julian Seward.</li>
4290 - an important World Wide Web technology that enables a client web browser
4291 to request data from a program executed on the Web server.</li>
4293 - a log or record of changes made to a project.</li>
4295 - a computer system that accesses a (remote) service on another computer
4296 by some kind of network.</li>
4298 - a set of data values of a particular simple type, one for each row of
4299 the table.</li>
4301 - a packet of information sent by a server to a World Wide Web browser
4302 and then sent back by the browser each time it accesses that server.</li>
4304 - Comma-seperated values</li>
4307 - an organized collection of data.</li>
4310 - a PHP module that extends PHP with additional functionality.</li>
4312 - a list of commonly asked question and there answers.</li>
4314 - one part of divided data/columns.</li>
4316 - a field or group of fields in a database record that point to a key
4317 field or group of fields forming a key of another database record in some
4318 (usually different) table.</li>
4320 - the free PDF library</li>
4322 GD Graphics Library</a> - a library by Thomas Boutell and others for
4323 dynamically manipulating images.</li>
4326 - gzip is short for GNU zip, a GNU free software file compression
4327 program.</li>
4329 - any machine connected to a computer network, a node that has a hostname.</li>
4331 - the unique name by which a network attached device is known on a network.</li>
4333 (HyperText Transfer Protocol)</a>
4334 - the primary method used to transfer or convey information on the World
4335 Wide Web.</li>
4338 additional security measures.</li>
4339 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4340 - a set of Internet-based services for servers using Microsoft Windows.</li>
4342 - a feature that allows quick access to the rows in a table.</li>
4344 - a data-oriented protocol used by source and destination hosts for
4345 communicating data across a packet-switched internetwork.</li>
4347 - a unique number that devices use in order to identify and communicate
4348 with each other on a network utilizing the Internet Protocol standard.</li>
4350 (Internet Server Application Programming Interface)</a>
4351 - the API of Internet Information Services (IIS).</li>
4353 - a business or organization that offers users access to the Internet and related services.</li>
4355 - a most commonly used standard method of lossy compression for
4356 photographic images.</li>
4362 - line of personal computers is designed, developed, manufactured, and
4363 marketed by Apple Computer.</li>
4364 <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>
4365 - the operating system which is included with all currently shipping Apple
4366 Macintosh computers in the consumer and professional markets.</li>
4368 - a cryptographic library.</li>
4370 - the MCrypt PHP extension.</li>
4371 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4372 - an Internet Standard for the format of e-mail.</li>
4374 - some sort of extension for the Apache Webserver.</li>
4376 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4377 Management System (DBMS).</li>
4379 - the improved MySQL client PHP extension.</li>
4381 - the MySQL client PHP extension.</li>
4383 - open standard for office documents.</li>
4384 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4385 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4387 (Portable Document Format)</a>
4388 - a file format developed by Adobe Systems for representing two
4389 dimensional documents in a device independent and resolution independent
4390 format.</li>
4392 - the PHP Extension and Application Repository.</li>
4394 - the perl-compatible regular expression functions for PHP</li>
4396 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4397 programming language used mainly for developing server-side applications
4398 and dynamic web content, and more recently, a broader range of software
4399 applications.</li>
4401 - a connection through which data is sent and received.</li>
4403 - Request for Comments (RFC) documents are a series of memoranda
4404 encompassing new research, innovations, and methodologies applicable to
4405 Internet technologies.</li>
4409 - represents a single, implicitly structured data item in a table.</li>
4411 - a computer system that provides services to other computing
4412 systems over a network.</li>
4413 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4414 - handlers for different table types</li>
4416 - a form of inter-process communication.</li>
4418 Sockets Layer)</a>
4419 - a cryptographic protocol which provides secure communication on the Internet.</li>
4421 - Structured Query Language</li>
4423 - a set of data elements (cells) that is organized, defined and stored as
4424 horizontal rows and vertical columns where each item can be uniquely
4425 identified by a label or key or by it?s position in relation to other items.</li>
4428 - a type of archive file format: the Tape ARchive format.</li>
4430 - one of the core protocols of the Internet protocol suite.</li>
4434 - a sequence of characters, conforming to a standardized format, that is
4435 used for referring to resources, such as documents and images on the
4436 Internet, by their location.</li>
4438 - A computer (program) that is responsible for accepting HTTP requests
4439 from clients and serving them Web pages.</li>
4441 - a W3C-recommended general-purpose markup language for creating
4442 special-purpose markup languages, capable of describing many different
4443 kinds of data.</li>
4445 - a popular data compression and archival format.</li>
4447 - an open-source, cross-platform data compression library by Jean-loup
4448 Gailly and Mark Adler.</li>
4449 </ul>
4459 </body>
4460 </html>