| blob | 2a747abf8304b084b9d1e11ced42655db83736af |
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>
42 <li>Local documents:
46 </ul>
47 </li>
48 <li>Documentation version:
50 </li>
51 </ul>
53 <!-- REQUIREMENTS -->
60 </li>
61 <li>You need GD2 support in PHP to display inline
63 original aspect ratio</li>
66 </ul>
67 </li>
71 PHP extension on your web server accelerates not only the login
72 phase but every other action that you do in phpMyAdmin.</li>
74 </ul>
76 <!-- INTRODUCTION -->
79 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
80 a single database. To accomplish the latter you'll need a properly set up
81 MySQL user who can read/write only the desired database. It's up to you to
82 look up the appropriate part in the MySQL manual.
83 </p>
88 <li>create, copy, drop, rename and alter databases, tables, fields and
89 indexes</li>
90 <li>maintenance server, databases and tables, with proposals on server
91 configuration</li>
92 <li>execute, edit and bookmark any
94 batch-queries</li>
97 </li>
104 OpenDocument Text and Spreadsheet,
106 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
107 </li>
111 <li>using Query-by-example (QBE), create complex queries automatically
112 connecting required tables</li>
114 your Database layout</li>
116 <li>transform stored data into any format using a set of predefined
117 functions, like displaying BLOB-data as image or download-link
118 </li>
124 </li>
125 </ul>
128 <p> Many people have difficulty
129 understanding the concept of user management with regards to phpMyAdmin. When
130 a user logs in to phpMyAdmin, that username and password are passed directly
131 to MySQL. phpMyAdmin does no account management on its own (other than
132 allowing one to manipulate the MySQL user account information); all users
133 must be valid MySQL users.</p>
142 <!-- INSTALLATION -->
150 </ol>
153 phpMyAdmin does not apply any special security methods to the MySQL database
154 server. It is still the system administrator's job to grant permissions on
156 be used for this.
157 </p>
165 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
166 before uploading them to your server, as PHP seems not to like
171 <ol><li>Untar or unzip the distribution (be sure to unzip the subdirectories):
173 document root. If you don't have direct access to your document root,
174 put the files in a directory on your local machine, and, after step 3,
175 transfer the directory on your web server using, for example, ftp.</li>
176 <li>Ensure that all the scripts have the appropriate owner (if PHP is
177 running in safe mode, having some scripts with an owner different
178 from the owner of other scripts will be a
183 <li>Now you must configure your installation. There are two methods that
184 can be used. Traditionally, users have hand-edited a copy of
185 config.inc.php, but now a wizard-style setup script is provided for
186 those who prefer a graphical installation. Creating a config.inc.php is
187 still a quick way to get started and needed for some advanced features.
188 <ul><li>To manually create the file, simply use your text editor to
191 file) in the main (top-level) phpMyAdmin directory (the one
195 default value is okay for a particular setting, there is no
197 few directives to get going, a simple configuration may look
198 like this:
199 <pre>
200 <?php
201 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
203 $i=0;
204 $i++;
205 $cfg['Servers'][$i]['auth_type'] = 'cookie';
206 ?>
207 </pre>
208 Or, if you prefer to not be prompted every time you log in:
209 <pre>
210 <?php
212 $i=0;
213 $i++;
214 $cfg['Servers'][$i]['user'] = 'root';
215 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
216 ?>
217 </pre>
218 For a full explanation of possible configuration values, see the
224 directory. This is a security measure. On a Linux/Unix system you
225 can use the following commands:
226 <pre>
227 cd phpMyAdmin
228 mkdir config # create directory for saving
229 chmod o+rw config # give it world writable permissions
230 </pre>
231 And to edit an existing configuration, copy it over first:
232 <pre>
233 cp config.inc.php config/ # copy current configuration for editing
234 chmod o+w config/config.inc.php # give it world writable permissions
235 </pre>
236 On other platforms, simply create the folder and ensure that your
245 the webserver does not have the proper permissions you may see the
247 config/</tt> directory exists and has the proper permissions -
249 and upload (via FTP or some similar means) to the proper location.<br /><br />
251 Once the file has been saved, it must be moved out of the <tt>
252 config/</tt> directory and the permissions must be reset, again
253 as a security measure:
254 <pre>
255 mv config/config.inc.php . # move file to current directory
256 chmod o-rw config.inc.php # remove world read and write permissions
257 </pre>
258 Now the file is ready to be used. You can choose to review or edit
259 the file with your favorite editor, if you prefer to set some
260 advanced options which the setup script does not provide.</li></ul></li>
261 <li>If you are using the
263 protect the phpMyAdmin installation directory because using
264 config does not require a user to
265 enter a password to access the phpMyAdmin installation. Use of an alternate
266 authentication method is recommended, for example with
274 in your browser. phpMyAdmin should now display a welcome screen
275 and your databases, or a login dialog if using
277 authentication mode.</li>
279 webserver configuration. For Apache you can use supplied .htaccess file
280 in that folder, for other webservers, you should configure this yourself.
281 Such configuration prevents from possible path exposure and cross side
282 scripting vulnerabilities that might happen to be found in that code.</li>
283 </ol>
287 <p> For a whole set of new features (bookmarks, comments,
290 transformation, etc.) you need to create a set of special tables. Those
291 tables can be located in your own database, or in a central database for a
292 multi-user installation (this database would then be accessed by the
293 controluser, so no other user should have rights to it).</p>
302 installation.</p>
307 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
308 that you may need special (administrator) privileges to create the database
309 and tables, and that the script may need some tuning, depending on the
310 database name.</p>
315 section</a>. You will also need to have a controluser with the proper rights
322 unpacked one. Configuration files from very old versions (2.3.0 or older) may
323 require some tweaking as some options have been changed or removed.</p>
327 is version-specific.</p>
330 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
331 you should run the SQL script found in
338 where you want to give users access to their own database and don't want
339 them to play around with others.<br />
340 Nevertheless be aware that MS Internet Explorer seems to be really buggy
342 in this area!<br />
345 that your user/password pair are not in clear in the configuration file.
346 </li>
349 authentication modes are more secure: the MySQL login information does
350 not need to be set in the phpMyAdmin configuration file (except possibly
352 However, keep in mind that the password travels in plain text, unless
353 you are using the HTTPS protocol.<br />
354 In cookie mode, the password is stored, encrypted with the blowfish
355 algorithm, in a temporary cookie.</li>
358 your MySQL server is older than 4.1.2, or is running with
368 file under the
370 $cfg['Servers'][$i]['controluser']</a></tt> and
375 only an example: use something else in your file!</b> Input these
376 statements from the phpMyAdmin SQL Query window or mysql command–line
377 client.<br />
379 if it's not the same as the MySQL server's one.
381 <pre>
382 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
383 GRANT SELECT (
384 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
385 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
386 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
387 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
388 Execute_priv, Repl_slave_priv, Repl_client_priv
389 ) ON mysql.user TO 'pma'@'localhost';
390 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
391 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
392 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
393 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
395 If you are using an old MySQL version (below 4.0.2), please replace
396 the first GRANT SELECT query by this one:
398 <pre>
399 GRANT SELECT (
400 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
401 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
402 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
403 ) ON mysql.user TO 'pma'@'localhost';</pre>
405 ... and if you want to use the many new relation and bookmark features:
407 <pre>
409 </pre>
413 Of course, the above queries only work if your MySQL version supports
417 on a set of particular databases. Normally you shouldn't give global
418 privileges to an ordinary user, unless you understand the impact of those
419 privileges (for example, you are creating a superuser).<br />
423 <pre>
424 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
425 </pre>
427 What the user may now do is controlled entirely by the MySQL user
428 management system.<br />
430 authentication mode, you don't need to fill the user/password fields
432 array.</li>
433 </ul>
438 method and allows you to log in as any valid MySQL user.</li>
439 <li>Is supported with most PHP configurations. For
452 mode.</li>
453 </ul>
457 <ul><li>You can use this method as a replacement for the
459 (for example, if you're running
461 <li>Obviously, the user must enable cookies in the browser, but this is
462 now a requirement for all authentication modes.</li>
463 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
464 with the same username.</li>
465 <li>If you want to log in to arbitrary server see
470 not required.</li>
471 </ul>
475 <ul><li>This mode is the less secure one because it requires you to fill the
477 $cfg['Servers'][$i]['user']</a> and
479 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
480 can read your config.inc.php can discover your username and password).
481 <br />
488 is an entry explaining how to protect your configuration file.</li>
489 <li>For additional security in this mode, you may wish to consider the Host
490 authentication
492 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
494 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
495 directives.</li>
496 <li>Unlike cookie and http, does not require a user to log in when first
497 loading the phpMyAdmin site. This is by design but could allow any
498 user to access your installation. Use of some restriction method is
500 HTTP-AUTH directive or disallowing incoming HTTP requests at
501 one’s router or firewall will suffice (both of which
502 are beyond the scope of this manual but easily searchable with Google).</li>
503 </ul>
505 <!-- CONFIGURATION -->
509 users:</span> PHP does not seem to like
513 before saving a script you have modified.</p>
518 section to create one. This file only needs to contain the parameters you want to
519 change from their corresponding default value in
522 <p> The parameters which relate to design (like colors) are placed in
525 your site specific code to be included on start and end of each page.</p>
529 (with full path) to your phpMyAdmin installation's directory.
532 some web servers are case–sensitive.
535 Starting with version 2.3.0, it is advisable to try leaving this
536 blank. In most cases phpMyAdmin automatically detects the proper
537 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
538 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
539 A good test is to browse a table, edit a row and save it. There should
540 be an error message if phpMyAdmin is having trouble auto–detecting
541 the correct value. If you get an error that this must be set or if
542 the autodetect code fails to detect your path, please post a bug
543 report on our bug tracker so we can improve the code.</dd>
547 with master / foreign – tables (see
549 <br />
550 If you tried to set this up and it does not work for you, have a look on
552 use it. You will find a link that will analyze why those features have
553 been disabled.<br />
554 If you do not want to use those features set this variable to
559 algorithm to encrypt the password.<br />
561 passphrase of your choice. It will be used internally by the blowfish
562 algorithm: you won’t be prompted for this passphrase. The maximum
567 MySQL servers. Therefore, a
569 been added which contains the login information for the different servers.
570 The first
572 contains the hostname of the first server, the second
574 the hostname of the second server, etc. In
576 server definition, however you can put as many as you need in
578 have to define all settings, just those you need to change).</dd>
582 $i-th MySQL-server. E.g. localhost.</dd>
587 ignores this port number and connects with the socket, so if you want
588 to connect to a port different from the default port, use
591 </dd>
595 To determine the correct socket, check your MySQL configuration or, using the
597 Among the resulting information displayed will be the socket used.</dd>
600 <dd>What type connection to use with the MySQL server. Your options are
602 is nearly guaranteed to be available on all MySQL servers, while
603 sockets are not supported on some platforms.<br /><br />
605 To use the socket mode, your MySQL server must be on the same machine
606 as the Web server.</dd>
609 <dd>What php MySQL extension to use for the connection. Valid options are:
610 <br /><br />
613 The classic MySQL extension. This is the recommended and default
614 method at this time.<br /><br />
617 The improved MySQL extension. This extension became available
618 with php 5.0.0 and is the recommended way to connect to a server
622 <dd>Whether to use a compressed protocol for the MySQL server connection
623 or not (experimental).<br />
629 </dt>
631 all relational features (see
633 and, for a MySQL server older than 4.1.2 or running with
636 authentication mode).<br /><br />
639 cookie authentication modes (or 'config'
640 authentication mode since phpMyAdmin 2.2.1), you need to supply the
645 This account is used to check what databases the user will see at
646 login.<br />
650 In phpMyAdmin versions before 2.2.5, those were called
655 <dd>Whether config or cookie or
657 should be used for this server.
659 is the plain old way: username and password are stored in
661 <li>'cookie' authentication mode
663 2.2.3 allows you to log in as any valid MySQL user with the
664 help of cookies. Username and password are stored in
665 cookies during the session and password is deleted when it
666 ends. This can also allow you to log in in arbitrary server if
667 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
668 </li>
669 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in older versions)
670 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
671 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
672 <li>'signon' authentication mode
674 as introduced in 2.10.0 allows you to log in from prepared PHP
675 session data. This is useful for implementing single signon
676 from another application. Sample way how to seed session is in
681 URL</a> to use this authentication method.
682 </ul>
685 for more information.
686 </dd>
690 </dt>
691 <dd>
692 When using auth_type = 'config', this is the user/password-pair
693 which phpMyAdmin will use to connect to the
694 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
695 cookie authentication is used and should be empty.</dd>
697 <span
699 </dt>
700 <dd>
701 Allow attempt to log in without password when a login with password
702 fails. This can be used together with http authentication, when
703 authentication is done some other way and phpMyAdmin gets user name
704 from auth and uses empty password for connecting to MySQL. Password
705 login is still tried first, but as fallback, no password method is
706 tried.</dd>
709 </dt>
710 <dd>
711 If set to a (an array of) database name(s), only this (these) database(s)
712 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
713 database(s) name(s) may contain MySQL wildcards characters
717 This setting is an efficient way to lower the server load since the
718 latter does not need to send MySQL requests to build the available
720 privileges rules of the MySQL database server</span>. If set, it just
721 means only these databases will be displayed but
723 <br /><br />
725 An example of using more that one database:
727 <br /><br />
729 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
730 databases in the left frame, so that you can individually arrange your databases.<br />
731 If you want to have certain databases at the top, but don't care about the others, you do not
732 need to specify all other databases. Use:
734 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
735 order.</dd>
738 </dt>
739 <dd>Regular expression for hiding some databases. This only hides them
740 from listing, but a user is still able to access them (using, for example,
741 the SQL query area). To limit access, use the MySQL privilege system.
742 <br /><br />
747 More information on regular expressions can be found in the
749 PCRE pattern syntax</a> portion of the PHP reference manual.
750 </dd>
753 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
754 this string will be displayed instead of the hostname in the pull-down
755 menu on the main page. This can be useful if you want to show only
756 certain databases on your system, for example.</dd>
760 </dt>
761 <dd>The name of the database containing the linked-tables infrastructure.
762 <br /><br />
765 section in this document to see the benefits of this infrastructure,
766 and for a quick way of creating this database and the needed tables.
767 <br /><br />
769 If you are the only user of this phpMyAdmin installation, you can
770 use your current database to store those special tables; in this
771 case, just put your current database name in
773 set this parameter to the name of your central database containing
774 the linked-tables infrastructure.</dd>
778 </dt>
780 useful for queries you often run.<br /><br />
782 To allow the usage of this functionality:
784 <li>enter the table name in
786 </ul>
787 </dd>
791 </dt>
793 which field is a key in another table (a foreign key). phpMyAdmin
794 currently uses this to
795 <ul><li>make clickable, when you browse the master table, the data values
796 that point to the foreign table;</li>
798 when browsing the master table, if you move the mouse to a column
799 containing a foreign key (use also the 'table_info' table);<br />
802 <li>in edit/insert mode, display a drop-down list of possible foreign
806 <li>display links on the table properties page, to check referential
807 integrity (display missing foreign keys) for each described key;
808 </li>
812 schema of your database (also uses the table_coords table).</li>
813 </ul>
815 The keys can be numeric or character.<br /><br />
817 To allow the usage of this functionality:
820 infrastructure</li>
821 <li>put the relation table name in
823 <li>now as normal user open phpMyAdmin and for each one of your
824 tables where you want to use this feature, click
826 </li>
827 </ul>
831 future development of the cross-db relations.
832 </dd>
836 </dt>
837 <dd>
838 Since release 2.3.0 you can describe, in a special 'table_info'
839 table, which field is to be displayed as a tool-tip when moving the
840 cursor over the corresponding key.<br />
841 This configuration variable will hold the name of this special
842 table. To allow the usage of this functionality:
844 <li>put the table name in
846 <li>then for each table where you want to use this feature,
848 to choose the field.</li>
849 </ul>
851 </dd>
855 </dt>
858 the relations between your tables. To do this it needs two tables
863 schema output).<br /><br />
867 To allow the usage of this functionality:
870 infrastructure</li>
871 <li>put the correct table names in
874 </ul>
877 </dd>
881 </dt>
883 Since release 2.3.0 you can store comments to describe each column for
885 <br /><br />
887 Starting with release 2.5.0, comments are consequently used on the table
888 property pages and table browse view, showing up as tool-tips above the
889 column name (properties page) or embedded within the header of table in
890 browse view. They can also be shown in a table dump. Please see the
891 relevant configuration directives later on.<br /><br />
893 Also new in release 2.5.0 is a MIME-transformation system which is also
895 Transformations</a> for further information. To use the
896 MIME-transformation system, your column_info table has to have the three
897 new fields 'mimetype', 'transformation', 'transformation_options'.
898 <br /><br />
900 To allow the usage of this functionality:
902 infrastructure</li>
903 <li>put the table name in
907 <pre>
908 ALTER TABLE `pma_column_comments`
909 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
910 ADD `transformation` VARCHAR( 255 ) NOT NULL,
911 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
912 </pre>
915 renamed from<br />
918 </ul>
919 </dd>
923 </dt>
926 all queries you entered manually into the phpMyAdmin interface. If you
927 don't want to use a table-based history, you can use the JavaScript-based
928 history. Using that, all your history items are deleted when closing the
929 window.<br /><br />
931 Using
933 you can specify an amount of history items you want to have on hold. On
934 every login, this list gets cut to the maximum amount.<br /><br />
936 The query history is only available if JavaScript is enabled in your
937 browser.<br /><br />
939 To allow the usage of this functionality:
942 infrastructure</li>
944 </li>
945 </ul>
946 </dd>
949 </dt>
951 column_info table got enhanced with three new fields. If the above variable
953 latest table structure available. If not, it will emit a warning to the
954 superuser.<br /><br />
956 You can disable this checking behavior by setting the variable to false,
957 which should offer a performance increase.<br /><br />
959 Recommended to set to FALSE, when you are sure, your table structure is
960 up to date.</dd>
962 boolean</dt>
963 <dd>Whether to allow root access. This is just simplification of rules below.
964 </dd>
967 </dt>
969 authentication is disabled.<br /><br />
972 all deny rules followed by allow rules. Access is allowed by default. Any
973 client which does not match a Deny command or does match an Allow command
974 will be allowed access to the server. <br /><br />
977 applies all allow rules followed by deny rules. Access is denied by
978 default. Any client which does not match an Allow directive or does
979 match a Deny directive will be denied access to the server.<br /><br />
981 If your rule order is set to 'explicit', the authentication is
982 performed in a similar fashion to rule order 'deny,allow', with the
986 and was available in Apache by specifying allow and deny rules without
987 setting any order.
988 </dd>
990 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
991 </dt>
992 <dd>The general format for the rules is as such:
994 <pre>
996 </pre>
1001 well (please note that those containing SERVER_ADDRESS might not be
1002 available on all webservers):
1003 <pre>
1009 </pre>
1011 Having an empty rule list is equivalent to either using
1017 following work:<br />
1019 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1020 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1021 But the following does not work:<br />
1024 </dd>
1025 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1026 <dd>Name of session which will be used for signon authentication method.
1027 </dd>
1029 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1030 </dd>
1032 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1033 </dd>
1036 <dd>If you have more than one server configured, you can set
1038 that server when phpMyAdmin is started, or set it to 0 to be given a
1039 list of servers without logging in.<br />
1041 MUST be set to that server.</dd>
1044 <dd>Defines whether to use GZip output buffering for increased
1046 Set to true/false for enabling/disabling. When set to 'auto' (string),
1047 phpMyAdmin tries to enable output buffering and will automatically disable
1048 it if your browser has some problems with buffering. IE6 with a certain patch
1049 is known to cause data corruption when having enabled buffering.</dd>
1052 <dd>Whether persistent connections should be used or not (mysql_connect or
1053 mysql_pconnect).</dd>
1059 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1060 to zero, no time limit is imposed.<br />
1061 This setting is used while importing/exporting dump files but has no
1062 effect when PHP is running in safe mode.</dd>
1065 <dd>Set the number of bytes a script is allowed to allocate. If number set
1066 to zero, no limit is imposed.<br />
1067 This setting is used while importing/exporting dump files but has no
1068 effect when PHP is running in safe mode.<br />
1072 <dd>Mark used tables and make it possible to show databases with locked
1077 generated by phpMyAdmin should be displayed or not.</dd>
1080 <dd>Defines whether normal users (non-administrator) are allowed to
1081 delete their own database or not. If set as FALSE, the link "Drop
1083 mydatabase" will be rejected. Quite practical for
1085 customers.<br />
1086 Please note that this limitation of SQL queries is not as strict as
1087 when using MySQL privileges. This is due to nature of SQL queries
1088 which might be quite complicated. So this choice should be viewed as
1089 help to avoid accidental dropping rather than strict privilege
1090 limitation.</dd>
1094 displayed when you're about to lose data.</dd>
1097 <dd>Define whether the previous login should be recalled or not in cookie
1098 authentication mode.</dd>
1105 means that it will be kept for existing session. This is recommended
1106 for not trusted environments.</dd>
1109 <dd>If enabled (default), logout deletes cookies for all servers,
1110 otherwise only for current one. Setting this to false makes it easy to
1111 forget to log out from other server, when you are using more of
1112 them.</dd>
1118 <dd>Define whether phpMyAdmin will continue executing a multi-query
1119 statement if one of the queries fails. Default is to abort execution.</dd>
1122 <dd>Define whether phpMyAdmin will output the results of each query of a
1123 multi-query statement embedded into the
1128 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1129 <br /><br />
1132 MySQL servers behind the firewall where your
1134 </dd>
1137 <dd>Defines whether to use a select-based menu and display only the current
1138 tables in the left frame (smaller page). Only in Non-Lightmode you can
1139 use the feature to display nested folders using
1141 </dd>
1144 <dd>In light mode, defines whether to display the names of databases (in the
1145 selector) using a tree, see also
1147 </dd>
1150 <dd>The string used to separate the parts of the database name when showing
1151 them in a tree.</dd>
1154 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1155 This means if you have tables like 'first__second__third' this will be
1157 If set to FALSE or empty, the feature is disabled. NOTE: You should
1158 not use this separator at the beginning or end of a
1159 table name or multiple times after another without any other
1160 characters in between.</dd>
1163 <dd>Defines how many sublevels should be displayed when splitting
1164 up tables by the above separator.</dd>
1167 <dd>Defines whether to display table comment as tool-tip in left frame or
1168 not.</dd>
1171 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1172 comment and the real name. That means that if you have a table called
1173 'user0001' and add the comment 'MyName' on it, you will see the name
1174 'MyName' used consequently in the left frame and the tool-tip shows
1175 the real name of the DB.</dd>
1178 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1180 When setting this to 'nested', the Alias of the Tablename is only used
1181 to split/nest the tables according to the
1183 directive. So only the folder is called like the Alias, the tablename itself
1184 stays the real tablename.</dd>
1187 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1190 <dd>Enter URL where logo in left frame will point to. For use especially
1191 with self made theme which changes this.</dd>
1193 <dd>Defines whether or not to display a server choice at the top of the left frame.
1194 Defaults to FALSE.</dd>
1196 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1197 Defaults to FALSE (drop-down).</dd>
1199 <dd>Defines whether or not to display space usage and statistics about databases
1200 and tables.<br />
1201 Note that statistics requires at least MySQL 3.23.3 and that, at this
1202 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1207 </dt>
1210 not at the starting main (right) frame. This setting
1211 does not check MySQL commands entered directly.<br /><br />
1213 Please note that to block the usage of phpinfo() in scripts, you
1220 hard coded password value in the configuration file, end users can't
1221 be allowed to change their passwords.</dd>
1224 <dd>Defines whether to suggest a database name on the
1229 content.</dd>
1232 <dd>Defines whether navigation bar buttons and the right panel top menu
1233 contain text or symbols only. A value of TRUE displays icons, FALSE
1234 displays text and 'both' displays both icons and text.</dd>
1237 <dd>Defines whether a user should be displayed a
1241 <dd>Number of rows displayed when browsing a result set. If the result set
1248 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1252 from editing when browsing a table's content. Valid values are:
1257 </ul>
1258 </dd>
1261 <dd>Defines whether or not MySQL functions fields should be displayed in
1262 edit/insert mode.</dd>
1265 <dd>Defines which type of editing controls should be used for CHAR and
1266 VARCHAR fields. Possible values are:
1267 <ul><li>input - this allows to limit size of text to size of field in
1268 MySQL, but has problems with newlines in fields</li>
1269 <li>textarea - no problems with newlines in fields, but also no
1270 length limitations</li>
1271 </ul>
1272 Default is old behavior so input.</dd>
1278 <dd>If there are fewer items than this in the set of foreign keys, then a
1279 drop-down box of foreign keys is presented, in the style described by the
1281 setting.</dd>
1284 <dd>For the foreign key drop-down fields, there are several methods of
1285 display, offering both the key and value data. The contents of the
1286 array should be one or both of the following strings:
1292 </dt>
1293 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1294 creating a dump file</dd>
1297 </dt>
1298 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1299 compressed exports. This doesn't affect smaller dumps and allows users to
1300 create larger dumps that won't otherwise fit in memory due to php
1301 memory limit. Produced files contain more GZip/BZip2 headers, but all
1302 normal programs handle this correctly.</dd>
1306 mainframe.</dd>
1310 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1315 <dd>How many columns will be utilized to display the tables on the
1316 database property view? Default is 1 column. When setting this to a
1317 value larger than 1, the type of the database will be omitted for more
1318 display space.</dd>
1322 <dd>Defines the tab displayed by default on server view. Possible
1329 <dd>Defines the tab displayed by default on database view. Possible
1334 <dd>Defines the tab displayed by default on table view. Possible
1341 points to the MySQL documentation (type depends
1342 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1343 generated.<br />
1345 for more information about MySQL manuals and their types.</dd>
1348 <dd>Type of MySQL documentation:
1354 </ul>
1355 </dd>
1358 <dd>Defines the default language to use, if not browser-defined or
1359 user-defined.<br />
1361 this setting.</dd>
1364 <dd>Defines the default connection collation to use, if not
1365 user-defined.<br />
1370 <dd>Force: always use this language (must be defined in the
1374 <dd>Limit list of available languages to those matching the given regular
1375 expression. For example if you want only Czech and English, you should
1379 <dd>Default character set to use for recoding of MySQL queries. This must be
1380 enabled and it's described by
1382 option.<br />
1383 You can give here any character set which is in
1385 array and this is just default choice, user can select any of them.</dd>
1388 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1389 support (compiled in or module) in PHP to allow MySQL queries recoding
1390 and used language file must have it enabled (by default only these
1391 which are in Unicode, just to avoid losing some characters).<br /><br />
1394 in the Export page, to choose the character set when exporting a file.
1395 </dd>
1398 <dd>You can select here which functions will be used for character set
1399 conversion. Possible values are:
1400 <ul><li>auto - automatically use available one (first is tested
1401 iconv, then recode)</li>
1404 </ul>
1405 Default is auto.</dd>
1408 <dd>Specify some parameters for iconv used in charset conversion. See
1411 used, so that invalid characters will be transliterated.</dd>
1414 <dd>Available character sets for MySQL conversion. You can add your own (any of
1415 supported by recode/iconv) or remove these which you don't use.
1416 Character sets will be shown in same order as here listed, so if you
1417 frequently use some of these move them to the top.</dd>
1421 MIME transformations.<br />
1422 Possible values are:
1423 <ul><li>auto - automatically detect, this is a bit expensive
1425 according to your server real possibilities</li>
1428 </ul>
1429 Default is auto.
1430 </dd>
1434 </dd>
1436 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1437 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1438 </dt>
1439 <dd>The background styles used for both the frames.
1442 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1444 <dd>The style used for the pointer in the navi frame.
1453 </dd>
1457 <dd>The style used for table headers. See
1462 </dd>
1466 </dd>
1468 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1470 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1472 </dt>
1474 The former feature highlights the row over which your mouse is passing
1475 and the latter lets you visually mark/unmark rows by clicking on
1476 them.<br />
1481 <dd>You put here a valid CSS font family value, for example
1486 <dd>You put here a valid CSS font family value, for example
1500 </dt>
1502 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1504 The Char* values are used for CHAR and VARCHAR editing (if configured
1508 </dt>
1512 </dt>
1513 <dd>Defines if the whole textarea of the query box will be selected on
1514 click.</dd>
1517 </dt>
1518 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1519 editing.</dd>
1522 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1523 Can be turned off by a toggle button on the browse page.</dd>
1527 </dt>
1528 <dd>Defines the place where modify and delete links would be put when
1529 tables contents are displayed (you may have them displayed both at the
1530 left and at the right).
1536 </dt>
1538 Define which one is displayed by default. The first mode displays each
1539 row on a horizontal line, the second rotates the headers by 90
1540 degrees, so you can use descriptive headers even though fields only
1541 contain small values and still print them out. The vertical mode sorts
1542 each row on a vertical lineup.<br /><br />
1544 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1545 the rotation of the header for horizontalflipped is done via CSS. If
1546 set to 'fake' PHP does the transformation for you, but of course this
1547 does not look as good as CSS.</dd>
1551 <dd>When editing/creating new columns in a table all fields normally get
1552 lined up one field a line. (default: 'horizontal'). If you set this to
1553 'vertical' you can have each field lined up vertically beneath each
1554 other. You can save up a lot of place on the horizontal direction and
1555 no longer have to scroll.</dd>
1559 </dt>
1561 display of column comments in Browse or Property display. In browse
1562 mode, the comments are shown inside the header. In property mode,
1563 comments are displayed using a CSS-formatted dashed-line below the
1564 name of the field. The comment is shown as a tool-tip for that field.
1565 </dd>
1568 <dd>
1569 The name of the directory where
1571 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1572 are available under a drop-down box when you click the database name,
1574 <br /><br />
1576 If you want different directory for each user, %u will be replaced
1577 with username.<br /><br />
1581 compressed formats is enabled).<br /><br />
1583 This feature is useful when your file is too big to be uploaded via
1585 uploads are disabled in PHP.<br /><br />
1587 Please note that if PHP is running in safe mode, this directory must
1588 be owned by the same user as the owner of the phpMyAdmin scripts.
1589 <br /><br />
1593 alternatives.
1594 </dd>
1597 <dd>
1598 The name of the directory where docSQL files can be uploaded for
1599 import into phpMyAdmin.
1600 <br /><br />
1601 Please note that if PHP is running in safe mode, this directory must
1602 be owned by the same user as the owner of the phpMyAdmin scripts.
1603 </dd>
1606 <dd>
1607 The name of the directory where dumps can be saved.<br /><br />
1609 If you want different directory for each user, %u will be replaced
1610 with username.<br /><br />
1612 Please note that the directory has to be writable for user running
1613 webserver.<br /><br />
1615 Please note that if PHP is running in safe mode, this directory must
1616 be owned by the same user as the owner of the phpMyAdmin scripts.
1617 </dd>
1620 <dd>
1621 The name of the directory where temporary files can be stored.
1622 <br /><br />
1623 This is needed for native MS Excel export, see
1626 </dd>
1629 <dd>
1630 In this array are defined default parameters for export, names of
1631 items are similar to texts seen on export page, so you can easily
1632 identify what they mean.
1633 </dd>
1636 <dd>
1637 In this array are defined default parameters for import, names of
1638 items are similar to texts seen on import page, so you can easily
1639 identify what they mean.
1640 </dd>
1643 <dd>
1644 Repeat the headers every X cells, or 0 to deactivate.
1645 </dd>
1653 </dt>
1654 <dd>
1655 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1656 or icon is always displayed on the left panel. If JavaScript is enabled in
1657 your browser, a click on this opens a distinct query window, which is
1658 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1659 changes to display a query box.<br /><br />
1661 The size of this query window can be customized with
1663 - both integers for the size in pixels. Note that normally, those
1665 theme you are using.<br /><br />
1669 opens the query window and puts the current query
1670 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1671 query in the right panel's query box.
1672 <br /><br />
1673 The usage of the JavaScript query window is recommended if you have a
1674 JavaScript enabled browser. Basic functions are used to exchange quite
1675 a few variables, so most 4th generation browsers should be capable to
1676 use that feature. It currently is only tested with Internet Explorer 6
1677 and Mozilla 1.x.
1678 <br /><br />
1680 to a table, which has to be created by you (see <a
1682 all your queries will be appended to the form, but only as long as
1683 your window is opened they remain saved.
1684 <br /><br />
1685 When using the JavaScript based query window, it will always get
1686 updated when you click on a new table/db to browse and will focus if
1687 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1688 the query window by checking the box "Do not overwrite this query from
1689 outside the window" below the query textarea. Then you can browse
1690 tables/databases in the background without losing the contents of the
1691 textarea, so this is especially useful when composing a query with
1692 tables you first have to look in. The checkbox will get automatically
1693 checked whenever you change the contents of the textarea. Please
1694 uncheck the button whenever you definitely want the query window to
1695 get updated even though you have made alterations.
1696 <br /><br />
1699 <br /><br />
1700 The query window also has a custom tabbed look to group the features.
1702 default tab to be used when opening the query window. It can be set to
1703 either 'sql', 'files', 'history' or 'full'.</dd>
1709 <dd><ul><li>For InnoDB tables, determines for how large tables phpMyAdmin
1711 If the approximate row count as returned by
1714 count will be used.</li>
1715 <li>For VIEWs, since obtaining the exact count could have an
1716 impact on performance, this value is the maximum to be displayed.
1717 </li>
1718 </ul>
1719 </dd>
1723 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1725 page. By clicking on the button 'toggle scratchboard' on the page
1726 where you edit x/y coordinates of those elements you can activate a
1727 scratchboard where all your elements are placed. By clicking on an
1728 element, you can move them around in the pre-defined area and the x/y
1729 coordinates will get updated dynamically. Likewise, when entering a
1730 new position directly into the input field, the new position in the
1731 scratchboard changes after your cursor leaves the input field.<br />
1732 You have to click on the 'OK'-button below the tables to save the new
1733 positions. If you want to place a new element, first add it to the
1734 table of elements and then you can drag the new element around.<br />
1735 By changing the paper size and the orientation you can change the size
1736 of the scratchboard as well. You can do so by just changing the
1737 dropdown field below, and the scratchboard will resize automatically,
1738 without interfering with the current placement of the elements.<br />
1739 If ever an element gets out of range you can either enlarge the paper
1740 size or click on the 'reset' button to place all elements below each
1741 other.<br />
1743 get this control to work. The basic Drag&Drop script functionality
1744 was kindly borrowed from www.youngpup.net and is underlying so
1745 specific license.</dd>
1748 <dd>Sorts database and table names according to natural order (for example,
1749 t1, t2, t10). Currently implemented in the left panel (Light mode)
1750 and in Database view, for the table list.</dd>
1756 <dd>Allows you to specify window's title bar. Following magic string can
1757 be used to get special values:
1758 <dl>
1764 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1773 </dl>
1774 </dd>
1784 </dd>
1787 <dd>If theme manager is active, use this as the path of the subdirectory
1788 containing all the themes.</dd>
1802 </dt>
1803 <dd>Default queries that will be displayed in query boxes when user didn't
1804 specify any. Use %d for database name, %t for table name and %f for a
1805 comma separated list of field names. Note that %t and %f are only
1809 <dd>
1810 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
1811 default we use HTML to format the query, but you can disable this by
1813 </dd>
1816 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1817 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1818 query inside a bracket is indented. By changing
1821 specifies the units of the indent amount that you specified. This is
1822 used via stylesheets.</dd>
1825 <dd>This array is used to define the colours for each type of element of
1826 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1828 If you specify an empty string for the color of a class, it is ignored
1829 in creating the stylesheet.
1830 You should not alter the class names, only the colour strings.<br />
1851 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1855 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1856 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1857 </ul>
1858 </dd>
1862 <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,
1863 as originally published on
1865 <br />
1866 For help in setting up your system to use the service, see the
1868 </dd>
1872 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1873 and any password, so we use those by default. Instead, if
1874 you have an account with them, you can put your login details
1875 here, and it will be used in place of the anonymous login.</dd>
1876 </dl>
1877 </dd>
1880 <dd><b>DEVELOPERS ONLY!</b></dd>
1883 <dd><b>DEVELOPERS ONLY!</b><br />
1884 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1885 the code.<br />
1886 For help in setting up your system to this, see the
1890 <dd><b>DEVELOPERS ONLY!</b><br />
1891 Enable profiling support for phpMyAdmin. This will append a chunk of data
1892 to the end of every page displayed in the main window with profiling
1893 statistics for that page.<br />
1894 You may need to increase the maximum execution time for this to
1895 complete successfully.<i>Profiling was removed from the code for
1896 version 2.9.0 due to licensing issues.</i></dd>
1898 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
1899 <dd><b>DEVELOPERS ONLY!</b><br />
1900 When profiling data is displayed, this variable controls the threshold of
1901 display for any profiling data, based on the average time each time has
1902 taken. If it is over the threshold it is displayed, otherwise it is not
1903 displayed. This takes a value in milliseconds. In most cases you don't need
1904 to edit this.</dd>
1907 <dd>All possible types of a MySQL column. In most cases you don't need to
1908 edit this.</dd>
1911 <dd>Possible attributes for fields. In most cases you don't need to edit
1912 this.</dd>
1915 <dd>A list of functions MySQL supports. In most cases you don't need to
1916 edit this.</dd>
1919 <dd>Mapping of column types to meta types used for preferring displayed
1920 functions. In most cases you don't need to edit this.</dd>
1923 <dd>Functions preferred for column meta types as defined in
1924 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
1925 to edit this.</dd>
1928 <dd>Functions selected by default when inserting/changing row, Functions
1929 are defined for meta types from
1931 <code>first_timestamp</code>, which is used for first timestamp column
1932 in table.</dd>
1935 <dd>Operators available for search operations on numeric and date fields.
1936 </dd>
1939 <dd>Operators available for search operations on character fields.
1940 Note that we put <code>LIKE</code> by default instead of
1941 <code>LIKE %...%</code>, to avoid unintended performance problems
1942 in case of huge tables.</dd>
1945 <dd>Operators available for search operations on enum fields.</dd>
1948 <dd>Additional operators available for search operations when the
1949 field can be null.</dd>
1951 </dl>
1953 <!-- TRANSFORMATIONS -->
1959 </ol>
1963 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
1965 section</a> on how to do so.</p>
1967 <p> You can apply different transformations to the contents of each field. The
1968 transformation will take the content of each field and transform it with
1969 certain rules defined in the selected transformation.</p>
1971 <p> Say you have a field 'filename' which contains a filename. Normally you would
1972 see in phpMyAdmin only this filename. Using transformations you can transform
1973 that filename into a HTML link, so you can click inside of the phpMyAdmin
1974 structure on the field's link and will see the file displayed in a new browser
1975 window. Using transformation options you can also specify strings to
1976 append/prepend to a string or the format you want the output stored in.</p>
1978 <p> For a general overview of all available transformations and their options,
1979 you can consult your
1980 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
1981 installation.</p>
1983 <p> For a tutorial on how to effectively use transformations, see our
1985 the official phpMyAdmin homepage.</p>
1989 <p> Go to your <i>tbl_properties_structure.php</i> page (i.e. reached through
1990 clicking on the 'Structure' link for a table). There click on
1991 "Change" (or change icon) and there you will see three new fields at
1992 the end of the line. They are called 'MIME-type', 'Browser transformation' and
1993 'Transformation options'.</p>
1995 <ul><li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
1996 empty or to use 'auto' [this feature is not yet available]. Please note that
1997 transformations are inactive as long as no MIME-type is selected.</li>
1999 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2000 hopefully growing amount of pre-defined transformations. See below for information on
2001 how to build your own transformation.<br />
2003 There are global transformations and mimetype-bound transformations. Global transformations
2004 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2005 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2006 transformations which operate on the main mimetype (like 'image'), which will most likely
2007 take the subtype into regard, and those who only operate on a
2008 specific subtype (like 'image/jpeg').<br />
2010 You can use transformations on mimetypes for which the function was not defined for. There
2011 is no security check for you selected the right transformation, so take care of what the
2012 output will be like.</li>
2014 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2015 transform-function specific options here. Usually the transforms can operate with default
2016 options, but it is generally a good idea to look up the overview to see which options are
2017 necessary.<br />
2019 Much like the ENUM/SET-Fields, you have to split up several options using the format
2020 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2021 parsed as an array, leaving the first value the first element in the array, and so
2022 forth.<br />
2024 If you want to specify a MIME character set you can define it in the transformation_options.
2025 You have to put that outside of the pre-defined options of the specific mime-transform,
2027 for which you can specify 2 options and you want to append a character set, enter "'first
2028 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2030 </ul>
2034 <p> All mimetypes and their transformations are defined through single files in
2035 the directory 'libraries/transformations/'.</p>
2037 <p> They are stored in files to ease up customization and easy adding of new
2038 transformations.</p>
2040 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2041 always work. It makes no sense to apply a transformation to a mimetype, the
2042 transform-function doesn't know to handle.</p>
2044 <p> One can, however, use empty mime-types and global transformations which should work
2045 for many mimetypes. You can also use transforms on a different mimetype they where built
2046 for, but pay attention to option usage as well as what the transformation does to your
2047 field.</p>
2049 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2050 any other transform function and provides some basic functions.</p>
2052 <p> There are 5 possible file names:</p>
2054 <ol><li>A mimetype+subtype transform:<br /><br />
2056 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2058 Please not that mimetype and subtype are separated via '_', which shall
2059 not be contained in their names. The transform function/filename may
2060 contain only characters which cause no problems in the file system as
2061 well as the PHP function naming convention.<br /><br />
2063 The transform function will the be called
2064 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2066 <b>Example:</b><br /><br />
2068 <tt>text_html__formatted.inc.php</tt><br />
2069 <tt>PMA_transform_text_html__formatted()</tt></li>
2071 <li>A mimetype (w/o subtype) transform:<br /><br />
2073 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2075 Please note that there are no single '_' characters.
2076 The transform function/filename may contain only characters which cause
2077 no problems in the file system as well as the PHP function naming
2078 convention.<br /><br />
2080 The transform function will the be called
2081 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2083 <b>Example:</b><br /><br />
2085 <tt>text__formatted.inc.php</tt><br />
2086 <tt>PMA_transform_text__formatted()</tt></li>
2088 <li>A mimetype+subtype without specific transform function<br /><br />
2090 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2092 Please note that there are no '__' characters in the filename. Do not
2093 use special characters in the filename causing problems with the file
2094 system.<br /><br />
2096 No transformation function is defined in the file itself.<br /><br />
2098 <b>Example:</b><br /><br />
2100 <tt>text_plain.inc.php</tt><br />
2101 (No function)</li>
2103 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2105 <tt>[mimetype].inc.php</tt><br /><br />
2107 Please note that there are no '_' characters in the filename. Do not use
2108 special characters in the filename causing problems with the file system.
2109 <br /><br />
2111 No transformation function is defined in the file itself.<br /><br />
2113 <b>Example:</b><br /><br />
2115 <tt>text.inc.php</tt><br />
2116 (No function)</li>
2118 <li>A global transform function with no specific mimetype<br /><br />
2120 <tt>global__[transform].inc.php</tt><br /><br />
2122 The transform function will the be called
2123 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2125 <b>Example:</b><br /><br />
2127 <tt>global__formatted</tt><br />
2128 <tt>PMA_transform_global__formatted()</tt></li>
2129 </ol>
2131 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2132 transform function.</p>
2134 <p> All filenames containing no '__' in themselves are not shown as valid transform
2135 functions in the dropdown.</p>
2137 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2138 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2139 without a transform function. Also note the introduction of a function description in
2140 the language files. For each function a $strTransformation_[filename without .inc.php]
2141 has to exist.</p>
2143 <p> You can use the template generator to generate new functions and entries in the
2144 language file.</p>
2146 <p> To create a new transform function please see
2147 <tt>libraries/transformations/template_generator.sh</tt>.
2148 To create a new, empty mimetype please see
2149 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2151 <p> A transform function always gets passed three variables:</p>
2153 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2154 you want to transform.</li>
2155 <li><b>$options</b> - Contains any user-passed options to a transform function
2156 as an array.</li>
2157 <li><b>$meta</b> - Contains an object with field information to your column.
2158 The data is drawn from the output of the
2160 function. This means, all object properties described on the
2162 available in this variable and can be used to transform a field accordingly
2163 to unsigned/zerofill/not_null/... properties.<br />
2164 The $meta->mimetype variable contains the original MIME-type of the
2165 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2166 </ol>
2168 <!-- FAQ -->
2175 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2179 </ol>
2181 <p> Please have a look at our
2183 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2184 features and or interface.</p>
2190 action is required or phpMyAdmin sends a blank page or a page full of
2191 cryptic characters to my browser, what can I do?</a></h4>
2193 <p> There are some known PHP bugs with output buffering and compression.<br />
2195 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2196 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2197 configuration file.<br />
2198 Furthermore, we know about such problems connected to the release
2199 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2200 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2205 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2206 See also the
2208 entry about PHP bugs with output buffering.<br />
2209 If your server keeps crashing, please ask for help in the various Apache
2210 support groups.</p>
2214 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2215 script: I'm always displayed the login screen.</a></h4>
2217 <p> This is a known PHP bug (see this
2219 official PHP bug database. It means there is and won't be any phpMyAdmin
2220 fix against it because there is no way to code a fix.</p>
2226 application misbehaved by not returning a complete set of
2228 </h4>
2230 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2231 Have a look at the last message in this
2233 official PHP bug database.</p>
2238 and/or many error messages with the
2240 mode.</a></h4>
2242 <p> This is a known problem with the PHP
2244 filter: it's not so stable. Please use instead the cookie authentication mode.
2245 </p>
2250 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2251 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2252 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2253 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2254 <i>left.php</i> and <i>libraries/common.lib.php</i>.</p>
2259 work.</a></h4>
2261 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2262 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2263 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2264 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2265 We faced PHP crashes when trying to download a dump with MS Internet
2266 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2267 this case you should switch to the release version of PHP 4.2.0.</p>
2271 an error about safe mode being in effect.</a></h4>
2273 <p> Your uploaded file is saved by PHP in the "upload dir", as
2274 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2275 the system default is <i>/tmp</i>).<br />
2276 We recommend the following setup for Apache servers running in safe mode,
2277 to enable uploads of files while being reasonably secure:</p>
2279 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2280 <li>give ownership to the Apache server's user.group:
2281 <tt>chown apache.apache /tmp/php</tt></li>
2282 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2283 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2284 <li>restart Apache</li>
2285 </ul>
2289 general file uploads don't work on my system and uploaded files have a
2290 <tt>Content-Type:</tt> header in the first line.</a></h4>
2292 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2293 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2294 So the problem is that this package has a serious bug that was corrected
2295 ages ago in PHP (2001-01-28: see
2297 for more details). The problem is that the bugged package is still
2298 available though it was corrected (see
2300 for more details).<br />
2301 So please download
2302 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2303 and the problem should go away.<br />
2304 And that fixes the \r\n problem with file uploads!</p>
2308 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2309 I'm using the Apache server.</a></h4>
2311 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2312 your <i>httpd.conf</i>:</p>
2316 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2320 uploading a file from the query box.</a></h4>
2322 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2323 restrictions. Assuming that the restriction allows you to open files in the
2324 current directory ('.'), all you have to do is create a 'tmp' directory
2325 under the phpMyAdmin install directory, with permissions 777 and the same
2326 owner as the owner of your phpMyAdmin directory. The uploaded files will
2327 be moved there, and after execution of your
2333 <p> The MySQL manual explains how to
2335 reset the permissions</a>.</p>
2340 execute a bookmark.</a></h4>
2342 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2343 cannot access the uploaded query.</p>
2348 submit a query from the convenient text area.</a></h4>
2350 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2351 and try to increase it.</p>
2355 </h4>
2357 <p> In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2358 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2359 names to align with current standards.</p>
2364 </h4>
2366 <p> Starting with version 2.7.0, the import engine has been re–written and these
2367 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2368 to take advantage of the new import features.</p>
2370 <p> The first things to check (or ask your host provider to check) are the
2371 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2372 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2373 All of these three settings limit the maximum size of data that can be
2374 submitted and handled by PHP. One user also said that post_max_size
2375 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2377 There exist several workarounds if your upload is too big or your
2378 hosting provider is unwilling to change the settings:</p>
2381 feature. This allows one to
2382 upload a file to the server via scp, ftp, or your favorite file transfer
2383 method. PhpMyAdmin is then able to import the files from the temporary
2385 section</a> of this document.</li>
2387 BigDump</a>) to split the files before uploading. We cannot support this
2388 or any third party applications, but are aware of users having success
2389 with it.</li>
2390 <li>If you have shell (command line) access, use MySQL to import the files
2391 directly. You can do this by issuing the "source" command from
2392 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2393 </ul>
2397 support?</a></h4>
2399 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2400 fully supported. Please note that the older your MySQL version is, the more
2401 limitations you will have to face.<br />
2402 phpMyAdmin may connect to your MySQL server using php's classic
2405 is available in php 5.0.<br />
2406 Either way, the developers of both extensions recommend to use the classic
2407 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2408 When compiling php, we strongly recommend that you manually link the MySQL
2409 extension of your choice to a MySQL client library of at least the same
2410 minor version since the one that is bundled with some php distributions is
2413 If your webserver is running on a windows system, you might want to try
2414 MySQL's
2416 instead of the MySQL / MySQLi extensions that are bundled with the official
2417 php Win32 builds.
2418 <br />
2419 MySQL 5.1 is not yet supported.</p>
2423 message, "Client does not support authentication protocol requested
2424 by server; consider upgrading MySQL client"</a></h5>
2426 <p> You tried to access MySQL with an old MySQL client library. The version of
2427 your MySQL client library can be checked in your phpinfo() output.
2428 In general, it should have at least the same minor version as your server
2432 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2433 changed the authentication hash and your PHP is trying to use the old method.
2435 with the proper client library to match your MySQL installation. Your
2436 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2437 More information (and several workarounds) are located in the
2439 </p>
2443 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2444 capital letter in its name it is changed to lowercase as it should. But
2445 if I try to DROP this table MySQL is unable to find the corresponding
2446 file.</a></h4>
2448 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2449 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2450 directive.</p>
2454 script seems not to know the font face I'm using!</a></h4>
2456 <p> The "FPDF" library we're using for this feature requires some
2457 special files to use font faces.<br />
2459 these files.</p>
2463 check PHP Configuration".</a></h4>
2465 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2466 "MySQL extension". This extension may be part of the PHP
2467 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2468 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2469 to load the extension but failed.<br /><br />
2471 Usually, the problem is solved by installing a software package called
2472 "PHP-MySQL" or something similar.</p>
2477 and I cannot log in using cookie auth.</a></h4>
2479 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2483 so I cannot upload.</a></h4>
2485 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2486 parameter is not set to "on".</p>
2490 a new table the table and field names are changed to lowercase!</a></h4>
2492 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2493 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2494 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2495 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2496 directory and add the following line to the group [mysqld]:</p>
2498 <pre>set-variable = lower_case_table_names=0</pre>
2500 <p> Next, save the file and restart the MySQL service. You can always check the
2501 value of this directive using the query</p>
2503 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2507 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2510 </p>
2514 and I get problems, such as undefined variables when I run a
2517 <p> A tip from Jose Fandos: put a comment on the following two lines
2518 in httpd.conf, like this:</p>
2520 <pre>
2521 # mod_gzip_item_include file \.php$
2523 </pre>
2525 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2526 PHP scripts. Of course you have to restart Apache.</p>
2531 I get the error "No input file specified" when trying to
2532 run phpMyAdmin.</a></h4>
2534 <p> This is a permission problem. Right-click on the phpmyadmin folder
2535 and choose properties. Under the tab Security, click on "Add"
2536 and select the user "IUSR_machine" from the list. Now set his
2537 permissions and it should work.</p>
2541 db_details_structure.php with plenty of tables).</a></h4>
2544 GZIP output buffering is enabled. If you turn off it (by
2546 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2547 PHP 5.0.0.</p>
2551 message 'Errorcode: 13'. What does this mean?</a></h4>
2553 <p> This can happen due to a MySQL bug when having database / table names with
2554 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2555 To fix this, turn off this directive, convert all database and table names
2556 to lower case and turn it on again. Alternatively, there's a bug-fix
2557 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2561 and the fields are duplicated.</a></h4>
2563 <p> It is possible to configure Apache in such a way that PHP has problems
2564 interpreting .php files.</p>
2566 <p> The problems occur when two different (and conflicting) set of directives
2567 are used:</p>
2569 <pre>
2570 SetOutputFilter PHP
2571 SetInputFilter PHP
2572 </pre>
2574 <p> and</p>
2576 <pre>AddType application/x-httpd-php .php</pre>
2578 <p> In the case we saw, one set of directives was in
2579 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2580 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2581 The recommended way is with <tt>AddType</tt>, so just comment out
2582 the first set of lines and restart Apache:</p>
2584 <pre>
2585 #SetOutputFilter PHP
2586 #SetInputFilter PHP
2587 </pre>
2592 <p> This problem is known to happen when the server is running Turck MMCache
2593 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2598 <p> Yes.<br />
2599 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2600 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2601 <tt>error_reporting</tt> settings.
2602 </p>
2605 <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>
2607 <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>
2610 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2611 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2612 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2613 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2614 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2615 enabled.) Click <tt>OK</tt>.</li>
2616 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2617 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2618 </ol>
2622 PHP 5.0.4 on 64-bit systems?</a></h4>
2624 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2625 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2631 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2632 Table and script parts are optional. If you want
2633 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2634 some configuration. Following lines apply only for <a
2636 that you have enabled some features within global configuration. You need
2637 <code>Options FollowSymLinks</code> and <code>AllowOverride
2638 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2639 you need mod_rewrite to be enabled. Then you just need to create following
2640 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2641 (don't forget to change directory name inside of it):</p>
2643 <pre>
2644 RewriteEngine On
2645 RewriteBase /path_to_phpMyAdmin
2646 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2647 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2648 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2649 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2650 </pre>
2653 <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>
2655 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2656 following rewrite rule:</p>
2658 <pre>
2659 RewriteEngine On
2660 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2661 </pre>
2665 </h4>
2666 <p>
2667 There can be many explanations to this and a look at your server's
2668 error log file might give a clue.
2669 </p>
2673 password encryption in cookie auth doesn't work.</a></h4>
2675 <p> If your cluster consist of different architectures, PHP code used for
2676 encryption/decryption won't work correct. This is caused by use of
2677 pack/unpack functions in code. Only solution is to use mcrypt extension
2678 which works fine in this case.</p>
2684 headers already sent by ..." is displayed, what's the problem?</a></h4>
2686 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2687 (I.E. no blank lines, no spaces, no characters...) neither before the
2688 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2689 tag at the end.</p>
2694 <p> Either there is an error with your PHP setup or your username/password is
2695 wrong. Try to make a small script which uses mysql_connect and see if it
2696 works. If it doesn't, it may be you haven't even compiled MySQL support
2697 into PHP.</p>
2701 connect to local MySQL server through socket '/tmp/mysql.sock'
2702 (111) ..." is displayed. What can I do?</a></h4>
2704 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2706 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2707 In your <i>php.ini</i> you will find a line</p>
2709 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2711 <p> change it to</p>
2713 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2715 <p> Then restart apache and it will work.</p>
2717 <p> Here is a fix suggested by Brad Ummer:</p>
2719 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2720 To do this, telnet to your server and go to the MySQL bin directory. In
2721 this directory there should be a file named <i>mysqladmin</i>. Type
2722 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2723 info about your MySQL server, including the socket
2724 (<i>/tmp/mysql.sock</i>, for example).</li>
2725 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2726 phpMyAdmin, you need to complete the socket information in the
2727 <i>config.inc.php</i>.<br />
2728 For example:
2730 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2731 <br /><br />
2733 Please also make sure that the permissions of this file allow to be readable
2734 by your webserver (i.e. '0755').</li>
2735 </ul>
2737 <p> Have also a look at the
2739 corresponding section of the MySQL documentation</a>.</p>
2743 what can I do?</a></h4>
2746 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2747 sometime.<br />
2748 Also have a look at your PHP version number: if it contains "4.0b..."
2749 it means you're running a beta version of PHP. That's not a so good idea,
2750 please upgrade to a plain revision.</p>
2754 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2755 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2757 <p> Check the value you set for the
2759 directive in the phpMyAdmin configuration file.</p>
2763 password: YES)"-error when trying to access a MySQL-Server on a
2764 host which is port-forwarded for my localhost.</a></h4>
2766 <p> When you are using a port on your localhost, which you redirect via
2767 port-forwarding to another host, MySQL is not resolving the localhost
2768 as expected.<br />
2769 Erik Wasser explains: The solution is: if your host is "localhost"
2770 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2771 connection for speeding up things. And that doesn't work in this configuration
2772 with port forwarding.<br />
2778 <p> Themes are configured with
2782 <br />
2784 should not delete the directory "original" or its underlying
2785 structure, because this is the system theme used by phpMyAdmin.
2786 "original" contains all images and styles, for backwards
2787 compatibility and for all themes that would not include images or css-files.
2788 <br /><br />
2791 is enabled, you can select your favorite theme on the main page. Your
2792 selected theme will be stored in a cookie.<br /><br /></p>
2794 <p> To create a theme:</p>
2796 <ul><li>make a new subdirectory (for example "your_theme_name") under
2798 (by default <tt>themes</tt>)</li>
2799 <li>copy the files and directories from "original" to
2800 "your_theme_name"</li>
2801 <li>edit the css-files in "your_theme_name/css"</li>
2802 <li>put your new images in "your_theme_name/img"</li>
2803 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2804 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2805 contain your chosen theme name, that will be visible in user interface</li>
2806 <li>make a new screenshot of your theme and save it under
2807 "your_theme_name/screen.png"</li>
2808 </ul>
2810 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2811 theme verbose name, theme generation and theme version. These versions and
2812 generations are enumerated from 1 and do not have any direct dependence on
2813 phpMyAdmin version. Themes within same generation should be backwards
2814 compatible - theme with version 2 should work in phpMyAdmin requiring
2815 version 1. Themes with different generation are incompatible.</p>
2817 <p> If you do not want to use your own symbols and buttons, remove the
2818 directory "img" in "your_theme_name". phpMyAdmin will
2819 use the default icons and buttons (from the system-theme "original").
2820 </p>
2824 what can I do?</a></h4>
2826 <p> Here are a few points to check:</p>
2828 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2830 directive empty. See also
2832 </li>
2833 <li>Maybe you have a broken PHP installation or you need to upgrade
2834 your Zend Optimizer. See
2836 http://bugs.php.net/bug.php?id=31134</a>.
2837 </li>
2838 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2839 set to the default (200) or another low value, you could get this
2840 error if your table has a high number of columns. Adjust this setting
2841 accordingly. (Thanks to Klaus Dorninger for the hint).
2842 </li>
2843 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2844 of ";" will cause this error. Replace it with "&;".
2845 </li>
2846 </ul>
2853 who logged out can not log in again in with the same nick.</a></h4>
2855 <p> This is related to the authentication mechanism (protocol) used by
2856 phpMyAdmin. To bypass this problem: just close all the opened
2857 browser windows and then go back to phpMyAdmin. You should be able to
2858 log in again.</p>
2862 limit error or a time limit error.</a></h4>
2864 <p> Compressed dumps are built in memory and because of this are limited to
2865 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2866 using
2868 (enabled by default). Zip exports can not be handled this way, so if you need
2869 Zip files for larger dump, you have to use another way.</p>
2873 or alter a table.</a></h4>
2875 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
2879 bundled with the MySQL server distribution.</a></h4>
2881 <p> The problem is that mysqldump creates invalid comments like this:</p>
2883 <pre>
2884 -- MySQL dump 8.22
2885 --
2886 -- Host: localhost Database: database
2887 ---------------------------------------------------------
2888 -- Server version 3.23.54
2889 </pre>
2891 <p> The invalid part of the code is the horizontal line made of dashes that
2892 appears once in every dump created with mysqldump. If you want to run your
2893 dump you have to turn it into valid MySQL. This means, you have to add a
2894 whitespace after the first two dashes of the line or add a # before it:
2895 <br />
2896 <code>
2897 -- -------------------------------------------------------<br />
2898 </code>
2899 or<br />
2900 <code>
2901 #---------------------------------------------------------
2902 </code>
2903 </p>
2910 <p> Please note that you should not use the separating string multiple times
2911 without any characters between them, or at the beginning/end of your table
2912 name. If you have to, think about using another TableSeparator or disabling
2913 that feature</p>
2918 <p> In Relation view, being able to choose a table in another database,
2919 or having more than one index field in the foreign key.<br /><br/>
2920 In Query-by-example (Query), automatic generation of the query
2921 LEFT JOIN from the foreign table.<br /><br/>
2922 </p>
2926 I get series of errors like "Warning: unable to parse url". How
2927 can this be fixed?</a></h4>
2928 <p>
2929 Your table neither have a primary key nor an unique one, so we must use a
2930 long expression to identify this row. This causes problems to parse_url
2931 function. The workaround is to create a primary or unique key.
2932 <br />
2933 </p>
2937 a MIME-Transformation onto!</a></h4>
2939 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
2940 nested forms can be put inside the table where phpMyAdmin displays the results.
2941 You can, however, use any form inside of a table if keep the parent
2942 form-container with the target to tbl_row_delete.php and just put your own
2943 input-elements inside. If you use a custom submit input field, the form will
2944 submit itself to the displaying page again, where you can validate the
2945 $HTTP_POST_VARS in a transformation.
2947 For a tutorial on how to effectively use transformations, see our
2949 on the official phpMyAdmin-homepage.</p>
2953 MySQL server</a></h4>
2955 <p> When MySQL is running in ANSI-compatibility mode, there are some major
2958 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
2959 the quote-character (") is interpreted as an identifier quote character and
2960 not as a string quote character, which makes many internal phpMyAdmin
2962 statements. There is no workaround to this behaviour. News to this item will
2963 be posted in Bug report
2964 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
2965 </p>
2969 more that one column with the same value
2970 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
2971 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
2973 <p> Please make sure that your table has a primary key, so that phpMyAdmin
2974 can use it for the Edit and Delete links.</p>
2979 <p> phpMyAdmin uses a quick method to get the row count, and this method
2980 only returns an approximate count in the case of InnoDB tables. See
2982 a way to modify those results, but
2983 this could have a serious impact on performance.</p>
2988 <p> The number of records in queries containing COUNT and GROUP BY is
2989 not correctly calculated. Also, sorting results of a query like
2994 containing an hyphen.
2995 </a></h4>
2996 <p>
2997 The tests I have made with current MySQL 4.1.11 API shows that the
2998 API does not accept this syntax for the USE command. Enclosing the
2999 db name with backquotes works. For further confusion, no backquotes
3000 are needed with command-line mysql.
3001 </p>
3003 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3006 <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
3007 need to install it for each customer.
3008 </a></h4>
3009 <p>
3010 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3011 your users. The development of this feature was kindly sponsored by
3012 NetCologne GmbH.
3013 This requires a properly setup MySQL user management and phpMyAdmin
3014 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3016 </p>
3020 access.
3021 </a></h4>
3022 <p>
3023 This depends on your system.<br />
3024 If you're running a server which cannot be accessed by other people, it's
3025 sufficient to use the directory protection bundled with your webserver
3027 If other people have telnet access to your server, you should use
3028 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3029 <br /><br />
3030 Suggestions:
3031 </p>
3032 <ul>
3033 <li>
3035 </li>
3036 <li>
3037 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3038 is a user whose password is only known to you, and apache is the
3039 group under which Apache runs.
3040 </li>
3041 <li>
3042 You should use PHP safe mode, to protect from other users that try
3044 </li>
3045 </ul>
3050 </a></h4>
3051 <p>
3056 </p>
3059 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3060 authentication.
3061 </a></h4>
3065 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3066 and/or
3068 are wrong.</li>
3070 <li>You have already setup a security mechanism for the
3071 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3072 phpMyAdmin's authentication, so remove it.</li>
3073 </ul>
3080 and put the privileges you want. For example,
3082 would let a user create/manage his/her database(s).</p>
3087 <p> If you have existing rules from an old .htaccess file, you can take them
3090 be a major benefit here if your installation is suited to using it. Then
3091 you can just add those updated lines into the
3095 <p> If you want a pre-made sample, you can try this fragment. It stops the
3096 'root' user from logging in from any networks other than the private
3099 <pre>
3100 //block root from logging in except from the private networks
3101 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3102 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3103 'deny root from all',
3104 'allow root from localhost',
3108 );
3109 </pre>
3114 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3115 different than the one set in your
3117 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3118 while a domain name is defined in the config file.</p>
3124 when trying to create a table with more than 14 fields.
3125 </a></h4>
3126 <p>
3127 We could reproduce this problem only under Win98/98SE. Testing under
3128 WinNT4 or Win2K, we could easily create more than 60 fields.
3129 <br />
3130 A workaround is to create a smaller number of fields, then come back to
3131 your table properties and add the other fields.
3132 </p>
3136 <p>
3137 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3138 with each script/website that use forms.<br />
3139 Upgrade or downgrade your Xitami server.
3140 </p>
3143 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3144 <p>
3145 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3146 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3147 don't seem to work.<br />
3149 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3150 the user's temporary directory, so they must be moved before closing
3151 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3154 </p>
3158 Explorer never stores the cookies.
3159 </a></h4>
3160 <p>
3161 MS Internet Explorer seems to be really buggy about cookies, at least till
3163 in this area!
3164 <br />
3165 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3166 work!
3167 </p>
3171 rows.
3172 </a></h4>
3173 <p>
3175 </p>
3178 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3179 when trying to modify a row in a table with many fields, or with a text field
3180 </a></h4>
3181 <p>
3182 Your table neither have a primary key nor an unique one, so we must use a
3183 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
3184 those browsers, and this not happen in Netscape, for example. The
3185 workaround is to create a primary or unique key, or use another browser.
3186 <br />
3187 </p>
3191 page.
3192 </a></h4>
3193 <p>
3194 Some browsers support right-clicking into the frame you want to refresh,
3195 just do this in the right frame.<br />
3196 </p>
3200 query box.
3201 </a></h4>
3202 <p>
3203 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3204 Mozilla versions.<br />
3205 </p>
3209 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3210 </a></h4>
3211 <p>
3212 This is a Mozilla bug (see bug #26882 at
3214 </p>
3219 </a></h4>
3220 <p>
3221 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3222 data in octet-stream mode. Since we can't detect the specific Netscape
3223 version, we cannot workaround this bug.
3224 </p>
3228 wrong.</a></h4>
3230 <p> Please ensure that you have set your browser's character set to the one of the
3231 language file you have selected on phpMyAdmin's start page.
3232 Alternatively, you can try the auto detection mode that is supported by the
3233 recent versions of the most browsers.</p>
3236 <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
3239 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3240 Netscape and Mozilla do not have this problem.</p>
3243 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3244 I cannot manage two servers: I log in to the first one, then the other one,
3245 but if I switch back to the first, I have to log in on each operation.</a></h4>
3251 but nothing happens after that, only a blank screen.</a></h4>
3254 bug in Opera6, because it is not able to interpret frameset definitions
3255 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3256 Opera7 at least.</p>
3265 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3270 address and you are starting
3272 containing a domain name, or the reverse situation.</li>
3273 <li>Security settings in IE and/or Microsoft Security Center are
3274 too high, thus blocking scripts execution.</li>
3275 <li>The Windows Firewall is blocking Apache and MySQL. You must
3279 </ul>
3282 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3283 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3284 installed in their Firefox is causing the problem.</p>
3291 </a></h4>
3292 <p>
3293 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3294 specifying a wrong field-type.<br />
3295 Common errors include:
3296 </p>
3297 <ul>
3300 </ul>
3301 <p>
3302 Also, look at the syntax chapter in the MySQL manual to confirm that your
3303 syntax is correct.
3304 </p>
3308 phpMyAdmin generates only one index with those 2 fields.
3309 </a></h4>
3310 <p>
3312 index. If you want two indexes, create the first one when creating the
3313 table, save, then display the table properties and click the Index link to
3314 create the other index.
3315 </p>
3319 <p>
3320 Since version 2.2.3, you have a checkbox for each field that can be null.
3322 field's value. Since version 2.5.5, you have to use the checkbox to get
3324 a literal NULL in the field, and not a NULL value (this works in PHP4).
3325 </p>
3330 <p> Click on a database or table name in the left frame, the properties will be
3332 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3333 statements that can be used to recreate your database/table.
3334 <br /><br />
3336 transmit the resulting dump to your station. Depending on your PHP
3337 configuration, you will see options to compress the dump. See also the
3339 configuration variable.<br /><br />
3342 this document.</p>
3347 </a></h4>
3349 <p> Click on a database name in the left frame, the properties will be
3351 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3353 the path to your dump filename, or use the Browse button. Then click Go.
3354 <br /><br />
3356 that you upgrade to take advantage of the new features.
3357 <br /><br />
3359 in this document.
3360 </p>
3365 <p> Here is an example with the tables persons, towns and countries, all
3367 table, create it as explained in the configuration section. Then create the
3368 example tables:</p>
3370 <pre>
3371 CREATE TABLE REL_countries (
3372 country_code char(1) NOT NULL default '',
3373 description varchar(10) NOT NULL default '',
3374 PRIMARY KEY (country_code)
3375 ) TYPE=MyISAM;
3377 INSERT INTO REL_countries VALUES ('C', 'Canada');
3379 CREATE TABLE REL_persons (
3380 id tinyint(4) NOT NULL auto_increment,
3381 person_name varchar(32) NOT NULL default '',
3383 country_code char(1) NOT NULL default '',
3384 PRIMARY KEY (id)
3385 ) TYPE=MyISAM;
3387 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3388 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3390 CREATE TABLE REL_towns (
3392 description varchar(30) NOT NULL default '',
3393 PRIMARY KEY (town_code)
3394 ) TYPE=MyISAM;
3396 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3397 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3398 </pre>
3404 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3408 </ul>
3416 <li>In the fields row, choose persons.person_name and click the
3418 <li>Do the same for towns.description and countries.descriptions in the
3421 the correct joins have been generated</li>
3423 </ul>
3427 <p>
3428 Starting from the previous example, create the pma_table_info as explained
3429 in the configuration section, then browse your persons table,
3430 and move the mouse over a town code or country code.
3431 <br /><br />
3432 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3433 enables: drop-down list of possible values.
3434 </p>
3437 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3438 <p>
3441 <br /><br />
3442 Then you need to think about your schema layout. Which tables will go on
3443 which pages?
3444 </p>
3445 <ul>
3451 page and click Go. If you like, you
3453 linked tables onto the new page.</li>
3454 <li>Select the name of the new page (making sure the Edit radio button
3455 is selected) and click Go.</li>
3457 Coordinates are relative; your diagram will
3458 be automatically scaled to fit the page. When initially placing tables
3459 on the page, just pick any coordinates -- say, 50x50. After clicking
3461 position the element correctly.</li>
3463 first be sure to click the Save
3464 button beneath the list of tables and coordinates, to save any changes
3465 you made there. Then scroll all the way down, select the
3467 you want, and click Go.</li>
3468 <li>Internet Explorer for Windows may suggest an incorrect filename when
3473 browsers on Windows, do not have this problem.</li>
3474 </ul>
3478 columns!</a></h4>
3480 <p> No, it's MySQL that is doing
3486 underscores in the database name?</a></h4>
3488 <p> If you do not put a backslash before the underscore, this is a wildcard
3491 john2db ...<br /><br />
3493 If you put a backslash before the underscore, it means that the database
3494 name will have a real underscore.</p>
3498 statistics pages?</a></h4>
3509 if it already exists during the import. It does NOT drop the table after
3510 your export, it only affects the import file.</li>
3512 Otherwise, you may get an error if the table name exists but has a
3513 different structure.</li>
3515 (if any) will be included in backup.</li>
3517 field and table names formed with special characters are protected.</li>
3519 types set in the pmadb in the dump as
3521 </li>
3522 </ul>
3527 command, for better documentation (but resulting file is bigger).</li>
3529 once the INSERT verb and the table name.</li>
3532 </li>
3534 more info is provided in the
3536 but basically with this selected, invalid values are adjusted and
3537 inserted rather than causing the entire statement to fail.</li>
3538 </ul>
3542 in its name.</a></h4>
3545 is the normal way to reference a database and table name. Worse, MySQL
3546 will usually let you create a database with a dot, but then you cannot
3547 work with it, nor delete it.</p>
3560 for usage.<br />
3561 On a more recent pear version, I had problems with the state of Net_DIME
3562 being beta, so this single command
3564 needed modules.<br />
3565 If you use the Validator, you should be aware that any
3567 submit will be stored anonymously (database/table/column names,
3568 strings, numbers replaced with generic values). The Mimer
3571 We utilize it as free SOAP service.</p>
3575 it, but MySQL says "BLOB column '...' used in key specification without
3578 <p> The right way to do this, is to create the field without any indexes,
3580 dialog. On this page, you will be able to choose your BLOB field, and
3581 set a size to the index, which is the condition to create an index on
3582 a BLOB field.</p>
3586 editing fields?</a></h4>
3588 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3589 with many editing fields (table structure changes, row editing, etc.)
3590 (must be enabled in configuration - see.
3592 You can also have a look at the directive
3594 ('vertical') and see if this eases up editing for you.</p>
3598 WTF is this feature then useful for?</a></h4>
3600 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3601 on them. Otherwise you could just put a comment on the field. Because entering
3602 your own mimetype will cause serious syntax checking issues and validation,
3603 this introduces a high-risk false-user-input situation. Instead you have to
3604 initialize mimetypes using functions or empty mimetype definitions.<br />
3605 Plus, you have a whole overview of available mimetypes. Who knows all those
3606 mimetypes by heart so he/she can enter it at will?</p>
3610 can't I see any bookmarks below the query box? What is this variable for?
3611 </a></h4>
3613 <p> Any query you have executed can be stored as a bookmark on the page where the
3614 results are displayed. You will find a button labeled 'Bookmark this query'
3615 just at the end of the page.<br />
3616 As soon as you have stored a bookmark, it is related to the database you run
3617 the query on. You can now access a bookmark dropdown on each page, the query
3618 box appears on for that database.<br /><br />
3620 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3624 aware of that you HAVE to create a valid query, otherwise your query won't be
3625 even able to be stored in the database.<br />
3627 for your query will remain the way it is, but will be stripped of the /**/
3628 chars. So you can use:<br /><br />
3632 which will be expanded to<br /><br />
3636 in your query, where VARIABLE is the string you entered in the input box. If
3637 an empty string is provided, no replacements are made.<br /><br />
3639 A more complex example. Say you have stored this query:<br /><br />
3641 <br /><br />
3644 the full query will be:<br /><br />
3647 <br /><br />
3651 spaces inserted there
3652 will be later also inserted as spaces in your query and may lead to unexpected
3653 results especially when
3655 Your initial query which is going to be stored as a bookmark has to yield at
3656 least one result row so
3657 you can store the bookmark. You may have that to work around using well
3661 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3662 include exported table?</a></h4>
3664 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3665 document should look like following one (assuming you have table
3668 <pre>
3669 \documentclass{article} % or any class you want
3670 \usepackage{longtable} % for displaying table
3671 \begin{document} % start of document
3672 \include{table} % including exported table
3673 \end{document} % end of document
3674 </pre>
3678 access them.
3679 </a></h4>
3682 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3683 enable users to see all the database names.
3686 So if your users do not need those privileges, you can remove them and their
3687 databases list will shorten.</p>
3691 possible values for a field, based on some foreign table?</a></h4>
3693 <p> You have to setup appropriate links between the tables, and also
3697 foreign table, a drop-down list of values will be available.
3698 You will see two lists of values, the first list containing the key
3699 and the display field, the second list containing the display field
3700 and the key. The reason for this is to be able to type the first
3701 letter of either the key or the display field.<br /><br />
3703 For 200 values or more, a distinct window will appear, to browse foreign
3704 key values and choose one.</p>
3708 automatically when entering Browse mode for a table?</a></h4>
3710 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3711 </p>
3715 Excel files, how can I enable that?</a></h4>
3717 <p> Current version does support direct export to Microsoft Excel and Word
3718 versions 2000 and newer. If you need export older versions, you can use
3720 which works out of the box or you can
3722 several problems, most important are limitation of cell content to 255
3723 chars and no support for charsets, so think carefully whether you want to
3724 enable this.</b>. For enabling this you need to set
3728 module Spreadsheet_Excel_Writer into php include path. The
3729 installation can be done by following command:</p>
3731 <pre>
3732 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3733 </pre>
3735 <p> First part of switches set we want to install beta version of that module
3736 (no stable version available yet) and then we tell pear we want to satisfy
3737 dependencies.</p>
3739 <p> If you are running in PHP safe mode, you will have to set
3742 modules are located, for example:</p>
3744 <pre>
3745 safe_mode_include_dir = /usr/local/lib/php
3746 </pre>
3750 <pre>
3751 cd phpMyAdmin
3752 mkdir tmp
3753 chmod o+rwx tmp
3754 </pre>
3758 what happens to my column comments stored in pmadb?</a></h4>
3760 <p> Automatic migration of a table's pmadb-style column comments to the native
3761 ones is done whenever you enter Structure page for this table.</p>
3768 <p> Our Bug Tracker is located at
3770 under the Bugs section.<br /><br />
3772 But please first discuss your bug with other users:<br />
3778 existing language, where do I start?</a></h4>
3780 <p> Always use the current CVS version of your language file.
3782 don't know how to get the CVS version, please ask one of the developers.
3783 <br />
3784 Please note that we try not to use HTML entities like &eacute; in
3785 the translations, since we define the right character set in the file.
3786 With HTML entities, the text on JavaScript messages would not
3787 display correctly.
3788 However there are some entities that need to be there, for quotes
3789 ,non-breakable spaces, ampersands, less than, greater than.<br />
3790 You can then put your translations, as a zip file to avoid losing special
3791 characters, on the sourceforge.net translation tracker.<br />
3792 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3793 list, because this is where we ask for translations of new messages.</p>
3797 phpMyAdmin. How should I proceed?</a></h4>
3802 <tt>cvs -d:pserver:anonymous@phpmyadmin.cvs.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
3803 [Password: simply press the Enter key]<br />
3804 <tt>cvs -z3 -d:pserver:anonymous@phpmyadmin.cvs.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
3805 [This will create a new sub-directory named phpMyAdmin]</li>
3807 <li>put the modified files (tar'ed and gzip'ed) inside the patch tracker of
3808 the
3810 </li>
3811 </ol>
3813 <p> Write access to the CVS tree is granted only to experienced developers who
3814 have already contributed something useful to phpMyAdmin.<br />
3820 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3822 <p> Please refer to
3823 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3824 </p>
3826 <!-- DEVELOPERS -->
3829 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3830 great features have been written by other people and you too can help to
3831 make phpMyAdmin a useful tool.</p>
3833 <p> If you're planning to contribute source, please read the following
3834 information:</p>
3840 it free from other code.<br />
3841 Commonly used functions should be added to
3844 <li>Obviously, you're free to use whatever coding style you want. But
3845 please try to keep your code as simple as possible: beginners are
3846 using phpMyAdmin as an example application.<br />
3847 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3848 compliant on one hand, they fit the
3851 coding standards</a>
3852 on the other hand. Please pay attention to this.</li>
3853 <li>Please try to keep up the file-naming conventions. Table-related stuff
3856 <li>Please don't use verbose strings in your code, instead add the string
3861 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3862 better debug and profile their code.<br />
3863 Please see the
3865 options for more information.<br />
3866 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3867 lost during its re-entry into Earth's atmosphere and in memory of the
3868 brave men and women who gave their lives for the people of Earth.</li>
3869 </ul>
3871 <!-- CREDITS -->
3874 <pre>
3875 phpMyAdmin - Credits
3876 ====================
3878 CREDITS, in chronological order
3879 -------------------------------
3882 * creator of the phpmyadmin project
3886 * multi-language version
3887 * various fixes and improvements
3889 * current project maintainer
3892 * started SourceForge phpMyAdmin project in March 2001
3893 * sync'ed different existing CVS trees with new features and bugfixes
3894 * multi-language improvements, dynamic language selection
3895 * current project maintainer
3896 * many bugfixes and improvements
3899 * rewrote and optimized javascript, DHTML and DOM stuff
3900 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
3901 generate XHTML1.0 and CSS2 compliant codes
3902 * improved the language detection system
3903 * many bugfixes and improvements
3906 * database maintenance controls
3907 * table type code
3909 * DB-based configuration (Not completed)
3912 * many bugfixes and improvements
3915 * bookmarks feature
3916 * multiple dump feature
3917 * gzip dump feature
3918 * zip dump feature
3921 * various fixes
3922 * moderator of the phpMyAdmin former users forum at phpwizard.net
3928 * rewrote and fix dump code
3929 * bugfixes
3932 * rewrote dump code for PHP4
3933 * mySQL table statistics
3934 * bugfixes
3937 * main author of the version 2.1.0.1
3938 * bugfixes
3942 * abstract database interface (PMA_DBI) with MySQLi support
3943 * privileges administration
3945 * various features and fixes
3946 * German language file updates
3949 * automatic joins in QBE
3950 * links column in printview
3951 * Relation view
3954 * enhanced index creation/display feature
3955 * feature to use a different charset for HTML than for MySQL
3956 * improvements of export feature
3957 * various features and fixes
3958 * Czech language file updates
3961 (http://sf.net/projects/phpmysqlformgen/)
3962 * suggested the patch for multiple table printviews
3965 * built the patch for vertical display of table rows
3966 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
3967 * Improvement of column/db comments
3968 * (MIME)-Transformations for columns
3969 * Use custom alias names for Databases in left frame
3970 * hierarchical/nested table display
3971 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
3972 * new icon sets
3973 * vertical display of column properties page
3974 * some bugfixes, features, support, German language additions
3977 * japanese kanji encoding conversion feature
3980 * the Cookie authentication mode
3983 * table relation-links feature
3986 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
3987 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
3988 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
3994 * phpMyAdmin logo (until June 2004)
3997 * blowfish library from the Horde project
4000 * mysqli support
4001 * many bugfixes and improvements
4004 * redesign for 2.6.0
4005 * phpMyAdmin sailboat logo (June 2004)
4008 * Representation at conferences
4011 * interface improvements
4012 * various bugfixes
4014 And also to the following people who have contributed minor changes,
4015 enhancements, bugfixes or support for a new language since version 2.1.0:
4017 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4018 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4019 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4020 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4022 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4023 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4024 Luís V., Martijn W. van der Lee,
4025 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4029 Original Credits of Version 2.1.0
4030 ---------------------------------
4032 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4033 to create a web-based interface to MySQL using PHP3. Although I have not
4034 used any of his source-code, there are some concepts I've borrowed from
4035 him. phpMyAdmin was created because Peter told me he wasn't going to
4036 further develop his (great) tool.
4037 Thanks go to
4039 code for the check when dropping a table or database. He also suggested
4040 that you should be able to specify the primary key on tbl_create.php3. To
4041 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4042 well as a bug-report. Plus many smaller improvements.
4044 were introduced in 1.3.0 (including quite significant ones like the
4045 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4046 bug-fixes and help.
4048 language-independent by outsourcing the strings to a separate file. He
4049 also contributed the French translation.
4051 tbl_select.php3, a feature to display only some fields from a table.
4053 functions in tbl_change.php3. He also added the
4056 servers and is a regular contributor for bug-fixes.
4058 features for 2.0.6.
4059 The following people have contributed minor changes, enhancements, bugfixes
4060 or support for a new language:
4061 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4062 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4063 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4064 G. Wieggers.
4066 And thanks to everyone else who sent me email with suggestions, bug-reports
4067 and or just some feedback.
4068 </pre>
4074 <ul>
4076 - the default name of Apache's directory-level configuration file.</li>
4080 - a software application that enables a user to display and interact with
4081 text, images, and other information typically located on a web page at a
4082 website on the World Wide Web.</li>
4084 - a free software/open source data compression algorithm and program
4085 developed by Julian Seward.</li>
4087 - an important World Wide Web technology that enables a client web browser
4088 to request data from a program executed on the Web server.</li>
4090 - a log or record of changes made to a project.</li>
4092 - a computer system that accesses a (remote) service on another computer
4093 by some kind of network.</li>
4095 - a set of data values of a particular simple type, one for each row of
4096 the table.</li>
4098 - a packet of information sent by a server to a World Wide Web browser
4099 and then sent back by the browser each time it accesses that server.</li>
4101 - Comma-seperated values</li>
4104 - an organized collection of data.</li>
4107 - a PHP module that extends PHP with additional functionality.</li>
4109 - a list of commonly asked question and there answers.</li>
4111 - one part of divided data/columns.</li>
4113 - a field or group of fields in a database record that point to a key
4114 field or group of fields forming a key of another database record in some
4115 (usually different) table.</li>
4117 - the free PDF library</li>
4119 GD Graphics Library</a> - a library by Thomas Boutell and others for
4120 dynamically manipulating images.</li>
4123 - gzip is short for GNU zip, a GNU free software file compression
4124 program.</li>
4126 - any machine connected to a computer network, a node that has a hostname.</li>
4128 - the unique name by which a network attached device is known on a network.</li>
4130 (HyperText Transfer Protocol)</a>
4131 - the primary method used to transfer or convey information on the World
4132 Wide Web.</li>
4135 additional security measures.</li>
4136 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4137 - a set of Internet-based services for servers using Microsoft Windows.</li>
4139 - a feature that allows quick access to the rows in a table.</li>
4141 - a data-oriented protocol used by source and destination hosts for
4142 communicating data across a packet-switched internetwork.</li>
4144 - a unique number that devices use in order to identify and communicate
4145 with each other on a network utilizing the Internet Protocol standard.</li>
4147 (Internet Server Application Programming Interface)</a>
4148 - the API of Internet Information Services (IIS).</li>
4150 - a business or organization that offers users access to the Internet and related services.</li>
4152 - a most commonly used standard method of lossy compression for
4153 photographic images.</li>
4159 - line of personal computers is designed, developed, manufactured, and
4160 marketed by Apple Computer.</li>
4161 <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>
4162 - the operating system which is included with all currently shipping Apple
4163 Macintosh computers in the consumer and professional markets.</li>
4165 - a cryptographic library.</li>
4167 - the MCrypt PHP extension.</li>
4168 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4169 - an Internet Standard for the format of e-mail.</li>
4171 - some sort of extension for the Apache Webserver.</li>
4173 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4174 Management System (DBMS).</li>
4176 - the improved MySQL client PHP extension.</li>
4178 - the MySQL client PHP extension.</li>
4180 - open standard for office documents.</li>
4181 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4182 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4184 (Portable Document Format)</a>
4185 - a file format developed by Adobe Systems for representing two
4186 dimensional documents in a device independent and resolution independent
4187 format.</li>
4189 - the PHP Extension and Application Repository.</li>
4191 - the perl-compatible regular expression functions for PHP</li>
4193 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4194 programming language used mainly for developing server-side applications
4195 and dynamic web content, and more recently, a broader range of software
4196 applications.</li>
4198 - a connection through which data is sent and received.</li>
4200 - Request for Comments (RFC) documents are a series of memoranda
4201 encompassing new research, innovations, and methodologies applicable to
4202 Internet technologies.</li>
4206 - represents a single, implicitly structured data item in a table.</li>
4208 - a computer system that provides services to other computing
4209 systems over a network.</li>
4210 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4211 - handlers for different table types</li>
4213 - a form of inter-process communication.</li>
4215 Sockets Layer)</a>
4216 - a cryptographic protocol which provides secure communication on the Internet.</li>
4218 - Structured Query Language</li>
4220 - a set of data elements (cells) that is organized, defined and stored as
4221 horizontal rows and vertical columns where each item can be uniquely
4222 identified by a label or key or by it?s position in relation to other items.</li>
4225 - a type of archive file format: the Tape ARchive format.</li>
4227 - one of the core protocols of the Internet protocol suite.</li>
4231 - a sequence of characters, conforming to a standardized format, that is
4232 used for referring to resources, such as documents and images on the
4233 Internet, by their location.</li>
4235 - A computer (program) that is responsible for accepting HTTP requests
4236 from clients and serving them Web pages.</li>
4238 - a W3C-recommended general-purpose markup language for creating
4239 special-purpose markup languages, capable of describing many different
4240 kinds of data.</li>
4242 - a popular data compression and archival format.</li>
4244 - an open-source, cross-platform data compression library by Jean-loup
4245 Gailly and Mark Adler.</li>
4246 </ul>
4256 </body>
4257 </html>