| blob | db395e80b635ae4fc4b39b56331108c9654bc149 |
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
16 </head>
20 <!-- TOP MENU -->
34 </ul>
39 phpMyAdmin homepage</a></li>
41 SourceForge phpMyAdmin project page</a></li>
43 Official phpMyAdmin wiki</a></li>
44 <li>Local documents:
48 </ul>
49 </li>
50 <li>Documentation version:
52 </li>
53 </ul>
55 <!-- REQUIREMENTS -->
62 </li>
63 <li>You need GD2 support in PHP to display inline
65 original aspect ratio</li>
68 </ul>
69 </li>
73 PHP extension on your web server accelerates not only the login
74 phase but every other action that you do in phpMyAdmin.</li>
76 </ul>
78 <!-- INTRODUCTION -->
81 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
82 a single database. To accomplish the latter you'll need a properly set up
83 MySQL user who can read/write only the desired database. It's up to you to
84 look up the appropriate part in the MySQL manual.
85 </p>
90 <li>create, copy, drop, rename and alter databases, tables, fields and
91 indexes</li>
92 <li>maintenance server, databases and tables, with proposals on server
93 configuration</li>
94 <li>execute, edit and bookmark any
96 batch-queries</li>
99 </li>
106 OpenDocument Text and Spreadsheet,
108 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
109 </li>
113 <li>using Query-by-example (QBE), create complex queries automatically
114 connecting required tables</li>
116 your Database layout</li>
118 <li>transform stored data into any format using a set of predefined
119 functions, like displaying BLOB-data as image or download-link
120 </li>
126 </li>
127 </ul>
130 <p> Many people have difficulty
131 understanding the concept of user management with regards to phpMyAdmin. When
132 a user logs in to phpMyAdmin, that username and password are passed directly
133 to MySQL. phpMyAdmin does no account management on its own (other than
134 allowing one to manipulate the MySQL user account information); all users
135 must be valid MySQL users.</p>
144 <!-- INSTALLATION -->
152 </ol>
155 phpMyAdmin does not apply any special security methods to the MySQL database
156 server. It is still the system administrator's job to grant permissions on
158 be used for this.
159 </p>
167 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
168 before uploading them to your server, as PHP seems not to like
173 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
174 Downloads page. Some kits contain only the English messages,
175 others contain all languages in UTF-8 format (this should be fine
176 in most situations), others contain all
177 languages and all character sets. We'll assume you chose a kit whose
179 </li>
180 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
182 document root. If you don't have direct access to your document root,
183 put the files in a directory on your local machine, and, after step 4,
184 transfer the directory on your web server using, for example, ftp.</li>
185 <li>Ensure that all the scripts have the appropriate owner (if PHP is
186 running in safe mode, having some scripts with an owner different
187 from the owner of other scripts will be a
192 <li>Now you must configure your installation. There are two methods that
193 can be used. Traditionally, users have hand-edited a copy of
194 config.inc.php, but now a wizard-style setup script is provided for
195 those who prefer a graphical installation. Creating a config.inc.php is
196 still a quick way to get started and needed for some advanced features.
197 <ul><li>To manually create the file, simply use your text editor to
200 file) in the main (top-level) phpMyAdmin directory (the one
204 default value is okay for a particular setting, there is no
206 few directives to get going, a simple configuration may look
207 like this:
208 <pre>
209 <?php
210 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
212 $i=0;
213 $i++;
214 $cfg['Servers'][$i]['auth_type'] = 'cookie';
215 ?>
216 </pre>
217 Or, if you prefer to not be prompted every time you log in:
218 <pre>
219 <?php
221 $i=0;
222 $i++;
223 $cfg['Servers'][$i]['user'] = 'root';
224 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
225 ?>
226 </pre>
227 For a full explanation of possible configuration values, see the
233 directory. This is a security measure. On a Linux/Unix system you
234 can use the following commands:
235 <pre>
236 cd phpMyAdmin
237 mkdir config # create directory for saving
238 chmod o+rw config # give it world writable permissions
239 </pre>
240 And to edit an existing configuration, copy it over first:
241 <pre>
242 cp config.inc.php config/ # copy current configuration for editing
243 chmod o+w config/config.inc.php # give it world writable permissions
244 </pre>
245 On other platforms, simply create the folder and ensure that your
254 the webserver does not have the proper permissions you may see the
256 config/</tt> directory exists and has the proper permissions -
258 and upload (via FTP or some similar means) to the proper location.<br /><br />
260 Once the file has been saved, it must be moved out of the <tt>
261 config/</tt> directory and the permissions must be reset, again
262 as a security measure:
263 <pre>
264 mv config/config.inc.php . # move file to current directory
265 chmod o-rw config.inc.php # remove world read and write permissions
266 </pre>
267 Now the file is ready to be used. You can choose to review or edit
268 the file with your favorite editor, if you prefer to set some
269 advanced options which the setup script does not provide.</li></ul></li>
270 <li>If you are using the
272 protect the phpMyAdmin installation directory because using
273 config does not require a user to
274 enter a password to access the phpMyAdmin installation. Use of an alternate
275 authentication method is recommended, for example with
283 in your browser. phpMyAdmin should now display a welcome screen
284 and your databases, or a login dialog if using
286 authentication mode.</li>
288 webserver configuration. For Apache you can use supplied .htaccess file
289 in that folder, for other webservers, you should configure this yourself.
290 Such configuration prevents from possible path exposure and cross side
291 scripting vulnerabilities that might happen to be found in that code.</li>
292 </ol>
296 <p> For a whole set of new features (bookmarks, comments,
299 transformation, etc.) you need to create a set of special tables. Those
300 tables can be located in your own database, or in a central database for a
301 multi-user installation (this database would then be accessed by the
302 controluser, so no other user should have rights to it).</p>
311 installation.</p>
316 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
317 that you may need special (administrator) privileges to create the database
318 and tables, and that the script may need some tuning, depending on the
319 database name.</p>
324 section</a>. You will also need to have a controluser with the proper rights
331 unpacked one. Configuration files from very old versions (2.3.0 or older) may
332 require some tweaking as some options have been changed or removed.</p>
336 is version-specific.</p>
339 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
340 you should run the SQL script found in
347 where you want to give users access to their own database and don't want
348 them to play around with others.<br />
349 Nevertheless be aware that MS Internet Explorer seems to be really buggy
351 in this area!<br />
354 that your user/password pair are not in clear in the configuration file.
355 </li>
358 authentication modes are more secure: the MySQL login information does
359 not need to be set in the phpMyAdmin configuration file (except possibly
361 However, keep in mind that the password travels in plain text, unless
362 you are using the HTTPS protocol.<br />
363 In cookie mode, the password is stored, encrypted with the blowfish
364 algorithm, in a temporary cookie.</li>
367 your MySQL server is older than 4.1.2, or is running with
377 file under the
379 $cfg['Servers'][$i]['controluser']</a></tt> and
384 only an example: use something else in your file!</b> Input these
385 statements from the phpMyAdmin SQL Query window or mysql command–line
386 client.<br />
388 if it's not the same as the MySQL server's one.
390 <pre>
391 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
392 GRANT SELECT (
393 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
394 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
395 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
396 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
397 Execute_priv, Repl_slave_priv, Repl_client_priv
398 ) ON mysql.user TO 'pma'@'localhost';
399 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
400 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
401 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
402 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
404 If you are using an old MySQL version (below 4.0.2), please replace
405 the first GRANT SELECT query by this one:
407 <pre>
408 GRANT SELECT (
409 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
410 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
411 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
412 ) ON mysql.user TO 'pma'@'localhost';</pre>
414 ... and if you want to use the many new relation and bookmark features:
416 <pre>
418 </pre>
422 Of course, the above queries only work if your MySQL version supports
426 on a set of particular databases. Normally you shouldn't give global
427 privileges to an ordinary user, unless you understand the impact of those
428 privileges (for example, you are creating a superuser).<br />
432 <pre>
433 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
434 </pre>
436 What the user may now do is controlled entirely by the MySQL user
437 management system.<br />
439 authentication mode, you don't need to fill the user/password fields
441 array.</li>
442 </ul>
447 method and allows you to log in as any valid MySQL user.</li>
448 <li>Is supported with most PHP configurations. For
461 mode.</li>
462 </ul>
466 <ul><li>You can use this method as a replacement for the
468 (for example, if you're running
470 <li>Obviously, the user must enable cookies in the browser, but this is
471 now a requirement for all authentication modes.</li>
472 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
473 with the same username.</li>
474 <li>If you want to log in to arbitrary server see
479 not required.</li>
480 </ul>
484 <ul><li>This mode is the less secure one because it requires you to fill the
486 $cfg['Servers'][$i]['user']</a> and
488 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
489 can read your config.inc.php can discover your username and password).
490 <br />
497 is an entry explaining how to protect your configuration file.</li>
498 <li>For additional security in this mode, you may wish to consider the Host
499 authentication
501 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
503 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
504 directives.</li>
505 <li>Unlike cookie and http, does not require a user to log in when first
506 loading the phpMyAdmin site. This is by design but could allow any
507 user to access your installation. Use of some restriction method is
509 HTTP-AUTH directive or disallowing incoming HTTP requests at
510 one’s router or firewall will suffice (both of which
511 are beyond the scope of this manual but easily searchable with Google).</li>
512 </ul>
514 <!-- CONFIGURATION -->
518 users:</span> PHP does not seem to like
522 before saving a script you have modified.</p>
527 section to create one. This file only needs to contain the parameters you want to
528 change from their corresponding default value in
531 <p> The parameters which relate to design (like colors) are placed in
534 your site specific code to be included on start and end of each page.</p>
538 (with full path) to your phpMyAdmin installation's directory.
541 some web servers are case–sensitive.
544 Starting with version 2.3.0, it is advisable to try leaving this
545 blank. In most cases phpMyAdmin automatically detects the proper
546 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
547 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
548 A good test is to browse a table, edit a row and save it. There should
549 be an error message if phpMyAdmin is having trouble auto–detecting
550 the correct value. If you get an error that this must be set or if
551 the autodetect code fails to detect your path, please post a bug
552 report on our bug tracker so we can improve the code.</dd>
556 with master / foreign – tables (see
558 <br />
559 If you tried to set this up and it does not work for you, have a look on
561 use it. You will find a link that will analyze why those features have
562 been disabled.<br />
563 If you do not want to use those features set this variable to
568 algorithm to encrypt the password.<br />
570 passphrase of your choice. It will be used internally by the blowfish
571 algorithm: you won’t be prompted for this passphrase. The maximum
576 MySQL servers. Therefore, a
578 been added which contains the login information for the different servers.
579 The first
581 contains the hostname of the first server, the second
583 the hostname of the second server, etc. In
585 server definition, however you can put as many as you need in
587 have to define all settings, just those you need to change).</dd>
591 $i-th MySQL-server. E.g. localhost.</dd>
596 ignores this port number and connects with the socket, so if you want
597 to connect to a port different from the default port, use
600 </dd>
604 To determine the correct socket, check your MySQL configuration or, using the
606 Among the resulting information displayed will be the socket used.</dd>
609 <dd>Whether to enable SSL for connection to MySQL server.
610 </dd>
613 <dd>What type connection to use with the MySQL server. Your options are
615 is nearly guaranteed to be available on all MySQL servers, while
616 sockets are not supported on some platforms.<br /><br />
618 To use the socket mode, your MySQL server must be on the same machine
619 as the Web server.</dd>
622 <dd>What php MySQL extension to use for the connection. Valid options are:
623 <br /><br />
626 The classic MySQL extension. This is the recommended and default
627 method at this time.<br /><br />
630 The improved MySQL extension. This extension became available
631 with php 5.0.0 and is the recommended way to connect to a server
635 <dd>Whether to use a compressed protocol for the MySQL server connection
636 or not (experimental).<br />
642 </dt>
644 all relational features (see
646 and, for a MySQL server older than 4.1.2 or running with
649 authentication mode).<br /><br />
652 cookie authentication modes (or 'config'
653 authentication mode since phpMyAdmin 2.2.1), you need to supply the
658 This account is used to check what databases the user will see at
659 login.<br />
663 In phpMyAdmin versions before 2.2.5, those were called
667 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
668 <dd>Whether config or cookie or
670 should be used for this server.
672 is the plain old way: username and password are stored in
674 <li>'cookie' authentication mode
676 2.2.3 allows you to log in as any valid MySQL user with the
677 help of cookies. Username and password are stored in
678 cookies during the session and password is deleted when it
679 ends. This can also allow you to log in in arbitrary server if
680 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
681 </li>
682 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in older versions and can be written also as 'http')
683 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
684 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
685 <li>'signon' authentication mode
687 as introduced in 2.10.0 allows you to log in from prepared PHP
688 session data. This is useful for implementing single signon
689 from another application. Sample way how to seed session is in
695 </ul>
698 for more information.
699 </dd>
703 </dt>
704 <dd>
705 When using auth_type = 'config', this is the user/password-pair
706 which phpMyAdmin will use to connect to the
707 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
708 cookie authentication is used and should be empty.</dd>
710 <span
712 </dt>
713 <dd>
714 Allow attempt to log in without password when a login with password
715 fails. This can be used together with http authentication, when
716 authentication is done some other way and phpMyAdmin gets user name
717 from auth and uses empty password for connecting to MySQL. Password
718 login is still tried first, but as fallback, no password method is
719 tried.</dd>
722 </dt>
723 <dd>
724 If set to a (an array of) database name(s), only this (these) database(s)
725 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
726 database(s) name(s) may contain MySQL wildcards characters
730 This setting is an efficient way to lower the server load since the
731 latter does not need to send MySQL requests to build the available
733 privileges rules of the MySQL database server</span>. If set, it just
734 means only these databases will be displayed but
736 <br /><br />
738 An example of using more that one database:
740 <br /><br />
742 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
743 databases in the left frame, so that you can individually arrange your databases.<br />
744 If you want to have certain databases at the top, but don't care about the others, you do not
745 need to specify all other databases. Use:
747 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
748 order.</dd>
751 </dt>
752 <dd>Regular expression for hiding some databases. This only hides them
753 from listing, but a user is still able to access them (using, for example,
754 the SQL query area). To limit access, use the MySQL privilege system.
755 <br /><br />
760 More information on regular expressions can be found in the
762 PCRE pattern syntax</a> portion of the PHP reference manual.
763 </dd>
766 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
767 this string will be displayed instead of the hostname in the pull-down
768 menu on the main page. This can be useful if you want to show only
769 certain databases on your system, for example.</dd>
773 </dt>
774 <dd>The name of the database containing the linked-tables infrastructure.
775 <br /><br />
778 section in this document to see the benefits of this infrastructure,
779 and for a quick way of creating this database and the needed tables.
780 <br /><br />
782 If you are the only user of this phpMyAdmin installation, you can
783 use your current database to store those special tables; in this
784 case, just put your current database name in
786 set this parameter to the name of your central database containing
787 the linked-tables infrastructure.</dd>
791 </dt>
793 useful for queries you often run.<br /><br />
795 To allow the usage of this functionality:
797 <li>enter the table name in
799 </ul>
800 </dd>
804 </dt>
806 which field is a key in another table (a foreign key). phpMyAdmin
807 currently uses this to
808 <ul><li>make clickable, when you browse the master table, the data values
809 that point to the foreign table;</li>
811 when browsing the master table, if you move the mouse to a column
812 containing a foreign key (use also the 'table_info' table);<br />
815 <li>in edit/insert mode, display a drop-down list of possible foreign
819 <li>display links on the table properties page, to check referential
820 integrity (display missing foreign keys) for each described key;
821 </li>
825 schema of your database (also uses the table_coords table).</li>
826 </ul>
828 The keys can be numeric or character.<br /><br />
830 To allow the usage of this functionality:
833 infrastructure</li>
834 <li>put the relation table name in
836 <li>now as normal user open phpMyAdmin and for each one of your
837 tables where you want to use this feature, click
839 </li>
840 </ul>
844 future development of the cross-db relations.
845 </dd>
849 </dt>
850 <dd>
851 Since release 2.3.0 you can describe, in a special 'table_info'
852 table, which field is to be displayed as a tool-tip when moving the
853 cursor over the corresponding key.<br />
854 This configuration variable will hold the name of this special
855 table. To allow the usage of this functionality:
857 <li>put the table name in
859 <li>then for each table where you want to use this feature,
861 to choose the field.</li>
862 </ul>
864 </dd>
868 </dt>
871 the relations between your tables. To do this it needs two tables
876 schema output).<br /><br />
880 To allow the usage of this functionality:
883 infrastructure</li>
884 <li>put the correct table names in
887 </ul>
890 </dd>
894 </dt>
896 Since release 2.3.0 you can store comments to describe each column for
898 <br /><br />
900 Starting with release 2.5.0, comments are consequently used on the table
901 property pages and table browse view, showing up as tool-tips above the
902 column name (properties page) or embedded within the header of table in
903 browse view. They can also be shown in a table dump. Please see the
904 relevant configuration directives later on.<br /><br />
906 Also new in release 2.5.0 is a MIME-transformation system which is also
908 Transformations</a> for further information. To use the
909 MIME-transformation system, your column_info table has to have the three
910 new fields 'mimetype', 'transformation', 'transformation_options'.
911 <br /><br />
913 To allow the usage of this functionality:
915 infrastructure</li>
916 <li>put the table name in
920 <pre>
921 ALTER TABLE `pma_column_comments`
922 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
923 ADD `transformation` VARCHAR( 255 ) NOT NULL,
924 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
925 </pre>
928 renamed from<br />
931 </ul>
932 </dd>
936 </dt>
939 all queries you entered manually into the phpMyAdmin interface. If you
940 don't want to use a table-based history, you can use the JavaScript-based
941 history. Using that, all your history items are deleted when closing the
942 window.<br /><br />
944 Using
946 you can specify an amount of history items you want to have on hold. On
947 every login, this list gets cut to the maximum amount.<br /><br />
949 The query history is only available if JavaScript is enabled in your
950 browser.<br /><br />
952 To allow the usage of this functionality:
955 infrastructure</li>
957 </li>
958 </ul>
959 </dd>
963 </dt>
965 to visually manage the relations.
966 <br /><br />
968 To allow the usage of this functionality:
971 infrastructure</li>
973 </li>
974 </ul>
975 </dd>
978 </dt>
980 column_info table got enhanced with three new fields. If the above variable
982 latest table structure available. If not, it will emit a warning to the
983 superuser.<br /><br />
985 You can disable this checking behavior by setting the variable to false,
986 which should offer a performance increase.<br /><br />
988 Recommended to set to FALSE, when you are sure, your table structure is
989 up to date.</dd>
991 boolean</dt>
992 <dd>Whether to allow root access. This is just simplification of rules below.
993 </dd>
996 </dt>
998 authentication is disabled.<br /><br />
1001 all deny rules followed by allow rules. Access is allowed by default. Any
1002 client which does not match a Deny command or does match an Allow command
1003 will be allowed access to the server. <br /><br />
1006 applies all allow rules followed by deny rules. Access is denied by
1007 default. Any client which does not match an Allow directive or does
1008 match a Deny directive will be denied access to the server.<br /><br />
1010 If your rule order is set to 'explicit', the authentication is
1011 performed in a similar fashion to rule order 'deny,allow', with the
1015 and was available in Apache by specifying allow and deny rules without
1016 setting any order.<br /><br />
1018 Please also see <a
1020 address behind proxies.
1021 </dd>
1023 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1024 </dt>
1025 <dd>The general format for the rules is as such:
1027 <pre>
1029 </pre>
1034 well (please note that those containing SERVER_ADDRESS might not be
1035 available on all webservers):
1036 <pre>
1042 </pre>
1044 Having an empty rule list is equivalent to either using
1050 following work:<br />
1052 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1053 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1054 But the following does not work:<br />
1057 </dd>
1058 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1059 <dd>Name of session which will be used for signon authentication method.
1060 </dd>
1062 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1063 </dd>
1065 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1066 </dd>
1069 <dd>If you have more than one server configured, you can set
1071 that server when phpMyAdmin is started, or set it to 0 to be given a
1072 list of servers without logging in.<br />
1074 MUST be set to that server.</dd>
1077 <dd>Defines whether to use GZip output buffering for increased
1079 Set to true/false for enabling/disabling. When set to 'auto' (string),
1080 phpMyAdmin tries to enable output buffering and will automatically disable
1081 it if your browser has some problems with buffering. IE6 with a certain patch
1082 is known to cause data corruption when having enabled buffering.</dd>
1085 <dd>Whether persistent connections should be used or not (mysql_connect or
1086 mysql_pconnect).</dd>
1092 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1093 to zero, no time limit is imposed.<br />
1094 This setting is used while importing/exporting dump files but has no
1095 effect when PHP is running in safe mode.</dd>
1098 <dd>Set the number of bytes a script is allowed to allocate. If number set
1099 to zero, no limit is imposed.<br />
1100 This setting is used while importing/exporting dump files but has no
1101 effect when PHP is running in safe mode.<br />
1105 <dd>Mark used tables and make it possible to show databases with locked
1110 generated by phpMyAdmin should be displayed or not.</dd>
1113 <dd>Defines whether normal users (non-administrator) are allowed to
1114 delete their own database or not. If set as FALSE, the link "Drop
1116 mydatabase" will be rejected. Quite practical for
1118 customers.<br />
1119 Please note that this limitation of SQL queries is not as strict as
1120 when using MySQL privileges. This is due to nature of SQL queries
1121 which might be quite complicated. So this choice should be viewed as
1122 help to avoid accidental dropping rather than strict privilege
1123 limitation.</dd>
1127 displayed when you're about to lose data.</dd>
1130 <dd>Define whether the previous login should be recalled or not in cookie
1131 authentication mode.</dd>
1138 means that it will be kept for existing session. This is recommended
1139 for not trusted environments.</dd>
1142 <dd>If enabled (default), logout deletes cookies for all servers,
1143 otherwise only for current one. Setting this to false makes it easy to
1144 forget to log out from other server, when you are using more of
1145 them.</dd>
1151 <dd>Define whether phpMyAdmin will continue executing a multi-query
1152 statement if one of the queries fails. Default is to abort execution.</dd>
1155 <dd>Define whether phpMyAdmin will output the results of each query of a
1156 multi-query statement embedded into the
1161 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1162 <br /><br />
1165 MySQL servers behind the firewall where your
1167 </dd>
1170 <dd>Defines whether to use a select-based menu and display only the current
1171 tables in the left frame (smaller page). Only in Non-Lightmode you can
1172 use the feature to display nested folders using
1174 </dd>
1177 <dd>In light mode, defines whether to display the names of databases (in the
1178 selector) using a tree, see also
1180 </dd>
1183 <dd>The string used to separate the parts of the database name when showing
1184 them in a tree.</dd>
1187 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1188 This means if you have tables like 'first__second__third' this will be
1190 If set to FALSE or empty, the feature is disabled. NOTE: You should
1191 not use this separator at the beginning or end of a
1192 table name or multiple times after another without any other
1193 characters in between.</dd>
1196 <dd>Defines how many sublevels should be displayed when splitting
1197 up tables by the above separator.</dd>
1200 <dd>Defines whether to display table comment as tool-tip in left frame or
1201 not.</dd>
1204 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1205 comment and the real name. That means that if you have a table called
1206 'user0001' and add the comment 'MyName' on it, you will see the name
1207 'MyName' used consequently in the left frame and the tool-tip shows
1208 the real name of the DB.</dd>
1211 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1213 When setting this to 'nested', the Alias of the Tablename is only used
1214 to split/nest the tables according to the
1216 directive. So only the folder is called like the Alias, the tablename itself
1217 stays the real tablename.</dd>
1220 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1223 <dd>Enter URL where logo in the navigation frame will point to.
1224 For use especially with self made theme which changes this.
1232 <dd>Defines whether or not to display a server choice at the top of the left frame.
1233 Defaults to FALSE.</dd>
1235 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1236 Defaults to FALSE (drop-down).</dd>
1238 <dd>Defines whether to display database choice in light navigation frame as links
1239 instead of in a drop-down. Defaults to FALSE (drop-down).</dd>
1241 <dd>Defines whether or not to display space usage and statistics about databases
1242 and tables.<br />
1243 Note that statistics requires at least MySQL 3.23.3 and that, at this
1244 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1247 <dd>Defines whether to display detailed server information on main page.
1248 You can additionally hide more information by using
1250 </dd>
1255 </dt>
1258 not at the starting main (right) frame. This setting
1259 does not check MySQL commands entered directly.<br /><br />
1261 Please note that to block the usage of phpinfo() in scripts, you
1268 hard coded password value in the configuration file, end users can't
1269 be allowed to change their passwords.</dd>
1272 <dd>Defines whether to suggest a database name on the
1277 content.</dd>
1280 <dd>Defines whether navigation bar buttons and the right panel top menu
1281 contain text or symbols only. A value of TRUE displays icons, FALSE
1282 displays text and 'both' displays both icons and text.</dd>
1285 <dd>Defines whether a user should be displayed a
1289 <dd>Number of rows displayed when browsing a result set. If the result set
1296 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1300 from editing when browsing a table's content. Valid values are:
1305 </ul>
1306 </dd>
1309 <dd>Defines whether or not MySQL functions fields should be initially
1310 displayed in edit/insert mode. Since version 2.10, the user can
1311 toggle this setting from the interface.
1312 </dd>
1315 <dd>Defines which type of editing controls should be used for CHAR and
1316 VARCHAR fields. Possible values are:
1317 <ul><li>input - this allows to limit size of text to size of field in
1318 MySQL, but has problems with newlines in fields</li>
1319 <li>textarea - no problems with newlines in fields, but also no
1320 length limitations</li>
1321 </ul>
1322 Default is old behavior so input.</dd>
1328 <dd>If there are fewer items than this in the set of foreign keys, then a
1329 drop-down box of foreign keys is presented, in the style described by the
1331 setting.</dd>
1334 <dd>For the foreign key drop-down fields, there are several methods of
1335 display, offering both the key and value data. The contents of the
1336 array should be one or both of the following strings:
1342 </dt>
1343 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1344 creating a dump file</dd>
1347 </dt>
1348 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1349 compressed exports. This doesn't affect smaller dumps and allows users to
1350 create larger dumps that won't otherwise fit in memory due to php
1351 memory limit. Produced files contain more GZip/BZip2 headers, but all
1352 normal programs handle this correctly.</dd>
1356 mainframe.</dd>
1360 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1365 <dd>How many columns will be utilized to display the tables on the
1366 database property view? Default is 1 column. When setting this to a
1367 value larger than 1, the type of the database will be omitted for more
1368 display space.</dd>
1372 <dd>Defines the tab displayed by default on server view. Possible
1379 <dd>Defines the tab displayed by default on database view. Possible
1384 <dd>Defines the tab displayed by default on table view. Possible
1391 points to the MySQL documentation (type depends
1392 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1393 generated.<br />
1395 for more information about MySQL manuals and their types.</dd>
1398 <dd>Type of MySQL documentation:
1404 </ul>
1405 </dd>
1408 <dd>Defines the default language to use, if not browser-defined or
1409 user-defined.<br />
1411 this setting.</dd>
1414 <dd>Defines the default connection collation to use, if not
1415 user-defined.<br />
1420 <dd>Force: always use this language (must be defined in the
1424 <dd>Limit list of available languages to those matching the given regular
1425 expression. For example if you want only Czech and English, you should
1429 <dd>Default character set to use for recoding of MySQL queries. This must be
1430 enabled and it's described by
1432 option.<br />
1433 You can give here any character set which is in
1435 array and this is just default choice, user can select any of them.</dd>
1438 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1439 support (compiled in or module) in PHP to allow MySQL queries recoding
1440 and used language file must have it enabled (by default only these
1441 which are in Unicode, just to avoid losing some characters).<br /><br />
1444 in the Export page, to choose the character set when exporting a file.
1445 </dd>
1448 <dd>You can select here which functions will be used for character set
1449 conversion. Possible values are:
1450 <ul><li>auto - automatically use available one (first is tested
1451 iconv, then recode)</li>
1454 </ul>
1455 Default is auto.</dd>
1458 <dd>Specify some parameters for iconv used in charset conversion. See
1461 used, so that invalid characters will be transliterated.</dd>
1464 <dd>Available character sets for MySQL conversion. You can add your own (any of
1465 supported by recode/iconv) or remove these which you don't use.
1466 Character sets will be shown in same order as here listed, so if you
1467 frequently use some of these move them to the top.</dd>
1472 default empty, you need to fill in some trusted proxy servers if you
1473 want to use rules for IP addresses behind proxy.<br /><br />
1475 The following example specifies that phpMyAdmin should trust a
1477 <pre>
1478 $cfg['TrustedProxies'] =
1480 </pre>
1481 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1482 client's IP address as usual.
1483 </dd>
1487 MIME transformations.<br />
1488 Possible values are:
1489 <ul><li>auto - automatically detect, this is a bit expensive
1491 according to your server real possibilities</li>
1494 </ul>
1495 Default is auto.
1496 </dd>
1500 </dd>
1502 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1503 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1504 </dt>
1505 <dd>The background styles used for both the frames.
1508 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1510 <dd>The style used for the pointer in the navi frame.
1519 </dd>
1523 <dd>The style used for table headers. See
1528 </dd>
1532 </dd>
1534 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1536 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1538 </dt>
1540 The former feature highlights the row over which your mouse is passing
1541 and the latter lets you visually mark/unmark rows by clicking on
1542 them.<br />
1547 <dd>You put here a valid CSS font family value, for example
1552 <dd>You put here a valid CSS font family value, for example
1566 </dt>
1568 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1570 The Char* values are used for CHAR and VARCHAR editing (if configured
1574 </dt>
1578 </dt>
1579 <dd>Defines if the whole textarea of the query box will be selected on
1580 click.</dd>
1583 </dt>
1584 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1585 editing.</dd>
1588 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1589 Can be turned off by a toggle button on the browse page.</dd>
1593 </dt>
1594 <dd>Defines the place where modify and delete links would be put when
1595 tables contents are displayed (you may have them displayed both at the
1596 left and at the right).
1602 </dt>
1604 Define which one is displayed by default. The first mode displays each
1605 row on a horizontal line, the second rotates the headers by 90
1606 degrees, so you can use descriptive headers even though fields only
1607 contain small values and still print them out. The vertical mode sorts
1608 each row on a vertical lineup.<br /><br />
1610 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1611 the rotation of the header for horizontalflipped is done via CSS. If
1612 set to 'fake' PHP does the transformation for you, but of course this
1613 does not look as good as CSS.</dd>
1617 string or integer</dt>
1618 <dd>When editing/creating new columns in a table all fields normally get
1619 lined up one field a line. (default: 'horizontal'). If you set this to
1620 'vertical' you can have each field lined up vertically beneath each
1621 other. You can save up a lot of place on the horizontal direction and
1622 no longer have to scroll. If you set this to integer, editing of fewer
1623 columns will appear in 'vertical' mode, while editing of more fields
1624 still in 'horizontal' mode. This way you can still effectively edit
1625 large number of fields, while having full view on few of them.</dd>
1629 </dt>
1631 display of column comments in Browse or Property display. In browse
1632 mode, the comments are shown inside the header. In property mode,
1633 comments are displayed using a CSS-formatted dashed-line below the
1634 name of the field. The comment is shown as a tool-tip for that field.
1635 </dd>
1647 <dd>Whether to display a link to validate a query in any SQL Query box.
1654 <dd>
1655 The name of the directory where
1657 <dd>
1658 The name of the directory where
1660 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1661 are available under a drop-down box when you click the database name,
1663 <br /><br />
1665 If you want different directory for each user, %u will be replaced
1666 with username.<br /><br />
1670 compressed formats is enabled).<br /><br />
1672 This feature is useful when your file is too big to be uploaded via
1674 uploads are disabled in PHP.<br /><br />
1676 Please note that if PHP is running in safe mode, this directory must
1677 be owned by the same user as the owner of the phpMyAdmin scripts.
1678 <br /><br />
1682 alternatives.
1683 </dd>
1686 <dd>
1687 The name of the directory where dumps can be saved.<br /><br />
1689 If you want different directory for each user, %u will be replaced
1690 with username.<br /><br />
1692 Please note that the directory has to be writable for user running
1693 webserver.<br /><br />
1695 Please note that if PHP is running in safe mode, this directory must
1696 be owned by the same user as the owner of the phpMyAdmin scripts.
1697 </dd>
1700 <dd>
1701 The name of the directory where temporary files can be stored.
1702 <br /><br />
1703 This is needed for native MS Excel export, see
1706 </dd>
1709 <dd>
1710 In this array are defined default parameters for export, names of
1711 items are similar to texts seen on export page, so you can easily
1712 identify what they mean.
1713 </dd>
1716 <dd>
1717 In this array are defined default parameters for import, names of
1718 items are similar to texts seen on import page, so you can easily
1719 identify what they mean.
1720 </dd>
1723 <dd>
1724 Repeat the headers every X cells, or 0 to deactivate.
1725 </dd>
1733 </dt>
1734 <dd>
1735 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1736 or icon is always displayed on the left panel. If JavaScript is enabled in
1737 your browser, a click on this opens a distinct query window, which is
1738 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1739 changes to display a query box.<br /><br />
1741 The size of this query window can be customized with
1743 - both integers for the size in pixels. Note that normally, those
1745 theme you are using.<br /><br />
1749 opens the query window and puts the current query
1750 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1751 query in the right panel's query box.
1752 <br /><br />
1753 The usage of the JavaScript query window is recommended if you have a
1754 JavaScript enabled browser. Basic functions are used to exchange quite
1755 a few variables, so most 4th generation browsers should be capable to
1756 use that feature. It currently is only tested with Internet Explorer 6
1757 and Mozilla 1.x.
1758 <br /><br />
1760 to a table, which has to be created by you (see <a
1762 all your queries will be appended to the form, but only as long as
1763 your window is opened they remain saved.
1764 <br /><br />
1765 When using the JavaScript based query window, it will always get
1766 updated when you click on a new table/db to browse and will focus if
1767 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1768 the query window by checking the box "Do not overwrite this query from
1769 outside the window" below the query textarea. Then you can browse
1770 tables/databases in the background without losing the contents of the
1771 textarea, so this is especially useful when composing a query with
1772 tables you first have to look in. The checkbox will get automatically
1773 checked whenever you change the contents of the textarea. Please
1774 uncheck the button whenever you definitely want the query window to
1775 get updated even though you have made alterations.
1776 <br /><br />
1779 <br /><br />
1780 The query window also has a custom tabbed look to group the features.
1782 default tab to be used when opening the query window. It can be set to
1783 either 'sql', 'files', 'history' or 'full'.</dd>
1789 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1791 If the approximate row count as returned by
1794 count will be used.
1795 </dd>
1797 <dd>For VIEWs, since obtaining the exact count could have an
1798 impact on performance, this value is the maximum to be displayed, using
1800 any row counting.
1801 </dd>
1805 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1807 page. By clicking on the button 'toggle scratchboard' on the page
1808 where you edit x/y coordinates of those elements you can activate a
1809 scratchboard where all your elements are placed. By clicking on an
1810 element, you can move them around in the pre-defined area and the x/y
1811 coordinates will get updated dynamically. Likewise, when entering a
1812 new position directly into the input field, the new position in the
1813 scratchboard changes after your cursor leaves the input field.<br />
1814 You have to click on the 'OK'-button below the tables to save the new
1815 positions. If you want to place a new element, first add it to the
1816 table of elements and then you can drag the new element around.<br />
1817 By changing the paper size and the orientation you can change the size
1818 of the scratchboard as well. You can do so by just changing the
1819 dropdown field below, and the scratchboard will resize automatically,
1820 without interfering with the current placement of the elements.<br />
1821 If ever an element gets out of range you can either enlarge the paper
1822 size or click on the 'reset' button to place all elements below each
1823 other.<br />
1825 get this control to work. The basic Drag&Drop script functionality
1826 was kindly borrowed from www.youngpup.net and is underlying so
1827 specific license.</dd>
1830 <dd>Sorts database and table names according to natural order (for example,
1831 t1, t2, t10). Currently implemented in the left panel (Light mode)
1832 and in Database view, for the table list.</dd>
1838 <dd>Allows you to specify window's title bar. Following magic string can
1839 be used to get special values:
1840 <dl>
1846 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1855 </dl>
1856 </dd>
1866 </dd>
1869 <dd>If theme manager is active, use this as the path of the subdirectory
1870 containing all the themes.</dd>
1884 </dt>
1885 <dd>Default queries that will be displayed in query boxes when user didn't
1886 specify any. Use %d for database name, %t for table name and %f for a
1887 comma separated list of field names. Note that %t and %f are only
1891 <dd>
1892 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
1893 default we use HTML to format the query, but you can disable this by
1895 </dd>
1898 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1899 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1900 query inside a bracket is indented. By changing
1903 specifies the units of the indent amount that you specified. This is
1904 used via stylesheets.</dd>
1907 <dd>This array is used to define the colours for each type of element of
1908 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1910 If you specify an empty string for the color of a class, it is ignored
1911 in creating the stylesheet.
1912 You should not alter the class names, only the colour strings.<br />
1933 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1937 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1938 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1939 </ul>
1940 </dd>
1944 <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,
1945 as originally published on
1947 <br />
1948 For help in setting up your system to use the service, see the
1950 </dd>
1954 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1955 and any password, so we use those by default. Instead, if
1956 you have an account with them, you can put your login details
1957 here, and it will be used in place of the anonymous login.</dd>
1958 </dl>
1959 </dd>
1962 <dd><b>DEVELOPERS ONLY!</b></dd>
1965 <dd><b>DEVELOPERS ONLY!</b><br />
1966 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1967 the code.<br />
1968 For help in setting up your system to this, see the
1972 <dd><b>DEVELOPERS ONLY!</b><br />
1973 Enable profiling support for phpMyAdmin. This will append a chunk of data
1974 to the end of every page displayed in the main window with profiling
1975 statistics for that page.<br />
1976 You may need to increase the maximum execution time for this to
1977 complete successfully.<i>Profiling was removed from the code for
1978 version 2.9.0 due to licensing issues.</i></dd>
1980 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
1981 <dd><b>DEVELOPERS ONLY!</b><br />
1982 When profiling data is displayed, this variable controls the threshold of
1983 display for any profiling data, based on the average time each time has
1984 taken. If it is over the threshold it is displayed, otherwise it is not
1985 displayed. This takes a value in milliseconds. In most cases you don't need
1986 to edit this.</dd>
1989 <dd>All possible types of a MySQL column. In most cases you don't need to
1990 edit this.</dd>
1993 <dd>Possible attributes for fields. In most cases you don't need to edit
1994 this.</dd>
1997 <dd>A list of functions MySQL supports. In most cases you don't need to
1998 edit this.</dd>
2001 <dd>Mapping of column types to meta types used for preferring displayed
2002 functions. In most cases you don't need to edit this.</dd>
2005 <dd>Functions preferred for column meta types as defined in
2006 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2007 to edit this.</dd>
2010 <dd>Functions selected by default when inserting/changing row, Functions
2011 are defined for meta types from
2013 <code>first_timestamp</code>, which is used for first timestamp column
2014 in table.</dd>
2017 <dd>Operators available for search operations on numeric and date fields.
2018 </dd>
2021 <dd>Operators available for search operations on character fields.
2022 Note that we put <code>LIKE</code> by default instead of
2023 <code>LIKE %...%</code>, to avoid unintended performance problems
2024 in case of huge tables.</dd>
2027 <dd>Operators available for search operations on enum fields.</dd>
2030 <dd>Additional operators available for search operations when the
2031 field can be null.</dd>
2033 </dl>
2035 <!-- TRANSFORMATIONS -->
2041 </ol>
2045 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2047 section</a> on how to do so.</p>
2049 <p> You can apply different transformations to the contents of each field. The
2050 transformation will take the content of each field and transform it with
2051 certain rules defined in the selected transformation.</p>
2053 <p> Say you have a field 'filename' which contains a filename. Normally you would
2054 see in phpMyAdmin only this filename. Using transformations you can transform
2055 that filename into a HTML link, so you can click inside of the phpMyAdmin
2056 structure on the field's link and will see the file displayed in a new browser
2057 window. Using transformation options you can also specify strings to
2058 append/prepend to a string or the format you want the output stored in.</p>
2060 <p> For a general overview of all available transformations and their options,
2061 you can consult your
2062 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2063 installation.</p>
2065 <p> For a tutorial on how to effectively use transformations, see our
2067 the official phpMyAdmin homepage.</p>
2071 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2072 clicking on the 'Structure' link for a table). There click on
2073 "Change" (or change icon) and there you will see three new fields at
2074 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2075 'Transformation options'.</p>
2077 <ul><li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
2078 empty or to use 'auto' [this feature is not yet available]. Please note that
2079 transformations are inactive as long as no MIME-type is selected.</li>
2081 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2082 hopefully growing amount of pre-defined transformations. See below for information on
2083 how to build your own transformation.<br />
2085 There are global transformations and mimetype-bound transformations. Global transformations
2086 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2087 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2088 transformations which operate on the main mimetype (like 'image'), which will most likely
2089 take the subtype into regard, and those who only operate on a
2090 specific subtype (like 'image/jpeg').<br />
2092 You can use transformations on mimetypes for which the function was not defined for. There
2093 is no security check for you selected the right transformation, so take care of what the
2094 output will be like.</li>
2096 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2097 transform-function specific options here. Usually the transforms can operate with default
2098 options, but it is generally a good idea to look up the overview to see which options are
2099 necessary.<br />
2101 Much like the ENUM/SET-Fields, you have to split up several options using the format
2102 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2103 parsed as an array, leaving the first value the first element in the array, and so
2104 forth.<br />
2106 If you want to specify a MIME character set you can define it in the transformation_options.
2107 You have to put that outside of the pre-defined options of the specific mime-transform,
2109 for which you can specify 2 options and you want to append a character set, enter "'first
2110 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2112 </ul>
2116 <p> All mimetypes and their transformations are defined through single files in
2117 the directory 'libraries/transformations/'.</p>
2119 <p> They are stored in files to ease up customization and easy adding of new
2120 transformations.</p>
2122 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2123 always work. It makes no sense to apply a transformation to a mimetype, the
2124 transform-function doesn't know to handle.</p>
2126 <p> One can, however, use empty mime-types and global transformations which should work
2127 for many mimetypes. You can also use transforms on a different mimetype they where built
2128 for, but pay attention to option usage as well as what the transformation does to your
2129 field.</p>
2131 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2132 any other transform function and provides some basic functions.</p>
2134 <p> There are 5 possible file names:</p>
2136 <ol><li>A mimetype+subtype transform:<br /><br />
2138 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2140 Please not that mimetype and subtype are separated via '_', which shall
2141 not be contained in their names. The transform function/filename may
2142 contain only characters which cause no problems in the file system as
2143 well as the PHP function naming convention.<br /><br />
2145 The transform function will the be called
2146 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2148 <b>Example:</b><br /><br />
2150 <tt>text_html__formatted.inc.php</tt><br />
2151 <tt>PMA_transform_text_html__formatted()</tt></li>
2153 <li>A mimetype (w/o subtype) transform:<br /><br />
2155 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2157 Please note that there are no single '_' characters.
2158 The transform function/filename may contain only characters which cause
2159 no problems in the file system as well as the PHP function naming
2160 convention.<br /><br />
2162 The transform function will the be called
2163 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2165 <b>Example:</b><br /><br />
2167 <tt>text__formatted.inc.php</tt><br />
2168 <tt>PMA_transform_text__formatted()</tt></li>
2170 <li>A mimetype+subtype without specific transform function<br /><br />
2172 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2174 Please note that there are no '__' characters in the filename. Do not
2175 use special characters in the filename causing problems with the file
2176 system.<br /><br />
2178 No transformation function is defined in the file itself.<br /><br />
2180 <b>Example:</b><br /><br />
2182 <tt>text_plain.inc.php</tt><br />
2183 (No function)</li>
2185 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2187 <tt>[mimetype].inc.php</tt><br /><br />
2189 Please note that there are no '_' characters in the filename. Do not use
2190 special characters in the filename causing problems with the file system.
2191 <br /><br />
2193 No transformation function is defined in the file itself.<br /><br />
2195 <b>Example:</b><br /><br />
2197 <tt>text.inc.php</tt><br />
2198 (No function)</li>
2200 <li>A global transform function with no specific mimetype<br /><br />
2202 <tt>global__[transform].inc.php</tt><br /><br />
2204 The transform function will the be called
2205 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2207 <b>Example:</b><br /><br />
2209 <tt>global__formatted</tt><br />
2210 <tt>PMA_transform_global__formatted()</tt></li>
2211 </ol>
2213 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2214 transform function.</p>
2216 <p> All filenames containing no '__' in themselves are not shown as valid transform
2217 functions in the dropdown.</p>
2219 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2220 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2221 without a transform function. Also note the introduction of a function description in
2222 the language files. For each function a $strTransformation_[filename without .inc.php]
2223 has to exist.</p>
2225 <p> You can use the template generator to generate new functions and entries in the
2226 language file.</p>
2228 <p> To create a new transform function please see
2229 <tt>libraries/transformations/template_generator.sh</tt>.
2230 To create a new, empty mimetype please see
2231 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2233 <p> A transform function always gets passed three variables:</p>
2235 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2236 you want to transform.</li>
2237 <li><b>$options</b> - Contains any user-passed options to a transform function
2238 as an array.</li>
2239 <li><b>$meta</b> - Contains an object with field information to your column.
2240 The data is drawn from the output of the
2242 function. This means, all object properties described on the
2244 available in this variable and can be used to transform a field accordingly
2245 to unsigned/zerofill/not_null/... properties.<br />
2246 The $meta->mimetype variable contains the original MIME-type of the
2247 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2248 </ol>
2250 <!-- FAQ -->
2257 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2261 </ol>
2263 <p> Please have a look at our
2265 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2266 features and or interface.</p>
2272 action is required or phpMyAdmin sends a blank page or a page full of
2273 cryptic characters to my browser, what can I do?</a></h4>
2275 <p> There are some known PHP bugs with output buffering and compression.<br />
2277 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2278 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2279 configuration file.<br />
2280 Furthermore, we know about such problems connected to the release
2281 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2282 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2287 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2288 See also the
2290 entry about PHP bugs with output buffering.<br />
2291 If your server keeps crashing, please ask for help in the various Apache
2292 support groups.</p>
2296 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2297 script: I'm always displayed the login screen.</a></h4>
2299 <p> This is a known PHP bug (see this
2301 official PHP bug database. It means there is and won't be any phpMyAdmin
2302 fix against it because there is no way to code a fix.</p>
2308 application misbehaved by not returning a complete set of
2310 </h4>
2312 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2313 Have a look at the last message in this
2315 official PHP bug database.</p>
2320 and/or many error messages with the
2322 mode.</a></h4>
2324 <p> This is a known problem with the PHP
2326 filter: it's not so stable. Please use instead the cookie authentication mode.
2327 </p>
2332 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2333 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2334 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2335 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2336 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2341 work.</a></h4>
2343 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2344 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2345 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2346 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2347 We faced PHP crashes when trying to download a dump with MS Internet
2348 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2349 this case you should switch to the release version of PHP 4.2.0.</p>
2353 an error about safe mode being in effect.</a></h4>
2355 <p> Your uploaded file is saved by PHP in the "upload dir", as
2356 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2357 the system default is <i>/tmp</i>).<br />
2358 We recommend the following setup for Apache servers running in safe mode,
2359 to enable uploads of files while being reasonably secure:</p>
2361 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2362 <li>give ownership to the Apache server's user.group:
2363 <tt>chown apache.apache /tmp/php</tt></li>
2364 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2365 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2366 <li>restart Apache</li>
2367 </ul>
2371 general file uploads don't work on my system and uploaded files have a
2372 <tt>Content-Type:</tt> header in the first line.</a></h4>
2374 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2375 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2376 So the problem is that this package has a serious bug that was corrected
2377 ages ago in PHP (2001-01-28: see
2379 for more details). The problem is that the bugged package is still
2380 available though it was corrected (see
2382 for more details).<br />
2383 So please download
2384 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2385 and the problem should go away.<br />
2386 And that fixes the \r\n problem with file uploads!</p>
2390 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2391 I'm using the Apache server.</a></h4>
2393 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2394 your <i>httpd.conf</i>:</p>
2398 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2402 uploading a file from the query box.</a></h4>
2404 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2405 restrictions. Assuming that the restriction allows you to open files in the
2406 current directory ('.'), all you have to do is create a 'tmp' directory
2407 under the phpMyAdmin install directory, with permissions 777 and the same
2408 owner as the owner of your phpMyAdmin directory. The uploaded files will
2409 be moved there, and after execution of your
2415 <p> The MySQL manual explains how to
2417 reset the permissions</a>.</p>
2422 execute a bookmark.</a></h4>
2424 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2425 cannot access the uploaded query.</p>
2430 submit a query from the convenient text area.</a></h4>
2432 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2433 and try to increase it.</p>
2437 </h4>
2439 <p> In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2440 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2441 names to align with current standards.</p>
2446 </h4>
2448 <p> Starting with version 2.7.0, the import engine has been re–written and these
2449 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2450 to take advantage of the new import features.</p>
2452 <p> The first things to check (or ask your host provider to check) are the
2453 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2454 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2455 All of these three settings limit the maximum size of data that can be
2456 submitted and handled by PHP. One user also said that post_max_size
2457 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2459 There exist several workarounds if your upload is too big or your
2460 hosting provider is unwilling to change the settings:</p>
2463 feature. This allows one to
2464 upload a file to the server via scp, ftp, or your favorite file transfer
2465 method. PhpMyAdmin is then able to import the files from the temporary
2467 section</a> of this document.</li>
2469 BigDump</a>) to split the files before uploading. We cannot support this
2470 or any third party applications, but are aware of users having success
2471 with it.</li>
2472 <li>If you have shell (command line) access, use MySQL to import the files
2473 directly. You can do this by issuing the "source" command from
2474 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2475 </ul>
2479 support?</a></h4>
2481 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2482 fully supported. Please note that the older your MySQL version is, the more
2483 limitations you will have to face.<br />
2484 phpMyAdmin may connect to your MySQL server using php's classic
2487 is available in php 5.0.<br />
2488 Either way, the developers of both extensions recommend to use the classic
2489 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2490 When compiling php, we strongly recommend that you manually link the MySQL
2491 extension of your choice to a MySQL client library of at least the same
2492 minor version since the one that is bundled with some php distributions is
2495 If your webserver is running on a windows system, you might want to try
2496 MySQL's
2498 instead of the MySQL / MySQLi extensions that are bundled with the official
2499 php Win32 builds.
2500 <br />
2501 MySQL 5.1 is not yet supported.</p>
2505 message, "Client does not support authentication protocol requested
2506 by server; consider upgrading MySQL client"</a></h5>
2508 <p> You tried to access MySQL with an old MySQL client library. The version of
2509 your MySQL client library can be checked in your phpinfo() output.
2510 In general, it should have at least the same minor version as your server
2514 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2515 changed the authentication hash and your PHP is trying to use the old method.
2517 with the proper client library to match your MySQL installation. Your
2518 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2519 More information (and several workarounds) are located in the
2521 </p>
2525 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2526 capital letter in its name it is changed to lowercase as it should. But
2527 if I try to DROP this table MySQL is unable to find the corresponding
2528 file.</a></h4>
2530 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2531 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2532 directive.</p>
2536 script seems not to know the font face I'm using!</a></h4>
2538 <p> The "FPDF" library we're using for this feature requires some
2539 special files to use font faces.<br />
2541 these files.</p>
2545 check PHP Configuration".</a></h4>
2547 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2548 "MySQL extension". This extension may be part of the PHP
2549 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2550 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2551 to load the extension but failed.<br /><br />
2553 Usually, the problem is solved by installing a software package called
2554 "PHP-MySQL" or something similar.</p>
2559 and I cannot log in using cookie auth.</a></h4>
2561 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2565 so I cannot upload.</a></h4>
2567 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2568 parameter is not set to "on".</p>
2572 a new table the table and field names are changed to lowercase!</a></h4>
2574 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2575 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2576 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2577 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2578 directory and add the following line to the group [mysqld]:</p>
2580 <pre>set-variable = lower_case_table_names=0</pre>
2582 <p> Next, save the file and restart the MySQL service. You can always check the
2583 value of this directive using the query</p>
2585 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2589 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2592 </p>
2596 and I get problems, such as undefined variables when I run a
2599 <p> A tip from Jose Fandos: put a comment on the following two lines
2600 in httpd.conf, like this:</p>
2602 <pre>
2603 # mod_gzip_item_include file \.php$
2605 </pre>
2607 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2608 PHP scripts. Of course you have to restart Apache.</p>
2613 I get the error "No input file specified" when trying to
2614 run phpMyAdmin.</a></h4>
2616 <p> This is a permission problem. Right-click on the phpmyadmin folder
2617 and choose properties. Under the tab Security, click on "Add"
2618 and select the user "IUSR_machine" from the list. Now set his
2619 permissions and it should work.</p>
2623 db_structure.php with plenty of tables).</a></h4>
2626 GZIP output buffering is enabled. If you turn off it (by
2628 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2629 PHP 5.0.0.</p>
2633 message 'Errorcode: 13'. What does this mean?</a></h4>
2635 <p> This can happen due to a MySQL bug when having database / table names with
2636 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2637 To fix this, turn off this directive, convert all database and table names
2638 to lower case and turn it on again. Alternatively, there's a bug-fix
2639 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2643 and the fields are duplicated.</a></h4>
2645 <p> It is possible to configure Apache in such a way that PHP has problems
2646 interpreting .php files.</p>
2648 <p> The problems occur when two different (and conflicting) set of directives
2649 are used:</p>
2651 <pre>
2652 SetOutputFilter PHP
2653 SetInputFilter PHP
2654 </pre>
2656 <p> and</p>
2658 <pre>AddType application/x-httpd-php .php</pre>
2660 <p> In the case we saw, one set of directives was in
2661 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2662 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2663 The recommended way is with <tt>AddType</tt>, so just comment out
2664 the first set of lines and restart Apache:</p>
2666 <pre>
2667 #SetOutputFilter PHP
2668 #SetInputFilter PHP
2669 </pre>
2674 <p> This problem is known to happen when the server is running Turck MMCache
2675 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2680 <p> Yes.<br />
2681 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2682 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2683 <tt>error_reporting</tt> settings.
2684 </p>
2687 <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>
2689 <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>
2692 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2693 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2694 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2695 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2696 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2697 enabled.) Click <tt>OK</tt>.</li>
2698 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2699 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2700 </ol>
2704 PHP 5.0.4 on 64-bit systems?</a></h4>
2706 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2707 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2713 http://server/phpMyAdmin/index.php?db=database&table=table&target=script.
2714 Table and script parts are optional. If you want
2715 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2716 some configuration. Following lines apply only for <a
2718 that you have enabled some features within global configuration. You need
2719 <code>Options FollowSymLinks</code> and <code>AllowOverride
2720 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2721 you need mod_rewrite to be enabled. Then you just need to create following
2722 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2723 (don't forget to change directory name inside of it):</p>
2725 <pre>
2726 RewriteEngine On
2727 RewriteBase /path_to_phpMyAdmin
2728 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2729 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2730 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2731 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2732 </pre>
2735 <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>
2737 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2738 following rewrite rule:</p>
2740 <pre>
2741 RewriteEngine On
2742 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2743 </pre>
2747 </h4>
2748 <p>
2749 There can be many explanations to this and a look at your server's
2750 error log file might give a clue.
2751 </p>
2755 password encryption in cookie auth doesn't work.</a></h4>
2757 <p> If your cluster consist of different architectures, PHP code used for
2758 encryption/decryption won't work correct. This is caused by use of
2759 pack/unpack functions in code. Only solution is to use mcrypt extension
2760 which works fine in this case.</p>
2766 headers already sent by ..." is displayed, what's the problem?</a></h4>
2768 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2769 (I.E. no blank lines, no spaces, no characters...) neither before the
2770 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2771 tag at the end.</p>
2776 <p> Either there is an error with your PHP setup or your username/password is
2777 wrong. Try to make a small script which uses mysql_connect and see if it
2778 works. If it doesn't, it may be you haven't even compiled MySQL support
2779 into PHP.</p>
2783 connect to local MySQL server through socket '/tmp/mysql.sock'
2784 (111) ..." is displayed. What can I do?</a></h4>
2786 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2788 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2789 In your <i>php.ini</i> you will find a line</p>
2791 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2793 <p> change it to</p>
2795 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2797 <p> Then restart apache and it will work.</p>
2799 <p> Here is a fix suggested by Brad Ummer:</p>
2801 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2802 To do this, telnet to your server and go to the MySQL bin directory. In
2803 this directory there should be a file named <i>mysqladmin</i>. Type
2804 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2805 info about your MySQL server, including the socket
2806 (<i>/tmp/mysql.sock</i>, for example).</li>
2807 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2808 phpMyAdmin, you need to complete the socket information in the
2809 <i>config.inc.php</i>.<br />
2810 For example:
2812 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2813 <br /><br />
2815 Please also make sure that the permissions of this file allow to be readable
2816 by your webserver (i.e. '0755').</li>
2817 </ul>
2819 <p> Have also a look at the
2821 corresponding section of the MySQL documentation</a>.</p>
2825 what can I do?</a></h4>
2828 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2829 sometime.<br />
2830 Also have a look at your PHP version number: if it contains "4.0b..."
2831 it means you're running a beta version of PHP. That's not a so good idea,
2832 please upgrade to a plain revision.</p>
2836 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2837 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2839 <p> Check the value you set for the
2841 directive in the phpMyAdmin configuration file.</p>
2845 password: YES)"-error when trying to access a MySQL-Server on a
2846 host which is port-forwarded for my localhost.</a></h4>
2848 <p> When you are using a port on your localhost, which you redirect via
2849 port-forwarding to another host, MySQL is not resolving the localhost
2850 as expected.<br />
2851 Erik Wasser explains: The solution is: if your host is "localhost"
2852 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2853 connection for speeding up things. And that doesn't work in this configuration
2854 with port forwarding.<br />
2860 <p> Themes are configured with
2864 <br />
2866 should not delete the directory "original" or its underlying
2867 structure, because this is the system theme used by phpMyAdmin.
2868 "original" contains all images and styles, for backwards
2869 compatibility and for all themes that would not include images or css-files.
2870 <br /><br />
2873 is enabled, you can select your favorite theme on the main page. Your
2874 selected theme will be stored in a cookie.<br /><br /></p>
2876 <p> To create a theme:</p>
2878 <ul><li>make a new subdirectory (for example "your_theme_name") under
2880 (by default <tt>themes</tt>)</li>
2881 <li>copy the files and directories from "original" to
2882 "your_theme_name"</li>
2883 <li>edit the css-files in "your_theme_name/css"</li>
2884 <li>put your new images in "your_theme_name/img"</li>
2885 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2886 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2887 contain your chosen theme name, that will be visible in user interface</li>
2888 <li>make a new screenshot of your theme and save it under
2889 "your_theme_name/screen.png"</li>
2890 </ul>
2892 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2893 theme verbose name, theme generation and theme version. These versions and
2894 generations are enumerated from 1 and do not have any direct dependence on
2895 phpMyAdmin version. Themes within same generation should be backwards
2896 compatible - theme with version 2 should work in phpMyAdmin requiring
2897 version 1. Themes with different generation are incompatible.</p>
2899 <p> If you do not want to use your own symbols and buttons, remove the
2900 directory "img" in "your_theme_name". phpMyAdmin will
2901 use the default icons and buttons (from the system-theme "original").
2902 </p>
2906 what can I do?</a></h4>
2908 <p> Here are a few points to check:</p>
2910 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2912 directive empty. See also
2914 </li>
2915 <li>Maybe you have a broken PHP installation or you need to upgrade
2916 your Zend Optimizer. See
2918 http://bugs.php.net/bug.php?id=31134</a>.
2919 </li>
2920 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2921 set to the default (200) or another low value, you could get this
2922 error if your table has a high number of columns. Adjust this setting
2923 accordingly. (Thanks to Klaus Dorninger for the hint).
2924 </li>
2925 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2926 of ";" will cause this error. Replace it with "&;".
2927 </li>
2929 you might want to increase
2931 </li>
2932 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
2933 </li>
2934 </ul>
2941 who logged out can not log in again in with the same nick.</a></h4>
2943 <p> This is related to the authentication mechanism (protocol) used by
2944 phpMyAdmin. To bypass this problem: just close all the opened
2945 browser windows and then go back to phpMyAdmin. You should be able to
2946 log in again.</p>
2950 limit error or a time limit error.</a></h4>
2952 <p> Compressed dumps are built in memory and because of this are limited to
2953 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2954 using
2956 (enabled by default). Zip exports can not be handled this way, so if you need
2957 Zip files for larger dump, you have to use another way.</p>
2961 or alter a table.</a></h4>
2963 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
2967 bundled with the MySQL server distribution.</a></h4>
2969 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
2971 <pre>
2972 -- MySQL dump 8.22
2973 --
2974 -- Host: localhost Database: database
2975 ---------------------------------------------------------
2976 -- Server version 3.23.54
2977 </pre>
2979 <p> The invalid part of the code is the horizontal line made of dashes that
2980 appears once in every dump created with mysqldump. If you want to run your
2981 dump you have to turn it into valid MySQL. This means, you have to add a
2982 whitespace after the first two dashes of the line or add a # before it:
2983 <br />
2984 <code>
2985 -- -------------------------------------------------------<br />
2986 </code>
2987 or<br />
2988 <code>
2989 #---------------------------------------------------------
2990 </code>
2991 </p>
2998 <p> Please note that you should not use the separating string multiple times
2999 without any characters between them, or at the beginning/end of your table
3000 name. If you have to, think about using another TableSeparator or disabling
3001 that feature</p>
3006 <p> In Relation view, being able to choose a table in another database,
3007 or having more than one index field in the foreign key.<br /><br/>
3008 In Query-by-example (Query), automatic generation of the query
3009 LEFT JOIN from the foreign table.<br /><br/>
3010 </p>
3014 I get series of errors like "Warning: unable to parse url". How
3015 can this be fixed?</a></h4>
3016 <p>
3017 Your table neither have a primary key nor an unique one, so we must use a
3018 long expression to identify this row. This causes problems to parse_url
3019 function. The workaround is to create a primary or unique key.
3020 <br />
3021 </p>
3025 a MIME-Transformation onto!</a></h4>
3027 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3028 nested forms can be put inside the table where phpMyAdmin displays the results.
3029 You can, however, use any form inside of a table if keep the parent
3030 form-container with the target to tbl_row_delete.php and just put your own
3031 input-elements inside. If you use a custom submit input field, the form will
3032 submit itself to the displaying page again, where you can validate the
3033 $HTTP_POST_VARS in a transformation.
3035 For a tutorial on how to effectively use transformations, see our
3037 on the official phpMyAdmin-homepage.</p>
3041 MySQL server</a></h4>
3043 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3046 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3047 the quote-character (") is interpreted as an identifier quote character and
3048 not as a string quote character, which makes many internal phpMyAdmin
3050 statements. There is no workaround to this behaviour. News to this item will
3051 be posted in Bug report
3052 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3053 </p>
3057 more that one column with the same value
3058 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3059 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3061 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3062 can use it for the Edit and Delete links.</p>
3067 <p> phpMyAdmin uses a quick method to get the row count, and this method
3068 only returns an approximate count in the case of InnoDB tables. See
3070 a way to modify those results, but
3071 this could have a serious impact on performance.</p>
3076 <p> The number of records in queries containing COUNT and GROUP BY is
3077 not correctly calculated. Also, sorting results of a query like
3082 containing an hyphen.
3083 </a></h4>
3084 <p>
3085 The tests I have made with current MySQL 4.1.11 API shows that the
3086 API does not accept this syntax for the USE command. Enclosing the
3087 db name with backquotes works. For further confusion, no backquotes
3088 are needed with command-line mysql.
3089 </p>
3091 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3094 <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
3095 need to install it for each customer.
3096 </a></h4>
3097 <p>
3098 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3099 your users. The development of this feature was kindly sponsored by
3100 NetCologne GmbH.
3101 This requires a properly setup MySQL user management and phpMyAdmin
3102 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3104 </p>
3108 access.
3109 </a></h4>
3110 <p>
3111 This depends on your system.<br />
3112 If you're running a server which cannot be accessed by other people, it's
3113 sufficient to use the directory protection bundled with your webserver
3115 If other people have telnet access to your server, you should use
3116 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3117 <br /><br />
3118 Suggestions:
3119 </p>
3120 <ul>
3121 <li>
3123 </li>
3124 <li>
3125 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3126 is a user whose password is only known to you, and apache is the
3127 group under which Apache runs.
3128 </li>
3129 <li>
3130 You should use PHP safe mode, to protect from other users that try
3132 </li>
3133 </ul>
3138 </a></h4>
3139 <p>
3144 </p>
3147 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3148 authentication.
3149 </a></h4>
3153 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3154 and/or
3156 are wrong.</li>
3158 <li>You have already setup a security mechanism for the
3159 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3160 phpMyAdmin's authentication, so remove it.</li>
3161 </ul>
3168 and put the privileges you want. For example,
3170 would let a user create/manage his/her database(s).</p>
3175 <p> If you have existing rules from an old .htaccess file, you can take them
3178 be a major benefit here if your installation is suited to using it. Then
3179 you can just add those updated lines into the
3183 <p> If you want a pre-made sample, you can try this fragment. It stops the
3184 'root' user from logging in from any networks other than the private
3187 <pre>
3188 //block root from logging in except from the private networks
3189 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3190 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3191 'deny root from all',
3192 'allow root from localhost',
3196 );
3197 </pre>
3202 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3203 different than the one set in your
3205 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3206 while a domain name is defined in the config file.</p>
3211 <p>When starting phpMyAdmin, you can use the <tt>db</tt>, <tt>pma_username</tt>, <tt>pma_password</tt> and <tt>server</tt> parameters. This last one can contain either the numeric host index (from <tt>$i</tt> of the configuration file) or one of the host names present in the configuration file. Using <tt>pma_username</tt> and <tt>pma_password</tt> has been tested along with the usage of 'cookie' <tt>auth_type</tt>.</p>
3217 when trying to create a table with more than 14 fields.
3218 </a></h4>
3219 <p>
3220 We could reproduce this problem only under Win98/98SE. Testing under
3221 WinNT4 or Win2K, we could easily create more than 60 fields.
3222 <br />
3223 A workaround is to create a smaller number of fields, then come back to
3224 your table properties and add the other fields.
3225 </p>
3229 <p>
3230 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3231 with each script/website that use forms.<br />
3232 Upgrade or downgrade your Xitami server.
3233 </p>
3236 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3237 <p>
3238 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3239 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3240 don't seem to work.<br />
3242 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3243 the user's temporary directory, so they must be moved before closing
3244 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3247 </p>
3251 Explorer never stores the cookies.
3252 </a></h4>
3253 <p>
3254 MS Internet Explorer seems to be really buggy about cookies, at least till
3256 in this area!
3257 <br />
3258 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3259 work!
3260 </p>
3264 rows.
3265 </a></h4>
3266 <p>
3268 </p>
3271 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3272 when trying to modify a row in a table with many fields, or with a text field
3273 </a></h4>
3274 <p>
3275 Your table neither have a primary key nor an unique one, so we must use a
3276 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
3277 those browsers, and this not happen in Netscape, for example. The
3278 workaround is to create a primary or unique key, or use another browser.
3279 <br />
3280 </p>
3284 page.
3285 </a></h4>
3286 <p>
3287 Some browsers support right-clicking into the frame you want to refresh,
3288 just do this in the right frame.<br />
3289 </p>
3293 query box.
3294 </a></h4>
3295 <p>
3296 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3297 Mozilla versions.<br />
3298 </p>
3302 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3303 </a></h4>
3304 <p>
3305 This is a Mozilla bug (see bug #26882 at
3307 </p>
3312 </a></h4>
3313 <p>
3314 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3315 data in octet-stream mode. Since we can't detect the specific Netscape
3316 version, we cannot workaround this bug.
3317 </p>
3321 wrong.</a></h4>
3323 <p> Please ensure that you have set your browser's character set to the one of the
3324 language file you have selected on phpMyAdmin's start page.
3325 Alternatively, you can try the auto detection mode that is supported by the
3326 recent versions of the most browsers.</p>
3329 <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
3332 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3333 Netscape and Mozilla do not have this problem.</p>
3336 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3337 I cannot manage two servers: I log in to the first one, then the other one,
3338 but if I switch back to the first, I have to log in on each operation.</a></h4>
3344 but nothing happens after that, only a blank screen.</a></h4>
3347 bug in Opera6, because it is not able to interpret frameset definitions
3348 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3349 Opera7 at least.</p>
3358 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3363 address and you are starting
3365 containing a domain name, or the reverse situation.</li>
3366 <li>Security settings in IE and/or Microsoft Security Center are
3367 too high, thus blocking scripts execution.</li>
3368 <li>The Windows Firewall is blocking Apache and MySQL. You must
3372 </ul>
3375 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3376 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3377 installed in their Firefox is causing the problem.</p>
3384 </a></h4>
3385 <p>
3386 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3387 specifying a wrong field-type.<br />
3388 Common errors include:
3389 </p>
3390 <ul>
3393 </ul>
3394 <p>
3395 Also, look at the syntax chapter in the MySQL manual to confirm that your
3396 syntax is correct.
3397 </p>
3401 phpMyAdmin generates only one index with those 2 fields.
3402 </a></h4>
3403 <p>
3405 index. If you want two indexes, create the first one when creating the
3406 table, save, then display the table properties and click the Index link to
3407 create the other index.
3408 </p>
3412 <p>
3413 Since version 2.2.3, you have a checkbox for each field that can be null.
3415 field's value. Since version 2.5.5, you have to use the checkbox to get
3417 a literal NULL in the field, and not a NULL value (this works in PHP4).
3418 </p>
3423 <p> Click on a database or table name in the left frame, the properties will be
3425 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3426 statements that can be used to recreate your database/table.
3427 <br /><br />
3429 transmit the resulting dump to your station. Depending on your PHP
3430 configuration, you will see options to compress the dump. See also the
3432 configuration variable.<br /><br />
3435 this document.</p>
3440 </a></h4>
3442 <p> Click on a database name in the left frame, the properties will be
3444 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3446 the path to your dump filename, or use the Browse button. Then click Go.
3447 <br /><br />
3449 that you upgrade to take advantage of the new features.
3450 <br /><br />
3452 in this document.
3453 </p>
3458 <p> Here is an example with the tables persons, towns and countries, all
3460 table, create it as explained in the configuration section. Then create the
3461 example tables:</p>
3463 <pre>
3464 CREATE TABLE REL_countries (
3465 country_code char(1) NOT NULL default '',
3466 description varchar(10) NOT NULL default '',
3467 PRIMARY KEY (country_code)
3468 ) TYPE=MyISAM;
3470 INSERT INTO REL_countries VALUES ('C', 'Canada');
3472 CREATE TABLE REL_persons (
3473 id tinyint(4) NOT NULL auto_increment,
3474 person_name varchar(32) NOT NULL default '',
3476 country_code char(1) NOT NULL default '',
3477 PRIMARY KEY (id)
3478 ) TYPE=MyISAM;
3480 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3481 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3483 CREATE TABLE REL_towns (
3485 description varchar(30) NOT NULL default '',
3486 PRIMARY KEY (town_code)
3487 ) TYPE=MyISAM;
3489 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3490 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3491 </pre>
3497 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3501 </ul>
3509 <li>In the fields row, choose persons.person_name and click the
3511 <li>Do the same for towns.description and countries.descriptions in the
3514 the correct joins have been generated</li>
3516 </ul>
3520 <p>
3521 Starting from the previous example, create the pma_table_info as explained
3522 in the configuration section, then browse your persons table,
3523 and move the mouse over a town code or country code.
3524 <br /><br />
3525 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3526 enables: drop-down list of possible values.
3527 </p>
3530 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3531 <p>
3534 <br /><br />
3535 Then you need to think about your schema layout. Which tables will go on
3536 which pages?
3537 </p>
3538 <ul>
3544 page and click Go. If you like, you
3546 linked tables onto the new page.</li>
3547 <li>Select the name of the new page (making sure the Edit radio button
3548 is selected) and click Go.</li>
3550 Coordinates are relative; your diagram will
3551 be automatically scaled to fit the page. When initially placing tables
3552 on the page, just pick any coordinates -- say, 50x50. After clicking
3554 position the element correctly.</li>
3556 first be sure to click the Save
3557 button beneath the list of tables and coordinates, to save any changes
3558 you made there. Then scroll all the way down, select the
3560 you want, and click Go.</li>
3561 <li>Internet Explorer for Windows may suggest an incorrect filename when
3566 browsers on Windows, do not have this problem.</li>
3567 </ul>
3571 columns!</a></h4>
3573 <p> No, it's MySQL that is doing
3579 underscores in the database name?</a></h4>
3581 <p> If you do not put a backslash before the underscore, this is a wildcard
3584 john2db ...<br /><br />
3586 If you put a backslash before the underscore, it means that the database
3587 name will have a real underscore.</p>
3591 statistics pages?</a></h4>
3602 if it already exists during the import. It does NOT drop the table after
3603 your export, it only affects the import file.</li>
3605 Otherwise, you may get an error if the table name exists but has a
3606 different structure.</li>
3608 (if any) will be included in backup.</li>
3610 field and table names formed with special characters are protected.</li>
3612 types set in the pmadb in the dump as
3614 </li>
3615 </ul>
3620 command, for better documentation (but resulting file is bigger).</li>
3622 once the INSERT verb and the table name.</li>
3625 </li>
3627 more info is provided in the
3629 but basically with this selected, invalid values are adjusted and
3630 inserted rather than causing the entire statement to fail.</li>
3631 </ul>
3635 in its name.</a></h4>
3638 is the normal way to reference a database and table name. Worse, MySQL
3639 will usually let you create a database with a dot, but then you cannot
3640 work with it, nor delete it.</p>
3653 for usage.<br />
3654 On a more recent pear version, I had problems with the state of Net_DIME
3655 being beta, so this single command
3657 needed modules.<br />
3658 If you use the Validator, you should be aware that any
3660 submit will be stored anonymously (database/table/column names,
3661 strings, numbers replaced with generic values). The Mimer
3664 We utilize it as free SOAP service.</p>
3668 it, but MySQL says "BLOB column '...' used in key specification without
3671 <p> The right way to do this, is to create the field without any indexes,
3673 dialog. On this page, you will be able to choose your BLOB field, and
3674 set a size to the index, which is the condition to create an index on
3675 a BLOB field.</p>
3679 editing fields?</a></h4>
3681 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3682 with many editing fields (table structure changes, row editing, etc.)
3683 (must be enabled in configuration - see.
3685 You can also have a look at the directive
3687 ('vertical') and see if this eases up editing for you.</p>
3691 WTF is this feature then useful for?</a></h4>
3693 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3694 on them. Otherwise you could just put a comment on the field. Because entering
3695 your own mimetype will cause serious syntax checking issues and validation,
3696 this introduces a high-risk false-user-input situation. Instead you have to
3697 initialize mimetypes using functions or empty mimetype definitions.<br />
3698 Plus, you have a whole overview of available mimetypes. Who knows all those
3699 mimetypes by heart so he/she can enter it at will?</p>
3703 can't I see any bookmarks below the query box? What is this variable for?
3704 </a></h4>
3706 <p> Any query you have executed can be stored as a bookmark on the page where the
3707 results are displayed. You will find a button labeled 'Bookmark this query'
3708 just at the end of the page.<br />
3709 As soon as you have stored a bookmark, it is related to the database you run
3710 the query on. You can now access a bookmark dropdown on each page, the query
3711 box appears on for that database.<br /><br />
3713 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3717 aware of that you HAVE to create a valid query, otherwise your query won't be
3718 even able to be stored in the database.<br />
3720 for your query will remain the way it is, but will be stripped of the /**/
3721 chars. So you can use:<br /><br />
3725 which will be expanded to<br /><br />
3729 in your query, where VARIABLE is the string you entered in the input box. If
3730 an empty string is provided, no replacements are made.<br /><br />
3732 A more complex example. Say you have stored this query:<br /><br />
3734 <br /><br />
3737 the full query will be:<br /><br />
3740 <br /><br />
3744 spaces inserted there
3745 will be later also inserted as spaces in your query and may lead to unexpected
3746 results especially when
3748 Your initial query which is going to be stored as a bookmark has to yield at
3749 least one result row so
3750 you can store the bookmark. You may have that to work around using well
3754 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3755 include exported table?</a></h4>
3757 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3758 document should look like following one (assuming you have table
3761 <pre>
3762 \documentclass{article} % or any class you want
3763 \usepackage{longtable} % for displaying table
3764 \begin{document} % start of document
3765 \include{table} % including exported table
3766 \end{document} % end of document
3767 </pre>
3771 access them.
3772 </a></h4>
3775 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3776 enable users to see all the database names.
3779 So if your users do not need those privileges, you can remove them and their
3780 databases list will shorten.</p>
3784 possible values for a field, based on some foreign table?</a></h4>
3786 <p> You have to setup appropriate links between the tables, and also
3790 foreign table, a drop-down list of values will be available.
3791 You will see two lists of values, the first list containing the key
3792 and the display field, the second list containing the display field
3793 and the key. The reason for this is to be able to type the first
3794 letter of either the key or the display field.<br /><br />
3796 For 200 values or more, a distinct window will appear, to browse foreign
3797 key values and choose one.</p>
3801 automatically when entering Browse mode for a table?</a></h4>
3803 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3804 </p>
3808 Excel files, how can I enable that?</a></h4>
3810 <p> Current version does support direct export to Microsoft Excel and Word
3811 versions 2000 and newer. If you need export older versions, you can use
3813 which works out of the box or you can
3815 several problems, most important are limitation of cell content to 255
3816 chars and no support for charsets, so think carefully whether you want to
3817 enable this.</b>. For enabling this you need to set
3821 module Spreadsheet_Excel_Writer into php include path. The
3822 installation can be done by following command:</p>
3824 <pre>
3825 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3826 </pre>
3828 <p> First part of switches set we want to install beta version of that module
3829 (no stable version available yet) and then we tell pear we want to satisfy
3830 dependencies.</p>
3832 <p> If you are running in PHP safe mode, you will have to set
3835 modules are located, for example:</p>
3837 <pre>
3838 safe_mode_include_dir = /usr/local/lib/php
3839 </pre>
3843 <pre>
3844 cd phpMyAdmin
3845 mkdir tmp
3846 chmod o+rwx tmp
3847 </pre>
3851 what happens to my column comments stored in pmadb?</a></h4>
3853 <p> Automatic migration of a table's pmadb-style column comments to the native
3854 ones is done whenever you enter Structure page for this table.</p>
3861 <p> Our Bug Tracker is located at
3863 under the Bugs section.<br /><br />
3865 But please first discuss your bug with other users:<br />
3871 existing language, where do I start?</a></h4>
3873 <p> Always use the current SVN version of your language file.
3875 don't know how to get the SVN version, please ask one of the developers.
3876 <br />
3877 Please note that we try not to use HTML entities like &eacute; in
3878 the translations, since we define the right character set in the file.
3879 With HTML entities, the text on JavaScript messages would not
3880 display correctly.
3881 However there are some entities that need to be there, for quotes
3882 ,non-breakable spaces, ampersands, less than, greater than.<br />
3883 You can then put your translations, as a zip file to avoid losing special
3884 characters, on the sourceforge.net translation tracker.<br />
3885 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3886 list, because this is where we ask for translations of new messages.</p>
3890 phpMyAdmin. How should I proceed?</a></h4>
3896 </li>
3898 <li>generate patch with your changes:
3900 </li>
3903 tracker of the phpMyAdmin project</a>.
3904 </li>
3905 </ol>
3907 <p> Write access to the SVN tree is granted only to experienced developers who
3908 have already contributed something useful to phpMyAdmin.<br />
3914 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3916 <p> Please refer to
3917 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3918 </p>
3920 <!-- DEVELOPERS -->
3923 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3924 great features have been written by other people and you too can help to
3925 make phpMyAdmin a useful tool.</p>
3927 <p> If you're planning to contribute source, please read the following
3928 information:</p>
3934 it free from other code.<br />
3935 Commonly used functions should be added to
3938 <li>Obviously, you're free to use whatever coding style you want. But
3939 please try to keep your code as simple as possible: beginners are
3940 using phpMyAdmin as an example application.<br />
3941 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3942 compliant on one hand, they fit the
3945 coding standards</a>
3946 on the other hand. Please pay attention to this.</li>
3947 <li>Please try to keep up the file-naming conventions. Table-related stuff
3950 <li>Please don't use verbose strings in your code, instead add the string
3955 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3956 better debug and profile their code.<br />
3957 Please see the
3959 options for more information.<br />
3960 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3961 lost during its re-entry into Earth's atmosphere and in memory of the
3962 brave men and women who gave their lives for the people of Earth.</li>
3963 </ul>
3965 <!-- CREDITS -->
3968 <pre>
3969 phpMyAdmin - Credits
3970 ====================
3972 CREDITS, in chronological order
3973 -------------------------------
3976 * creator of the phpmyadmin project
3980 * multi-language version
3981 * various fixes and improvements
3983 * current project maintainer
3986 * started SourceForge phpMyAdmin project in March 2001
3987 * sync'ed different existing CVS trees with new features and bugfixes
3988 * multi-language improvements, dynamic language selection
3989 * current project maintainer
3990 * many bugfixes and improvements
3993 * rewrote and optimized javascript, DHTML and DOM stuff
3994 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
3995 generate XHTML1.0 and CSS2 compliant codes
3996 * improved the language detection system
3997 * many bugfixes and improvements
4000 * database maintenance controls
4001 * table type code
4003 * DB-based configuration (Not completed)
4006 * many bugfixes and improvements
4009 * bookmarks feature
4010 * multiple dump feature
4011 * gzip dump feature
4012 * zip dump feature
4015 * various fixes
4016 * moderator of the phpMyAdmin former users forum at phpwizard.net
4022 * rewrote and fix dump code
4023 * bugfixes
4026 * rewrote dump code for PHP4
4027 * mySQL table statistics
4028 * bugfixes
4031 * main author of the version 2.1.0.1
4032 * bugfixes
4036 * abstract database interface (PMA_DBI) with MySQLi support
4037 * privileges administration
4039 * various features and fixes
4040 * German language file updates
4043 * automatic joins in QBE
4044 * links column in printview
4045 * Relation view
4048 * enhanced index creation/display feature
4049 * feature to use a different charset for HTML than for MySQL
4050 * improvements of export feature
4051 * various features and fixes
4052 * Czech language file updates
4055 (http://sf.net/projects/phpmysqlformgen/)
4056 * suggested the patch for multiple table printviews
4059 * built the patch for vertical display of table rows
4060 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4061 * Improvement of column/db comments
4062 * (MIME)-Transformations for columns
4063 * Use custom alias names for Databases in left frame
4064 * hierarchical/nested table display
4065 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4066 * new icon sets
4067 * vertical display of column properties page
4068 * some bugfixes, features, support, German language additions
4071 * japanese kanji encoding conversion feature
4074 * the Cookie authentication mode
4077 * table relation-links feature
4080 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4081 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4082 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4088 * phpMyAdmin logo (until June 2004)
4091 * blowfish library from the Horde project
4094 * mysqli support
4095 * many bugfixes and improvements
4098 * redesign for 2.6.0
4099 * phpMyAdmin sailboat logo (June 2004)
4102 * Representation at conferences
4105 * interface improvements
4106 * various bugfixes
4108 - Ivan A Kirillov
4109 * new relations Designer
4111 And also to the following people who have contributed minor changes,
4112 enhancements, bugfixes or support for a new language since version 2.1.0:
4114 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4115 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4116 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4117 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4119 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4120 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4121 Luís V., Martijn W. van der Lee,
4122 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4126 Original Credits of Version 2.1.0
4127 ---------------------------------
4129 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4130 to create a web-based interface to MySQL using PHP3. Although I have not
4131 used any of his source-code, there are some concepts I've borrowed from
4132 him. phpMyAdmin was created because Peter told me he wasn't going to
4133 further develop his (great) tool.
4134 Thanks go to
4136 code for the check when dropping a table or database. He also suggested
4137 that you should be able to specify the primary key on tbl_create.php3. To
4138 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4139 well as a bug-report. Plus many smaller improvements.
4141 were introduced in 1.3.0 (including quite significant ones like the
4142 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4143 bug-fixes and help.
4145 language-independent by outsourcing the strings to a separate file. He
4146 also contributed the French translation.
4148 tbl_select.php3, a feature to display only some fields from a table.
4150 functions in tbl_change.php3. He also added the
4153 servers and is a regular contributor for bug-fixes.
4155 features for 2.0.6.
4156 The following people have contributed minor changes, enhancements, bugfixes
4157 or support for a new language:
4158 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4159 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4160 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4161 G. Wieggers.
4163 And thanks to everyone else who sent me email with suggestions, bug-reports
4164 and or just some feedback.
4165 </pre>
4171 <ul>
4173 - the default name of Apache's directory-level configuration file.</li>
4177 - a software application that enables a user to display and interact with
4178 text, images, and other information typically located on a web page at a
4179 website on the World Wide Web.</li>
4181 - a free software/open source data compression algorithm and program
4182 developed by Julian Seward.</li>
4184 - an important World Wide Web technology that enables a client web browser
4185 to request data from a program executed on the Web server.</li>
4187 - a log or record of changes made to a project.</li>
4189 - a computer system that accesses a (remote) service on another computer
4190 by some kind of network.</li>
4192 - a set of data values of a particular simple type, one for each row of
4193 the table.</li>
4195 - a packet of information sent by a server to a World Wide Web browser
4196 and then sent back by the browser each time it accesses that server.</li>
4198 - Comma-seperated values</li>
4201 - an organized collection of data.</li>
4204 - a PHP module that extends PHP with additional functionality.</li>
4206 - a list of commonly asked question and there answers.</li>
4208 - one part of divided data/columns.</li>
4210 - a field or group of fields in a database record that point to a key
4211 field or group of fields forming a key of another database record in some
4212 (usually different) table.</li>
4214 - the free PDF library</li>
4216 GD Graphics Library</a> - a library by Thomas Boutell and others for
4217 dynamically manipulating images.</li>
4220 - gzip is short for GNU zip, a GNU free software file compression
4221 program.</li>
4223 - any machine connected to a computer network, a node that has a hostname.</li>
4225 - the unique name by which a network attached device is known on a network.</li>
4227 (HyperText Transfer Protocol)</a>
4228 - the primary method used to transfer or convey information on the World
4229 Wide Web.</li>
4232 additional security measures.</li>
4233 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4234 - a set of Internet-based services for servers using Microsoft Windows.</li>
4236 - a feature that allows quick access to the rows in a table.</li>
4238 - a data-oriented protocol used by source and destination hosts for
4239 communicating data across a packet-switched internetwork.</li>
4241 - a unique number that devices use in order to identify and communicate
4242 with each other on a network utilizing the Internet Protocol standard.</li>
4244 (Internet Server Application Programming Interface)</a>
4245 - the API of Internet Information Services (IIS).</li>
4247 - a business or organization that offers users access to the Internet and related services.</li>
4249 - a most commonly used standard method of lossy compression for
4250 photographic images.</li>
4256 - line of personal computers is designed, developed, manufactured, and
4257 marketed by Apple Computer.</li>
4258 <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>
4259 - the operating system which is included with all currently shipping Apple
4260 Macintosh computers in the consumer and professional markets.</li>
4262 - a cryptographic library.</li>
4264 - the MCrypt PHP extension.</li>
4265 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4266 - an Internet Standard for the format of e-mail.</li>
4268 - some sort of extension for the Apache Webserver.</li>
4270 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4271 Management System (DBMS).</li>
4273 - the improved MySQL client PHP extension.</li>
4275 - the MySQL client PHP extension.</li>
4277 - open standard for office documents.</li>
4278 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4279 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4281 (Portable Document Format)</a>
4282 - a file format developed by Adobe Systems for representing two
4283 dimensional documents in a device independent and resolution independent
4284 format.</li>
4286 - the PHP Extension and Application Repository.</li>
4288 - the perl-compatible regular expression functions for PHP</li>
4290 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4291 programming language used mainly for developing server-side applications
4292 and dynamic web content, and more recently, a broader range of software
4293 applications.</li>
4295 - a connection through which data is sent and received.</li>
4297 - Request for Comments (RFC) documents are a series of memoranda
4298 encompassing new research, innovations, and methodologies applicable to
4299 Internet technologies.</li>
4303 - represents a single, implicitly structured data item in a table.</li>
4305 - a computer system that provides services to other computing
4306 systems over a network.</li>
4307 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4308 - handlers for different table types</li>
4310 - a form of inter-process communication.</li>
4312 Sockets Layer)</a>
4313 - a cryptographic protocol which provides secure communication on the Internet.</li>
4315 - Structured Query Language</li>
4317 - a set of data elements (cells) that is organized, defined and stored as
4318 horizontal rows and vertical columns where each item can be uniquely
4319 identified by a label or key or by it?s position in relation to other items.</li>
4322 - a type of archive file format: the Tape ARchive format.</li>
4324 - one of the core protocols of the Internet protocol suite.</li>
4328 - a sequence of characters, conforming to a standardized format, that is
4329 used for referring to resources, such as documents and images on the
4330 Internet, by their location.</li>
4332 - A computer (program) that is responsible for accepting HTTP requests
4333 from clients and serving them Web pages.</li>
4335 - a W3C-recommended general-purpose markup language for creating
4336 special-purpose markup languages, capable of describing many different
4337 kinds of data.</li>
4339 - a popular data compression and archival format.</li>
4341 - an open-source, cross-platform data compression library by Jean-loup
4342 Gailly and Mark Adler.</li>
4343 </ul>
4353 </body>
4354 </html>