| blob | 865683b6f25d671c79b81538b20d4b4839593837 |
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
683 URL</a> to use this authentication method.
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>
1209 </dt>
1212 not at the starting main (right) frame. This setting
1213 does not check MySQL commands entered directly.<br /><br />
1215 Please note that to block the usage of phpinfo() in scripts, you
1222 hard coded password value in the configuration file, end users can't
1223 be allowed to change their passwords.</dd>
1226 <dd>Defines whether to suggest a database name on the
1231 content.</dd>
1234 <dd>Defines whether navigation bar buttons and the right panel top menu
1235 contain text or symbols only. A value of TRUE displays icons, FALSE
1236 displays text and 'both' displays both icons and text.</dd>
1239 <dd>Defines whether a user should be displayed a
1243 <dd>Number of rows displayed when browsing a result set. If the result set
1250 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1254 from editing when browsing a table's content. Valid values are:
1259 </ul>
1260 </dd>
1263 <dd>Defines whether or not MySQL functions fields should be displayed in
1264 edit/insert mode.</dd>
1267 <dd>Defines which type of editing controls should be used for CHAR and
1268 VARCHAR fields. Possible values are:
1269 <ul><li>input - this allows to limit size of text to size of field in
1270 MySQL, but has problems with newlines in fields</li>
1271 <li>textarea - no problems with newlines in fields, but also no
1272 length limitations</li>
1273 </ul>
1274 Default is old behavior so input.</dd>
1280 <dd>If there are fewer items than this in the set of foreign keys, then a
1281 drop-down box of foreign keys is presented, in the style described by the
1283 setting.</dd>
1286 <dd>For the foreign key drop-down fields, there are several methods of
1287 display, offering both the key and value data. The contents of the
1288 array should be one or both of the following strings:
1294 </dt>
1295 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1296 creating a dump file</dd>
1299 </dt>
1300 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1301 compressed exports. This doesn't affect smaller dumps and allows users to
1302 create larger dumps that won't otherwise fit in memory due to php
1303 memory limit. Produced files contain more GZip/BZip2 headers, but all
1304 normal programs handle this correctly.</dd>
1308 mainframe.</dd>
1312 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1317 <dd>How many columns will be utilized to display the tables on the
1318 database property view? Default is 1 column. When setting this to a
1319 value larger than 1, the type of the database will be omitted for more
1320 display space.</dd>
1324 <dd>Defines the tab displayed by default on server view. Possible
1331 <dd>Defines the tab displayed by default on database view. Possible
1336 <dd>Defines the tab displayed by default on table view. Possible
1343 points to the MySQL documentation (type depends
1344 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1345 generated.<br />
1347 for more information about MySQL manuals and their types.</dd>
1350 <dd>Type of MySQL documentation:
1356 </ul>
1357 </dd>
1360 <dd>Defines the default language to use, if not browser-defined or
1361 user-defined.<br />
1363 this setting.</dd>
1366 <dd>Defines the default connection collation to use, if not
1367 user-defined.<br />
1372 <dd>Force: always use this language (must be defined in the
1376 <dd>Limit list of available languages to those matching the given regular
1377 expression. For example if you want only Czech and English, you should
1381 <dd>Default character set to use for recoding of MySQL queries. This must be
1382 enabled and it's described by
1384 option.<br />
1385 You can give here any character set which is in
1387 array and this is just default choice, user can select any of them.</dd>
1390 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1391 support (compiled in or module) in PHP to allow MySQL queries recoding
1392 and used language file must have it enabled (by default only these
1393 which are in Unicode, just to avoid losing some characters).<br /><br />
1396 in the Export page, to choose the character set when exporting a file.
1397 </dd>
1400 <dd>You can select here which functions will be used for character set
1401 conversion. Possible values are:
1402 <ul><li>auto - automatically use available one (first is tested
1403 iconv, then recode)</li>
1406 </ul>
1407 Default is auto.</dd>
1410 <dd>Specify some parameters for iconv used in charset conversion. See
1413 used, so that invalid characters will be transliterated.</dd>
1416 <dd>Available character sets for MySQL conversion. You can add your own (any of
1417 supported by recode/iconv) or remove these which you don't use.
1418 Character sets will be shown in same order as here listed, so if you
1419 frequently use some of these move them to the top.</dd>
1423 MIME transformations.<br />
1424 Possible values are:
1425 <ul><li>auto - automatically detect, this is a bit expensive
1427 according to your server real possibilities</li>
1430 </ul>
1431 Default is auto.
1432 </dd>
1436 </dd>
1438 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1439 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1440 </dt>
1441 <dd>The background styles used for both the frames.
1444 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1446 <dd>The style used for the pointer in the navi frame.
1455 </dd>
1459 <dd>The style used for table headers. See
1464 </dd>
1468 </dd>
1470 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1472 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1474 </dt>
1476 The former feature highlights the row over which your mouse is passing
1477 and the latter lets you visually mark/unmark rows by clicking on
1478 them.<br />
1483 <dd>You put here a valid CSS font family value, for example
1488 <dd>You put here a valid CSS font family value, for example
1502 </dt>
1504 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1506 The Char* values are used for CHAR and VARCHAR editing (if configured
1510 </dt>
1514 </dt>
1515 <dd>Defines if the whole textarea of the query box will be selected on
1516 click.</dd>
1519 </dt>
1520 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1521 editing.</dd>
1524 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1525 Can be turned off by a toggle button on the browse page.</dd>
1529 </dt>
1530 <dd>Defines the place where modify and delete links would be put when
1531 tables contents are displayed (you may have them displayed both at the
1532 left and at the right).
1538 </dt>
1540 Define which one is displayed by default. The first mode displays each
1541 row on a horizontal line, the second rotates the headers by 90
1542 degrees, so you can use descriptive headers even though fields only
1543 contain small values and still print them out. The vertical mode sorts
1544 each row on a vertical lineup.<br /><br />
1546 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1547 the rotation of the header for horizontalflipped is done via CSS. If
1548 set to 'fake' PHP does the transformation for you, but of course this
1549 does not look as good as CSS.</dd>
1553 <dd>When editing/creating new columns in a table all fields normally get
1554 lined up one field a line. (default: 'horizontal'). If you set this to
1555 'vertical' you can have each field lined up vertically beneath each
1556 other. You can save up a lot of place on the horizontal direction and
1557 no longer have to scroll.</dd>
1561 </dt>
1563 display of column comments in Browse or Property display. In browse
1564 mode, the comments are shown inside the header. In property mode,
1565 comments are displayed using a CSS-formatted dashed-line below the
1566 name of the field. The comment is shown as a tool-tip for that field.
1567 </dd>
1570 <dd>
1571 The name of the directory where
1573 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1574 are available under a drop-down box when you click the database name,
1576 <br /><br />
1578 If you want different directory for each user, %u will be replaced
1579 with username.<br /><br />
1583 compressed formats is enabled).<br /><br />
1585 This feature is useful when your file is too big to be uploaded via
1587 uploads are disabled in PHP.<br /><br />
1589 Please note that if PHP is running in safe mode, this directory must
1590 be owned by the same user as the owner of the phpMyAdmin scripts.
1591 <br /><br />
1595 alternatives.
1596 </dd>
1599 <dd>
1600 The name of the directory where docSQL files can be uploaded for
1601 import into phpMyAdmin.
1602 <br /><br />
1603 Please note that if PHP is running in safe mode, this directory must
1604 be owned by the same user as the owner of the phpMyAdmin scripts.
1605 </dd>
1608 <dd>
1609 The name of the directory where dumps can be saved.<br /><br />
1611 If you want different directory for each user, %u will be replaced
1612 with username.<br /><br />
1614 Please note that the directory has to be writable for user running
1615 webserver.<br /><br />
1617 Please note that if PHP is running in safe mode, this directory must
1618 be owned by the same user as the owner of the phpMyAdmin scripts.
1619 </dd>
1622 <dd>
1623 The name of the directory where temporary files can be stored.
1624 <br /><br />
1625 This is needed for native MS Excel export, see
1628 </dd>
1631 <dd>
1632 In this array are defined default parameters for export, names of
1633 items are similar to texts seen on export page, so you can easily
1634 identify what they mean.
1635 </dd>
1638 <dd>
1639 In this array are defined default parameters for import, names of
1640 items are similar to texts seen on import page, so you can easily
1641 identify what they mean.
1642 </dd>
1645 <dd>
1646 Repeat the headers every X cells, or 0 to deactivate.
1647 </dd>
1655 </dt>
1656 <dd>
1657 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1658 or icon is always displayed on the left panel. If JavaScript is enabled in
1659 your browser, a click on this opens a distinct query window, which is
1660 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1661 changes to display a query box.<br /><br />
1663 The size of this query window can be customized with
1665 - both integers for the size in pixels. Note that normally, those
1667 theme you are using.<br /><br />
1671 opens the query window and puts the current query
1672 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1673 query in the right panel's query box.
1674 <br /><br />
1675 The usage of the JavaScript query window is recommended if you have a
1676 JavaScript enabled browser. Basic functions are used to exchange quite
1677 a few variables, so most 4th generation browsers should be capable to
1678 use that feature. It currently is only tested with Internet Explorer 6
1679 and Mozilla 1.x.
1680 <br /><br />
1682 to a table, which has to be created by you (see <a
1684 all your queries will be appended to the form, but only as long as
1685 your window is opened they remain saved.
1686 <br /><br />
1687 When using the JavaScript based query window, it will always get
1688 updated when you click on a new table/db to browse and will focus if
1689 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1690 the query window by checking the box "Do not overwrite this query from
1691 outside the window" below the query textarea. Then you can browse
1692 tables/databases in the background without losing the contents of the
1693 textarea, so this is especially useful when composing a query with
1694 tables you first have to look in. The checkbox will get automatically
1695 checked whenever you change the contents of the textarea. Please
1696 uncheck the button whenever you definitely want the query window to
1697 get updated even though you have made alterations.
1698 <br /><br />
1701 <br /><br />
1702 The query window also has a custom tabbed look to group the features.
1704 default tab to be used when opening the query window. It can be set to
1705 either 'sql', 'files', 'history' or 'full'.</dd>
1711 <dd><ul><li>For InnoDB tables, determines for how large tables phpMyAdmin
1713 If the approximate row count as returned by
1716 count will be used.</li>
1717 <li>For VIEWs, since obtaining the exact count could have an
1718 impact on performance, this value is the maximum to be displayed.
1719 </li>
1720 </ul>
1721 </dd>
1725 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1727 page. By clicking on the button 'toggle scratchboard' on the page
1728 where you edit x/y coordinates of those elements you can activate a
1729 scratchboard where all your elements are placed. By clicking on an
1730 element, you can move them around in the pre-defined area and the x/y
1731 coordinates will get updated dynamically. Likewise, when entering a
1732 new position directly into the input field, the new position in the
1733 scratchboard changes after your cursor leaves the input field.<br />
1734 You have to click on the 'OK'-button below the tables to save the new
1735 positions. If you want to place a new element, first add it to the
1736 table of elements and then you can drag the new element around.<br />
1737 By changing the paper size and the orientation you can change the size
1738 of the scratchboard as well. You can do so by just changing the
1739 dropdown field below, and the scratchboard will resize automatically,
1740 without interfering with the current placement of the elements.<br />
1741 If ever an element gets out of range you can either enlarge the paper
1742 size or click on the 'reset' button to place all elements below each
1743 other.<br />
1745 get this control to work. The basic Drag&Drop script functionality
1746 was kindly borrowed from www.youngpup.net and is underlying so
1747 specific license.</dd>
1750 <dd>Sorts database and table names according to natural order (for example,
1751 t1, t2, t10). Currently implemented in the left panel (Light mode)
1752 and in Database view, for the table list.</dd>
1758 <dd>Allows you to specify window's title bar. Following magic string can
1759 be used to get special values:
1760 <dl>
1766 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1775 </dl>
1776 </dd>
1786 </dd>
1789 <dd>If theme manager is active, use this as the path of the subdirectory
1790 containing all the themes.</dd>
1804 </dt>
1805 <dd>Default queries that will be displayed in query boxes when user didn't
1806 specify any. Use %d for database name, %t for table name and %f for a
1807 comma separated list of field names. Note that %t and %f are only
1811 <dd>
1812 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
1813 default we use HTML to format the query, but you can disable this by
1815 </dd>
1818 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1819 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1820 query inside a bracket is indented. By changing
1823 specifies the units of the indent amount that you specified. This is
1824 used via stylesheets.</dd>
1827 <dd>This array is used to define the colours for each type of element of
1828 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1830 If you specify an empty string for the color of a class, it is ignored
1831 in creating the stylesheet.
1832 You should not alter the class names, only the colour strings.<br />
1853 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1857 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1858 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1859 </ul>
1860 </dd>
1864 <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,
1865 as originally published on
1867 <br />
1868 For help in setting up your system to use the service, see the
1870 </dd>
1874 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1875 and any password, so we use those by default. Instead, if
1876 you have an account with them, you can put your login details
1877 here, and it will be used in place of the anonymous login.</dd>
1878 </dl>
1879 </dd>
1882 <dd><b>DEVELOPERS ONLY!</b></dd>
1885 <dd><b>DEVELOPERS ONLY!</b><br />
1886 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1887 the code.<br />
1888 For help in setting up your system to this, see the
1892 <dd><b>DEVELOPERS ONLY!</b><br />
1893 Enable profiling support for phpMyAdmin. This will append a chunk of data
1894 to the end of every page displayed in the main window with profiling
1895 statistics for that page.<br />
1896 You may need to increase the maximum execution time for this to
1897 complete successfully.<i>Profiling was removed from the code for
1898 version 2.9.0 due to licensing issues.</i></dd>
1900 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
1901 <dd><b>DEVELOPERS ONLY!</b><br />
1902 When profiling data is displayed, this variable controls the threshold of
1903 display for any profiling data, based on the average time each time has
1904 taken. If it is over the threshold it is displayed, otherwise it is not
1905 displayed. This takes a value in milliseconds. In most cases you don't need
1906 to edit this.</dd>
1909 <dd>All possible types of a MySQL column. In most cases you don't need to
1910 edit this.</dd>
1913 <dd>Possible attributes for fields. In most cases you don't need to edit
1914 this.</dd>
1917 <dd>A list of functions MySQL supports. In most cases you don't need to
1918 edit this.</dd>
1921 <dd>Mapping of column types to meta types used for preferring displayed
1922 functions. In most cases you don't need to edit this.</dd>
1925 <dd>Functions preferred for column meta types as defined in
1926 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
1927 to edit this.</dd>
1930 <dd>Functions selected by default when inserting/changing row, Functions
1931 are defined for meta types from
1933 <code>first_timestamp</code>, which is used for first timestamp column
1934 in table.</dd>
1937 <dd>Operators available for search operations on numeric and date fields.
1938 </dd>
1941 <dd>Operators available for search operations on character fields.
1942 Note that we put <code>LIKE</code> by default instead of
1943 <code>LIKE %...%</code>, to avoid unintended performance problems
1944 in case of huge tables.</dd>
1947 <dd>Operators available for search operations on enum fields.</dd>
1950 <dd>Additional operators available for search operations when the
1951 field can be null.</dd>
1953 </dl>
1955 <!-- TRANSFORMATIONS -->
1961 </ol>
1965 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
1967 section</a> on how to do so.</p>
1969 <p> You can apply different transformations to the contents of each field. The
1970 transformation will take the content of each field and transform it with
1971 certain rules defined in the selected transformation.</p>
1973 <p> Say you have a field 'filename' which contains a filename. Normally you would
1974 see in phpMyAdmin only this filename. Using transformations you can transform
1975 that filename into a HTML link, so you can click inside of the phpMyAdmin
1976 structure on the field's link and will see the file displayed in a new browser
1977 window. Using transformation options you can also specify strings to
1978 append/prepend to a string or the format you want the output stored in.</p>
1980 <p> For a general overview of all available transformations and their options,
1981 you can consult your
1982 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
1983 installation.</p>
1985 <p> For a tutorial on how to effectively use transformations, see our
1987 the official phpMyAdmin homepage.</p>
1991 <p> Go to your <i>tbl_properties_structure.php</i> page (i.e. reached through
1992 clicking on the 'Structure' link for a table). There click on
1993 "Change" (or change icon) and there you will see three new fields at
1994 the end of the line. They are called 'MIME-type', 'Browser transformation' and
1995 'Transformation options'.</p>
1997 <ul><li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
1998 empty or to use 'auto' [this feature is not yet available]. Please note that
1999 transformations are inactive as long as no MIME-type is selected.</li>
2001 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2002 hopefully growing amount of pre-defined transformations. See below for information on
2003 how to build your own transformation.<br />
2005 There are global transformations and mimetype-bound transformations. Global transformations
2006 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2007 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2008 transformations which operate on the main mimetype (like 'image'), which will most likely
2009 take the subtype into regard, and those who only operate on a
2010 specific subtype (like 'image/jpeg').<br />
2012 You can use transformations on mimetypes for which the function was not defined for. There
2013 is no security check for you selected the right transformation, so take care of what the
2014 output will be like.</li>
2016 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2017 transform-function specific options here. Usually the transforms can operate with default
2018 options, but it is generally a good idea to look up the overview to see which options are
2019 necessary.<br />
2021 Much like the ENUM/SET-Fields, you have to split up several options using the format
2022 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2023 parsed as an array, leaving the first value the first element in the array, and so
2024 forth.<br />
2026 If you want to specify a MIME character set you can define it in the transformation_options.
2027 You have to put that outside of the pre-defined options of the specific mime-transform,
2029 for which you can specify 2 options and you want to append a character set, enter "'first
2030 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2032 </ul>
2036 <p> All mimetypes and their transformations are defined through single files in
2037 the directory 'libraries/transformations/'.</p>
2039 <p> They are stored in files to ease up customization and easy adding of new
2040 transformations.</p>
2042 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2043 always work. It makes no sense to apply a transformation to a mimetype, the
2044 transform-function doesn't know to handle.</p>
2046 <p> One can, however, use empty mime-types and global transformations which should work
2047 for many mimetypes. You can also use transforms on a different mimetype they where built
2048 for, but pay attention to option usage as well as what the transformation does to your
2049 field.</p>
2051 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2052 any other transform function and provides some basic functions.</p>
2054 <p> There are 5 possible file names:</p>
2056 <ol><li>A mimetype+subtype transform:<br /><br />
2058 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2060 Please not that mimetype and subtype are separated via '_', which shall
2061 not be contained in their names. The transform function/filename may
2062 contain only characters which cause no problems in the file system as
2063 well as the PHP function naming convention.<br /><br />
2065 The transform function will the be called
2066 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2068 <b>Example:</b><br /><br />
2070 <tt>text_html__formatted.inc.php</tt><br />
2071 <tt>PMA_transform_text_html__formatted()</tt></li>
2073 <li>A mimetype (w/o subtype) transform:<br /><br />
2075 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2077 Please note that there are no single '_' characters.
2078 The transform function/filename may contain only characters which cause
2079 no problems in the file system as well as the PHP function naming
2080 convention.<br /><br />
2082 The transform function will the be called
2083 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2085 <b>Example:</b><br /><br />
2087 <tt>text__formatted.inc.php</tt><br />
2088 <tt>PMA_transform_text__formatted()</tt></li>
2090 <li>A mimetype+subtype without specific transform function<br /><br />
2092 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2094 Please note that there are no '__' characters in the filename. Do not
2095 use special characters in the filename causing problems with the file
2096 system.<br /><br />
2098 No transformation function is defined in the file itself.<br /><br />
2100 <b>Example:</b><br /><br />
2102 <tt>text_plain.inc.php</tt><br />
2103 (No function)</li>
2105 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2107 <tt>[mimetype].inc.php</tt><br /><br />
2109 Please note that there are no '_' characters in the filename. Do not use
2110 special characters in the filename causing problems with the file system.
2111 <br /><br />
2113 No transformation function is defined in the file itself.<br /><br />
2115 <b>Example:</b><br /><br />
2117 <tt>text.inc.php</tt><br />
2118 (No function)</li>
2120 <li>A global transform function with no specific mimetype<br /><br />
2122 <tt>global__[transform].inc.php</tt><br /><br />
2124 The transform function will the be called
2125 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2127 <b>Example:</b><br /><br />
2129 <tt>global__formatted</tt><br />
2130 <tt>PMA_transform_global__formatted()</tt></li>
2131 </ol>
2133 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2134 transform function.</p>
2136 <p> All filenames containing no '__' in themselves are not shown as valid transform
2137 functions in the dropdown.</p>
2139 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2140 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2141 without a transform function. Also note the introduction of a function description in
2142 the language files. For each function a $strTransformation_[filename without .inc.php]
2143 has to exist.</p>
2145 <p> You can use the template generator to generate new functions and entries in the
2146 language file.</p>
2148 <p> To create a new transform function please see
2149 <tt>libraries/transformations/template_generator.sh</tt>.
2150 To create a new, empty mimetype please see
2151 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2153 <p> A transform function always gets passed three variables:</p>
2155 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2156 you want to transform.</li>
2157 <li><b>$options</b> - Contains any user-passed options to a transform function
2158 as an array.</li>
2159 <li><b>$meta</b> - Contains an object with field information to your column.
2160 The data is drawn from the output of the
2162 function. This means, all object properties described on the
2164 available in this variable and can be used to transform a field accordingly
2165 to unsigned/zerofill/not_null/... properties.<br />
2166 The $meta->mimetype variable contains the original MIME-type of the
2167 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2168 </ol>
2170 <!-- FAQ -->
2177 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2181 </ol>
2183 <p> Please have a look at our
2185 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2186 features and or interface.</p>
2192 action is required or phpMyAdmin sends a blank page or a page full of
2193 cryptic characters to my browser, what can I do?</a></h4>
2195 <p> There are some known PHP bugs with output buffering and compression.<br />
2197 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2198 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2199 configuration file.<br />
2200 Furthermore, we know about such problems connected to the release
2201 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2202 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2207 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2208 See also the
2210 entry about PHP bugs with output buffering.<br />
2211 If your server keeps crashing, please ask for help in the various Apache
2212 support groups.</p>
2216 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2217 script: I'm always displayed the login screen.</a></h4>
2219 <p> This is a known PHP bug (see this
2221 official PHP bug database. It means there is and won't be any phpMyAdmin
2222 fix against it because there is no way to code a fix.</p>
2228 application misbehaved by not returning a complete set of
2230 </h4>
2232 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2233 Have a look at the last message in this
2235 official PHP bug database.</p>
2240 and/or many error messages with the
2242 mode.</a></h4>
2244 <p> This is a known problem with the PHP
2246 filter: it's not so stable. Please use instead the cookie authentication mode.
2247 </p>
2252 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2253 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2254 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2255 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2256 <i>left.php</i> and <i>libraries/common.lib.php</i>.</p>
2261 work.</a></h4>
2263 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2264 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2265 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2266 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2267 We faced PHP crashes when trying to download a dump with MS Internet
2268 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2269 this case you should switch to the release version of PHP 4.2.0.</p>
2273 an error about safe mode being in effect.</a></h4>
2275 <p> Your uploaded file is saved by PHP in the "upload dir", as
2276 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2277 the system default is <i>/tmp</i>).<br />
2278 We recommend the following setup for Apache servers running in safe mode,
2279 to enable uploads of files while being reasonably secure:</p>
2281 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2282 <li>give ownership to the Apache server's user.group:
2283 <tt>chown apache.apache /tmp/php</tt></li>
2284 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2285 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2286 <li>restart Apache</li>
2287 </ul>
2291 general file uploads don't work on my system and uploaded files have a
2292 <tt>Content-Type:</tt> header in the first line.</a></h4>
2294 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2295 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2296 So the problem is that this package has a serious bug that was corrected
2297 ages ago in PHP (2001-01-28: see
2299 for more details). The problem is that the bugged package is still
2300 available though it was corrected (see
2302 for more details).<br />
2303 So please download
2304 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2305 and the problem should go away.<br />
2306 And that fixes the \r\n problem with file uploads!</p>
2310 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2311 I'm using the Apache server.</a></h4>
2313 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2314 your <i>httpd.conf</i>:</p>
2318 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2322 uploading a file from the query box.</a></h4>
2324 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2325 restrictions. Assuming that the restriction allows you to open files in the
2326 current directory ('.'), all you have to do is create a 'tmp' directory
2327 under the phpMyAdmin install directory, with permissions 777 and the same
2328 owner as the owner of your phpMyAdmin directory. The uploaded files will
2329 be moved there, and after execution of your
2335 <p> The MySQL manual explains how to
2337 reset the permissions</a>.</p>
2342 execute a bookmark.</a></h4>
2344 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2345 cannot access the uploaded query.</p>
2350 submit a query from the convenient text area.</a></h4>
2352 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2353 and try to increase it.</p>
2357 </h4>
2359 <p> In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2360 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2361 names to align with current standards.</p>
2366 </h4>
2368 <p> Starting with version 2.7.0, the import engine has been re–written and these
2369 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2370 to take advantage of the new import features.</p>
2372 <p> The first things to check (or ask your host provider to check) are the
2373 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2374 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2375 All of these three settings limit the maximum size of data that can be
2376 submitted and handled by PHP. One user also said that post_max_size
2377 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2379 There exist several workarounds if your upload is too big or your
2380 hosting provider is unwilling to change the settings:</p>
2383 feature. This allows one to
2384 upload a file to the server via scp, ftp, or your favorite file transfer
2385 method. PhpMyAdmin is then able to import the files from the temporary
2387 section</a> of this document.</li>
2389 BigDump</a>) to split the files before uploading. We cannot support this
2390 or any third party applications, but are aware of users having success
2391 with it.</li>
2392 <li>If you have shell (command line) access, use MySQL to import the files
2393 directly. You can do this by issuing the "source" command from
2394 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2395 </ul>
2399 support?</a></h4>
2401 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2402 fully supported. Please note that the older your MySQL version is, the more
2403 limitations you will have to face.<br />
2404 phpMyAdmin may connect to your MySQL server using php's classic
2407 is available in php 5.0.<br />
2408 Either way, the developers of both extensions recommend to use the classic
2409 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2410 When compiling php, we strongly recommend that you manually link the MySQL
2411 extension of your choice to a MySQL client library of at least the same
2412 minor version since the one that is bundled with some php distributions is
2415 If your webserver is running on a windows system, you might want to try
2416 MySQL's
2418 instead of the MySQL / MySQLi extensions that are bundled with the official
2419 php Win32 builds.
2420 <br />
2421 MySQL 5.1 is not yet supported.</p>
2425 message, "Client does not support authentication protocol requested
2426 by server; consider upgrading MySQL client"</a></h5>
2428 <p> You tried to access MySQL with an old MySQL client library. The version of
2429 your MySQL client library can be checked in your phpinfo() output.
2430 In general, it should have at least the same minor version as your server
2434 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2435 changed the authentication hash and your PHP is trying to use the old method.
2437 with the proper client library to match your MySQL installation. Your
2438 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2439 More information (and several workarounds) are located in the
2441 </p>
2445 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2446 capital letter in its name it is changed to lowercase as it should. But
2447 if I try to DROP this table MySQL is unable to find the corresponding
2448 file.</a></h4>
2450 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2451 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2452 directive.</p>
2456 script seems not to know the font face I'm using!</a></h4>
2458 <p> The "FPDF" library we're using for this feature requires some
2459 special files to use font faces.<br />
2461 these files.</p>
2465 check PHP Configuration".</a></h4>
2467 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2468 "MySQL extension". This extension may be part of the PHP
2469 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2470 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2471 to load the extension but failed.<br /><br />
2473 Usually, the problem is solved by installing a software package called
2474 "PHP-MySQL" or something similar.</p>
2479 and I cannot log in using cookie auth.</a></h4>
2481 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2485 so I cannot upload.</a></h4>
2487 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2488 parameter is not set to "on".</p>
2492 a new table the table and field names are changed to lowercase!</a></h4>
2494 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2495 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2496 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2497 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2498 directory and add the following line to the group [mysqld]:</p>
2500 <pre>set-variable = lower_case_table_names=0</pre>
2502 <p> Next, save the file and restart the MySQL service. You can always check the
2503 value of this directive using the query</p>
2505 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2509 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2512 </p>
2516 and I get problems, such as undefined variables when I run a
2519 <p> A tip from Jose Fandos: put a comment on the following two lines
2520 in httpd.conf, like this:</p>
2522 <pre>
2523 # mod_gzip_item_include file \.php$
2525 </pre>
2527 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2528 PHP scripts. Of course you have to restart Apache.</p>
2533 I get the error "No input file specified" when trying to
2534 run phpMyAdmin.</a></h4>
2536 <p> This is a permission problem. Right-click on the phpmyadmin folder
2537 and choose properties. Under the tab Security, click on "Add"
2538 and select the user "IUSR_machine" from the list. Now set his
2539 permissions and it should work.</p>
2543 db_details_structure.php with plenty of tables).</a></h4>
2546 GZIP output buffering is enabled. If you turn off it (by
2548 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2549 PHP 5.0.0.</p>
2553 message 'Errorcode: 13'. What does this mean?</a></h4>
2555 <p> This can happen due to a MySQL bug when having database / table names with
2556 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2557 To fix this, turn off this directive, convert all database and table names
2558 to lower case and turn it on again. Alternatively, there's a bug-fix
2559 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2563 and the fields are duplicated.</a></h4>
2565 <p> It is possible to configure Apache in such a way that PHP has problems
2566 interpreting .php files.</p>
2568 <p> The problems occur when two different (and conflicting) set of directives
2569 are used:</p>
2571 <pre>
2572 SetOutputFilter PHP
2573 SetInputFilter PHP
2574 </pre>
2576 <p> and</p>
2578 <pre>AddType application/x-httpd-php .php</pre>
2580 <p> In the case we saw, one set of directives was in
2581 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2582 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2583 The recommended way is with <tt>AddType</tt>, so just comment out
2584 the first set of lines and restart Apache:</p>
2586 <pre>
2587 #SetOutputFilter PHP
2588 #SetInputFilter PHP
2589 </pre>
2594 <p> This problem is known to happen when the server is running Turck MMCache
2595 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2600 <p> Yes.<br />
2601 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2602 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2603 <tt>error_reporting</tt> settings.
2604 </p>
2607 <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>
2609 <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>
2612 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2613 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2614 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2615 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2616 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2617 enabled.) Click <tt>OK</tt>.</li>
2618 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2619 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2620 </ol>
2624 PHP 5.0.4 on 64-bit systems?</a></h4>
2626 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2627 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2633 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2634 Table and script parts are optional. If you want
2635 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2636 some configuration. Following lines apply only for <a
2638 that you have enabled some features within global configuration. You need
2639 <code>Options FollowSymLinks</code> and <code>AllowOverride
2640 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2641 you need mod_rewrite to be enabled. Then you just need to create following
2642 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2643 (don't forget to change directory name inside of it):</p>
2645 <pre>
2646 RewriteEngine On
2647 RewriteBase /path_to_phpMyAdmin
2648 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2649 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2650 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2651 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2652 </pre>
2655 <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>
2657 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2658 following rewrite rule:</p>
2660 <pre>
2661 RewriteEngine On
2662 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2663 </pre>
2667 </h4>
2668 <p>
2669 There can be many explanations to this and a look at your server's
2670 error log file might give a clue.
2671 </p>
2675 password encryption in cookie auth doesn't work.</a></h4>
2677 <p> If your cluster consist of different architectures, PHP code used for
2678 encryption/decryption won't work correct. This is caused by use of
2679 pack/unpack functions in code. Only solution is to use mcrypt extension
2680 which works fine in this case.</p>
2686 headers already sent by ..." is displayed, what's the problem?</a></h4>
2688 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2689 (I.E. no blank lines, no spaces, no characters...) neither before the
2690 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2691 tag at the end.</p>
2696 <p> Either there is an error with your PHP setup or your username/password is
2697 wrong. Try to make a small script which uses mysql_connect and see if it
2698 works. If it doesn't, it may be you haven't even compiled MySQL support
2699 into PHP.</p>
2703 connect to local MySQL server through socket '/tmp/mysql.sock'
2704 (111) ..." is displayed. What can I do?</a></h4>
2706 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2708 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2709 In your <i>php.ini</i> you will find a line</p>
2711 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2713 <p> change it to</p>
2715 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2717 <p> Then restart apache and it will work.</p>
2719 <p> Here is a fix suggested by Brad Ummer:</p>
2721 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2722 To do this, telnet to your server and go to the MySQL bin directory. In
2723 this directory there should be a file named <i>mysqladmin</i>. Type
2724 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2725 info about your MySQL server, including the socket
2726 (<i>/tmp/mysql.sock</i>, for example).</li>
2727 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2728 phpMyAdmin, you need to complete the socket information in the
2729 <i>config.inc.php</i>.<br />
2730 For example:
2732 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2733 <br /><br />
2735 Please also make sure that the permissions of this file allow to be readable
2736 by your webserver (i.e. '0755').</li>
2737 </ul>
2739 <p> Have also a look at the
2741 corresponding section of the MySQL documentation</a>.</p>
2745 what can I do?</a></h4>
2748 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2749 sometime.<br />
2750 Also have a look at your PHP version number: if it contains "4.0b..."
2751 it means you're running a beta version of PHP. That's not a so good idea,
2752 please upgrade to a plain revision.</p>
2756 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2757 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2759 <p> Check the value you set for the
2761 directive in the phpMyAdmin configuration file.</p>
2765 password: YES)"-error when trying to access a MySQL-Server on a
2766 host which is port-forwarded for my localhost.</a></h4>
2768 <p> When you are using a port on your localhost, which you redirect via
2769 port-forwarding to another host, MySQL is not resolving the localhost
2770 as expected.<br />
2771 Erik Wasser explains: The solution is: if your host is "localhost"
2772 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2773 connection for speeding up things. And that doesn't work in this configuration
2774 with port forwarding.<br />
2780 <p> Themes are configured with
2784 <br />
2786 should not delete the directory "original" or its underlying
2787 structure, because this is the system theme used by phpMyAdmin.
2788 "original" contains all images and styles, for backwards
2789 compatibility and for all themes that would not include images or css-files.
2790 <br /><br />
2793 is enabled, you can select your favorite theme on the main page. Your
2794 selected theme will be stored in a cookie.<br /><br /></p>
2796 <p> To create a theme:</p>
2798 <ul><li>make a new subdirectory (for example "your_theme_name") under
2800 (by default <tt>themes</tt>)</li>
2801 <li>copy the files and directories from "original" to
2802 "your_theme_name"</li>
2803 <li>edit the css-files in "your_theme_name/css"</li>
2804 <li>put your new images in "your_theme_name/img"</li>
2805 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2806 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2807 contain your chosen theme name, that will be visible in user interface</li>
2808 <li>make a new screenshot of your theme and save it under
2809 "your_theme_name/screen.png"</li>
2810 </ul>
2812 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2813 theme verbose name, theme generation and theme version. These versions and
2814 generations are enumerated from 1 and do not have any direct dependence on
2815 phpMyAdmin version. Themes within same generation should be backwards
2816 compatible - theme with version 2 should work in phpMyAdmin requiring
2817 version 1. Themes with different generation are incompatible.</p>
2819 <p> If you do not want to use your own symbols and buttons, remove the
2820 directory "img" in "your_theme_name". phpMyAdmin will
2821 use the default icons and buttons (from the system-theme "original").
2822 </p>
2826 what can I do?</a></h4>
2828 <p> Here are a few points to check:</p>
2830 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2832 directive empty. See also
2834 </li>
2835 <li>Maybe you have a broken PHP installation or you need to upgrade
2836 your Zend Optimizer. See
2838 http://bugs.php.net/bug.php?id=31134</a>.
2839 </li>
2840 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2841 set to the default (200) or another low value, you could get this
2842 error if your table has a high number of columns. Adjust this setting
2843 accordingly. (Thanks to Klaus Dorninger for the hint).
2844 </li>
2845 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2846 of ";" will cause this error. Replace it with "&;".
2847 </li>
2848 </ul>
2855 who logged out can not log in again in with the same nick.</a></h4>
2857 <p> This is related to the authentication mechanism (protocol) used by
2858 phpMyAdmin. To bypass this problem: just close all the opened
2859 browser windows and then go back to phpMyAdmin. You should be able to
2860 log in again.</p>
2864 limit error or a time limit error.</a></h4>
2866 <p> Compressed dumps are built in memory and because of this are limited to
2867 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2868 using
2870 (enabled by default). Zip exports can not be handled this way, so if you need
2871 Zip files for larger dump, you have to use another way.</p>
2875 or alter a table.</a></h4>
2877 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
2881 bundled with the MySQL server distribution.</a></h4>
2883 <p> The problem is that mysqldump creates invalid comments like this:</p>
2885 <pre>
2886 -- MySQL dump 8.22
2887 --
2888 -- Host: localhost Database: database
2889 ---------------------------------------------------------
2890 -- Server version 3.23.54
2891 </pre>
2893 <p> The invalid part of the code is the horizontal line made of dashes that
2894 appears once in every dump created with mysqldump. If you want to run your
2895 dump you have to turn it into valid MySQL. This means, you have to add a
2896 whitespace after the first two dashes of the line or add a # before it:
2897 <br />
2898 <code>
2899 -- -------------------------------------------------------<br />
2900 </code>
2901 or<br />
2902 <code>
2903 #---------------------------------------------------------
2904 </code>
2905 </p>
2912 <p> Please note that you should not use the separating string multiple times
2913 without any characters between them, or at the beginning/end of your table
2914 name. If you have to, think about using another TableSeparator or disabling
2915 that feature</p>
2920 <p> In Relation view, being able to choose a table in another database,
2921 or having more than one index field in the foreign key.<br /><br/>
2922 In Query-by-example (Query), automatic generation of the query
2923 LEFT JOIN from the foreign table.<br /><br/>
2924 </p>
2928 I get series of errors like "Warning: unable to parse url". How
2929 can this be fixed?</a></h4>
2930 <p>
2931 Your table neither have a primary key nor an unique one, so we must use a
2932 long expression to identify this row. This causes problems to parse_url
2933 function. The workaround is to create a primary or unique key.
2934 <br />
2935 </p>
2939 a MIME-Transformation onto!</a></h4>
2941 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
2942 nested forms can be put inside the table where phpMyAdmin displays the results.
2943 You can, however, use any form inside of a table if keep the parent
2944 form-container with the target to tbl_row_delete.php and just put your own
2945 input-elements inside. If you use a custom submit input field, the form will
2946 submit itself to the displaying page again, where you can validate the
2947 $HTTP_POST_VARS in a transformation.
2949 For a tutorial on how to effectively use transformations, see our
2951 on the official phpMyAdmin-homepage.</p>
2955 MySQL server</a></h4>
2957 <p> When MySQL is running in ANSI-compatibility mode, there are some major
2960 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
2961 the quote-character (") is interpreted as an identifier quote character and
2962 not as a string quote character, which makes many internal phpMyAdmin
2964 statements. There is no workaround to this behaviour. News to this item will
2965 be posted in Bug report
2966 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
2967 </p>
2971 more that one column with the same value
2972 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
2973 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
2975 <p> Please make sure that your table has a primary key, so that phpMyAdmin
2976 can use it for the Edit and Delete links.</p>
2981 <p> phpMyAdmin uses a quick method to get the row count, and this method
2982 only returns an approximate count in the case of InnoDB tables. See
2984 a way to modify those results, but
2985 this could have a serious impact on performance.</p>
2990 <p> The number of records in queries containing COUNT and GROUP BY is
2991 not correctly calculated. Also, sorting results of a query like
2996 containing an hyphen.
2997 </a></h4>
2998 <p>
2999 The tests I have made with current MySQL 4.1.11 API shows that the
3000 API does not accept this syntax for the USE command. Enclosing the
3001 db name with backquotes works. For further confusion, no backquotes
3002 are needed with command-line mysql.
3003 </p>
3005 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3008 <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
3009 need to install it for each customer.
3010 </a></h4>
3011 <p>
3012 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3013 your users. The development of this feature was kindly sponsored by
3014 NetCologne GmbH.
3015 This requires a properly setup MySQL user management and phpMyAdmin
3016 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3018 </p>
3022 access.
3023 </a></h4>
3024 <p>
3025 This depends on your system.<br />
3026 If you're running a server which cannot be accessed by other people, it's
3027 sufficient to use the directory protection bundled with your webserver
3029 If other people have telnet access to your server, you should use
3030 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3031 <br /><br />
3032 Suggestions:
3033 </p>
3034 <ul>
3035 <li>
3037 </li>
3038 <li>
3039 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3040 is a user whose password is only known to you, and apache is the
3041 group under which Apache runs.
3042 </li>
3043 <li>
3044 You should use PHP safe mode, to protect from other users that try
3046 </li>
3047 </ul>
3052 </a></h4>
3053 <p>
3058 </p>
3061 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3062 authentication.
3063 </a></h4>
3067 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3068 and/or
3070 are wrong.</li>
3072 <li>You have already setup a security mechanism for the
3073 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3074 phpMyAdmin's authentication, so remove it.</li>
3075 </ul>
3082 and put the privileges you want. For example,
3084 would let a user create/manage his/her database(s).</p>
3089 <p> If you have existing rules from an old .htaccess file, you can take them
3092 be a major benefit here if your installation is suited to using it. Then
3093 you can just add those updated lines into the
3097 <p> If you want a pre-made sample, you can try this fragment. It stops the
3098 'root' user from logging in from any networks other than the private
3101 <pre>
3102 //block root from logging in except from the private networks
3103 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3104 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3105 'deny root from all',
3106 'allow root from localhost',
3110 );
3111 </pre>
3116 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3117 different than the one set in your
3119 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3120 while a domain name is defined in the config file.</p>
3126 when trying to create a table with more than 14 fields.
3127 </a></h4>
3128 <p>
3129 We could reproduce this problem only under Win98/98SE. Testing under
3130 WinNT4 or Win2K, we could easily create more than 60 fields.
3131 <br />
3132 A workaround is to create a smaller number of fields, then come back to
3133 your table properties and add the other fields.
3134 </p>
3138 <p>
3139 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3140 with each script/website that use forms.<br />
3141 Upgrade or downgrade your Xitami server.
3142 </p>
3145 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3146 <p>
3147 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3148 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3149 don't seem to work.<br />
3151 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3152 the user's temporary directory, so they must be moved before closing
3153 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3156 </p>
3160 Explorer never stores the cookies.
3161 </a></h4>
3162 <p>
3163 MS Internet Explorer seems to be really buggy about cookies, at least till
3165 in this area!
3166 <br />
3167 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3168 work!
3169 </p>
3173 rows.
3174 </a></h4>
3175 <p>
3177 </p>
3180 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3181 when trying to modify a row in a table with many fields, or with a text field
3182 </a></h4>
3183 <p>
3184 Your table neither have a primary key nor an unique one, so we must use a
3185 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
3186 those browsers, and this not happen in Netscape, for example. The
3187 workaround is to create a primary or unique key, or use another browser.
3188 <br />
3189 </p>
3193 page.
3194 </a></h4>
3195 <p>
3196 Some browsers support right-clicking into the frame you want to refresh,
3197 just do this in the right frame.<br />
3198 </p>
3202 query box.
3203 </a></h4>
3204 <p>
3205 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3206 Mozilla versions.<br />
3207 </p>
3211 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3212 </a></h4>
3213 <p>
3214 This is a Mozilla bug (see bug #26882 at
3216 </p>
3221 </a></h4>
3222 <p>
3223 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3224 data in octet-stream mode. Since we can't detect the specific Netscape
3225 version, we cannot workaround this bug.
3226 </p>
3230 wrong.</a></h4>
3232 <p> Please ensure that you have set your browser's character set to the one of the
3233 language file you have selected on phpMyAdmin's start page.
3234 Alternatively, you can try the auto detection mode that is supported by the
3235 recent versions of the most browsers.</p>
3238 <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
3241 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3242 Netscape and Mozilla do not have this problem.</p>
3245 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3246 I cannot manage two servers: I log in to the first one, then the other one,
3247 but if I switch back to the first, I have to log in on each operation.</a></h4>
3253 but nothing happens after that, only a blank screen.</a></h4>
3256 bug in Opera6, because it is not able to interpret frameset definitions
3257 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3258 Opera7 at least.</p>
3267 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3272 address and you are starting
3274 containing a domain name, or the reverse situation.</li>
3275 <li>Security settings in IE and/or Microsoft Security Center are
3276 too high, thus blocking scripts execution.</li>
3277 <li>The Windows Firewall is blocking Apache and MySQL. You must
3281 </ul>
3284 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3285 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3286 installed in their Firefox is causing the problem.</p>
3293 </a></h4>
3294 <p>
3295 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3296 specifying a wrong field-type.<br />
3297 Common errors include:
3298 </p>
3299 <ul>
3302 </ul>
3303 <p>
3304 Also, look at the syntax chapter in the MySQL manual to confirm that your
3305 syntax is correct.
3306 </p>
3310 phpMyAdmin generates only one index with those 2 fields.
3311 </a></h4>
3312 <p>
3314 index. If you want two indexes, create the first one when creating the
3315 table, save, then display the table properties and click the Index link to
3316 create the other index.
3317 </p>
3321 <p>
3322 Since version 2.2.3, you have a checkbox for each field that can be null.
3324 field's value. Since version 2.5.5, you have to use the checkbox to get
3326 a literal NULL in the field, and not a NULL value (this works in PHP4).
3327 </p>
3332 <p> Click on a database or table name in the left frame, the properties will be
3334 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3335 statements that can be used to recreate your database/table.
3336 <br /><br />
3338 transmit the resulting dump to your station. Depending on your PHP
3339 configuration, you will see options to compress the dump. See also the
3341 configuration variable.<br /><br />
3344 this document.</p>
3349 </a></h4>
3351 <p> Click on a database name in the left frame, the properties will be
3353 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3355 the path to your dump filename, or use the Browse button. Then click Go.
3356 <br /><br />
3358 that you upgrade to take advantage of the new features.
3359 <br /><br />
3361 in this document.
3362 </p>
3367 <p> Here is an example with the tables persons, towns and countries, all
3369 table, create it as explained in the configuration section. Then create the
3370 example tables:</p>
3372 <pre>
3373 CREATE TABLE REL_countries (
3374 country_code char(1) NOT NULL default '',
3375 description varchar(10) NOT NULL default '',
3376 PRIMARY KEY (country_code)
3377 ) TYPE=MyISAM;
3379 INSERT INTO REL_countries VALUES ('C', 'Canada');
3381 CREATE TABLE REL_persons (
3382 id tinyint(4) NOT NULL auto_increment,
3383 person_name varchar(32) NOT NULL default '',
3385 country_code char(1) NOT NULL default '',
3386 PRIMARY KEY (id)
3387 ) TYPE=MyISAM;
3389 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3390 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3392 CREATE TABLE REL_towns (
3394 description varchar(30) NOT NULL default '',
3395 PRIMARY KEY (town_code)
3396 ) TYPE=MyISAM;
3398 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3399 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3400 </pre>
3406 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3410 </ul>
3418 <li>In the fields row, choose persons.person_name and click the
3420 <li>Do the same for towns.description and countries.descriptions in the
3423 the correct joins have been generated</li>
3425 </ul>
3429 <p>
3430 Starting from the previous example, create the pma_table_info as explained
3431 in the configuration section, then browse your persons table,
3432 and move the mouse over a town code or country code.
3433 <br /><br />
3434 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3435 enables: drop-down list of possible values.
3436 </p>
3439 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3440 <p>
3443 <br /><br />
3444 Then you need to think about your schema layout. Which tables will go on
3445 which pages?
3446 </p>
3447 <ul>
3453 page and click Go. If you like, you
3455 linked tables onto the new page.</li>
3456 <li>Select the name of the new page (making sure the Edit radio button
3457 is selected) and click Go.</li>
3459 Coordinates are relative; your diagram will
3460 be automatically scaled to fit the page. When initially placing tables
3461 on the page, just pick any coordinates -- say, 50x50. After clicking
3463 position the element correctly.</li>
3465 first be sure to click the Save
3466 button beneath the list of tables and coordinates, to save any changes
3467 you made there. Then scroll all the way down, select the
3469 you want, and click Go.</li>
3470 <li>Internet Explorer for Windows may suggest an incorrect filename when
3475 browsers on Windows, do not have this problem.</li>
3476 </ul>
3480 columns!</a></h4>
3482 <p> No, it's MySQL that is doing
3488 underscores in the database name?</a></h4>
3490 <p> If you do not put a backslash before the underscore, this is a wildcard
3493 john2db ...<br /><br />
3495 If you put a backslash before the underscore, it means that the database
3496 name will have a real underscore.</p>
3500 statistics pages?</a></h4>
3511 if it already exists during the import. It does NOT drop the table after
3512 your export, it only affects the import file.</li>
3514 Otherwise, you may get an error if the table name exists but has a
3515 different structure.</li>
3517 (if any) will be included in backup.</li>
3519 field and table names formed with special characters are protected.</li>
3521 types set in the pmadb in the dump as
3523 </li>
3524 </ul>
3529 command, for better documentation (but resulting file is bigger).</li>
3531 once the INSERT verb and the table name.</li>
3534 </li>
3536 more info is provided in the
3538 but basically with this selected, invalid values are adjusted and
3539 inserted rather than causing the entire statement to fail.</li>
3540 </ul>
3544 in its name.</a></h4>
3547 is the normal way to reference a database and table name. Worse, MySQL
3548 will usually let you create a database with a dot, but then you cannot
3549 work with it, nor delete it.</p>
3562 for usage.<br />
3563 On a more recent pear version, I had problems with the state of Net_DIME
3564 being beta, so this single command
3566 needed modules.<br />
3567 If you use the Validator, you should be aware that any
3569 submit will be stored anonymously (database/table/column names,
3570 strings, numbers replaced with generic values). The Mimer
3573 We utilize it as free SOAP service.</p>
3577 it, but MySQL says "BLOB column '...' used in key specification without
3580 <p> The right way to do this, is to create the field without any indexes,
3582 dialog. On this page, you will be able to choose your BLOB field, and
3583 set a size to the index, which is the condition to create an index on
3584 a BLOB field.</p>
3588 editing fields?</a></h4>
3590 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3591 with many editing fields (table structure changes, row editing, etc.)
3592 (must be enabled in configuration - see.
3594 You can also have a look at the directive
3596 ('vertical') and see if this eases up editing for you.</p>
3600 WTF is this feature then useful for?</a></h4>
3602 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3603 on them. Otherwise you could just put a comment on the field. Because entering
3604 your own mimetype will cause serious syntax checking issues and validation,
3605 this introduces a high-risk false-user-input situation. Instead you have to
3606 initialize mimetypes using functions or empty mimetype definitions.<br />
3607 Plus, you have a whole overview of available mimetypes. Who knows all those
3608 mimetypes by heart so he/she can enter it at will?</p>
3612 can't I see any bookmarks below the query box? What is this variable for?
3613 </a></h4>
3615 <p> Any query you have executed can be stored as a bookmark on the page where the
3616 results are displayed. You will find a button labeled 'Bookmark this query'
3617 just at the end of the page.<br />
3618 As soon as you have stored a bookmark, it is related to the database you run
3619 the query on. You can now access a bookmark dropdown on each page, the query
3620 box appears on for that database.<br /><br />
3622 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3626 aware of that you HAVE to create a valid query, otherwise your query won't be
3627 even able to be stored in the database.<br />
3629 for your query will remain the way it is, but will be stripped of the /**/
3630 chars. So you can use:<br /><br />
3634 which will be expanded to<br /><br />
3638 in your query, where VARIABLE is the string you entered in the input box. If
3639 an empty string is provided, no replacements are made.<br /><br />
3641 A more complex example. Say you have stored this query:<br /><br />
3643 <br /><br />
3646 the full query will be:<br /><br />
3649 <br /><br />
3653 spaces inserted there
3654 will be later also inserted as spaces in your query and may lead to unexpected
3655 results especially when
3657 Your initial query which is going to be stored as a bookmark has to yield at
3658 least one result row so
3659 you can store the bookmark. You may have that to work around using well
3663 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3664 include exported table?</a></h4>
3666 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3667 document should look like following one (assuming you have table
3670 <pre>
3671 \documentclass{article} % or any class you want
3672 \usepackage{longtable} % for displaying table
3673 \begin{document} % start of document
3674 \include{table} % including exported table
3675 \end{document} % end of document
3676 </pre>
3680 access them.
3681 </a></h4>
3684 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3685 enable users to see all the database names.
3688 So if your users do not need those privileges, you can remove them and their
3689 databases list will shorten.</p>
3693 possible values for a field, based on some foreign table?</a></h4>
3695 <p> You have to setup appropriate links between the tables, and also
3699 foreign table, a drop-down list of values will be available.
3700 You will see two lists of values, the first list containing the key
3701 and the display field, the second list containing the display field
3702 and the key. The reason for this is to be able to type the first
3703 letter of either the key or the display field.<br /><br />
3705 For 200 values or more, a distinct window will appear, to browse foreign
3706 key values and choose one.</p>
3710 automatically when entering Browse mode for a table?</a></h4>
3712 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3713 </p>
3717 Excel files, how can I enable that?</a></h4>
3719 <p> Current version does support direct export to Microsoft Excel and Word
3720 versions 2000 and newer. If you need export older versions, you can use
3722 which works out of the box or you can
3724 several problems, most important are limitation of cell content to 255
3725 chars and no support for charsets, so think carefully whether you want to
3726 enable this.</b>. For enabling this you need to set
3730 module Spreadsheet_Excel_Writer into php include path. The
3731 installation can be done by following command:</p>
3733 <pre>
3734 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3735 </pre>
3737 <p> First part of switches set we want to install beta version of that module
3738 (no stable version available yet) and then we tell pear we want to satisfy
3739 dependencies.</p>
3741 <p> If you are running in PHP safe mode, you will have to set
3744 modules are located, for example:</p>
3746 <pre>
3747 safe_mode_include_dir = /usr/local/lib/php
3748 </pre>
3752 <pre>
3753 cd phpMyAdmin
3754 mkdir tmp
3755 chmod o+rwx tmp
3756 </pre>
3760 what happens to my column comments stored in pmadb?</a></h4>
3762 <p> Automatic migration of a table's pmadb-style column comments to the native
3763 ones is done whenever you enter Structure page for this table.</p>
3770 <p> Our Bug Tracker is located at
3772 under the Bugs section.<br /><br />
3774 But please first discuss your bug with other users:<br />
3780 existing language, where do I start?</a></h4>
3782 <p> Always use the current SVN version of your language file.
3784 don't know how to get the SVN version, please ask one of the developers.
3785 <br />
3786 Please note that we try not to use HTML entities like &eacute; in
3787 the translations, since we define the right character set in the file.
3788 With HTML entities, the text on JavaScript messages would not
3789 display correctly.
3790 However there are some entities that need to be there, for quotes
3791 ,non-breakable spaces, ampersands, less than, greater than.<br />
3792 You can then put your translations, as a zip file to avoid losing special
3793 characters, on the sourceforge.net translation tracker.<br />
3794 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3795 list, because this is where we ask for translations of new messages.</p>
3799 phpMyAdmin. How should I proceed?</a></h4>
3805 </li>
3807 <li>generate patch with your changes:
3809 </li>
3812 tracker of the phpMyAdmin project</a>.
3813 </li>
3814 </ol>
3816 <p> Write access to the SVN tree is granted only to experienced developers who
3817 have already contributed something useful to phpMyAdmin.<br />
3823 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3825 <p> Please refer to
3826 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3827 </p>
3829 <!-- DEVELOPERS -->
3832 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3833 great features have been written by other people and you too can help to
3834 make phpMyAdmin a useful tool.</p>
3836 <p> If you're planning to contribute source, please read the following
3837 information:</p>
3843 it free from other code.<br />
3844 Commonly used functions should be added to
3847 <li>Obviously, you're free to use whatever coding style you want. But
3848 please try to keep your code as simple as possible: beginners are
3849 using phpMyAdmin as an example application.<br />
3850 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3851 compliant on one hand, they fit the
3854 coding standards</a>
3855 on the other hand. Please pay attention to this.</li>
3856 <li>Please try to keep up the file-naming conventions. Table-related stuff
3859 <li>Please don't use verbose strings in your code, instead add the string
3864 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3865 better debug and profile their code.<br />
3866 Please see the
3868 options for more information.<br />
3869 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3870 lost during its re-entry into Earth's atmosphere and in memory of the
3871 brave men and women who gave their lives for the people of Earth.</li>
3872 </ul>
3874 <!-- CREDITS -->
3877 <pre>
3878 phpMyAdmin - Credits
3879 ====================
3881 CREDITS, in chronological order
3882 -------------------------------
3885 * creator of the phpmyadmin project
3889 * multi-language version
3890 * various fixes and improvements
3892 * current project maintainer
3895 * started SourceForge phpMyAdmin project in March 2001
3896 * sync'ed different existing CVS trees with new features and bugfixes
3897 * multi-language improvements, dynamic language selection
3898 * current project maintainer
3899 * many bugfixes and improvements
3902 * rewrote and optimized javascript, DHTML and DOM stuff
3903 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
3904 generate XHTML1.0 and CSS2 compliant codes
3905 * improved the language detection system
3906 * many bugfixes and improvements
3909 * database maintenance controls
3910 * table type code
3912 * DB-based configuration (Not completed)
3915 * many bugfixes and improvements
3918 * bookmarks feature
3919 * multiple dump feature
3920 * gzip dump feature
3921 * zip dump feature
3924 * various fixes
3925 * moderator of the phpMyAdmin former users forum at phpwizard.net
3931 * rewrote and fix dump code
3932 * bugfixes
3935 * rewrote dump code for PHP4
3936 * mySQL table statistics
3937 * bugfixes
3940 * main author of the version 2.1.0.1
3941 * bugfixes
3945 * abstract database interface (PMA_DBI) with MySQLi support
3946 * privileges administration
3948 * various features and fixes
3949 * German language file updates
3952 * automatic joins in QBE
3953 * links column in printview
3954 * Relation view
3957 * enhanced index creation/display feature
3958 * feature to use a different charset for HTML than for MySQL
3959 * improvements of export feature
3960 * various features and fixes
3961 * Czech language file updates
3964 (http://sf.net/projects/phpmysqlformgen/)
3965 * suggested the patch for multiple table printviews
3968 * built the patch for vertical display of table rows
3969 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
3970 * Improvement of column/db comments
3971 * (MIME)-Transformations for columns
3972 * Use custom alias names for Databases in left frame
3973 * hierarchical/nested table display
3974 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
3975 * new icon sets
3976 * vertical display of column properties page
3977 * some bugfixes, features, support, German language additions
3980 * japanese kanji encoding conversion feature
3983 * the Cookie authentication mode
3986 * table relation-links feature
3989 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
3990 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
3991 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
3997 * phpMyAdmin logo (until June 2004)
4000 * blowfish library from the Horde project
4003 * mysqli support
4004 * many bugfixes and improvements
4007 * redesign for 2.6.0
4008 * phpMyAdmin sailboat logo (June 2004)
4011 * Representation at conferences
4014 * interface improvements
4015 * various bugfixes
4017 And also to the following people who have contributed minor changes,
4018 enhancements, bugfixes or support for a new language since version 2.1.0:
4020 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4021 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4022 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4023 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4025 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4026 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4027 Luís V., Martijn W. van der Lee,
4028 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4032 Original Credits of Version 2.1.0
4033 ---------------------------------
4035 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4036 to create a web-based interface to MySQL using PHP3. Although I have not
4037 used any of his source-code, there are some concepts I've borrowed from
4038 him. phpMyAdmin was created because Peter told me he wasn't going to
4039 further develop his (great) tool.
4040 Thanks go to
4042 code for the check when dropping a table or database. He also suggested
4043 that you should be able to specify the primary key on tbl_create.php3. To
4044 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4045 well as a bug-report. Plus many smaller improvements.
4047 were introduced in 1.3.0 (including quite significant ones like the
4048 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4049 bug-fixes and help.
4051 language-independent by outsourcing the strings to a separate file. He
4052 also contributed the French translation.
4054 tbl_select.php3, a feature to display only some fields from a table.
4056 functions in tbl_change.php3. He also added the
4059 servers and is a regular contributor for bug-fixes.
4061 features for 2.0.6.
4062 The following people have contributed minor changes, enhancements, bugfixes
4063 or support for a new language:
4064 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4065 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4066 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4067 G. Wieggers.
4069 And thanks to everyone else who sent me email with suggestions, bug-reports
4070 and or just some feedback.
4071 </pre>
4077 <ul>
4079 - the default name of Apache's directory-level configuration file.</li>
4083 - a software application that enables a user to display and interact with
4084 text, images, and other information typically located on a web page at a
4085 website on the World Wide Web.</li>
4087 - a free software/open source data compression algorithm and program
4088 developed by Julian Seward.</li>
4090 - an important World Wide Web technology that enables a client web browser
4091 to request data from a program executed on the Web server.</li>
4093 - a log or record of changes made to a project.</li>
4095 - a computer system that accesses a (remote) service on another computer
4096 by some kind of network.</li>
4098 - a set of data values of a particular simple type, one for each row of
4099 the table.</li>
4101 - a packet of information sent by a server to a World Wide Web browser
4102 and then sent back by the browser each time it accesses that server.</li>
4104 - Comma-seperated values</li>
4107 - an organized collection of data.</li>
4110 - a PHP module that extends PHP with additional functionality.</li>
4112 - a list of commonly asked question and there answers.</li>
4114 - one part of divided data/columns.</li>
4116 - a field or group of fields in a database record that point to a key
4117 field or group of fields forming a key of another database record in some
4118 (usually different) table.</li>
4120 - the free PDF library</li>
4122 GD Graphics Library</a> - a library by Thomas Boutell and others for
4123 dynamically manipulating images.</li>
4126 - gzip is short for GNU zip, a GNU free software file compression
4127 program.</li>
4129 - any machine connected to a computer network, a node that has a hostname.</li>
4131 - the unique name by which a network attached device is known on a network.</li>
4133 (HyperText Transfer Protocol)</a>
4134 - the primary method used to transfer or convey information on the World
4135 Wide Web.</li>
4138 additional security measures.</li>
4139 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4140 - a set of Internet-based services for servers using Microsoft Windows.</li>
4142 - a feature that allows quick access to the rows in a table.</li>
4144 - a data-oriented protocol used by source and destination hosts for
4145 communicating data across a packet-switched internetwork.</li>
4147 - a unique number that devices use in order to identify and communicate
4148 with each other on a network utilizing the Internet Protocol standard.</li>
4150 (Internet Server Application Programming Interface)</a>
4151 - the API of Internet Information Services (IIS).</li>
4153 - a business or organization that offers users access to the Internet and related services.</li>
4155 - a most commonly used standard method of lossy compression for
4156 photographic images.</li>
4162 - line of personal computers is designed, developed, manufactured, and
4163 marketed by Apple Computer.</li>
4164 <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>
4165 - the operating system which is included with all currently shipping Apple
4166 Macintosh computers in the consumer and professional markets.</li>
4168 - a cryptographic library.</li>
4170 - the MCrypt PHP extension.</li>
4171 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4172 - an Internet Standard for the format of e-mail.</li>
4174 - some sort of extension for the Apache Webserver.</li>
4176 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4177 Management System (DBMS).</li>
4179 - the improved MySQL client PHP extension.</li>
4181 - the MySQL client PHP extension.</li>
4183 - open standard for office documents.</li>
4184 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4185 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4187 (Portable Document Format)</a>
4188 - a file format developed by Adobe Systems for representing two
4189 dimensional documents in a device independent and resolution independent
4190 format.</li>
4192 - the PHP Extension and Application Repository.</li>
4194 - the perl-compatible regular expression functions for PHP</li>
4196 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4197 programming language used mainly for developing server-side applications
4198 and dynamic web content, and more recently, a broader range of software
4199 applications.</li>
4201 - a connection through which data is sent and received.</li>
4203 - Request for Comments (RFC) documents are a series of memoranda
4204 encompassing new research, innovations, and methodologies applicable to
4205 Internet technologies.</li>
4209 - represents a single, implicitly structured data item in a table.</li>
4211 - a computer system that provides services to other computing
4212 systems over a network.</li>
4213 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4214 - handlers for different table types</li>
4216 - a form of inter-process communication.</li>
4218 Sockets Layer)</a>
4219 - a cryptographic protocol which provides secure communication on the Internet.</li>
4221 - Structured Query Language</li>
4223 - a set of data elements (cells) that is organized, defined and stored as
4224 horizontal rows and vertical columns where each item can be uniquely
4225 identified by a label or key or by it?s position in relation to other items.</li>
4228 - a type of archive file format: the Tape ARchive format.</li>
4230 - one of the core protocols of the Internet protocol suite.</li>
4234 - a sequence of characters, conforming to a standardized format, that is
4235 used for referring to resources, such as documents and images on the
4236 Internet, by their location.</li>
4238 - A computer (program) that is responsible for accepting HTTP requests
4239 from clients and serving them Web pages.</li>
4241 - a W3C-recommended general-purpose markup language for creating
4242 special-purpose markup languages, capable of describing many different
4243 kinds of data.</li>
4245 - a popular data compression and archival format.</li>
4247 - an open-source, cross-platform data compression library by Jean-loup
4248 Gailly and Mark Adler.</li>
4249 </ul>
4259 </body>
4260 </html>