| blob | 69b69e44130ec29b96e3379954c658254adc0808 |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 </li>
63 <li>You need GD2 support in PHP to display inline
65 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
198 provided for those who prefer a graphical installation. Creating a
200 still a quick way to get started and needed for some advanced features.
201 <ul><li>To manually create the file, simply use your text editor to
204 file) in the main (top-level) phpMyAdmin directory (the one
208 default value is okay for a particular setting, there is no
210 few directives to get going, a simple configuration may look
211 like this:
212 <pre>
213 <?php
214 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
216 $i=0;
217 $i++;
218 $cfg['Servers'][$i]['auth_type'] = 'cookie';
219 ?>
220 </pre>
221 Or, if you prefer to not be prompted every time you log in:
222 <pre>
223 <?php
225 $i=0;
226 $i++;
227 $cfg['Servers'][$i]['user'] = 'root';
228 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
229 ?>
230 </pre>
231 For a full explanation of possible configuration values, see the
237 directory. This is a security measure. On a Linux/Unix system you
238 can use the following commands:
239 <pre>
240 cd phpMyAdmin
241 mkdir config # create directory for saving
242 chmod o+rw config # give it world writable permissions
243 </pre>
244 And to edit an existing configuration, copy it over first:
245 <pre>
246 cp config.inc.php config/ # copy current configuration for editing
247 chmod o+w config/config.inc.php # give it world writable permissions
248 </pre>
249 On other platforms, simply create the folder and ensure that your
258 the webserver does not have the proper permissions you may see the
260 config/</tt> directory exists and has the proper permissions -
262 and upload (via FTP or some similar means) to the proper location.<br /><br />
264 Once the file has been saved, it must be moved out of the <tt>
265 config/</tt> directory and the permissions must be reset, again
266 as a security measure:
267 <pre>
268 mv config/config.inc.php . # move file to current directory
269 chmod o-rw config.inc.php # remove world read and write permissions
270 </pre>
271 Now the file is ready to be used. You can choose to review or edit
272 the file with your favorite editor, if you prefer to set some
273 advanced options which the setup script does not provide.</li></ul></li>
274 <li>If you are using the
276 protect the phpMyAdmin installation directory because using
277 config does not require a user to
278 enter a password to access the phpMyAdmin installation. Use of an alternate
279 authentication method is recommended, for example with
287 in your browser. phpMyAdmin should now display a welcome screen
288 and your databases, or a login dialog if using
290 authentication mode.</li>
292 webserver configuration. For Apache you can use supplied .htaccess file
293 in that folder, for other webservers, you should configure this yourself.
294 Such configuration prevents from possible path exposure and cross side
295 scripting vulnerabilities that might happen to be found in that code.</li>
296 </ol>
300 <p> For a whole set of new features (bookmarks, comments,
303 transformation, etc.) you need to create a set of special tables. Those
304 tables can be located in your own database, or in a central database for a
305 multi-user installation (this database would then be accessed by the
306 controluser, so no other user should have rights to it).</p>
315 installation.</p>
320 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
321 that you may need special (administrator) privileges to create the database
322 and tables, and that the script may need some tuning, depending on the
323 database name.</p>
328 section</a>. You will also need to have a controluser with the proper rights
335 unpacked one. Configuration files from very old versions (2.3.0 or before) may
336 require some tweaking as some options have been changed or removed.
338 statement that you might find near the end of your configuration file.</p>
342 is version-specific.</p>
345 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
346 you should run the SQL script found in
353 where you want to give users access to their own database and don't want
354 them to play around with others.<br />
355 Nevertheless be aware that MS Internet Explorer seems to be really buggy
357 in this area!<br />
360 that your user/password pair are not in clear in the configuration file.
361 </li>
364 authentication modes are more secure: the MySQL login information does
365 not need to be set in the phpMyAdmin configuration file (except possibly
367 However, keep in mind that the password travels in plain text, unless
368 you are using the HTTPS protocol.<br />
369 In cookie mode, the password is stored, encrypted with the blowfish
370 algorithm, in a temporary cookie.</li>
373 your MySQL server is previous to 4.1.2, or is running with
383 file under the
385 $cfg['Servers'][$i]['controluser']</a></tt> and
390 only an example: use something else in your file!</b> Input these
391 statements from the phpMyAdmin SQL Query window or mysql command–line
392 client.<br />
394 if it's not the same as the MySQL server's one.
396 <pre>
397 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
398 GRANT SELECT (
399 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
400 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
401 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
402 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
403 Execute_priv, Repl_slave_priv, Repl_client_priv
404 ) ON mysql.user TO 'pma'@'localhost';
405 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
406 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
407 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
408 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
410 If you are using an old MySQL version (below 4.0.2), please replace
411 the first GRANT SELECT query by this one:
413 <pre>
414 GRANT SELECT (
415 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
416 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
417 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
418 ) ON mysql.user TO 'pma'@'localhost';</pre>
420 ... and if you want to use the many new relation and bookmark features:
422 <pre>
424 </pre>
428 Of course, the above queries only work if your MySQL version supports
432 on a set of particular databases. Normally you shouldn't give global
433 privileges to an ordinary user, unless you understand the impact of those
434 privileges (for example, you are creating a superuser).<br />
438 <pre>
439 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
440 </pre>
442 What the user may now do is controlled entirely by the MySQL user
443 management system.<br />
445 authentication mode, you don't need to fill the user/password fields
447 array.</li>
448 </ul>
453 method and allows you to log in as any valid MySQL user.</li>
454 <li>Is supported with most PHP configurations. For
467 mode.</li>
468 </ul>
472 <ul><li>You can use this method as a replacement for the
474 (for example, if you're running
476 <li>Obviously, the user must enable cookies in the browser, but this is
477 now a requirement for all authentication modes.</li>
478 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
479 with the same username.</li>
480 <li>If you want to log in to arbitrary server see
485 not required.</li>
486 </ul>
490 <ul><li>This mode is a convenient way of using credentials from another
491 application to authenticate to phpMyAdmin.</li>
492 <li>The other application has to store login information into
493 session data.</li>
495 section.</li>
496 </ul>
499 <ul><li>This mode is the less secure one because it requires you to fill the
501 $cfg['Servers'][$i]['user']</a> and
503 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
504 can read your config.inc.php can discover your username and password).
505 <br />
512 is an entry explaining how to protect your configuration file.</li>
513 <li>For additional security in this mode, you may wish to consider the Host
514 authentication
516 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
518 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
519 directives.</li>
520 <li>Unlike cookie and http, does not require a user to log in when first
521 loading the phpMyAdmin site. This is by design but could allow any
522 user to access your installation. Use of some restriction method is
524 HTTP-AUTH directive or disallowing incoming HTTP requests at
525 one’s router or firewall will suffice (both of which
526 are beyond the scope of this manual but easily searchable with Google).</li>
527 </ul>
529 <!-- CONFIGURATION -->
533 users:</span> PHP does not seem to like
537 before saving a script you have modified.</p>
542 section to create one. This file only needs to contain the parameters you want to
543 change from their corresponding default value in
546 <p> The parameters which relate to design (like colors) are placed in
549 your site specific code to be included on start and end of each page.</p>
553 (with full path) to your phpMyAdmin installation's directory.
556 some web servers are case–sensitive.
559 Starting with version 2.3.0, it is advisable to try leaving this
560 blank. In most cases phpMyAdmin automatically detects the proper
561 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
562 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
563 A good test is to browse a table, edit a row and save it. There should
564 be an error message if phpMyAdmin is having trouble auto–detecting
565 the correct value. If you get an error that this must be set or if
566 the autodetect code fails to detect your path, please post a bug
567 report on our bug tracker so we can improve the code.</dd>
571 with master / foreign – tables (see
573 <br />
574 If you tried to set this up and it does not work for you, have a look on
576 use it. You will find a link that will analyze why those features have
577 been disabled.<br />
578 If you do not want to use those features set this variable to
582 <dd>A warning is displayed on the main page if Suhosin is detected.
584 from appearing.</dd>
588 algorithm to encrypt the password.<br />
590 passphrase of your choice. It will be used internally by the blowfish
591 algorithm: you won’t be prompted for this passphrase. The maximum
596 MySQL servers. Therefore, a
598 been added which contains the login information for the different servers.
599 The first
601 contains the hostname of the first server, the second
603 the hostname of the second server, etc. In
605 server definition, however you can put as many as you need in
607 have to define all settings, just those you need to change).</dd>
611 $i-th MySQL-server. E.g. localhost.</dd>
616 ignores this port number and connects with the socket, so if you want
617 to connect to a port different from the default port, use
620 </dd>
624 To determine the correct socket, check your MySQL configuration or, using the
626 Among the resulting information displayed will be the socket used.</dd>
629 <dd>Whether to enable SSL for connection to MySQL server.
630 </dd>
633 <dd>What type connection to use with the MySQL server. Your options are
635 is nearly guaranteed to be available on all MySQL servers, while
636 sockets are not supported on some platforms.<br /><br />
638 To use the socket mode, your MySQL server must be on the same machine
639 as the Web server.</dd>
642 <dd>What php MySQL extension to use for the connection. Valid options are:
643 <br /><br />
646 The classic MySQL extension. This is the recommended and default
647 method at this time.<br /><br />
650 The improved MySQL extension. This extension became available
651 with php 5.0.0 and is the recommended way to connect to a server
655 <dd>Whether to use a compressed protocol for the MySQL server connection
656 or not (experimental).<br />
662 </dt>
664 all relational features (see
666 and, for a MySQL server previous to 4.1.2 or running with
669 authentication mode).<br /><br />
672 cookie authentication modes (or 'config'
673 authentication mode since phpMyAdmin 2.2.1), you need to supply the
678 This account is used to check what databases the user will see at
679 login.<br />
683 In phpMyAdmin versions before 2.2.5, those were called
687 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
688 <dd>Whether config or cookie or
690 should be used for this server.
692 is the plain old way: username and password are stored in
694 <li>'cookie' authentication mode
696 2.2.3 allows you to log in as any valid MySQL user with the
697 help of cookies. Username and password are stored in
698 cookies during the session and password is deleted when it
699 ends. This can also allow you to log in in arbitrary server if
700 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
701 </li>
702 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
703 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
704 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
705 <li>'signon' authentication mode
707 as introduced in 2.10.0 allows you to log in from prepared PHP
708 session data. This is useful for implementing single signon
709 from another application. Sample way how to seed session is in
715 </ul>
718 for more information.
719 </dd>
723 </dt>
724 <dd>
725 When using auth_type = 'config', this is the user/password-pair
726 which phpMyAdmin will use to connect to the
727 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
728 cookie authentication is used and should be empty.</dd>
730 <span
732 </dt>
733 <dd>
734 Allow attempt to log in without password when a login with password
735 fails. This can be used together with http authentication, when
736 authentication is done some other way and phpMyAdmin gets user name
737 from auth and uses empty password for connecting to MySQL. Password
738 login is still tried first, but as fallback, no password method is
739 tried.</dd>
742 </dt>
743 <dd>
744 If set to a (an array of) database name(s), only this (these) database(s)
745 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
746 database(s) name(s) may contain MySQL wildcards characters
750 This setting is an efficient way to lower the server load since the
751 latter does not need to send MySQL requests to build the available
753 privileges rules of the MySQL database server</span>. If set, it just
754 means only these databases will be displayed but
756 <br /><br />
758 An example of using more that one database:
760 <br /><br />
762 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
763 databases in the left frame, so that you can individually arrange your databases.<br />
764 If you want to have certain databases at the top, but don't care about the others, you do not
765 need to specify all other databases. Use:
767 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
768 order.</dd>
771 </dt>
772 <dd>Regular expression for hiding some databases. This only hides them
773 from listing, but a user is still able to access them (using, for example,
774 the SQL query area). To limit access, use the MySQL privilege system.
775 <br /><br />
780 More information on regular expressions can be found in the
782 PCRE pattern syntax</a> portion of the PHP reference manual.
783 </dd>
786 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
787 this string will be displayed instead of the hostname in the pull-down
788 menu on the main page. This can be useful if you want to show only
789 certain databases on your system, for example. For HTTP auth, all
790 non-US-ASCII characters will be stripped.</dd>
794 </dt>
795 <dd>The name of the database containing the linked-tables infrastructure.
796 <br /><br />
799 section in this document to see the benefits of this infrastructure,
800 and for a quick way of creating this database and the needed tables.
801 <br /><br />
803 If you are the only user of this phpMyAdmin installation, you can
804 use your current database to store those special tables; in this
805 case, just put your current database name in
807 set this parameter to the name of your central database containing
808 the linked-tables infrastructure.</dd>
812 </dt>
814 useful for queries you often run.<br /><br />
816 To allow the usage of this functionality:
818 <li>enter the table name in
820 </ul>
821 </dd>
825 </dt>
827 which field is a key in another table (a foreign key). phpMyAdmin
828 currently uses this to
829 <ul><li>make clickable, when you browse the master table, the data values
830 that point to the foreign table;</li>
832 when browsing the master table, if you move the mouse to a column
833 containing a foreign key (use also the 'table_info' table);<br />
836 <li>in edit/insert mode, display a drop-down list of possible foreign
840 <li>display links on the table properties page, to check referential
841 integrity (display missing foreign keys) for each described key;
842 </li>
846 schema of your database (also uses the table_coords table).</li>
847 </ul>
849 The keys can be numeric or character.<br /><br />
851 To allow the usage of this functionality:
854 infrastructure</li>
855 <li>put the relation table name in
857 <li>now as normal user open phpMyAdmin and for each one of your
858 tables where you want to use this feature, click
860 </li>
861 </ul>
865 future development of the cross-db relations.
866 </dd>
870 </dt>
871 <dd>
872 Since release 2.3.0 you can describe, in a special 'table_info'
873 table, which field is to be displayed as a tool-tip when moving the
874 cursor over the corresponding key.<br />
875 This configuration variable will hold the name of this special
876 table. To allow the usage of this functionality:
878 <li>put the table name in
880 <li>then for each table where you want to use this feature,
882 to choose the field.</li>
883 </ul>
885 </dd>
889 </dt>
892 the relations between your tables. To do this it needs two tables
897 schema output).<br /><br />
901 To allow the usage of this functionality:
904 infrastructure</li>
905 <li>put the correct table names in
908 </ul>
911 </dd>
915 </dt>
917 Since release 2.3.0 you can store comments to describe each column for
919 <br /><br />
921 Starting with release 2.5.0, comments are consequently used on the table
922 property pages and table browse view, showing up as tool-tips above the
923 column name (properties page) or embedded within the header of table in
924 browse view. They can also be shown in a table dump. Please see the
925 relevant configuration directives later on.<br /><br />
927 Also new in release 2.5.0 is a MIME-transformation system which is also
929 Transformations</a> for further information. To use the
930 MIME-transformation system, your column_info table has to have the three
931 new fields 'mimetype', 'transformation', 'transformation_options'.
932 <br /><br />
934 To allow the usage of this functionality:
936 infrastructure</li>
937 <li>put the table name in
941 <pre>
942 ALTER TABLE `pma_column_comments`
943 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
944 ADD `transformation` VARCHAR( 255 ) NOT NULL,
945 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
946 </pre>
949 renamed from<br />
952 </ul>
953 </dd>
957 </dt>
960 all queries you entered manually into the phpMyAdmin interface. If you
961 don't want to use a table-based history, you can use the JavaScript-based
962 history. Using that, all your history items are deleted when closing the
963 window.<br /><br />
965 Using
967 you can specify an amount of history items you want to have on hold. On
968 every login, this list gets cut to the maximum amount.<br /><br />
970 The query history is only available if JavaScript is enabled in your
971 browser.<br /><br />
973 To allow the usage of this functionality:
976 infrastructure</li>
978 </li>
979 </ul>
980 </dd>
984 </dt>
986 to visually manage the relations.
987 <br /><br />
989 To allow the usage of this functionality:
992 infrastructure</li>
994 </li>
995 </ul>
996 </dd>
999 </dt>
1001 column_info table got enhanced with three new fields. If the above variable
1003 latest table structure available. If not, it will emit a warning to the
1004 superuser.<br /><br />
1006 You can disable this checking behavior by setting the variable to false,
1007 which should offer a performance increase.<br /><br />
1009 Recommended to set to FALSE, when you are sure, your table structure is
1010 up to date.</dd>
1012 boolean</dt>
1013 <dd>Whether to allow root access. This is just simplification of rules below.
1014 </dd>
1017 </dt>
1019 authentication is disabled.<br /><br />
1022 all deny rules followed by allow rules. Access is allowed by default. Any
1023 client which does not match a Deny command or does match an Allow command
1024 will be allowed access to the server. <br /><br />
1027 applies all allow rules followed by deny rules. Access is denied by
1028 default. Any client which does not match an Allow directive or does
1029 match a Deny directive will be denied access to the server.<br /><br />
1031 If your rule order is set to 'explicit', the authentication is
1032 performed in a similar fashion to rule order 'deny,allow', with the
1036 and was available in Apache by specifying allow and deny rules without
1037 setting any order.<br /><br />
1039 Please also see <a
1041 address behind proxies.
1042 </dd>
1044 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1045 </dt>
1046 <dd>The general format for the rules is as such:
1048 <pre>
1050 </pre>
1055 well (please note that those containing SERVER_ADDRESS might not be
1056 available on all webservers):
1057 <pre>
1063 </pre>
1065 Having an empty rule list is equivalent to either using
1071 following work:<br />
1073 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1074 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1075 But the following does not work:<br />
1078 </dd>
1079 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1080 <dd>Name of session which will be used for signon authentication method.
1081 </dd>
1083 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1084 </dd>
1086 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1087 </dd>
1090 <dd>If you have more than one server configured, you can set
1092 that server when phpMyAdmin is started, or set it to 0 to be given a
1093 list of servers without logging in.<br />
1095 MUST be set to that server.</dd>
1098 <dd>The maximum number of database names to be displayed in the
1099 navigation frame and the database list.</dd>
1102 <dd>The maximum number of table names to be displayed in the
1103 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1104 when in Light mode.</dd>
1107 <dd>The maximum number of characters when a SQL query is displayed. The
1108 default limit of 1000 should be correct to avoid the display of tons
1109 of hexadecimal codes that represent BLOBs, but some users have real
1113 <dd>Defines whether to use GZip output buffering for increased
1115 Set to true/false for enabling/disabling. When set to 'auto' (string),
1116 phpMyAdmin tries to enable output buffering and will automatically disable
1117 it if your browser has some problems with buffering. IE6 with a certain patch
1118 is known to cause data corruption when having enabled buffering.</dd>
1121 <dd>Whether persistent connections should be used or not (mysql_connect or
1122 mysql_pconnect).</dd>
1128 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1129 to zero, no time 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.</dd>
1134 <dd>Set the number of bytes a script is allowed to allocate. If number set
1135 to zero, no limit is imposed.<br />
1136 This setting is used while importing/exporting dump files but has no
1137 effect when PHP is running in safe mode.<br />
1141 <dd>Mark used tables and make it possible to show databases with locked
1146 generated by phpMyAdmin should be displayed or not.</dd>
1149 <dd>Defines whether normal users (non-administrator) are allowed to
1150 delete their own database or not. If set as FALSE, the link "Drop
1152 mydatabase" will be rejected. Quite practical for
1154 customers.<br />
1155 Please note that this limitation of SQL queries is not as strict as
1156 when using MySQL privileges. This is due to nature of SQL queries
1157 which might be quite complicated. So this choice should be viewed as
1158 help to avoid accidental dropping rather than strict privilege
1159 limitation.</dd>
1163 displayed when you're about to lose data.</dd>
1166 <dd>Define whether the previous login should be recalled or not in cookie
1167 authentication mode.</dd>
1174 means that it will be kept for existing session. This is recommended
1175 for not trusted environments.</dd>
1178 <dd>If enabled (default), logout deletes cookies for all servers,
1179 otherwise only for current one. Setting this to false makes it easy to
1180 forget to log out from other server, when you are using more of
1181 them.</dd>
1187 <dd>Define whether phpMyAdmin will continue executing a multi-query
1188 statement if one of the queries fails. Default is to abort execution.</dd>
1191 <dd>Define whether phpMyAdmin will output the results of each query of a
1192 multi-query statement embedded into the
1197 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1198 <br /><br />
1201 MySQL servers behind the firewall where your
1203 </dd>
1206 <dd>Defines whether to use a select-based menu and display only the current
1207 tables in the left frame (smaller page). Only in Non-Lightmode you can
1208 use the feature to display nested folders using
1210 </dd>
1213 <dd>In light mode, defines whether to display the names of databases (in the
1214 selector) using a tree, see also
1216 </dd>
1219 <dd>The string used to separate the parts of the database name when showing
1220 them in a tree.</dd>
1223 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1224 This means if you have tables like 'first__second__third' this will be
1226 If set to FALSE or empty, the feature is disabled. NOTE: You should
1227 not use this separator at the beginning or end of a
1228 table name or multiple times after another without any other
1229 characters in between.</dd>
1232 <dd>Defines how many sublevels should be displayed when splitting
1233 up tables by the above separator.</dd>
1236 <dd>Defines whether to display table comment as tool-tip in left frame or
1237 not.</dd>
1240 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1241 comment and the real name. That means that if you have a table called
1242 'user0001' and add the comment 'MyName' on it, you will see the name
1243 'MyName' used consequently in the left frame and the tool-tip shows
1244 the real name of the DB.</dd>
1247 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1249 When setting this to 'nested', the Alias of the Tablename is only used
1250 to split/nest the tables according to the
1252 directive. So only the folder is called like the Alias, the tablename itself
1253 stays the real tablename.</dd>
1256 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1259 <dd>Enter URL where logo in the navigation frame will point to.
1260 For use especially with self made theme which changes this.
1269 <dd>Defines whether or not to display a server choice at the top of the left frame.
1270 Defaults to FALSE.</dd>
1272 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1273 Defaults to FALSE (drop-down).</dd>
1275 <dd>Defines whether to display database choice in light navigation frame as links
1276 instead of in a drop-down. Defaults to 'auto' - on main page list is
1277 shown, when database is selected, only drop down is displayed.</dd>
1279 <dd>Defines whether or not to display space usage and statistics about databases
1280 and tables.<br />
1281 Note that statistics requires at least MySQL 3.23.3 and that, at this
1282 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1285 <dd>Defines whether to display detailed server information on main page.
1286 You can additionally hide more information by using
1288 </dd>
1293 </dt>
1296 not at the starting main (right) frame. This setting
1297 does not check MySQL commands entered directly.<br /><br />
1299 Please note that to block the usage of phpinfo() in scripts, you
1306 hard coded password value in the configuration file, end users can't
1307 be allowed to change their passwords.</dd>
1310 <dd>Defines whether to suggest a database name on the
1315 content.</dd>
1318 <dd>Defines whether navigation bar buttons and the right panel top menu
1319 contain text or symbols only. A value of TRUE displays icons, FALSE
1320 displays text and 'both' displays both icons and text.</dd>
1323 <dd>Defines whether a user should be displayed a
1327 <dd>Number of rows displayed when browsing a result set. If the result set
1334 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1338 from editing when browsing a table's content. Valid values are:
1343 </ul>
1344 </dd>
1347 <dd>Defines whether or not MySQL functions fields should be initially
1348 displayed in edit/insert mode. Since version 2.10, the user can
1349 toggle this setting from the interface.
1350 </dd>
1353 <dd>Defines which type of editing controls should be used for CHAR and
1354 VARCHAR fields. Possible values are:
1355 <ul><li>input - this allows to limit size of text to size of field in
1356 MySQL, but has problems with newlines in fields</li>
1357 <li>textarea - no problems with newlines in fields, but also no
1358 length limitations</li>
1359 </ul>
1360 Default is old behavior so input.</dd>
1366 <dd>If there are fewer items than this in the set of foreign keys, then a
1367 drop-down box of foreign keys is presented, in the style described by the
1369 setting.</dd>
1372 <dd>For the foreign key drop-down fields, there are several methods of
1373 display, offering both the key and value data. The contents of the
1374 array should be one or both of the following strings:
1380 </dt>
1381 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1382 creating a dump file</dd>
1385 </dt>
1386 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1387 compressed exports. This doesn't affect smaller dumps and allows users to
1388 create larger dumps that won't otherwise fit in memory due to php
1389 memory limit. Produced files contain more GZip/BZip2 headers, but all
1390 normal programs handle this correctly.</dd>
1394 mainframe.</dd>
1398 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1403 <dd>How many columns will be utilized to display the tables on the
1404 database property view? Default is 1 column. When setting this to a
1405 value larger than 1, the type of the database will be omitted for more
1406 display space.</dd>
1410 <dd>Defines the tab displayed by default on server view. Possible
1417 <dd>Defines the tab displayed by default on database view. Possible
1422 <dd>Defines the tab displayed by default on table view. Possible
1429 points to the MySQL documentation (type depends
1430 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1431 generated.<br />
1433 for more information about MySQL manuals and their types.</dd>
1436 <dd>Type of MySQL documentation:
1442 </ul>
1443 </dd>
1446 <dd>Defines the default language to use, if not browser-defined or
1447 user-defined.<br />
1449 this setting.</dd>
1452 <dd>Defines the default connection collation to use, if not
1453 user-defined.<br />
1458 <dd>Force: always use this language (must be defined in the
1462 <dd>Limit list of available languages to those matching the given regular
1463 expression. For example if you want only Czech and English, you should
1467 <dd>Default character set to use for recoding of MySQL queries. This must be
1468 enabled and it's described by
1470 option.<br />
1471 You can give here any character set which is in
1473 array and this is just default choice, user can select any of them.</dd>
1476 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1477 support (compiled in or module) in PHP to allow MySQL queries recoding
1478 and used language file must have it enabled (by default only these
1479 which are in Unicode, just to avoid losing some characters).<br /><br />
1482 in the Export page, to choose the character set when exporting a file.
1483 </dd>
1486 <dd>You can select here which functions will be used for character set
1487 conversion. Possible values are:
1488 <ul><li>auto - automatically use available one (first is tested
1489 iconv, then recode)</li>
1492 </ul>
1493 Default is auto.</dd>
1496 <dd>Specify some parameters for iconv used in charset conversion. See
1499 used, so that invalid characters will be transliterated.</dd>
1502 <dd>Available character sets for MySQL conversion. You can add your own (any of
1503 supported by recode/iconv) or remove these which you don't use.
1504 Character sets will be shown in same order as here listed, so if you
1505 frequently use some of these move them to the top.</dd>
1510 default empty, you need to fill in some trusted proxy servers if you
1511 want to use rules for IP addresses behind proxy.<br /><br />
1513 The following example specifies that phpMyAdmin should trust a
1515 <pre>
1516 $cfg['TrustedProxies'] =
1518 </pre>
1519 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1520 client's IP address as usual.
1521 </dd>
1525 MIME transformations.<br />
1526 Possible values are:
1527 <ul><li>auto - automatically detect, this is a bit expensive
1529 according to your server real possibilities</li>
1532 </ul>
1533 Default is auto.
1534 </dd>
1538 </dd>
1540 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1541 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1542 </dt>
1543 <dd>The background styles used for both the frames.
1546 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1548 <dd>The style used for the pointer in the navi frame.
1552 <dd>The color used for the database name in the navi frame.
1561 </dd>
1565 <dd>The style used for table headers. See
1570 </dd>
1574 </dd>
1576 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1578 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1580 </dt>
1582 The former feature highlights the row over which your mouse is passing
1583 and the latter lets you visually mark/unmark rows by clicking on
1584 them.<br />
1589 <dd>You put here a valid CSS font family value, for example
1594 <dd>You put here a valid CSS font family value, for example
1608 </dt>
1610 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1612 The Char* values are used for CHAR and VARCHAR editing (if configured
1616 </dt>
1620 </dt>
1621 <dd>Defines if the whole textarea of the query box will be selected on
1622 click.</dd>
1625 </dt>
1626 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1627 editing.</dd>
1630 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1631 Can be turned off by a toggle button on the browse page.</dd>
1635 </dt>
1636 <dd>Defines the place where modify and delete links would be put when
1637 tables contents are displayed (you may have them displayed both at the
1638 left and at the right).
1644 </dt>
1646 Define which one is displayed by default. The first mode displays each
1647 row on a horizontal line, the second rotates the headers by 90
1648 degrees, so you can use descriptive headers even though fields only
1649 contain small values and still print them out. The vertical mode sorts
1650 each row on a vertical lineup.<br /><br />
1652 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1653 the rotation of the header for horizontalflipped is done via CSS. If
1654 set to 'fake' PHP does the transformation for you, but of course this
1655 does not look as good as CSS.</dd>
1659 string or integer</dt>
1660 <dd>When editing/creating new columns in a table all fields normally get
1661 lined up one field a line. (default: 'horizontal'). If you set this to
1662 'vertical' you can have each field lined up vertically beneath each
1663 other. You can save up a lot of place on the horizontal direction and
1664 no longer have to scroll. If you set this to integer, editing of fewer
1665 columns will appear in 'vertical' mode, while editing of more fields
1666 still in 'horizontal' mode. This way you can still effectively edit
1667 large number of fields, while having full view on few of them.</dd>
1671 </dt>
1673 display of column comments in Browse or Property display. In browse
1674 mode, the comments are shown inside the header. In property mode,
1675 comments are displayed using a CSS-formatted dashed-line below the
1676 name of the field. The comment is shown as a tool-tip for that field.
1677 </dd>
1689 <dd>Whether to display a link to validate a query in any SQL Query box.
1696 <dd>
1697 The name of the directory where
1699 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1700 are available under a drop-down box when you click the database or
1701 table name, then the Import tab.
1702 <br /><br />
1704 If you want different directory for each user, %u will be replaced
1705 with username.<br /><br />
1709 compressed formats is enabled).<br /><br />
1711 This feature is useful when your file is too big to be uploaded via
1713 uploads are disabled in PHP.<br /><br />
1715 Please note that if PHP is running in safe mode, this directory must
1716 be owned by the same user as the owner of the phpMyAdmin scripts.
1717 <br /><br />
1721 alternatives.
1722 </dd>
1725 <dd>
1726 The name of the directory where dumps can be saved.<br /><br />
1728 If you want different directory for each user, %u will be replaced
1729 with username.<br /><br />
1731 Please note that the directory must exist and has to be writable
1732 for the user running the webserver.<br /><br />
1734 Please note that if PHP is running in safe mode, this directory must
1735 be owned by the same user as the owner of the phpMyAdmin scripts.
1736 </dd>
1739 <dd>
1740 The name of the directory where temporary files can be stored.
1741 <br /><br />
1742 This is needed for native MS Excel export, see
1745 </dd>
1748 <dd>
1749 In this array are defined default parameters for export, names of
1750 items are similar to texts seen on export page, so you can easily
1751 identify what they mean.
1752 </dd>
1755 <dd>
1756 In this array are defined default parameters for import, names of
1757 items are similar to texts seen on import page, so you can easily
1758 identify what they mean.
1759 </dd>
1762 <dd>
1763 Repeat the headers every X cells, or 0 to deactivate.
1764 </dd>
1772 </dt>
1773 <dd>
1774 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1775 or icon is always displayed on the left panel. If JavaScript is enabled in
1776 your browser, a click on this opens a distinct query window, which is
1777 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1778 changes to display a query box.<br /><br />
1780 The size of this query window can be customized with
1782 - both integers for the size in pixels. Note that normally, those
1784 theme you are using.<br /><br />
1788 opens the query window and puts the current query
1789 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1790 query in the right panel's query box.
1791 <br /><br />
1792 The usage of the JavaScript query window is recommended if you have a
1793 JavaScript enabled browser. Basic functions are used to exchange quite
1794 a few variables, so most 4th generation browsers should be capable to
1795 use that feature. It currently is only tested with Internet Explorer 6
1796 and Mozilla 1.x.
1797 <br /><br />
1799 to a table, which has to be created by you (see <a
1801 all your queries will be appended to the form, but only as long as
1802 your window is opened they remain saved.
1803 <br /><br />
1804 When using the JavaScript based query window, it will always get
1805 updated when you click on a new table/db to browse and will focus if
1806 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1807 the query window by checking the box "Do not overwrite this query from
1808 outside the window" below the query textarea. Then you can browse
1809 tables/databases in the background without losing the contents of the
1810 textarea, so this is especially useful when composing a query with
1811 tables you first have to look in. The checkbox will get automatically
1812 checked whenever you change the contents of the textarea. Please
1813 uncheck the button whenever you definitely want the query window to
1814 get updated even though you have made alterations.
1815 <br /><br />
1818 <br /><br />
1819 The query window also has a custom tabbed look to group the features.
1821 default tab to be used when opening the query window. It can be set to
1822 either 'sql', 'files', 'history' or 'full'.</dd>
1828 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1830 If the approximate row count as returned by
1833 count will be used.
1834 </dd>
1836 <dd>For VIEWs, since obtaining the exact count could have an
1837 impact on performance, this value is the maximum to be displayed, using
1839 any row counting.
1840 </dd>
1844 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1846 page. By clicking on the button 'toggle scratchboard' on the page
1847 where you edit x/y coordinates of those elements you can activate a
1848 scratchboard where all your elements are placed. By clicking on an
1849 element, you can move them around in the pre-defined area and the x/y
1850 coordinates will get updated dynamically. Likewise, when entering a
1851 new position directly into the input field, the new position in the
1852 scratchboard changes after your cursor leaves the input field.<br />
1853 You have to click on the 'OK'-button below the tables to save the new
1854 positions. If you want to place a new element, first add it to the
1855 table of elements and then you can drag the new element around.<br />
1856 By changing the paper size and the orientation you can change the size
1857 of the scratchboard as well. You can do so by just changing the
1858 dropdown field below, and the scratchboard will resize automatically,
1859 without interfering with the current placement of the elements.<br />
1860 If ever an element gets out of range you can either enlarge the paper
1861 size or click on the 'reset' button to place all elements below each
1862 other.<br />
1864 get this control to work. The basic Drag&Drop script functionality
1865 was kindly borrowed from www.youngpup.net and is underlying so
1866 specific license.</dd>
1869 <dd>Sorts database and table names according to natural order (for example,
1870 t1, t2, t10). Currently implemented in the left panel (Light mode)
1871 and in Database view, for the table list.</dd>
1877 <dd>Allows you to specify window's title bar. Following magic string can
1878 be used to get special values:
1879 <dl>
1885 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1894 </dl>
1895 </dd>
1905 </dd>
1908 <dd>If theme manager is active, use this as the path of the subdirectory
1909 containing all the themes.</dd>
1923 </dt>
1924 <dd>Default queries that will be displayed in query boxes when user didn't
1925 specify any. Use %d for database name, %t for table name and %f for a
1926 comma separated list of field names. Note that %t and %f are only
1930 <dd>
1931 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
1932 default we use HTML to format the query, but you can disable this by
1934 </dd>
1937 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1938 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1939 query inside a bracket is indented. By changing
1942 specifies the units of the indent amount that you specified. This is
1943 used via stylesheets.</dd>
1946 <dd>This array is used to define the colours for each type of element of
1947 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1949 If you specify an empty string for the color of a class, it is ignored
1950 in creating the stylesheet.
1951 You should not alter the class names, only the colour strings.<br />
1972 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1976 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1977 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1978 </ul>
1979 </dd>
1983 <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,
1984 as originally published on
1986 <br />
1987 For help in setting up your system to use the service, see the
1989 </dd>
1993 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1994 and any password, so we use those by default. Instead, if
1995 you have an account with them, you can put your login details
1996 here, and it will be used in place of the anonymous login.</dd>
1997 </dl>
1998 </dd>
2001 <dd><b>DEVELOPERS ONLY!</b></dd>
2004 <dd><b>DEVELOPERS ONLY!</b><br />
2005 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2006 the code.<br />
2007 For help in setting up your system to this, see the
2011 <dd><b>DEVELOPERS ONLY!</b><br />
2012 Enable profiling support for phpMyAdmin. This will append a chunk of data
2013 to the end of every page displayed in the main window with profiling
2014 statistics for that page.<br />
2015 You may need to increase the maximum execution time for this to
2016 complete successfully.<i>Profiling was removed from the code for
2017 version 2.9.0 due to licensing issues.</i></dd>
2019 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2020 <dd><b>DEVELOPERS ONLY!</b><br />
2021 When profiling data is displayed, this variable controls the threshold of
2022 display for any profiling data, based on the average time each time has
2023 taken. If it is over the threshold it is displayed, otherwise it is not
2024 displayed. This takes a value in milliseconds. In most cases you don't need
2025 to edit this.</dd>
2028 <dd>All possible types of a MySQL column. In most cases you don't need to
2029 edit this.</dd>
2032 <dd>Possible attributes for fields. In most cases you don't need to edit
2033 this.</dd>
2036 <dd>A list of functions MySQL supports. In most cases you don't need to
2037 edit this.</dd>
2040 <dd>Mapping of column types to meta types used for preferring displayed
2041 functions. In most cases you don't need to edit this.</dd>
2044 <dd>Functions preferred for column meta types as defined in
2045 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2046 to edit this.</dd>
2049 <dd>Functions selected by default when inserting/changing row, Functions
2050 are defined for meta types from
2052 <code>first_timestamp</code>, which is used for first timestamp column
2053 in table.</dd>
2056 <dd>Operators available for search operations on numeric and date fields.
2057 </dd>
2060 <dd>Operators available for search operations on character fields.
2061 Note that we put <code>LIKE</code> by default instead of
2062 <code>LIKE %...%</code>, to avoid unintended performance problems
2063 in case of huge tables.</dd>
2066 <dd>Operators available for search operations on enum fields.</dd>
2069 <dd>Additional operators available for search operations when the
2070 field can be null.</dd>
2072 </dl>
2074 <!-- TRANSFORMATIONS -->
2080 </ol>
2084 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2086 section</a> on how to do so.</p>
2088 <p> You can apply different transformations to the contents of each field. The
2089 transformation will take the content of each field and transform it with
2090 certain rules defined in the selected transformation.</p>
2092 <p> Say you have a field 'filename' which contains a filename. Normally you would
2093 see in phpMyAdmin only this filename. Using transformations you can transform
2094 that filename into a HTML link, so you can click inside of the phpMyAdmin
2095 structure on the field's link and will see the file displayed in a new browser
2096 window. Using transformation options you can also specify strings to
2097 append/prepend to a string or the format you want the output stored in.</p>
2099 <p> For a general overview of all available transformations and their options,
2100 you can consult your
2101 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2102 installation.</p>
2104 <p> For a tutorial on how to effectively use transformations, see our
2106 the official phpMyAdmin homepage.</p>
2110 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2111 clicking on the 'Structure' link for a table). There click on
2112 "Change" (or change icon) and there you will see three new fields at
2113 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2114 'Transformation options'.</p>
2116 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2117 that corresponds to the column's contents. Please note that
2118 transformations are inactive as long as no MIME-type is selected.</li>
2120 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2121 hopefully growing amount of pre-defined transformations. See below for information on
2122 how to build your own transformation.<br />
2124 There are global transformations and mimetype-bound transformations. Global transformations
2125 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2126 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2127 transformations which operate on the main mimetype (like 'image'), which will most likely
2128 take the subtype into regard, and those who only operate on a
2129 specific subtype (like 'image/jpeg').<br />
2131 You can use transformations on mimetypes for which the function was not defined for. There
2132 is no security check for you selected the right transformation, so take care of what the
2133 output will be like.</li>
2135 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2136 transform-function specific options here. Usually the transforms can operate with default
2137 options, but it is generally a good idea to look up the overview to see which options are
2138 necessary.<br />
2140 Much like the ENUM/SET-Fields, you have to split up several options using the format
2141 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2142 parsed as an array, leaving the first value the first element in the array, and so
2143 forth.<br />
2145 If you want to specify a MIME character set you can define it in the transformation_options.
2146 You have to put that outside of the pre-defined options of the specific mime-transform,
2148 for which you can specify 2 options and you want to append a character set, enter "'first
2149 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2151 </ul>
2155 <p> All mimetypes and their transformations are defined through single files in
2156 the directory 'libraries/transformations/'.</p>
2158 <p> They are stored in files to ease up customization and easy adding of new
2159 transformations.</p>
2161 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2162 always work. It makes no sense to apply a transformation to a mimetype, the
2163 transform-function doesn't know to handle.</p>
2165 <p> One can, however, use empty mime-types and global transformations which should work
2166 for many mimetypes. You can also use transforms on a different mimetype they where built
2167 for, but pay attention to option usage as well as what the transformation does to your
2168 field.</p>
2170 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2171 any other transform function and provides some basic functions.</p>
2173 <p> There are 5 possible file names:</p>
2175 <ol><li>A mimetype+subtype transform:<br /><br />
2177 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2179 Please not that mimetype and subtype are separated via '_', which shall
2180 not be contained in their names. The transform function/filename may
2181 contain only characters which cause no problems in the file system as
2182 well as the PHP function naming convention.<br /><br />
2184 The transform function will the be called
2185 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2187 <b>Example:</b><br /><br />
2189 <tt>text_html__formatted.inc.php</tt><br />
2190 <tt>PMA_transform_text_html__formatted()</tt></li>
2192 <li>A mimetype (w/o subtype) transform:<br /><br />
2194 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2196 Please note that there are no single '_' characters.
2197 The transform function/filename may contain only characters which cause
2198 no problems in the file system as well as the PHP function naming
2199 convention.<br /><br />
2201 The transform function will the be called
2202 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2204 <b>Example:</b><br /><br />
2206 <tt>text__formatted.inc.php</tt><br />
2207 <tt>PMA_transform_text__formatted()</tt></li>
2209 <li>A mimetype+subtype without specific transform function<br /><br />
2211 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2213 Please note that there are no '__' characters in the filename. Do not
2214 use special characters in the filename causing problems with the file
2215 system.<br /><br />
2217 No transformation function is defined in the file itself.<br /><br />
2219 <b>Example:</b><br /><br />
2221 <tt>text_plain.inc.php</tt><br />
2222 (No function)</li>
2224 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2226 <tt>[mimetype].inc.php</tt><br /><br />
2228 Please note that there are no '_' characters in the filename. Do not use
2229 special characters in the filename causing problems with the file system.
2230 <br /><br />
2232 No transformation function is defined in the file itself.<br /><br />
2234 <b>Example:</b><br /><br />
2236 <tt>text.inc.php</tt><br />
2237 (No function)</li>
2239 <li>A global transform function with no specific mimetype<br /><br />
2241 <tt>global__[transform].inc.php</tt><br /><br />
2243 The transform function will the be called
2244 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2246 <b>Example:</b><br /><br />
2248 <tt>global__formatted</tt><br />
2249 <tt>PMA_transform_global__formatted()</tt></li>
2250 </ol>
2252 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2253 transform function.</p>
2255 <p> All filenames containing no '__' in themselves are not shown as valid transform
2256 functions in the dropdown.</p>
2258 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2259 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2260 without a transform function. Also note the introduction of a function description in
2261 the language files. For each function a $strTransformation_[filename without .inc.php]
2262 has to exist.</p>
2264 <p> You can use the template generator to generate new functions and entries in the
2265 language file.</p>
2267 <p> To create a new transform function please see
2268 <tt>libraries/transformations/template_generator.sh</tt>.
2269 To create a new, empty mimetype please see
2270 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2272 <p> A transform function always gets passed three variables:</p>
2274 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2275 you want to transform.</li>
2276 <li><b>$options</b> - Contains any user-passed options to a transform function
2277 as an array.</li>
2278 <li><b>$meta</b> - Contains an object with field information to your column.
2279 The data is drawn from the output of the
2281 function. This means, all object properties described on the
2283 available in this variable and can be used to transform a field accordingly
2284 to unsigned/zerofill/not_null/... properties.<br />
2285 The $meta->mimetype variable contains the original MIME-type of the
2286 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2287 </ol>
2289 <!-- FAQ -->
2296 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2300 </ol>
2302 <p> Please have a look at our
2304 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2305 features and or interface.</p>
2311 action is required or phpMyAdmin sends a blank page or a page full of
2312 cryptic characters to my browser, what can I do?</a></h4>
2314 <p> There are some known PHP bugs with output buffering and compression.<br />
2316 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2317 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2318 configuration file.<br />
2319 Furthermore, we know about such problems connected to the release
2320 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2321 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2326 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2327 See also the
2329 entry about PHP bugs with output buffering.<br />
2330 If your server keeps crashing, please ask for help in the various Apache
2331 support groups.</p>
2335 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2336 script: I'm always displayed the login screen.</a></h4>
2338 <p> This is a known PHP bug (see this
2340 official PHP bug database. It means there is and won't be any phpMyAdmin
2341 fix against it because there is no way to code a fix.</p>
2347 application misbehaved by not returning a complete set of
2349 </h4>
2351 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2352 Have a look at the last message in this
2354 official PHP bug database.</p>
2359 and/or many error messages with the
2361 mode.</a></h4>
2363 <p> This is a known problem with the PHP
2365 filter: it's not so stable. Please use instead the cookie authentication mode.
2366 </p>
2371 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2372 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2373 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2374 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2375 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2380 work.</a></h4>
2382 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2383 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2384 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2385 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2386 We faced PHP crashes when trying to download a dump with MS Internet
2387 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2388 this case you should switch to the release version of PHP 4.2.0.</p>
2392 an error about safe mode being in effect.</a></h4>
2394 <p> Your uploaded file is saved by PHP in the "upload dir", as
2395 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2396 the system default is <i>/tmp</i>).<br />
2397 We recommend the following setup for Apache servers running in safe mode,
2398 to enable uploads of files while being reasonably secure:</p>
2400 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2401 <li>give ownership to the Apache server's user.group:
2402 <tt>chown apache.apache /tmp/php</tt></li>
2403 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2404 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2405 <li>restart Apache</li>
2406 </ul>
2410 general file uploads don't work on my system and uploaded files have a
2411 <tt>Content-Type:</tt> header in the first line.</a></h4>
2413 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2414 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2415 So the problem is that this package has a serious bug that was corrected
2416 ages ago in PHP (2001-01-28: see
2418 for more details). The problem is that the bugged package is still
2419 available though it was corrected (see
2421 for more details).<br />
2422 So please download
2423 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2424 and the problem should go away.<br />
2425 And that fixes the \r\n problem with file uploads!</p>
2429 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2430 I'm using the Apache server.</a></h4>
2432 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2433 your <i>httpd.conf</i>:</p>
2437 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2441 uploading a file from the query box.</a></h4>
2443 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2444 restrictions. Assuming that the restriction allows you to open files in the
2445 current directory ('.'), all you have to do is create a 'tmp' directory
2446 under the phpMyAdmin install directory, with permissions 777 and the same
2447 owner as the owner of your phpMyAdmin directory. The uploaded files will
2448 be moved there, and after execution of your
2454 <p> The MySQL manual explains how to
2456 reset the permissions</a>.</p>
2461 execute a bookmark.</a></h4>
2463 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2464 cannot access the uploaded query.</p>
2469 submit a query from the convenient text area.</a></h4>
2471 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2472 and try to increase it.</p>
2476 </h4>
2478 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2479 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2480 names to align with current standards.</p>
2485 </h4>
2487 <p> Starting with version 2.7.0, the import engine has been re–written and these
2488 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2489 to take advantage of the new import features.</p>
2491 <p> The first things to check (or ask your host provider to check) are the
2492 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2493 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2494 All of these three settings limit the maximum size of data that can be
2495 submitted and handled by PHP. One user also said that post_max_size
2496 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2498 There exist several workarounds if your upload is too big or your
2499 hosting provider is unwilling to change the settings:</p>
2502 feature. This allows one to
2503 upload a file to the server via scp, ftp, or your favorite file transfer
2504 method. PhpMyAdmin is then able to import the files from the temporary
2506 section</a> of this document.</li>
2508 BigDump</a>) to split the files before uploading. We cannot support this
2509 or any third party applications, but are aware of users having success
2510 with it.</li>
2511 <li>If you have shell (command line) access, use MySQL to import the files
2512 directly. You can do this by issuing the "source" command from
2513 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2514 </ul>
2518 support?</a></h4>
2520 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2521 fully supported. Please note that the older your MySQL version is, the more
2522 limitations you will have to face.<br />
2523 phpMyAdmin may connect to your MySQL server using php's classic
2526 is available in php 5.0.<br />
2527 Either way, the developers of both extensions recommend to use the classic
2528 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2529 When compiling php, we strongly recommend that you manually link the MySQL
2530 extension of your choice to a MySQL client library of at least the same
2531 minor version since the one that is bundled with some php distributions is
2534 If your webserver is running on a windows system, you might want to try
2535 MySQL's
2537 instead of the MySQL / MySQLi extensions that are bundled with the official
2538 php Win32 builds.
2539 <br />
2540 MySQL 5.1 is not yet supported.</p>
2544 message, "Client does not support authentication protocol requested
2545 by server; consider upgrading MySQL client"</a></h5>
2547 <p> You tried to access MySQL with an old MySQL client library. The version of
2548 your MySQL client library can be checked in your phpinfo() output.
2549 In general, it should have at least the same minor version as your server
2553 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2554 changed the authentication hash and your PHP is trying to use the old method.
2556 with the proper client library to match your MySQL installation. Your
2557 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2558 More information (and several workarounds) are located in the
2560 </p>
2564 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2565 capital letter in its name it is changed to lowercase as it should. But
2566 if I try to DROP this table MySQL is unable to find the corresponding
2567 file.</a></h4>
2569 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2570 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2571 directive.</p>
2575 script seems not to know the font face I'm using!</a></h4>
2577 <p> The "FPDF" library we're using for this feature requires some
2578 special files to use font faces.<br />
2580 these files.</p>
2584 check PHP Configuration".</a></h4>
2586 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2587 "MySQL extension". This extension may be part of the PHP
2588 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2589 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2590 to load the extension but failed.<br /><br />
2592 Usually, the problem is solved by installing a software package called
2593 "PHP-MySQL" or something similar.</p>
2598 and I cannot log in using cookie auth.</a></h4>
2600 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2604 so I cannot upload.</a></h4>
2606 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2607 parameter is not set to "on".</p>
2611 a new table the table and field names are changed to lowercase!</a></h4>
2613 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2614 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2615 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2616 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2617 directory and add the following line to the group [mysqld]:</p>
2619 <pre>set-variable = lower_case_table_names=0</pre>
2621 <p> Next, save the file and restart the MySQL service. You can always check the
2622 value of this directive using the query</p>
2624 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2628 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2631 </p>
2635 and I get problems, such as undefined variables when I run a
2638 <p> A tip from Jose Fandos: put a comment on the following two lines
2639 in httpd.conf, like this:</p>
2641 <pre>
2642 # mod_gzip_item_include file \.php$
2644 </pre>
2646 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2647 PHP scripts. Of course you have to restart Apache.</p>
2652 I get the error "No input file specified" when trying to
2653 run phpMyAdmin.</a></h4>
2655 <p> This is a permission problem. Right-click on the phpmyadmin folder
2656 and choose properties. Under the tab Security, click on "Add"
2657 and select the user "IUSR_machine" from the list. Now set his
2658 permissions and it should work.</p>
2662 db_structure.php with plenty of tables).</a></h4>
2665 GZIP output buffering is enabled. If you turn off it (by
2667 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2668 PHP 5.0.0.</p>
2672 message 'Errorcode: 13'. What does this mean?</a></h4>
2674 <p> This can happen due to a MySQL bug when having database / table names with
2675 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2676 To fix this, turn off this directive, convert all database and table names
2677 to lower case and turn it on again. Alternatively, there's a bug-fix
2678 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2682 and the fields are duplicated.</a></h4>
2684 <p> It is possible to configure Apache in such a way that PHP has problems
2685 interpreting .php files.</p>
2687 <p> The problems occur when two different (and conflicting) set of directives
2688 are used:</p>
2690 <pre>
2691 SetOutputFilter PHP
2692 SetInputFilter PHP
2693 </pre>
2695 <p> and</p>
2697 <pre>AddType application/x-httpd-php .php</pre>
2699 <p> In the case we saw, one set of directives was in
2700 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2701 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2702 The recommended way is with <tt>AddType</tt>, so just comment out
2703 the first set of lines and restart Apache:</p>
2705 <pre>
2706 #SetOutputFilter PHP
2707 #SetInputFilter PHP
2708 </pre>
2713 <p> This problem is known to happen when the server is running Turck MMCache
2714 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2719 <p> Yes.<br />
2720 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2721 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2722 <tt>error_reporting</tt> settings.
2723 </p>
2726 <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>
2728 <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>
2731 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2732 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2733 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2734 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2735 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2736 enabled.) Click <tt>OK</tt>.</li>
2737 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2738 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2739 </ol>
2743 PHP 5.0.4 on 64-bit systems?</a></h4>
2745 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2746 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2752 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2753 Table and script parts are optional. If you want
2754 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2755 some configuration. Following lines apply only for <a
2757 that you have enabled some features within global configuration. You need
2758 <code>Options FollowSymLinks</code> and <code>AllowOverride
2759 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2760 you need mod_rewrite to be enabled. Then you just need to create following
2761 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2762 (don't forget to change directory name inside of it):</p>
2764 <pre>
2765 RewriteEngine On
2766 RewriteBase /path_to_phpMyAdmin
2767 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2768 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2769 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2770 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2771 </pre>
2774 <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>
2776 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2777 following rewrite rule:</p>
2779 <pre>
2780 RewriteEngine On
2781 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2782 </pre>
2786 </h4>
2787 <p>
2788 There can be many explanations to this and a look at your server's
2789 error log file might give a clue.
2790 </p>
2794 password encryption in cookie auth doesn't work.</a></h4>
2796 <p> If your cluster consist of different architectures, PHP code used for
2797 encryption/decryption won't work correct. This is caused by use of
2798 pack/unpack functions in code. Only solution is to use mcrypt extension
2799 which works fine in this case.</p>
2804 <p> Yes but the default configuration values of Suhosin are known to cause
2805 problems with some operations, for example editing a table with many
2806 columns and no primary key. Tuning information is available at
2808 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2809 although the parameter names have changed (<tt>suhosin</tt> instead
2811 <tt>SuhosinDisableWarning</tt> directive</a>.
2812 </p>
2818 headers already sent by ..." is displayed, what's the problem?</a></h4>
2820 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2821 (I.E. no blank lines, no spaces, no characters...) neither before the
2822 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2823 tag at the end. We also got a report from a user under IIS, that used
2824 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2825 contained an end-of-line character (hex 0A) at the end; removing this character
2826 cleared his errors.</p>
2831 <p> Either there is an error with your PHP setup or your username/password is
2832 wrong. Try to make a small script which uses mysql_connect and see if it
2833 works. If it doesn't, it may be you haven't even compiled MySQL support
2834 into PHP.</p>
2838 connect to local MySQL server through socket '/tmp/mysql.sock'
2839 (111) ..." is displayed. What can I do?</a></h4>
2841 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2843 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2844 In your <i>php.ini</i> you will find a line</p>
2846 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2848 <p> change it to</p>
2850 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2852 <p> Then restart apache and it will work.</p>
2854 <p> Here is a fix suggested by Brad Ummer:</p>
2856 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2857 To do this, telnet to your server and go to the MySQL bin directory. In
2858 this directory there should be a file named <i>mysqladmin</i>. Type
2859 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2860 info about your MySQL server, including the socket
2861 (<i>/tmp/mysql.sock</i>, for example).</li>
2862 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2863 phpMyAdmin, you need to complete the socket information in the
2864 <i>config.inc.php</i>.<br />
2865 For example:
2867 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2868 <br /><br />
2870 Please also make sure that the permissions of this file allow to be readable
2871 by your webserver (i.e. '0755').</li>
2872 </ul>
2874 <p> Have also a look at the
2876 corresponding section of the MySQL documentation</a>.</p>
2880 what can I do?</a></h4>
2883 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2884 sometime.<br />
2885 Also have a look at your PHP version number: if it contains "4.0b..."
2886 it means you're running a beta version of PHP. That's not a so good idea,
2887 please upgrade to a plain revision.</p>
2891 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2892 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2894 <p> Check the value you set for the
2896 directive in the phpMyAdmin configuration file.</p>
2900 password: YES)"-error when trying to access a MySQL-Server on a
2901 host which is port-forwarded for my localhost.</a></h4>
2903 <p> When you are using a port on your localhost, which you redirect via
2904 port-forwarding to another host, MySQL is not resolving the localhost
2905 as expected.<br />
2906 Erik Wasser explains: The solution is: if your host is "localhost"
2907 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2908 connection for speeding up things. And that doesn't work in this configuration
2909 with port forwarding.<br />
2915 <p> Themes are configured with
2919 <br />
2921 should not delete the directory "original" or its underlying
2922 structure, because this is the system theme used by phpMyAdmin.
2923 "original" contains all images and styles, for backwards
2924 compatibility and for all themes that would not include images or css-files.
2925 <br /><br />
2928 is enabled, you can select your favorite theme on the main page. Your
2929 selected theme will be stored in a cookie.<br /><br /></p>
2931 <p> To create a theme:</p>
2933 <ul><li>make a new subdirectory (for example "your_theme_name") under
2935 (by default <tt>themes</tt>)</li>
2936 <li>copy the files and directories from "original" to
2937 "your_theme_name"</li>
2938 <li>edit the css-files in "your_theme_name/css"</li>
2939 <li>put your new images in "your_theme_name/img"</li>
2940 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2941 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2942 contain your chosen theme name, that will be visible in user interface</li>
2943 <li>make a new screenshot of your theme and save it under
2944 "your_theme_name/screen.png"</li>
2945 </ul>
2947 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2948 theme verbose name, theme generation and theme version. These versions and
2949 generations are enumerated from 1 and do not have any direct dependence on
2950 phpMyAdmin version. Themes within same generation should be backwards
2951 compatible - theme with version 2 should work in phpMyAdmin requiring
2952 version 1. Themes with different generation are incompatible.</p>
2954 <p> If you do not want to use your own symbols and buttons, remove the
2955 directory "img" in "your_theme_name". phpMyAdmin will
2956 use the default icons and buttons (from the system-theme "original").
2957 </p>
2961 what can I do?</a></h4>
2963 <p> Here are a few points to check:</p>
2965 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2967 directive empty. See also
2969 </li>
2970 <li>Maybe you have a broken PHP installation or you need to upgrade
2971 your Zend Optimizer. See
2973 http://bugs.php.net/bug.php?id=31134</a>.
2974 </li>
2975 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2976 set to the default (200) or another low value, you could get this
2977 error if your table has a high number of columns. Adjust this setting
2978 accordingly. (Thanks to Klaus Dorninger for the hint).
2979 </li>
2980 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2981 of ";" will cause this error. Replace it with "&;".
2982 </li>
2984 you might want to increase
2986 </li>
2987 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
2988 </li>
2989 </ul>
2996 who logged out can not log in again in with the same nick.</a></h4>
2998 <p> This is related to the authentication mechanism (protocol) used by
2999 phpMyAdmin. To bypass this problem: just close all the opened
3000 browser windows and then go back to phpMyAdmin. You should be able to
3001 log in again.</p>
3005 limit error or a time limit error.</a></h4>
3007 <p> Compressed dumps are built in memory and because of this are limited to
3008 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3009 using
3011 (enabled by default). Zip exports can not be handled this way, so if you need
3012 Zip files for larger dump, you have to use another way.</p>
3016 or alter a table.</a></h4>
3018 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3022 bundled with the MySQL server distribution.</a></h4>
3024 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3026 <pre>
3027 -- MySQL dump 8.22
3028 --
3029 -- Host: localhost Database: database
3030 ---------------------------------------------------------
3031 -- Server version 3.23.54
3032 </pre>
3034 <p> The invalid part of the code is the horizontal line made of dashes that
3035 appears once in every dump created with mysqldump. If you want to run your
3036 dump you have to turn it into valid MySQL. This means, you have to add a
3037 whitespace after the first two dashes of the line or add a # before it:
3038 <br />
3039 <code>
3040 -- -------------------------------------------------------<br />
3041 </code>
3042 or<br />
3043 <code>
3044 #---------------------------------------------------------
3045 </code>
3046 </p>
3053 <p> Please note that you should not use the separating string multiple times
3054 without any characters between them, or at the beginning/end of your table
3055 name. If you have to, think about using another TableSeparator or disabling
3056 that feature</p>
3061 <p> In Relation view, being able to choose a table in another database,
3062 or having more than one index field in the foreign key.<br /><br/>
3063 In Query-by-example (Query), automatic generation of the query
3064 LEFT JOIN from the foreign table.<br /><br/>
3065 </p>
3069 I get series of errors like "Warning: unable to parse url". How
3070 can this be fixed?</a></h4>
3071 <p>
3072 Your table neither have a primary key nor an unique one, so we must use a
3073 long expression to identify this row. This causes problems to parse_url
3074 function. The workaround is to create a primary or unique key.
3075 <br />
3076 </p>
3080 a MIME-Transformation onto!</a></h4>
3082 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3083 nested forms can be put inside the table where phpMyAdmin displays the results.
3084 You can, however, use any form inside of a table if keep the parent
3085 form-container with the target to tbl_row_delete.php and just put your own
3086 input-elements inside. If you use a custom submit input field, the form will
3087 submit itself to the displaying page again, where you can validate the
3088 $HTTP_POST_VARS in a transformation.
3090 For a tutorial on how to effectively use transformations, see our
3092 on the official phpMyAdmin-homepage.</p>
3096 MySQL server</a></h4>
3098 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3101 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3102 the quote-character (") is interpreted as an identifier quote character and
3103 not as a string quote character, which makes many internal phpMyAdmin
3105 statements. There is no workaround to this behaviour. News to this item will
3106 be posted in Bug report
3107 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3108 </p>
3112 more that one column with the same value
3113 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3114 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3116 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3117 can use it for the Edit and Delete links.</p>
3122 <p> phpMyAdmin uses a quick method to get the row count, and this method
3123 only returns an approximate count in the case of InnoDB tables. See
3125 a way to modify those results, but
3126 this could have a serious impact on performance.</p>
3131 <p> The number of records in queries containing COUNT and GROUP BY is
3132 not correctly calculated. Also, sorting results of a query like
3137 containing an hyphen.
3138 </a></h4>
3139 <p>
3140 The tests I have made with current MySQL 4.1.11 API shows that the
3141 API does not accept this syntax for the USE command. Enclosing the
3142 db name with backquotes works. For further confusion, no backquotes
3143 are needed with command-line mysql.
3144 </p>
3147 <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>
3148 <p>
3149 This has been a known limitation of phpMyAdmin since the beginning and
3150 it's not likely to be solved in the future.
3151 </p>
3153 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3156 <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
3157 need to install it for each customer.
3158 </a></h4>
3159 <p>
3160 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3161 your users. The development of this feature was kindly sponsored by
3162 NetCologne GmbH.
3163 This requires a properly setup MySQL user management and phpMyAdmin
3164 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3166 </p>
3170 access.
3171 </a></h4>
3172 <p>
3173 This depends on your system.<br />
3174 If you're running a server which cannot be accessed by other people, it's
3175 sufficient to use the directory protection bundled with your webserver
3177 If other people have telnet access to your server, you should use
3178 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3179 <br /><br />
3180 Suggestions:
3181 </p>
3182 <ul>
3183 <li>
3185 </li>
3186 <li>
3187 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3188 is a user whose password is only known to you, and apache is the
3189 group under which Apache runs.
3190 </li>
3191 <li>
3192 You should use PHP safe mode, to protect from other users that try
3194 </li>
3195 </ul>
3200 </a></h4>
3201 <p>
3206 </p>
3209 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3210 authentication.
3211 </a></h4>
3215 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3216 and/or
3218 are wrong.</li>
3220 <li>You have already setup a security mechanism for the
3221 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3222 phpMyAdmin's authentication, so remove it.</li>
3223 </ul>
3230 and put the privileges you want. For example,
3232 would let a user create/manage his/her database(s).</p>
3237 <p> If you have existing rules from an old .htaccess file, you can take them
3240 be a major benefit here if your installation is suited to using it. Then
3241 you can just add those updated lines into the
3245 <p> If you want a pre-made sample, you can try this fragment. It stops the
3246 'root' user from logging in from any networks other than the private
3249 <pre>
3250 //block root from logging in except from the private networks
3251 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3252 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3253 'deny root from all',
3254 'allow root from localhost',
3258 );
3259 </pre>
3264 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3265 different than the one set in your
3267 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3268 while a domain name is defined in the config file.</p>
3273 <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>
3279 when trying to create a table with more than 14 fields.
3280 </a></h4>
3281 <p>
3282 We could reproduce this problem only under Win98/98SE. Testing under
3283 WinNT4 or Win2K, we could easily create more than 60 fields.
3284 <br />
3285 A workaround is to create a smaller number of fields, then come back to
3286 your table properties and add the other fields.
3287 </p>
3291 <p>
3292 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3293 with each script/website that use forms.<br />
3294 Upgrade or downgrade your Xitami server.
3295 </p>
3298 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3299 <p>
3300 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3301 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3302 don't seem to work.<br />
3304 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3305 the user's temporary directory, so they must be moved before closing
3306 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3309 </p>
3313 Explorer never stores the cookies.
3314 </a></h4>
3315 <p>
3316 MS Internet Explorer seems to be really buggy about cookies, at least till
3318 in this area!
3319 <br />
3320 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3321 work!
3322 </p>
3326 rows.
3327 </a></h4>
3328 <p>
3330 </p>
3333 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3334 when trying to modify a row in a table with many fields, or with a text field
3335 </a></h4>
3336 <p>
3337 Your table neither have a primary key nor an unique one, so we must use a
3338 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
3339 those browsers, and this not happen in Netscape, for example. The
3340 workaround is to create a primary or unique key, or use another browser.
3341 <br />
3342 </p>
3346 page.
3347 </a></h4>
3348 <p>
3349 Some browsers support right-clicking into the frame you want to refresh,
3350 just do this in the right frame.<br />
3351 </p>
3355 query box.
3356 </a></h4>
3357 <p>
3358 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3359 Mozilla versions.<br />
3360 </p>
3364 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3365 </a></h4>
3366 <p>
3367 This is a Mozilla bug (see bug #26882 at
3369 </p>
3374 </a></h4>
3375 <p>
3376 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3377 data in octet-stream mode. Since we can't detect the specific Netscape
3378 version, we cannot workaround this bug.
3379 </p>
3383 wrong.</a></h4>
3385 <p> Please ensure that you have set your browser's character set to the one of the
3386 language file you have selected on phpMyAdmin's start page.
3387 Alternatively, you can try the auto detection mode that is supported by the
3388 recent versions of the most browsers.</p>
3391 <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
3394 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3395 Netscape and Mozilla do not have this problem.</p>
3398 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3399 I cannot manage two servers: I log in to the first one, then the other one,
3400 but if I switch back to the first, I have to log in on each operation.</a></h4>
3406 but nothing happens after that, only a blank screen.</a></h4>
3409 bug in Opera6, because it is not able to interpret frameset definitions
3410 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3411 Opera7 at least.</p>
3420 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3425 address and you are starting
3427 containing a domain name, or the reverse situation.</li>
3428 <li>Security settings in IE and/or Microsoft Security Center are
3429 too high, thus blocking scripts execution.</li>
3430 <li>The Windows Firewall is blocking Apache and MySQL. You must
3434 </ul>
3437 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3438 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3439 installed in their Firefox is causing the problem.</p>
3446 </a></h4>
3447 <p>
3448 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3449 specifying a wrong field-type.<br />
3450 Common errors include:
3451 </p>
3452 <ul>
3455 </ul>
3456 <p>
3457 Also, look at the syntax chapter in the MySQL manual to confirm that your
3458 syntax is correct.
3459 </p>
3463 phpMyAdmin generates only one index with those 2 fields.
3464 </a></h4>
3465 <p>
3467 index. If you want two indexes, create the first one when creating the
3468 table, save, then display the table properties and click the Index link to
3469 create the other index.
3470 </p>
3474 <p>
3475 Since version 2.2.3, you have a checkbox for each field that can be null.
3477 field's value. Since version 2.5.5, you have to use the checkbox to get
3479 a literal NULL in the field, and not a NULL value (this works in PHP4).
3480 </p>
3485 <p> Click on a database or table name in the left frame, the properties will be
3487 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3488 statements that can be used to recreate your database/table.
3489 <br /><br />
3491 transmit the resulting dump to your station. Depending on your PHP
3492 configuration, you will see options to compress the dump. See also the
3494 configuration variable.<br /><br />
3497 this document.</p>
3502 </a></h4>
3504 <p> Click on a database name in the left frame, the properties will be
3506 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3508 the path to your dump filename, or use the Browse button. Then click Go.
3509 <br /><br />
3511 that you upgrade to take advantage of the new features.
3512 <br /><br />
3514 in this document.
3515 </p>
3520 <p> Here is an example with the tables persons, towns and countries, all
3522 table, create it as explained in the configuration section. Then create the
3523 example tables:</p>
3525 <pre>
3526 CREATE TABLE REL_countries (
3527 country_code char(1) NOT NULL default '',
3528 description varchar(10) NOT NULL default '',
3529 PRIMARY KEY (country_code)
3530 ) TYPE=MyISAM;
3532 INSERT INTO REL_countries VALUES ('C', 'Canada');
3534 CREATE TABLE REL_persons (
3535 id tinyint(4) NOT NULL auto_increment,
3536 person_name varchar(32) NOT NULL default '',
3538 country_code char(1) NOT NULL default '',
3539 PRIMARY KEY (id)
3540 ) TYPE=MyISAM;
3542 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3543 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3545 CREATE TABLE REL_towns (
3547 description varchar(30) NOT NULL default '',
3548 PRIMARY KEY (town_code)
3549 ) TYPE=MyISAM;
3551 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3552 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3553 </pre>
3559 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3563 </ul>
3571 <li>In the fields row, choose persons.person_name and click the
3573 <li>Do the same for towns.description and countries.descriptions in the
3576 the correct joins have been generated</li>
3578 </ul>
3582 <p>
3583 Starting from the previous example, create the pma_table_info as explained
3584 in the configuration section, then browse your persons table,
3585 and move the mouse over a town code or country code.
3586 <br /><br />
3587 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3588 enables: drop-down list of possible values.
3589 </p>
3592 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3593 <p>
3596 <br /><br />
3597 Then you need to think about your schema layout. Which tables will go on
3598 which pages?
3599 </p>
3600 <ul>
3606 page and click Go. If you like, you
3608 linked tables onto the new page.</li>
3609 <li>Select the name of the new page (making sure the Edit radio button
3610 is selected) and click Go.</li>
3612 Coordinates are relative; your diagram will
3613 be automatically scaled to fit the page. When initially placing tables
3614 on the page, just pick any coordinates -- say, 50x50. After clicking
3616 position the element correctly.</li>
3618 first be sure to click the Save
3619 button beneath the list of tables and coordinates, to save any changes
3620 you made there. Then scroll all the way down, select the
3622 you want, and click Go.</li>
3623 <li>Internet Explorer for Windows may suggest an incorrect filename when
3628 browsers on Windows, do not have this problem.</li>
3629 </ul>
3633 columns!</a></h4>
3635 <p> No, it's MySQL that is doing
3641 underscores in the database name?</a></h4>
3643 <p> If you do not put a backslash before the underscore, this is a wildcard
3646 john2db ...<br /><br />
3648 If you put a backslash before the underscore, it means that the database
3649 name will have a real underscore.</p>
3653 statistics pages?</a></h4>
3664 if it already exists during the import. It does NOT drop the table after
3665 your export, it only affects the import file.</li>
3667 Otherwise, you may get an error if the table name exists but has a
3668 different structure.</li>
3670 (if any) will be included in backup.</li>
3672 field and table names formed with special characters are protected.</li>
3674 types set in the pmadb in the dump as
3676 </li>
3677 </ul>
3682 command, for better documentation (but resulting file is bigger).</li>
3684 once the INSERT verb and the table name.</li>
3687 </li>
3689 more info is provided in the
3691 but basically with this selected, invalid values are adjusted and
3692 inserted rather than causing the entire statement to fail.</li>
3693 </ul>
3697 in its name.</a></h4>
3700 is the normal way to reference a database and table name. Worse, MySQL
3701 will usually let you create a database with a dot, but then you cannot
3702 work with it, nor delete it.</p>
3715 for usage.<br />
3716 On a more recent pear version, I had problems with the state of Net_DIME
3717 being beta, so this single command
3719 needed modules.<br />
3720 If you use the Validator, you should be aware that any
3722 submit will be stored anonymously (database/table/column names,
3723 strings, numbers replaced with generic values). The Mimer
3726 We utilize it as free SOAP service.</p>
3730 it, but MySQL says "BLOB column '...' used in key specification without
3733 <p> The right way to do this, is to create the field without any indexes,
3735 dialog. On this page, you will be able to choose your BLOB field, and
3736 set a size to the index, which is the condition to create an index on
3737 a BLOB field.</p>
3741 editing fields?</a></h4>
3743 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3744 with many editing fields (table structure changes, row editing, etc.)
3745 (must be enabled in configuration - see.
3747 You can also have a look at the directive
3749 ('vertical') and see if this eases up editing for you.</p>
3753 WTF is this feature then useful for?</a></h4>
3755 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3756 on them. Otherwise you could just put a comment on the field. Because entering
3757 your own mimetype will cause serious syntax checking issues and validation,
3758 this introduces a high-risk false-user-input situation. Instead you have to
3759 initialize mimetypes using functions or empty mimetype definitions.<br />
3760 Plus, you have a whole overview of available mimetypes. Who knows all those
3761 mimetypes by heart so he/she can enter it at will?</p>
3765 can't I see any bookmarks below the query box? What is this variable for?
3766 </a></h4>
3768 <p> Any query you have executed can be stored as a bookmark on the page where the
3769 results are displayed. You will find a button labeled 'Bookmark this query'
3770 just at the end of the page.<br />
3771 As soon as you have stored a bookmark, it is related to the database you run
3772 the query on. You can now access a bookmark dropdown on each page, the query
3773 box appears on for that database.<br /><br />
3775 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3779 aware of that you HAVE to create a valid query, otherwise your query won't be
3780 even able to be stored in the database.<br />
3782 for your query will remain the way it is, but will be stripped of the /**/
3783 chars. So you can use:<br /><br />
3787 which will be expanded to<br /><br />
3791 in your query, where VARIABLE is the string you entered in the input box. If
3792 an empty string is provided, no replacements are made.<br /><br />
3794 A more complex example. Say you have stored this query:<br /><br />
3796 <br /><br />
3799 the full query will be:<br /><br />
3802 <br /><br />
3806 spaces inserted there
3807 will be later also inserted as spaces in your query and may lead to unexpected
3808 results especially when
3810 Your initial query which is going to be stored as a bookmark has to yield at
3811 least one result row so
3812 you can store the bookmark. You may have that to work around using well
3816 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3817 include exported table?</a></h4>
3819 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3820 document should look like following one (assuming you have table
3823 <pre>
3824 \documentclass{article} % or any class you want
3825 \usepackage{longtable} % for displaying table
3826 \begin{document} % start of document
3827 \include{table} % including exported table
3828 \end{document} % end of document
3829 </pre>
3833 access them.
3834 </a></h4>
3837 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3838 enable users to see all the database names.
3841 So if your users do not need those privileges, you can remove them and their
3842 databases list will shorten.</p>
3846 possible values for a field, based on some foreign table?</a></h4>
3848 <p> You have to setup appropriate links between the tables, and also
3852 foreign table, a drop-down list of values will be available.
3853 You will see two lists of values, the first list containing the key
3854 and the display field, the second list containing the display field
3855 and the key. The reason for this is to be able to type the first
3856 letter of either the key or the display field.<br /><br />
3858 For 200 values or more, a distinct window will appear, to browse foreign
3859 key values and choose one.</p>
3863 automatically when entering Browse mode for a table?</a></h4>
3865 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3866 </p>
3870 Excel files, how can I enable that?</a></h4>
3872 <p> Current version does support direct export to Microsoft Excel and Word
3873 versions 2000 and newer. If you need export older versions, you can use
3875 which works out of the box or you can
3877 several problems, most important are limitation of cell content to 255
3878 chars and no support for charsets, so think carefully whether you want to
3879 enable this.</b>. For enabling this you need to set
3883 module Spreadsheet_Excel_Writer into php include path. The
3884 installation can be done by following command:</p>
3886 <pre>
3887 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3888 </pre>
3890 <p> First part of switches set we want to install beta version of that module
3891 (no stable version available yet) and then we tell pear we want to satisfy
3892 dependencies.</p>
3894 <p> If you are running in PHP safe mode, you will have to set
3897 modules are located, for example:</p>
3899 <pre>
3900 safe_mode_include_dir = /usr/local/lib/php
3901 </pre>
3905 <pre>
3906 cd phpMyAdmin
3907 mkdir tmp
3908 chmod o+rwx tmp
3909 </pre>
3913 what happens to my column comments stored in pmadb?</a></h4>
3915 <p> Automatic migration of a table's pmadb-style column comments to the native
3916 ones is done whenever you enter Structure page for this table.</p>
3923 <p> Our Bug Tracker is located at
3925 under the Bugs section.<br /><br />
3927 But please first discuss your bug with other users:<br />
3933 existing language, where do I start?</a></h4>
3935 <p> Always use the current SVN version of your language file.
3937 don't know how to get the SVN version, please ask one of the developers.
3938 <br />
3939 Please note that we try not to use HTML entities like &eacute; in
3940 the translations, since we define the right character set in the file.
3941 With HTML entities, the text on JavaScript messages would not
3942 display correctly.
3943 However there are some entities that need to be there, for quotes
3944 ,non-breakable spaces, ampersands, less than, greater than.<br />
3945 You can then put your translations, as a zip file to avoid losing special
3946 characters, on the sourceforge.net translation tracker.<br />
3947 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3948 list, because this is where we ask for translations of new messages.</p>
3952 phpMyAdmin. How should I proceed?</a></h4>
3957 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
3958 </li>
3960 <li>generate patch with your changes:
3962 </li>
3965 tracker of the phpMyAdmin project</a>.
3966 </li>
3967 </ol>
3969 <p> Write access to the SVN tree is granted only to experienced developers who
3970 have already contributed something useful to phpMyAdmin.<br />
3976 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3978 <p> Please refer to
3979 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3980 </p>
3982 <!-- DEVELOPERS -->
3985 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3986 great features have been written by other people and you too can help to
3987 make phpMyAdmin a useful tool.</p>
3989 <p> If you're planning to contribute source, please read the following
3990 information:</p>
3996 it free from other code.<br />
3997 Commonly used functions should be added to
4000 <li>Obviously, you're free to use whatever coding style you want. But
4001 please try to keep your code as simple as possible: beginners are
4002 using phpMyAdmin as an example application.<br />
4003 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4004 compliant on one hand, they fit the
4007 coding standards</a>
4008 on the other hand. Please pay attention to this.</li>
4009 <li>Please try to keep up the file-naming conventions. Table-related stuff
4012 <li>Please don't use verbose strings in your code, instead add the string
4017 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4018 better debug and profile their code.<br />
4019 Please see the
4021 options for more information.<br />
4022 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4023 lost during its re-entry into Earth's atmosphere and in memory of the
4024 brave men and women who gave their lives for the people of Earth.</li>
4025 </ul>
4027 <!-- CREDITS -->
4030 <pre>
4031 phpMyAdmin - Credits
4032 ====================
4034 CREDITS, in chronological order
4035 -------------------------------
4038 * creator of the phpmyadmin project
4042 * multi-language version
4043 * various fixes and improvements
4045 * current project maintainer
4048 * started SourceForge phpMyAdmin project in March 2001
4049 * sync'ed different existing CVS trees with new features and bugfixes
4050 * multi-language improvements, dynamic language selection
4051 * current project maintainer
4052 * many bugfixes and improvements
4055 * rewrote and optimized javascript, DHTML and DOM stuff
4056 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4057 generate XHTML1.0 and CSS2 compliant codes
4058 * improved the language detection system
4059 * many bugfixes and improvements
4062 * database maintenance controls
4063 * table type code
4065 * DB-based configuration (Not completed)
4068 * many bugfixes and improvements
4071 * bookmarks feature
4072 * multiple dump feature
4073 * gzip dump feature
4074 * zip dump feature
4077 * various fixes
4078 * moderator of the phpMyAdmin former users forum at phpwizard.net
4084 * rewrote and fix dump code
4085 * bugfixes
4088 * rewrote dump code for PHP4
4089 * mySQL table statistics
4090 * bugfixes
4093 * main author of the version 2.1.0.1
4094 * bugfixes
4098 * abstract database interface (PMA_DBI) with MySQLi support
4099 * privileges administration
4101 * various features and fixes
4102 * German language file updates
4105 * automatic joins in QBE
4106 * links column in printview
4107 * Relation view
4110 * enhanced index creation/display feature
4111 * feature to use a different charset for HTML than for MySQL
4112 * improvements of export feature
4113 * various features and fixes
4114 * Czech language file updates
4117 (http://sf.net/projects/phpmysqlformgen/)
4118 * suggested the patch for multiple table printviews
4121 * built the patch for vertical display of table rows
4122 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4123 * Improvement of column/db comments
4124 * (MIME)-Transformations for columns
4125 * Use custom alias names for Databases in left frame
4126 * hierarchical/nested table display
4127 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4128 * new icon sets
4129 * vertical display of column properties page
4130 * some bugfixes, features, support, German language additions
4133 * japanese kanji encoding conversion feature
4136 * the Cookie authentication mode
4139 * table relation-links feature
4142 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4143 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4144 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4150 * phpMyAdmin logo (until June 2004)
4153 * blowfish library from the Horde project
4156 * mysqli support
4157 * many bugfixes and improvements
4160 * redesign for 2.6.0
4161 * phpMyAdmin sailboat logo (June 2004)
4164 * Representation at conferences
4167 * interface improvements
4168 * various bugfixes
4170 - Ivan A Kirillov
4171 * new relations Designer
4173 And also to the following people who have contributed minor changes,
4174 enhancements, bugfixes or support for a new language since version 2.1.0:
4176 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4177 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4178 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4179 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4181 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4182 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4183 Luís V., Martijn W. van der Lee,
4184 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4188 Original Credits of Version 2.1.0
4189 ---------------------------------
4191 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4192 to create a web-based interface to MySQL using PHP3. Although I have not
4193 used any of his source-code, there are some concepts I've borrowed from
4194 him. phpMyAdmin was created because Peter told me he wasn't going to
4195 further develop his (great) tool.
4196 Thanks go to
4198 code for the check when dropping a table or database. He also suggested
4199 that you should be able to specify the primary key on tbl_create.php3. To
4200 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4201 well as a bug-report. Plus many smaller improvements.
4203 were introduced in 1.3.0 (including quite significant ones like the
4204 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4205 bug-fixes and help.
4207 language-independent by outsourcing the strings to a separate file. He
4208 also contributed the French translation.
4210 tbl_select.php3, a feature to display only some fields from a table.
4212 functions in tbl_change.php3. He also added the
4215 servers and is a regular contributor for bug-fixes.
4217 features for 2.0.6.
4218 The following people have contributed minor changes, enhancements, bugfixes
4219 or support for a new language:
4220 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4221 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4222 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4223 G. Wieggers.
4225 And thanks to everyone else who sent me email with suggestions, bug-reports
4226 and or just some feedback.
4227 </pre>
4233 <ul>
4235 - the default name of Apache's directory-level configuration file.</li>
4239 - a software application that enables a user to display and interact with
4240 text, images, and other information typically located on a web page at a
4241 website on the World Wide Web.</li>
4243 - a free software/open source data compression algorithm and program
4244 developed by Julian Seward.</li>
4246 - an important World Wide Web technology that enables a client web browser
4247 to request data from a program executed on the Web server.</li>
4249 - a log or record of changes made to a project.</li>
4251 - a computer system that accesses a (remote) service on another computer
4252 by some kind of network.</li>
4254 - a set of data values of a particular simple type, one for each row of
4255 the table.</li>
4257 - a packet of information sent by a server to a World Wide Web browser
4258 and then sent back by the browser each time it accesses that server.</li>
4260 - Comma-seperated values</li>
4263 - an organized collection of data.</li>
4266 - a PHP module that extends PHP with additional functionality.</li>
4268 - a list of commonly asked question and there answers.</li>
4270 - one part of divided data/columns.</li>
4272 - a field or group of fields in a database record that point to a key
4273 field or group of fields forming a key of another database record in some
4274 (usually different) table.</li>
4276 - the free PDF library</li>
4278 GD Graphics Library</a> - a library by Thomas Boutell and others for
4279 dynamically manipulating images.</li>
4282 - gzip is short for GNU zip, a GNU free software file compression
4283 program.</li>
4285 - any machine connected to a computer network, a node that has a hostname.</li>
4287 - the unique name by which a network attached device is known on a network.</li>
4289 (HyperText Transfer Protocol)</a>
4290 - the primary method used to transfer or convey information on the World
4291 Wide Web.</li>
4294 additional security measures.</li>
4295 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4296 - a set of Internet-based services for servers using Microsoft Windows.</li>
4298 - a feature that allows quick access to the rows in a table.</li>
4300 - a data-oriented protocol used by source and destination hosts for
4301 communicating data across a packet-switched internetwork.</li>
4303 - a unique number that devices use in order to identify and communicate
4304 with each other on a network utilizing the Internet Protocol standard.</li>
4306 (Internet Server Application Programming Interface)</a>
4307 - the API of Internet Information Services (IIS).</li>
4309 - a business or organization that offers users access to the Internet and related services.</li>
4311 - a most commonly used standard method of lossy compression for
4312 photographic images.</li>
4318 - line of personal computers is designed, developed, manufactured, and
4319 marketed by Apple Computer.</li>
4320 <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>
4321 - the operating system which is included with all currently shipping Apple
4322 Macintosh computers in the consumer and professional markets.</li>
4324 - a cryptographic library.</li>
4326 - the MCrypt PHP extension.</li>
4327 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4328 - an Internet Standard for the format of e-mail.</li>
4330 - some sort of extension for the Apache Webserver.</li>
4332 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4333 Management System (DBMS).</li>
4335 - the improved MySQL client PHP extension.</li>
4337 - the MySQL client PHP extension.</li>
4339 - open standard for office documents.</li>
4340 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4341 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4343 (Portable Document Format)</a>
4344 - a file format developed by Adobe Systems for representing two
4345 dimensional documents in a device independent and resolution independent
4346 format.</li>
4348 - the PHP Extension and Application Repository.</li>
4350 - the perl-compatible regular expression functions for PHP</li>
4352 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4353 programming language used mainly for developing server-side applications
4354 and dynamic web content, and more recently, a broader range of software
4355 applications.</li>
4357 - a connection through which data is sent and received.</li>
4359 - Request for Comments (RFC) documents are a series of memoranda
4360 encompassing new research, innovations, and methodologies applicable to
4361 Internet technologies.</li>
4365 - represents a single, implicitly structured data item in a table.</li>
4367 - a computer system that provides services to other computing
4368 systems over a network.</li>
4369 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4370 - handlers for different table types</li>
4372 - a form of inter-process communication.</li>
4374 Sockets Layer)</a>
4375 - a cryptographic protocol which provides secure communication on the Internet.</li>
4377 - Structured Query Language</li>
4379 - a set of data elements (cells) that is organized, defined and stored as
4380 horizontal rows and vertical columns where each item can be uniquely
4381 identified by a label or key or by it?s position in relation to other items.</li>
4384 - a type of archive file format: the Tape ARchive format.</li>
4386 - one of the core protocols of the Internet protocol suite.</li>
4390 - a sequence of characters, conforming to a standardized format, that is
4391 used for referring to resources, such as documents and images on the
4392 Internet, by their location.</li>
4394 - A computer (program) that is responsible for accepting HTTP requests
4395 from clients and serving them Web pages.</li>
4397 - a W3C-recommended general-purpose markup language for creating
4398 special-purpose markup languages, capable of describing many different
4399 kinds of data.</li>
4401 - a popular data compression and archival format.</li>
4403 - an open-source, cross-platform data compression library by Jean-loup
4404 Gailly and Mark Adler.</li>
4405 </ul>
4415 </body>
4416 </html>