| blob | 908630a909f46d8511022f903d34752b28800c0b |
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>
68 </ul>
69 </li>
73 PHP extension on your web server accelerates not only the login
74 phase but every other action that you do in phpMyAdmin.</li>
76 </ul>
78 <!-- INTRODUCTION -->
81 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
82 a single database. To accomplish the latter you'll need a properly set up
83 MySQL user who can read/write only the desired database. It's up to you to
84 look up the appropriate part in the MySQL manual.
85 </p>
90 <li>create, copy, drop, rename and alter databases, tables, fields and
91 indexes</li>
92 <li>maintenance server, databases and tables, with proposals on server
93 configuration</li>
94 <li>execute, edit and bookmark any
96 batch-queries</li>
99 </li>
106 OpenDocument Text and Spreadsheet,
108 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
109 </li>
113 <li>using Query-by-example (QBE), create complex queries automatically
114 connecting required tables</li>
116 your Database layout</li>
118 <li>transform stored data into any format using a set of predefined
119 functions, like displaying BLOB-data as image or download-link
120 </li>
126 </li>
127 </ul>
130 <p> Many people have difficulty
131 understanding the concept of user management with regards to phpMyAdmin. When
132 a user logs in to phpMyAdmin, that username and password are passed directly
133 to MySQL. phpMyAdmin does no account management on its own (other than
134 allowing one to manipulate the MySQL user account information); all users
135 must be valid MySQL users.</p>
144 <!-- INSTALLATION -->
152 </ol>
155 phpMyAdmin does not apply any special security methods to the MySQL database
156 server. It is still the system administrator's job to grant permissions on
158 be used for this.
159 </p>
167 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
168 before uploading them to your server, as PHP seems not to like
173 <ol><li>Untar or unzip the distribution (be sure to unzip the subdirectories):
175 document root. If you don't have direct access to your document root,
176 put the files in a directory on your local machine, and, after step 3,
177 transfer the directory on your web server using, for example, ftp.</li>
178 <li>Ensure that all the scripts have the appropriate owner (if PHP is
179 running in safe mode, having some scripts with an owner different
180 from the owner of other scripts will be a
185 <li>Now you must configure your installation. There are two methods that
186 can be used. Traditionally, users have hand-edited a copy of
187 config.inc.php, but now a wizard-style setup script is provided for
188 those who prefer a graphical installation. Creating a config.inc.php is
189 still a quick way to get started and needed for some advanced features.
190 <ul><li>To manually create the file, simply use your text editor to
193 file) in the main (top-level) phpMyAdmin directory (the one
197 default value is okay for a particular setting, there is no
199 few directives to get going, a simple configuration may look
200 like this:
201 <pre>
202 <?php
203 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
205 $i=0;
206 $i++;
207 $cfg['Servers'][$i]['auth_type'] = 'cookie';
208 ?>
209 </pre>
210 Or, if you prefer to not be prompted every time you log in:
211 <pre>
212 <?php
214 $i=0;
215 $i++;
216 $cfg['Servers'][$i]['user'] = 'root';
217 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
218 ?>
219 </pre>
220 For a full explanation of possible configuration values, see the
226 directory. This is a security measure. On a Linux/Unix system you
227 can use the following commands:
228 <pre>
229 cd phpMyAdmin
230 mkdir config # create directory for saving
231 chmod o+rw config # give it world writable permissions
232 </pre>
233 And to edit an existing configuration, copy it over first:
234 <pre>
235 cp config.inc.php config/ # copy current configuration for editing
236 chmod o+w config/config.inc.php # give it world writable permissions
237 </pre>
238 On other platforms, simply create the folder and ensure that your
247 the webserver does not have the proper permissions you may see the
249 config/</tt> directory exists and has the proper permissions -
251 and upload (via FTP or some similar means) to the proper location.<br /><br />
253 Once the file has been saved, it must be moved out of the <tt>
254 config/</tt> directory and the permissions must be reset, again
255 as a security measure:
256 <pre>
257 mv config/config.inc.php . # move file to current directory
258 chmod o-rw config.inc.php # remove world read and write permissions
259 </pre>
260 Now the file is ready to be used. You can choose to review or edit
261 the file with your favorite editor, if you prefer to set some
262 advanced options which the setup script does not provide.</li></ul></li>
263 <li>If you are using the
265 protect the phpMyAdmin installation directory because using
266 config does not require a user to
267 enter a password to access the phpMyAdmin installation. Use of an alternate
268 authentication method is recommended, for example with
276 in your browser. phpMyAdmin should now display a welcome screen
277 and your databases, or a login dialog if using
279 authentication mode.</li>
281 webserver configuration. For Apache you can use supplied .htaccess file
282 in that folder, for other webservers, you should configure this yourself.
283 Such configuration prevents from possible path exposure and cross side
284 scripting vulnerabilities that might happen to be found in that code.</li>
285 </ol>
289 <p> For a whole set of new features (bookmarks, comments,
292 transformation, etc.) you need to create a set of special tables. Those
293 tables can be located in your own database, or in a central database for a
294 multi-user installation (this database would then be accessed by the
295 controluser, so no other user should have rights to it).</p>
304 installation.</p>
309 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
310 that you may need special (administrator) privileges to create the database
311 and tables, and that the script may need some tuning, depending on the
312 database name.</p>
317 section</a>. You will also need to have a controluser with the proper rights
324 unpacked one. Configuration files from very old versions (2.3.0 or older) may
325 require some tweaking as some options have been changed or removed.</p>
329 is version-specific.</p>
332 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
333 you should run the SQL script found in
340 where you want to give users access to their own database and don't want
341 them to play around with others.<br />
342 Nevertheless be aware that MS Internet Explorer seems to be really buggy
344 in this area!<br />
347 that your user/password pair are not in clear in the configuration file.
348 </li>
351 authentication modes are more secure: the MySQL login information does
352 not need to be set in the phpMyAdmin configuration file (except possibly
354 However, keep in mind that the password travels in plain text, unless
355 you are using the HTTPS protocol.<br />
356 In cookie mode, the password is stored, encrypted with the blowfish
357 algorithm, in a temporary cookie.</li>
360 your MySQL server is older than 4.1.2, or is running with
370 file under the
372 $cfg['Servers'][$i]['controluser']</a></tt> and
377 only an example: use something else in your file!</b> Input these
378 statements from the phpMyAdmin SQL Query window or mysql command–line
379 client.<br />
381 if it's not the same as the MySQL server's one.
383 <pre>
384 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
385 GRANT SELECT (
386 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
387 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
388 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
389 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
390 Execute_priv, Repl_slave_priv, Repl_client_priv
391 ) ON mysql.user TO 'pma'@'localhost';
392 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
393 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
394 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
395 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
397 If you are using an old MySQL version (below 4.0.2), please replace
398 the first GRANT SELECT query by this one:
400 <pre>
401 GRANT SELECT (
402 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
403 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
404 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
405 ) ON mysql.user TO 'pma'@'localhost';</pre>
407 ... and if you want to use the many new relation and bookmark features:
409 <pre>
411 </pre>
415 Of course, the above queries only work if your MySQL version supports
419 on a set of particular databases. Normally you shouldn't give global
420 privileges to an ordinary user, unless you understand the impact of those
421 privileges (for example, you are creating a superuser).<br />
425 <pre>
426 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
427 </pre>
429 What the user may now do is controlled entirely by the MySQL user
430 management system.<br />
432 authentication mode, you don't need to fill the user/password fields
434 array.</li>
435 </ul>
440 method and allows you to log in as any valid MySQL user.</li>
441 <li>Is supported with most PHP configurations. For
454 mode.</li>
455 </ul>
459 <ul><li>You can use this method as a replacement for the
461 (for example, if you're running
463 <li>Obviously, the user must enable cookies in the browser, but this is
464 now a requirement for all authentication modes.</li>
465 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
466 with the same username.</li>
467 <li>If you want to log in to arbitrary server see
472 not required.</li>
473 </ul>
477 <ul><li>This mode is the less secure one because it requires you to fill the
479 $cfg['Servers'][$i]['user']</a> and
481 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
482 can read your config.inc.php can discover your username and password).
483 <br />
490 is an entry explaining how to protect your configuration file.</li>
491 <li>For additional security in this mode, you may wish to consider the Host
492 authentication
494 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
496 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
497 directives.</li>
498 <li>Unlike cookie and http, does not require a user to log in when first
499 loading the phpMyAdmin site. This is by design but could allow any
500 user to access your installation. Use of some restriction method is
502 HTTP-AUTH directive or disallowing incoming HTTP requests at
503 one’s router or firewall will suffice (both of which
504 are beyond the scope of this manual but easily searchable with Google).</li>
505 </ul>
507 <!-- CONFIGURATION -->
511 users:</span> PHP does not seem to like
515 before saving a script you have modified.</p>
520 section to create one. This file only needs to contain the parameters you want to
521 change from their corresponding default value in
524 <p> The parameters which relate to design (like colors) are placed in
527 your site specific code to be included on start and end of each page.</p>
531 (with full path) to your phpMyAdmin installation's directory.
534 some web servers are case–sensitive.
537 Starting with version 2.3.0, it is advisable to try leaving this
538 blank. In most cases phpMyAdmin automatically detects the proper
539 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
540 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
541 A good test is to browse a table, edit a row and save it. There should
542 be an error message if phpMyAdmin is having trouble auto–detecting
543 the correct value. If you get an error that this must be set or if
544 the autodetect code fails to detect your path, please post a bug
545 report on our bug tracker so we can improve the code.</dd>
549 with master / foreign – tables (see
551 <br />
552 If you tried to set this up and it does not work for you, have a look on
554 use it. You will find a link that will analyze why those features have
555 been disabled.<br />
556 If you do not want to use those features set this variable to
561 algorithm to encrypt the password.<br />
563 passphrase of your choice. It will be used internally by the blowfish
564 algorithm: you won’t be prompted for this passphrase. The maximum
569 MySQL servers. Therefore, a
571 been added which contains the login information for the different servers.
572 The first
574 contains the hostname of the first server, the second
576 the hostname of the second server, etc. In
578 server definition, however you can put as many as you need in
580 have to define all settings, just those you need to change).</dd>
584 $i-th MySQL-server. E.g. localhost.</dd>
589 ignores this port number and connects with the socket, so if you want
590 to connect to a port different from the default port, use
593 </dd>
597 To determine the correct socket, check your MySQL configuration or, using the
599 Among the resulting information displayed will be the socket used.</dd>
602 <dd>What type connection to use with the MySQL server. Your options are
604 is nearly guaranteed to be available on all MySQL servers, while
605 sockets are not supported on some platforms.<br /><br />
607 To use the socket mode, your MySQL server must be on the same machine
608 as the Web server.</dd>
611 <dd>What php MySQL extension to use for the connection. Valid options are:
612 <br /><br />
615 The classic MySQL extension. This is the recommended and default
616 method at this time.<br /><br />
619 The improved MySQL extension. This extension became available
620 with php 5.0.0 and is the recommended way to connect to a server
624 <dd>Whether to use a compressed protocol for the MySQL server connection
625 or not (experimental).<br />
631 </dt>
633 all relational features (see
635 and, for a MySQL server older than 4.1.2 or running with
638 authentication mode).<br /><br />
641 cookie authentication modes (or 'config'
642 authentication mode since phpMyAdmin 2.2.1), you need to supply the
647 This account is used to check what databases the user will see at
648 login.<br />
652 In phpMyAdmin versions before 2.2.5, those were called
657 <dd>Whether config or cookie or
659 should be used for this server.
661 is the plain old way: username and password are stored in
663 <li>'cookie' authentication mode
665 2.2.3 allows you to log in as any valid MySQL user with the
666 help of cookies. Username and password are stored in
667 cookies during the session and password is deleted when it
668 ends. This can also allow you to log in in arbitrary server if
669 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
670 </li>
671 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in older versions)
672 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
673 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
674 <li>'signon' authentication mode
676 as introduced in 2.10.0 allows you to log in from prepared PHP
677 session data. This is useful for implementing single signon
678 from another application. Sample way how to seed session is in
684 </ul>
687 for more information.
688 </dd>
692 </dt>
693 <dd>
694 When using auth_type = 'config', this is the user/password-pair
695 which phpMyAdmin will use to connect to the
696 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
697 cookie authentication is used and should be empty.</dd>
699 <span
701 </dt>
702 <dd>
703 Allow attempt to log in without password when a login with password
704 fails. This can be used together with http authentication, when
705 authentication is done some other way and phpMyAdmin gets user name
706 from auth and uses empty password for connecting to MySQL. Password
707 login is still tried first, but as fallback, no password method is
708 tried.</dd>
711 </dt>
712 <dd>
713 If set to a (an array of) database name(s), only this (these) database(s)
714 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
715 database(s) name(s) may contain MySQL wildcards characters
719 This setting is an efficient way to lower the server load since the
720 latter does not need to send MySQL requests to build the available
722 privileges rules of the MySQL database server</span>. If set, it just
723 means only these databases will be displayed but
725 <br /><br />
727 An example of using more that one database:
729 <br /><br />
731 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
732 databases in the left frame, so that you can individually arrange your databases.<br />
733 If you want to have certain databases at the top, but don't care about the others, you do not
734 need to specify all other databases. Use:
736 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
737 order.</dd>
740 </dt>
741 <dd>Regular expression for hiding some databases. This only hides them
742 from listing, but a user is still able to access them (using, for example,
743 the SQL query area). To limit access, use the MySQL privilege system.
744 <br /><br />
749 More information on regular expressions can be found in the
751 PCRE pattern syntax</a> portion of the PHP reference manual.
752 </dd>
755 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
756 this string will be displayed instead of the hostname in the pull-down
757 menu on the main page. This can be useful if you want to show only
758 certain databases on your system, for example.</dd>
762 </dt>
763 <dd>The name of the database containing the linked-tables infrastructure.
764 <br /><br />
767 section in this document to see the benefits of this infrastructure,
768 and for a quick way of creating this database and the needed tables.
769 <br /><br />
771 If you are the only user of this phpMyAdmin installation, you can
772 use your current database to store those special tables; in this
773 case, just put your current database name in
775 set this parameter to the name of your central database containing
776 the linked-tables infrastructure.</dd>
780 </dt>
782 useful for queries you often run.<br /><br />
784 To allow the usage of this functionality:
786 <li>enter the table name in
788 </ul>
789 </dd>
793 </dt>
795 which field is a key in another table (a foreign key). phpMyAdmin
796 currently uses this to
797 <ul><li>make clickable, when you browse the master table, the data values
798 that point to the foreign table;</li>
800 when browsing the master table, if you move the mouse to a column
801 containing a foreign key (use also the 'table_info' table);<br />
804 <li>in edit/insert mode, display a drop-down list of possible foreign
808 <li>display links on the table properties page, to check referential
809 integrity (display missing foreign keys) for each described key;
810 </li>
814 schema of your database (also uses the table_coords table).</li>
815 </ul>
817 The keys can be numeric or character.<br /><br />
819 To allow the usage of this functionality:
822 infrastructure</li>
823 <li>put the relation table name in
825 <li>now as normal user open phpMyAdmin and for each one of your
826 tables where you want to use this feature, click
828 </li>
829 </ul>
833 future development of the cross-db relations.
834 </dd>
838 </dt>
839 <dd>
840 Since release 2.3.0 you can describe, in a special 'table_info'
841 table, which field is to be displayed as a tool-tip when moving the
842 cursor over the corresponding key.<br />
843 This configuration variable will hold the name of this special
844 table. To allow the usage of this functionality:
846 <li>put the table name in
848 <li>then for each table where you want to use this feature,
850 to choose the field.</li>
851 </ul>
853 </dd>
857 </dt>
860 the relations between your tables. To do this it needs two tables
865 schema output).<br /><br />
869 To allow the usage of this functionality:
872 infrastructure</li>
873 <li>put the correct table names in
876 </ul>
879 </dd>
883 </dt>
885 Since release 2.3.0 you can store comments to describe each column for
887 <br /><br />
889 Starting with release 2.5.0, comments are consequently used on the table
890 property pages and table browse view, showing up as tool-tips above the
891 column name (properties page) or embedded within the header of table in
892 browse view. They can also be shown in a table dump. Please see the
893 relevant configuration directives later on.<br /><br />
895 Also new in release 2.5.0 is a MIME-transformation system which is also
897 Transformations</a> for further information. To use the
898 MIME-transformation system, your column_info table has to have the three
899 new fields 'mimetype', 'transformation', 'transformation_options'.
900 <br /><br />
902 To allow the usage of this functionality:
904 infrastructure</li>
905 <li>put the table name in
909 <pre>
910 ALTER TABLE `pma_column_comments`
911 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
912 ADD `transformation` VARCHAR( 255 ) NOT NULL,
913 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
914 </pre>
917 renamed from<br />
920 </ul>
921 </dd>
925 </dt>
928 all queries you entered manually into the phpMyAdmin interface. If you
929 don't want to use a table-based history, you can use the JavaScript-based
930 history. Using that, all your history items are deleted when closing the
931 window.<br /><br />
933 Using
935 you can specify an amount of history items you want to have on hold. On
936 every login, this list gets cut to the maximum amount.<br /><br />
938 The query history is only available if JavaScript is enabled in your
939 browser.<br /><br />
941 To allow the usage of this functionality:
944 infrastructure</li>
946 </li>
947 </ul>
948 </dd>
951 </dt>
953 column_info table got enhanced with three new fields. If the above variable
955 latest table structure available. If not, it will emit a warning to the
956 superuser.<br /><br />
958 You can disable this checking behavior by setting the variable to false,
959 which should offer a performance increase.<br /><br />
961 Recommended to set to FALSE, when you are sure, your table structure is
962 up to date.</dd>
964 boolean</dt>
965 <dd>Whether to allow root access. This is just simplification of rules below.
966 </dd>
969 </dt>
971 authentication is disabled.<br /><br />
974 all deny rules followed by allow rules. Access is allowed by default. Any
975 client which does not match a Deny command or does match an Allow command
976 will be allowed access to the server. <br /><br />
979 applies all allow rules followed by deny rules. Access is denied by
980 default. Any client which does not match an Allow directive or does
981 match a Deny directive will be denied access to the server.<br /><br />
983 If your rule order is set to 'explicit', the authentication is
984 performed in a similar fashion to rule order 'deny,allow', with the
988 and was available in Apache by specifying allow and deny rules without
989 setting any order.
990 </dd>
992 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
993 </dt>
994 <dd>The general format for the rules is as such:
996 <pre>
998 </pre>
1003 well (please note that those containing SERVER_ADDRESS might not be
1004 available on all webservers):
1005 <pre>
1011 </pre>
1013 Having an empty rule list is equivalent to either using
1019 following work:<br />
1021 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1022 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1023 But the following does not work:<br />
1026 </dd>
1027 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1028 <dd>Name of session which will be used for signon authentication method.
1029 </dd>
1031 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1032 </dd>
1034 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1035 </dd>
1038 <dd>If you have more than one server configured, you can set
1040 that server when phpMyAdmin is started, or set it to 0 to be given a
1041 list of servers without logging in.<br />
1043 MUST be set to that server.</dd>
1046 <dd>Defines whether to use GZip output buffering for increased
1048 Set to true/false for enabling/disabling. When set to 'auto' (string),
1049 phpMyAdmin tries to enable output buffering and will automatically disable
1050 it if your browser has some problems with buffering. IE6 with a certain patch
1051 is known to cause data corruption when having enabled buffering.</dd>
1054 <dd>Whether persistent connections should be used or not (mysql_connect or
1055 mysql_pconnect).</dd>
1061 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1062 to zero, no time limit is imposed.<br />
1063 This setting is used while importing/exporting dump files but has no
1064 effect when PHP is running in safe mode.</dd>
1067 <dd>Set the number of bytes a script is allowed to allocate. If number set
1068 to zero, no limit is imposed.<br />
1069 This setting is used while importing/exporting dump files but has no
1070 effect when PHP is running in safe mode.<br />
1074 <dd>Mark used tables and make it possible to show databases with locked
1079 generated by phpMyAdmin should be displayed or not.</dd>
1082 <dd>Defines whether normal users (non-administrator) are allowed to
1083 delete their own database or not. If set as FALSE, the link "Drop
1085 mydatabase" will be rejected. Quite practical for
1087 customers.<br />
1088 Please note that this limitation of SQL queries is not as strict as
1089 when using MySQL privileges. This is due to nature of SQL queries
1090 which might be quite complicated. So this choice should be viewed as
1091 help to avoid accidental dropping rather than strict privilege
1092 limitation.</dd>
1096 displayed when you're about to lose data.</dd>
1099 <dd>Define whether the previous login should be recalled or not in cookie
1100 authentication mode.</dd>
1107 means that it will be kept for existing session. This is recommended
1108 for not trusted environments.</dd>
1111 <dd>If enabled (default), logout deletes cookies for all servers,
1112 otherwise only for current one. Setting this to false makes it easy to
1113 forget to log out from other server, when you are using more of
1114 them.</dd>
1120 <dd>Define whether phpMyAdmin will continue executing a multi-query
1121 statement if one of the queries fails. Default is to abort execution.</dd>
1124 <dd>Define whether phpMyAdmin will output the results of each query of a
1125 multi-query statement embedded into the
1130 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1131 <br /><br />
1134 MySQL servers behind the firewall where your
1136 </dd>
1139 <dd>Defines whether to use a select-based menu and display only the current
1140 tables in the left frame (smaller page). Only in Non-Lightmode you can
1141 use the feature to display nested folders using
1143 </dd>
1146 <dd>In light mode, defines whether to display the names of databases (in the
1147 selector) using a tree, see also
1149 </dd>
1152 <dd>The string used to separate the parts of the database name when showing
1153 them in a tree.</dd>
1156 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1157 This means if you have tables like 'first__second__third' this will be
1159 If set to FALSE or empty, the feature is disabled. NOTE: You should
1160 not use this separator at the beginning or end of a
1161 table name or multiple times after another without any other
1162 characters in between.</dd>
1165 <dd>Defines how many sublevels should be displayed when splitting
1166 up tables by the above separator.</dd>
1169 <dd>Defines whether to display table comment as tool-tip in left frame or
1170 not.</dd>
1173 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1174 comment and the real name. That means that if you have a table called
1175 'user0001' and add the comment 'MyName' on it, you will see the name
1176 'MyName' used consequently in the left frame and the tool-tip shows
1177 the real name of the DB.</dd>
1180 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1182 When setting this to 'nested', the Alias of the Tablename is only used
1183 to split/nest the tables according to the
1185 directive. So only the folder is called like the Alias, the tablename itself
1186 stays the real tablename.</dd>
1189 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1192 <dd>Enter URL where logo in left frame will point to. For use especially
1193 with self made theme which changes this.</dd>
1195 <dd>Defines whether or not to display a server choice at the top of the left frame.
1196 Defaults to FALSE.</dd>
1198 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1199 Defaults to FALSE (drop-down).</dd>
1201 <dd>Defines whether or not to display space usage and statistics about databases
1202 and tables.<br />
1203 Note that statistics requires at least MySQL 3.23.3 and that, at this
1204 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1207 <dd>Defines whether to display detailed server information on main page.
1208 You can additionally hide more information by using
1210 </dd>
1215 </dt>
1218 not at the starting main (right) frame. This setting
1219 does not check MySQL commands entered directly.<br /><br />
1221 Please note that to block the usage of phpinfo() in scripts, you
1228 hard coded password value in the configuration file, end users can't
1229 be allowed to change their passwords.</dd>
1232 <dd>Defines whether to suggest a database name on the
1237 content.</dd>
1240 <dd>Defines whether navigation bar buttons and the right panel top menu
1241 contain text or symbols only. A value of TRUE displays icons, FALSE
1242 displays text and 'both' displays both icons and text.</dd>
1245 <dd>Defines whether a user should be displayed a
1249 <dd>Number of rows displayed when browsing a result set. If the result set
1256 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1260 from editing when browsing a table's content. Valid values are:
1265 </ul>
1266 </dd>
1269 <dd>Defines whether or not MySQL functions fields should be displayed in
1270 edit/insert mode.</dd>
1273 <dd>Defines which type of editing controls should be used for CHAR and
1274 VARCHAR fields. Possible values are:
1275 <ul><li>input - this allows to limit size of text to size of field in
1276 MySQL, but has problems with newlines in fields</li>
1277 <li>textarea - no problems with newlines in fields, but also no
1278 length limitations</li>
1279 </ul>
1280 Default is old behavior so input.</dd>
1286 <dd>If there are fewer items than this in the set of foreign keys, then a
1287 drop-down box of foreign keys is presented, in the style described by the
1289 setting.</dd>
1292 <dd>For the foreign key drop-down fields, there are several methods of
1293 display, offering both the key and value data. The contents of the
1294 array should be one or both of the following strings:
1300 </dt>
1301 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1302 creating a dump file</dd>
1305 </dt>
1306 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1307 compressed exports. This doesn't affect smaller dumps and allows users to
1308 create larger dumps that won't otherwise fit in memory due to php
1309 memory limit. Produced files contain more GZip/BZip2 headers, but all
1310 normal programs handle this correctly.</dd>
1314 mainframe.</dd>
1318 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1323 <dd>How many columns will be utilized to display the tables on the
1324 database property view? Default is 1 column. When setting this to a
1325 value larger than 1, the type of the database will be omitted for more
1326 display space.</dd>
1330 <dd>Defines the tab displayed by default on server view. Possible
1337 <dd>Defines the tab displayed by default on database view. Possible
1342 <dd>Defines the tab displayed by default on table view. Possible
1349 points to the MySQL documentation (type depends
1350 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1351 generated.<br />
1353 for more information about MySQL manuals and their types.</dd>
1356 <dd>Type of MySQL documentation:
1362 </ul>
1363 </dd>
1366 <dd>Defines the default language to use, if not browser-defined or
1367 user-defined.<br />
1369 this setting.</dd>
1372 <dd>Defines the default connection collation to use, if not
1373 user-defined.<br />
1378 <dd>Force: always use this language (must be defined in the
1382 <dd>Limit list of available languages to those matching the given regular
1383 expression. For example if you want only Czech and English, you should
1387 <dd>Default character set to use for recoding of MySQL queries. This must be
1388 enabled and it's described by
1390 option.<br />
1391 You can give here any character set which is in
1393 array and this is just default choice, user can select any of them.</dd>
1396 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1397 support (compiled in or module) in PHP to allow MySQL queries recoding
1398 and used language file must have it enabled (by default only these
1399 which are in Unicode, just to avoid losing some characters).<br /><br />
1402 in the Export page, to choose the character set when exporting a file.
1403 </dd>
1406 <dd>You can select here which functions will be used for character set
1407 conversion. Possible values are:
1408 <ul><li>auto - automatically use available one (first is tested
1409 iconv, then recode)</li>
1412 </ul>
1413 Default is auto.</dd>
1416 <dd>Specify some parameters for iconv used in charset conversion. See
1419 used, so that invalid characters will be transliterated.</dd>
1422 <dd>Available character sets for MySQL conversion. You can add your own (any of
1423 supported by recode/iconv) or remove these which you don't use.
1424 Character sets will be shown in same order as here listed, so if you
1425 frequently use some of these move them to the top.</dd>
1429 MIME transformations.<br />
1430 Possible values are:
1431 <ul><li>auto - automatically detect, this is a bit expensive
1433 according to your server real possibilities</li>
1436 </ul>
1437 Default is auto.
1438 </dd>
1442 </dd>
1444 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1445 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1446 </dt>
1447 <dd>The background styles used for both the frames.
1450 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1452 <dd>The style used for the pointer in the navi frame.
1461 </dd>
1465 <dd>The style used for table headers. See
1470 </dd>
1474 </dd>
1476 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1478 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1480 </dt>
1482 The former feature highlights the row over which your mouse is passing
1483 and the latter lets you visually mark/unmark rows by clicking on
1484 them.<br />
1489 <dd>You put here a valid CSS font family value, for example
1494 <dd>You put here a valid CSS font family value, for example
1508 </dt>
1510 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1512 The Char* values are used for CHAR and VARCHAR editing (if configured
1516 </dt>
1520 </dt>
1521 <dd>Defines if the whole textarea of the query box will be selected on
1522 click.</dd>
1525 </dt>
1526 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1527 editing.</dd>
1530 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1531 Can be turned off by a toggle button on the browse page.</dd>
1535 </dt>
1536 <dd>Defines the place where modify and delete links would be put when
1537 tables contents are displayed (you may have them displayed both at the
1538 left and at the right).
1544 </dt>
1546 Define which one is displayed by default. The first mode displays each
1547 row on a horizontal line, the second rotates the headers by 90
1548 degrees, so you can use descriptive headers even though fields only
1549 contain small values and still print them out. The vertical mode sorts
1550 each row on a vertical lineup.<br /><br />
1552 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1553 the rotation of the header for horizontalflipped is done via CSS. If
1554 set to 'fake' PHP does the transformation for you, but of course this
1555 does not look as good as CSS.</dd>
1559 <dd>When editing/creating new columns in a table all fields normally get
1560 lined up one field a line. (default: 'horizontal'). If you set this to
1561 'vertical' you can have each field lined up vertically beneath each
1562 other. You can save up a lot of place on the horizontal direction and
1563 no longer have to scroll.</dd>
1567 </dt>
1569 display of column comments in Browse or Property display. In browse
1570 mode, the comments are shown inside the header. In property mode,
1571 comments are displayed using a CSS-formatted dashed-line below the
1572 name of the field. The comment is shown as a tool-tip for that field.
1573 </dd>
1576 <dd>
1577 The name of the directory where
1579 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1580 are available under a drop-down box when you click the database name,
1582 <br /><br />
1584 If you want different directory for each user, %u will be replaced
1585 with username.<br /><br />
1589 compressed formats is enabled).<br /><br />
1591 This feature is useful when your file is too big to be uploaded via
1593 uploads are disabled in PHP.<br /><br />
1595 Please note that if PHP is running in safe mode, this directory must
1596 be owned by the same user as the owner of the phpMyAdmin scripts.
1597 <br /><br />
1601 alternatives.
1602 </dd>
1605 <dd>
1606 The name of the directory where docSQL files can be uploaded for
1607 import into phpMyAdmin.
1608 <br /><br />
1609 Please note that if PHP is running in safe mode, this directory must
1610 be owned by the same user as the owner of the phpMyAdmin scripts.
1611 </dd>
1614 <dd>
1615 The name of the directory where dumps can be saved.<br /><br />
1617 If you want different directory for each user, %u will be replaced
1618 with username.<br /><br />
1620 Please note that the directory has to be writable for user running
1621 webserver.<br /><br />
1623 Please note that if PHP is running in safe mode, this directory must
1624 be owned by the same user as the owner of the phpMyAdmin scripts.
1625 </dd>
1628 <dd>
1629 The name of the directory where temporary files can be stored.
1630 <br /><br />
1631 This is needed for native MS Excel export, see
1634 </dd>
1637 <dd>
1638 In this array are defined default parameters for export, names of
1639 items are similar to texts seen on export page, so you can easily
1640 identify what they mean.
1641 </dd>
1644 <dd>
1645 In this array are defined default parameters for import, names of
1646 items are similar to texts seen on import page, so you can easily
1647 identify what they mean.
1648 </dd>
1651 <dd>
1652 Repeat the headers every X cells, or 0 to deactivate.
1653 </dd>
1661 </dt>
1662 <dd>
1663 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1664 or icon is always displayed on the left panel. If JavaScript is enabled in
1665 your browser, a click on this opens a distinct query window, which is
1666 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1667 changes to display a query box.<br /><br />
1669 The size of this query window can be customized with
1671 - both integers for the size in pixels. Note that normally, those
1673 theme you are using.<br /><br />
1677 opens the query window and puts the current query
1678 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1679 query in the right panel's query box.
1680 <br /><br />
1681 The usage of the JavaScript query window is recommended if you have a
1682 JavaScript enabled browser. Basic functions are used to exchange quite
1683 a few variables, so most 4th generation browsers should be capable to
1684 use that feature. It currently is only tested with Internet Explorer 6
1685 and Mozilla 1.x.
1686 <br /><br />
1688 to a table, which has to be created by you (see <a
1690 all your queries will be appended to the form, but only as long as
1691 your window is opened they remain saved.
1692 <br /><br />
1693 When using the JavaScript based query window, it will always get
1694 updated when you click on a new table/db to browse and will focus if
1695 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1696 the query window by checking the box "Do not overwrite this query from
1697 outside the window" below the query textarea. Then you can browse
1698 tables/databases in the background without losing the contents of the
1699 textarea, so this is especially useful when composing a query with
1700 tables you first have to look in. The checkbox will get automatically
1701 checked whenever you change the contents of the textarea. Please
1702 uncheck the button whenever you definitely want the query window to
1703 get updated even though you have made alterations.
1704 <br /><br />
1707 <br /><br />
1708 The query window also has a custom tabbed look to group the features.
1710 default tab to be used when opening the query window. It can be set to
1711 either 'sql', 'files', 'history' or 'full'.</dd>
1717 <dd><ul><li>For InnoDB tables, determines for how large tables phpMyAdmin
1719 If the approximate row count as returned by
1722 count will be used.</li>
1723 <li>For VIEWs, since obtaining the exact count could have an
1724 impact on performance, this value is the maximum to be displayed.
1725 </li>
1726 </ul>
1727 </dd>
1731 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1733 page. By clicking on the button 'toggle scratchboard' on the page
1734 where you edit x/y coordinates of those elements you can activate a
1735 scratchboard where all your elements are placed. By clicking on an
1736 element, you can move them around in the pre-defined area and the x/y
1737 coordinates will get updated dynamically. Likewise, when entering a
1738 new position directly into the input field, the new position in the
1739 scratchboard changes after your cursor leaves the input field.<br />
1740 You have to click on the 'OK'-button below the tables to save the new
1741 positions. If you want to place a new element, first add it to the
1742 table of elements and then you can drag the new element around.<br />
1743 By changing the paper size and the orientation you can change the size
1744 of the scratchboard as well. You can do so by just changing the
1745 dropdown field below, and the scratchboard will resize automatically,
1746 without interfering with the current placement of the elements.<br />
1747 If ever an element gets out of range you can either enlarge the paper
1748 size or click on the 'reset' button to place all elements below each
1749 other.<br />
1751 get this control to work. The basic Drag&Drop script functionality
1752 was kindly borrowed from www.youngpup.net and is underlying so
1753 specific license.</dd>
1756 <dd>Sorts database and table names according to natural order (for example,
1757 t1, t2, t10). Currently implemented in the left panel (Light mode)
1758 and in Database view, for the table list.</dd>
1764 <dd>Allows you to specify window's title bar. Following magic string can
1765 be used to get special values:
1766 <dl>
1772 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1781 </dl>
1782 </dd>
1792 </dd>
1795 <dd>If theme manager is active, use this as the path of the subdirectory
1796 containing all the themes.</dd>
1810 </dt>
1811 <dd>Default queries that will be displayed in query boxes when user didn't
1812 specify any. Use %d for database name, %t for table name and %f for a
1813 comma separated list of field names. Note that %t and %f are only
1817 <dd>
1818 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
1819 default we use HTML to format the query, but you can disable this by
1821 </dd>
1824 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1825 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1826 query inside a bracket is indented. By changing
1829 specifies the units of the indent amount that you specified. This is
1830 used via stylesheets.</dd>
1833 <dd>This array is used to define the colours for each type of element of
1834 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1836 If you specify an empty string for the color of a class, it is ignored
1837 in creating the stylesheet.
1838 You should not alter the class names, only the colour strings.<br />
1859 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1863 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1864 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1865 </ul>
1866 </dd>
1870 <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,
1871 as originally published on
1873 <br />
1874 For help in setting up your system to use the service, see the
1876 </dd>
1880 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1881 and any password, so we use those by default. Instead, if
1882 you have an account with them, you can put your login details
1883 here, and it will be used in place of the anonymous login.</dd>
1884 </dl>
1885 </dd>
1888 <dd><b>DEVELOPERS ONLY!</b></dd>
1891 <dd><b>DEVELOPERS ONLY!</b><br />
1892 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1893 the code.<br />
1894 For help in setting up your system to this, see the
1898 <dd><b>DEVELOPERS ONLY!</b><br />
1899 Enable profiling support for phpMyAdmin. This will append a chunk of data
1900 to the end of every page displayed in the main window with profiling
1901 statistics for that page.<br />
1902 You may need to increase the maximum execution time for this to
1903 complete successfully.<i>Profiling was removed from the code for
1904 version 2.9.0 due to licensing issues.</i></dd>
1906 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
1907 <dd><b>DEVELOPERS ONLY!</b><br />
1908 When profiling data is displayed, this variable controls the threshold of
1909 display for any profiling data, based on the average time each time has
1910 taken. If it is over the threshold it is displayed, otherwise it is not
1911 displayed. This takes a value in milliseconds. In most cases you don't need
1912 to edit this.</dd>
1915 <dd>All possible types of a MySQL column. In most cases you don't need to
1916 edit this.</dd>
1919 <dd>Possible attributes for fields. In most cases you don't need to edit
1920 this.</dd>
1923 <dd>A list of functions MySQL supports. In most cases you don't need to
1924 edit this.</dd>
1927 <dd>Mapping of column types to meta types used for preferring displayed
1928 functions. In most cases you don't need to edit this.</dd>
1931 <dd>Functions preferred for column meta types as defined in
1932 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
1933 to edit this.</dd>
1936 <dd>Functions selected by default when inserting/changing row, Functions
1937 are defined for meta types from
1939 <code>first_timestamp</code>, which is used for first timestamp column
1940 in table.</dd>
1943 <dd>Operators available for search operations on numeric and date fields.
1944 </dd>
1947 <dd>Operators available for search operations on character fields.
1948 Note that we put <code>LIKE</code> by default instead of
1949 <code>LIKE %...%</code>, to avoid unintended performance problems
1950 in case of huge tables.</dd>
1953 <dd>Operators available for search operations on enum fields.</dd>
1956 <dd>Additional operators available for search operations when the
1957 field can be null.</dd>
1959 </dl>
1961 <!-- TRANSFORMATIONS -->
1967 </ol>
1971 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
1973 section</a> on how to do so.</p>
1975 <p> You can apply different transformations to the contents of each field. The
1976 transformation will take the content of each field and transform it with
1977 certain rules defined in the selected transformation.</p>
1979 <p> Say you have a field 'filename' which contains a filename. Normally you would
1980 see in phpMyAdmin only this filename. Using transformations you can transform
1981 that filename into a HTML link, so you can click inside of the phpMyAdmin
1982 structure on the field's link and will see the file displayed in a new browser
1983 window. Using transformation options you can also specify strings to
1984 append/prepend to a string or the format you want the output stored in.</p>
1986 <p> For a general overview of all available transformations and their options,
1987 you can consult your
1988 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
1989 installation.</p>
1991 <p> For a tutorial on how to effectively use transformations, see our
1993 the official phpMyAdmin homepage.</p>
1997 <p> Go to your <i>tbl_properties_structure.php</i> page (i.e. reached through
1998 clicking on the 'Structure' link for a table). There click on
1999 "Change" (or change icon) and there you will see three new fields at
2000 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2001 'Transformation options'.</p>
2003 <ul><li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
2004 empty or to use 'auto' [this feature is not yet available]. Please note that
2005 transformations are inactive as long as no MIME-type is selected.</li>
2007 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2008 hopefully growing amount of pre-defined transformations. See below for information on
2009 how to build your own transformation.<br />
2011 There are global transformations and mimetype-bound transformations. Global transformations
2012 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2013 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2014 transformations which operate on the main mimetype (like 'image'), which will most likely
2015 take the subtype into regard, and those who only operate on a
2016 specific subtype (like 'image/jpeg').<br />
2018 You can use transformations on mimetypes for which the function was not defined for. There
2019 is no security check for you selected the right transformation, so take care of what the
2020 output will be like.</li>
2022 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2023 transform-function specific options here. Usually the transforms can operate with default
2024 options, but it is generally a good idea to look up the overview to see which options are
2025 necessary.<br />
2027 Much like the ENUM/SET-Fields, you have to split up several options using the format
2028 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2029 parsed as an array, leaving the first value the first element in the array, and so
2030 forth.<br />
2032 If you want to specify a MIME character set you can define it in the transformation_options.
2033 You have to put that outside of the pre-defined options of the specific mime-transform,
2035 for which you can specify 2 options and you want to append a character set, enter "'first
2036 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2038 </ul>
2042 <p> All mimetypes and their transformations are defined through single files in
2043 the directory 'libraries/transformations/'.</p>
2045 <p> They are stored in files to ease up customization and easy adding of new
2046 transformations.</p>
2048 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2049 always work. It makes no sense to apply a transformation to a mimetype, the
2050 transform-function doesn't know to handle.</p>
2052 <p> One can, however, use empty mime-types and global transformations which should work
2053 for many mimetypes. You can also use transforms on a different mimetype they where built
2054 for, but pay attention to option usage as well as what the transformation does to your
2055 field.</p>
2057 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2058 any other transform function and provides some basic functions.</p>
2060 <p> There are 5 possible file names:</p>
2062 <ol><li>A mimetype+subtype transform:<br /><br />
2064 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2066 Please not that mimetype and subtype are separated via '_', which shall
2067 not be contained in their names. The transform function/filename may
2068 contain only characters which cause no problems in the file system as
2069 well as the PHP function naming convention.<br /><br />
2071 The transform function will the be called
2072 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2074 <b>Example:</b><br /><br />
2076 <tt>text_html__formatted.inc.php</tt><br />
2077 <tt>PMA_transform_text_html__formatted()</tt></li>
2079 <li>A mimetype (w/o subtype) transform:<br /><br />
2081 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2083 Please note that there are no single '_' characters.
2084 The transform function/filename may contain only characters which cause
2085 no problems in the file system as well as the PHP function naming
2086 convention.<br /><br />
2088 The transform function will the be called
2089 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2091 <b>Example:</b><br /><br />
2093 <tt>text__formatted.inc.php</tt><br />
2094 <tt>PMA_transform_text__formatted()</tt></li>
2096 <li>A mimetype+subtype without specific transform function<br /><br />
2098 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2100 Please note that there are no '__' characters in the filename. Do not
2101 use special characters in the filename causing problems with the file
2102 system.<br /><br />
2104 No transformation function is defined in the file itself.<br /><br />
2106 <b>Example:</b><br /><br />
2108 <tt>text_plain.inc.php</tt><br />
2109 (No function)</li>
2111 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2113 <tt>[mimetype].inc.php</tt><br /><br />
2115 Please note that there are no '_' characters in the filename. Do not use
2116 special characters in the filename causing problems with the file system.
2117 <br /><br />
2119 No transformation function is defined in the file itself.<br /><br />
2121 <b>Example:</b><br /><br />
2123 <tt>text.inc.php</tt><br />
2124 (No function)</li>
2126 <li>A global transform function with no specific mimetype<br /><br />
2128 <tt>global__[transform].inc.php</tt><br /><br />
2130 The transform function will the be called
2131 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2133 <b>Example:</b><br /><br />
2135 <tt>global__formatted</tt><br />
2136 <tt>PMA_transform_global__formatted()</tt></li>
2137 </ol>
2139 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2140 transform function.</p>
2142 <p> All filenames containing no '__' in themselves are not shown as valid transform
2143 functions in the dropdown.</p>
2145 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2146 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2147 without a transform function. Also note the introduction of a function description in
2148 the language files. For each function a $strTransformation_[filename without .inc.php]
2149 has to exist.</p>
2151 <p> You can use the template generator to generate new functions and entries in the
2152 language file.</p>
2154 <p> To create a new transform function please see
2155 <tt>libraries/transformations/template_generator.sh</tt>.
2156 To create a new, empty mimetype please see
2157 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2159 <p> A transform function always gets passed three variables:</p>
2161 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2162 you want to transform.</li>
2163 <li><b>$options</b> - Contains any user-passed options to a transform function
2164 as an array.</li>
2165 <li><b>$meta</b> - Contains an object with field information to your column.
2166 The data is drawn from the output of the
2168 function. This means, all object properties described on the
2170 available in this variable and can be used to transform a field accordingly
2171 to unsigned/zerofill/not_null/... properties.<br />
2172 The $meta->mimetype variable contains the original MIME-type of the
2173 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2174 </ol>
2176 <!-- FAQ -->
2183 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2187 </ol>
2189 <p> Please have a look at our
2191 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2192 features and or interface.</p>
2198 action is required or phpMyAdmin sends a blank page or a page full of
2199 cryptic characters to my browser, what can I do?</a></h4>
2201 <p> There are some known PHP bugs with output buffering and compression.<br />
2203 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2204 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2205 configuration file.<br />
2206 Furthermore, we know about such problems connected to the release
2207 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2208 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2213 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2214 See also the
2216 entry about PHP bugs with output buffering.<br />
2217 If your server keeps crashing, please ask for help in the various Apache
2218 support groups.</p>
2222 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2223 script: I'm always displayed the login screen.</a></h4>
2225 <p> This is a known PHP bug (see this
2227 official PHP bug database. It means there is and won't be any phpMyAdmin
2228 fix against it because there is no way to code a fix.</p>
2234 application misbehaved by not returning a complete set of
2236 </h4>
2238 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2239 Have a look at the last message in this
2241 official PHP bug database.</p>
2246 and/or many error messages with the
2248 mode.</a></h4>
2250 <p> This is a known problem with the PHP
2252 filter: it's not so stable. Please use instead the cookie authentication mode.
2253 </p>
2258 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2259 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2260 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2261 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2262 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2267 work.</a></h4>
2269 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2270 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2271 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2272 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2273 We faced PHP crashes when trying to download a dump with MS Internet
2274 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2275 this case you should switch to the release version of PHP 4.2.0.</p>
2279 an error about safe mode being in effect.</a></h4>
2281 <p> Your uploaded file is saved by PHP in the "upload dir", as
2282 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2283 the system default is <i>/tmp</i>).<br />
2284 We recommend the following setup for Apache servers running in safe mode,
2285 to enable uploads of files while being reasonably secure:</p>
2287 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2288 <li>give ownership to the Apache server's user.group:
2289 <tt>chown apache.apache /tmp/php</tt></li>
2290 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2291 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2292 <li>restart Apache</li>
2293 </ul>
2297 general file uploads don't work on my system and uploaded files have a
2298 <tt>Content-Type:</tt> header in the first line.</a></h4>
2300 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2301 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2302 So the problem is that this package has a serious bug that was corrected
2303 ages ago in PHP (2001-01-28: see
2305 for more details). The problem is that the bugged package is still
2306 available though it was corrected (see
2308 for more details).<br />
2309 So please download
2310 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2311 and the problem should go away.<br />
2312 And that fixes the \r\n problem with file uploads!</p>
2316 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2317 I'm using the Apache server.</a></h4>
2319 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2320 your <i>httpd.conf</i>:</p>
2324 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2328 uploading a file from the query box.</a></h4>
2330 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2331 restrictions. Assuming that the restriction allows you to open files in the
2332 current directory ('.'), all you have to do is create a 'tmp' directory
2333 under the phpMyAdmin install directory, with permissions 777 and the same
2334 owner as the owner of your phpMyAdmin directory. The uploaded files will
2335 be moved there, and after execution of your
2341 <p> The MySQL manual explains how to
2343 reset the permissions</a>.</p>
2348 execute a bookmark.</a></h4>
2350 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2351 cannot access the uploaded query.</p>
2356 submit a query from the convenient text area.</a></h4>
2358 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2359 and try to increase it.</p>
2363 </h4>
2365 <p> In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2366 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2367 names to align with current standards.</p>
2372 </h4>
2374 <p> Starting with version 2.7.0, the import engine has been re–written and these
2375 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2376 to take advantage of the new import features.</p>
2378 <p> The first things to check (or ask your host provider to check) are the
2379 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2380 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2381 All of these three settings limit the maximum size of data that can be
2382 submitted and handled by PHP. One user also said that post_max_size
2383 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2385 There exist several workarounds if your upload is too big or your
2386 hosting provider is unwilling to change the settings:</p>
2389 feature. This allows one to
2390 upload a file to the server via scp, ftp, or your favorite file transfer
2391 method. PhpMyAdmin is then able to import the files from the temporary
2393 section</a> of this document.</li>
2395 BigDump</a>) to split the files before uploading. We cannot support this
2396 or any third party applications, but are aware of users having success
2397 with it.</li>
2398 <li>If you have shell (command line) access, use MySQL to import the files
2399 directly. You can do this by issuing the "source" command from
2400 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2401 </ul>
2405 support?</a></h4>
2407 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2408 fully supported. Please note that the older your MySQL version is, the more
2409 limitations you will have to face.<br />
2410 phpMyAdmin may connect to your MySQL server using php's classic
2413 is available in php 5.0.<br />
2414 Either way, the developers of both extensions recommend to use the classic
2415 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2416 When compiling php, we strongly recommend that you manually link the MySQL
2417 extension of your choice to a MySQL client library of at least the same
2418 minor version since the one that is bundled with some php distributions is
2421 If your webserver is running on a windows system, you might want to try
2422 MySQL's
2424 instead of the MySQL / MySQLi extensions that are bundled with the official
2425 php Win32 builds.
2426 <br />
2427 MySQL 5.1 is not yet supported.</p>
2431 message, "Client does not support authentication protocol requested
2432 by server; consider upgrading MySQL client"</a></h5>
2434 <p> You tried to access MySQL with an old MySQL client library. The version of
2435 your MySQL client library can be checked in your phpinfo() output.
2436 In general, it should have at least the same minor version as your server
2440 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2441 changed the authentication hash and your PHP is trying to use the old method.
2443 with the proper client library to match your MySQL installation. Your
2444 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2445 More information (and several workarounds) are located in the
2447 </p>
2451 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2452 capital letter in its name it is changed to lowercase as it should. But
2453 if I try to DROP this table MySQL is unable to find the corresponding
2454 file.</a></h4>
2456 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2457 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2458 directive.</p>
2462 script seems not to know the font face I'm using!</a></h4>
2464 <p> The "FPDF" library we're using for this feature requires some
2465 special files to use font faces.<br />
2467 these files.</p>
2471 check PHP Configuration".</a></h4>
2473 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2474 "MySQL extension". This extension may be part of the PHP
2475 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2476 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2477 to load the extension but failed.<br /><br />
2479 Usually, the problem is solved by installing a software package called
2480 "PHP-MySQL" or something similar.</p>
2485 and I cannot log in using cookie auth.</a></h4>
2487 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2491 so I cannot upload.</a></h4>
2493 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2494 parameter is not set to "on".</p>
2498 a new table the table and field names are changed to lowercase!</a></h4>
2500 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2501 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2502 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2503 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2504 directory and add the following line to the group [mysqld]:</p>
2506 <pre>set-variable = lower_case_table_names=0</pre>
2508 <p> Next, save the file and restart the MySQL service. You can always check the
2509 value of this directive using the query</p>
2511 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2515 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2518 </p>
2522 and I get problems, such as undefined variables when I run a
2525 <p> A tip from Jose Fandos: put a comment on the following two lines
2526 in httpd.conf, like this:</p>
2528 <pre>
2529 # mod_gzip_item_include file \.php$
2531 </pre>
2533 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2534 PHP scripts. Of course you have to restart Apache.</p>
2539 I get the error "No input file specified" when trying to
2540 run phpMyAdmin.</a></h4>
2542 <p> This is a permission problem. Right-click on the phpmyadmin folder
2543 and choose properties. Under the tab Security, click on "Add"
2544 and select the user "IUSR_machine" from the list. Now set his
2545 permissions and it should work.</p>
2549 db_details_structure.php with plenty of tables).</a></h4>
2552 GZIP output buffering is enabled. If you turn off it (by
2554 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2555 PHP 5.0.0.</p>
2559 message 'Errorcode: 13'. What does this mean?</a></h4>
2561 <p> This can happen due to a MySQL bug when having database / table names with
2562 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2563 To fix this, turn off this directive, convert all database and table names
2564 to lower case and turn it on again. Alternatively, there's a bug-fix
2565 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2569 and the fields are duplicated.</a></h4>
2571 <p> It is possible to configure Apache in such a way that PHP has problems
2572 interpreting .php files.</p>
2574 <p> The problems occur when two different (and conflicting) set of directives
2575 are used:</p>
2577 <pre>
2578 SetOutputFilter PHP
2579 SetInputFilter PHP
2580 </pre>
2582 <p> and</p>
2584 <pre>AddType application/x-httpd-php .php</pre>
2586 <p> In the case we saw, one set of directives was in
2587 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2588 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2589 The recommended way is with <tt>AddType</tt>, so just comment out
2590 the first set of lines and restart Apache:</p>
2592 <pre>
2593 #SetOutputFilter PHP
2594 #SetInputFilter PHP
2595 </pre>
2600 <p> This problem is known to happen when the server is running Turck MMCache
2601 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2606 <p> Yes.<br />
2607 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2608 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2609 <tt>error_reporting</tt> settings.
2610 </p>
2613 <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>
2615 <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>
2618 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2619 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2620 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2621 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2622 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2623 enabled.) Click <tt>OK</tt>.</li>
2624 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2625 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2626 </ol>
2630 PHP 5.0.4 on 64-bit systems?</a></h4>
2632 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2633 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2639 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2640 Table and script parts are optional. If you want
2641 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2642 some configuration. Following lines apply only for <a
2644 that you have enabled some features within global configuration. You need
2645 <code>Options FollowSymLinks</code> and <code>AllowOverride
2646 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2647 you need mod_rewrite to be enabled. Then you just need to create following
2648 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2649 (don't forget to change directory name inside of it):</p>
2651 <pre>
2652 RewriteEngine On
2653 RewriteBase /path_to_phpMyAdmin
2654 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2655 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2656 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2657 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2658 </pre>
2661 <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>
2663 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2664 following rewrite rule:</p>
2666 <pre>
2667 RewriteEngine On
2668 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2669 </pre>
2673 </h4>
2674 <p>
2675 There can be many explanations to this and a look at your server's
2676 error log file might give a clue.
2677 </p>
2681 password encryption in cookie auth doesn't work.</a></h4>
2683 <p> If your cluster consist of different architectures, PHP code used for
2684 encryption/decryption won't work correct. This is caused by use of
2685 pack/unpack functions in code. Only solution is to use mcrypt extension
2686 which works fine in this case.</p>
2692 headers already sent by ..." is displayed, what's the problem?</a></h4>
2694 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2695 (I.E. no blank lines, no spaces, no characters...) neither before the
2696 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2697 tag at the end.</p>
2702 <p> Either there is an error with your PHP setup or your username/password is
2703 wrong. Try to make a small script which uses mysql_connect and see if it
2704 works. If it doesn't, it may be you haven't even compiled MySQL support
2705 into PHP.</p>
2709 connect to local MySQL server through socket '/tmp/mysql.sock'
2710 (111) ..." is displayed. What can I do?</a></h4>
2712 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2714 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2715 In your <i>php.ini</i> you will find a line</p>
2717 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2719 <p> change it to</p>
2721 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2723 <p> Then restart apache and it will work.</p>
2725 <p> Here is a fix suggested by Brad Ummer:</p>
2727 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2728 To do this, telnet to your server and go to the MySQL bin directory. In
2729 this directory there should be a file named <i>mysqladmin</i>. Type
2730 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2731 info about your MySQL server, including the socket
2732 (<i>/tmp/mysql.sock</i>, for example).</li>
2733 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2734 phpMyAdmin, you need to complete the socket information in the
2735 <i>config.inc.php</i>.<br />
2736 For example:
2738 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2739 <br /><br />
2741 Please also make sure that the permissions of this file allow to be readable
2742 by your webserver (i.e. '0755').</li>
2743 </ul>
2745 <p> Have also a look at the
2747 corresponding section of the MySQL documentation</a>.</p>
2751 what can I do?</a></h4>
2754 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2755 sometime.<br />
2756 Also have a look at your PHP version number: if it contains "4.0b..."
2757 it means you're running a beta version of PHP. That's not a so good idea,
2758 please upgrade to a plain revision.</p>
2762 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2763 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2765 <p> Check the value you set for the
2767 directive in the phpMyAdmin configuration file.</p>
2771 password: YES)"-error when trying to access a MySQL-Server on a
2772 host which is port-forwarded for my localhost.</a></h4>
2774 <p> When you are using a port on your localhost, which you redirect via
2775 port-forwarding to another host, MySQL is not resolving the localhost
2776 as expected.<br />
2777 Erik Wasser explains: The solution is: if your host is "localhost"
2778 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2779 connection for speeding up things. And that doesn't work in this configuration
2780 with port forwarding.<br />
2786 <p> Themes are configured with
2790 <br />
2792 should not delete the directory "original" or its underlying
2793 structure, because this is the system theme used by phpMyAdmin.
2794 "original" contains all images and styles, for backwards
2795 compatibility and for all themes that would not include images or css-files.
2796 <br /><br />
2799 is enabled, you can select your favorite theme on the main page. Your
2800 selected theme will be stored in a cookie.<br /><br /></p>
2802 <p> To create a theme:</p>
2804 <ul><li>make a new subdirectory (for example "your_theme_name") under
2806 (by default <tt>themes</tt>)</li>
2807 <li>copy the files and directories from "original" to
2808 "your_theme_name"</li>
2809 <li>edit the css-files in "your_theme_name/css"</li>
2810 <li>put your new images in "your_theme_name/img"</li>
2811 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2812 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2813 contain your chosen theme name, that will be visible in user interface</li>
2814 <li>make a new screenshot of your theme and save it under
2815 "your_theme_name/screen.png"</li>
2816 </ul>
2818 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2819 theme verbose name, theme generation and theme version. These versions and
2820 generations are enumerated from 1 and do not have any direct dependence on
2821 phpMyAdmin version. Themes within same generation should be backwards
2822 compatible - theme with version 2 should work in phpMyAdmin requiring
2823 version 1. Themes with different generation are incompatible.</p>
2825 <p> If you do not want to use your own symbols and buttons, remove the
2826 directory "img" in "your_theme_name". phpMyAdmin will
2827 use the default icons and buttons (from the system-theme "original").
2828 </p>
2832 what can I do?</a></h4>
2834 <p> Here are a few points to check:</p>
2836 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2838 directive empty. See also
2840 </li>
2841 <li>Maybe you have a broken PHP installation or you need to upgrade
2842 your Zend Optimizer. See
2844 http://bugs.php.net/bug.php?id=31134</a>.
2845 </li>
2846 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2847 set to the default (200) or another low value, you could get this
2848 error if your table has a high number of columns. Adjust this setting
2849 accordingly. (Thanks to Klaus Dorninger for the hint).
2850 </li>
2851 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2852 of ";" will cause this error. Replace it with "&;".
2853 </li>
2854 </ul>
2861 who logged out can not log in again in with the same nick.</a></h4>
2863 <p> This is related to the authentication mechanism (protocol) used by
2864 phpMyAdmin. To bypass this problem: just close all the opened
2865 browser windows and then go back to phpMyAdmin. You should be able to
2866 log in again.</p>
2870 limit error or a time limit error.</a></h4>
2872 <p> Compressed dumps are built in memory and because of this are limited to
2873 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2874 using
2876 (enabled by default). Zip exports can not be handled this way, so if you need
2877 Zip files for larger dump, you have to use another way.</p>
2881 or alter a table.</a></h4>
2883 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
2887 bundled with the MySQL server distribution.</a></h4>
2889 <p> The problem is that mysqldump creates invalid comments like this:</p>
2891 <pre>
2892 -- MySQL dump 8.22
2893 --
2894 -- Host: localhost Database: database
2895 ---------------------------------------------------------
2896 -- Server version 3.23.54
2897 </pre>
2899 <p> The invalid part of the code is the horizontal line made of dashes that
2900 appears once in every dump created with mysqldump. If you want to run your
2901 dump you have to turn it into valid MySQL. This means, you have to add a
2902 whitespace after the first two dashes of the line or add a # before it:
2903 <br />
2904 <code>
2905 -- -------------------------------------------------------<br />
2906 </code>
2907 or<br />
2908 <code>
2909 #---------------------------------------------------------
2910 </code>
2911 </p>
2918 <p> Please note that you should not use the separating string multiple times
2919 without any characters between them, or at the beginning/end of your table
2920 name. If you have to, think about using another TableSeparator or disabling
2921 that feature</p>
2926 <p> In Relation view, being able to choose a table in another database,
2927 or having more than one index field in the foreign key.<br /><br/>
2928 In Query-by-example (Query), automatic generation of the query
2929 LEFT JOIN from the foreign table.<br /><br/>
2930 </p>
2934 I get series of errors like "Warning: unable to parse url". How
2935 can this be fixed?</a></h4>
2936 <p>
2937 Your table neither have a primary key nor an unique one, so we must use a
2938 long expression to identify this row. This causes problems to parse_url
2939 function. The workaround is to create a primary or unique key.
2940 <br />
2941 </p>
2945 a MIME-Transformation onto!</a></h4>
2947 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
2948 nested forms can be put inside the table where phpMyAdmin displays the results.
2949 You can, however, use any form inside of a table if keep the parent
2950 form-container with the target to tbl_row_delete.php and just put your own
2951 input-elements inside. If you use a custom submit input field, the form will
2952 submit itself to the displaying page again, where you can validate the
2953 $HTTP_POST_VARS in a transformation.
2955 For a tutorial on how to effectively use transformations, see our
2957 on the official phpMyAdmin-homepage.</p>
2961 MySQL server</a></h4>
2963 <p> When MySQL is running in ANSI-compatibility mode, there are some major
2966 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
2967 the quote-character (") is interpreted as an identifier quote character and
2968 not as a string quote character, which makes many internal phpMyAdmin
2970 statements. There is no workaround to this behaviour. News to this item will
2971 be posted in Bug report
2972 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
2973 </p>
2977 more that one column with the same value
2978 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
2979 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
2981 <p> Please make sure that your table has a primary key, so that phpMyAdmin
2982 can use it for the Edit and Delete links.</p>
2987 <p> phpMyAdmin uses a quick method to get the row count, and this method
2988 only returns an approximate count in the case of InnoDB tables. See
2990 a way to modify those results, but
2991 this could have a serious impact on performance.</p>
2996 <p> The number of records in queries containing COUNT and GROUP BY is
2997 not correctly calculated. Also, sorting results of a query like
3002 containing an hyphen.
3003 </a></h4>
3004 <p>
3005 The tests I have made with current MySQL 4.1.11 API shows that the
3006 API does not accept this syntax for the USE command. Enclosing the
3007 db name with backquotes works. For further confusion, no backquotes
3008 are needed with command-line mysql.
3009 </p>
3011 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3014 <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
3015 need to install it for each customer.
3016 </a></h4>
3017 <p>
3018 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3019 your users. The development of this feature was kindly sponsored by
3020 NetCologne GmbH.
3021 This requires a properly setup MySQL user management and phpMyAdmin
3022 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3024 </p>
3028 access.
3029 </a></h4>
3030 <p>
3031 This depends on your system.<br />
3032 If you're running a server which cannot be accessed by other people, it's
3033 sufficient to use the directory protection bundled with your webserver
3035 If other people have telnet access to your server, you should use
3036 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3037 <br /><br />
3038 Suggestions:
3039 </p>
3040 <ul>
3041 <li>
3043 </li>
3044 <li>
3045 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3046 is a user whose password is only known to you, and apache is the
3047 group under which Apache runs.
3048 </li>
3049 <li>
3050 You should use PHP safe mode, to protect from other users that try
3052 </li>
3053 </ul>
3058 </a></h4>
3059 <p>
3064 </p>
3067 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3068 authentication.
3069 </a></h4>
3073 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3074 and/or
3076 are wrong.</li>
3078 <li>You have already setup a security mechanism for the
3079 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3080 phpMyAdmin's authentication, so remove it.</li>
3081 </ul>
3088 and put the privileges you want. For example,
3090 would let a user create/manage his/her database(s).</p>
3095 <p> If you have existing rules from an old .htaccess file, you can take them
3098 be a major benefit here if your installation is suited to using it. Then
3099 you can just add those updated lines into the
3103 <p> If you want a pre-made sample, you can try this fragment. It stops the
3104 'root' user from logging in from any networks other than the private
3107 <pre>
3108 //block root from logging in except from the private networks
3109 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3110 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3111 'deny root from all',
3112 'allow root from localhost',
3116 );
3117 </pre>
3122 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3123 different than the one set in your
3125 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3126 while a domain name is defined in the config file.</p>
3132 when trying to create a table with more than 14 fields.
3133 </a></h4>
3134 <p>
3135 We could reproduce this problem only under Win98/98SE. Testing under
3136 WinNT4 or Win2K, we could easily create more than 60 fields.
3137 <br />
3138 A workaround is to create a smaller number of fields, then come back to
3139 your table properties and add the other fields.
3140 </p>
3144 <p>
3145 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3146 with each script/website that use forms.<br />
3147 Upgrade or downgrade your Xitami server.
3148 </p>
3151 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3152 <p>
3153 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3154 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3155 don't seem to work.<br />
3157 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3158 the user's temporary directory, so they must be moved before closing
3159 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3162 </p>
3166 Explorer never stores the cookies.
3167 </a></h4>
3168 <p>
3169 MS Internet Explorer seems to be really buggy about cookies, at least till
3171 in this area!
3172 <br />
3173 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3174 work!
3175 </p>
3179 rows.
3180 </a></h4>
3181 <p>
3183 </p>
3186 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3187 when trying to modify a row in a table with many fields, or with a text field
3188 </a></h4>
3189 <p>
3190 Your table neither have a primary key nor an unique one, so we must use a
3191 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
3192 those browsers, and this not happen in Netscape, for example. The
3193 workaround is to create a primary or unique key, or use another browser.
3194 <br />
3195 </p>
3199 page.
3200 </a></h4>
3201 <p>
3202 Some browsers support right-clicking into the frame you want to refresh,
3203 just do this in the right frame.<br />
3204 </p>
3208 query box.
3209 </a></h4>
3210 <p>
3211 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3212 Mozilla versions.<br />
3213 </p>
3217 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3218 </a></h4>
3219 <p>
3220 This is a Mozilla bug (see bug #26882 at
3222 </p>
3227 </a></h4>
3228 <p>
3229 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3230 data in octet-stream mode. Since we can't detect the specific Netscape
3231 version, we cannot workaround this bug.
3232 </p>
3236 wrong.</a></h4>
3238 <p> Please ensure that you have set your browser's character set to the one of the
3239 language file you have selected on phpMyAdmin's start page.
3240 Alternatively, you can try the auto detection mode that is supported by the
3241 recent versions of the most browsers.</p>
3244 <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
3247 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3248 Netscape and Mozilla do not have this problem.</p>
3251 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3252 I cannot manage two servers: I log in to the first one, then the other one,
3253 but if I switch back to the first, I have to log in on each operation.</a></h4>
3259 but nothing happens after that, only a blank screen.</a></h4>
3262 bug in Opera6, because it is not able to interpret frameset definitions
3263 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3264 Opera7 at least.</p>
3273 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3278 address and you are starting
3280 containing a domain name, or the reverse situation.</li>
3281 <li>Security settings in IE and/or Microsoft Security Center are
3282 too high, thus blocking scripts execution.</li>
3283 <li>The Windows Firewall is blocking Apache and MySQL. You must
3287 </ul>
3290 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3291 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3292 installed in their Firefox is causing the problem.</p>
3299 </a></h4>
3300 <p>
3301 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3302 specifying a wrong field-type.<br />
3303 Common errors include:
3304 </p>
3305 <ul>
3308 </ul>
3309 <p>
3310 Also, look at the syntax chapter in the MySQL manual to confirm that your
3311 syntax is correct.
3312 </p>
3316 phpMyAdmin generates only one index with those 2 fields.
3317 </a></h4>
3318 <p>
3320 index. If you want two indexes, create the first one when creating the
3321 table, save, then display the table properties and click the Index link to
3322 create the other index.
3323 </p>
3327 <p>
3328 Since version 2.2.3, you have a checkbox for each field that can be null.
3330 field's value. Since version 2.5.5, you have to use the checkbox to get
3332 a literal NULL in the field, and not a NULL value (this works in PHP4).
3333 </p>
3338 <p> Click on a database or table name in the left frame, the properties will be
3340 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3341 statements that can be used to recreate your database/table.
3342 <br /><br />
3344 transmit the resulting dump to your station. Depending on your PHP
3345 configuration, you will see options to compress the dump. See also the
3347 configuration variable.<br /><br />
3350 this document.</p>
3355 </a></h4>
3357 <p> Click on a database name in the left frame, the properties will be
3359 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3361 the path to your dump filename, or use the Browse button. Then click Go.
3362 <br /><br />
3364 that you upgrade to take advantage of the new features.
3365 <br /><br />
3367 in this document.
3368 </p>
3373 <p> Here is an example with the tables persons, towns and countries, all
3375 table, create it as explained in the configuration section. Then create the
3376 example tables:</p>
3378 <pre>
3379 CREATE TABLE REL_countries (
3380 country_code char(1) NOT NULL default '',
3381 description varchar(10) NOT NULL default '',
3382 PRIMARY KEY (country_code)
3383 ) TYPE=MyISAM;
3385 INSERT INTO REL_countries VALUES ('C', 'Canada');
3387 CREATE TABLE REL_persons (
3388 id tinyint(4) NOT NULL auto_increment,
3389 person_name varchar(32) NOT NULL default '',
3391 country_code char(1) NOT NULL default '',
3392 PRIMARY KEY (id)
3393 ) TYPE=MyISAM;
3395 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3396 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3398 CREATE TABLE REL_towns (
3400 description varchar(30) NOT NULL default '',
3401 PRIMARY KEY (town_code)
3402 ) TYPE=MyISAM;
3404 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3405 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3406 </pre>
3412 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3416 </ul>
3424 <li>In the fields row, choose persons.person_name and click the
3426 <li>Do the same for towns.description and countries.descriptions in the
3429 the correct joins have been generated</li>
3431 </ul>
3435 <p>
3436 Starting from the previous example, create the pma_table_info as explained
3437 in the configuration section, then browse your persons table,
3438 and move the mouse over a town code or country code.
3439 <br /><br />
3440 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3441 enables: drop-down list of possible values.
3442 </p>
3445 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3446 <p>
3449 <br /><br />
3450 Then you need to think about your schema layout. Which tables will go on
3451 which pages?
3452 </p>
3453 <ul>
3459 page and click Go. If you like, you
3461 linked tables onto the new page.</li>
3462 <li>Select the name of the new page (making sure the Edit radio button
3463 is selected) and click Go.</li>
3465 Coordinates are relative; your diagram will
3466 be automatically scaled to fit the page. When initially placing tables
3467 on the page, just pick any coordinates -- say, 50x50. After clicking
3469 position the element correctly.</li>
3471 first be sure to click the Save
3472 button beneath the list of tables and coordinates, to save any changes
3473 you made there. Then scroll all the way down, select the
3475 you want, and click Go.</li>
3476 <li>Internet Explorer for Windows may suggest an incorrect filename when
3481 browsers on Windows, do not have this problem.</li>
3482 </ul>
3486 columns!</a></h4>
3488 <p> No, it's MySQL that is doing
3494 underscores in the database name?</a></h4>
3496 <p> If you do not put a backslash before the underscore, this is a wildcard
3499 john2db ...<br /><br />
3501 If you put a backslash before the underscore, it means that the database
3502 name will have a real underscore.</p>
3506 statistics pages?</a></h4>
3517 if it already exists during the import. It does NOT drop the table after
3518 your export, it only affects the import file.</li>
3520 Otherwise, you may get an error if the table name exists but has a
3521 different structure.</li>
3523 (if any) will be included in backup.</li>
3525 field and table names formed with special characters are protected.</li>
3527 types set in the pmadb in the dump as
3529 </li>
3530 </ul>
3535 command, for better documentation (but resulting file is bigger).</li>
3537 once the INSERT verb and the table name.</li>
3540 </li>
3542 more info is provided in the
3544 but basically with this selected, invalid values are adjusted and
3545 inserted rather than causing the entire statement to fail.</li>
3546 </ul>
3550 in its name.</a></h4>
3553 is the normal way to reference a database and table name. Worse, MySQL
3554 will usually let you create a database with a dot, but then you cannot
3555 work with it, nor delete it.</p>
3568 for usage.<br />
3569 On a more recent pear version, I had problems with the state of Net_DIME
3570 being beta, so this single command
3572 needed modules.<br />
3573 If you use the Validator, you should be aware that any
3575 submit will be stored anonymously (database/table/column names,
3576 strings, numbers replaced with generic values). The Mimer
3579 We utilize it as free SOAP service.</p>
3583 it, but MySQL says "BLOB column '...' used in key specification without
3586 <p> The right way to do this, is to create the field without any indexes,
3588 dialog. On this page, you will be able to choose your BLOB field, and
3589 set a size to the index, which is the condition to create an index on
3590 a BLOB field.</p>
3594 editing fields?</a></h4>
3596 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3597 with many editing fields (table structure changes, row editing, etc.)
3598 (must be enabled in configuration - see.
3600 You can also have a look at the directive
3602 ('vertical') and see if this eases up editing for you.</p>
3606 WTF is this feature then useful for?</a></h4>
3608 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3609 on them. Otherwise you could just put a comment on the field. Because entering
3610 your own mimetype will cause serious syntax checking issues and validation,
3611 this introduces a high-risk false-user-input situation. Instead you have to
3612 initialize mimetypes using functions or empty mimetype definitions.<br />
3613 Plus, you have a whole overview of available mimetypes. Who knows all those
3614 mimetypes by heart so he/she can enter it at will?</p>
3618 can't I see any bookmarks below the query box? What is this variable for?
3619 </a></h4>
3621 <p> Any query you have executed can be stored as a bookmark on the page where the
3622 results are displayed. You will find a button labeled 'Bookmark this query'
3623 just at the end of the page.<br />
3624 As soon as you have stored a bookmark, it is related to the database you run
3625 the query on. You can now access a bookmark dropdown on each page, the query
3626 box appears on for that database.<br /><br />
3628 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3632 aware of that you HAVE to create a valid query, otherwise your query won't be
3633 even able to be stored in the database.<br />
3635 for your query will remain the way it is, but will be stripped of the /**/
3636 chars. So you can use:<br /><br />
3640 which will be expanded to<br /><br />
3644 in your query, where VARIABLE is the string you entered in the input box. If
3645 an empty string is provided, no replacements are made.<br /><br />
3647 A more complex example. Say you have stored this query:<br /><br />
3649 <br /><br />
3652 the full query will be:<br /><br />
3655 <br /><br />
3659 spaces inserted there
3660 will be later also inserted as spaces in your query and may lead to unexpected
3661 results especially when
3663 Your initial query which is going to be stored as a bookmark has to yield at
3664 least one result row so
3665 you can store the bookmark. You may have that to work around using well
3669 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3670 include exported table?</a></h4>
3672 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3673 document should look like following one (assuming you have table
3676 <pre>
3677 \documentclass{article} % or any class you want
3678 \usepackage{longtable} % for displaying table
3679 \begin{document} % start of document
3680 \include{table} % including exported table
3681 \end{document} % end of document
3682 </pre>
3686 access them.
3687 </a></h4>
3690 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3691 enable users to see all the database names.
3694 So if your users do not need those privileges, you can remove them and their
3695 databases list will shorten.</p>
3699 possible values for a field, based on some foreign table?</a></h4>
3701 <p> You have to setup appropriate links between the tables, and also
3705 foreign table, a drop-down list of values will be available.
3706 You will see two lists of values, the first list containing the key
3707 and the display field, the second list containing the display field
3708 and the key. The reason for this is to be able to type the first
3709 letter of either the key or the display field.<br /><br />
3711 For 200 values or more, a distinct window will appear, to browse foreign
3712 key values and choose one.</p>
3716 automatically when entering Browse mode for a table?</a></h4>
3718 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3719 </p>
3723 Excel files, how can I enable that?</a></h4>
3725 <p> Current version does support direct export to Microsoft Excel and Word
3726 versions 2000 and newer. If you need export older versions, you can use
3728 which works out of the box or you can
3730 several problems, most important are limitation of cell content to 255
3731 chars and no support for charsets, so think carefully whether you want to
3732 enable this.</b>. For enabling this you need to set
3736 module Spreadsheet_Excel_Writer into php include path. The
3737 installation can be done by following command:</p>
3739 <pre>
3740 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3741 </pre>
3743 <p> First part of switches set we want to install beta version of that module
3744 (no stable version available yet) and then we tell pear we want to satisfy
3745 dependencies.</p>
3747 <p> If you are running in PHP safe mode, you will have to set
3750 modules are located, for example:</p>
3752 <pre>
3753 safe_mode_include_dir = /usr/local/lib/php
3754 </pre>
3758 <pre>
3759 cd phpMyAdmin
3760 mkdir tmp
3761 chmod o+rwx tmp
3762 </pre>
3766 what happens to my column comments stored in pmadb?</a></h4>
3768 <p> Automatic migration of a table's pmadb-style column comments to the native
3769 ones is done whenever you enter Structure page for this table.</p>
3776 <p> Our Bug Tracker is located at
3778 under the Bugs section.<br /><br />
3780 But please first discuss your bug with other users:<br />
3786 existing language, where do I start?</a></h4>
3788 <p> Always use the current SVN version of your language file.
3790 don't know how to get the SVN version, please ask one of the developers.
3791 <br />
3792 Please note that we try not to use HTML entities like &eacute; in
3793 the translations, since we define the right character set in the file.
3794 With HTML entities, the text on JavaScript messages would not
3795 display correctly.
3796 However there are some entities that need to be there, for quotes
3797 ,non-breakable spaces, ampersands, less than, greater than.<br />
3798 You can then put your translations, as a zip file to avoid losing special
3799 characters, on the sourceforge.net translation tracker.<br />
3800 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3801 list, because this is where we ask for translations of new messages.</p>
3805 phpMyAdmin. How should I proceed?</a></h4>
3811 </li>
3813 <li>generate patch with your changes:
3815 </li>
3818 tracker of the phpMyAdmin project</a>.
3819 </li>
3820 </ol>
3822 <p> Write access to the SVN tree is granted only to experienced developers who
3823 have already contributed something useful to phpMyAdmin.<br />
3829 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3831 <p> Please refer to
3832 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3833 </p>
3835 <!-- DEVELOPERS -->
3838 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3839 great features have been written by other people and you too can help to
3840 make phpMyAdmin a useful tool.</p>
3842 <p> If you're planning to contribute source, please read the following
3843 information:</p>
3849 it free from other code.<br />
3850 Commonly used functions should be added to
3853 <li>Obviously, you're free to use whatever coding style you want. But
3854 please try to keep your code as simple as possible: beginners are
3855 using phpMyAdmin as an example application.<br />
3856 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3857 compliant on one hand, they fit the
3860 coding standards</a>
3861 on the other hand. Please pay attention to this.</li>
3862 <li>Please try to keep up the file-naming conventions. Table-related stuff
3865 <li>Please don't use verbose strings in your code, instead add the string
3870 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3871 better debug and profile their code.<br />
3872 Please see the
3874 options for more information.<br />
3875 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3876 lost during its re-entry into Earth's atmosphere and in memory of the
3877 brave men and women who gave their lives for the people of Earth.</li>
3878 </ul>
3880 <!-- CREDITS -->
3883 <pre>
3884 phpMyAdmin - Credits
3885 ====================
3887 CREDITS, in chronological order
3888 -------------------------------
3891 * creator of the phpmyadmin project
3895 * multi-language version
3896 * various fixes and improvements
3898 * current project maintainer
3901 * started SourceForge phpMyAdmin project in March 2001
3902 * sync'ed different existing CVS trees with new features and bugfixes
3903 * multi-language improvements, dynamic language selection
3904 * current project maintainer
3905 * many bugfixes and improvements
3908 * rewrote and optimized javascript, DHTML and DOM stuff
3909 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
3910 generate XHTML1.0 and CSS2 compliant codes
3911 * improved the language detection system
3912 * many bugfixes and improvements
3915 * database maintenance controls
3916 * table type code
3918 * DB-based configuration (Not completed)
3921 * many bugfixes and improvements
3924 * bookmarks feature
3925 * multiple dump feature
3926 * gzip dump feature
3927 * zip dump feature
3930 * various fixes
3931 * moderator of the phpMyAdmin former users forum at phpwizard.net
3937 * rewrote and fix dump code
3938 * bugfixes
3941 * rewrote dump code for PHP4
3942 * mySQL table statistics
3943 * bugfixes
3946 * main author of the version 2.1.0.1
3947 * bugfixes
3951 * abstract database interface (PMA_DBI) with MySQLi support
3952 * privileges administration
3954 * various features and fixes
3955 * German language file updates
3958 * automatic joins in QBE
3959 * links column in printview
3960 * Relation view
3963 * enhanced index creation/display feature
3964 * feature to use a different charset for HTML than for MySQL
3965 * improvements of export feature
3966 * various features and fixes
3967 * Czech language file updates
3970 (http://sf.net/projects/phpmysqlformgen/)
3971 * suggested the patch for multiple table printviews
3974 * built the patch for vertical display of table rows
3975 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
3976 * Improvement of column/db comments
3977 * (MIME)-Transformations for columns
3978 * Use custom alias names for Databases in left frame
3979 * hierarchical/nested table display
3980 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
3981 * new icon sets
3982 * vertical display of column properties page
3983 * some bugfixes, features, support, German language additions
3986 * japanese kanji encoding conversion feature
3989 * the Cookie authentication mode
3992 * table relation-links feature
3995 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
3996 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
3997 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4003 * phpMyAdmin logo (until June 2004)
4006 * blowfish library from the Horde project
4009 * mysqli support
4010 * many bugfixes and improvements
4013 * redesign for 2.6.0
4014 * phpMyAdmin sailboat logo (June 2004)
4017 * Representation at conferences
4020 * interface improvements
4021 * various bugfixes
4023 And also to the following people who have contributed minor changes,
4024 enhancements, bugfixes or support for a new language since version 2.1.0:
4026 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4027 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4028 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4029 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4031 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4032 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4033 Luís V., Martijn W. van der Lee,
4034 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4038 Original Credits of Version 2.1.0
4039 ---------------------------------
4041 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4042 to create a web-based interface to MySQL using PHP3. Although I have not
4043 used any of his source-code, there are some concepts I've borrowed from
4044 him. phpMyAdmin was created because Peter told me he wasn't going to
4045 further develop his (great) tool.
4046 Thanks go to
4048 code for the check when dropping a table or database. He also suggested
4049 that you should be able to specify the primary key on tbl_create.php3. To
4050 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4051 well as a bug-report. Plus many smaller improvements.
4053 were introduced in 1.3.0 (including quite significant ones like the
4054 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4055 bug-fixes and help.
4057 language-independent by outsourcing the strings to a separate file. He
4058 also contributed the French translation.
4060 tbl_select.php3, a feature to display only some fields from a table.
4062 functions in tbl_change.php3. He also added the
4065 servers and is a regular contributor for bug-fixes.
4067 features for 2.0.6.
4068 The following people have contributed minor changes, enhancements, bugfixes
4069 or support for a new language:
4070 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4071 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4072 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4073 G. Wieggers.
4075 And thanks to everyone else who sent me email with suggestions, bug-reports
4076 and or just some feedback.
4077 </pre>
4083 <ul>
4085 - the default name of Apache's directory-level configuration file.</li>
4089 - a software application that enables a user to display and interact with
4090 text, images, and other information typically located on a web page at a
4091 website on the World Wide Web.</li>
4093 - a free software/open source data compression algorithm and program
4094 developed by Julian Seward.</li>
4096 - an important World Wide Web technology that enables a client web browser
4097 to request data from a program executed on the Web server.</li>
4099 - a log or record of changes made to a project.</li>
4101 - a computer system that accesses a (remote) service on another computer
4102 by some kind of network.</li>
4104 - a set of data values of a particular simple type, one for each row of
4105 the table.</li>
4107 - a packet of information sent by a server to a World Wide Web browser
4108 and then sent back by the browser each time it accesses that server.</li>
4110 - Comma-seperated values</li>
4113 - an organized collection of data.</li>
4116 - a PHP module that extends PHP with additional functionality.</li>
4118 - a list of commonly asked question and there answers.</li>
4120 - one part of divided data/columns.</li>
4122 - a field or group of fields in a database record that point to a key
4123 field or group of fields forming a key of another database record in some
4124 (usually different) table.</li>
4126 - the free PDF library</li>
4128 GD Graphics Library</a> - a library by Thomas Boutell and others for
4129 dynamically manipulating images.</li>
4132 - gzip is short for GNU zip, a GNU free software file compression
4133 program.</li>
4135 - any machine connected to a computer network, a node that has a hostname.</li>
4137 - the unique name by which a network attached device is known on a network.</li>
4139 (HyperText Transfer Protocol)</a>
4140 - the primary method used to transfer or convey information on the World
4141 Wide Web.</li>
4144 additional security measures.</li>
4145 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4146 - a set of Internet-based services for servers using Microsoft Windows.</li>
4148 - a feature that allows quick access to the rows in a table.</li>
4150 - a data-oriented protocol used by source and destination hosts for
4151 communicating data across a packet-switched internetwork.</li>
4153 - a unique number that devices use in order to identify and communicate
4154 with each other on a network utilizing the Internet Protocol standard.</li>
4156 (Internet Server Application Programming Interface)</a>
4157 - the API of Internet Information Services (IIS).</li>
4159 - a business or organization that offers users access to the Internet and related services.</li>
4161 - a most commonly used standard method of lossy compression for
4162 photographic images.</li>
4168 - line of personal computers is designed, developed, manufactured, and
4169 marketed by Apple Computer.</li>
4170 <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>
4171 - the operating system which is included with all currently shipping Apple
4172 Macintosh computers in the consumer and professional markets.</li>
4174 - a cryptographic library.</li>
4176 - the MCrypt PHP extension.</li>
4177 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4178 - an Internet Standard for the format of e-mail.</li>
4180 - some sort of extension for the Apache Webserver.</li>
4182 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4183 Management System (DBMS).</li>
4185 - the improved MySQL client PHP extension.</li>
4187 - the MySQL client PHP extension.</li>
4189 - open standard for office documents.</li>
4190 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4191 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4193 (Portable Document Format)</a>
4194 - a file format developed by Adobe Systems for representing two
4195 dimensional documents in a device independent and resolution independent
4196 format.</li>
4198 - the PHP Extension and Application Repository.</li>
4200 - the perl-compatible regular expression functions for PHP</li>
4202 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4203 programming language used mainly for developing server-side applications
4204 and dynamic web content, and more recently, a broader range of software
4205 applications.</li>
4207 - a connection through which data is sent and received.</li>
4209 - Request for Comments (RFC) documents are a series of memoranda
4210 encompassing new research, innovations, and methodologies applicable to
4211 Internet technologies.</li>
4215 - represents a single, implicitly structured data item in a table.</li>
4217 - a computer system that provides services to other computing
4218 systems over a network.</li>
4219 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4220 - handlers for different table types</li>
4222 - a form of inter-process communication.</li>
4224 Sockets Layer)</a>
4225 - a cryptographic protocol which provides secure communication on the Internet.</li>
4227 - Structured Query Language</li>
4229 - a set of data elements (cells) that is organized, defined and stored as
4230 horizontal rows and vertical columns where each item can be uniquely
4231 identified by a label or key or by it?s position in relation to other items.</li>
4234 - a type of archive file format: the Tape ARchive format.</li>
4236 - one of the core protocols of the Internet protocol suite.</li>
4240 - a sequence of characters, conforming to a standardized format, that is
4241 used for referring to resources, such as documents and images on the
4242 Internet, by their location.</li>
4244 - A computer (program) that is responsible for accepting HTTP requests
4245 from clients and serving them Web pages.</li>
4247 - a W3C-recommended general-purpose markup language for creating
4248 special-purpose markup languages, capable of describing many different
4249 kinds of data.</li>
4251 - a popular data compression and archival format.</li>
4253 - an open-source, cross-platform data compression library by Jean-loup
4254 Gailly and Mark Adler.</li>
4255 </ul>
4265 </body>
4266 </html>