| blob | e0271080f47ce4c1853a6bb37085992bfd0686fe |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 </li>
63 <li>You need GD2 support in PHP to display inline
65 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
198 provided for those who prefer a graphical installation. Creating a
200 still a quick way to get started and needed for some advanced features.
201 <ul><li>To manually create the file, simply use your text editor to
204 file) in the main (top-level) phpMyAdmin directory (the one
208 default value is okay for a particular setting, there is no
210 few directives to get going, a simple configuration may look
211 like this:
212 <pre>
213 <?php
214 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
216 $i=0;
217 $i++;
218 $cfg['Servers'][$i]['auth_type'] = 'cookie';
219 ?>
220 </pre>
221 Or, if you prefer to not be prompted every time you log in:
222 <pre>
223 <?php
225 $i=0;
226 $i++;
227 $cfg['Servers'][$i]['user'] = 'root';
228 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
229 ?>
230 </pre>
231 For a full explanation of possible configuration values, see the
237 directory. This is a security measure. On a Linux/Unix system you
238 can use the following commands:
239 <pre>
240 cd phpMyAdmin
241 mkdir config # create directory for saving
242 chmod o+rw config # give it world writable permissions
243 </pre>
244 And to edit an existing configuration, copy it over first:
245 <pre>
246 cp config.inc.php config/ # copy current configuration for editing
247 chmod o+w config/config.inc.php # give it world writable permissions
248 </pre>
249 On other platforms, simply create the folder and ensure that your
258 the webserver does not have the proper permissions you may see the
260 config/</tt> directory exists and has the proper permissions -
262 and upload (via FTP or some similar means) to the proper location.<br /><br />
264 Once the file has been saved, it must be moved out of the <tt>
265 config/</tt> directory and the permissions must be reset, again
266 as a security measure:
267 <pre>
268 mv config/config.inc.php . # move file to current directory
269 chmod o-rw config.inc.php # remove world read and write permissions
270 </pre>
271 Now the file is ready to be used. You can choose to review or edit
272 the file with your favorite editor, if you prefer to set some
273 advanced options which the setup script does not provide.</li></ul></li>
274 <li>If you are using the
276 protect the phpMyAdmin installation directory because using
277 config does not require a user to
278 enter a password to access the phpMyAdmin installation. Use of an alternate
279 authentication method is recommended, for example with
287 in your browser. phpMyAdmin should now display a welcome screen
288 and your databases, or a login dialog if using
290 authentication mode.</li>
292 webserver configuration. For Apache you can use supplied .htaccess file
293 in that folder, for other webservers, you should configure this yourself.
294 Such configuration prevents from possible path exposure and cross side
295 scripting vulnerabilities that might happen to be found in that code.</li>
296 </ol>
300 <p> For a whole set of new features (bookmarks, comments,
303 transformation, etc.) you need to create a set of special tables. Those
304 tables can be located in your own database, or in a central database for a
305 multi-user installation (this database would then be accessed by the
306 controluser, so no other user should have rights to it).</p>
315 installation.</p>
320 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
321 that you may need special (administrator) privileges to create the database
322 and tables, and that the script may need some tuning, depending on the
323 database name.</p>
328 section</a>. You will also need to have a controluser with the proper rights
335 unpacked one. Configuration files from very old versions (2.3.0 or before) may
336 require some tweaking as some options have been changed or removed.
338 statement that you might find near the end of your configuration file.</p>
342 is version-specific.</p>
345 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
346 you should run the SQL script found in
353 where you want to give users access to their own database and don't want
354 them to play around with others.<br />
355 Nevertheless be aware that MS Internet Explorer seems to be really buggy
357 in this area!<br />
360 that your user/password pair are not in clear in the configuration file.
361 </li>
364 authentication modes are more secure: the MySQL login information does
365 not need to be set in the phpMyAdmin configuration file (except possibly
367 However, keep in mind that the password travels in plain text, unless
368 you are using the HTTPS protocol.<br />
369 In cookie mode, the password is stored, encrypted with the blowfish
370 algorithm, in a temporary cookie.</li>
373 your MySQL server is previous to 4.1.2, or is running with
383 file under the
385 $cfg['Servers'][$i]['controluser']</a></tt> and
390 only an example: use something else in your file!</b> Input these
391 statements from the phpMyAdmin SQL Query window or mysql command–line
392 client.<br />
394 if it's not the same as the MySQL server's one.
396 <pre>
397 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
398 GRANT SELECT (
399 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
400 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
401 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
402 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
403 Execute_priv, Repl_slave_priv, Repl_client_priv
404 ) ON mysql.user TO 'pma'@'localhost';
405 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
406 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
407 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
408 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
410 If you are using an old MySQL version (below 4.0.2), please replace
411 the first GRANT SELECT query by this one:
413 <pre>
414 GRANT SELECT (
415 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
416 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
417 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
418 ) ON mysql.user TO 'pma'@'localhost';</pre>
420 ... and if you want to use the many new relation and bookmark features:
422 <pre>
424 </pre>
428 Of course, the above queries only work if your MySQL version supports
432 on a set of particular databases. Normally you shouldn't give global
433 privileges to an ordinary user, unless you understand the impact of those
434 privileges (for example, you are creating a superuser).<br />
438 <pre>
439 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
440 </pre>
442 What the user may now do is controlled entirely by the MySQL user
443 management system.<br />
445 authentication mode, you don't need to fill the user/password fields
447 array.</li>
448 </ul>
453 method and allows you to log in as any valid MySQL user.</li>
454 <li>Is supported with most PHP configurations. For
467 mode.</li>
468 </ul>
472 <ul><li>You can use this method as a replacement for the
474 (for example, if you're running
476 <li>Obviously, the user must enable cookies in the browser, but this is
477 now a requirement for all authentication modes.</li>
478 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
479 with the same username.</li>
480 <li>If you want to log in to arbitrary server see
485 not required.</li>
486 </ul>
490 <ul><li>This mode is a convenient way of using credentials from another
491 application to authenticate to phpMyAdmin.</li>
492 <li>The other application has to store login information into
493 session data.</li>
495 section.</li>
496 </ul>
499 <ul><li>This mode is the less secure one because it requires you to fill the
501 $cfg['Servers'][$i]['user']</a> and
503 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
504 can read your config.inc.php can discover your username and password).
505 <br />
512 is an entry explaining how to protect your configuration file.</li>
513 <li>For additional security in this mode, you may wish to consider the Host
514 authentication
516 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
518 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
519 directives.</li>
520 <li>Unlike cookie and http, does not require a user to log in when first
521 loading the phpMyAdmin site. This is by design but could allow any
522 user to access your installation. Use of some restriction method is
524 HTTP-AUTH directive or disallowing incoming HTTP requests at
525 one’s router or firewall will suffice (both of which
526 are beyond the scope of this manual but easily searchable with Google).</li>
527 </ul>
529 <!-- CONFIGURATION -->
533 users:</span> PHP does not seem to like
537 before saving a script you have modified.</p>
542 section to create one. This file only needs to contain the parameters you want to
543 change from their corresponding default value in
546 <p> The parameters which relate to design (like colors) are placed in
549 your site specific code to be included on start and end of each page.</p>
553 (with full path) to your phpMyAdmin installation's directory.
556 some web servers are case–sensitive.
559 Starting with version 2.3.0, it is advisable to try leaving this
560 blank. In most cases phpMyAdmin automatically detects the proper
561 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
562 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
563 A good test is to browse a table, edit a row and save it. There should
564 be an error message if phpMyAdmin is having trouble auto–detecting
565 the correct value. If you get an error that this must be set or if
566 the autodetect code fails to detect your path, please post a bug
567 report on our bug tracker so we can improve the code.</dd>
571 with master / foreign – tables (see
573 <br />
574 If you tried to set this up and it does not work for you, have a look on
576 use it. You will find a link that will analyze why those features have
577 been disabled.<br />
578 If you do not want to use those features set this variable to
582 <dd>A warning is displayed on the main page if Suhosin is detected.
584 from appearing.</dd>
588 domain to call phpMyAdmin inside a frame, and is a potential security
589 hole allowing cross-frame scripting attacks.</dd>
593 algorithm to encrypt the password.<br />
595 passphrase of your choice. It will be used internally by the blowfish
596 algorithm: you won’t be prompted for this passphrase. The maximum
601 MySQL servers. Therefore, a
603 been added which contains the login information for the different servers.
604 The first
606 contains the hostname of the first server, the second
608 the hostname of the second server, etc. In
610 server definition, however you can put as many as you need in
612 have to define all settings, just those you need to change).</dd>
616 $i-th MySQL-server. E.g. localhost.</dd>
621 ignores this port number and connects with the socket, so if you want
622 to connect to a port different from the default port, use
625 </dd>
629 To determine the correct socket, check your MySQL configuration or, using the
631 Among the resulting information displayed will be the socket used.</dd>
634 <dd>Whether to enable SSL for connection to MySQL server.
635 </dd>
638 <dd>What type connection to use with the MySQL server. Your options are
640 is nearly guaranteed to be available on all MySQL servers, while
641 sockets are not supported on some platforms.<br /><br />
643 To use the socket mode, your MySQL server must be on the same machine
644 as the Web server.</dd>
647 <dd>What php MySQL extension to use for the connection. Valid options are:
648 <br /><br />
651 The classic MySQL extension. This is the recommended and default
652 method at this time.<br /><br />
655 The improved MySQL extension. This extension became available
656 with php 5.0.0 and is the recommended way to connect to a server
660 <dd>Whether to use a compressed protocol for the MySQL server connection
661 or not (experimental).<br />
667 </dt>
669 all relational features (see
671 and, for a MySQL server previous to 4.1.2 or running with
674 authentication mode).<br /><br />
677 cookie authentication modes (or 'config'
678 authentication mode since phpMyAdmin 2.2.1), you need to supply the
683 This account is used to check what databases the user will see at
684 login.<br />
688 In phpMyAdmin versions before 2.2.5, those were called
692 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
693 <dd>Whether config or cookie or
695 should be used for this server.
697 is the plain old way: username and password are stored in
699 <li>'cookie' authentication mode
701 2.2.3 allows you to log in as any valid MySQL user with the
702 help of cookies. Username and password are stored in
703 cookies during the session and password is deleted when it
704 ends. This can also allow you to log in in arbitrary server if
705 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
706 </li>
707 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
708 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
709 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
710 <li>'signon' authentication mode
712 as introduced in 2.10.0 allows you to log in from prepared PHP
713 session data. This is useful for implementing single signon
714 from another application. Sample way how to seed session is in
720 </ul>
723 for more information.
724 </dd>
728 </dt>
729 <dd>
730 When using auth_type = 'config', this is the user/password-pair
731 which phpMyAdmin will use to connect to the
732 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
733 cookie authentication is used and should be empty.</dd>
735 <span
737 </dt>
738 <dd>
739 Allow attempt to log in without password when a login with password
740 fails. This can be used together with http authentication, when
741 authentication is done some other way and phpMyAdmin gets user name
742 from auth and uses empty password for connecting to MySQL. Password
743 login is still tried first, but as fallback, no password method is
744 tried.</dd>
747 </dt>
748 <dd>
749 If set to a (an array of) database name(s), only this (these) database(s)
750 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
751 database(s) name(s) may contain MySQL wildcards characters
755 This setting is an efficient way to lower the server load since the
756 latter does not need to send MySQL requests to build the available
758 privileges rules of the MySQL database server</span>. If set, it just
759 means only these databases will be displayed but
761 <br /><br />
763 An example of using more that one database:
765 <br /><br />
767 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
768 databases in the left frame, so that you can individually arrange your databases.<br />
769 If you want to have certain databases at the top, but don't care about the others, you do not
770 need to specify all other databases. Use:
772 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
773 order.</dd>
776 </dt>
777 <dd>Regular expression for hiding some databases. This only hides them
778 from listing, but a user is still able to access them (using, for example,
779 the SQL query area). To limit access, use the MySQL privilege system.
780 <br /><br />
785 More information on regular expressions can be found in the
787 PCRE pattern syntax</a> portion of the PHP reference manual.
788 </dd>
791 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
792 this string will be displayed instead of the hostname in the pull-down
793 menu on the main page. This can be useful if you want to show only
794 certain databases on your system, for example. For HTTP auth, all
795 non-US-ASCII characters will be stripped.</dd>
799 </dt>
800 <dd>The name of the database containing the linked-tables infrastructure.
801 <br /><br />
804 section in this document to see the benefits of this infrastructure,
805 and for a quick way of creating this database and the needed tables.
806 <br /><br />
808 If you are the only user of this phpMyAdmin installation, you can
809 use your current database to store those special tables; in this
810 case, just put your current database name in
812 set this parameter to the name of your central database containing
813 the linked-tables infrastructure.</dd>
817 </dt>
819 useful for queries you often run.<br /><br />
821 To allow the usage of this functionality:
823 <li>enter the table name in
825 </ul>
826 </dd>
830 </dt>
832 which field is a key in another table (a foreign key). phpMyAdmin
833 currently uses this to
834 <ul><li>make clickable, when you browse the master table, the data values
835 that point to the foreign table;</li>
837 when browsing the master table, if you move the mouse to a column
838 containing a foreign key (use also the 'table_info' table);<br />
841 <li>in edit/insert mode, display a drop-down list of possible foreign
845 <li>display links on the table properties page, to check referential
846 integrity (display missing foreign keys) for each described key;
847 </li>
851 schema of your database (also uses the table_coords table).</li>
852 </ul>
854 The keys can be numeric or character.<br /><br />
856 To allow the usage of this functionality:
859 infrastructure</li>
860 <li>put the relation table name in
862 <li>now as normal user open phpMyAdmin and for each one of your
863 tables where you want to use this feature, click
865 </li>
866 </ul>
870 future development of the cross-db relations.
871 </dd>
875 </dt>
876 <dd>
877 Since release 2.3.0 you can describe, in a special 'table_info'
878 table, which field is to be displayed as a tool-tip when moving the
879 cursor over the corresponding key.<br />
880 This configuration variable will hold the name of this special
881 table. To allow the usage of this functionality:
883 <li>put the table name in
885 <li>then for each table where you want to use this feature,
887 to choose the field.</li>
888 </ul>
890 </dd>
894 </dt>
897 the relations between your tables. To do this it needs two tables
902 schema output).<br /><br />
906 To allow the usage of this functionality:
909 infrastructure</li>
910 <li>put the correct table names in
913 </ul>
916 </dd>
920 </dt>
922 Since release 2.3.0 you can store comments to describe each column for
924 <br /><br />
926 Starting with release 2.5.0, comments are consequently used on the table
927 property pages and table browse view, showing up as tool-tips above the
928 column name (properties page) or embedded within the header of table in
929 browse view. They can also be shown in a table dump. Please see the
930 relevant configuration directives later on.<br /><br />
932 Also new in release 2.5.0 is a MIME-transformation system which is also
934 Transformations</a> for further information. To use the
935 MIME-transformation system, your column_info table has to have the three
936 new fields 'mimetype', 'transformation', 'transformation_options'.
937 <br /><br />
939 To allow the usage of this functionality:
941 infrastructure</li>
942 <li>put the table name in
946 <pre>
947 ALTER TABLE `pma_column_comments`
948 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
949 ADD `transformation` VARCHAR( 255 ) NOT NULL,
950 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
951 </pre>
954 renamed from<br />
957 </ul>
958 </dd>
962 </dt>
965 all queries you entered manually into the phpMyAdmin interface. If you
966 don't want to use a table-based history, you can use the JavaScript-based
967 history. Using that, all your history items are deleted when closing the
968 window.<br /><br />
970 Using
972 you can specify an amount of history items you want to have on hold. On
973 every login, this list gets cut to the maximum amount.<br /><br />
975 The query history is only available if JavaScript is enabled in your
976 browser.<br /><br />
978 To allow the usage of this functionality:
981 infrastructure</li>
983 </li>
984 </ul>
985 </dd>
989 </dt>
991 to visually manage the relations.
992 <br /><br />
994 To allow the usage of this functionality:
997 infrastructure</li>
999 </li>
1000 </ul>
1001 </dd>
1004 </dt>
1006 column_info table got enhanced with three new fields. If the above variable
1008 latest table structure available. If not, it will emit a warning to the
1009 superuser.<br /><br />
1011 You can disable this checking behavior by setting the variable to false,
1012 which should offer a performance increase.<br /><br />
1014 Recommended to set to FALSE, when you are sure, your table structure is
1015 up to date.</dd>
1017 boolean</dt>
1018 <dd>Whether to allow root access. This is just simplification of rules below.
1019 </dd>
1022 </dt>
1024 authentication is disabled.<br /><br />
1027 all deny rules followed by allow rules. Access is allowed by default. Any
1028 client which does not match a Deny command or does match an Allow command
1029 will be allowed access to the server. <br /><br />
1032 applies all allow rules followed by deny rules. Access is denied by
1033 default. Any client which does not match an Allow directive or does
1034 match a Deny directive will be denied access to the server.<br /><br />
1036 If your rule order is set to 'explicit', the authentication is
1037 performed in a similar fashion to rule order 'deny,allow', with the
1041 and was available in Apache by specifying allow and deny rules without
1042 setting any order.<br /><br />
1044 Please also see <a
1046 address behind proxies.
1047 </dd>
1049 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1050 </dt>
1051 <dd>The general format for the rules is as such:
1053 <pre>
1055 </pre>
1060 well (please note that those containing SERVER_ADDRESS might not be
1061 available on all webservers):
1062 <pre>
1068 </pre>
1070 Having an empty rule list is equivalent to either using
1076 following work:<br />
1078 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1079 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1080 But the following does not work:<br />
1083 </dd>
1084 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1085 <dd>Name of session which will be used for signon authentication method.
1086 </dd>
1088 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1089 </dd>
1091 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1092 </dd>
1095 <dd>If you have more than one server configured, you can set
1097 that server when phpMyAdmin is started, or set it to 0 to be given a
1098 list of servers without logging in.<br />
1100 MUST be set to that server.</dd>
1103 <dd>The maximum number of database names to be displayed in the
1104 navigation frame and the database list.</dd>
1107 <dd>The maximum number of table names to be displayed in the
1108 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1109 when in Light mode.</dd>
1112 <dd>The maximum number of characters when a SQL query is displayed. The
1113 default limit of 1000 should be correct to avoid the display of tons
1114 of hexadecimal codes that represent BLOBs, but some users have real
1115 SQL queries that are longer than 1000 characters. Also, if a query's
1116 length exceeds this limit, this query is not saved in the history.</dd>
1119 <dd>Defines whether to use GZip output buffering for increased
1121 Set to true/false for enabling/disabling. When set to 'auto' (string),
1122 phpMyAdmin tries to enable output buffering and will automatically disable
1123 it if your browser has some problems with buffering. IE6 with a certain patch
1124 is known to cause data corruption when having enabled buffering.</dd>
1127 <dd>Whether persistent connections should be used or not (mysql_connect or
1128 mysql_pconnect).</dd>
1134 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1135 to zero, no time limit is imposed.<br />
1136 This setting is used while importing/exporting dump files but has no
1137 effect when PHP is running in safe mode.</dd>
1140 <dd>Set the number of bytes a script is allowed to allocate. If number set
1141 to zero, no limit is imposed.<br />
1142 This setting is used while importing/exporting dump files but has no
1143 effect when PHP is running in safe mode.<br />
1147 <dd>Mark used tables and make it possible to show databases with locked
1152 generated by phpMyAdmin should be displayed or not.</dd>
1155 <dd>Defines whether normal users (non-administrator) are allowed to
1156 delete their own database or not. If set as FALSE, the link "Drop
1158 mydatabase" will be rejected. Quite practical for
1160 customers.<br />
1161 Please note that this limitation of SQL queries is not as strict as
1162 when using MySQL privileges. This is due to nature of SQL queries
1163 which might be quite complicated. So this choice should be viewed as
1164 help to avoid accidental dropping rather than strict privilege
1165 limitation.</dd>
1169 displayed when you're about to lose data.</dd>
1172 <dd>Define whether the previous login should be recalled or not in cookie
1173 authentication mode.</dd>
1180 means that it will be kept for existing session. This is recommended
1181 for not trusted environments.</dd>
1184 <dd>If enabled (default), logout deletes cookies for all servers,
1185 otherwise only for current one. Setting this to false makes it easy to
1186 forget to log out from other server, when you are using more of
1187 them.</dd>
1193 <dd>Define whether phpMyAdmin will continue executing a multi-query
1194 statement if one of the queries fails. Default is to abort execution.</dd>
1197 <dd>Define whether phpMyAdmin will output the results of each query of a
1198 multi-query statement embedded into the
1203 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1204 <br /><br />
1207 MySQL servers behind the firewall where your
1209 </dd>
1212 <dd>Defines whether to use a select-based menu and display only the current
1213 tables in the left frame (smaller page). Only in Non-Lightmode you can
1214 use the feature to display nested folders using
1216 </dd>
1219 <dd>In light mode, defines whether to display the names of databases (in the
1220 selector) using a tree, see also
1222 </dd>
1225 <dd>The string used to separate the parts of the database name when showing
1226 them in a tree.</dd>
1229 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1230 This means if you have tables like 'first__second__third' this will be
1232 If set to FALSE or empty, the feature is disabled. NOTE: You should
1233 not use this separator at the beginning or end of a
1234 table name or multiple times after another without any other
1235 characters in between.</dd>
1238 <dd>Defines how many sublevels should be displayed when splitting
1239 up tables by the above separator.</dd>
1242 <dd>Defines whether to display table comment as tool-tip in left frame or
1243 not.</dd>
1246 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1247 comment and the real name. That means that if you have a table called
1248 'user0001' and add the comment 'MyName' on it, you will see the name
1249 'MyName' used consequently in the left frame and the tool-tip shows
1250 the real name of the DB.</dd>
1253 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1255 When setting this to 'nested', the Alias of the Tablename is only used
1256 to split/nest the tables according to the
1258 directive. So only the folder is called like the Alias, the tablename itself
1259 stays the real tablename.</dd>
1262 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1265 <dd>Enter URL where logo in the navigation frame will point to.
1266 For use especially with self made theme which changes this.
1275 <dd>Defines whether or not to display a server choice at the top of the left frame.
1276 Defaults to FALSE.</dd>
1278 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1279 Defaults to FALSE (drop-down).</dd>
1281 <dd>Defines whether to display database choice in light navigation frame as links
1282 instead of in a drop-down. Defaults to 'auto' - on main page list is
1283 shown, when database is selected, only drop down is displayed.</dd>
1285 <dd>Defines whether or not to display space usage and statistics about databases
1286 and tables.<br />
1287 Note that statistics requires at least MySQL 3.23.3 and that, at this
1288 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1291 <dd>Defines whether to display detailed server information on main page.
1292 You can additionally hide more information by using
1294 </dd>
1299 </dt>
1302 not at the starting main (right) frame. This setting
1303 does not check MySQL commands entered directly.<br /><br />
1305 Please note that to block the usage of phpinfo() in scripts, you
1312 hard coded password value in the configuration file, end users can't
1313 be allowed to change their passwords.</dd>
1316 <dd>Defines whether to suggest a database name on the
1321 content.</dd>
1324 <dd>Defines whether navigation bar buttons and the right panel top menu
1325 contain text or symbols only. A value of TRUE displays icons, FALSE
1326 displays text and 'both' displays both icons and text.</dd>
1329 <dd>Defines whether a user should be displayed a
1333 <dd>Number of rows displayed when browsing a result set. If the result set
1340 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1344 from editing when browsing a table's content. Valid values are:
1349 </ul>
1350 </dd>
1353 <dd>Defines whether or not MySQL functions fields should be initially
1354 displayed in edit/insert mode. Since version 2.10, the user can
1355 toggle this setting from the interface.
1356 </dd>
1359 <dd>Defines which type of editing controls should be used for CHAR and
1360 VARCHAR fields. Possible values are:
1361 <ul><li>input - this allows to limit size of text to size of field in
1362 MySQL, but has problems with newlines in fields</li>
1363 <li>textarea - no problems with newlines in fields, but also no
1364 length limitations</li>
1365 </ul>
1366 Default is old behavior so input.</dd>
1372 <dd>If there are fewer items than this in the set of foreign keys, then a
1373 drop-down box of foreign keys is presented, in the style described by the
1375 setting.</dd>
1378 <dd>For the foreign key drop-down fields, there are several methods of
1379 display, offering both the key and value data. The contents of the
1380 array should be one or both of the following strings:
1386 </dt>
1387 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1388 creating a dump file</dd>
1391 </dt>
1392 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1393 compressed exports. This doesn't affect smaller dumps and allows users to
1394 create larger dumps that won't otherwise fit in memory due to php
1395 memory limit. Produced files contain more GZip/BZip2 headers, but all
1396 normal programs handle this correctly.</dd>
1400 mainframe.</dd>
1404 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1409 <dd>How many columns will be utilized to display the tables on the
1410 database property view? Default is 1 column. When setting this to a
1411 value larger than 1, the type of the database will be omitted for more
1412 display space.</dd>
1416 <dd>Defines the tab displayed by default on server view. Possible
1423 <dd>Defines the tab displayed by default on database view. Possible
1428 <dd>Defines the tab displayed by default on table view. Possible
1435 points to the MySQL documentation (type depends
1436 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1437 generated.<br />
1439 for more information about MySQL manuals and their types.</dd>
1442 <dd>Type of MySQL documentation:
1448 </ul>
1449 </dd>
1452 <dd>Defines the default language to use, if not browser-defined or
1453 user-defined.<br />
1455 this setting.</dd>
1458 <dd>Defines the default connection collation to use, if not
1459 user-defined.<br />
1464 <dd>Force: always use this language (must be defined in the
1468 <dd>Limit list of available languages to those matching the given regular
1469 expression. For example if you want only Czech and English, you should
1473 <dd>Default character set to use for recoding of MySQL queries. This must be
1474 enabled and it's described by
1476 option.<br />
1477 You can give here any character set which is in
1479 array and this is just default choice, user can select any of them.</dd>
1482 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1483 support (compiled in or module) in PHP to allow MySQL queries recoding
1484 and used language file must have it enabled (by default only these
1485 which are in Unicode, just to avoid losing some characters).<br /><br />
1488 in the Export page, to choose the character set when exporting a file.
1489 </dd>
1492 <dd>You can select here which functions will be used for character set
1493 conversion. Possible values are:
1494 <ul><li>auto - automatically use available one (first is tested
1495 iconv, then recode)</li>
1498 </ul>
1499 Default is auto.</dd>
1502 <dd>Specify some parameters for iconv used in charset conversion. See
1505 used, so that invalid characters will be transliterated.</dd>
1508 <dd>Available character sets for MySQL conversion. You can add your own (any of
1509 supported by recode/iconv) or remove these which you don't use.
1510 Character sets will be shown in same order as here listed, so if you
1511 frequently use some of these move them to the top.</dd>
1516 default empty, you need to fill in some trusted proxy servers if you
1517 want to use rules for IP addresses behind proxy.<br /><br />
1519 The following example specifies that phpMyAdmin should trust a
1521 <pre>
1522 $cfg['TrustedProxies'] =
1524 </pre>
1525 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1526 client's IP address as usual.
1527 </dd>
1531 MIME transformations.<br />
1532 Possible values are:
1533 <ul><li>auto - automatically detect, this is a bit expensive
1535 according to your server real possibilities</li>
1538 </ul>
1539 Default is auto.
1540 </dd>
1544 </dd>
1546 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1547 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1548 </dt>
1549 <dd>The background styles used for both the frames.
1552 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1554 <dd>The style used for the pointer in the navi frame.
1558 <dd>The color used for the database name in the navi frame.
1567 </dd>
1571 <dd>The style used for table headers. See
1576 </dd>
1580 </dd>
1582 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1584 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1586 </dt>
1588 The former feature highlights the row over which your mouse is passing
1589 and the latter lets you visually mark/unmark rows by clicking on
1590 them.<br />
1595 <dd>You put here a valid CSS font family value, for example
1600 <dd>You put here a valid CSS font family value, for example
1614 </dt>
1616 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1618 The Char* values are used for CHAR and VARCHAR editing (if configured
1622 </dt>
1626 </dt>
1627 <dd>Defines if the whole textarea of the query box will be selected on
1628 click.</dd>
1631 </dt>
1632 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1633 editing.</dd>
1636 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1637 Can be turned off by a toggle button on the browse page.</dd>
1641 </dt>
1642 <dd>Defines the place where modify and delete links would be put when
1643 tables contents are displayed (you may have them displayed both at the
1644 left and at the right).
1650 </dt>
1652 Define which one is displayed by default. The first mode displays each
1653 row on a horizontal line, the second rotates the headers by 90
1654 degrees, so you can use descriptive headers even though fields only
1655 contain small values and still print them out. The vertical mode sorts
1656 each row on a vertical lineup.<br /><br />
1658 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1659 the rotation of the header for horizontalflipped is done via CSS. If
1660 set to 'fake' PHP does the transformation for you, but of course this
1661 does not look as good as CSS.</dd>
1665 string or integer</dt>
1666 <dd>When editing/creating new columns in a table all fields normally get
1667 lined up one field a line. (default: 'horizontal'). If you set this to
1668 'vertical' you can have each field lined up vertically beneath each
1669 other. You can save up a lot of place on the horizontal direction and
1670 no longer have to scroll. If you set this to integer, editing of fewer
1671 columns will appear in 'vertical' mode, while editing of more fields
1672 still in 'horizontal' mode. This way you can still effectively edit
1673 large number of fields, while having full view on few of them.</dd>
1677 </dt>
1679 display of column comments in Browse or Property display. In browse
1680 mode, the comments are shown inside the header. In property mode,
1681 comments are displayed using a CSS-formatted dashed-line below the
1682 name of the field. The comment is shown as a tool-tip for that field.
1683 </dd>
1695 <dd>Whether to display a link to validate a query in any SQL Query box.
1702 <dd>
1703 The name of the directory where
1705 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1706 are available under a drop-down box when you click the database or
1707 table name, then the Import tab.
1708 <br /><br />
1710 If you want different directory for each user, %u will be replaced
1711 with username.<br /><br />
1715 compressed formats is enabled).<br /><br />
1717 This feature is useful when your file is too big to be uploaded via
1719 uploads are disabled in PHP.<br /><br />
1721 Please note that if PHP is running in safe mode, this directory must
1722 be owned by the same user as the owner of the phpMyAdmin scripts.
1723 <br /><br />
1727 alternatives.
1728 </dd>
1731 <dd>
1732 The name of the directory where dumps can be saved.<br /><br />
1734 If you want different directory for each user, %u will be replaced
1735 with username.<br /><br />
1737 Please note that the directory must exist and has to be writable
1738 for the user running the webserver.<br /><br />
1740 Please note that if PHP is running in safe mode, this directory must
1741 be owned by the same user as the owner of the phpMyAdmin scripts.
1742 </dd>
1745 <dd>
1746 The name of the directory where temporary files can be stored.
1747 <br /><br />
1748 This is needed for native MS Excel export, see
1751 </dd>
1754 <dd>
1755 In this array are defined default parameters for export, names of
1756 items are similar to texts seen on export page, so you can easily
1757 identify what they mean.
1758 </dd>
1761 <dd>
1762 In this array are defined default parameters for import, names of
1763 items are similar to texts seen on import page, so you can easily
1764 identify what they mean.
1765 </dd>
1768 <dd>
1769 Repeat the headers every X cells, or 0 to deactivate.
1770 </dd>
1778 </dt>
1779 <dd>
1780 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1781 or icon is always displayed on the left panel. If JavaScript is enabled in
1782 your browser, a click on this opens a distinct query window, which is
1783 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1784 changes to display a query box.<br /><br />
1786 The size of this query window can be customized with
1788 - both integers for the size in pixels. Note that normally, those
1790 theme you are using.<br /><br />
1794 opens the query window and puts the current query
1795 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1796 query in the right panel's query box.
1797 <br /><br />
1798 The usage of the JavaScript query window is recommended if you have a
1799 JavaScript enabled browser. Basic functions are used to exchange quite
1800 a few variables, so most 4th generation browsers should be capable to
1801 use that feature. It currently is only tested with Internet Explorer 6
1802 and Mozilla 1.x.
1803 <br /><br />
1805 to a table, which has to be created by you (see <a
1807 all your queries will be appended to the form, but only as long as
1808 your window is opened they remain saved.
1809 <br /><br />
1810 When using the JavaScript based query window, it will always get
1811 updated when you click on a new table/db to browse and will focus if
1812 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1813 the query window by checking the box "Do not overwrite this query from
1814 outside the window" below the query textarea. Then you can browse
1815 tables/databases in the background without losing the contents of the
1816 textarea, so this is especially useful when composing a query with
1817 tables you first have to look in. The checkbox will get automatically
1818 checked whenever you change the contents of the textarea. Please
1819 uncheck the button whenever you definitely want the query window to
1820 get updated even though you have made alterations.
1821 <br /><br />
1824 <br /><br />
1825 The query window also has a custom tabbed look to group the features.
1827 default tab to be used when opening the query window. It can be set to
1828 either 'sql', 'files', 'history' or 'full'.</dd>
1834 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1836 If the approximate row count as returned by
1839 count will be used.
1840 </dd>
1842 <dd>For VIEWs, since obtaining the exact count could have an
1843 impact on performance, this value is the maximum to be displayed, using
1845 any row counting.
1846 </dd>
1850 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1852 page. By clicking on the button 'toggle scratchboard' on the page
1853 where you edit x/y coordinates of those elements you can activate a
1854 scratchboard where all your elements are placed. By clicking on an
1855 element, you can move them around in the pre-defined area and the x/y
1856 coordinates will get updated dynamically. Likewise, when entering a
1857 new position directly into the input field, the new position in the
1858 scratchboard changes after your cursor leaves the input field.<br />
1859 You have to click on the 'OK'-button below the tables to save the new
1860 positions. If you want to place a new element, first add it to the
1861 table of elements and then you can drag the new element around.<br />
1862 By changing the paper size and the orientation you can change the size
1863 of the scratchboard as well. You can do so by just changing the
1864 dropdown field below, and the scratchboard will resize automatically,
1865 without interfering with the current placement of the elements.<br />
1866 If ever an element gets out of range you can either enlarge the paper
1867 size or click on the 'reset' button to place all elements below each
1868 other.<br />
1870 get this control to work. The basic Drag&Drop script functionality
1871 was kindly borrowed from www.youngpup.net and is underlying so
1872 specific license.</dd>
1875 <dd>Sorts database and table names according to natural order (for example,
1876 t1, t2, t10). Currently implemented in the left panel (Light mode)
1877 and in Database view, for the table list.</dd>
1883 <dd>Allows you to specify window's title bar. Following magic string can
1884 be used to get special values:
1885 <dl>
1891 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1900 </dl>
1901 </dd>
1911 </dd>
1914 <dd>If theme manager is active, use this as the path of the subdirectory
1915 containing all the themes.</dd>
1929 </dt>
1930 <dd>Default queries that will be displayed in query boxes when user didn't
1931 specify any. Use %d for database name, %t for table name and %f for a
1932 comma separated list of field names. Note that %t and %f are only
1936 <dd>
1937 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
1938 default we use HTML to format the query, but you can disable this by
1940 </dd>
1943 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1944 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1945 query inside a bracket is indented. By changing
1948 specifies the units of the indent amount that you specified. This is
1949 used via stylesheets.</dd>
1952 <dd>This array is used to define the colours for each type of element of
1953 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1955 If you specify an empty string for the color of a class, it is ignored
1956 in creating the stylesheet.
1957 You should not alter the class names, only the colour strings.<br />
1978 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1982 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1983 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1984 </ul>
1985 </dd>
1989 <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,
1990 as originally published on
1992 <br />
1993 For help in setting up your system to use the service, see the
1995 </dd>
1999 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2000 and any password, so we use those by default. Instead, if
2001 you have an account with them, you can put your login details
2002 here, and it will be used in place of the anonymous login.</dd>
2003 </dl>
2004 </dd>
2007 <dd><b>DEVELOPERS ONLY!</b></dd>
2010 <dd><b>DEVELOPERS ONLY!</b><br />
2011 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2012 the code.<br />
2013 For help in setting up your system to this, see the
2017 <dd><b>DEVELOPERS ONLY!</b><br />
2018 Enable profiling support for phpMyAdmin. This will append a chunk of data
2019 to the end of every page displayed in the main window with profiling
2020 statistics for that page.<br />
2021 You may need to increase the maximum execution time for this to
2022 complete successfully.<i>Profiling was removed from the code for
2023 version 2.9.0 due to licensing issues.</i></dd>
2025 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2026 <dd><b>DEVELOPERS ONLY!</b><br />
2027 When profiling data is displayed, this variable controls the threshold of
2028 display for any profiling data, based on the average time each time has
2029 taken. If it is over the threshold it is displayed, otherwise it is not
2030 displayed. This takes a value in milliseconds. In most cases you don't need
2031 to edit this.</dd>
2034 <dd>All possible types of a MySQL column. In most cases you don't need to
2035 edit this.</dd>
2038 <dd>Possible attributes for fields. In most cases you don't need to edit
2039 this.</dd>
2042 <dd>A list of functions MySQL supports. In most cases you don't need to
2043 edit this.</dd>
2046 <dd>Mapping of column types to meta types used for preferring displayed
2047 functions. In most cases you don't need to edit this.</dd>
2050 <dd>Functions preferred for column meta types as defined in
2051 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2052 to edit this.</dd>
2055 <dd>Functions selected by default when inserting/changing row, Functions
2056 are defined for meta types from
2058 <code>first_timestamp</code>, which is used for first timestamp column
2059 in table.</dd>
2062 <dd>Operators available for search operations on numeric and date fields.
2063 </dd>
2066 <dd>Operators available for search operations on character fields.
2067 Note that we put <code>LIKE</code> by default instead of
2068 <code>LIKE %...%</code>, to avoid unintended performance problems
2069 in case of huge tables.</dd>
2072 <dd>Operators available for search operations on enum fields.</dd>
2075 <dd>Additional operators available for search operations when the
2076 field can be null.</dd>
2078 </dl>
2080 <!-- TRANSFORMATIONS -->
2086 </ol>
2090 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2092 section</a> on how to do so.</p>
2094 <p> You can apply different transformations to the contents of each field. The
2095 transformation will take the content of each field and transform it with
2096 certain rules defined in the selected transformation.</p>
2098 <p> Say you have a field 'filename' which contains a filename. Normally you would
2099 see in phpMyAdmin only this filename. Using transformations you can transform
2100 that filename into a HTML link, so you can click inside of the phpMyAdmin
2101 structure on the field's link and will see the file displayed in a new browser
2102 window. Using transformation options you can also specify strings to
2103 append/prepend to a string or the format you want the output stored in.</p>
2105 <p> For a general overview of all available transformations and their options,
2106 you can consult your
2107 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2108 installation.</p>
2110 <p> For a tutorial on how to effectively use transformations, see our
2112 the official phpMyAdmin homepage.</p>
2116 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2117 clicking on the 'Structure' link for a table). There click on
2118 "Change" (or change icon) and there you will see three new fields at
2119 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2120 'Transformation options'.</p>
2122 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2123 that corresponds to the column's contents. Please note that
2124 transformations are inactive as long as no MIME-type is selected.</li>
2126 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2127 hopefully growing amount of pre-defined transformations. See below for information on
2128 how to build your own transformation.<br />
2130 There are global transformations and mimetype-bound transformations. Global transformations
2131 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2132 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2133 transformations which operate on the main mimetype (like 'image'), which will most likely
2134 take the subtype into regard, and those who only operate on a
2135 specific subtype (like 'image/jpeg').<br />
2137 You can use transformations on mimetypes for which the function was not defined for. There
2138 is no security check for you selected the right transformation, so take care of what the
2139 output will be like.</li>
2141 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2142 transform-function specific options here. Usually the transforms can operate with default
2143 options, but it is generally a good idea to look up the overview to see which options are
2144 necessary.<br />
2146 Much like the ENUM/SET-Fields, you have to split up several options using the format
2147 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2148 parsed as an array, leaving the first value the first element in the array, and so
2149 forth.<br />
2151 If you want to specify a MIME character set you can define it in the transformation_options.
2152 You have to put that outside of the pre-defined options of the specific mime-transform,
2154 for which you can specify 2 options and you want to append a character set, enter "'first
2155 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2157 </ul>
2161 <p> All mimetypes and their transformations are defined through single files in
2162 the directory 'libraries/transformations/'.</p>
2164 <p> They are stored in files to ease up customization and easy adding of new
2165 transformations.</p>
2167 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2168 always work. It makes no sense to apply a transformation to a mimetype, the
2169 transform-function doesn't know to handle.</p>
2171 <p> One can, however, use empty mime-types and global transformations which should work
2172 for many mimetypes. You can also use transforms on a different mimetype they where built
2173 for, but pay attention to option usage as well as what the transformation does to your
2174 field.</p>
2176 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2177 any other transform function and provides some basic functions.</p>
2179 <p> There are 5 possible file names:</p>
2181 <ol><li>A mimetype+subtype transform:<br /><br />
2183 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2185 Please not that mimetype and subtype are separated via '_', which shall
2186 not be contained in their names. The transform function/filename may
2187 contain only characters which cause no problems in the file system as
2188 well as the PHP function naming convention.<br /><br />
2190 The transform function will the be called
2191 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2193 <b>Example:</b><br /><br />
2195 <tt>text_html__formatted.inc.php</tt><br />
2196 <tt>PMA_transform_text_html__formatted()</tt></li>
2198 <li>A mimetype (w/o subtype) transform:<br /><br />
2200 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2202 Please note that there are no single '_' characters.
2203 The transform function/filename may contain only characters which cause
2204 no problems in the file system as well as the PHP function naming
2205 convention.<br /><br />
2207 The transform function will the be called
2208 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2210 <b>Example:</b><br /><br />
2212 <tt>text__formatted.inc.php</tt><br />
2213 <tt>PMA_transform_text__formatted()</tt></li>
2215 <li>A mimetype+subtype without specific transform function<br /><br />
2217 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2219 Please note that there are no '__' characters in the filename. Do not
2220 use special characters in the filename causing problems with the file
2221 system.<br /><br />
2223 No transformation function is defined in the file itself.<br /><br />
2225 <b>Example:</b><br /><br />
2227 <tt>text_plain.inc.php</tt><br />
2228 (No function)</li>
2230 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2232 <tt>[mimetype].inc.php</tt><br /><br />
2234 Please note that there are no '_' characters in the filename. Do not use
2235 special characters in the filename causing problems with the file system.
2236 <br /><br />
2238 No transformation function is defined in the file itself.<br /><br />
2240 <b>Example:</b><br /><br />
2242 <tt>text.inc.php</tt><br />
2243 (No function)</li>
2245 <li>A global transform function with no specific mimetype<br /><br />
2247 <tt>global__[transform].inc.php</tt><br /><br />
2249 The transform function will the be called
2250 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2252 <b>Example:</b><br /><br />
2254 <tt>global__formatted</tt><br />
2255 <tt>PMA_transform_global__formatted()</tt></li>
2256 </ol>
2258 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2259 transform function.</p>
2261 <p> All filenames containing no '__' in themselves are not shown as valid transform
2262 functions in the dropdown.</p>
2264 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2265 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2266 without a transform function. Also note the introduction of a function description in
2267 the language files. For each function a $strTransformation_[filename without .inc.php]
2268 has to exist.</p>
2270 <p> You can use the template generator to generate new functions and entries in the
2271 language file.</p>
2273 <p> To create a new transform function please see
2274 <tt>libraries/transformations/template_generator.sh</tt>.
2275 To create a new, empty mimetype please see
2276 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2278 <p> A transform function always gets passed three variables:</p>
2280 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2281 you want to transform.</li>
2282 <li><b>$options</b> - Contains any user-passed options to a transform function
2283 as an array.</li>
2284 <li><b>$meta</b> - Contains an object with field information to your column.
2285 The data is drawn from the output of the
2287 function. This means, all object properties described on the
2289 available in this variable and can be used to transform a field accordingly
2290 to unsigned/zerofill/not_null/... properties.<br />
2291 The $meta->mimetype variable contains the original MIME-type of the
2292 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2293 </ol>
2295 <!-- FAQ -->
2302 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2306 </ol>
2308 <p> Please have a look at our
2310 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2311 features and or interface.</p>
2317 action is required or phpMyAdmin sends a blank page or a page full of
2318 cryptic characters to my browser, what can I do?</a></h4>
2320 <p> There are some known PHP bugs with output buffering and compression.<br />
2322 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2323 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2324 configuration file.<br />
2325 Furthermore, we know about such problems connected to the release
2326 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2327 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2332 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2333 See also the
2335 entry about PHP bugs with output buffering.<br />
2336 If your server keeps crashing, please ask for help in the various Apache
2337 support groups.</p>
2341 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2342 script: I'm always displayed the login screen.</a></h4>
2344 <p> This is a known PHP bug (see this
2346 official PHP bug database. It means there is and won't be any phpMyAdmin
2347 fix against it because there is no way to code a fix.</p>
2353 application misbehaved by not returning a complete set of
2355 </h4>
2357 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2358 Have a look at the last message in this
2360 official PHP bug database.</p>
2365 and/or many error messages with the
2367 mode.</a></h4>
2369 <p> This is a known problem with the PHP
2371 filter: it's not so stable. Please use instead the cookie authentication mode.
2372 </p>
2377 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2378 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2379 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2380 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2381 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2386 work.</a></h4>
2388 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2389 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2390 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2391 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2392 We faced PHP crashes when trying to download a dump with MS Internet
2393 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2394 this case you should switch to the release version of PHP 4.2.0.</p>
2398 an error about safe mode being in effect.</a></h4>
2400 <p> Your uploaded file is saved by PHP in the "upload dir", as
2401 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2402 the system default is <i>/tmp</i>).<br />
2403 We recommend the following setup for Apache servers running in safe mode,
2404 to enable uploads of files while being reasonably secure:</p>
2406 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2407 <li>give ownership to the Apache server's user.group:
2408 <tt>chown apache.apache /tmp/php</tt></li>
2409 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2410 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2411 <li>restart Apache</li>
2412 </ul>
2416 general file uploads don't work on my system and uploaded files have a
2417 <tt>Content-Type:</tt> header in the first line.</a></h4>
2419 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2420 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2421 So the problem is that this package has a serious bug that was corrected
2422 ages ago in PHP (2001-01-28: see
2424 for more details). The problem is that the bugged package is still
2425 available though it was corrected (see
2427 for more details).<br />
2428 So please download
2429 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2430 and the problem should go away.<br />
2431 And that fixes the \r\n problem with file uploads!</p>
2435 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2436 I'm using the Apache server.</a></h4>
2438 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2439 your <i>httpd.conf</i>:</p>
2443 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2447 uploading a file from the query box.</a></h4>
2449 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2450 restrictions. Assuming that the restriction allows you to open files in the
2451 current directory ('.'), all you have to do is create a 'tmp' directory
2452 under the phpMyAdmin install directory, with permissions 777 and the same
2453 owner as the owner of your phpMyAdmin directory. The uploaded files will
2454 be moved there, and after execution of your
2460 <p> The MySQL manual explains how to
2462 reset the permissions</a>.</p>
2467 execute a bookmark.</a></h4>
2469 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2470 cannot access the uploaded query.</p>
2475 submit a query from the convenient text area.</a></h4>
2477 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2478 and try to increase it.</p>
2482 </h4>
2484 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2485 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2486 names to align with current standards.</p>
2491 </h4>
2493 <p> Starting with version 2.7.0, the import engine has been re–written and these
2494 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2495 to take advantage of the new import features.</p>
2497 <p> The first things to check (or ask your host provider to check) are the
2498 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2499 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2500 All of these three settings limit the maximum size of data that can be
2501 submitted and handled by PHP. One user also said that post_max_size
2502 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2504 There exist several workarounds if your upload is too big or your
2505 hosting provider is unwilling to change the settings:</p>
2508 feature. This allows one to
2509 upload a file to the server via scp, ftp, or your favorite file transfer
2510 method. PhpMyAdmin is then able to import the files from the temporary
2512 section</a> of this document.</li>
2514 BigDump</a>) to split the files before uploading. We cannot support this
2515 or any third party applications, but are aware of users having success
2516 with it.</li>
2517 <li>If you have shell (command line) access, use MySQL to import the files
2518 directly. You can do this by issuing the "source" command from
2519 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2520 </ul>
2524 support?</a></h4>
2526 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2527 fully supported. Please note that the older your MySQL version is, the more
2528 limitations you will have to face.<br />
2529 phpMyAdmin may connect to your MySQL server using php's classic
2532 is available in php 5.0.<br />
2533 Either way, the developers of both extensions recommend to use the classic
2534 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2535 When compiling php, we strongly recommend that you manually link the MySQL
2536 extension of your choice to a MySQL client library of at least the same
2537 minor version since the one that is bundled with some php distributions is
2540 If your webserver is running on a windows system, you might want to try
2541 MySQL's
2543 instead of the MySQL / MySQLi extensions that are bundled with the official
2544 php Win32 builds.
2545 <br />
2546 MySQL 5.1 is not yet supported.</p>
2550 message, "Client does not support authentication protocol requested
2551 by server; consider upgrading MySQL client"</a></h5>
2553 <p> You tried to access MySQL with an old MySQL client library. The version of
2554 your MySQL client library can be checked in your phpinfo() output.
2555 In general, it should have at least the same minor version as your server
2559 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2560 changed the authentication hash and your PHP is trying to use the old method.
2562 with the proper client library to match your MySQL installation. Your
2563 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2564 More information (and several workarounds) are located in the
2566 </p>
2570 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2571 capital letter in its name it is changed to lowercase as it should. But
2572 if I try to DROP this table MySQL is unable to find the corresponding
2573 file.</a></h4>
2575 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2576 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2577 directive.</p>
2581 script seems not to know the font face I'm using!</a></h4>
2583 <p> The "FPDF" library we're using for this feature requires some
2584 special files to use font faces.<br />
2586 these files.</p>
2590 check PHP Configuration".</a></h4>
2592 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2593 "MySQL extension". This extension may be part of the PHP
2594 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2595 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2596 to load the extension but failed.<br /><br />
2598 Usually, the problem is solved by installing a software package called
2599 "PHP-MySQL" or something similar.</p>
2604 and I cannot log in using cookie auth.</a></h4>
2606 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2610 so I cannot upload.</a></h4>
2612 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2613 parameter is not set to "on".</p>
2617 a new table the table and field names are changed to lowercase!</a></h4>
2619 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2620 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2621 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2622 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2623 directory and add the following line to the group [mysqld]:</p>
2625 <pre>set-variable = lower_case_table_names=0</pre>
2627 <p> Next, save the file and restart the MySQL service. You can always check the
2628 value of this directive using the query</p>
2630 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2634 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2637 </p>
2641 and I get problems, such as undefined variables when I run a
2644 <p> A tip from Jose Fandos: put a comment on the following two lines
2645 in httpd.conf, like this:</p>
2647 <pre>
2648 # mod_gzip_item_include file \.php$
2650 </pre>
2652 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2653 PHP scripts. Of course you have to restart Apache.</p>
2658 I get the error "No input file specified" when trying to
2659 run phpMyAdmin.</a></h4>
2661 <p> This is a permission problem. Right-click on the phpmyadmin folder
2662 and choose properties. Under the tab Security, click on "Add"
2663 and select the user "IUSR_machine" from the list. Now set his
2664 permissions and it should work.</p>
2668 db_structure.php with plenty of tables).</a></h4>
2671 GZIP output buffering is enabled. If you turn off it (by
2673 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2674 PHP 5.0.0.</p>
2678 message 'Errorcode: 13'. What does this mean?</a></h4>
2680 <p> This can happen due to a MySQL bug when having database / table names with
2681 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2682 To fix this, turn off this directive, convert all database and table names
2683 to lower case and turn it on again. Alternatively, there's a bug-fix
2684 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2688 and the fields are duplicated.</a></h4>
2690 <p> It is possible to configure Apache in such a way that PHP has problems
2691 interpreting .php files.</p>
2693 <p> The problems occur when two different (and conflicting) set of directives
2694 are used:</p>
2696 <pre>
2697 SetOutputFilter PHP
2698 SetInputFilter PHP
2699 </pre>
2701 <p> and</p>
2703 <pre>AddType application/x-httpd-php .php</pre>
2705 <p> In the case we saw, one set of directives was in
2706 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2707 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2708 The recommended way is with <tt>AddType</tt>, so just comment out
2709 the first set of lines and restart Apache:</p>
2711 <pre>
2712 #SetOutputFilter PHP
2713 #SetInputFilter PHP
2714 </pre>
2719 <p> This problem is known to happen when the server is running Turck MMCache
2720 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2725 <p> Yes.<br />
2726 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2727 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2728 <tt>error_reporting</tt> settings.
2729 </p>
2732 <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>
2734 <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>
2737 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2738 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2739 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2740 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2741 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2742 enabled.) Click <tt>OK</tt>.</li>
2743 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2744 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2745 </ol>
2749 PHP 5.0.4 on 64-bit systems?</a></h4>
2751 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2752 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2758 http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script. For <tt>server</tt> you use the server number which refers to
2759 the order of the server paragraph in <tt>config.inc.php</tt>.
2760 Table and script parts are optional. If you want
2761 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2762 some configuration. Following lines apply only for <a
2764 that you have enabled some features within global configuration. You need
2765 <code>Options FollowSymLinks</code> and <code>AllowOverride
2766 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2767 you need mod_rewrite to be enabled. Then you just need to create following
2768 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2769 (don't forget to change directory name inside of it):</p>
2771 <pre>
2772 RewriteEngine On
2773 RewriteBase /path_to_phpMyAdmin
2774 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2775 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2776 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2777 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2778 </pre>
2781 <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>
2783 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2784 following rewrite rule:</p>
2786 <pre>
2787 RewriteEngine On
2788 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2789 </pre>
2793 </h4>
2794 <p>
2795 There can be many explanations to this and a look at your server's
2796 error log file might give a clue.
2797 </p>
2801 password encryption in cookie auth doesn't work.</a></h4>
2803 <p> If your cluster consist of different architectures, PHP code used for
2804 encryption/decryption won't work correct. This is caused by use of
2805 pack/unpack functions in code. Only solution is to use mcrypt extension
2806 which works fine in this case.</p>
2811 <p> Yes but the default configuration values of Suhosin are known to cause
2812 problems with some operations, for example editing a table with many
2813 columns and no primary key. Tuning information is available at
2815 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2816 although the parameter names have changed (<tt>suhosin</tt> instead
2818 <tt>SuhosinDisableWarning</tt> directive</a>.
2819 </p>
2825 headers already sent by ..." is displayed, what's the problem?</a></h4>
2827 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2828 (I.E. no blank lines, no spaces, no characters...) neither before the
2829 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2830 tag at the end. We also got a report from a user under IIS, that used
2831 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2832 contained an end-of-line character (hex 0A) at the end; removing this character
2833 cleared his errors.</p>
2838 <p> Either there is an error with your PHP setup or your username/password is
2839 wrong. Try to make a small script which uses mysql_connect and see if it
2840 works. If it doesn't, it may be you haven't even compiled MySQL support
2841 into PHP.</p>
2845 connect to local MySQL server through socket '/tmp/mysql.sock'
2846 (111) ..." is displayed. What can I do?</a></h4>
2848 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2850 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2851 In your <i>php.ini</i> you will find a line</p>
2853 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2855 <p> change it to</p>
2857 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2859 <p> Then restart apache and it will work.</p>
2861 <p> Here is a fix suggested by Brad Ummer:</p>
2863 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2864 To do this, telnet to your server and go to the MySQL bin directory. In
2865 this directory there should be a file named <i>mysqladmin</i>. Type
2866 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2867 info about your MySQL server, including the socket
2868 (<i>/tmp/mysql.sock</i>, for example).</li>
2869 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2870 phpMyAdmin, you need to complete the socket information in the
2871 <i>config.inc.php</i>.<br />
2872 For example:
2874 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2875 <br /><br />
2877 Please also make sure that the permissions of this file allow to be readable
2878 by your webserver (i.e. '0755').</li>
2879 </ul>
2881 <p> Have also a look at the
2883 corresponding section of the MySQL documentation</a>.</p>
2887 what can I do?</a></h4>
2890 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2891 sometime.<br />
2892 Also have a look at your PHP version number: if it contains "4.0b..."
2893 it means you're running a beta version of PHP. That's not a so good idea,
2894 please upgrade to a plain revision.</p>
2898 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2899 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2901 <p> Check the value you set for the
2903 directive in the phpMyAdmin configuration file.</p>
2907 password: YES)"-error when trying to access a MySQL-Server on a
2908 host which is port-forwarded for my localhost.</a></h4>
2910 <p> When you are using a port on your localhost, which you redirect via
2911 port-forwarding to another host, MySQL is not resolving the localhost
2912 as expected.<br />
2913 Erik Wasser explains: The solution is: if your host is "localhost"
2914 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2915 connection for speeding up things. And that doesn't work in this configuration
2916 with port forwarding.<br />
2922 <p> Themes are configured with
2926 <br />
2928 should not delete the directory "original" or its underlying
2929 structure, because this is the system theme used by phpMyAdmin.
2930 "original" contains all images and styles, for backwards
2931 compatibility and for all themes that would not include images or css-files.
2932 <br /><br />
2935 is enabled, you can select your favorite theme on the main page. Your
2936 selected theme will be stored in a cookie.<br /><br /></p>
2938 <p> To create a theme:</p>
2940 <ul><li>make a new subdirectory (for example "your_theme_name") under
2942 (by default <tt>themes</tt>)</li>
2943 <li>copy the files and directories from "original" to
2944 "your_theme_name"</li>
2945 <li>edit the css-files in "your_theme_name/css"</li>
2946 <li>put your new images in "your_theme_name/img"</li>
2947 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2948 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2949 contain your chosen theme name, that will be visible in user interface</li>
2950 <li>make a new screenshot of your theme and save it under
2951 "your_theme_name/screen.png"</li>
2952 </ul>
2954 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2955 theme verbose name, theme generation and theme version. These versions and
2956 generations are enumerated from 1 and do not have any direct dependence on
2957 phpMyAdmin version. Themes within same generation should be backwards
2958 compatible - theme with version 2 should work in phpMyAdmin requiring
2959 version 1. Themes with different generation are incompatible.</p>
2961 <p> If you do not want to use your own symbols and buttons, remove the
2962 directory "img" in "your_theme_name". phpMyAdmin will
2963 use the default icons and buttons (from the system-theme "original").
2964 </p>
2968 what can I do?</a></h4>
2970 <p> Here are a few points to check:</p>
2972 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2974 directive empty. See also
2976 </li>
2977 <li>Maybe you have a broken PHP installation or you need to upgrade
2978 your Zend Optimizer. See
2980 http://bugs.php.net/bug.php?id=31134</a>.
2981 </li>
2982 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2983 set to the default (200) or another low value, you could get this
2984 error if your table has a high number of columns. Adjust this setting
2985 accordingly. (Thanks to Klaus Dorninger for the hint).
2986 </li>
2987 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2988 of ";" will cause this error. Replace it with "&;".
2989 </li>
2991 you might want to increase
2993 </li>
2994 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
2995 </li>
2996 </ul>
3003 who logged out can not log in again in with the same nick.</a></h4>
3005 <p> This is related to the authentication mechanism (protocol) used by
3006 phpMyAdmin. To bypass this problem: just close all the opened
3007 browser windows and then go back to phpMyAdmin. You should be able to
3008 log in again.</p>
3012 limit error or a time limit error.</a></h4>
3014 <p> Compressed dumps are built in memory and because of this are limited to
3015 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3016 using
3018 (enabled by default). Zip exports can not be handled this way, so if you need
3019 Zip files for larger dump, you have to use another way.</p>
3023 or alter a table.</a></h4>
3025 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3029 bundled with the MySQL server distribution.</a></h4>
3031 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3033 <pre>
3034 -- MySQL dump 8.22
3035 --
3036 -- Host: localhost Database: database
3037 ---------------------------------------------------------
3038 -- Server version 3.23.54
3039 </pre>
3041 <p> The invalid part of the code is the horizontal line made of dashes that
3042 appears once in every dump created with mysqldump. If you want to run your
3043 dump you have to turn it into valid MySQL. This means, you have to add a
3044 whitespace after the first two dashes of the line or add a # before it:
3045 <br />
3046 <code>
3047 -- -------------------------------------------------------<br />
3048 </code>
3049 or<br />
3050 <code>
3051 #---------------------------------------------------------
3052 </code>
3053 </p>
3060 <p> Please note that you should not use the separating string multiple times
3061 without any characters between them, or at the beginning/end of your table
3062 name. If you have to, think about using another TableSeparator or disabling
3063 that feature</p>
3068 <p> In Relation view, being able to choose a table in another database,
3069 or having more than one index field in the foreign key.<br /><br/>
3070 In Query-by-example (Query), automatic generation of the query
3071 LEFT JOIN from the foreign table.<br /><br/>
3072 </p>
3076 I get series of errors like "Warning: unable to parse url". How
3077 can this be fixed?</a></h4>
3078 <p>
3079 Your table neither have a primary key nor an unique one, so we must use a
3080 long expression to identify this row. This causes problems to parse_url
3081 function. The workaround is to create a primary or unique key.
3082 <br />
3083 </p>
3087 a MIME-Transformation onto!</a></h4>
3089 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3090 nested forms can be put inside the table where phpMyAdmin displays the results.
3091 You can, however, use any form inside of a table if keep the parent
3092 form-container with the target to tbl_row_delete.php and just put your own
3093 input-elements inside. If you use a custom submit input field, the form will
3094 submit itself to the displaying page again, where you can validate the
3095 $HTTP_POST_VARS in a transformation.
3097 For a tutorial on how to effectively use transformations, see our
3099 on the official phpMyAdmin-homepage.</p>
3103 MySQL server</a></h4>
3105 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3108 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3109 the quote-character (") is interpreted as an identifier quote character and
3110 not as a string quote character, which makes many internal phpMyAdmin
3112 statements. There is no workaround to this behaviour. News to this item will
3113 be posted in Bug report
3114 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3115 </p>
3119 more that one column with the same value
3120 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3121 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3123 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3124 can use it for the Edit and Delete links.</p>
3129 <p> phpMyAdmin uses a quick method to get the row count, and this method
3130 only returns an approximate count in the case of InnoDB tables. See
3132 a way to modify those results, but
3133 this could have a serious impact on performance.</p>
3138 <p> The number of records in queries containing COUNT and GROUP BY is
3139 not correctly calculated. Also, sorting results of a query like
3144 containing an hyphen.
3145 </a></h4>
3146 <p>
3147 The tests I have made with current MySQL 4.1.11 API shows that the
3148 API does not accept this syntax for the USE command. Enclosing the
3149 db name with backquotes works. For further confusion, no backquotes
3150 are needed with command-line mysql.
3151 </p>
3154 <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>
3155 <p>
3156 This has been a known limitation of phpMyAdmin since the beginning and
3157 it's not likely to be solved in the future.
3158 </p>
3160 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3163 <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
3164 need to install it for each customer.
3165 </a></h4>
3166 <p>
3167 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3168 your users. The development of this feature was kindly sponsored by
3169 NetCologne GmbH.
3170 This requires a properly setup MySQL user management and phpMyAdmin
3171 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3173 </p>
3177 access.
3178 </a></h4>
3179 <p>
3180 This depends on your system.<br />
3181 If you're running a server which cannot be accessed by other people, it's
3182 sufficient to use the directory protection bundled with your webserver
3184 If other people have telnet access to your server, you should use
3185 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3186 <br /><br />
3187 Suggestions:
3188 </p>
3189 <ul>
3190 <li>
3192 </li>
3193 <li>
3194 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3195 is a user whose password is only known to you, and apache is the
3196 group under which Apache runs.
3197 </li>
3198 <li>
3199 You should use PHP safe mode, to protect from other users that try
3201 </li>
3202 </ul>
3207 </a></h4>
3208 <p>
3213 </p>
3216 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3217 authentication.
3218 </a></h4>
3222 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3223 and/or
3225 are wrong.</li>
3227 <li>You have already setup a security mechanism for the
3228 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3229 phpMyAdmin's authentication, so remove it.</li>
3230 </ul>
3237 and put the privileges you want. For example,
3239 would let a user create/manage his/her database(s).</p>
3244 <p> If you have existing rules from an old .htaccess file, you can take them
3247 be a major benefit here if your installation is suited to using it. Then
3248 you can just add those updated lines into the
3252 <p> If you want a pre-made sample, you can try this fragment. It stops the
3253 'root' user from logging in from any networks other than the private
3256 <pre>
3257 //block root from logging in except from the private networks
3258 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3259 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3260 'deny root from all',
3261 'allow root from localhost',
3265 );
3266 </pre>
3271 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3272 different than the one set in your
3274 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3275 while a domain name is defined in the config file.</p>
3280 <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>
3286 when trying to create a table with more than 14 fields.
3287 </a></h4>
3288 <p>
3289 We could reproduce this problem only under Win98/98SE. Testing under
3290 WinNT4 or Win2K, we could easily create more than 60 fields.
3291 <br />
3292 A workaround is to create a smaller number of fields, then come back to
3293 your table properties and add the other fields.
3294 </p>
3298 <p>
3299 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3300 with each script/website that use forms.<br />
3301 Upgrade or downgrade your Xitami server.
3302 </p>
3305 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3306 <p>
3307 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3308 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3309 don't seem to work.<br />
3311 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3312 the user's temporary directory, so they must be moved before closing
3313 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3316 </p>
3320 Explorer never stores the cookies.
3321 </a></h4>
3322 <p>
3323 MS Internet Explorer seems to be really buggy about cookies, at least till
3325 in this area!
3326 <br />
3327 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3328 work!
3329 </p>
3333 rows.
3334 </a></h4>
3335 <p>
3337 </p>
3340 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3341 when trying to modify a row in a table with many fields, or with a text field
3342 </a></h4>
3343 <p>
3344 Your table neither have a primary key nor an unique one, so we must use a
3345 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
3346 those browsers, and this not happen in Netscape, for example. The
3347 workaround is to create a primary or unique key, or use another browser.
3348 <br />
3349 </p>
3353 page.
3354 </a></h4>
3355 <p>
3356 Some browsers support right-clicking into the frame you want to refresh,
3357 just do this in the right frame.<br />
3358 </p>
3362 query box.
3363 </a></h4>
3364 <p>
3365 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3366 Mozilla versions.<br />
3367 </p>
3371 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3372 </a></h4>
3373 <p>
3374 This is a Mozilla bug (see bug #26882 at
3376 </p>
3381 </a></h4>
3382 <p>
3383 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3384 data in octet-stream mode. Since we can't detect the specific Netscape
3385 version, we cannot workaround this bug.
3386 </p>
3390 wrong.</a></h4>
3392 <p> Please ensure that you have set your browser's character set to the one of the
3393 language file you have selected on phpMyAdmin's start page.
3394 Alternatively, you can try the auto detection mode that is supported by the
3395 recent versions of the most browsers.</p>
3398 <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
3401 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3402 Netscape and Mozilla do not have this problem.</p>
3405 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3406 I cannot manage two servers: I log in to the first one, then the other one,
3407 but if I switch back to the first, I have to log in on each operation.</a></h4>
3413 but nothing happens after that, only a blank screen.</a></h4>
3416 bug in Opera6, because it is not able to interpret frameset definitions
3417 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3418 Opera7 at least.</p>
3427 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3432 address and you are starting
3434 containing a domain name, or the reverse situation.</li>
3435 <li>Security settings in IE and/or Microsoft Security Center are
3436 too high, thus blocking scripts execution.</li>
3437 <li>The Windows Firewall is blocking Apache and MySQL. You must
3441 </ul>
3444 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3445 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3446 installed in their Firefox is causing the problem.</p>
3453 </a></h4>
3454 <p>
3455 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3456 specifying a wrong field-type.<br />
3457 Common errors include:
3458 </p>
3459 <ul>
3462 </ul>
3463 <p>
3464 Also, look at the syntax chapter in the MySQL manual to confirm that your
3465 syntax is correct.
3466 </p>
3470 phpMyAdmin generates only one index with those 2 fields.
3471 </a></h4>
3472 <p>
3474 index. If you want two indexes, create the first one when creating the
3475 table, save, then display the table properties and click the Index link to
3476 create the other index.
3477 </p>
3481 <p>
3482 Since version 2.2.3, you have a checkbox for each field that can be null.
3484 field's value. Since version 2.5.5, you have to use the checkbox to get
3486 a literal NULL in the field, and not a NULL value (this works in PHP4).
3487 </p>
3492 <p> Click on a database or table name in the left frame, the properties will be
3494 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3495 statements that can be used to recreate your database/table.
3496 <br /><br />
3498 transmit the resulting dump to your station. Depending on your PHP
3499 configuration, you will see options to compress the dump. See also the
3501 configuration variable.<br /><br />
3504 this document.</p>
3509 </a></h4>
3511 <p> Click on a database name in the left frame, the properties will be
3513 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3515 the path to your dump filename, or use the Browse button. Then click Go.
3516 <br /><br />
3518 that you upgrade to take advantage of the new features.
3519 <br /><br />
3521 in this document.
3522 </p>
3527 <p> Here is an example with the tables persons, towns and countries, all
3529 table, create it as explained in the configuration section. Then create the
3530 example tables:</p>
3532 <pre>
3533 CREATE TABLE REL_countries (
3534 country_code char(1) NOT NULL default '',
3535 description varchar(10) NOT NULL default '',
3536 PRIMARY KEY (country_code)
3537 ) TYPE=MyISAM;
3539 INSERT INTO REL_countries VALUES ('C', 'Canada');
3541 CREATE TABLE REL_persons (
3542 id tinyint(4) NOT NULL auto_increment,
3543 person_name varchar(32) NOT NULL default '',
3545 country_code char(1) NOT NULL default '',
3546 PRIMARY KEY (id)
3547 ) TYPE=MyISAM;
3549 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3550 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3552 CREATE TABLE REL_towns (
3554 description varchar(30) NOT NULL default '',
3555 PRIMARY KEY (town_code)
3556 ) TYPE=MyISAM;
3558 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3559 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3560 </pre>
3566 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3570 </ul>
3578 <li>In the fields row, choose persons.person_name and click the
3580 <li>Do the same for towns.description and countries.descriptions in the
3583 the correct joins have been generated</li>
3585 </ul>
3589 <p>
3590 Starting from the previous example, create the pma_table_info as explained
3591 in the configuration section, then browse your persons table,
3592 and move the mouse over a town code or country code.
3593 <br /><br />
3594 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3595 enables: drop-down list of possible values.
3596 </p>
3599 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3600 <p>
3603 <br /><br />
3604 Then you need to think about your schema layout. Which tables will go on
3605 which pages?
3606 </p>
3607 <ul>
3613 page and click Go. If you like, you
3615 linked tables onto the new page.</li>
3616 <li>Select the name of the new page (making sure the Edit radio button
3617 is selected) and click Go.</li>
3619 Coordinates are relative; your diagram will
3620 be automatically scaled to fit the page. When initially placing tables
3621 on the page, just pick any coordinates -- say, 50x50. After clicking
3623 position the element correctly.</li>
3625 first be sure to click the Save
3626 button beneath the list of tables and coordinates, to save any changes
3627 you made there. Then scroll all the way down, select the
3629 you want, and click Go.</li>
3630 <li>Internet Explorer for Windows may suggest an incorrect filename when
3635 browsers on Windows, do not have this problem.</li>
3636 </ul>
3640 columns!</a></h4>
3642 <p> No, it's MySQL that is doing
3648 underscores in the database name?</a></h4>
3650 <p> If you do not put a backslash before the underscore, this is a wildcard
3653 john2db ...<br /><br />
3655 If you put a backslash before the underscore, it means that the database
3656 name will have a real underscore.</p>
3660 statistics pages?</a></h4>
3671 if it already exists during the import. It does NOT drop the table after
3672 your export, it only affects the import file.</li>
3674 Otherwise, you may get an error if the table name exists but has a
3675 different structure.</li>
3677 (if any) will be included in backup.</li>
3679 field and table names formed with special characters are protected.</li>
3681 types set in the pmadb in the dump as
3683 </li>
3684 </ul>
3689 command, for better documentation (but resulting file is bigger).</li>
3691 once the INSERT verb and the table name.</li>
3694 </li>
3696 more info is provided in the
3698 but basically with this selected, invalid values are adjusted and
3699 inserted rather than causing the entire statement to fail.</li>
3700 </ul>
3704 in its name.</a></h4>
3707 is the normal way to reference a database and table name. Worse, MySQL
3708 will usually let you create a database with a dot, but then you cannot
3709 work with it, nor delete it.</p>
3722 for usage.<br />
3723 On a more recent pear version, I had problems with the state of Net_DIME
3724 being beta, so this single command
3726 needed modules.<br />
3727 If you use the Validator, you should be aware that any
3729 submit will be stored anonymously (database/table/column names,
3730 strings, numbers replaced with generic values). The Mimer
3733 We utilize it as free SOAP service.</p>
3737 it, but MySQL says "BLOB column '...' used in key specification without
3740 <p> The right way to do this, is to create the field without any indexes,
3742 dialog. On this page, you will be able to choose your BLOB field, and
3743 set a size to the index, which is the condition to create an index on
3744 a BLOB field.</p>
3748 editing fields?</a></h4>
3750 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3751 with many editing fields (table structure changes, row editing, etc.)
3752 (must be enabled in configuration - see.
3754 You can also have a look at the directive
3756 ('vertical') and see if this eases up editing for you.</p>
3760 WTF is this feature then useful for?</a></h4>
3762 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3763 on them. Otherwise you could just put a comment on the field. Because entering
3764 your own mimetype will cause serious syntax checking issues and validation,
3765 this introduces a high-risk false-user-input situation. Instead you have to
3766 initialize mimetypes using functions or empty mimetype definitions.<br />
3767 Plus, you have a whole overview of available mimetypes. Who knows all those
3768 mimetypes by heart so he/she can enter it at will?</p>
3772 can't I see any bookmarks below the query box? What is this variable for?
3773 </a></h4>
3775 <p> Any query you have executed can be stored as a bookmark on the page where the
3776 results are displayed. You will find a button labeled 'Bookmark this query'
3777 just at the end of the page.<br />
3778 As soon as you have stored a bookmark, it is related to the database you run
3779 the query on. You can now access a bookmark dropdown on each page, the query
3780 box appears on for that database.<br /><br />
3782 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3786 aware of that you HAVE to create a valid query, otherwise your query won't be
3787 even able to be stored in the database.<br />
3789 for your query will remain the way it is, but will be stripped of the /**/
3790 chars. So you can use:<br /><br />
3794 which will be expanded to<br /><br />
3798 in your query, where VARIABLE is the string you entered in the input box. If
3799 an empty string is provided, no replacements are made.<br /><br />
3801 A more complex example. Say you have stored this query:<br /><br />
3803 <br /><br />
3806 the full query will be:<br /><br />
3809 <br /><br />
3813 spaces inserted there
3814 will be later also inserted as spaces in your query and may lead to unexpected
3815 results especially when
3817 Your initial query which is going to be stored as a bookmark has to yield at
3818 least one result row so
3819 you can store the bookmark. You may have that to work around using well
3823 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3824 include exported table?</a></h4>
3826 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3827 document should look like following one (assuming you have table
3830 <pre>
3831 \documentclass{article} % or any class you want
3832 \usepackage{longtable} % for displaying table
3833 \begin{document} % start of document
3834 \include{table} % including exported table
3835 \end{document} % end of document
3836 </pre>
3840 access them.
3841 </a></h4>
3844 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3845 enable users to see all the database names.
3848 So if your users do not need those privileges, you can remove them and their
3849 databases list will shorten.</p>
3853 possible values for a field, based on some foreign table?</a></h4>
3855 <p> You have to setup appropriate links between the tables, and also
3859 foreign table, a drop-down list of values will be available.
3860 You will see two lists of values, the first list containing the key
3861 and the display field, the second list containing the display field
3862 and the key. The reason for this is to be able to type the first
3863 letter of either the key or the display field.<br /><br />
3865 For 200 values or more, a distinct window will appear, to browse foreign
3866 key values and choose one.</p>
3870 automatically when entering Browse mode for a table?</a></h4>
3872 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3873 </p>
3877 Excel files, how can I enable that?</a></h4>
3879 <p> Current version does support direct export to Microsoft Excel and Word
3880 versions 2000 and newer. If you need export older versions, you can use
3882 which works out of the box or you can
3884 several problems, most important are limitation of cell content to 255
3885 chars and no support for charsets, so think carefully whether you want to
3886 enable this.</b>. For enabling this you need to set
3890 module Spreadsheet_Excel_Writer into php include path. The
3891 installation can be done by following command:</p>
3893 <pre>
3894 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3895 </pre>
3897 <p> First part of switches set we want to install beta version of that module
3898 (no stable version available yet) and then we tell pear we want to satisfy
3899 dependencies.</p>
3901 <p> If you are running in PHP safe mode, you will have to set
3904 modules are located, for example:</p>
3906 <pre>
3907 safe_mode_include_dir = /usr/local/lib/php
3908 </pre>
3912 <pre>
3913 cd phpMyAdmin
3914 mkdir tmp
3915 chmod o+rwx tmp
3916 </pre>
3920 what happens to my column comments stored in pmadb?</a></h4>
3922 <p> Automatic migration of a table's pmadb-style column comments to the native
3923 ones is done whenever you enter Structure page for this table.</p>
3930 <p> Our Bug Tracker is located at
3932 under the Bugs section.<br /><br />
3934 But please first discuss your bug with other users:<br />
3940 existing language, where do I start?</a></h4>
3942 <p> Always use the current SVN version of your language file.
3944 don't know how to get the SVN version, please ask one of the developers.
3945 <br />
3946 Please note that we try not to use HTML entities like &eacute; in
3947 the translations, since we define the right character set in the file.
3948 With HTML entities, the text on JavaScript messages would not
3949 display correctly.
3950 However there are some entities that need to be there, for quotes
3951 ,non-breakable spaces, ampersands, less than, greater than.<br />
3952 You can then put your translations, as a zip file to avoid losing special
3953 characters, on the sourceforge.net translation tracker.<br />
3954 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3955 list, because this is where we ask for translations of new messages.</p>
3959 phpMyAdmin. How should I proceed?</a></h4>
3964 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
3965 </li>
3967 <li>generate patch with your changes:
3969 </li>
3972 tracker of the phpMyAdmin project</a>.
3973 </li>
3974 </ol>
3976 <p> Write access to the SVN tree is granted only to experienced developers who
3977 have already contributed something useful to phpMyAdmin.<br />
3983 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3985 <p> Please refer to
3986 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3987 </p>
3989 <!-- DEVELOPERS -->
3992 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3993 great features have been written by other people and you too can help to
3994 make phpMyAdmin a useful tool.</p>
3996 <p> If you're planning to contribute source, please read the following
3997 information:</p>
4003 it free from other code.<br />
4004 Commonly used functions should be added to
4007 <li>Obviously, you're free to use whatever coding style you want. But
4008 please try to keep your code as simple as possible: beginners are
4009 using phpMyAdmin as an example application.<br />
4010 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4011 compliant on one hand, they fit the
4014 coding standards</a>
4015 on the other hand. Please pay attention to this.</li>
4016 <li>Please try to keep up the file-naming conventions. Table-related stuff
4019 <li>Please don't use verbose strings in your code, instead add the string
4024 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4025 better debug and profile their code.<br />
4026 Please see the
4028 options for more information.<br />
4029 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4030 lost during its re-entry into Earth's atmosphere and in memory of the
4031 brave men and women who gave their lives for the people of Earth.</li>
4032 </ul>
4034 <!-- CREDITS -->
4037 <pre>
4038 phpMyAdmin - Credits
4039 ====================
4041 CREDITS, in chronological order
4042 -------------------------------
4045 * creator of the phpmyadmin project
4049 * multi-language version
4050 * various fixes and improvements
4052 * current project maintainer
4055 * started SourceForge phpMyAdmin project in March 2001
4056 * sync'ed different existing CVS trees with new features and bugfixes
4057 * multi-language improvements, dynamic language selection
4058 * current project maintainer
4059 * many bugfixes and improvements
4062 * rewrote and optimized javascript, DHTML and DOM stuff
4063 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4064 generate XHTML1.0 and CSS2 compliant codes
4065 * improved the language detection system
4066 * many bugfixes and improvements
4069 * database maintenance controls
4070 * table type code
4072 * DB-based configuration (Not completed)
4075 * many bugfixes and improvements
4078 * bookmarks feature
4079 * multiple dump feature
4080 * gzip dump feature
4081 * zip dump feature
4084 * various fixes
4085 * moderator of the phpMyAdmin former users forum at phpwizard.net
4091 * rewrote and fix dump code
4092 * bugfixes
4095 * rewrote dump code for PHP4
4096 * mySQL table statistics
4097 * bugfixes
4100 * main author of the version 2.1.0.1
4101 * bugfixes
4105 * abstract database interface (PMA_DBI) with MySQLi support
4106 * privileges administration
4108 * various features and fixes
4109 * German language file updates
4112 * automatic joins in QBE
4113 * links column in printview
4114 * Relation view
4117 * enhanced index creation/display feature
4118 * feature to use a different charset for HTML than for MySQL
4119 * improvements of export feature
4120 * various features and fixes
4121 * Czech language file updates
4124 (http://sf.net/projects/phpmysqlformgen/)
4125 * suggested the patch for multiple table printviews
4128 * built the patch for vertical display of table rows
4129 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4130 * Improvement of column/db comments
4131 * (MIME)-Transformations for columns
4132 * Use custom alias names for Databases in left frame
4133 * hierarchical/nested table display
4134 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4135 * new icon sets
4136 * vertical display of column properties page
4137 * some bugfixes, features, support, German language additions
4140 * japanese kanji encoding conversion feature
4143 * the Cookie authentication mode
4146 * table relation-links feature
4149 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4150 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4151 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4157 * phpMyAdmin logo (until June 2004)
4160 * blowfish library from the Horde project
4163 * mysqli support
4164 * many bugfixes and improvements
4167 * redesign for 2.6.0
4168 * phpMyAdmin sailboat logo (June 2004)
4171 * Representation at conferences
4174 * interface improvements
4175 * various bugfixes
4177 - Ivan A Kirillov
4178 * new relations Designer
4180 And also to the following people who have contributed minor changes,
4181 enhancements, bugfixes or support for a new language since version 2.1.0:
4183 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4184 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4185 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4186 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4188 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4189 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4190 Luís V., Martijn W. van der Lee,
4191 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4195 Original Credits of Version 2.1.0
4196 ---------------------------------
4198 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4199 to create a web-based interface to MySQL using PHP3. Although I have not
4200 used any of his source-code, there are some concepts I've borrowed from
4201 him. phpMyAdmin was created because Peter told me he wasn't going to
4202 further develop his (great) tool.
4203 Thanks go to
4205 code for the check when dropping a table or database. He also suggested
4206 that you should be able to specify the primary key on tbl_create.php3. To
4207 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4208 well as a bug-report. Plus many smaller improvements.
4210 were introduced in 1.3.0 (including quite significant ones like the
4211 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4212 bug-fixes and help.
4214 language-independent by outsourcing the strings to a separate file. He
4215 also contributed the French translation.
4217 tbl_select.php3, a feature to display only some fields from a table.
4219 functions in tbl_change.php3. He also added the
4222 servers and is a regular contributor for bug-fixes.
4224 features for 2.0.6.
4225 The following people have contributed minor changes, enhancements, bugfixes
4226 or support for a new language:
4227 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4228 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4229 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4230 G. Wieggers.
4232 And thanks to everyone else who sent me email with suggestions, bug-reports
4233 and or just some feedback.
4234 </pre>
4240 <ul>
4242 - the default name of Apache's directory-level configuration file.</li>
4246 - a software application that enables a user to display and interact with
4247 text, images, and other information typically located on a web page at a
4248 website on the World Wide Web.</li>
4250 - a free software/open source data compression algorithm and program
4251 developed by Julian Seward.</li>
4253 - an important World Wide Web technology that enables a client web browser
4254 to request data from a program executed on the Web server.</li>
4256 - a log or record of changes made to a project.</li>
4258 - a computer system that accesses a (remote) service on another computer
4259 by some kind of network.</li>
4261 - a set of data values of a particular simple type, one for each row of
4262 the table.</li>
4264 - a packet of information sent by a server to a World Wide Web browser
4265 and then sent back by the browser each time it accesses that server.</li>
4267 - Comma-seperated values</li>
4270 - an organized collection of data.</li>
4273 - a PHP module that extends PHP with additional functionality.</li>
4275 - a list of commonly asked question and there answers.</li>
4277 - one part of divided data/columns.</li>
4279 - a field or group of fields in a database record that point to a key
4280 field or group of fields forming a key of another database record in some
4281 (usually different) table.</li>
4283 - the free PDF library</li>
4285 GD Graphics Library</a> - a library by Thomas Boutell and others for
4286 dynamically manipulating images.</li>
4289 - gzip is short for GNU zip, a GNU free software file compression
4290 program.</li>
4292 - any machine connected to a computer network, a node that has a hostname.</li>
4294 - the unique name by which a network attached device is known on a network.</li>
4296 (HyperText Transfer Protocol)</a>
4297 - the primary method used to transfer or convey information on the World
4298 Wide Web.</li>
4301 additional security measures.</li>
4302 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4303 - a set of Internet-based services for servers using Microsoft Windows.</li>
4305 - a feature that allows quick access to the rows in a table.</li>
4307 - a data-oriented protocol used by source and destination hosts for
4308 communicating data across a packet-switched internetwork.</li>
4310 - a unique number that devices use in order to identify and communicate
4311 with each other on a network utilizing the Internet Protocol standard.</li>
4313 (Internet Server Application Programming Interface)</a>
4314 - the API of Internet Information Services (IIS).</li>
4316 - a business or organization that offers users access to the Internet and related services.</li>
4318 - a most commonly used standard method of lossy compression for
4319 photographic images.</li>
4325 - line of personal computers is designed, developed, manufactured, and
4326 marketed by Apple Computer.</li>
4327 <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>
4328 - the operating system which is included with all currently shipping Apple
4329 Macintosh computers in the consumer and professional markets.</li>
4331 - a cryptographic library.</li>
4333 - the MCrypt PHP extension.</li>
4334 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4335 - an Internet Standard for the format of e-mail.</li>
4337 - some sort of extension for the Apache Webserver.</li>
4339 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4340 Management System (DBMS).</li>
4342 - the improved MySQL client PHP extension.</li>
4344 - the MySQL client PHP extension.</li>
4346 - open standard for office documents.</li>
4347 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4348 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4350 (Portable Document Format)</a>
4351 - a file format developed by Adobe Systems for representing two
4352 dimensional documents in a device independent and resolution independent
4353 format.</li>
4355 - the PHP Extension and Application Repository.</li>
4357 - the perl-compatible regular expression functions for PHP</li>
4359 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4360 programming language used mainly for developing server-side applications
4361 and dynamic web content, and more recently, a broader range of software
4362 applications.</li>
4364 - a connection through which data is sent and received.</li>
4366 - Request for Comments (RFC) documents are a series of memoranda
4367 encompassing new research, innovations, and methodologies applicable to
4368 Internet technologies.</li>
4372 - represents a single, implicitly structured data item in a table.</li>
4374 - a computer system that provides services to other computing
4375 systems over a network.</li>
4376 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4377 - handlers for different table types</li>
4379 - a form of inter-process communication.</li>
4381 Sockets Layer)</a>
4382 - a cryptographic protocol which provides secure communication on the Internet.</li>
4384 - Structured Query Language</li>
4386 - a set of data elements (cells) that is organized, defined and stored as
4387 horizontal rows and vertical columns where each item can be uniquely
4388 identified by a label or key or by it?s position in relation to other items.</li>
4391 - a type of archive file format: the Tape ARchive format.</li>
4393 - one of the core protocols of the Internet protocol suite.</li>
4397 - a sequence of characters, conforming to a standardized format, that is
4398 used for referring to resources, such as documents and images on the
4399 Internet, by their location.</li>
4401 - A computer (program) that is responsible for accepting HTTP requests
4402 from clients and serving them Web pages.</li>
4404 - a W3C-recommended general-purpose markup language for creating
4405 special-purpose markup languages, capable of describing many different
4406 kinds of data.</li>
4408 - a popular data compression and archival format.</li>
4410 - an open-source, cross-platform data compression library by Jean-loup
4411 Gailly and Mark Adler.</li>
4412 </ul>
4422 </body>
4423 </html>