| blob | 4c520d3875448af28147d77f8429c1968c4d4de7 |
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 and the Standard PHP Library (SPL) extension.
63 </li>
65 <li>You need GD2 support in PHP to display inline
67 original aspect ratio</li>
73 load pages significantly slower.
74 </li>
75 </ul>
76 </li>
79 </ul>
81 <!-- INTRODUCTION -->
84 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
85 a single database. To accomplish the latter you'll need a properly set up
86 MySQL user who can read/write only the desired database. It's up to you to
87 look up the appropriate part in the MySQL manual.
88 </p>
93 <li>create, copy, drop, rename and alter databases, tables, fields and
94 indexes</li>
95 <li>maintenance server, databases and tables, with proposals on server
96 configuration</li>
97 <li>execute, edit and bookmark any
99 batch-queries</li>
102 </li>
109 OpenDocument Text and Spreadsheet,
111 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
112 </li>
116 <li>using Query-by-example (QBE), create complex queries automatically
117 connecting required tables</li>
119 your Database layout</li>
121 <li>transform stored data into any format using a set of predefined
122 functions, like displaying BLOB-data as image or download-link
123 </li>
129 </li>
130 </ul>
133 <p> Many people have difficulty
134 understanding the concept of user management with regards to phpMyAdmin. When
135 a user logs in to phpMyAdmin, that username and password are passed directly
136 to MySQL. phpMyAdmin does no account management on its own (other than
137 allowing one to manipulate the MySQL user account information); all users
138 must be valid MySQL users.</p>
147 <!-- INSTALLATION -->
155 </ol>
158 phpMyAdmin does not apply any special security methods to the MySQL database
159 server. It is still the system administrator's job to grant permissions on
161 be used for this.
162 </p>
170 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
171 before uploading them to your server, as PHP seems not to like
176 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
177 Downloads page. Some kits contain only the English messages,
178 others contain all languages in UTF-8 format (this should be fine
179 in most situations), others contain all
180 languages and all character sets. We'll assume you chose a kit whose
182 </li>
183 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
185 document root. If you don't have direct access to your document root,
186 put the files in a directory on your local machine, and, after step 4,
187 transfer the directory on your web server using, for example, ftp.</li>
188 <li>Ensure that all the scripts have the appropriate owner (if PHP is
189 running in safe mode, having some scripts with an owner different
190 from the owner of other scripts will be a
195 <li>Now you must configure your installation. There are two methods that
196 can be used. Traditionally, users have hand-edited a copy of
198 provided for those who prefer a graphical installation. Creating a
199 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
200 <ul><li>To manually create the file, simply use your text editor to
203 file) in the main (top-level) phpMyAdmin directory (the one
207 default value is okay for a particular setting, there is no
209 few directives to get going, a simple configuration may look
210 like this:
211 <pre>
212 <?php
213 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
215 $i=0;
216 $i++;
217 $cfg['Servers'][$i]['auth_type'] = 'cookie';
218 ?>
219 </pre>
220 Or, if you prefer to not be prompted every time you log in:
221 <pre>
222 <?php
224 $i=0;
225 $i++;
226 $cfg['Servers'][$i]['user'] = 'root';
227 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
228 ?>
229 </pre>
230 For a full explanation of possible configuration values, see the
236 directory. This is a security measure. On a Linux/Unix system you
237 can use the following commands:
238 <pre>
239 cd phpMyAdmin
240 mkdir config # create directory for saving
241 chmod o+rw config # give it world writable permissions
242 </pre>
243 And to edit an existing configuration, copy it over first:
244 <pre>
245 cp config.inc.php config/ # copy current configuration for editing
246 chmod o+w config/config.inc.php # give it world writable permissions
247 </pre>
248 On other platforms, simply create the folder and ensure that your
257 the webserver does not have the proper permissions you may see the
259 config/</tt> directory exists and has the proper permissions -
261 and upload (via FTP or some similar means) to the proper location.<br /><br />
263 Once the file has been saved, it must be moved out of the <tt>
264 config/</tt> directory and the permissions must be reset, again
265 as a security measure:
266 <pre>
267 mv config/config.inc.php . # move file to current directory
268 chmod o-rw config.inc.php # remove world read and write permissions
269 </pre>
270 Now the file is ready to be used. You can choose to review or edit
271 the file with your favorite editor, if you prefer to set some
272 advanced options which the setup script does not provide.</li></ul></li>
273 <li>If you are using the
275 protect the phpMyAdmin installation directory because using
276 config does not require a user to
277 enter a password to access the phpMyAdmin installation. Use of an alternate
278 authentication method is recommended, for example with
286 in your browser. phpMyAdmin should now display a welcome screen
287 and your databases, or a login dialog if using
289 authentication mode.</li>
291 webserver configuration. For Apache you can use supplied .htaccess file
292 in that folder, for other webservers, you should configure this yourself.
293 Such configuration prevents from possible path exposure and cross side
294 scripting vulnerabilities that might happen to be found in that code.</li>
295 </ol>
299 <p> For a whole set of new features (bookmarks, comments,
302 transformation, etc.) you need to create a set of special tables. Those
303 tables can be located in your own database, or in a central database for a
304 multi-user installation (this database would then be accessed by the
305 controluser, so no other user should have rights to it).</p>
315 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
316 that you may need special (administrator) privileges to create the database
317 and tables, and that the script may need some tuning, depending on the
318 database name.</p>
323 section</a>. You will also need to have a controluser with the proper rights
330 unpacked one. Configuration files from very old versions (2.3.0 or before) may
331 require some tweaking as some options have been changed or removed.
333 statement that you might find near the end of your configuration file.</p>
337 is version-specific.</p>
340 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
341 you should run the SQL script found in
348 where you want to give users access to their own database and don't want
349 them to play around with others.<br />
350 Nevertheless be aware that MS Internet Explorer seems to be really buggy
352 in this area!<br />
355 that your user/password pair are not in clear in the configuration file.
356 </li>
359 authentication modes are more secure: the MySQL login information does
360 not need to be set in the phpMyAdmin configuration file (except possibly
362 However, keep in mind that the password travels in plain text, unless
363 you are using the HTTPS protocol.<br />
364 In cookie mode, the password is stored, encrypted with the blowfish
365 algorithm, in a temporary cookie.</li>
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 want to use the many new relation and bookmark features:
406 <pre>
408 </pre>
414 on a set of particular databases. Normally you shouldn't give global
415 privileges to an ordinary user, unless you understand the impact of those
416 privileges (for example, you are creating a superuser).<br />
420 <pre>
421 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
422 </pre>
424 What the user may now do is controlled entirely by the MySQL user
425 management system.<br />
427 authentication mode, you don't need to fill the user/password fields
429 array.</li>
430 </ul>
435 method and allows you to log in as any valid MySQL user.</li>
436 <li>Is supported with most PHP configurations. For
449 mode.</li>
450 </ul>
454 <ul><li>You can use this method as a replacement for the
456 (for example, if you're running
458 <li>Obviously, the user must enable cookies in the browser, but this is
459 now a requirement for all authentication modes.</li>
460 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
461 with the same username.</li>
462 <li>If you want to log in to arbitrary server see
467 not required.</li>
468 </ul>
472 <ul><li>This mode is a convenient way of using credentials from another
473 application to authenticate to phpMyAdmin.</li>
474 <li>The other application has to store login information into
475 session data.</li>
477 section.</li>
478 </ul>
481 <ul><li>This mode is the less secure one because it requires you to fill the
483 $cfg['Servers'][$i]['user']</a> and
485 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
486 can read your config.inc.php can discover your username and password).
487 <br />
494 is an entry explaining how to protect your configuration file.</li>
495 <li>For additional security in this mode, you may wish to consider the Host
496 authentication
498 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
500 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
501 directives.</li>
502 <li>Unlike cookie and http, does not require a user to log in when first
503 loading the phpMyAdmin site. This is by design but could allow any
504 user to access your installation. Use of some restriction method is
506 HTTP-AUTH directive or disallowing incoming HTTP requests at
507 one’s router or firewall will suffice (both of which
508 are beyond the scope of this manual but easily searchable with Google).</li>
509 </ul>
511 <p>
512 The Swekey is a low cost authentication USB key that can be used in
513 web applications.<br /><br />
514 When Swekey authentication is activated, phpMyAdmin requires the
515 users's Swekey to be plugged before entering the login page (currently
516 supported for cookie authentication mode only). Swekey Authentication is
517 disabled by default.<br /><br />
519 </p>
520 <pre>
521 $cfg['Servers'][$i]['auth_swekey_config'] = './swekey.conf';
522 </pre>
523 <p>
525 each user with their Swekey Id. A self documented sample file is provided
527 users' information.<br /><br />
528 If you want to purchase a Swekey please visit
530 since this link provides funding for phpMyAdmin.
531 </p>
532 <!-- CONFIGURATION -->
536 users:</span> PHP does not seem to like
540 before saving a script you have modified.</p>
545 section to create one. This file only needs to contain the parameters you want to
546 change from their corresponding default value in
549 <p> The parameters which relate to design (like colors) are placed in
552 your site specific code to be included on start and end of each page.</p>
556 (with full path) to your phpMyAdmin installation's directory.
559 some web servers are case–sensitive.
562 Starting with version 2.3.0, it is advisable to try leaving this
563 blank. In most cases phpMyAdmin automatically detects the proper
564 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
565 href="https://sf.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
566 A good test is to browse a table, edit a row and save it. There should
567 be an error message if phpMyAdmin is having trouble auto–detecting
568 the correct value. If you get an error that this must be set or if
569 the autodetect code fails to detect your path, please post a bug
570 report on our bug tracker so we can improve the code.</dd>
574 with master / foreign – tables (see
576 <br />
577 If you tried to set this up and it does not work for you, have a look on
579 use it. You will find a link that will analyze why those features have
580 been disabled.<br />
581 If you do not want to use those features set this variable to
585 <dd>A warning is displayed on the main page if Suhosin is detected.
587 from appearing.</dd>
591 domain to call phpMyAdmin inside a frame, and is a potential security
592 hole allowing cross-frame scripting attacks.</dd>
596 algorithm to encrypt the password.<br />
598 passphrase of your choice. It will be used internally by the blowfish
599 algorithm: you won’t be prompted for this passphrase. The maximum
604 MySQL servers. Therefore, a
606 been added which contains the login information for the different servers.
607 The first
609 contains the hostname of the first server, the second
611 the hostname of the second server, etc. In
613 server definition, however you can put as many as you need in
615 have to define all settings, just those you need to change).</dd>
619 $i-th MySQL-server. E.g. localhost.</dd>
624 ignores this port number and connects with the socket, so if you want
625 to connect to a port different from the default port, use
628 </dd>
632 To determine the correct socket, check your MySQL configuration or, using the
634 Among the resulting information displayed will be the socket used.</dd>
637 <dd>Whether to enable SSL for connection to MySQL server.
638 </dd>
641 <dd>What type connection to use with the MySQL server. Your options are
643 is nearly guaranteed to be available on all MySQL servers, while
644 sockets are not supported on some platforms.<br /><br />
646 To use the socket mode, your MySQL server must be on the same machine
647 as the Web server.</dd>
650 <dd>What php MySQL extension to use for the connection. Valid options are:
651 <br /><br />
654 The classic MySQL extension. This is the recommended and default
655 method at this time.<br /><br />
658 The improved MySQL extension. This extension became available
659 with php 5.0.0 and is the recommended way to connect to a server
663 <dd>Whether to use a compressed protocol for the MySQL server connection
664 or not (experimental).<br />
670 </dt>
672 all relational features (see
674 and, for a MySQL server previous to 4.1.2 or running with
677 authentication mode).<br /><br />
680 cookie authentication modes (or 'config'
681 authentication mode since phpMyAdmin 2.2.1), you need to supply the
686 This account is used to check what databases the user will see at
687 login.<br />
691 In phpMyAdmin versions before 2.2.5, those were called
695 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
696 <dd>Whether config or cookie or
698 should be used for this server.
700 is the plain old way: username and password are stored in
702 <li>'cookie' authentication mode
704 2.2.3 allows you to log in as any valid MySQL user with the
705 help of cookies. Username and password are stored in
706 cookies during the session and password is deleted when it
707 ends. This can also allow you to log in in arbitrary server if
708 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
709 </li>
710 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
711 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
712 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
713 <li>'signon' authentication mode
715 as introduced in 2.10.0 allows you to log in from prepared PHP
716 session data. This is useful for implementing single signon
717 from another application. Sample way how to seed session is in
723 </ul>
726 for more information.
727 </dd>
729 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
730 </dt>
731 <dd>
733 names for hardware authentication. Leave empty to deactivate this feature.
734 </dd>
738 </dt>
739 <dd>
740 When using auth_type = 'config', this is the user/password-pair
741 which phpMyAdmin will use to connect to the
742 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
743 cookie authentication is used and should be empty.</dd>
745 <span
747 </dt>
748 <dd>
749 Allow attempt to log in without password when a login with password
750 fails. This can be used together with http authentication, when
751 authentication is done some other way and phpMyAdmin gets user name
752 from auth and uses empty password for connecting to MySQL. Password
753 login is still tried first, but as fallback, no password method is
754 tried.</dd>
757 </dt>
758 <dd>
759 If set to a (an array of) database name(s), only this (these) database(s)
760 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
761 database(s) name(s) may contain MySQL wildcards characters
765 This setting is an efficient way to lower the server load since the
766 latter does not need to send MySQL requests to build the available
768 privileges rules of the MySQL database server</span>. If set, it just
769 means only these databases will be displayed but
771 <br /><br />
773 An example of using more that one database:
775 <br /><br />
777 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
778 databases in the left frame, so that you can individually arrange your databases.<br />
779 If you want to have certain databases at the top, but don't care about the others, you do not
780 need to specify all other databases. Use:
782 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
783 order.</dd>
786 </dt>
787 <dd>Regular expression for hiding some databases. This only hides them
788 from listing, but a user is still able to access them (using, for example,
789 the SQL query area). To limit access, use the MySQL privilege system.
790 <br /><br />
795 More information on regular expressions can be found in the
797 PCRE pattern syntax</a> portion of the PHP reference manual.
798 </dd>
801 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
802 this string will be displayed instead of the hostname in the pull-down
803 menu on the main page. This can be useful if you want to show only
804 certain databases on your system, for example. For HTTP auth, all
805 non-US-ASCII characters will be stripped.</dd>
809 </dt>
810 <dd>The name of the database containing the linked-tables infrastructure.
811 <br /><br />
814 section in this document to see the benefits of this infrastructure,
815 and for a quick way of creating this database and the needed tables.
816 <br /><br />
818 If you are the only user of this phpMyAdmin installation, you can
819 use your current database to store those special tables; in this
820 case, just put your current database name in
822 set this parameter to the name of your central database containing
823 the linked-tables infrastructure.</dd>
827 </dt>
829 useful for queries you often run.<br /><br />
831 To allow the usage of this functionality:
833 <li>enter the table name in
835 </ul>
836 </dd>
840 </dt>
842 which field is a key in another table (a foreign key). phpMyAdmin
843 currently uses this to
844 <ul><li>make clickable, when you browse the master table, the data values
845 that point to the foreign table;</li>
847 when browsing the master table, if you move the mouse to a column
848 containing a foreign key (use also the 'table_info' table);<br />
851 <li>in edit/insert mode, display a drop-down list of possible foreign
855 <li>display links on the table properties page, to check referential
856 integrity (display missing foreign keys) for each described key;
857 </li>
861 schema of your database (also uses the table_coords table).</li>
862 </ul>
864 The keys can be numeric or character.<br /><br />
866 To allow the usage of this functionality:
869 infrastructure</li>
870 <li>put the relation table name in
872 <li>now as normal user open phpMyAdmin and for each one of your
873 tables where you want to use this feature, click
875 </li>
876 </ul>
880 future development of the cross-db relations.
881 </dd>
885 </dt>
886 <dd>
887 Since release 2.3.0 you can describe, in a special 'table_info'
888 table, which field is to be displayed as a tool-tip when moving the
889 cursor over the corresponding key.<br />
890 This configuration variable will hold the name of this special
891 table. To allow the usage of this functionality:
893 <li>put the table name in
895 <li>then for each table where you want to use this feature,
897 to choose the field.</li>
898 </ul>
900 </dd>
904 </dt>
907 the relations between your tables. To do this it needs two tables
912 schema output).<br /><br />
916 To allow the usage of this functionality:
919 infrastructure</li>
920 <li>put the correct table names in
923 </ul>
926 </dd>
930 </dt>
932 Since release 2.3.0 you can store comments to describe each column for
934 <br /><br />
936 Starting with release 2.5.0, comments are consequently used on the table
937 property pages and table browse view, showing up as tool-tips above the
938 column name (properties page) or embedded within the header of table in
939 browse view. They can also be shown in a table dump. Please see the
940 relevant configuration directives later on.<br /><br />
942 Also new in release 2.5.0 is a MIME-transformation system which is also
944 Transformations</a> for further information. To use the
945 MIME-transformation system, your column_info table has to have the three
946 new fields 'mimetype', 'transformation', 'transformation_options'.
947 <br /><br />
949 To allow the usage of this functionality:
951 infrastructure</li>
952 <li>put the table name in
956 <pre>
957 ALTER TABLE `pma_column_comments`
958 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
959 ADD `transformation` VARCHAR( 255 ) NOT NULL,
960 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
961 </pre>
964 renamed from<br />
967 </ul>
968 </dd>
972 </dt>
975 all queries you entered manually into the phpMyAdmin interface. If you
976 don't want to use a table-based history, you can use the JavaScript-based
977 history. Using that, all your history items are deleted when closing the
978 window.<br /><br />
980 Using
982 you can specify an amount of history items you want to have on hold. On
983 every login, this list gets cut to the maximum amount.<br /><br />
985 The query history is only available if JavaScript is enabled in your
986 browser.<br /><br />
988 To allow the usage of this functionality:
991 infrastructure</li>
993 </li>
994 </ul>
995 </dd>
999 </dt>
1001 to visually manage the relations.
1002 <br /><br />
1004 To allow the usage of this functionality:
1007 infrastructure</li>
1009 </li>
1010 </ul>
1011 </dd>
1014 </dt>
1016 column_info table got enhanced with three new fields. If the above variable
1018 latest table structure available. If not, it will emit a warning to the
1019 superuser.<br /><br />
1021 You can disable this checking behavior by setting the variable to false,
1022 which should offer a performance increase.<br /><br />
1024 Recommended to set to FALSE, when you are sure, your table structure is
1025 up to date.</dd>
1027 boolean</dt>
1028 <dd>Whether to allow root access. This is just simplification of rules below.
1029 </dd>
1032 </dt>
1034 authentication is disabled.<br /><br />
1037 all deny rules followed by allow rules. Access is allowed by default. Any
1038 client which does not match a Deny command or does match an Allow command
1039 will be allowed access to the server. <br /><br />
1042 applies all allow rules followed by deny rules. Access is denied by
1043 default. Any client which does not match an Allow directive or does
1044 match a Deny directive will be denied access to the server.<br /><br />
1046 If your rule order is set to 'explicit', the authentication is
1047 performed in a similar fashion to rule order 'deny,allow', with the
1051 and was available in Apache by specifying allow and deny rules without
1052 setting any order.<br /><br />
1054 Please also see <a
1056 address behind proxies.
1057 </dd>
1059 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1060 </dt>
1061 <dd>The general format for the rules is as such:
1063 <pre>
1065 </pre>
1070 well (please note that those containing SERVER_ADDRESS might not be
1071 available on all webservers):
1072 <pre>
1078 </pre>
1080 Having an empty rule list is equivalent to either using
1086 following work:<br />
1088 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1089 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1090 But the following does not work:<br />
1093 </dd>
1094 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1095 <dd>Name of session which will be used for signon authentication method.
1096 </dd>
1098 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1099 </dd>
1101 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1102 </dd>
1105 <dd>If you have more than one server configured, you can set
1107 that server when phpMyAdmin is started, or set it to 0 to be given a
1108 list of servers without logging in.<br />
1110 MUST be set to that server.</dd>
1113 <dd>The maximum number of database names to be displayed in the
1114 navigation frame and the database list.</dd>
1117 <dd>The maximum number of table names to be displayed in the
1118 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1119 when in Light mode.</dd>
1122 <dd>The maximum number of characters when a SQL query is displayed. The
1123 default limit of 1000 should be correct to avoid the display of tons
1124 of hexadecimal codes that represent BLOBs, but some users have real
1125 SQL queries that are longer than 1000 characters. Also, if a query's
1126 length exceeds this limit, this query is not saved in the history.</dd>
1129 <dd>Defines whether to use GZip output buffering for increased
1131 Set to true/false for enabling/disabling. When set to 'auto' (string),
1132 phpMyAdmin tries to enable output buffering and will automatically disable
1133 it if your browser has some problems with buffering. IE6 with a certain patch
1134 is known to cause data corruption when having enabled buffering.</dd>
1137 <dd>Whether persistent connections should be used or not (mysql_connect or
1138 mysql_pconnect).</dd>
1144 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1145 to zero, no time limit is imposed.<br />
1146 This setting is used while importing/exporting dump files but has no
1147 effect when PHP is running in safe mode.</dd>
1150 <dd>Set the number of bytes a script is allowed to allocate. If number set
1151 to zero, no limit is imposed.<br />
1152 This setting is used while importing/exporting dump files but has no
1153 effect when PHP is running in safe mode.<br />
1157 <dd>Mark used tables and make it possible to show databases with locked
1162 generated by phpMyAdmin should be displayed or not.</dd>
1165 <dd>Defines whether normal users (non-administrator) are allowed to
1166 delete their own database or not. If set as FALSE, the link "Drop
1168 mydatabase" will be rejected. Quite practical for
1170 customers.<br />
1171 Please note that this limitation of SQL queries is not as strict as
1172 when using MySQL privileges. This is due to nature of SQL queries
1173 which might be quite complicated. So this choice should be viewed as
1174 help to avoid accidental dropping rather than strict privilege
1175 limitation.</dd>
1179 displayed when you're about to lose data.</dd>
1182 <dd>Define whether the previous login should be recalled or not in cookie
1183 authentication mode.</dd>
1190 means that it will be kept for existing session. This is recommended
1191 for not trusted environments.</dd>
1194 <dd>If enabled (default), logout deletes cookies for all servers,
1195 otherwise only for current one. Setting this to false makes it easy to
1196 forget to log out from other server, when you are using more of
1197 them.</dd>
1203 <dd>Define whether phpMyAdmin will continue executing a multi-query
1204 statement if one of the queries fails. Default is to abort execution.</dd>
1207 <dd>Define whether phpMyAdmin will output the results of each query of a
1208 multi-query statement embedded into the
1213 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1214 <br /><br />
1217 MySQL servers behind the firewall where your
1219 </dd>
1222 <dd>Defines whether to use a select-based menu and display only the current
1223 tables in the left frame (smaller page). Only in Non-Lightmode you can
1224 use the feature to display nested folders using
1226 </dd>
1229 <dd>In light mode, defines whether to display the names of databases (in the
1230 selector) using a tree, see also
1232 </dd>
1235 <dd>The string used to separate the parts of the database name when showing
1236 them in a tree.</dd>
1239 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1240 This means if you have tables like 'first__second__third' this will be
1242 If set to FALSE or empty, the feature is disabled. NOTE: You should
1243 not use this separator at the beginning or end of a
1244 table name or multiple times after another without any other
1245 characters in between.</dd>
1248 <dd>Defines how many sublevels should be displayed when splitting
1249 up tables by the above separator.</dd>
1252 <dd>Defines whether to display table comment as tool-tip in left frame or
1253 not.</dd>
1256 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1257 comment and the real name. That means that if you have a table called
1258 'user0001' and add the comment 'MyName' on it, you will see the name
1259 'MyName' used consequently in the left frame and the tool-tip shows
1260 the real name of the DB.</dd>
1263 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1265 When setting this to 'nested', the Alias of the Tablename is only used
1266 to split/nest the tables according to the
1268 directive. So only the folder is called like the Alias, the tablename itself
1269 stays the real tablename.</dd>
1272 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1275 <dd>Enter URL where logo in the navigation frame will point to.
1276 For use especially with self made theme which changes this.
1285 <dd>Defines whether or not to display a server choice at the top of the left frame.
1286 Defaults to FALSE.</dd>
1288 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1289 Defaults to FALSE (drop-down).</dd>
1291 <dd>Defines whether to display database choice in light navigation frame as links
1292 instead of in a drop-down. Defaults to 'auto' - on main page list is
1293 shown, when database is selected, only drop down is displayed.</dd>
1296 <dd>Defines the tab displayed by default when clicking the small
1297 icon next to each table name in the navigation panel. Possible
1303 <dd>Defines whether or not to display space usage and statistics about databases
1304 and tables.<br />
1305 Note that statistics requires at least MySQL 3.23.3 and that, at this
1306 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1309 <dd>Defines whether to display detailed server information on main page.
1310 You can additionally hide more information by using
1312 </dd>
1317 </dt>
1320 not at the starting main (right) frame. This setting
1321 does not check MySQL commands entered directly.<br /><br />
1323 Please note that to block the usage of phpinfo() in scripts, you
1330 hard coded password value in the configuration file, end users can't
1331 be allowed to change their passwords.</dd>
1334 <dd>Defines whether to suggest a database name on the
1338 <dd>Defines whether navigation bar buttons and the right panel top menu
1339 contain text or symbols only. A value of TRUE displays icons, FALSE
1340 displays text and 'both' displays both icons and text.</dd>
1343 <dd>Defines whether a user should be displayed a
1347 <dd>Number of rows displayed when browsing a result set. If the result set
1354 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1358 from editing when browsing a table's content. Valid values are:
1363 </ul>
1364 </dd>
1367 <dd>Defines whether or not MySQL functions fields should be initially
1368 displayed in edit/insert mode. Since version 2.10, the user can
1369 toggle this setting from the interface.
1370 </dd>
1373 <dd>Defines which type of editing controls should be used for CHAR and
1374 VARCHAR fields. Possible values are:
1375 <ul><li>input - this allows to limit size of text to size of field in
1376 MySQL, but has problems with newlines in fields</li>
1377 <li>textarea - no problems with newlines in fields, but also no
1378 length limitations</li>
1379 </ul>
1380 Default is old behavior so input.</dd>
1386 <dd>If there are fewer items than this in the set of foreign keys, then a
1387 drop-down box of foreign keys is presented, in the style described by the
1389 setting.</dd>
1392 <dd>For the foreign key drop-down fields, there are several methods of
1393 display, offering both the key and value data. The contents of the
1394 array should be one or both of the following strings:
1400 </dt>
1401 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1402 creating a dump file</dd>
1405 </dt>
1406 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1407 compressed exports. This doesn't affect smaller dumps and allows users to
1408 create larger dumps that won't otherwise fit in memory due to php
1409 memory limit. Produced files contain more GZip/BZip2 headers, but all
1410 normal programs handle this correctly.</dd>
1414 mainframe.</dd>
1418 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1423 <dd>How many columns will be utilized to display the tables on the
1424 database property view? Default is 1 column. When setting this to a
1425 value larger than 1, the type of the database will be omitted for more
1426 display space.</dd>
1430 <dd>Defines the tab displayed by default on server view. Possible
1437 <dd>Defines the tab displayed by default on database view. Possible
1442 <dd>Defines the tab displayed by default on table view. Possible
1449 points to the MySQL documentation (type depends
1450 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1451 generated.<br />
1453 for more information about MySQL manuals and their types.</dd>
1456 <dd>Type of MySQL documentation:
1462 </ul>
1463 </dd>
1466 <dd>Defines the default language to use, if not browser-defined or
1467 user-defined.<br />
1469 this setting.</dd>
1472 <dd>Defines the default connection collation to use, if not
1473 user-defined.<br />
1478 <dd>Force: always use this language (must be defined in the
1482 <dd>Limit list of available languages to those matching the given regular
1483 expression. For example if you want only Czech and English, you should
1487 <dd>Default character set to use for recoding of MySQL queries. This must be
1488 enabled and it's described by
1490 option.<br />
1491 You can give here any character set which is in
1493 array and this is just default choice, user can select any of them.</dd>
1496 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1497 support (compiled in or module) in PHP to allow MySQL queries recoding
1498 and used language file must have it enabled (by default only these
1499 which are in Unicode, just to avoid losing some characters).<br /><br />
1502 in the Export page, to choose the character set when exporting a file.
1503 </dd>
1506 <dd>You can select here which functions will be used for character set
1507 conversion. Possible values are:
1508 <ul><li>auto - automatically use available one (first is tested
1509 iconv, then recode)</li>
1512 </ul>
1513 Default is auto.</dd>
1516 <dd>Specify some parameters for iconv used in charset conversion. See
1519 used, so that invalid characters will be transliterated.</dd>
1522 <dd>Available character sets for MySQL conversion. You can add your own (any of
1523 supported by recode/iconv) or remove these which you don't use.
1524 Character sets will be shown in same order as here listed, so if you
1525 frequently use some of these move them to the top.</dd>
1530 default empty, you need to fill in some trusted proxy servers if you
1531 want to use rules for IP addresses behind proxy.<br /><br />
1533 The following example specifies that phpMyAdmin should trust a
1535 <pre>
1536 $cfg['TrustedProxies'] =
1538 </pre>
1539 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1540 client's IP address as usual.
1541 </dd>
1545 MIME transformations.<br />
1546 Possible values are:
1547 <ul><li>auto - automatically detect, this is a bit expensive
1549 according to your server real possibilities</li>
1552 </ul>
1553 Default is auto.
1554 </dd>
1557 <dd>
1558 We normally check the permissions on the configuration file to ensure
1559 it's not world writable. However, phpMyAdmin could be installed on
1560 a NTFS filesystem mounted on a non-Windows server, in which case the
1561 permissions seems wrong but in fact cannot be detected. In this case
1563 </dd>
1567 </dd>
1569 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1570 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1571 </dt>
1572 <dd>The background styles used for both the frames.
1575 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1577 <dd>The style used for the pointer in the navi frame.
1581 </dt>
1582 <dd>The color used for the database name in the navi frame.
1591 </dd>
1595 <dd>The style used for table headers. See
1600 </dd>
1604 </dd>
1606 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1608 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1610 </dt>
1612 The former feature highlights the row over which your mouse is passing
1613 and the latter lets you visually mark/unmark rows by clicking on
1614 them.<br />
1619 <dd>You put here a valid CSS font family value, for example
1624 <dd>You put here a valid CSS font family value, for example
1638 </dt>
1640 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1642 The Char* values are used for CHAR and VARCHAR editing (if configured
1646 </dt>
1650 </dt>
1651 <dd>Defines if the whole textarea of the query box will be selected on
1652 click.</dd>
1655 </dt>
1656 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1657 editing.</dd>
1660 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1661 Can be turned off by a toggle button on the browse page.</dd>
1665 </dt>
1666 <dd>Defines the place where modify and delete links would be put when
1667 tables contents are displayed (you may have them displayed both at the
1668 left and at the right).
1674 </dt>
1676 Define which one is displayed by default. The first mode displays each
1677 row on a horizontal line, the second rotates the headers by 90
1678 degrees, so you can use descriptive headers even though fields only
1679 contain small values and still print them out. The vertical mode sorts
1680 each row on a vertical lineup.<br /><br />
1682 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1683 the rotation of the header for horizontalflipped is done via CSS. If
1684 set to 'fake' PHP does the transformation for you, but of course this
1685 does not look as good as CSS.</dd>
1689 string or integer</dt>
1690 <dd>When editing/creating new columns in a table all fields normally get
1691 lined up one field a line. (default: 'horizontal'). If you set this to
1692 'vertical' you can have each field lined up vertically beneath each
1693 other. You can save up a lot of place on the horizontal direction and
1694 no longer have to scroll. If you set this to integer, editing of fewer
1695 columns will appear in 'vertical' mode, while editing of more fields
1696 still in 'horizontal' mode. This way you can still effectively edit
1697 large number of fields, while having full view on few of them.</dd>
1701 </dt>
1703 display of column comments in Browse or Property display. In browse
1704 mode, the comments are shown inside the header. In property mode,
1705 comments are displayed using a CSS-formatted dashed-line below the
1706 name of the field. The comment is shown as a tool-tip for that field.
1707 </dd>
1719 <dd>Whether to display a link to validate a query in any SQL Query box.
1726 <dd>
1727 The name of the directory where
1729 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1730 are available under a drop-down box when you click the database or
1731 table name, then the Import tab.
1732 <br /><br />
1734 If you want different directory for each user, %u will be replaced
1735 with username.<br /><br />
1739 compressed formats is enabled).<br /><br />
1741 This feature is useful when your file is too big to be uploaded via
1743 uploads are disabled in PHP.<br /><br />
1745 Please note that if PHP is running in safe mode, this directory must
1746 be owned by the same user as the owner of the phpMyAdmin scripts.
1747 <br /><br />
1751 alternatives.
1752 </dd>
1755 <dd>
1756 The name of the directory where dumps can be saved.<br /><br />
1758 If you want different directory for each user, %u will be replaced
1759 with username.<br /><br />
1761 Please note that the directory must exist and has to be writable for
1762 the user running webserver.<br /><br />
1764 Please note that if PHP is running in safe mode, this directory must
1765 be owned by the same user as the owner of the phpMyAdmin scripts.
1766 </dd>
1769 <dd>
1770 The name of the directory where temporary files can be stored.
1771 <br /><br />
1772 This is needed for native MS Excel export, see
1775 </dd>
1778 <dd>
1779 In this array are defined default parameters for export, names of
1780 items are similar to texts seen on export page, so you can easily
1781 identify what they mean.
1782 </dd>
1785 <dd>
1786 In this array are defined default parameters for import, names of
1787 items are similar to texts seen on import page, so you can easily
1788 identify what they mean.
1789 </dd>
1792 <dd>
1793 Repeat the headers every X cells, or 0 to deactivate.
1794 </dd>
1802 </dt>
1803 <dd>
1804 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1805 or icon is always displayed on the left panel. If JavaScript is enabled in
1806 your browser, a click on this opens a distinct query window, which is
1807 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1808 changes to display a query box.<br /><br />
1810 The size of this query window can be customized with
1812 - both integers for the size in pixels. Note that normally, those
1814 theme you are using.<br /><br />
1818 opens the query window and puts the current query
1819 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1820 query in the right panel's query box.
1821 <br /><br />
1822 The usage of the JavaScript query window is recommended if you have a
1823 JavaScript enabled browser. Basic functions are used to exchange quite
1824 a few variables, so most 4th generation browsers should be capable to
1825 use that feature. It currently is only tested with Internet Explorer 6
1826 and Mozilla 1.x.
1827 <br /><br />
1829 to a table, which has to be created by you (see <a
1831 all your queries will be appended to the form, but only as long as
1832 your window is opened they remain saved.
1833 <br /><br />
1834 When using the JavaScript based query window, it will always get
1835 updated when you click on a new table/db to browse and will focus if
1836 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1837 the query window by checking the box "Do not overwrite this query from
1838 outside the window" below the query textarea. Then you can browse
1839 tables/databases in the background without losing the contents of the
1840 textarea, so this is especially useful when composing a query with
1841 tables you first have to look in. The checkbox will get automatically
1842 checked whenever you change the contents of the textarea. Please
1843 uncheck the button whenever you definitely want the query window to
1844 get updated even though you have made alterations.
1845 <br /><br />
1848 <br /><br />
1849 The query window also has a custom tabbed look to group the features.
1851 default tab to be used when opening the query window. It can be set to
1852 either 'sql', 'files', 'history' or 'full'.</dd>
1858 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1860 If the approximate row count as returned by
1863 count will be used.
1864 </dd>
1866 <dd>For VIEWs, since obtaining the exact count could have an
1867 impact on performance, this value is the maximum to be displayed, using
1869 any row counting.
1870 </dd>
1874 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1876 page. By clicking on the button 'toggle scratchboard' on the page
1877 where you edit x/y coordinates of those elements you can activate a
1878 scratchboard where all your elements are placed. By clicking on an
1879 element, you can move them around in the pre-defined area and the x/y
1880 coordinates will get updated dynamically. Likewise, when entering a
1881 new position directly into the input field, the new position in the
1882 scratchboard changes after your cursor leaves the input field.<br />
1883 You have to click on the 'OK'-button below the tables to save the new
1884 positions. If you want to place a new element, first add it to the
1885 table of elements and then you can drag the new element around.<br />
1886 By changing the paper size and the orientation you can change the size
1887 of the scratchboard as well. You can do so by just changing the
1888 dropdown field below, and the scratchboard will resize automatically,
1889 without interfering with the current placement of the elements.<br />
1890 If ever an element gets out of range you can either enlarge the paper
1891 size or click on the 'reset' button to place all elements below each
1892 other.<br />
1894 get this control to work. The basic Drag&Drop script functionality
1895 was kindly borrowed from www.youngpup.net and is underlying so
1896 specific license.</dd>
1899 <dd>Sorts database and table names according to natural order (for example,
1900 t1, t2, t10). Currently implemented in the left panel (Light mode)
1901 and in Database view, for the table list.</dd>
1905 closed state. A value of 'open' does the reverse.</dd>
1911 <dd>Allows you to specify window's title bar. Following magic string can
1912 be used to get special values:
1913 <dl>
1919 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1928 </dl>
1929 </dd>
1939 </dd>
1942 <dd>If theme manager is active, use this as the path of the subdirectory
1943 containing all the themes.</dd>
1957 </dt>
1958 <dd>Default queries that will be displayed in query boxes when user didn't
1959 specify any. Use %d for database name, %t for table name and %f for a
1960 comma separated list of field names. Note that %t and %f are only
1964 <dd>
1965 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
1966 default we use HTML to format the query, but you can disable this by
1968 </dd>
1971 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1972 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1973 query inside a bracket is indented. By changing
1976 specifies the units of the indent amount that you specified. This is
1977 used via stylesheets.</dd>
1980 <dd>This array is used to define the colours for each type of element of
1981 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1983 If you specify an empty string for the color of a class, it is ignored
1984 in creating the stylesheet.
1985 You should not alter the class names, only the colour strings.<br />
2006 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2010 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2011 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2012 </ul>
2013 </dd>
2017 <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,
2018 as originally published on
2020 <br />
2021 For help in setting up your system to use the service, see the
2023 </dd>
2027 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2028 and any password, so we use those by default. Instead, if
2029 you have an account with them, you can put your login details
2030 here, and it will be used in place of the anonymous login.</dd>
2031 </dl>
2032 </dd>
2035 <dd><b>DEVELOPERS ONLY!</b></dd>
2038 <dd><b>DEVELOPERS ONLY!</b><br />
2039 Enable logging queries and execution times to be displayed in the bottom
2040 of main page (right frame).</dd>
2043 <dd><b>DEVELOPERS ONLY!</b><br />
2044 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2045 the code.<br />
2046 For help in setting up your system to this, see the
2050 <dd><b>DEVELOPERS ONLY!</b><br />
2051 Enable profiling support for phpMyAdmin. This will append a chunk of data
2052 to the end of every page displayed in the main window with profiling
2053 statistics for that page.<br />
2054 You may need to increase the maximum execution time for this to
2055 complete successfully.<i>Profiling was removed from the code for
2056 version 2.9.0 due to licensing issues.</i></dd>
2058 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2059 <dd><b>DEVELOPERS ONLY!</b><br />
2060 When profiling data is displayed, this variable controls the threshold of
2061 display for any profiling data, based on the average time each time has
2062 taken. If it is over the threshold it is displayed, otherwise it is not
2063 displayed. This takes a value in milliseconds. In most cases you don't need
2064 to edit this.</dd>
2067 <dd>All possible types of a MySQL column. In most cases you don't need to
2068 edit this.</dd>
2071 <dd>Possible attributes for fields. In most cases you don't need to edit
2072 this.</dd>
2075 <dd>A list of functions MySQL supports. In most cases you don't need to
2076 edit this.</dd>
2079 <dd>Mapping of column types to meta types used for preferring displayed
2080 functions. In most cases you don't need to edit this.</dd>
2083 <dd>Functions preferred for column meta types as defined in
2084 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2085 to edit this.</dd>
2088 <dd>Functions selected by default when inserting/changing row, Functions
2089 are defined for meta types from
2091 <code>first_timestamp</code>, which is used for first timestamp column
2092 in table.</dd>
2095 <dd>Operators available for search operations on numeric and date fields.
2096 </dd>
2099 <dd>Operators available for search operations on character fields.
2100 Note that we put <code>LIKE</code> by default instead of
2101 <code>LIKE %...%</code>, to avoid unintended performance problems
2102 in case of huge tables.</dd>
2105 <dd>Operators available for search operations on enum fields.</dd>
2108 <dd>Additional operators available for search operations when the
2109 field can be null.</dd>
2111 </dl>
2113 <!-- TRANSFORMATIONS -->
2119 </ol>
2123 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2125 section</a> on how to do so.</p>
2127 <p> You can apply different transformations to the contents of each field. The
2128 transformation will take the content of each field and transform it with
2129 certain rules defined in the selected transformation.</p>
2131 <p> Say you have a field 'filename' which contains a filename. Normally you would
2132 see in phpMyAdmin only this filename. Using transformations you can transform
2133 that filename into a HTML link, so you can click inside of the phpMyAdmin
2134 structure on the field's link and will see the file displayed in a new browser
2135 window. Using transformation options you can also specify strings to
2136 append/prepend to a string or the format you want the output stored in.</p>
2138 <p> For a general overview of all available transformations and their options,
2139 you can consult your
2140 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2141 installation.</p>
2143 <p> For a tutorial on how to effectively use transformations, see our
2145 the official phpMyAdmin homepage.</p>
2149 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2150 clicking on the 'Structure' link for a table). There click on
2151 "Change" (or change icon) and there you will see three new fields at
2152 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2153 'Transformation options'.</p>
2155 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2156 that corresponds to the column's contents. Please note that
2157 transformations are inactive as long as no MIME-type is selected.</li>
2159 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2160 hopefully growing amount of pre-defined transformations. See below for information on
2161 how to build your own transformation.<br />
2163 There are global transformations and mimetype-bound transformations. Global transformations
2164 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2165 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2166 transformations which operate on the main mimetype (like 'image'), which will most likely
2167 take the subtype into regard, and those who only operate on a
2168 specific subtype (like 'image/jpeg').<br />
2170 You can use transformations on mimetypes for which the function was not defined for. There
2171 is no security check for you selected the right transformation, so take care of what the
2172 output will be like.</li>
2174 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2175 transform-function specific options here. Usually the transforms can operate with default
2176 options, but it is generally a good idea to look up the overview to see which options are
2177 necessary.<br />
2179 Much like the ENUM/SET-Fields, you have to split up several options using the format
2180 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2181 parsed as an array, leaving the first value the first element in the array, and so
2182 forth.<br />
2184 If you want to specify a MIME character set you can define it in the transformation_options.
2185 You have to put that outside of the pre-defined options of the specific mime-transform,
2187 for which you can specify 2 options and you want to append a character set, enter "'first
2188 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2190 </ul>
2194 <p> All mimetypes and their transformations are defined through single files in
2195 the directory 'libraries/transformations/'.</p>
2197 <p> They are stored in files to ease up customization and easy adding of new
2198 transformations.</p>
2200 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2201 always work. It makes no sense to apply a transformation to a mimetype, the
2202 transform-function doesn't know to handle.</p>
2204 <p> One can, however, use empty mime-types and global transformations which should work
2205 for many mimetypes. You can also use transforms on a different mimetype they where built
2206 for, but pay attention to option usage as well as what the transformation does to your
2207 field.</p>
2209 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2210 any other transform function and provides some basic functions.</p>
2212 <p> There are 5 possible file names:</p>
2214 <ol><li>A mimetype+subtype transform:<br /><br />
2216 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2218 Please not that mimetype and subtype are separated via '_', which shall
2219 not be contained in their names. The transform function/filename may
2220 contain only characters which cause no problems in the file system as
2221 well as the PHP function naming convention.<br /><br />
2223 The transform function will the be called
2224 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2226 <b>Example:</b><br /><br />
2228 <tt>text_html__formatted.inc.php</tt><br />
2229 <tt>PMA_transform_text_html__formatted()</tt></li>
2231 <li>A mimetype (w/o subtype) transform:<br /><br />
2233 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2235 Please note that there are no single '_' characters.
2236 The transform function/filename may contain only characters which cause
2237 no problems in the file system as well as the PHP function naming
2238 convention.<br /><br />
2240 The transform function will the be called
2241 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2243 <b>Example:</b><br /><br />
2245 <tt>text__formatted.inc.php</tt><br />
2246 <tt>PMA_transform_text__formatted()</tt></li>
2248 <li>A mimetype+subtype without specific transform function<br /><br />
2250 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2252 Please note that there are no '__' characters in the filename. Do not
2253 use special characters in the filename causing problems with the file
2254 system.<br /><br />
2256 No transformation function is defined in the file itself.<br /><br />
2258 <b>Example:</b><br /><br />
2260 <tt>text_plain.inc.php</tt><br />
2261 (No function)</li>
2263 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2265 <tt>[mimetype].inc.php</tt><br /><br />
2267 Please note that there are no '_' characters in the filename. Do not use
2268 special characters in the filename causing problems with the file system.
2269 <br /><br />
2271 No transformation function is defined in the file itself.<br /><br />
2273 <b>Example:</b><br /><br />
2275 <tt>text.inc.php</tt><br />
2276 (No function)</li>
2278 <li>A global transform function with no specific mimetype<br /><br />
2280 <tt>global__[transform].inc.php</tt><br /><br />
2282 The transform function will the be called
2283 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2285 <b>Example:</b><br /><br />
2287 <tt>global__formatted</tt><br />
2288 <tt>PMA_transform_global__formatted()</tt></li>
2289 </ol>
2291 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2292 transform function.</p>
2294 <p> All filenames containing no '__' in themselves are not shown as valid transform
2295 functions in the dropdown.</p>
2297 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2298 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2299 without a transform function. Also note the introduction of a function description in
2300 the language files. For each function a $strTransformation_[filename without .inc.php]
2301 has to exist.</p>
2303 <p> You can use the template generator to generate new functions and entries in the
2304 language file.</p>
2306 <p> To create a new transform function please see
2307 <tt>libraries/transformations/template_generator.sh</tt>.
2308 To create a new, empty mimetype please see
2309 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2311 <p> A transform function always gets passed three variables:</p>
2313 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2314 you want to transform.</li>
2315 <li><b>$options</b> - Contains any user-passed options to a transform function
2316 as an array.</li>
2317 <li><b>$meta</b> - Contains an object with field information to your column.
2318 The data is drawn from the output of the
2320 function. This means, all object properties described on the
2322 available in this variable and can be used to transform a field accordingly
2323 to unsigned/zerofill/not_null/... properties.<br />
2324 The $meta->mimetype variable contains the original MIME-type of the
2325 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2326 </ol>
2328 <!-- FAQ -->
2335 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2339 </ol>
2341 <p> Please have a look at our
2343 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2344 features and or interface.</p>
2350 action is required or phpMyAdmin sends a blank page or a page full of
2351 cryptic characters to my browser, what can I do?</a></h4>
2353 <p> There are some known PHP bugs with output buffering and compression.<br />
2355 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2356 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2357 configuration file.<br />
2358 Furthermore, we know about such problems connected to the release
2359 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2360 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2365 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2366 See also the
2368 entry about PHP bugs with output buffering.<br />
2369 If your server keeps crashing, please ask for help in the various Apache
2370 support groups.</p>
2374 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2375 script: I'm always displayed the login screen.</a></h4>
2377 <p> This is a known PHP bug (see this
2379 official PHP bug database. It means there is and won't be any phpMyAdmin
2380 fix against it because there is no way to code a fix.</p>
2386 application misbehaved by not returning a complete set of
2388 </h4>
2390 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2391 Have a look at the last message in this
2393 official PHP bug database.</p>
2398 and/or many error messages with the
2400 mode.</a></h4>
2402 <p> This is a known problem with the PHP
2404 filter: it's not so stable. Please use instead the cookie authentication mode.
2405 </p>
2410 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2411 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2412 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2413 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2414 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2419 work.</a></h4>
2421 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2422 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2423 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2424 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2425 We faced PHP crashes when trying to download a dump with MS Internet
2426 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2427 this case you should switch to the release version of PHP 4.2.0.</p>
2431 an error about safe mode being in effect.</a></h4>
2433 <p> Your uploaded file is saved by PHP in the "upload dir", as
2434 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2435 the system default is <i>/tmp</i>).<br />
2436 We recommend the following setup for Apache servers running in safe mode,
2437 to enable uploads of files while being reasonably secure:</p>
2439 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2440 <li>give ownership to the Apache server's user.group:
2441 <tt>chown apache.apache /tmp/php</tt></li>
2442 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2443 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2444 <li>restart Apache</li>
2445 </ul>
2449 general file uploads don't work on my system and uploaded files have a
2450 <tt>Content-Type:</tt> header in the first line.</a></h4>
2452 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2453 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2454 So the problem is that this package has a serious bug that was corrected
2455 ages ago in PHP (2001-01-28: see
2457 for more details). The problem is that the bugged package is still
2458 available though it was corrected (see
2460 for more details).<br />
2461 So please download
2462 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2463 and the problem should go away.<br />
2464 And that fixes the \r\n problem with file uploads!</p>
2468 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2469 I'm using the Apache server.</a></h4>
2471 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2472 your <i>httpd.conf</i>:</p>
2476 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2480 uploading a file from the query box.</a></h4>
2482 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2483 restrictions. Assuming that the restriction allows you to open files in the
2484 current directory ('.'), all you have to do is create a 'tmp' directory
2485 under the phpMyAdmin install directory, with permissions 777 and the same
2486 owner as the owner of your phpMyAdmin directory. The uploaded files will
2487 be moved there, and after execution of your
2493 <p> The MySQL manual explains how to
2495 reset the permissions</a>.</p>
2500 execute a bookmark.</a></h4>
2502 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2503 cannot access the uploaded query.</p>
2508 submit a query from the convenient text area.</a></h4>
2510 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2511 and try to increase it.</p>
2515 </h4>
2517 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2518 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2519 names to align with current standards.</p>
2524 </h4>
2526 <p> Starting with version 2.7.0, the import engine has been re–written and these
2527 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2528 to take advantage of the new import features.</p>
2530 <p> The first things to check (or ask your host provider to check) are the
2531 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2532 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2533 All of these three settings limit the maximum size of data that can be
2534 submitted and handled by PHP. One user also said that post_max_size
2535 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2537 There exist several workarounds if your upload is too big or your
2538 hosting provider is unwilling to change the settings:</p>
2541 feature. This allows one to
2542 upload a file to the server via scp, ftp, or your favorite file transfer
2543 method. PhpMyAdmin is then able to import the files from the temporary
2545 section</a> of this document.</li>
2547 BigDump</a>) to split the files before uploading. We cannot support this
2548 or any third party applications, but are aware of users having success
2549 with it.</li>
2550 <li>If you have shell (command line) access, use MySQL to import the files
2551 directly. You can do this by issuing the "source" command from
2552 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2553 </ul>
2557 support?</a></h4>
2559 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2560 fully supported. phpMyAdmin may connect to your MySQL server
2561 using PHP's classic
2564 is available in php 5.0.<br />
2565 Either way, the developers of both extensions recommend to use the classic
2566 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2567 When compiling php, we strongly recommend that you manually link the MySQL
2568 extension of your choice to a MySQL client library of at least the same
2569 minor version since the one that is bundled with some PHP distributions is
2572 If your webserver is running on a windows system, you might want to try
2573 MySQL's
2575 instead of the MySQL / MySQLi extensions that are bundled with the official
2576 php Win32 builds.</p>
2580 message, "Client does not support authentication protocol requested
2581 by server; consider upgrading MySQL client"</a></h5>
2583 <p> You tried to access MySQL with an old MySQL client library. The version of
2584 your MySQL client library can be checked in your phpinfo() output.
2585 In general, it should have at least the same minor version as your server
2589 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2590 changed the authentication hash and your PHP is trying to use the old method.
2592 with the proper client library to match your MySQL installation. Your
2593 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2594 More information (and several workarounds) are located in the
2596 </p>
2600 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2601 capital letter in its name it is changed to lowercase as it should. But
2602 if I try to DROP this table MySQL is unable to find the corresponding
2603 file.</a></h4>
2605 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2606 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2607 directive.</p>
2611 script seems not to know the font face I'm using!</a></h4>
2613 <p> The "FPDF" library we're using for this feature requires some
2614 special files to use font faces.<br />
2616 these files.</p>
2620 check PHP Configuration".</a></h4>
2622 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2623 "MySQL extension". This extension may be part of the PHP
2624 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2625 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2626 to load the extension but failed.<br /><br />
2628 Usually, the problem is solved by installing a software package called
2629 "PHP-MySQL" or something similar.</p>
2634 and I cannot log in using cookie auth.</a></h4>
2636 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2640 so I cannot upload.</a></h4>
2642 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2643 parameter is not set to "on".</p>
2647 a new table the table and field names are changed to lowercase!</a></h4>
2649 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2650 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2651 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2652 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2653 directory and add the following line to the group [mysqld]:</p>
2655 <pre>set-variable = lower_case_table_names=0</pre>
2657 <p> Next, save the file and restart the MySQL service. You can always check the
2658 value of this directive using the query</p>
2660 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2664 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2667 </p>
2671 and I get problems, such as undefined variables when I run a
2674 <p> A tip from Jose Fandos: put a comment on the following two lines
2675 in httpd.conf, like this:</p>
2677 <pre>
2678 # mod_gzip_item_include file \.php$
2680 </pre>
2682 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2683 PHP scripts. Of course you have to restart Apache.</p>
2688 I get the error "No input file specified" when trying to
2689 run phpMyAdmin.</a></h4>
2691 <p> This is a permission problem. Right-click on the phpmyadmin folder
2692 and choose properties. Under the tab Security, click on "Add"
2693 and select the user "IUSR_machine" from the list. Now set his
2694 permissions and it should work.</p>
2698 db_structure.php with plenty of tables).</a></h4>
2701 GZIP output buffering is enabled. If you turn off it (by
2703 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2704 PHP 5.0.0.</p>
2708 message 'Errorcode: 13'. What does this mean?</a></h4>
2710 <p> This can happen due to a MySQL bug when having database / table names with
2711 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2712 To fix this, turn off this directive, convert all database and table names
2713 to lower case and turn it on again. Alternatively, there's a bug-fix
2714 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2718 and the fields are duplicated.</a></h4>
2720 <p> It is possible to configure Apache in such a way that PHP has problems
2721 interpreting .php files.</p>
2723 <p> The problems occur when two different (and conflicting) set of directives
2724 are used:</p>
2726 <pre>
2727 SetOutputFilter PHP
2728 SetInputFilter PHP
2729 </pre>
2731 <p> and</p>
2733 <pre>AddType application/x-httpd-php .php</pre>
2735 <p> In the case we saw, one set of directives was in
2736 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2737 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2738 The recommended way is with <tt>AddType</tt>, so just comment out
2739 the first set of lines and restart Apache:</p>
2741 <pre>
2742 #SetOutputFilter PHP
2743 #SetInputFilter PHP
2744 </pre>
2749 <p> This problem is known to happen when the server is running Turck MMCache
2750 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2755 <p> Yes.<br />
2756 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2757 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2758 <tt>error_reporting</tt> settings.
2759 </p>
2762 <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>
2764 <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>
2767 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2768 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2769 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2770 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2771 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2772 enabled.) Click <tt>OK</tt>.</li>
2773 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2774 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2775 </ol>
2779 PHP 5.0.4 on 64-bit systems?</a></h4>
2781 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2782 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2788 http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script. For <tt>server</tt> you use the server number which refers to
2789 the order of the server paragraph in <tt>config.inc.php</tt>.
2790 Table and script parts are optional. If you want
2791 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2792 some configuration. Following lines apply only for <a
2794 that you have enabled some features within global configuration. You need
2795 <code>Options FollowSymLinks</code> and <code>AllowOverride
2796 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2797 you need mod_rewrite to be enabled. Then you just need to create following
2798 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2799 (don't forget to change directory name inside of it):</p>
2801 <pre>
2802 RewriteEngine On
2803 RewriteBase /path_to_phpMyAdmin
2804 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2805 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2806 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2807 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2808 </pre>
2811 <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>
2813 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2814 following rewrite rule:</p>
2816 <pre>
2817 RewriteEngine On
2818 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2819 </pre>
2823 </h4>
2824 <p>
2825 There can be many explanations to this and a look at your server's
2826 error log file might give a clue.
2827 </p>
2831 password encryption in cookie auth doesn't work.</a></h4>
2833 <p> If your cluster consist of different architectures, PHP code used for
2834 encryption/decryption won't work correct. This is caused by use of
2835 pack/unpack functions in code. Only solution is to use mcrypt extension
2836 which works fine in this case.</p>
2841 <p> Yes but the default configuration values of Suhosin are known to cause
2842 problems with some operations, for example editing a table with many
2843 columns and no primary key. Tuning information is available at
2845 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2846 although the parameter names have changed (<tt>suhosin</tt> instead
2848 <tt>SuhosinDisableWarning</tt> directive</a>.
2849 </p>
2855 headers already sent by ..." is displayed, what's the problem?</a></h4>
2857 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2858 (I.E. no blank lines, no spaces, no characters...) neither before the
2859 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2860 tag at the end. We also got a report from a user under IIS, that used
2861 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
2862 contained an end-of-line character (hex 0A) at the end; removing this character
2863 cleared his errors.</p>
2868 <p> Either there is an error with your PHP setup or your username/password is
2869 wrong. Try to make a small script which uses mysql_connect and see if it
2870 works. If it doesn't, it may be you haven't even compiled MySQL support
2871 into PHP.</p>
2875 connect to local MySQL server through socket '/tmp/mysql.sock'
2876 (111) ..." is displayed. What can I do?</a></h4>
2878 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2880 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2881 In your <i>php.ini</i> you will find a line</p>
2883 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2885 <p> change it to</p>
2887 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2889 <p> Then restart apache and it will work.</p>
2891 <p> Here is a fix suggested by Brad Ummer:</p>
2893 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2894 To do this, telnet to your server and go to the MySQL bin directory. In
2895 this directory there should be a file named <i>mysqladmin</i>. Type
2896 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2897 info about your MySQL server, including the socket
2898 (<i>/tmp/mysql.sock</i>, for example).</li>
2899 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2900 phpMyAdmin, you need to complete the socket information in the
2901 <i>config.inc.php</i>.<br />
2902 For example:
2904 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
2905 <br /><br />
2907 Please also make sure that the permissions of this file allow to be readable
2908 by your webserver (i.e. '0755').</li>
2909 </ul>
2911 <p> Have also a look at the
2913 corresponding section of the MySQL documentation</a>.</p>
2917 what can I do?</a></h4>
2920 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2921 sometime.<br />
2922 Also have a look at your PHP version number: if it contains "4.0b..."
2923 it means you're running a beta version of PHP. That's not a so good idea,
2924 please upgrade to a plain revision.</p>
2928 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2929 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2931 <p> Check the value you set for the
2933 directive in the phpMyAdmin configuration file.</p>
2937 password: YES)"-error when trying to access a MySQL-Server on a
2938 host which is port-forwarded for my localhost.</a></h4>
2940 <p> When you are using a port on your localhost, which you redirect via
2941 port-forwarding to another host, MySQL is not resolving the localhost
2942 as expected.<br />
2943 Erik Wasser explains: The solution is: if your host is "localhost"
2944 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2945 connection for speeding up things. And that doesn't work in this configuration
2946 with port forwarding.<br />
2952 <p> Themes are configured with
2956 <br />
2958 should not delete the directory "original" or its underlying
2959 structure, because this is the system theme used by phpMyAdmin.
2960 "original" contains all images and styles, for backwards
2961 compatibility and for all themes that would not include images or css-files.
2962 <br /><br />
2965 is enabled, you can select your favorite theme on the main page. Your
2966 selected theme will be stored in a cookie.<br /><br /></p>
2968 <p> To create a theme:</p>
2970 <ul><li>make a new subdirectory (for example "your_theme_name") under
2972 (by default <tt>themes</tt>)</li>
2973 <li>copy the files and directories from "original" to
2974 "your_theme_name"</li>
2975 <li>edit the css-files in "your_theme_name/css"</li>
2976 <li>put your new images in "your_theme_name/img"</li>
2977 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
2978 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
2979 contain your chosen theme name, that will be visible in user interface</li>
2980 <li>make a new screenshot of your theme and save it under
2981 "your_theme_name/screen.png"</li>
2982 </ul>
2984 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2985 theme verbose name, theme generation and theme version. These versions and
2986 generations are enumerated from 1 and do not have any direct dependence on
2987 phpMyAdmin version. Themes within same generation should be backwards
2988 compatible - theme with version 2 should work in phpMyAdmin requiring
2989 version 1. Themes with different generation are incompatible.</p>
2991 <p> If you do not want to use your own symbols and buttons, remove the
2992 directory "img" in "your_theme_name". phpMyAdmin will
2993 use the default icons and buttons (from the system-theme "original").
2994 </p>
2998 what can I do?</a></h4>
3000 <p> Here are a few points to check:</p>
3002 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3004 directive empty. See also
3006 </li>
3007 <li>Maybe you have a broken PHP installation or you need to upgrade
3008 your Zend Optimizer. See
3010 http://bugs.php.net/bug.php?id=31134</a>.
3011 </li>
3012 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3013 set to the default (200) or another low value, you could get this
3014 error if your table has a high number of columns. Adjust this setting
3015 accordingly. (Thanks to Klaus Dorninger for the hint).
3016 </li>
3017 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3018 of ";" will cause this error. Replace it with "&;".
3019 </li>
3021 you might want to increase
3023 </li>
3024 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3025 </li>
3026 </ul>
3033 who logged out can not log in again in with the same nick.</a></h4>
3035 <p> This is related to the authentication mechanism (protocol) used by
3036 phpMyAdmin. To bypass this problem: just close all the opened
3037 browser windows and then go back to phpMyAdmin. You should be able to
3038 log in again.</p>
3042 limit error or a time limit error.</a></h4>
3044 <p> Compressed dumps are built in memory and because of this are limited to
3045 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3046 using
3048 (enabled by default). Zip exports can not be handled this way, so if you need
3049 Zip files for larger dump, you have to use another way.</p>
3053 or alter a table.</a></h4>
3055 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
3059 bundled with the MySQL server distribution.</a></h4>
3061 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3063 <pre>
3064 -- MySQL dump 8.22
3065 --
3066 -- Host: localhost Database: database
3067 ---------------------------------------------------------
3068 -- Server version 3.23.54
3069 </pre>
3071 <p> The invalid part of the code is the horizontal line made of dashes that
3072 appears once in every dump created with mysqldump. If you want to run your
3073 dump you have to turn it into valid MySQL. This means, you have to add a
3074 whitespace after the first two dashes of the line or add a # before it:
3075 <br />
3076 <code>
3077 -- -------------------------------------------------------<br />
3078 </code>
3079 or<br />
3080 <code>
3081 #---------------------------------------------------------
3082 </code>
3083 </p>
3090 <p> Please note that you should not use the separating string multiple times
3091 without any characters between them, or at the beginning/end of your table
3092 name. If you have to, think about using another TableSeparator or disabling
3093 that feature</p>
3098 <p> In Relation view, being able to choose a table in another database,
3099 or having more than one index field in the foreign key.<br /><br/>
3100 In Query-by-example (Query), automatic generation of the query
3101 LEFT JOIN from the foreign table.<br /><br/>
3102 </p>
3106 I get series of errors like "Warning: unable to parse url". How
3107 can this be fixed?</a></h4>
3108 <p>
3109 Your table neither have a primary key nor an unique one, so we must use a
3110 long expression to identify this row. This causes problems to parse_url
3111 function. The workaround is to create a primary or unique key.
3112 <br />
3113 </p>
3117 a MIME-Transformation onto!</a></h4>
3119 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3120 nested forms can be put inside the table where phpMyAdmin displays the results.
3121 You can, however, use any form inside of a table if keep the parent
3122 form-container with the target to tbl_row_delete.php and just put your own
3123 input-elements inside. If you use a custom submit input field, the form will
3124 submit itself to the displaying page again, where you can validate the
3125 $HTTP_POST_VARS in a transformation.
3127 For a tutorial on how to effectively use transformations, see our
3129 on the official phpMyAdmin-homepage.</p>
3133 MySQL server</a></h4>
3135 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3138 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3139 the quote-character (") is interpreted as an identifier quote character and
3140 not as a string quote character, which makes many internal phpMyAdmin
3142 statements. There is no workaround to this behaviour. News to this item will
3143 be posted in Bug report
3144 <a href="https://sf.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3145 </p>
3149 more that one column with the same value
3150 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3151 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3153 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3154 can use it for the Edit and Delete links.</p>
3159 <p> phpMyAdmin uses a quick method to get the row count, and this method
3160 only returns an approximate count in the case of InnoDB tables. See
3162 a way to modify those results, but
3163 this could have a serious impact on performance.</p>
3168 <p> The number of records in queries containing COUNT and GROUP BY is
3169 not correctly calculated. Also, sorting results of a query like
3174 containing an hyphen.
3175 </a></h4>
3176 <p>
3177 The tests I have made with current MySQL 4.1.11 API shows that the
3178 API does not accept this syntax for the USE command. Enclosing the
3179 db name with backquotes works. For further confusion, no backquotes
3180 are needed with command-line mysql.
3181 </p>
3184 <a href="#faq3_14">3.14 I am not able to browse a table when I don't have the right to SELECT one of the columns.</a></h4>
3185 <p>
3186 This has been a known limitation of phpMyAdmin since the beginning and
3187 it's not likely to be solved in the future.
3188 </p>
3190 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3193 <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
3194 need to install it for each customer.
3195 </a></h4>
3196 <p>
3197 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3198 your users. The development of this feature was kindly sponsored by
3199 NetCologne GmbH.
3200 This requires a properly setup MySQL user management and phpMyAdmin
3201 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3203 </p>
3207 access.
3208 </a></h4>
3209 <p>
3210 This depends on your system.<br />
3211 If you're running a server which cannot be accessed by other people, it's
3212 sufficient to use the directory protection bundled with your webserver
3214 If other people have telnet access to your server, you should use
3215 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3216 <br /><br />
3217 Suggestions:
3218 </p>
3219 <ul>
3220 <li>
3222 </li>
3223 <li>
3224 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3225 is a user whose password is only known to you, and apache is the
3226 group under which Apache runs.
3227 </li>
3228 <li>
3229 You should use PHP safe mode, to protect from other users that try
3231 </li>
3232 </ul>
3237 </a></h4>
3238 <p>
3243 </p>
3246 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3247 authentication.
3248 </a></h4>
3252 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3253 and/or
3255 are wrong.</li>
3257 <li>You have already setup a security mechanism for the
3258 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3259 phpMyAdmin's authentication, so remove it.</li>
3260 </ul>
3267 and put the privileges you want. For example,
3269 would let a user create/manage his/her database(s).</p>
3274 <p> If you have existing rules from an old .htaccess file, you can take them
3277 be a major benefit here if your installation is suited to using it. Then
3278 you can just add those updated lines into the
3282 <p> If you want a pre-made sample, you can try this fragment. It stops the
3283 'root' user from logging in from any networks other than the private
3286 <pre>
3287 //block root from logging in except from the private networks
3288 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3289 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3290 'deny root from all',
3291 'allow root from localhost',
3295 );
3296 </pre>
3301 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3302 different than the one set in your
3304 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3305 while a domain name is defined in the config file.</p>
3310 <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>
3316 when trying to create a table with more than 14 fields.
3317 </a></h4>
3318 <p>
3319 We could reproduce this problem only under Win98/98SE. Testing under
3320 WinNT4 or Win2K, we could easily create more than 60 fields.
3321 <br />
3322 A workaround is to create a smaller number of fields, then come back to
3323 your table properties and add the other fields.
3324 </p>
3328 <p>
3329 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3330 with each script/website that use forms.<br />
3331 Upgrade or downgrade your Xitami server.
3332 </p>
3335 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3336 <p>
3337 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3338 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3339 don't seem to work.<br />
3341 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3342 the user's temporary directory, so they must be moved before closing
3343 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3346 </p>
3350 Explorer never stores the cookies.
3351 </a></h4>
3352 <p>
3353 MS Internet Explorer seems to be really buggy about cookies, at least till
3355 in this area!
3356 <br />
3357 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3358 work!
3359 </p>
3363 rows.
3364 </a></h4>
3365 <p>
3367 </p>
3370 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3371 when trying to modify a row in a table with many fields, or with a text field
3372 </a></h4>
3373 <p>
3374 Your table neither have a primary key nor an unique one, so we must use a
3375 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
3376 those browsers, and this not happen in Netscape, for example. The
3377 workaround is to create a primary or unique key, or use another browser.
3378 <br />
3379 </p>
3383 page.
3384 </a></h4>
3385 <p>
3386 Some browsers support right-clicking into the frame you want to refresh,
3387 just do this in the right frame.<br />
3388 </p>
3392 query box.
3393 </a></h4>
3394 <p>
3395 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3396 Mozilla versions.<br />
3397 </p>
3401 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3402 </a></h4>
3403 <p>
3404 This is a Mozilla bug (see bug #26882 at
3406 </p>
3411 </a></h4>
3412 <p>
3413 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3414 data in octet-stream mode. Since we can't detect the specific Netscape
3415 version, we cannot workaround this bug.
3416 </p>
3420 wrong.</a></h4>
3422 <p> Please ensure that you have set your browser's character set to the one of the
3423 language file you have selected on phpMyAdmin's start page.
3424 Alternatively, you can try the auto detection mode that is supported by the
3425 recent versions of the most browsers.</p>
3428 <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
3431 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3432 Netscape and Mozilla do not have this problem.</p>
3435 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3436 I cannot manage two servers: I log in to the first one, then the other one,
3437 but if I switch back to the first, I have to log in on each operation.</a></h4>
3443 but nothing happens after that, only a blank screen.</a></h4>
3446 bug in Opera6, because it is not able to interpret frameset definitions
3447 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3448 Opera7 at least.</p>
3457 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3462 address and you are starting
3464 containing a domain name, or the reverse situation.</li>
3465 <li>Security settings in IE and/or Microsoft Security Center are
3466 too high, thus blocking scripts execution.</li>
3467 <li>The Windows Firewall is blocking Apache and MySQL. You must
3471 </ul>
3474 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3475 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3476 installed in their Firefox is causing the problem.</p>
3483 </a></h4>
3484 <p>
3485 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3486 specifying a wrong field-type.<br />
3487 Common errors include:
3488 </p>
3489 <ul>
3492 </ul>
3493 <p>
3494 Also, look at the syntax chapter in the MySQL manual to confirm that your
3495 syntax is correct.
3496 </p>
3500 phpMyAdmin generates only one index with those 2 fields.
3501 </a></h4>
3502 <p>
3504 index. If you want two indexes, create the first one when creating the
3505 table, save, then display the table properties and click the Index link to
3506 create the other index.
3507 </p>
3511 <p>
3512 Since version 2.2.3, you have a checkbox for each field that can be null.
3514 field's value. Since version 2.5.5, you have to use the checkbox to get
3516 a literal NULL in the field, and not a NULL value (this works in PHP4).
3517 </p>
3522 <p> Click on a database or table name in the left frame, the properties will be
3524 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3525 statements that can be used to recreate your database/table.
3526 <br /><br />
3528 transmit the resulting dump to your station. Depending on your PHP
3529 configuration, you will see options to compress the dump. See also the
3531 configuration variable.<br /><br />
3534 this document.</p>
3539 </a></h4>
3541 <p> Click on a database name in the left frame, the properties will be
3543 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3545 the path to your dump filename, or use the Browse button. Then click Go.
3546 <br /><br />
3548 that you upgrade to take advantage of the new features.
3549 <br /><br />
3551 in this document.
3552 </p>
3557 <p> Here is an example with the tables persons, towns and countries, all
3559 table, create it as explained in the configuration section. Then create the
3560 example tables:</p>
3562 <pre>
3563 CREATE TABLE REL_countries (
3564 country_code char(1) NOT NULL default '',
3565 description varchar(10) NOT NULL default '',
3566 PRIMARY KEY (country_code)
3567 ) TYPE=MyISAM;
3569 INSERT INTO REL_countries VALUES ('C', 'Canada');
3571 CREATE TABLE REL_persons (
3572 id tinyint(4) NOT NULL auto_increment,
3573 person_name varchar(32) NOT NULL default '',
3575 country_code char(1) NOT NULL default '',
3576 PRIMARY KEY (id)
3577 ) TYPE=MyISAM;
3579 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3580 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3582 CREATE TABLE REL_towns (
3584 description varchar(30) NOT NULL default '',
3585 PRIMARY KEY (town_code)
3586 ) TYPE=MyISAM;
3588 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3589 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3590 </pre>
3596 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3600 </ul>
3608 <li>In the fields row, choose persons.person_name and click the
3610 <li>Do the same for towns.description and countries.descriptions in the
3613 the correct joins have been generated</li>
3615 </ul>
3619 <p>
3620 Starting from the previous example, create the pma_table_info as explained
3621 in the configuration section, then browse your persons table,
3622 and move the mouse over a town code or country code.
3623 <br /><br />
3624 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3625 enables: drop-down list of possible values.
3626 </p>
3629 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3630 <p>
3633 <br /><br />
3634 Then you need to think about your schema layout. Which tables will go on
3635 which pages?
3636 </p>
3637 <ul>
3643 page and click Go. If you like, you
3645 linked tables onto the new page.</li>
3646 <li>Select the name of the new page (making sure the Edit radio button
3647 is selected) and click Go.</li>
3649 Coordinates are relative; your diagram will
3650 be automatically scaled to fit the page. When initially placing tables
3651 on the page, just pick any coordinates -- say, 50x50. After clicking
3653 position the element correctly.</li>
3655 first be sure to click the Save
3656 button beneath the list of tables and coordinates, to save any changes
3657 you made there. Then scroll all the way down, select the
3659 you want, and click Go.</li>
3660 <li>Internet Explorer for Windows may suggest an incorrect filename when
3665 browsers on Windows, do not have this problem.</li>
3666 </ul>
3670 columns!</a></h4>
3672 <p> No, it's MySQL that is doing
3678 underscores in the database name?</a></h4>
3680 <p> If you do not put a backslash before the underscore, this is a wildcard
3683 john2db ...<br /><br />
3685 If you put a backslash before the underscore, it means that the database
3686 name will have a real underscore.</p>
3690 statistics pages?</a></h4>
3701 if it already exists during the import. It does NOT drop the table after
3702 your export, it only affects the import file.</li>
3704 Otherwise, you may get an error if the table name exists but has a
3705 different structure.</li>
3707 (if any) will be included in backup.</li>
3709 field and table names formed with special characters are protected.</li>
3711 types set in the pmadb in the dump as
3713 </li>
3714 </ul>
3719 command, for better documentation (but resulting file is bigger).</li>
3721 once the INSERT verb and the table name.</li>
3724 </li>
3726 more info is provided in the
3728 but basically with this selected, invalid values are adjusted and
3729 inserted rather than causing the entire statement to fail.</li>
3730 </ul>
3734 in its name.</a></h4>
3737 is the normal way to reference a database and table name. Worse, MySQL
3738 will usually let you create a database with a dot, but then you cannot
3739 work with it, nor delete it.</p>
3752 for usage.<br />
3753 On a more recent pear version, I had problems with the state of Net_DIME
3754 being beta, so this single command
3756 needed modules.<br />
3757 If you use the Validator, you should be aware that any
3759 submit will be stored anonymously (database/table/column names,
3760 strings, numbers replaced with generic values). The Mimer
3763 We utilize it as free SOAP service.</p>
3767 it, but MySQL says "BLOB column '...' used in key specification without
3770 <p> The right way to do this, is to create the field without any indexes,
3772 dialog. On this page, you will be able to choose your BLOB field, and
3773 set a size to the index, which is the condition to create an index on
3774 a BLOB field.</p>
3778 editing fields?</a></h4>
3780 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3781 with many editing fields (table structure changes, row editing, etc.)
3782 (must be enabled in configuration - see.
3784 You can also have a look at the directive
3786 ('vertical') and see if this eases up editing for you.</p>
3790 WTF is this feature then useful for?</a></h4>
3792 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3793 on them. Otherwise you could just put a comment on the field. Because entering
3794 your own mimetype will cause serious syntax checking issues and validation,
3795 this introduces a high-risk false-user-input situation. Instead you have to
3796 initialize mimetypes using functions or empty mimetype definitions.<br />
3797 Plus, you have a whole overview of available mimetypes. Who knows all those
3798 mimetypes by heart so he/she can enter it at will?</p>
3802 can't I see any bookmarks below the query box? What is this variable for?
3803 </a></h4>
3805 <p> Any query you have executed can be stored as a bookmark on the page where the
3806 results are displayed. You will find a button labeled 'Bookmark this query'
3807 just at the end of the page.<br />
3808 As soon as you have stored a bookmark, it is related to the database you run
3809 the query on. You can now access a bookmark dropdown on each page, the query
3810 box appears on for that database.<br /><br />
3812 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3816 aware of that you HAVE to create a valid query, otherwise your query won't be
3817 even able to be stored in the database.<br />
3819 for your query will remain the way it is, but will be stripped of the /**/
3820 chars. So you can use:<br /><br />
3824 which will be expanded to<br /><br />
3828 in your query, where VARIABLE is the string you entered in the input box. If
3829 an empty string is provided, no replacements are made.<br /><br />
3831 A more complex example. Say you have stored this query:<br /><br />
3833 <br /><br />
3836 the full query will be:<br /><br />
3839 <br /><br />
3843 spaces inserted there
3844 will be later also inserted as spaces in your query and may lead to unexpected
3845 results especially when
3847 Your initial query which is going to be stored as a bookmark has to yield at
3848 least one result row so
3849 you can store the bookmark. You may have that to work around using well
3853 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3854 include exported table?</a></h4>
3856 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3857 document should look like following one (assuming you have table
3860 <pre>
3861 \documentclass{article} % or any class you want
3862 \usepackage{longtable} % for displaying table
3863 \begin{document} % start of document
3864 \include{table} % including exported table
3865 \end{document} % end of document
3866 </pre>
3870 access them.
3871 </a></h4>
3874 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3875 enable users to see all the database names.
3878 So if your users do not need those privileges, you can remove them and their
3879 databases list will shorten.</p>
3883 possible values for a field, based on some foreign table?</a></h4>
3885 <p> You have to setup appropriate links between the tables, and also
3889 foreign table, a drop-down list of values will be available.
3890 You will see two lists of values, the first list containing the key
3891 and the display field, the second list containing the display field
3892 and the key. The reason for this is to be able to type the first
3893 letter of either the key or the display field.<br /><br />
3895 For 200 values or more, a distinct window will appear, to browse foreign
3896 key values and choose one.</p>
3900 automatically when entering Browse mode for a table?</a></h4>
3902 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3903 </p>
3907 Excel files, how can I enable that?</a></h4>
3909 <p> Current version does support direct export to Microsoft Excel and Word
3910 versions 2000 and newer. If you need export older versions, you can use
3912 which works out of the box or you can
3914 several problems, most important are limitation of cell content to 255
3915 chars and no support for charsets, so think carefully whether you want to
3916 enable this.</b>. For enabling this you need to set
3920 module Spreadsheet_Excel_Writer into php include path. The
3921 installation can be done by following command:</p>
3923 <pre>
3924 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3925 </pre>
3927 <p> First part of switches set we want to install beta version of that module
3928 (no stable version available yet) and then we tell pear we want to satisfy
3929 dependencies.</p>
3931 <p> If you are running in PHP safe mode, you will have to set
3934 modules are located, for example:</p>
3936 <pre>
3937 safe_mode_include_dir = /usr/local/lib/php
3938 </pre>
3942 <pre>
3943 cd phpMyAdmin
3944 mkdir tmp
3945 chmod o+rwx tmp
3946 </pre>
3950 what happens to my column comments stored in pmadb?</a></h4>
3952 <p> Automatic migration of a table's pmadb-style column comments to the native
3953 ones is done whenever you enter Structure page for this table.</p>
3960 <p> Our Bug Tracker is located at
3962 under the Bugs section.<br /><br />
3964 But please first discuss your bug with other users:<br />
3970 existing language, where do I start?</a></h4>
3972 <p> Always use the current SVN version of your language file.
3974 don't know how to get the SVN version, please ask one of the developers.
3975 <br />
3976 Please note that we try not to use HTML entities like &eacute; in
3977 the translations, since we define the right character set in the file.
3978 With HTML entities, the text on JavaScript messages would not
3979 display correctly.
3980 However there are some entities that need to be there, for quotes
3981 ,non-breakable spaces, ampersands, less than, greater than.<br />
3982 You can then put your translations, as a zip file to avoid losing special
3983 characters, on the sourceforge.net translation tracker.<br />
3984 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3985 list, because this is where we ask for translations of new messages.</p>
3989 phpMyAdmin. How should I proceed?</a></h4>
3994 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
3995 </li>
3997 <li>generate patch with your changes:
3999 </li>
4002 tracker of the phpMyAdmin project</a>.
4003 </li>
4004 </ol>
4006 <p> Write access to the SVN tree is granted only to experienced developers who
4007 have already contributed something useful to phpMyAdmin.<br />
4013 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4015 <p> Please refer to
4016 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4017 </p>
4019 <!-- DEVELOPERS -->
4022 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4023 great features have been written by other people and you too can help to
4024 make phpMyAdmin a useful tool.</p>
4026 <p> If you're planning to contribute source, please read the following
4027 information:</p>
4033 it free from other code.<br />
4034 Commonly used functions should be added to
4037 <li>Obviously, you're free to use whatever coding style you want. But
4038 please try to keep your code as simple as possible: beginners are
4039 using phpMyAdmin as an example application.<br />
4040 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4041 compliant on one hand, they fit the
4044 coding standards</a>
4045 on the other hand. Please pay attention to this.</li>
4046 <li>Please try to keep up the file-naming conventions. Table-related stuff
4049 <li>Please don't use verbose strings in your code, instead add the string
4054 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4055 better debug and profile their code.<br />
4056 Please see the
4058 options for more information.<br />
4059 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4060 lost during its re-entry into Earth's atmosphere and in memory of the
4061 brave men and women who gave their lives for the people of Earth.</li>
4062 </ul>
4064 <!-- CREDITS -->
4067 <pre>
4068 phpMyAdmin - Credits
4069 ====================
4071 CREDITS, in chronological order
4072 -------------------------------
4075 * creator of the phpmyadmin project
4079 * multi-language version
4080 * various fixes and improvements
4082 * current project maintainer
4085 * started SourceForge phpMyAdmin project in March 2001
4086 * sync'ed different existing CVS trees with new features and bugfixes
4087 * multi-language improvements, dynamic language selection
4088 * current project maintainer
4089 * many bugfixes and improvements
4092 * rewrote and optimized javascript, DHTML and DOM stuff
4093 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4094 generate XHTML1.0 and CSS2 compliant codes
4095 * improved the language detection system
4096 * many bugfixes and improvements
4099 * database maintenance controls
4100 * table type code
4102 * DB-based configuration (Not completed)
4105 * many bugfixes and improvements
4108 * bookmarks feature
4109 * multiple dump feature
4110 * gzip dump feature
4111 * zip dump feature
4114 * various fixes
4115 * moderator of the phpMyAdmin former users forum at phpwizard.net
4121 * rewrote and fix dump code
4122 * bugfixes
4125 * rewrote dump code for PHP4
4126 * mySQL table statistics
4127 * bugfixes
4130 * main author of the version 2.1.0.1
4131 * bugfixes
4135 * abstract database interface (PMA_DBI) with MySQLi support
4136 * privileges administration
4138 * various features and fixes
4139 * German language file updates
4142 * automatic joins in QBE
4143 * links column in printview
4144 * Relation view
4147 * enhanced index creation/display feature
4148 * feature to use a different charset for HTML than for MySQL
4149 * improvements of export feature
4150 * various features and fixes
4151 * Czech language file updates
4154 (http://sf.net/projects/phpmysqlformgen/)
4155 * suggested the patch for multiple table printviews
4158 * built the patch for vertical display of table rows
4159 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
4160 * Improvement of column/db comments
4161 * (MIME)-Transformations for columns
4162 * Use custom alias names for Databases in left frame
4163 * hierarchical/nested table display
4164 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
4165 * new icon sets
4166 * vertical display of column properties page
4167 * some bugfixes, features, support, German language additions
4170 * japanese kanji encoding conversion feature
4173 * the Cookie authentication mode
4176 * table relation-links feature
4179 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4180 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4181 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
4187 * phpMyAdmin logo (until June 2004)
4190 * blowfish library from the Horde project
4193 * mysqli support
4194 * many bugfixes and improvements
4197 * redesign for 2.6.0
4198 * phpMyAdmin sailboat logo (June 2004)
4201 * Representation at conferences
4204 * interface improvements
4205 * various bugfixes
4207 - Ivan A Kirillov
4208 * new relations Designer
4210 - Raj Kissu Rajandran (Google Summer of Code 2008)
4211 * BLOBstreaming support
4213 And also to the following people who have contributed minor changes,
4214 enhancements, bugfixes or support for a new language since version 2.1.0:
4216 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4217 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4218 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4219 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4221 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4222 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4223 Luís V., Martijn W. van der Lee,
4224 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4228 Original Credits of Version 2.1.0
4229 ---------------------------------
4231 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4232 to create a web-based interface to MySQL using PHP3. Although I have not
4233 used any of his source-code, there are some concepts I've borrowed from
4234 him. phpMyAdmin was created because Peter told me he wasn't going to
4235 further develop his (great) tool.
4236 Thanks go to
4238 code for the check when dropping a table or database. He also suggested
4239 that you should be able to specify the primary key on tbl_create.php3. To
4240 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4241 well as a bug-report. Plus many smaller improvements.
4243 were introduced in 1.3.0 (including quite significant ones like the
4244 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4245 bug-fixes and help.
4247 language-independent by outsourcing the strings to a separate file. He
4248 also contributed the French translation.
4250 tbl_select.php3, a feature to display only some fields from a table.
4252 functions in tbl_change.php3. He also added the
4255 servers and is a regular contributor for bug-fixes.
4257 features for 2.0.6.
4258 The following people have contributed minor changes, enhancements, bugfixes
4259 or support for a new language:
4260 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4261 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4262 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4263 G. Wieggers.
4265 And thanks to everyone else who sent me email with suggestions, bug-reports
4266 and or just some feedback.
4267 </pre>
4273 <ul>
4275 - the default name of Apache's directory-level configuration file.</li>
4279 - a software application that enables a user to display and interact with
4280 text, images, and other information typically located on a web page at a
4281 website on the World Wide Web.</li>
4283 - a free software/open source data compression algorithm and program
4284 developed by Julian Seward.</li>
4286 - an important World Wide Web technology that enables a client web browser
4287 to request data from a program executed on the Web server.</li>
4289 - a log or record of changes made to a project.</li>
4291 - a computer system that accesses a (remote) service on another computer
4292 by some kind of network.</li>
4294 - a set of data values of a particular simple type, one for each row of
4295 the table.</li>
4297 - a packet of information sent by a server to a World Wide Web browser
4298 and then sent back by the browser each time it accesses that server.</li>
4300 - Comma-separated values</li>
4303 - an organized collection of data.</li>
4306 - a PHP module that extends PHP with additional functionality.</li>
4308 - a list of commonly asked question and there answers.</li>
4310 - one part of divided data/columns.</li>
4312 - a field or group of fields in a database record that point to a key
4313 field or group of fields forming a key of another database record in some
4314 (usually different) table.</li>
4316 - the free PDF library</li>
4318 GD Graphics Library</a> - a library by Thomas Boutell and others for
4319 dynamically manipulating images.</li>
4322 - gzip is short for GNU zip, a GNU free software file compression
4323 program.</li>
4325 - any machine connected to a computer network, a node that has a hostname.</li>
4327 - the unique name by which a network attached device is known on a network.</li>
4329 (HyperText Transfer Protocol)</a>
4330 - the primary method used to transfer or convey information on the World
4331 Wide Web.</li>
4334 additional security measures.</li>
4335 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4336 - a set of Internet-based services for servers using Microsoft Windows.</li>
4338 - a feature that allows quick access to the rows in a table.</li>
4340 - a data-oriented protocol used by source and destination hosts for
4341 communicating data across a packet-switched internetwork.</li>
4343 - a unique number that devices use in order to identify and communicate
4344 with each other on a network utilizing the Internet Protocol standard.</li>
4346 (Internet Server Application Programming Interface)</a>
4347 - the API of Internet Information Services (IIS).</li>
4349 - a business or organization that offers users access to the Internet and related services.</li>
4351 - a most commonly used standard method of lossy compression for
4352 photographic images.</li>
4358 - line of personal computers is designed, developed, manufactured, and
4359 marketed by Apple Computer.</li>
4360 <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>
4361 - the operating system which is included with all currently shipping Apple
4362 Macintosh computers in the consumer and professional markets.</li>
4364 - a cryptographic library.</li>
4366 - the MCrypt PHP extension.</li>
4367 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4368 - an Internet Standard for the format of e-mail.</li>
4370 - some sort of extension for the Apache Webserver.</li>
4372 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4373 Management System (DBMS).</li>
4375 - the improved MySQL client PHP extension.</li>
4377 - the MySQL client PHP extension.</li>
4379 - open standard for office documents.</li>
4380 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4381 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4383 (Portable Document Format)</a>
4384 - a file format developed by Adobe Systems for representing two
4385 dimensional documents in a device independent and resolution independent
4386 format.</li>
4388 - the PHP Extension and Application Repository.</li>
4390 - the perl-compatible regular expression functions for PHP</li>
4392 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4393 programming language used mainly for developing server-side applications
4394 and dynamic web content, and more recently, a broader range of software
4395 applications.</li>
4397 - a connection through which data is sent and received.</li>
4399 - Request for Comments (RFC) documents are a series of memoranda
4400 encompassing new research, innovations, and methodologies applicable to
4401 Internet technologies.</li>
4405 - represents a single, implicitly structured data item in a table.</li>
4407 - a computer system that provides services to other computing
4408 systems over a network.</li>
4409 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4410 - handlers for different table types</li>
4412 - a form of inter-process communication.</li>
4414 Sockets Layer)</a>
4415 - a cryptographic protocol which provides secure communication on the Internet.</li>
4417 - Structured Query Language</li>
4419 - a set of data elements (cells) that is organized, defined and stored as
4420 horizontal rows and vertical columns where each item can be uniquely
4421 identified by a label or key or by it?s position in relation to other items.</li>
4424 - a type of archive file format: the Tape ARchive format.</li>
4426 - one of the core protocols of the Internet protocol suite.</li>
4430 - a sequence of characters, conforming to a standardized format, that is
4431 used for referring to resources, such as documents and images on the
4432 Internet, by their location.</li>
4434 - A computer (program) that is responsible for accepting HTTP requests
4435 from clients and serving them Web pages.</li>
4437 - a W3C-recommended general-purpose markup language for creating
4438 special-purpose markup languages, capable of describing many different
4439 kinds of data.</li>
4441 - a popular data compression and archival format.</li>
4443 - an open-source, cross-platform data compression library by Jean-loup
4444 Gailly and Mark Adler.</li>
4445 </ul>
4455 </body>
4456 </html>