| blob | cd345fedfdba17b5d6489d53bb4f1754de4b73ab |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 </li>
63 <li>You need GD2 support in PHP to display inline
65 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
197 config.inc.php, but now a wizard-style setup script is provided for
198 those who prefer a graphical installation. Creating a config.inc.php is
199 still a quick way to get started and needed for some advanced features.
200 <ul><li>To manually create the file, simply use your text editor to
203 file) in the main (top-level) phpMyAdmin directory (the one
207 default value is okay for a particular setting, there is no
209 few directives to get going, a simple configuration may look
210 like this:
211 <pre>
212 <?php
213 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
215 $i=0;
216 $i++;
217 $cfg['Servers'][$i]['auth_type'] = 'cookie';
218 ?>
219 </pre>
220 Or, if you prefer to not be prompted every time you log in:
221 <pre>
222 <?php
224 $i=0;
225 $i++;
226 $cfg['Servers'][$i]['user'] = 'root';
227 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
228 ?>
229 </pre>
230 For a full explanation of possible configuration values, see the
236 directory. This is a security measure. On a Linux/Unix system you
237 can use the following commands:
238 <pre>
239 cd phpMyAdmin
240 mkdir config # create directory for saving
241 chmod o+rw config # give it world writable permissions
242 </pre>
243 And to edit an existing configuration, copy it over first:
244 <pre>
245 cp config.inc.php config/ # copy current configuration for editing
246 chmod o+w config/config.inc.php # give it world writable permissions
247 </pre>
248 On other platforms, simply create the folder and ensure that your
257 the webserver does not have the proper permissions you may see the
259 config/</tt> directory exists and has the proper permissions -
261 and upload (via FTP or some similar means) to the proper location.<br /><br />
263 Once the file has been saved, it must be moved out of the <tt>
264 config/</tt> directory and the permissions must be reset, again
265 as a security measure:
266 <pre>
267 mv config/config.inc.php . # move file to current directory
268 chmod o-rw config.inc.php # remove world read and write permissions
269 </pre>
270 Now the file is ready to be used. You can choose to review or edit
271 the file with your favorite editor, if you prefer to set some
272 advanced options which the setup script does not provide.</li></ul></li>
273 <li>If you are using the
275 protect the phpMyAdmin installation directory because using
276 config does not require a user to
277 enter a password to access the phpMyAdmin installation. Use of an alternate
278 authentication method is recommended, for example with
286 in your browser. phpMyAdmin should now display a welcome screen
287 and your databases, or a login dialog if using
289 authentication mode.</li>
291 webserver configuration. For Apache you can use supplied .htaccess file
292 in that folder, for other webservers, you should configure this yourself.
293 Such configuration prevents from possible path exposure and cross side
294 scripting vulnerabilities that might happen to be found in that code.</li>
295 </ol>
299 <p> For a whole set of new features (bookmarks, comments,
302 transformation, etc.) you need to create a set of special tables. Those
303 tables can be located in your own database, or in a central database for a
304 multi-user installation (this database would then be accessed by the
305 controluser, so no other user should have rights to it).</p>
314 installation.</p>
319 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
320 that you may need special (administrator) privileges to create the database
321 and tables, and that the script may need some tuning, depending on the
322 database name.</p>
327 section</a>. You will also need to have a controluser with the proper rights
334 unpacked one. Configuration files from very old versions (2.3.0 or before) may
335 require some tweaking as some options have been changed or removed.
337 statement that you might find near the end of your configuration file.</p>
341 is version-specific.</p>
344 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
345 you should run the SQL script found in
352 where you want to give users access to their own database and don't want
353 them to play around with others.<br />
354 Nevertheless be aware that MS Internet Explorer seems to be really buggy
356 in this area!<br />
359 that your user/password pair are not in clear in the configuration file.
360 </li>
363 authentication modes are more secure: the MySQL login information does
364 not need to be set in the phpMyAdmin configuration file (except possibly
366 However, keep in mind that the password travels in plain text, unless
367 you are using the HTTPS protocol.<br />
368 In cookie mode, the password is stored, encrypted with the blowfish
369 algorithm, in a temporary cookie.</li>
372 your MySQL server is previous to 4.1.2, or is running with
382 file under the
384 $cfg['Servers'][$i]['controluser']</a></tt> and
389 only an example: use something else in your file!</b> Input these
390 statements from the phpMyAdmin SQL Query window or mysql command–line
391 client.<br />
393 if it's not the same as the MySQL server's one.
395 <pre>
396 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
397 GRANT SELECT (
398 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
399 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
400 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
401 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
402 Execute_priv, Repl_slave_priv, Repl_client_priv
403 ) ON mysql.user TO 'pma'@'localhost';
404 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
405 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
406 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
407 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
409 If you are using an old MySQL version (below 4.0.2), please replace
410 the first GRANT SELECT query by this one:
412 <pre>
413 GRANT SELECT (
414 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
415 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
416 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
417 ) ON mysql.user TO 'pma'@'localhost';</pre>
419 ... and if you want to use the many new relation and bookmark features:
421 <pre>
423 </pre>
427 Of course, the above queries only work if your MySQL version supports
431 on a set of particular databases. Normally you shouldn't give global
432 privileges to an ordinary user, unless you understand the impact of those
433 privileges (for example, you are creating a superuser).<br />
437 <pre>
438 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
439 </pre>
441 What the user may now do is controlled entirely by the MySQL user
442 management system.<br />
444 authentication mode, you don't need to fill the user/password fields
446 array.</li>
447 </ul>
452 method and allows you to log in as any valid MySQL user.</li>
453 <li>Is supported with most PHP configurations. For
466 mode.</li>
467 </ul>
471 <ul><li>You can use this method as a replacement for the
473 (for example, if you're running
475 <li>Obviously, the user must enable cookies in the browser, but this is
476 now a requirement for all authentication modes.</li>
477 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
478 with the same username.</li>
479 <li>If you want to log in to arbitrary server see
484 not required.</li>
485 </ul>
489 <ul><li>This mode is a convenient way of using credentials from another
490 application to authenticate to phpMyAdmin.</li>
491 <li>The other application has to store login information into
492 session data.</li>
494 section.</li>
495 </ul>
498 <ul><li>This mode is the less secure one because it requires you to fill the
500 $cfg['Servers'][$i]['user']</a> and
502 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
503 can read your config.inc.php can discover your username and password).
504 <br />
511 is an entry explaining how to protect your configuration file.</li>
512 <li>For additional security in this mode, you may wish to consider the Host
513 authentication
515 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
517 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
518 directives.</li>
519 <li>Unlike cookie and http, does not require a user to log in when first
520 loading the phpMyAdmin site. This is by design but could allow any
521 user to access your installation. Use of some restriction method is
523 HTTP-AUTH directive or disallowing incoming HTTP requests at
524 one’s router or firewall will suffice (both of which
525 are beyond the scope of this manual but easily searchable with Google).</li>
526 </ul>
528 <!-- CONFIGURATION -->
532 users:</span> PHP does not seem to like
536 before saving a script you have modified.</p>
541 section to create one. This file only needs to contain the parameters you want to
542 change from their corresponding default value in
545 <p> The parameters which relate to design (like colors) are placed in
548 your site specific code to be included on start and end of each page.</p>
552 (with full path) to your phpMyAdmin installation's directory.
555 some web servers are case–sensitive.
558 Starting with version 2.3.0, it is advisable to try leaving this
559 blank. In most cases phpMyAdmin automatically detects the proper
560 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
561 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
562 A good test is to browse a table, edit a row and save it. There should
563 be an error message if phpMyAdmin is having trouble auto–detecting
564 the correct value. If you get an error that this must be set or if
565 the autodetect code fails to detect your path, please post a bug
566 report on our bug tracker so we can improve the code.</dd>
570 with master / foreign – tables (see
572 <br />
573 If you tried to set this up and it does not work for you, have a look on
575 use it. You will find a link that will analyze why those features have
576 been disabled.<br />
577 If you do not want to use those features set this variable to
582 algorithm to encrypt the password.<br />
584 passphrase of your choice. It will be used internally by the blowfish
585 algorithm: you won’t be prompted for this passphrase. The maximum
590 MySQL servers. Therefore, a
592 been added which contains the login information for the different servers.
593 The first
595 contains the hostname of the first server, the second
597 the hostname of the second server, etc. In
599 server definition, however you can put as many as you need in
601 have to define all settings, just those you need to change).</dd>
605 $i-th MySQL-server. E.g. localhost.</dd>
610 ignores this port number and connects with the socket, so if you want
611 to connect to a port different from the default port, use
614 </dd>
618 To determine the correct socket, check your MySQL configuration or, using the
620 Among the resulting information displayed will be the socket used.</dd>
623 <dd>Whether to enable SSL for connection to MySQL server.
624 </dd>
627 <dd>What type connection to use with the MySQL server. Your options are
629 is nearly guaranteed to be available on all MySQL servers, while
630 sockets are not supported on some platforms.<br /><br />
632 To use the socket mode, your MySQL server must be on the same machine
633 as the Web server.</dd>
636 <dd>What php MySQL extension to use for the connection. Valid options are:
637 <br /><br />
640 The classic MySQL extension. This is the recommended and default
641 method at this time.<br /><br />
644 The improved MySQL extension. This extension became available
645 with php 5.0.0 and is the recommended way to connect to a server
649 <dd>Whether to use a compressed protocol for the MySQL server connection
650 or not (experimental).<br />
656 </dt>
658 all relational features (see
660 and, for a MySQL server previous to 4.1.2 or running with
663 authentication mode).<br /><br />
666 cookie authentication modes (or 'config'
667 authentication mode since phpMyAdmin 2.2.1), you need to supply the
672 This account is used to check what databases the user will see at
673 login.<br />
677 In phpMyAdmin versions before 2.2.5, those were called
681 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
682 <dd>Whether config or cookie or
684 should be used for this server.
686 is the plain old way: username and password are stored in
688 <li>'cookie' authentication mode
690 2.2.3 allows you to log in as any valid MySQL user with the
691 help of cookies. Username and password are stored in
692 cookies during the session and password is deleted when it
693 ends. This can also allow you to log in in arbitrary server if
694 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
695 </li>
696 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
697 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
698 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
699 <li>'signon' authentication mode
701 as introduced in 2.10.0 allows you to log in from prepared PHP
702 session data. This is useful for implementing single signon
703 from another application. Sample way how to seed session is in
709 </ul>
712 for more information.
713 </dd>
717 </dt>
718 <dd>
719 When using auth_type = 'config', this is the user/password-pair
720 which phpMyAdmin will use to connect to the
721 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
722 cookie authentication is used and should be empty.</dd>
724 <span
726 </dt>
727 <dd>
728 Allow attempt to log in without password when a login with password
729 fails. This can be used together with http authentication, when
730 authentication is done some other way and phpMyAdmin gets user name
731 from auth and uses empty password for connecting to MySQL. Password
732 login is still tried first, but as fallback, no password method is
733 tried.</dd>
736 </dt>
737 <dd>
738 If set to a (an array of) database name(s), only this (these) database(s)
739 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
740 database(s) name(s) may contain MySQL wildcards characters
744 This setting is an efficient way to lower the server load since the
745 latter does not need to send MySQL requests to build the available
747 privileges rules of the MySQL database server</span>. If set, it just
748 means only these databases will be displayed but
750 <br /><br />
752 An example of using more that one database:
754 <br /><br />
756 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
757 databases in the left frame, so that you can individually arrange your databases.<br />
758 If you want to have certain databases at the top, but don't care about the others, you do not
759 need to specify all other databases. Use:
761 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
762 order.</dd>
765 </dt>
766 <dd>Regular expression for hiding some databases. This only hides them
767 from listing, but a user is still able to access them (using, for example,
768 the SQL query area). To limit access, use the MySQL privilege system.
769 <br /><br />
774 More information on regular expressions can be found in the
776 PCRE pattern syntax</a> portion of the PHP reference manual.
777 </dd>
780 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
781 this string will be displayed instead of the hostname in the pull-down
782 menu on the main page. This can be useful if you want to show only
783 certain databases on your system, for example. For HTTP auth, all
784 non-US-ASCII characters will be stripped.</dd>
788 </dt>
789 <dd>The name of the database containing the linked-tables infrastructure.
790 <br /><br />
793 section in this document to see the benefits of this infrastructure,
794 and for a quick way of creating this database and the needed tables.
795 <br /><br />
797 If you are the only user of this phpMyAdmin installation, you can
798 use your current database to store those special tables; in this
799 case, just put your current database name in
801 set this parameter to the name of your central database containing
802 the linked-tables infrastructure.</dd>
806 </dt>
808 useful for queries you often run.<br /><br />
810 To allow the usage of this functionality:
812 <li>enter the table name in
814 </ul>
815 </dd>
819 </dt>
821 which field is a key in another table (a foreign key). phpMyAdmin
822 currently uses this to
823 <ul><li>make clickable, when you browse the master table, the data values
824 that point to the foreign table;</li>
826 when browsing the master table, if you move the mouse to a column
827 containing a foreign key (use also the 'table_info' table);<br />
830 <li>in edit/insert mode, display a drop-down list of possible foreign
834 <li>display links on the table properties page, to check referential
835 integrity (display missing foreign keys) for each described key;
836 </li>
840 schema of your database (also uses the table_coords table).</li>
841 </ul>
843 The keys can be numeric or character.<br /><br />
845 To allow the usage of this functionality:
848 infrastructure</li>
849 <li>put the relation table name in
851 <li>now as normal user open phpMyAdmin and for each one of your
852 tables where you want to use this feature, click
854 </li>
855 </ul>
859 future development of the cross-db relations.
860 </dd>
864 </dt>
865 <dd>
866 Since release 2.3.0 you can describe, in a special 'table_info'
867 table, which field is to be displayed as a tool-tip when moving the
868 cursor over the corresponding key.<br />
869 This configuration variable will hold the name of this special
870 table. To allow the usage of this functionality:
872 <li>put the table name in
874 <li>then for each table where you want to use this feature,
876 to choose the field.</li>
877 </ul>
879 </dd>
883 </dt>
886 the relations between your tables. To do this it needs two tables
891 schema output).<br /><br />
895 To allow the usage of this functionality:
898 infrastructure</li>
899 <li>put the correct table names in
902 </ul>
905 </dd>
909 </dt>
911 Since release 2.3.0 you can store comments to describe each column for
913 <br /><br />
915 Starting with release 2.5.0, comments are consequently used on the table
916 property pages and table browse view, showing up as tool-tips above the
917 column name (properties page) or embedded within the header of table in
918 browse view. They can also be shown in a table dump. Please see the
919 relevant configuration directives later on.<br /><br />
921 Also new in release 2.5.0 is a MIME-transformation system which is also
923 Transformations</a> for further information. To use the
924 MIME-transformation system, your column_info table has to have the three
925 new fields 'mimetype', 'transformation', 'transformation_options'.
926 <br /><br />
928 To allow the usage of this functionality:
930 infrastructure</li>
931 <li>put the table name in
935 <pre>
936 ALTER TABLE `pma_column_comments`
937 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
938 ADD `transformation` VARCHAR( 255 ) NOT NULL,
939 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
940 </pre>
943 renamed from<br />
946 </ul>
947 </dd>
951 </dt>
954 all queries you entered manually into the phpMyAdmin interface. If you
955 don't want to use a table-based history, you can use the JavaScript-based
956 history. Using that, all your history items are deleted when closing the
957 window.<br /><br />
959 Using
961 you can specify an amount of history items you want to have on hold. On
962 every login, this list gets cut to the maximum amount.<br /><br />
964 The query history is only available if JavaScript is enabled in your
965 browser.<br /><br />
967 To allow the usage of this functionality:
970 infrastructure</li>
972 </li>
973 </ul>
974 </dd>
978 </dt>
980 to visually manage the relations.
981 <br /><br />
983 To allow the usage of this functionality:
986 infrastructure</li>
988 </li>
989 </ul>
990 </dd>
993 </dt>
995 column_info table got enhanced with three new fields. If the above variable
997 latest table structure available. If not, it will emit a warning to the
998 superuser.<br /><br />
1000 You can disable this checking behavior by setting the variable to false,
1001 which should offer a performance increase.<br /><br />
1003 Recommended to set to FALSE, when you are sure, your table structure is
1004 up to date.</dd>
1006 boolean</dt>
1007 <dd>Whether to allow root access. This is just simplification of rules below.
1008 </dd>
1011 </dt>
1013 authentication is disabled.<br /><br />
1016 all deny rules followed by allow rules. Access is allowed by default. Any
1017 client which does not match a Deny command or does match an Allow command
1018 will be allowed access to the server. <br /><br />
1021 applies all allow rules followed by deny rules. Access is denied by
1022 default. Any client which does not match an Allow directive or does
1023 match a Deny directive will be denied access to the server.<br /><br />
1025 If your rule order is set to 'explicit', the authentication is
1026 performed in a similar fashion to rule order 'deny,allow', with the
1030 and was available in Apache by specifying allow and deny rules without
1031 setting any order.<br /><br />
1033 Please also see <a
1035 address behind proxies.
1036 </dd>
1038 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1039 </dt>
1040 <dd>The general format for the rules is as such:
1042 <pre>
1044 </pre>
1049 well (please note that those containing SERVER_ADDRESS might not be
1050 available on all webservers):
1051 <pre>
1057 </pre>
1059 Having an empty rule list is equivalent to either using
1065 following work:<br />
1067 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1068 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1069 But the following does not work:<br />
1072 </dd>
1073 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1074 <dd>Name of session which will be used for signon authentication method.
1075 </dd>
1077 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1078 </dd>
1080 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1081 </dd>
1084 <dd>If you have more than one server configured, you can set
1086 that server when phpMyAdmin is started, or set it to 0 to be given a
1087 list of servers without logging in.<br />
1089 MUST be set to that server.</dd>
1092 <dd>The maximum number of database names to be displayed in the
1093 navigation frame and the database list.</dd>
1096 <dd>The maximum number of table names to be displayed in the
1097 main panel's list. This limit is also enforced in the navigation panel
1098 when in Light mode.</dd>
1101 <dd>The maximum number of characters when a SQL query is displayed. The
1102 default limit of 1000 should be correct to avoid the display of tons
1103 of hexadecimal codes that represent BLOBs, but some users have real
1107 <dd>Defines whether to use GZip output buffering for increased
1109 Set to true/false for enabling/disabling. When set to 'auto' (string),
1110 phpMyAdmin tries to enable output buffering and will automatically disable
1111 it if your browser has some problems with buffering. IE6 with a certain patch
1112 is known to cause data corruption when having enabled buffering.</dd>
1115 <dd>Whether persistent connections should be used or not (mysql_connect or
1116 mysql_pconnect).</dd>
1122 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1123 to zero, no time limit is imposed.<br />
1124 This setting is used while importing/exporting dump files but has no
1125 effect when PHP is running in safe mode.</dd>
1128 <dd>Set the number of bytes a script is allowed to allocate. If number set
1129 to zero, no limit is imposed.<br />
1130 This setting is used while importing/exporting dump files but has no
1131 effect when PHP is running in safe mode.<br />
1135 <dd>Mark used tables and make it possible to show databases with locked
1140 generated by phpMyAdmin should be displayed or not.</dd>
1143 <dd>Defines whether normal users (non-administrator) are allowed to
1144 delete their own database or not. If set as FALSE, the link "Drop
1146 mydatabase" will be rejected. Quite practical for
1148 customers.<br />
1149 Please note that this limitation of SQL queries is not as strict as
1150 when using MySQL privileges. This is due to nature of SQL queries
1151 which might be quite complicated. So this choice should be viewed as
1152 help to avoid accidental dropping rather than strict privilege
1153 limitation.</dd>
1157 displayed when you're about to lose data.</dd>
1160 <dd>Define whether the previous login should be recalled or not in cookie
1161 authentication mode.</dd>
1168 means that it will be kept for existing session. This is recommended
1169 for not trusted environments.</dd>
1172 <dd>If enabled (default), logout deletes cookies for all servers,
1173 otherwise only for current one. Setting this to false makes it easy to
1174 forget to log out from other server, when you are using more of
1175 them.</dd>
1181 <dd>Define whether phpMyAdmin will continue executing a multi-query
1182 statement if one of the queries fails. Default is to abort execution.</dd>
1185 <dd>Define whether phpMyAdmin will output the results of each query of a
1186 multi-query statement embedded into the
1191 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1192 <br /><br />
1195 MySQL servers behind the firewall where your
1197 </dd>
1200 <dd>Defines whether to use a select-based menu and display only the current
1201 tables in the left frame (smaller page). Only in Non-Lightmode you can
1202 use the feature to display nested folders using
1204 </dd>
1207 <dd>In light mode, defines whether to display the names of databases (in the
1208 selector) using a tree, see also
1210 </dd>
1213 <dd>The string used to separate the parts of the database name when showing
1214 them in a tree.</dd>
1217 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1218 This means if you have tables like 'first__second__third' this will be
1220 If set to FALSE or empty, the feature is disabled. NOTE: You should
1221 not use this separator at the beginning or end of a
1222 table name or multiple times after another without any other
1223 characters in between.</dd>
1226 <dd>Defines how many sublevels should be displayed when splitting
1227 up tables by the above separator.</dd>
1230 <dd>Defines whether to display table comment as tool-tip in left frame or
1231 not.</dd>
1234 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1235 comment and the real name. That means that if you have a table called
1236 'user0001' and add the comment 'MyName' on it, you will see the name
1237 'MyName' used consequently in the left frame and the tool-tip shows
1238 the real name of the DB.</dd>
1241 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1243 When setting this to 'nested', the Alias of the Tablename is only used
1244 to split/nest the tables according to the
1246 directive. So only the folder is called like the Alias, the tablename itself
1247 stays the real tablename.</dd>
1250 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1253 <dd>Enter URL where logo in the navigation frame will point to.
1254 For use especially with self made theme which changes this.
1263 <dd>Defines whether or not to display a server choice at the top of the left frame.
1264 Defaults to FALSE.</dd>
1266 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1267 Defaults to FALSE (drop-down).</dd>
1269 <dd>Defines whether to display database choice in light navigation frame as links
1270 instead of in a drop-down. Defaults to 'auto' - on main page list is
1271 shown, when database is selected, only drop down is displayed.</dd>
1273 <dd>Defines whether or not to display space usage and statistics about databases
1274 and tables.<br />
1275 Note that statistics requires at least MySQL 3.23.3 and that, at this
1276 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1279 <dd>Defines whether to display detailed server information on main page.
1280 You can additionally hide more information by using
1282 </dd>
1287 </dt>
1290 not at the starting main (right) frame. This setting
1291 does not check MySQL commands entered directly.<br /><br />
1293 Please note that to block the usage of phpinfo() in scripts, you
1300 hard coded password value in the configuration file, end users can't
1301 be allowed to change their passwords.</dd>
1304 <dd>Defines whether to suggest a database name on the
1309 content.</dd>
1312 <dd>Defines whether navigation bar buttons and the right panel top menu
1313 contain text or symbols only. A value of TRUE displays icons, FALSE
1314 displays text and 'both' displays both icons and text.</dd>
1317 <dd>Defines whether a user should be displayed a
1321 <dd>Number of rows displayed when browsing a result set. If the result set
1328 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1332 from editing when browsing a table's content. Valid values are:
1337 </ul>
1338 </dd>
1341 <dd>Defines whether or not MySQL functions fields should be initially
1342 displayed in edit/insert mode. Since version 2.10, the user can
1343 toggle this setting from the interface.
1344 </dd>
1347 <dd>Defines which type of editing controls should be used for CHAR and
1348 VARCHAR fields. Possible values are:
1349 <ul><li>input - this allows to limit size of text to size of field in
1350 MySQL, but has problems with newlines in fields</li>
1351 <li>textarea - no problems with newlines in fields, but also no
1352 length limitations</li>
1353 </ul>
1354 Default is old behavior so input.</dd>
1360 <dd>If there are fewer items than this in the set of foreign keys, then a
1361 drop-down box of foreign keys is presented, in the style described by the
1363 setting.</dd>
1366 <dd>For the foreign key drop-down fields, there are several methods of
1367 display, offering both the key and value data. The contents of the
1368 array should be one or both of the following strings:
1374 </dt>
1375 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1376 creating a dump file</dd>
1379 </dt>
1380 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1381 compressed exports. This doesn't affect smaller dumps and allows users to
1382 create larger dumps that won't otherwise fit in memory due to php
1383 memory limit. Produced files contain more GZip/BZip2 headers, but all
1384 normal programs handle this correctly.</dd>
1388 mainframe.</dd>
1392 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1397 <dd>How many columns will be utilized to display the tables on the
1398 database property view? Default is 1 column. When setting this to a
1399 value larger than 1, the type of the database will be omitted for more
1400 display space.</dd>
1404 <dd>Defines the tab displayed by default on server view. Possible
1411 <dd>Defines the tab displayed by default on database view. Possible
1416 <dd>Defines the tab displayed by default on table view. Possible
1423 points to the MySQL documentation (type depends
1424 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1425 generated.<br />
1427 for more information about MySQL manuals and their types.</dd>
1430 <dd>Type of MySQL documentation:
1436 </ul>
1437 </dd>
1440 <dd>Defines the default language to use, if not browser-defined or
1441 user-defined.<br />
1443 this setting.</dd>
1446 <dd>Defines the default connection collation to use, if not
1447 user-defined.<br />
1452 <dd>Force: always use this language (must be defined in the
1456 <dd>Limit list of available languages to those matching the given regular
1457 expression. For example if you want only Czech and English, you should
1461 <dd>Default character set to use for recoding of MySQL queries. This must be
1462 enabled and it's described by
1464 option.<br />
1465 You can give here any character set which is in
1467 array and this is just default choice, user can select any of them.</dd>
1470 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1471 support (compiled in or module) in PHP to allow MySQL queries recoding
1472 and used language file must have it enabled (by default only these
1473 which are in Unicode, just to avoid losing some characters).<br /><br />
1476 in the Export page, to choose the character set when exporting a file.
1477 </dd>
1480 <dd>You can select here which functions will be used for character set
1481 conversion. Possible values are:
1482 <ul><li>auto - automatically use available one (first is tested
1483 iconv, then recode)</li>
1486 </ul>
1487 Default is auto.</dd>
1490 <dd>Specify some parameters for iconv used in charset conversion. See
1493 used, so that invalid characters will be transliterated.</dd>
1496 <dd>Available character sets for MySQL conversion. You can add your own (any of
1497 supported by recode/iconv) or remove these which you don't use.
1498 Character sets will be shown in same order as here listed, so if you
1499 frequently use some of these move them to the top.</dd>
1504 default empty, you need to fill in some trusted proxy servers if you
1505 want to use rules for IP addresses behind proxy.<br /><br />
1507 The following example specifies that phpMyAdmin should trust a
1509 <pre>
1510 $cfg['TrustedProxies'] =
1512 </pre>
1513 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1514 client's IP address as usual.
1515 </dd>
1519 MIME transformations.<br />
1520 Possible values are:
1521 <ul><li>auto - automatically detect, this is a bit expensive
1523 according to your server real possibilities</li>
1526 </ul>
1527 Default is auto.
1528 </dd>
1532 </dd>
1534 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1535 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1536 </dt>
1537 <dd>The background styles used for both the frames.
1540 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1542 <dd>The style used for the pointer in the navi frame.
1546 <dd>The color used for the database name in the navi frame.
1555 </dd>
1559 <dd>The style used for table headers. See
1564 </dd>
1568 </dd>
1570 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1572 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1574 </dt>
1576 The former feature highlights the row over which your mouse is passing
1577 and the latter lets you visually mark/unmark rows by clicking on
1578 them.<br />
1583 <dd>You put here a valid CSS font family value, for example
1588 <dd>You put here a valid CSS font family value, for example
1602 </dt>
1604 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1606 The Char* values are used for CHAR and VARCHAR editing (if configured
1610 </dt>
1614 </dt>
1615 <dd>Defines if the whole textarea of the query box will be selected on
1616 click.</dd>
1619 </dt>
1620 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1621 editing.</dd>
1624 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1625 Can be turned off by a toggle button on the browse page.</dd>
1629 </dt>
1630 <dd>Defines the place where modify and delete links would be put when
1631 tables contents are displayed (you may have them displayed both at the
1632 left and at the right).
1638 </dt>
1640 Define which one is displayed by default. The first mode displays each
1641 row on a horizontal line, the second rotates the headers by 90
1642 degrees, so you can use descriptive headers even though fields only
1643 contain small values and still print them out. The vertical mode sorts
1644 each row on a vertical lineup.<br /><br />
1646 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1647 the rotation of the header for horizontalflipped is done via CSS. If
1648 set to 'fake' PHP does the transformation for you, but of course this
1649 does not look as good as CSS.</dd>
1653 string or integer</dt>
1654 <dd>When editing/creating new columns in a table all fields normally get
1655 lined up one field a line. (default: 'horizontal'). If you set this to
1656 'vertical' you can have each field lined up vertically beneath each
1657 other. You can save up a lot of place on the horizontal direction and
1658 no longer have to scroll. If you set this to integer, editing of fewer
1659 columns will appear in 'vertical' mode, while editing of more fields
1660 still in 'horizontal' mode. This way you can still effectively edit
1661 large number of fields, while having full view on few of them.</dd>
1665 </dt>
1667 display of column comments in Browse or Property display. In browse
1668 mode, the comments are shown inside the header. In property mode,
1669 comments are displayed using a CSS-formatted dashed-line below the
1670 name of the field. The comment is shown as a tool-tip for that field.
1671 </dd>
1683 <dd>Whether to display a link to validate a query in any SQL Query box.
1690 <dd>
1691 The name of the directory where
1693 <dd>
1694 The name of the directory where
1696 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1697 are available under a drop-down box when you click the database name,
1699 <br /><br />
1701 If you want different directory for each user, %u will be replaced
1702 with username.<br /><br />
1706 compressed formats is enabled).<br /><br />
1708 This feature is useful when your file is too big to be uploaded via
1710 uploads are disabled in PHP.<br /><br />
1712 Please note that if PHP is running in safe mode, this directory must
1713 be owned by the same user as the owner of the phpMyAdmin scripts.
1714 <br /><br />
1718 alternatives.
1719 </dd>
1722 <dd>
1723 The name of the directory where dumps can be saved.<br /><br />
1725 If you want different directory for each user, %u will be replaced
1726 with username.<br /><br />
1728 Please note that the directory has to be writable for user running
1729 webserver.<br /><br />
1731 Please note that if PHP is running in safe mode, this directory must
1732 be owned by the same user as the owner of the phpMyAdmin scripts.
1733 </dd>
1736 <dd>
1737 The name of the directory where temporary files can be stored.
1738 <br /><br />
1739 This is needed for native MS Excel export, see
1742 </dd>
1745 <dd>
1746 In this array are defined default parameters for export, names of
1747 items are similar to texts seen on export page, so you can easily
1748 identify what they mean.
1749 </dd>
1752 <dd>
1753 In this array are defined default parameters for import, names of
1754 items are similar to texts seen on import page, so you can easily
1755 identify what they mean.
1756 </dd>
1759 <dd>
1760 Repeat the headers every X cells, or 0 to deactivate.
1761 </dd>
1769 </dt>
1770 <dd>
1771 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1772 or icon is always displayed on the left panel. If JavaScript is enabled in
1773 your browser, a click on this opens a distinct query window, which is
1774 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1775 changes to display a query box.<br /><br />
1777 The size of this query window can be customized with
1779 - both integers for the size in pixels. Note that normally, those
1781 theme you are using.<br /><br />
1785 opens the query window and puts the current query
1786 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1787 query in the right panel's query box.
1788 <br /><br />
1789 The usage of the JavaScript query window is recommended if you have a
1790 JavaScript enabled browser. Basic functions are used to exchange quite
1791 a few variables, so most 4th generation browsers should be capable to
1792 use that feature. It currently is only tested with Internet Explorer 6
1793 and Mozilla 1.x.
1794 <br /><br />
1796 to a table, which has to be created by you (see <a
1798 all your queries will be appended to the form, but only as long as
1799 your window is opened they remain saved.
1800 <br /><br />
1801 When using the JavaScript based query window, it will always get
1802 updated when you click on a new table/db to browse and will focus if
1803 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1804 the query window by checking the box "Do not overwrite this query from
1805 outside the window" below the query textarea. Then you can browse
1806 tables/databases in the background without losing the contents of the
1807 textarea, so this is especially useful when composing a query with
1808 tables you first have to look in. The checkbox will get automatically
1809 checked whenever you change the contents of the textarea. Please
1810 uncheck the button whenever you definitely want the query window to
1811 get updated even though you have made alterations.
1812 <br /><br />
1815 <br /><br />
1816 The query window also has a custom tabbed look to group the features.
1818 default tab to be used when opening the query window. It can be set to
1819 either 'sql', 'files', 'history' or 'full'.</dd>
1825 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1827 If the approximate row count as returned by
1830 count will be used.
1831 </dd>
1833 <dd>For VIEWs, since obtaining the exact count could have an
1834 impact on performance, this value is the maximum to be displayed, using
1836 any row counting.
1837 </dd>
1841 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1843 page. By clicking on the button 'toggle scratchboard' on the page
1844 where you edit x/y coordinates of those elements you can activate a
1845 scratchboard where all your elements are placed. By clicking on an
1846 element, you can move them around in the pre-defined area and the x/y
1847 coordinates will get updated dynamically. Likewise, when entering a
1848 new position directly into the input field, the new position in the
1849 scratchboard changes after your cursor leaves the input field.<br />
1850 You have to click on the 'OK'-button below the tables to save the new
1851 positions. If you want to place a new element, first add it to the
1852 table of elements and then you can drag the new element around.<br />
1853 By changing the paper size and the orientation you can change the size
1854 of the scratchboard as well. You can do so by just changing the
1855 dropdown field below, and the scratchboard will resize automatically,
1856 without interfering with the current placement of the elements.<br />
1857 If ever an element gets out of range you can either enlarge the paper
1858 size or click on the 'reset' button to place all elements below each
1859 other.<br />
1861 get this control to work. The basic Drag&Drop script functionality
1862 was kindly borrowed from www.youngpup.net and is underlying so
1863 specific license.</dd>
1866 <dd>Sorts database and table names according to natural order (for example,
1867 t1, t2, t10). Currently implemented in the left panel (Light mode)
1868 and in Database view, for the table list.</dd>
1874 <dd>Allows you to specify window's title bar. Following magic string can
1875 be used to get special values:
1876 <dl>
1882 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1891 </dl>
1892 </dd>
1902 </dd>
1905 <dd>If theme manager is active, use this as the path of the subdirectory
1906 containing all the themes.</dd>
1920 </dt>
1921 <dd>Default queries that will be displayed in query boxes when user didn't
1922 specify any. Use %d for database name, %t for table name and %f for a
1923 comma separated list of field names. Note that %t and %f are only
1927 <dd>
1928 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
1929 default we use HTML to format the query, but you can disable this by
1931 </dd>
1934 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1935 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1936 query inside a bracket is indented. By changing
1939 specifies the units of the indent amount that you specified. This is
1940 used via stylesheets.</dd>
1943 <dd>This array is used to define the colours for each type of element of
1944 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1946 If you specify an empty string for the color of a class, it is ignored
1947 in creating the stylesheet.
1948 You should not alter the class names, only the colour strings.<br />
1969 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1973 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1974 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1975 </ul>
1976 </dd>
1980 <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,
1981 as originally published on
1983 <br />
1984 For help in setting up your system to use the service, see the
1986 </dd>
1990 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1991 and any password, so we use those by default. Instead, if
1992 you have an account with them, you can put your login details
1993 here, and it will be used in place of the anonymous login.</dd>
1994 </dl>
1995 </dd>
1998 <dd><b>DEVELOPERS ONLY!</b></dd>
2001 <dd><b>DEVELOPERS ONLY!</b><br />
2002 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2003 the code.<br />
2004 For help in setting up your system to this, see the
2008 <dd><b>DEVELOPERS ONLY!</b><br />
2009 Enable profiling support for phpMyAdmin. This will append a chunk of data
2010 to the end of every page displayed in the main window with profiling
2011 statistics for that page.<br />
2012 You may need to increase the maximum execution time for this to
2013 complete successfully.<i>Profiling was removed from the code for
2014 version 2.9.0 due to licensing issues.</i></dd>
2016 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2017 <dd><b>DEVELOPERS ONLY!</b><br />
2018 When profiling data is displayed, this variable controls the threshold of
2019 display for any profiling data, based on the average time each time has
2020 taken. If it is over the threshold it is displayed, otherwise it is not
2021 displayed. This takes a value in milliseconds. In most cases you don't need
2022 to edit this.</dd>
2025 <dd>All possible types of a MySQL column. In most cases you don't need to
2026 edit this.</dd>
2029 <dd>Possible attributes for fields. In most cases you don't need to edit
2030 this.</dd>
2033 <dd>A list of functions MySQL supports. In most cases you don't need to
2034 edit this.</dd>
2037 <dd>Mapping of column types to meta types used for preferring displayed
2038 functions. In most cases you don't need to edit this.</dd>
2041 <dd>Functions preferred for column meta types as defined in
2042 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2043 to edit this.</dd>
2046 <dd>Functions selected by default when inserting/changing row, Functions
2047 are defined for meta types from
2049 <code>first_timestamp</code>, which is used for first timestamp column
2050 in table.</dd>
2053 <dd>Operators available for search operations on numeric and date fields.
2054 </dd>
2057 <dd>Operators available for search operations on character fields.
2058 Note that we put <code>LIKE</code> by default instead of
2059 <code>LIKE %...%</code>, to avoid unintended performance problems
2060 in case of huge tables.</dd>
2063 <dd>Operators available for search operations on enum fields.</dd>
2066 <dd>Additional operators available for search operations when the
2067 field can be null.</dd>
2069 </dl>
2071 <!-- TRANSFORMATIONS -->
2077 </ol>
2081 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2083 section</a> on how to do so.</p>
2085 <p> You can apply different transformations to the contents of each field. The
2086 transformation will take the content of each field and transform it with
2087 certain rules defined in the selected transformation.</p>
2089 <p> Say you have a field 'filename' which contains a filename. Normally you would
2090 see in phpMyAdmin only this filename. Using transformations you can transform
2091 that filename into a HTML link, so you can click inside of the phpMyAdmin
2092 structure on the field's link and will see the file displayed in a new browser
2093 window. Using transformation options you can also specify strings to
2094 append/prepend to a string or the format you want the output stored in.</p>
2096 <p> For a general overview of all available transformations and their options,
2097 you can consult your
2098 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2099 installation.</p>
2101 <p> For a tutorial on how to effectively use transformations, see our
2103 the official phpMyAdmin homepage.</p>
2107 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2108 clicking on the 'Structure' link for a table). There click on
2109 "Change" (or change icon) and there you will see three new fields at
2110 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2111 'Transformation options'.</p>
2113 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2114 that corresponds to the column's contents. Please note that
2115 transformations are inactive as long as no MIME-type is selected.</li>
2117 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2118 hopefully growing amount of pre-defined transformations. See below for information on
2119 how to build your own transformation.<br />
2121 There are global transformations and mimetype-bound transformations. Global transformations
2122 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2123 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2124 transformations which operate on the main mimetype (like 'image'), which will most likely
2125 take the subtype into regard, and those who only operate on a
2126 specific subtype (like 'image/jpeg').<br />
2128 You can use transformations on mimetypes for which the function was not defined for. There
2129 is no security check for you selected the right transformation, so take care of what the
2130 output will be like.</li>
2132 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2133 transform-function specific options here. Usually the transforms can operate with default
2134 options, but it is generally a good idea to look up the overview to see which options are
2135 necessary.<br />
2137 Much like the ENUM/SET-Fields, you have to split up several options using the format
2138 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2139 parsed as an array, leaving the first value the first element in the array, and so
2140 forth.<br />
2142 If you want to specify a MIME character set you can define it in the transformation_options.
2143 You have to put that outside of the pre-defined options of the specific mime-transform,
2145 for which you can specify 2 options and you want to append a character set, enter "'first
2146 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2148 </ul>
2152 <p> All mimetypes and their transformations are defined through single files in
2153 the directory 'libraries/transformations/'.</p>
2155 <p> They are stored in files to ease up customization and easy adding of new
2156 transformations.</p>
2158 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2159 always work. It makes no sense to apply a transformation to a mimetype, the
2160 transform-function doesn't know to handle.</p>
2162 <p> One can, however, use empty mime-types and global transformations which should work
2163 for many mimetypes. You can also use transforms on a different mimetype they where built
2164 for, but pay attention to option usage as well as what the transformation does to your
2165 field.</p>
2167 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2168 any other transform function and provides some basic functions.</p>
2170 <p> There are 5 possible file names:</p>
2172 <ol><li>A mimetype+subtype transform:<br /><br />
2174 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2176 Please not that mimetype and subtype are separated via '_', which shall
2177 not be contained in their names. The transform function/filename may
2178 contain only characters which cause no problems in the file system as
2179 well as the PHP function naming convention.<br /><br />
2181 The transform function will the be called
2182 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2184 <b>Example:</b><br /><br />
2186 <tt>text_html__formatted.inc.php</tt><br />
2187 <tt>PMA_transform_text_html__formatted()</tt></li>
2189 <li>A mimetype (w/o subtype) transform:<br /><br />
2191 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2193 Please note that there are no single '_' characters.
2194 The transform function/filename may contain only characters which cause
2195 no problems in the file system as well as the PHP function naming
2196 convention.<br /><br />
2198 The transform function will the be called
2199 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2201 <b>Example:</b><br /><br />
2203 <tt>text__formatted.inc.php</tt><br />
2204 <tt>PMA_transform_text__formatted()</tt></li>
2206 <li>A mimetype+subtype without specific transform function<br /><br />
2208 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2210 Please note that there are no '__' characters in the filename. Do not
2211 use special characters in the filename causing problems with the file
2212 system.<br /><br />
2214 No transformation function is defined in the file itself.<br /><br />
2216 <b>Example:</b><br /><br />
2218 <tt>text_plain.inc.php</tt><br />
2219 (No function)</li>
2221 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2223 <tt>[mimetype].inc.php</tt><br /><br />
2225 Please note that there are no '_' characters in the filename. Do not use
2226 special characters in the filename causing problems with the file system.
2227 <br /><br />
2229 No transformation function is defined in the file itself.<br /><br />
2231 <b>Example:</b><br /><br />
2233 <tt>text.inc.php</tt><br />
2234 (No function)</li>
2236 <li>A global transform function with no specific mimetype<br /><br />
2238 <tt>global__[transform].inc.php</tt><br /><br />
2240 The transform function will the be called
2241 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2243 <b>Example:</b><br /><br />
2245 <tt>global__formatted</tt><br />
2246 <tt>PMA_transform_global__formatted()</tt></li>
2247 </ol>
2249 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2250 transform function.</p>
2252 <p> All filenames containing no '__' in themselves are not shown as valid transform
2253 functions in the dropdown.</p>
2255 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2256 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2257 without a transform function. Also note the introduction of a function description in
2258 the language files. For each function a $strTransformation_[filename without .inc.php]
2259 has to exist.</p>
2261 <p> You can use the template generator to generate new functions and entries in the
2262 language file.</p>
2264 <p> To create a new transform function please see
2265 <tt>libraries/transformations/template_generator.sh</tt>.
2266 To create a new, empty mimetype please see
2267 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2269 <p> A transform function always gets passed three variables:</p>
2271 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2272 you want to transform.</li>
2273 <li><b>$options</b> - Contains any user-passed options to a transform function
2274 as an array.</li>
2275 <li><b>$meta</b> - Contains an object with field information to your column.
2276 The data is drawn from the output of the
2278 function. This means, all object properties described on the
2280 available in this variable and can be used to transform a field accordingly
2281 to unsigned/zerofill/not_null/... properties.<br />
2282 The $meta->mimetype variable contains the original MIME-type of the
2283 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2284 </ol>
2286 <!-- FAQ -->
2293 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2297 </ol>
2299 <p> Please have a look at our
2301 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2302 features and or interface.</p>
2308 action is required or phpMyAdmin sends a blank page or a page full of
2309 cryptic characters to my browser, what can I do?</a></h4>
2311 <p> There are some known PHP bugs with output buffering and compression.<br />
2313 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2314 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2315 configuration file.<br />
2316 Furthermore, we know about such problems connected to the release
2317 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2318 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2323 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2324 See also the
2326 entry about PHP bugs with output buffering.<br />
2327 If your server keeps crashing, please ask for help in the various Apache
2328 support groups.</p>
2332 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2333 script: I'm always displayed the login screen.</a></h4>
2335 <p> This is a known PHP bug (see this
2337 official PHP bug database. It means there is and won't be any phpMyAdmin
2338 fix against it because there is no way to code a fix.</p>
2344 application misbehaved by not returning a complete set of
2346 </h4>
2348 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2349 Have a look at the last message in this
2351 official PHP bug database.</p>
2356 and/or many error messages with the
2358 mode.</a></h4>
2360 <p> This is a known problem with the PHP
2362 filter: it's not so stable. Please use instead the cookie authentication mode.
2363 </p>
2368 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2369 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2370 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2371 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2372 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2377 work.</a></h4>
2379 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2380 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2381 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2382 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2383 We faced PHP crashes when trying to download a dump with MS Internet
2384 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2385 this case you should switch to the release version of PHP 4.2.0.</p>
2389 an error about safe mode being in effect.</a></h4>
2391 <p> Your uploaded file is saved by PHP in the "upload dir", as
2392 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2393 the system default is <i>/tmp</i>).<br />
2394 We recommend the following setup for Apache servers running in safe mode,
2395 to enable uploads of files while being reasonably secure:</p>
2397 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2398 <li>give ownership to the Apache server's user.group:
2399 <tt>chown apache.apache /tmp/php</tt></li>
2400 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2401 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2402 <li>restart Apache</li>
2403 </ul>
2407 general file uploads don't work on my system and uploaded files have a
2408 <tt>Content-Type:</tt> header in the first line.</a></h4>
2410 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2411 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2412 So the problem is that this package has a serious bug that was corrected
2413 ages ago in PHP (2001-01-28: see
2415 for more details). The problem is that the bugged package is still
2416 available though it was corrected (see
2418 for more details).<br />
2419 So please download
2420 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2421 and the problem should go away.<br />
2422 And that fixes the \r\n problem with file uploads!</p>
2426 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2427 I'm using the Apache server.</a></h4>
2429 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2430 your <i>httpd.conf</i>:</p>
2434 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2438 uploading a file from the query box.</a></h4>
2440 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2441 restrictions. Assuming that the restriction allows you to open files in the
2442 current directory ('.'), all you have to do is create a 'tmp' directory
2443 under the phpMyAdmin install directory, with permissions 777 and the same
2444 owner as the owner of your phpMyAdmin directory. The uploaded files will
2445 be moved there, and after execution of your
2451 <p> The MySQL manual explains how to
2453 reset the permissions</a>.</p>
2458 execute a bookmark.</a></h4>
2460 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2461 cannot access the uploaded query.</p>
2466 submit a query from the convenient text area.</a></h4>
2468 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2469 and try to increase it.</p>
2473 </h4>
2475 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2476 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2477 names to align with current standards.</p>
2482 </h4>
2484 <p> Starting with version 2.7.0, the import engine has been re–written and these
2485 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2486 to take advantage of the new import features.</p>
2488 <p> The first things to check (or ask your host provider to check) are the
2489 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2490 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2491 All of these three settings limit the maximum size of data that can be
2492 submitted and handled by PHP. One user also said that post_max_size
2493 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2495 There exist several workarounds if your upload is too big or your
2496 hosting provider is unwilling to change the settings:</p>
2499 feature. This allows one to
2500 upload a file to the server via scp, ftp, or your favorite file transfer
2501 method. PhpMyAdmin is then able to import the files from the temporary
2503 section</a> of this document.</li>
2505 BigDump</a>) to split the files before uploading. We cannot support this
2506 or any third party applications, but are aware of users having success
2507 with it.</li>
2508 <li>If you have shell (command line) access, use MySQL to import the files
2509 directly. You can do this by issuing the "source" command from
2510 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2511 </ul>
2515 support?</a></h4>
2517 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2518 fully supported. Please note that the older your MySQL version is, the more
2519 limitations you will have to face.<br />
2520 phpMyAdmin may connect to your MySQL server using php's classic
2523 is available in php 5.0.<br />
2524 Either way, the developers of both extensions recommend to use the classic
2525 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2526 When compiling php, we strongly recommend that you manually link the MySQL
2527 extension of your choice to a MySQL client library of at least the same
2528 minor version since the one that is bundled with some php distributions is
2531 If your webserver is running on a windows system, you might want to try
2532 MySQL's
2534 instead of the MySQL / MySQLi extensions that are bundled with the official
2535 php Win32 builds.
2536 <br />
2537 MySQL 5.1 is not yet supported.</p>
2541 message, "Client does not support authentication protocol requested
2542 by server; consider upgrading MySQL client"</a></h5>
2544 <p> You tried to access MySQL with an old MySQL client library. The version of
2545 your MySQL client library can be checked in your phpinfo() output.
2546 In general, it should have at least the same minor version as your server
2550 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2551 changed the authentication hash and your PHP is trying to use the old method.
2553 with the proper client library to match your MySQL installation. Your
2554 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2555 More information (and several workarounds) are located in the
2557 </p>
2561 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2562 capital letter in its name it is changed to lowercase as it should. But
2563 if I try to DROP this table MySQL is unable to find the corresponding
2564 file.</a></h4>
2566 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2567 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2568 directive.</p>
2572 script seems not to know the font face I'm using!</a></h4>
2574 <p> The "FPDF" library we're using for this feature requires some
2575 special files to use font faces.<br />
2577 these files.</p>
2581 check PHP Configuration".</a></h4>
2583 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2584 "MySQL extension". This extension may be part of the PHP
2585 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2586 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2587 to load the extension but failed.<br /><br />
2589 Usually, the problem is solved by installing a software package called
2590 "PHP-MySQL" or something similar.</p>
2595 and I cannot log in using cookie auth.</a></h4>
2597 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2601 so I cannot upload.</a></h4>
2603 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2604 parameter is not set to "on".</p>
2608 a new table the table and field names are changed to lowercase!</a></h4>
2610 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2611 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2612 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2613 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2614 directory and add the following line to the group [mysqld]:</p>
2616 <pre>set-variable = lower_case_table_names=0</pre>
2618 <p> Next, save the file and restart the MySQL service. You can always check the
2619 value of this directive using the query</p>
2621 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2625 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2628 </p>
2632 and I get problems, such as undefined variables when I run a
2635 <p> A tip from Jose Fandos: put a comment on the following two lines
2636 in httpd.conf, like this:</p>
2638 <pre>
2639 # mod_gzip_item_include file \.php$
2641 </pre>
2643 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2644 PHP scripts. Of course you have to restart Apache.</p>
2649 I get the error "No input file specified" when trying to
2650 run phpMyAdmin.</a></h4>
2652 <p> This is a permission problem. Right-click on the phpmyadmin folder
2653 and choose properties. Under the tab Security, click on "Add"
2654 and select the user "IUSR_machine" from the list. Now set his
2655 permissions and it should work.</p>
2659 db_structure.php with plenty of tables).</a></h4>
2662 GZIP output buffering is enabled. If you turn off it (by
2664 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2665 PHP 5.0.0.</p>
2669 message 'Errorcode: 13'. What does this mean?</a></h4>
2671 <p> This can happen due to a MySQL bug when having database / table names with
2672 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2673 To fix this, turn off this directive, convert all database and table names
2674 to lower case and turn it on again. Alternatively, there's a bug-fix
2675 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2679 and the fields are duplicated.</a></h4>
2681 <p> It is possible to configure Apache in such a way that PHP has problems
2682 interpreting .php files.</p>
2684 <p> The problems occur when two different (and conflicting) set of directives
2685 are used:</p>
2687 <pre>
2688 SetOutputFilter PHP
2689 SetInputFilter PHP
2690 </pre>
2692 <p> and</p>
2694 <pre>AddType application/x-httpd-php .php</pre>
2696 <p> In the case we saw, one set of directives was in
2697 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2698 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2699 The recommended way is with <tt>AddType</tt>, so just comment out
2700 the first set of lines and restart Apache:</p>
2702 <pre>
2703 #SetOutputFilter PHP
2704 #SetInputFilter PHP
2705 </pre>
2710 <p> This problem is known to happen when the server is running Turck MMCache
2711 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2716 <p> Yes.<br />
2717 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2718 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2719 <tt>error_reporting</tt> settings.
2720 </p>
2723 <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>
2725 <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>
2728 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2729 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2730 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2731 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2732 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2733 enabled.) Click <tt>OK</tt>.</li>
2734 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2735 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2736 </ol>
2740 PHP 5.0.4 on 64-bit systems?</a></h4>
2742 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2743 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2749 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2750 Table and script parts are optional. If you want
2751 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2752 some configuration. Following lines apply only for <a
2754 that you have enabled some features within global configuration. You need
2755 <code>Options FollowSymLinks</code> and <code>AllowOverride
2756 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2757 you need mod_rewrite to be enabled. Then you just need to create following
2758 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2759 (don't forget to change directory name inside of it):</p>
2761 <pre>
2762 RewriteEngine On
2763 RewriteBase /path_to_phpMyAdmin
2764 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2765 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2766 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2767 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2768 </pre>
2771 <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>
2773 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2774 following rewrite rule:</p>
2776 <pre>
2777 RewriteEngine On
2778 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2779 </pre>
2783 </h4>
2784 <p>
2785 There can be many explanations to this and a look at your server's
2786 error log file might give a clue.
2787 </p>
2791 password encryption in cookie auth doesn't work.</a></h4>
2793 <p> If your cluster consist of different architectures, PHP code used for
2794 encryption/decryption won't work correct. This is caused by use of
2795 pack/unpack functions in code. Only solution is to use mcrypt extension
2796 which works fine in this case.</p>
2802 headers already sent by ..." is displayed, what's the problem?</a></h4>
2804 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2805 (I.E. no blank lines, no spaces, no characters...) neither before the
2806 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2807 tag at the end. We also got a report from a user under IIS, that used
2808 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2809 contained an end-of-line character (hex 0A) at the end; removing this character
2810 cleared his errors.</p>
2815 <p> Either there is an error with your PHP setup or your username/password is
2816 wrong. Try to make a small script which uses mysql_connect and see if it
2817 works. If it doesn't, it may be you haven't even compiled MySQL support
2818 into PHP.</p>
2822 connect to local MySQL server through socket '/tmp/mysql.sock'
2823 (111) ..." is displayed. What can I do?</a></h4>
2825 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2827 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2828 In your <i>php.ini</i> you will find a line</p>
2830 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2832 <p> change it to</p>
2834 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2836 <p> Then restart apache and it will work.</p>
2838 <p> Here is a fix suggested by Brad Ummer:</p>
2840 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2841 To do this, telnet to your server and go to the MySQL bin directory. In
2842 this directory there should be a file named <i>mysqladmin</i>. Type
2843 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2844 info about your MySQL server, including the socket
2845 (<i>/tmp/mysql.sock</i>, for example).</li>
2846 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2847 phpMyAdmin, you need to complete the socket information in the
2848 <i>config.inc.php</i>.<br />
2849 For example:
2851 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2852 <br /><br />
2854 Please also make sure that the permissions of this file allow to be readable
2855 by your webserver (i.e. '0755').</li>
2856 </ul>
2858 <p> Have also a look at the
2860 corresponding section of the MySQL documentation</a>.</p>
2864 what can I do?</a></h4>
2867 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2868 sometime.<br />
2869 Also have a look at your PHP version number: if it contains "4.0b..."
2870 it means you're running a beta version of PHP. That's not a so good idea,
2871 please upgrade to a plain revision.</p>
2875 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2876 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2878 <p> Check the value you set for the
2880 directive in the phpMyAdmin configuration file.</p>
2884 password: YES)"-error when trying to access a MySQL-Server on a
2885 host which is port-forwarded for my localhost.</a></h4>
2887 <p> When you are using a port on your localhost, which you redirect via
2888 port-forwarding to another host, MySQL is not resolving the localhost
2889 as expected.<br />
2890 Erik Wasser explains: The solution is: if your host is "localhost"
2891 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2892 connection for speeding up things. And that doesn't work in this configuration
2893 with port forwarding.<br />
2899 <p> Themes are configured with
2903 <br />
2905 should not delete the directory "original" or its underlying
2906 structure, because this is the system theme used by phpMyAdmin.
2907 "original" contains all images and styles, for backwards
2908 compatibility and for all themes that would not include images or css-files.
2909 <br /><br />
2912 is enabled, you can select your favorite theme on the main page. Your
2913 selected theme will be stored in a cookie.<br /><br /></p>
2915 <p> To create a theme:</p>
2917 <ul><li>make a new subdirectory (for example "your_theme_name") under
2919 (by default <tt>themes</tt>)</li>
2920 <li>copy the files and directories from "original" to
2921 "your_theme_name"</li>
2922 <li>edit the css-files in "your_theme_name/css"</li>
2923 <li>put your new images in "your_theme_name/img"</li>
2924 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2925 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2926 contain your chosen theme name, that will be visible in user interface</li>
2927 <li>make a new screenshot of your theme and save it under
2928 "your_theme_name/screen.png"</li>
2929 </ul>
2931 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2932 theme verbose name, theme generation and theme version. These versions and
2933 generations are enumerated from 1 and do not have any direct dependence on
2934 phpMyAdmin version. Themes within same generation should be backwards
2935 compatible - theme with version 2 should work in phpMyAdmin requiring
2936 version 1. Themes with different generation are incompatible.</p>
2938 <p> If you do not want to use your own symbols and buttons, remove the
2939 directory "img" in "your_theme_name". phpMyAdmin will
2940 use the default icons and buttons (from the system-theme "original").
2941 </p>
2945 what can I do?</a></h4>
2947 <p> Here are a few points to check:</p>
2949 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2951 directive empty. See also
2953 </li>
2954 <li>Maybe you have a broken PHP installation or you need to upgrade
2955 your Zend Optimizer. See
2957 http://bugs.php.net/bug.php?id=31134</a>.
2958 </li>
2959 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2960 set to the default (200) or another low value, you could get this
2961 error if your table has a high number of columns. Adjust this setting
2962 accordingly. (Thanks to Klaus Dorninger for the hint).
2963 </li>
2964 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2965 of ";" will cause this error. Replace it with "&;".
2966 </li>
2968 you might want to increase
2970 </li>
2971 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
2972 </li>
2973 </ul>
2980 who logged out can not log in again in with the same nick.</a></h4>
2982 <p> This is related to the authentication mechanism (protocol) used by
2983 phpMyAdmin. To bypass this problem: just close all the opened
2984 browser windows and then go back to phpMyAdmin. You should be able to
2985 log in again.</p>
2989 limit error or a time limit error.</a></h4>
2991 <p> Compressed dumps are built in memory and because of this are limited to
2992 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2993 using
2995 (enabled by default). Zip exports can not be handled this way, so if you need
2996 Zip files for larger dump, you have to use another way.</p>
3000 or alter a table.</a></h4>
3002 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3006 bundled with the MySQL server distribution.</a></h4>
3008 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3010 <pre>
3011 -- MySQL dump 8.22
3012 --
3013 -- Host: localhost Database: database
3014 ---------------------------------------------------------
3015 -- Server version 3.23.54
3016 </pre>
3018 <p> The invalid part of the code is the horizontal line made of dashes that
3019 appears once in every dump created with mysqldump. If you want to run your
3020 dump you have to turn it into valid MySQL. This means, you have to add a
3021 whitespace after the first two dashes of the line or add a # before it:
3022 <br />
3023 <code>
3024 -- -------------------------------------------------------<br />
3025 </code>
3026 or<br />
3027 <code>
3028 #---------------------------------------------------------
3029 </code>
3030 </p>
3037 <p> Please note that you should not use the separating string multiple times
3038 without any characters between them, or at the beginning/end of your table
3039 name. If you have to, think about using another TableSeparator or disabling
3040 that feature</p>
3045 <p> In Relation view, being able to choose a table in another database,
3046 or having more than one index field in the foreign key.<br /><br/>
3047 In Query-by-example (Query), automatic generation of the query
3048 LEFT JOIN from the foreign table.<br /><br/>
3049 </p>
3053 I get series of errors like "Warning: unable to parse url". How
3054 can this be fixed?</a></h4>
3055 <p>
3056 Your table neither have a primary key nor an unique one, so we must use a
3057 long expression to identify this row. This causes problems to parse_url
3058 function. The workaround is to create a primary or unique key.
3059 <br />
3060 </p>
3064 a MIME-Transformation onto!</a></h4>
3066 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3067 nested forms can be put inside the table where phpMyAdmin displays the results.
3068 You can, however, use any form inside of a table if keep the parent
3069 form-container with the target to tbl_row_delete.php and just put your own
3070 input-elements inside. If you use a custom submit input field, the form will
3071 submit itself to the displaying page again, where you can validate the
3072 $HTTP_POST_VARS in a transformation.
3074 For a tutorial on how to effectively use transformations, see our
3076 on the official phpMyAdmin-homepage.</p>
3080 MySQL server</a></h4>
3082 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3085 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3086 the quote-character (") is interpreted as an identifier quote character and
3087 not as a string quote character, which makes many internal phpMyAdmin
3089 statements. There is no workaround to this behaviour. News to this item will
3090 be posted in Bug report
3091 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3092 </p>
3096 more that one column with the same value
3097 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3098 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3100 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3101 can use it for the Edit and Delete links.</p>
3106 <p> phpMyAdmin uses a quick method to get the row count, and this method
3107 only returns an approximate count in the case of InnoDB tables. See
3109 a way to modify those results, but
3110 this could have a serious impact on performance.</p>
3115 <p> The number of records in queries containing COUNT and GROUP BY is
3116 not correctly calculated. Also, sorting results of a query like
3121 containing an hyphen.
3122 </a></h4>
3123 <p>
3124 The tests I have made with current MySQL 4.1.11 API shows that the
3125 API does not accept this syntax for the USE command. Enclosing the
3126 db name with backquotes works. For further confusion, no backquotes
3127 are needed with command-line mysql.
3128 </p>
3131 <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>
3132 <p>
3133 This has been a known limitation of phpMyAdmin since the beginning and
3134 it's not likely to be solved in the future.
3135 </p>
3137 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3140 <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
3141 need to install it for each customer.
3142 </a></h4>
3143 <p>
3144 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3145 your users. The development of this feature was kindly sponsored by
3146 NetCologne GmbH.
3147 This requires a properly setup MySQL user management and phpMyAdmin
3148 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3150 </p>
3154 access.
3155 </a></h4>
3156 <p>
3157 This depends on your system.<br />
3158 If you're running a server which cannot be accessed by other people, it's
3159 sufficient to use the directory protection bundled with your webserver
3161 If other people have telnet access to your server, you should use
3162 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3163 <br /><br />
3164 Suggestions:
3165 </p>
3166 <ul>
3167 <li>
3169 </li>
3170 <li>
3171 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3172 is a user whose password is only known to you, and apache is the
3173 group under which Apache runs.
3174 </li>
3175 <li>
3176 You should use PHP safe mode, to protect from other users that try
3178 </li>
3179 </ul>
3184 </a></h4>
3185 <p>
3190 </p>
3193 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3194 authentication.
3195 </a></h4>
3199 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3200 and/or
3202 are wrong.</li>
3204 <li>You have already setup a security mechanism for the
3205 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3206 phpMyAdmin's authentication, so remove it.</li>
3207 </ul>
3214 and put the privileges you want. For example,
3216 would let a user create/manage his/her database(s).</p>
3221 <p> If you have existing rules from an old .htaccess file, you can take them
3224 be a major benefit here if your installation is suited to using it. Then
3225 you can just add those updated lines into the
3229 <p> If you want a pre-made sample, you can try this fragment. It stops the
3230 'root' user from logging in from any networks other than the private
3233 <pre>
3234 //block root from logging in except from the private networks
3235 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3236 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3237 'deny root from all',
3238 'allow root from localhost',
3242 );
3243 </pre>
3248 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3249 different than the one set in your
3251 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3252 while a domain name is defined in the config file.</p>
3257 <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>
3263 when trying to create a table with more than 14 fields.
3264 </a></h4>
3265 <p>
3266 We could reproduce this problem only under Win98/98SE. Testing under
3267 WinNT4 or Win2K, we could easily create more than 60 fields.
3268 <br />
3269 A workaround is to create a smaller number of fields, then come back to
3270 your table properties and add the other fields.
3271 </p>
3275 <p>
3276 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3277 with each script/website that use forms.<br />
3278 Upgrade or downgrade your Xitami server.
3279 </p>
3282 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3283 <p>
3284 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3285 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3286 don't seem to work.<br />
3288 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3289 the user's temporary directory, so they must be moved before closing
3290 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3293 </p>
3297 Explorer never stores the cookies.
3298 </a></h4>
3299 <p>
3300 MS Internet Explorer seems to be really buggy about cookies, at least till
3302 in this area!
3303 <br />
3304 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3305 work!
3306 </p>
3310 rows.
3311 </a></h4>
3312 <p>
3314 </p>
3317 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3318 when trying to modify a row in a table with many fields, or with a text field
3319 </a></h4>
3320 <p>
3321 Your table neither have a primary key nor an unique one, so we must use a
3322 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
3323 those browsers, and this not happen in Netscape, for example. The
3324 workaround is to create a primary or unique key, or use another browser.
3325 <br />
3326 </p>
3330 page.
3331 </a></h4>
3332 <p>
3333 Some browsers support right-clicking into the frame you want to refresh,
3334 just do this in the right frame.<br />
3335 </p>
3339 query box.
3340 </a></h4>
3341 <p>
3342 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3343 Mozilla versions.<br />
3344 </p>
3348 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3349 </a></h4>
3350 <p>
3351 This is a Mozilla bug (see bug #26882 at
3353 </p>
3358 </a></h4>
3359 <p>
3360 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3361 data in octet-stream mode. Since we can't detect the specific Netscape
3362 version, we cannot workaround this bug.
3363 </p>
3367 wrong.</a></h4>
3369 <p> Please ensure that you have set your browser's character set to the one of the
3370 language file you have selected on phpMyAdmin's start page.
3371 Alternatively, you can try the auto detection mode that is supported by the
3372 recent versions of the most browsers.</p>
3375 <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
3378 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3379 Netscape and Mozilla do not have this problem.</p>
3382 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3383 I cannot manage two servers: I log in to the first one, then the other one,
3384 but if I switch back to the first, I have to log in on each operation.</a></h4>
3390 but nothing happens after that, only a blank screen.</a></h4>
3393 bug in Opera6, because it is not able to interpret frameset definitions
3394 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3395 Opera7 at least.</p>
3404 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3409 address and you are starting
3411 containing a domain name, or the reverse situation.</li>
3412 <li>Security settings in IE and/or Microsoft Security Center are
3413 too high, thus blocking scripts execution.</li>
3414 <li>The Windows Firewall is blocking Apache and MySQL. You must
3418 </ul>
3421 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3422 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3423 installed in their Firefox is causing the problem.</p>
3430 </a></h4>
3431 <p>
3432 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3433 specifying a wrong field-type.<br />
3434 Common errors include:
3435 </p>
3436 <ul>
3439 </ul>
3440 <p>
3441 Also, look at the syntax chapter in the MySQL manual to confirm that your
3442 syntax is correct.
3443 </p>
3447 phpMyAdmin generates only one index with those 2 fields.
3448 </a></h4>
3449 <p>
3451 index. If you want two indexes, create the first one when creating the
3452 table, save, then display the table properties and click the Index link to
3453 create the other index.
3454 </p>
3458 <p>
3459 Since version 2.2.3, you have a checkbox for each field that can be null.
3461 field's value. Since version 2.5.5, you have to use the checkbox to get
3463 a literal NULL in the field, and not a NULL value (this works in PHP4).
3464 </p>
3469 <p> Click on a database or table name in the left frame, the properties will be
3471 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3472 statements that can be used to recreate your database/table.
3473 <br /><br />
3475 transmit the resulting dump to your station. Depending on your PHP
3476 configuration, you will see options to compress the dump. See also the
3478 configuration variable.<br /><br />
3481 this document.</p>
3486 </a></h4>
3488 <p> Click on a database name in the left frame, the properties will be
3490 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3492 the path to your dump filename, or use the Browse button. Then click Go.
3493 <br /><br />
3495 that you upgrade to take advantage of the new features.
3496 <br /><br />
3498 in this document.
3499 </p>
3504 <p> Here is an example with the tables persons, towns and countries, all
3506 table, create it as explained in the configuration section. Then create the
3507 example tables:</p>
3509 <pre>
3510 CREATE TABLE REL_countries (
3511 country_code char(1) NOT NULL default '',
3512 description varchar(10) NOT NULL default '',
3513 PRIMARY KEY (country_code)
3514 ) TYPE=MyISAM;
3516 INSERT INTO REL_countries VALUES ('C', 'Canada');
3518 CREATE TABLE REL_persons (
3519 id tinyint(4) NOT NULL auto_increment,
3520 person_name varchar(32) NOT NULL default '',
3522 country_code char(1) NOT NULL default '',
3523 PRIMARY KEY (id)
3524 ) TYPE=MyISAM;
3526 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3527 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3529 CREATE TABLE REL_towns (
3531 description varchar(30) NOT NULL default '',
3532 PRIMARY KEY (town_code)
3533 ) TYPE=MyISAM;
3535 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3536 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3537 </pre>
3543 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3547 </ul>
3555 <li>In the fields row, choose persons.person_name and click the
3557 <li>Do the same for towns.description and countries.descriptions in the
3560 the correct joins have been generated</li>
3562 </ul>
3566 <p>
3567 Starting from the previous example, create the pma_table_info as explained
3568 in the configuration section, then browse your persons table,
3569 and move the mouse over a town code or country code.
3570 <br /><br />
3571 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3572 enables: drop-down list of possible values.
3573 </p>
3576 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3577 <p>
3580 <br /><br />
3581 Then you need to think about your schema layout. Which tables will go on
3582 which pages?
3583 </p>
3584 <ul>
3590 page and click Go. If you like, you
3592 linked tables onto the new page.</li>
3593 <li>Select the name of the new page (making sure the Edit radio button
3594 is selected) and click Go.</li>
3596 Coordinates are relative; your diagram will
3597 be automatically scaled to fit the page. When initially placing tables
3598 on the page, just pick any coordinates -- say, 50x50. After clicking
3600 position the element correctly.</li>
3602 first be sure to click the Save
3603 button beneath the list of tables and coordinates, to save any changes
3604 you made there. Then scroll all the way down, select the
3606 you want, and click Go.</li>
3607 <li>Internet Explorer for Windows may suggest an incorrect filename when
3612 browsers on Windows, do not have this problem.</li>
3613 </ul>
3617 columns!</a></h4>
3619 <p> No, it's MySQL that is doing
3625 underscores in the database name?</a></h4>
3627 <p> If you do not put a backslash before the underscore, this is a wildcard
3630 john2db ...<br /><br />
3632 If you put a backslash before the underscore, it means that the database
3633 name will have a real underscore.</p>
3637 statistics pages?</a></h4>
3648 if it already exists during the import. It does NOT drop the table after
3649 your export, it only affects the import file.</li>
3651 Otherwise, you may get an error if the table name exists but has a
3652 different structure.</li>
3654 (if any) will be included in backup.</li>
3656 field and table names formed with special characters are protected.</li>
3658 types set in the pmadb in the dump as
3660 </li>
3661 </ul>
3666 command, for better documentation (but resulting file is bigger).</li>
3668 once the INSERT verb and the table name.</li>
3671 </li>
3673 more info is provided in the
3675 but basically with this selected, invalid values are adjusted and
3676 inserted rather than causing the entire statement to fail.</li>
3677 </ul>
3681 in its name.</a></h4>
3684 is the normal way to reference a database and table name. Worse, MySQL
3685 will usually let you create a database with a dot, but then you cannot
3686 work with it, nor delete it.</p>
3699 for usage.<br />
3700 On a more recent pear version, I had problems with the state of Net_DIME
3701 being beta, so this single command
3703 needed modules.<br />
3704 If you use the Validator, you should be aware that any
3706 submit will be stored anonymously (database/table/column names,
3707 strings, numbers replaced with generic values). The Mimer
3710 We utilize it as free SOAP service.</p>
3714 it, but MySQL says "BLOB column '...' used in key specification without
3717 <p> The right way to do this, is to create the field without any indexes,
3719 dialog. On this page, you will be able to choose your BLOB field, and
3720 set a size to the index, which is the condition to create an index on
3721 a BLOB field.</p>
3725 editing fields?</a></h4>
3727 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3728 with many editing fields (table structure changes, row editing, etc.)
3729 (must be enabled in configuration - see.
3731 You can also have a look at the directive
3733 ('vertical') and see if this eases up editing for you.</p>
3737 WTF is this feature then useful for?</a></h4>
3739 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3740 on them. Otherwise you could just put a comment on the field. Because entering
3741 your own mimetype will cause serious syntax checking issues and validation,
3742 this introduces a high-risk false-user-input situation. Instead you have to
3743 initialize mimetypes using functions or empty mimetype definitions.<br />
3744 Plus, you have a whole overview of available mimetypes. Who knows all those
3745 mimetypes by heart so he/she can enter it at will?</p>
3749 can't I see any bookmarks below the query box? What is this variable for?
3750 </a></h4>
3752 <p> Any query you have executed can be stored as a bookmark on the page where the
3753 results are displayed. You will find a button labeled 'Bookmark this query'
3754 just at the end of the page.<br />
3755 As soon as you have stored a bookmark, it is related to the database you run
3756 the query on. You can now access a bookmark dropdown on each page, the query
3757 box appears on for that database.<br /><br />
3759 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3763 aware of that you HAVE to create a valid query, otherwise your query won't be
3764 even able to be stored in the database.<br />
3766 for your query will remain the way it is, but will be stripped of the /**/
3767 chars. So you can use:<br /><br />
3771 which will be expanded to<br /><br />
3775 in your query, where VARIABLE is the string you entered in the input box. If
3776 an empty string is provided, no replacements are made.<br /><br />
3778 A more complex example. Say you have stored this query:<br /><br />
3780 <br /><br />
3783 the full query will be:<br /><br />
3786 <br /><br />
3790 spaces inserted there
3791 will be later also inserted as spaces in your query and may lead to unexpected
3792 results especially when
3794 Your initial query which is going to be stored as a bookmark has to yield at
3795 least one result row so
3796 you can store the bookmark. You may have that to work around using well
3800 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3801 include exported table?</a></h4>
3803 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3804 document should look like following one (assuming you have table
3807 <pre>
3808 \documentclass{article} % or any class you want
3809 \usepackage{longtable} % for displaying table
3810 \begin{document} % start of document
3811 \include{table} % including exported table
3812 \end{document} % end of document
3813 </pre>
3817 access them.
3818 </a></h4>
3821 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3822 enable users to see all the database names.
3825 So if your users do not need those privileges, you can remove them and their
3826 databases list will shorten.</p>
3830 possible values for a field, based on some foreign table?</a></h4>
3832 <p> You have to setup appropriate links between the tables, and also
3836 foreign table, a drop-down list of values will be available.
3837 You will see two lists of values, the first list containing the key
3838 and the display field, the second list containing the display field
3839 and the key. The reason for this is to be able to type the first
3840 letter of either the key or the display field.<br /><br />
3842 For 200 values or more, a distinct window will appear, to browse foreign
3843 key values and choose one.</p>
3847 automatically when entering Browse mode for a table?</a></h4>
3849 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3850 </p>
3854 Excel files, how can I enable that?</a></h4>
3856 <p> Current version does support direct export to Microsoft Excel and Word
3857 versions 2000 and newer. If you need export older versions, you can use
3859 which works out of the box or you can
3861 several problems, most important are limitation of cell content to 255
3862 chars and no support for charsets, so think carefully whether you want to
3863 enable this.</b>. For enabling this you need to set
3867 module Spreadsheet_Excel_Writer into php include path. The
3868 installation can be done by following command:</p>
3870 <pre>
3871 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3872 </pre>
3874 <p> First part of switches set we want to install beta version of that module
3875 (no stable version available yet) and then we tell pear we want to satisfy
3876 dependencies.</p>
3878 <p> If you are running in PHP safe mode, you will have to set
3881 modules are located, for example:</p>
3883 <pre>
3884 safe_mode_include_dir = /usr/local/lib/php
3885 </pre>
3889 <pre>
3890 cd phpMyAdmin
3891 mkdir tmp
3892 chmod o+rwx tmp
3893 </pre>
3897 what happens to my column comments stored in pmadb?</a></h4>
3899 <p> Automatic migration of a table's pmadb-style column comments to the native
3900 ones is done whenever you enter Structure page for this table.</p>
3907 <p> Our Bug Tracker is located at
3909 under the Bugs section.<br /><br />
3911 But please first discuss your bug with other users:<br />
3917 existing language, where do I start?</a></h4>
3919 <p> Always use the current SVN version of your language file.
3921 don't know how to get the SVN version, please ask one of the developers.
3922 <br />
3923 Please note that we try not to use HTML entities like &eacute; in
3924 the translations, since we define the right character set in the file.
3925 With HTML entities, the text on JavaScript messages would not
3926 display correctly.
3927 However there are some entities that need to be there, for quotes
3928 ,non-breakable spaces, ampersands, less than, greater than.<br />
3929 You can then put your translations, as a zip file to avoid losing special
3930 characters, on the sourceforge.net translation tracker.<br />
3931 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3932 list, because this is where we ask for translations of new messages.</p>
3936 phpMyAdmin. How should I proceed?</a></h4>
3942 </li>
3944 <li>generate patch with your changes:
3946 </li>
3949 tracker of the phpMyAdmin project</a>.
3950 </li>
3951 </ol>
3953 <p> Write access to the SVN tree is granted only to experienced developers who
3954 have already contributed something useful to phpMyAdmin.<br />
3960 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3962 <p> Please refer to
3963 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3964 </p>
3966 <!-- DEVELOPERS -->
3969 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3970 great features have been written by other people and you too can help to
3971 make phpMyAdmin a useful tool.</p>
3973 <p> If you're planning to contribute source, please read the following
3974 information:</p>
3980 it free from other code.<br />
3981 Commonly used functions should be added to
3984 <li>Obviously, you're free to use whatever coding style you want. But
3985 please try to keep your code as simple as possible: beginners are
3986 using phpMyAdmin as an example application.<br />
3987 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3988 compliant on one hand, they fit the
3991 coding standards</a>
3992 on the other hand. Please pay attention to this.</li>
3993 <li>Please try to keep up the file-naming conventions. Table-related stuff
3996 <li>Please don't use verbose strings in your code, instead add the string
4001 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4002 better debug and profile their code.<br />
4003 Please see the
4005 options for more information.<br />
4006 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4007 lost during its re-entry into Earth's atmosphere and in memory of the
4008 brave men and women who gave their lives for the people of Earth.</li>
4009 </ul>
4011 <!-- CREDITS -->
4014 <pre>
4015 phpMyAdmin - Credits
4016 ====================
4018 CREDITS, in chronological order
4019 -------------------------------
4022 * creator of the phpmyadmin project
4026 * multi-language version
4027 * various fixes and improvements
4029 * current project maintainer
4032 * started SourceForge phpMyAdmin project in March 2001
4033 * sync'ed different existing CVS trees with new features and bugfixes
4034 * multi-language improvements, dynamic language selection
4035 * current project maintainer
4036 * many bugfixes and improvements
4039 * rewrote and optimized javascript, DHTML and DOM stuff
4040 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4041 generate XHTML1.0 and CSS2 compliant codes
4042 * improved the language detection system
4043 * many bugfixes and improvements
4046 * database maintenance controls
4047 * table type code
4049 * DB-based configuration (Not completed)
4052 * many bugfixes and improvements
4055 * bookmarks feature
4056 * multiple dump feature
4057 * gzip dump feature
4058 * zip dump feature
4061 * various fixes
4062 * moderator of the phpMyAdmin former users forum at phpwizard.net
4068 * rewrote and fix dump code
4069 * bugfixes
4072 * rewrote dump code for PHP4
4073 * mySQL table statistics
4074 * bugfixes
4077 * main author of the version 2.1.0.1
4078 * bugfixes
4082 * abstract database interface (PMA_DBI) with MySQLi support
4083 * privileges administration
4085 * various features and fixes
4086 * German language file updates
4089 * automatic joins in QBE
4090 * links column in printview
4091 * Relation view
4094 * enhanced index creation/display feature
4095 * feature to use a different charset for HTML than for MySQL
4096 * improvements of export feature
4097 * various features and fixes
4098 * Czech language file updates
4101 (http://sf.net/projects/phpmysqlformgen/)
4102 * suggested the patch for multiple table printviews
4105 * built the patch for vertical display of table rows
4106 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4107 * Improvement of column/db comments
4108 * (MIME)-Transformations for columns
4109 * Use custom alias names for Databases in left frame
4110 * hierarchical/nested table display
4111 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4112 * new icon sets
4113 * vertical display of column properties page
4114 * some bugfixes, features, support, German language additions
4117 * japanese kanji encoding conversion feature
4120 * the Cookie authentication mode
4123 * table relation-links feature
4126 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4127 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4128 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4134 * phpMyAdmin logo (until June 2004)
4137 * blowfish library from the Horde project
4140 * mysqli support
4141 * many bugfixes and improvements
4144 * redesign for 2.6.0
4145 * phpMyAdmin sailboat logo (June 2004)
4148 * Representation at conferences
4151 * interface improvements
4152 * various bugfixes
4154 - Ivan A Kirillov
4155 * new relations Designer
4157 And also to the following people who have contributed minor changes,
4158 enhancements, bugfixes or support for a new language since version 2.1.0:
4160 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4161 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4162 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4163 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4165 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4166 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4167 Luís V., Martijn W. van der Lee,
4168 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4172 Original Credits of Version 2.1.0
4173 ---------------------------------
4175 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4176 to create a web-based interface to MySQL using PHP3. Although I have not
4177 used any of his source-code, there are some concepts I've borrowed from
4178 him. phpMyAdmin was created because Peter told me he wasn't going to
4179 further develop his (great) tool.
4180 Thanks go to
4182 code for the check when dropping a table or database. He also suggested
4183 that you should be able to specify the primary key on tbl_create.php3. To
4184 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4185 well as a bug-report. Plus many smaller improvements.
4187 were introduced in 1.3.0 (including quite significant ones like the
4188 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4189 bug-fixes and help.
4191 language-independent by outsourcing the strings to a separate file. He
4192 also contributed the French translation.
4194 tbl_select.php3, a feature to display only some fields from a table.
4196 functions in tbl_change.php3. He also added the
4199 servers and is a regular contributor for bug-fixes.
4201 features for 2.0.6.
4202 The following people have contributed minor changes, enhancements, bugfixes
4203 or support for a new language:
4204 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4205 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4206 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4207 G. Wieggers.
4209 And thanks to everyone else who sent me email with suggestions, bug-reports
4210 and or just some feedback.
4211 </pre>
4217 <ul>
4219 - the default name of Apache's directory-level configuration file.</li>
4223 - a software application that enables a user to display and interact with
4224 text, images, and other information typically located on a web page at a
4225 website on the World Wide Web.</li>
4227 - a free software/open source data compression algorithm and program
4228 developed by Julian Seward.</li>
4230 - an important World Wide Web technology that enables a client web browser
4231 to request data from a program executed on the Web server.</li>
4233 - a log or record of changes made to a project.</li>
4235 - a computer system that accesses a (remote) service on another computer
4236 by some kind of network.</li>
4238 - a set of data values of a particular simple type, one for each row of
4239 the table.</li>
4241 - a packet of information sent by a server to a World Wide Web browser
4242 and then sent back by the browser each time it accesses that server.</li>
4244 - Comma-seperated values</li>
4247 - an organized collection of data.</li>
4250 - a PHP module that extends PHP with additional functionality.</li>
4252 - a list of commonly asked question and there answers.</li>
4254 - one part of divided data/columns.</li>
4256 - a field or group of fields in a database record that point to a key
4257 field or group of fields forming a key of another database record in some
4258 (usually different) table.</li>
4260 - the free PDF library</li>
4262 GD Graphics Library</a> - a library by Thomas Boutell and others for
4263 dynamically manipulating images.</li>
4266 - gzip is short for GNU zip, a GNU free software file compression
4267 program.</li>
4269 - any machine connected to a computer network, a node that has a hostname.</li>
4271 - the unique name by which a network attached device is known on a network.</li>
4273 (HyperText Transfer Protocol)</a>
4274 - the primary method used to transfer or convey information on the World
4275 Wide Web.</li>
4278 additional security measures.</li>
4279 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4280 - a set of Internet-based services for servers using Microsoft Windows.</li>
4282 - a feature that allows quick access to the rows in a table.</li>
4284 - a data-oriented protocol used by source and destination hosts for
4285 communicating data across a packet-switched internetwork.</li>
4287 - a unique number that devices use in order to identify and communicate
4288 with each other on a network utilizing the Internet Protocol standard.</li>
4290 (Internet Server Application Programming Interface)</a>
4291 - the API of Internet Information Services (IIS).</li>
4293 - a business or organization that offers users access to the Internet and related services.</li>
4295 - a most commonly used standard method of lossy compression for
4296 photographic images.</li>
4302 - line of personal computers is designed, developed, manufactured, and
4303 marketed by Apple Computer.</li>
4304 <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>
4305 - the operating system which is included with all currently shipping Apple
4306 Macintosh computers in the consumer and professional markets.</li>
4308 - a cryptographic library.</li>
4310 - the MCrypt PHP extension.</li>
4311 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4312 - an Internet Standard for the format of e-mail.</li>
4314 - some sort of extension for the Apache Webserver.</li>
4316 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4317 Management System (DBMS).</li>
4319 - the improved MySQL client PHP extension.</li>
4321 - the MySQL client PHP extension.</li>
4323 - open standard for office documents.</li>
4324 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4325 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4327 (Portable Document Format)</a>
4328 - a file format developed by Adobe Systems for representing two
4329 dimensional documents in a device independent and resolution independent
4330 format.</li>
4332 - the PHP Extension and Application Repository.</li>
4334 - the perl-compatible regular expression functions for PHP</li>
4336 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4337 programming language used mainly for developing server-side applications
4338 and dynamic web content, and more recently, a broader range of software
4339 applications.</li>
4341 - a connection through which data is sent and received.</li>
4343 - Request for Comments (RFC) documents are a series of memoranda
4344 encompassing new research, innovations, and methodologies applicable to
4345 Internet technologies.</li>
4349 - represents a single, implicitly structured data item in a table.</li>
4351 - a computer system that provides services to other computing
4352 systems over a network.</li>
4353 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4354 - handlers for different table types</li>
4356 - a form of inter-process communication.</li>
4358 Sockets Layer)</a>
4359 - a cryptographic protocol which provides secure communication on the Internet.</li>
4361 - Structured Query Language</li>
4363 - a set of data elements (cells) that is organized, defined and stored as
4364 horizontal rows and vertical columns where each item can be uniquely
4365 identified by a label or key or by it?s position in relation to other items.</li>
4368 - a type of archive file format: the Tape ARchive format.</li>
4370 - one of the core protocols of the Internet protocol suite.</li>
4374 - a sequence of characters, conforming to a standardized format, that is
4375 used for referring to resources, such as documents and images on the
4376 Internet, by their location.</li>
4378 - A computer (program) that is responsible for accepting HTTP requests
4379 from clients and serving them Web pages.</li>
4381 - a W3C-recommended general-purpose markup language for creating
4382 special-purpose markup languages, capable of describing many different
4383 kinds of data.</li>
4385 - a popular data compression and archival format.</li>
4387 - an open-source, cross-platform data compression library by Jean-loup
4388 Gailly and Mark Adler.</li>
4389 </ul>
4399 </body>
4400 </html>