| blob | 984c53ba087c668acb54fda7896a96e158d87be9 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <head>
14 </head>
18 <h1>
20 4.0.0-dev
21 Documentation
22 </h1>
23 </div>
25 <!-- TOP MENU -->
34 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
39 </ul>
44 phpMyAdmin homepage</a></li>
46 SourceForge phpMyAdmin project page</a></li>
48 Official phpMyAdmin wiki</a></li>
50 Git repositories on Github</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
56 </ul>
58 <!-- REQUIREMENTS -->
65 , the Standard PHP Library (SPL) extension and JSON support.
66 </li>
69 currently the default), you should install the mbstring and ctype
70 extensions.
71 </li>
72 <li>You need GD2 support in PHP to display inline
74 original aspect ratio</li>
80 load pages significantly slower.
81 </li>
84 <li>To support XML and Open Document Spreadsheet importing,
85 you need PHP 5.2.17 or newer and the
87 </ul>
88 </li>
91 </ul>
93 <!-- INTRODUCTION -->
96 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
97 a single database. To accomplish the latter you'll need a properly set up
98 MySQL user who can read/write only the desired database. It's up to you to
99 look up the appropriate part in the MySQL manual.
100 </p>
105 <li>create, copy, drop, rename and alter databases, tables, columns and
106 indexes</li>
107 <li>maintenance server, databases and tables, with proposals on server
108 configuration</li>
109 <li>execute, edit and bookmark any
111 batch-queries</li>
114 </li>
121 OpenDocument Text and Spreadsheet,
124 </li>
125 <li>import data and MySQL structures from OpenDocument spreadsheets, as well as <abbr title="Extensible Markup Language">XML</abbr>, <abbr title="Comma Separated Values">CSV</abbr>, and <abbr title="Server Query Language">SQL</abbr> files</li>
129 <li>using Query-by-example (QBE), create complex queries automatically
130 connecting required tables</li>
132 your Database layout</li>
134 <li>transform stored data into any format using a set of predefined
135 functions, like displaying BLOB-data as image or download-link
136 </li>
144 <li>communicate in <a href="http://www.phpmyadmin.net/home_page/translations.php">62 different languages</a>
145 </li>
146 <li>synchronize two databases residing on the same as well as remote servers
148 </li>
150 </ul>
153 <p> Many people have difficulty
154 understanding the concept of user management with regards to phpMyAdmin. When
155 a user logs in to phpMyAdmin, that username and password are passed directly
156 to MySQL. phpMyAdmin does no account management on its own (other than
157 allowing one to manipulate the MySQL user account information); all users
158 must be valid MySQL users.</p>
167 <!-- INSTALLATION -->
175 </ol>
178 phpMyAdmin does not apply any special security methods to the MySQL database
179 server. It is still the system administrator's job to grant permissions on
181 be used for this.
182 </p>
190 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
191 before uploading them to your server, as PHP seems not to like
196 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
197 Downloads page. Some kits contain only the English messages,
198 others contain all languages in UTF-8 format (this should be fine
199 in most situations), others contain all
200 languages and all character sets. We'll assume you chose a kit whose
202 </li>
203 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
205 document root. If you don't have direct access to your document root,
206 put the files in a directory on your local machine, and, after step 4,
207 transfer the directory on your web server using, for example, ftp.</li>
208 <li>Ensure that all the scripts have the appropriate owner (if PHP is
209 running in safe mode, having some scripts with an owner different
210 from the owner of other scripts will be a
215 <li>Now you must configure your installation. There are two methods that
216 can be used. Traditionally, users have hand-edited a copy of
218 provided for those who prefer a graphical installation. Creating a
219 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
220 <ul><li>To manually create the file, simply use your text editor to
223 file) in the main (top-level) phpMyAdmin directory (the one
227 default value is okay for a particular setting, there is no
229 few directives to get going, a simple configuration may look
230 like this:
231 <pre>
232 <?php
233 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
235 $i=0;
236 $i++;
237 $cfg['Servers'][$i]['auth_type'] = 'cookie';
238 ?>
239 </pre>
240 Or, if you prefer to not be prompted every time you log in:
241 <pre>
242 <?php
244 $i=0;
245 $i++;
246 $cfg['Servers'][$i]['user'] = 'root';
247 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
248 $cfg['Servers'][$i]['auth_type'] = 'config';
249 ?>
250 </pre>
251 For a full explanation of possible configuration values, see the
257 directory. This is a security measure. On a Linux/Unix system you
258 can use the following commands:
259 <pre>
260 cd phpMyAdmin
261 mkdir config # create directory for saving
262 chmod o+rw config # give it world writable permissions
263 </pre>
264 And to edit an existing configuration, copy it over first:
265 <pre>
266 cp config.inc.php config/ # copy current configuration for editing
267 chmod o+w config/config.inc.php # give it world writable permissions
268 </pre>
269 On other platforms, simply create the folder and ensure that your
278 the webserver does not have the proper permissions you may see the
280 config/</tt> directory exists and has the proper permissions -
282 and upload (via FTP or some similar means) to the proper location.<br /><br />
284 Once the file has been saved, it must be moved out of the <tt>
285 config/</tt> directory and the permissions must be reset, again
286 as a security measure:
287 <pre>
288 mv config/config.inc.php . # move file to current directory
289 chmod o-rw config.inc.php # remove world read and write permissions
290 rm -rf config # remove not needed directory
291 </pre>
292 Now the file is ready to be used. You can choose to review or edit
293 the file with your favorite editor, if you prefer to set some
294 advanced options which the setup script does not provide.</li></ul></li>
295 <li>If you are using the
297 protect the phpMyAdmin installation directory because using
298 config does not require a user to
299 enter a password to access the phpMyAdmin installation. Use of an alternate
300 authentication method is recommended, for example with
308 in your browser. phpMyAdmin should now display a welcome screen
309 and your databases, or a login dialog if using
311 authentication mode.</li>
314 Apache you can use supplied <a href="#glossary"><i>.htaccess</i></a> file in that folder, for other
315 webservers, you should configure this yourself. Such configuration
316 prevents from possible path exposure and cross side scripting
317 vulnerabilities that might happen to be found in that code.</li>
318 <li>
319 It is generally good idea to protect public phpMyAdmin installation
320 against access by robots as they usually can not do anything good
322 your webserver or limit access by web server configuration, see
324 </li>
325 </ol>
329 <p> For a whole set of new features (bookmarks, comments,
331 tracking mechanism,
333 transformation, etc.) you need to create a set of special tables. Those
334 tables can be located in your own database, or in a central database for a
335 multi-user installation (this database would then be accessed by the
336 controluser, so no other user should have rights to it).</p>
347 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
348 that you may need special (administrator) privileges to create the database
349 and tables, and that the script may need some tuning, depending on the
350 database name.</p>
355 section</a>. You will also need to have a controluser with the proper rights
362 unpacked one. Configuration files from old versions may
363 require some tweaking as some options have been changed or removed; in
365 so you better remove it from your file and just use the default one.
367 statement that you might find near the end of your configuration file.</p>
371 is version-specific.</p>
374 version 5.x or newer and if you use the phpMyAdmin configuration storage,
382 where you want to give users access to their own database and don't want
383 them to play around with others.<br />
384 Nevertheless be aware that MS Internet Explorer seems to be really buggy
388 that your user/password pair are not in clear in the configuration file.
389 </li>
392 authentication modes are more secure: the MySQL login information does
393 not need to be set in the phpMyAdmin configuration file (except possibly
395 However, keep in mind that the password travels in plain text, unless
396 you are using the HTTPS protocol.<br />
397 In cookie mode, the password is stored, encrypted with the blowfish
398 algorithm, in a temporary cookie.</li>
410 file under the
412 $cfg['Servers'][$i]['controluser']</a></tt> and
417 only an example: use something else in your file!</b> Input these
421 if it's not the same as the MySQL server's one.
423 <pre>
424 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
425 GRANT SELECT (
426 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
427 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
428 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
429 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
430 Execute_priv, Repl_slave_priv, Repl_client_priv
431 ) ON mysql.user TO 'pma'@'localhost';
432 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
433 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
434 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
435 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
437 If you want to use the many new relation and bookmark features:
439 <pre>
441 </pre>
444 configuration storage</a> be set up).
445 <br /></li>
448 on a set of particular databases. Normally you shouldn't give global
449 privileges to an ordinary user, unless you understand the impact of those
450 privileges (for example, you are creating a superuser).<br />
454 <pre>
455 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
456 </pre>
458 What the user may now do is controlled entirely by the MySQL user
459 management system.<br />
461 authentication mode, you don't need to fill the user/password fields
463 array.</li>
464 </ul>
469 method and allows you to log in as any valid MySQL user.</li>
470 <li>Is supported with most PHP configurations. For
483 mode.</li>
484 </ul>
488 <ul><li>You can use this method as a replacement for the
490 (for example, if you're running
492 <li>Obviously, the user must enable cookies in the browser, but this is
493 now a requirement for all authentication modes.</li>
494 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
495 with the same username.</li>
496 <li>If you want to log in to arbitrary server see
501 not required.</li>
502 </ul>
506 <ul><li>This mode is a convenient way of using credentials from another
507 application to authenticate to phpMyAdmin.</li>
508 <li>The other application has to store login information into
509 session data.</li>
511 section.</li>
512 </ul>
515 <ul><li>This mode is the less secure one because it requires you to fill the
517 $cfg['Servers'][$i]['user']</a> and
519 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
520 can read your config.inc.php can discover your username and password).
521 <br />
528 is an entry explaining how to protect your configuration file.</li>
529 <li>For additional security in this mode, you may wish to consider the Host
530 authentication
532 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
534 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
535 directives.</li>
536 <li>Unlike cookie and http, does not require a user to log in when first
537 loading the phpMyAdmin site. This is by design but could allow any
538 user to access your installation. Use of some restriction method is
540 HTTP-AUTH directive or disallowing incoming HTTP requests at
541 one’s router or firewall will suffice (both of which
542 are beyond the scope of this manual but easily searchable with Google).</li>
543 </ul>
545 <p>
546 The Swekey is a low cost authentication USB key that can be used in
547 web applications.<br /><br />
548 When Swekey authentication is activated, phpMyAdmin requires the
549 users's Swekey to be plugged before entering the login page (currently
550 supported for cookie authentication mode only). Swekey Authentication is
551 disabled by default.<br /><br />
553 </p>
554 <pre>
555 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
556 </pre>
557 <p>
559 each user with their Swekey Id. It is important to place this file outside
560 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
562 users' information.<br /><br />
563 If you want to purchase a Swekey please visit
565 since this link provides funding for phpMyAdmin.
566 </p>
567 <!-- CONFIGURATION -->
571 users:</span> PHP does not seem to like
575 before saving a script you have modified.</p>
580 section to create one. This file only needs to contain the parameters you want to
581 change from their corresponding default value in
584 <p> The parameters which relate to design (like colors) are placed in
587 your site specific code to be included on start and end of each page.</p>
591 (with full path) to your phpMyAdmin installation's directory.
594 some web servers are case–sensitive.
597 Starting with version 2.3.0, it is advisable to try leaving this
598 blank. In most cases phpMyAdmin automatically detects the proper
599 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
600 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
601 A good test is to browse a table, edit a row and save it. There should
602 be an error message if phpMyAdmin is having trouble auto–detecting
603 the correct value. If you get an error that this must be set or if
604 the autodetect code fails to detect your path, please post a bug
605 report on our bug tracker so we can improve the code.</dd>
609 with master / foreign – tables (see
611 <br />
612 If you tried to set this up and it does not work for you, have a look on
614 use it. You will find a link that will analyze why those features have
615 been disabled.<br />
616 If you do not want to use those features set this variable to
620 <dd>A warning is displayed on the main page if Suhosin is detected.
622 from appearing.</dd>
625 <dd>Disable the default warning that is displayed if mcrypt is missing for
626 cookie authentication.
628 from appearing.</dd>
635 domain to call phpMyAdmin inside a frame, and is a potential security
636 hole allowing cross-frame scripting attacks.</dd>
640 algorithm to encrypt the password.<br />
642 passphrase of your choice. It will be used internally by the blowfish
643 algorithm: you won’t be prompted for this passphrase. There is
644 no maximum length for this secret.<br /><br />
646 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
647 makes a bit weaker security as this generated secret is stored in
648 session and furthermore it makes impossible to recall user name from
649 cookie.</dd>
653 MySQL servers. Therefore, a
655 been added which contains the login information for the different servers.
656 The first
658 contains the hostname of the first server, the second
660 the hostname of the second server, etc. In
662 server definition, however you can put as many as you need in
664 have to define all settings, just those you need to change).</dd>
668 $i-th MySQL-server. E.g. localhost.</dd>
673 ignores this port number and connects with the socket, so if you want
674 to connect to a port different from the default port, use
677 </dd>
681 To determine the correct socket, check your MySQL configuration or, using the
683 Among the resulting information displayed will be the socket used.</dd>
686 <dd>Whether to enable SSL for connection to MySQL server.
687 </dd>
690 <dd>What type connection to use with the MySQL server. Your options are
692 is nearly guaranteed to be available on all MySQL servers, while
693 sockets are not supported on some platforms.<br /><br />
695 To use the socket mode, your MySQL server must be on the same machine
696 as the Web server.</dd>
699 <dd>What php MySQL extension to use for the connection. Valid options are:
700 <br /><br />
703 The classic MySQL extension.<br /><br />
706 The improved MySQL extension. This extension became available
707 with PHP 5.0.0 and is the recommended way to connect to a server
711 <dd>Whether to use a compressed protocol for the MySQL server connection
712 or not (experimental).</dd>
716 </dt>
717 <dd>Permits to use an alternate host to hold the configuration storage
718 data.</dd>
723 </dt>
725 all relational features (see
727 and, for a MySQL server running with
730 authentication mode).<br /><br />
733 cookie authentication modes (or 'config'
734 authentication mode since phpMyAdmin 2.2.1), you need to supply the
739 This account is used to check what databases the user will see at
740 login.<br />
744 In phpMyAdmin versions before 2.2.5, those were called
748 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
749 <dd>Whether config or cookie or
751 should be used for this server.
753 is the plain old way: username and password are stored in
755 <li>'cookie' authentication mode
757 2.2.3 allows you to log in as any valid MySQL user with the
758 help of cookies. Username and password are stored in
759 cookies during the session and password is deleted when it
760 ends. This can also allow you to log in in arbitrary server if
761 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
762 </li>
763 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
764 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
765 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
766 <li>'signon' authentication mode
768 as introduced in 2.10.0 allows you to log in from prepared PHP
769 session data or using supplied PHP script. This is useful for implementing single signon
770 from another application.
776 You need to
782 this authentication method.</li>
783 </ul>
786 for more information.
787 </dd>
789 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
790 </dt>
791 <dd>
792 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
793 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
794 specified in your configuration, a string combined of "phpMyAdmin " and either
797 </dd>
799 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
800 </dt>
801 <dd>
803 names for hardware authentication. Leave empty to deactivate this feature.
804 </dd>
808 </dt>
809 <dd>
810 When using auth_type = 'config', this is the user/password-pair
811 which phpMyAdmin will use to connect to the
812 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
813 cookie authentication is used and should be empty.</dd>
815 <span
817 </dt>
818 <dd>
819 Allow attempt to log in without password when a login with password
820 fails. This can be used together with http authentication, when
821 authentication is done some other way and phpMyAdmin gets user name
822 from auth and uses empty password for connecting to MySQL. Password
823 login is still tried first, but as fallback, no password method is
824 tried.</dd>
827 </dt>
828 <dd>
829 If set to a (an array of) database name(s), only this (these) database(s)
830 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
831 database(s) name(s) may contain MySQL wildcards characters
835 This setting is an efficient way to lower the server load since the
836 latter does not need to send MySQL requests to build the available
838 privileges rules of the MySQL database server</span>. If set, it just
839 means only these databases will be displayed but
841 <br /><br />
843 An example of using more that one database:
845 <br /><br />
847 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
848 databases in the left frame, so that you can individually arrange your databases.<br />
849 If you want to have certain databases at the top, but don't care about the others, you do not
850 need to specify all other databases. Use:
852 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
853 order.</dd>
856 </dt>
857 <dd>Regular expression for hiding some databases from unprivileged users.
858 This only hides them
859 from listing, but a user is still able to access them (using, for example,
860 the SQL query area). To limit access, use the MySQL privilege system.
861 <br /><br />
866 More information on regular expressions can be found in the
868 PCRE pattern syntax</a> portion of the PHP reference manual.
869 </dd>
872 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
873 this string will be displayed instead of the hostname in the pull-down
874 menu on the main page. This can be useful if you want to show only
875 certain databases on your system, for example. For HTTP auth, all
876 non-US-ASCII characters will be stripped.</dd>
880 </dt>
881 <dd>The name of the database containing the phpMyAdmin configuration storage.
882 <br /><br />
885 section in this document to see the benefits of this feature,
886 and for a quick way of creating this database and the needed tables.
887 <br /><br />
889 If you are the only user of this phpMyAdmin installation, you can
890 use your current database to store those special tables; in this
891 case, just put your current database name in
893 set this parameter to the name of your central database containing
894 the phpMyAdmin configuration storage.</dd>
898 </dt>
900 useful for queries you often run.<br /><br />
902 To allow the usage of this functionality:
904 <li>enter the table name in
906 </ul>
907 </dd>
911 </dt>
913 which column is a key in another table (a foreign key). phpMyAdmin
914 currently uses this to
915 <ul><li>make clickable, when you browse the master table, the data values
916 that point to the foreign table;</li>
918 when browsing the master table, if you move the mouse to a column
919 containing a foreign key (use also the 'table_info' table);<br />
922 <li>in edit/insert mode, display a drop-down list of possible foreign
926 <li>display links on the table properties page, to check referential
927 integrity (display missing foreign keys) for each described key;
928 </li>
932 schema of your database (also uses the table_coords table).</li>
933 </ul>
935 The keys can be numeric or character.<br /><br />
937 To allow the usage of this functionality:
940 configuration storage</li>
941 <li>put the relation table name in
943 <li>now as normal user open phpMyAdmin and for each one of your
944 tables where you want to use this feature, click
946 columns.
947 </li>
948 </ul>
952 future development of the cross-db relations.
953 </dd>
957 </dt>
958 <dd>
959 Since release 2.3.0 you can describe, in a special 'table_info'
960 table, which column is to be displayed as a tool-tip when moving the
961 cursor over the corresponding key.<br />
962 This configuration variable will hold the name of this special
963 table. To allow the usage of this functionality:
965 <li>put the table name in
967 'pma_table_info')</li>
968 <li>then for each table where you want to use this feature,
970 to choose the column.</li>
971 </ul>
973 </dd>
977 </dt>
980 the relations between your tables. To do this it needs two tables
985 schema output).<br /><br />
989 To allow the usage of this functionality:
992 <li>put the correct table names in
995 </ul>
998 </dd>
1002 </dt>
1004 Since release 2.3.0 you can store comments to describe each column for
1006 <br /><br />
1008 Starting with release 2.5.0, comments are consequently used on the table
1009 property pages and table browse view, showing up as tool-tips above the
1010 column name (properties page) or embedded within the header of table in
1011 browse view. They can also be shown in a table dump. Please see the
1012 relevant configuration directives later on.<br /><br />
1014 Also new in release 2.5.0 is a MIME-transformation system which is also
1016 Transformations</a> for further information. To use the
1017 MIME-transformation system, your column_info table has to have the three
1018 new columns 'mimetype', 'transformation', 'transformation_options'.
1019 <br /><br />
1021 To allow the usage of this functionality:
1023 <li>put the table name in
1025 'pma_column_info')</li>
1028 <pre>
1029 ALTER TABLE `pma_column_comments`
1030 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1031 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1032 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1033 </pre>
1036 renamed from<br />
1039 </ul>
1040 </dd>
1044 </dt>
1047 all queries you entered manually into the phpMyAdmin interface. If you
1048 don't want to use a table-based history, you can use the JavaScript-based
1049 history. Using that, all your history items are deleted when closing the
1050 window.<br /><br />
1052 Using
1054 you can specify an amount of history items you want to have on hold. On
1055 every login, this list gets cut to the maximum amount.<br /><br />
1057 The query history is only available if JavaScript is enabled in your
1058 browser.<br /><br />
1060 To allow the usage of this functionality:
1064 (e.g. 'pma_history')
1065 </li>
1066 </ul>
1067 </dd>
1071 </dt>
1072 <dd>
1073 Since release 3.5.0 you can show recently used tables in the left navigation frame.
1074 It helps you to jump across table directly, without the need to select the database,
1075 and then select the table. Using
1077 you can configure the maximum number of recent tables shown. When you select a table
1078 from the list, it will jump to the page specified in
1079 <a href="#cfg_LeftDefaultTabTable" class="configrule">$cfg['LeftDefaultTabTable']</a>.<br/><br/>
1081 Without configuring the storage, you can still access the recently used tables,
1082 but it will disappear after you logout.<br/><br/>
1084 To allow the usage of this functionality persistently:
1086 <ul>
1089 </ul>
1090 </dd>
1094 </dt>
1095 <dd>
1096 Since release 3.5.0 phpMyAdmin can be configured to remember several things
1097 (sorted column
1099 , column order, and column visibility from a database table) for browsing tables.
1100 Without configuring the storage, these features still can be used,
1101 but the values will disappear after you logout.<br/><br/>
1103 To allow the usage of these functionality persistently:
1105 <ul>
1107 <li>put the table name in <tt>$cfg['Servers'][$i]['table_uiprefs']</tt> (e.g. 'pma_table_uiprefs')</li>
1108 </ul>
1109 </dd>
1113 </dt>
1114 <dd>
1115 Since release 3.3.x a tracking mechanism is available.
1117 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1118 and data definition statements. After enabling it you can create versions of tables.
1119 <br/><br/>
1120 The creation of a version has two effects:
1122 <ul>
1124 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1125 </ul>
1127 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1128 For the report you can use filters, for example you can get a list of statements within a date range.
1129 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1130 In addition you can export the (filtered) report to a file or to a temporary database.
1131 <br/><br/>
1133 To allow the usage of this functionality:
1135 <ul>
1138 </ul>
1139 </dd>
1142 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1143 </dt>
1144 <dd>
1145 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1146 <br/><br/>
1147 If this is set to true and you create a table or view with
1149 <ul>
1152 </ul>
1154 and no version exists for it, the mechanism will
1155 create a version for you automatically.
1156 </dd>
1159 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1160 </dt>
1161 <dd>
1162 Defines the list of statements the auto-creation uses for new versions. Default value is
1163 <br/>
1165 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1166 CREATE INDEX,DROP INDEX,
1167 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1168 CREATE VIEW,ALTER VIEW,DROP VIEW,
1169 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1170 </dd>
1173 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1174 </dt>
1175 <dd>
1176 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1177 <br/><br/>
1178 </dd>
1182 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1183 </dt>
1184 <dd>
1185 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1186 <br/><br/>
1187 </dd>
1190 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1191 </dt>
1192 <dd>
1193 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1194 <br/><br/>
1195 </dd>
1199 </dt>
1200 <dd>
1201 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1202 and store them in the database.
1203 <br /><br />
1206 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1207 or, it is is unavailable, until the end of session.
1208 <br /><br />
1210 To allow the usage of this functionality:
1212 <ul>
1214 configuration storage</li>
1216 </ul>
1217 </dd>
1221 </dt>
1223 to visually manage the relations.
1224 <br /><br />
1226 To allow the usage of this functionality:
1229 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1230 </li>
1231 </ul>
1232 </dd>
1234 <dt><span id="cfg_Servers_MaxTableUiprefs">$cfg['Servers'][$i]['MaxTableUiprefs']</span> integer
1235 </dt>
1239 When tables are dropped or renamed, table_uiprefs may contain invalid
1240 data (referring to tables which no longer exist).<br />
1241 We only keep this number of newest rows in table_uiprefs and automatically delete older rows.</dd>
1244 </dt>
1246 column_info table got enhanced with three new columns. If the above variable
1248 latest table structure available. If not, it will emit a warning to the
1249 superuser.<br /><br />
1251 You can disable this checking behavior by setting the variable to false,
1252 which should offer a performance increase.<br /><br />
1254 Recommended to set to FALSE, when you are sure, your table structure is
1255 up to date.</dd>
1257 boolean</dt>
1258 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1259 </dd>
1261 boolean</dt>
1262 <dd>Whether to allow logins without a password. The default
1264 to a MySQL server with was left with an empty password for root or
1265 on which an anonymous (blank) user is defined.
1266 </dd>
1269 </dt>
1271 authorization is disabled.<br /><br />
1274 all deny rules followed by allow rules. Access is allowed by default. Any
1275 client which does not match a Deny command or does match an Allow command
1276 will be allowed access to the server. <br /><br />
1279 applies all allow rules followed by deny rules. Access is denied by
1280 default. Any client which does not match an Allow directive or does
1281 match a Deny directive will be denied access to the server.<br /><br />
1283 If your rule order is set to 'explicit', authorization is
1284 performed in a similar fashion to rule order 'deny,allow', with the
1288 and was available in Apache by specifying allow and deny rules without
1289 setting any order.<br /><br />
1291 Please also see <a
1293 address behind proxies.
1294 </dd>
1296 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1297 </dt>
1298 <dd>The general format for the rules is as such:
1300 <pre>
1302 </pre>
1307 well (please note that those containing SERVER_ADDRESS might not be
1308 available on all webservers):
1309 <pre>
1315 </pre>
1317 Having an empty rule list is equivalent to either using
1323 following work:<br />
1325 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1326 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1327 But the following does not work:<br />
1330 Also IPv6 addresses are not supported.
1331 </dd>
1333 <dd>Disable using <tt>INFORMATION_SCHEMA</tt> to retrieve information (use <tt>SHOW</tt> commands instead), because of speed issues when many databases are present. Currently used in some parts of the code, more to come.
1334 </dd>
1335 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1337 DATABASES</tt> command used to fetch the name of available databases will
1338 probably be too slow, so it can be replaced by faster commands (see
1340 </dd>
1342 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1343 </dd>
1345 <dd>Name of PHP script to be sourced and executed to obtain
1346 login credentials. This is alternative approach to session based single
1347 signon. The script needs to provide function
1349 password, accepting single parameter of existing username (can be empty).
1351 </dd>
1352 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1353 <dd>Name of session which will be used for signon authentication method.
1355 this is session which phpMyAdmin uses internally. Takes effect only if
1357 is not configured.
1358 </dd>
1361 redirected to log in for signon authentication method. Should be absolute
1362 including protocol.
1363 </dd>
1366 redirected after logout (doesn't affect config authentication method).
1367 Should be absolute including protocol.
1368 </dd>
1371 <dd>If you have more than one server configured, you can set
1373 that server when phpMyAdmin is started, or set it to 0 to be given a
1374 list of servers without logging in.<br />
1376 MUST be set to that server.</dd>
1379 <dd>Defines whether to refresh only parts of certain pages using Ajax
1380 techniques. Applies only where a non-Ajax behavior is possible;
1381 for example, the Designer feature is Ajax-only so this directive
1382 does not apply to it.</dd>
1385 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1386 page.</dd>
1389 <dd>The maximum number of database names to be displayed in the
1390 navigation frame and the database list.</dd>
1393 <dd>The maximum number of table names to be displayed in the
1394 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1395 when in Light mode.</dd>
1403 to avoid the display of tons of hexadecimal codes that represent BLOBs, but
1405 queries that are longer than 1000 characters. Also, if a query's length
1406 exceeds this limit, this query is not saved in the history.</dd>
1409 <dd>Defines whether to use GZip output buffering for increased
1411 Set to true/false for enabling/disabling. When set to 'auto' (string),
1412 phpMyAdmin tries to enable output buffering and will automatically disable
1413 it if your browser has some problems with buffering. IE6 with a certain patch
1414 is known to cause data corruption when having enabled buffering.</dd>
1417 <dd>Whether <a href="http://php.net/manual/en/features.persistent-connections.php">persistent connections</a>
1418 should be used or not. Works with following extensions:
1419 <ul>
1420 <li>mysql (<a href="http://php.net/manual/en/function.mysql-pconnect.php">mysql_pconnect</a>),</li>
1421 <li>mysqli (requires PHP 5.3.0 or newer, <a href="http://php.net/manual/en/mysqli.persistconns.php">more information</a>).</li>
1422 </ul></dd>
1428 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1429 to zero, no time limit is imposed.<br />
1430 This setting is used while importing/exporting dump files and in the
1431 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1438 <dd>Set the number of bytes a script is allowed to allocate. If set
1439 to zero, no limit is imposed.<br />
1440 This setting is used while importing/exporting dump files and at some
1441 other places in phpMyAdmin so you definitely don't want to put here
1442 a too low value. It has no effect when PHP is running in safe mode.<br />
1443 You can also use any string as in php.ini, eg. '16M'. Ensure
1447 <dd>Mark used tables and make it possible to show databases with locked
1452 generated by phpMyAdmin should be displayed or not.</dd>
1456 query box should be kept displayed after its submission.</dd>
1459 <dd>Defines whether normal users (non-administrator) are allowed to
1460 delete their own database or not. If set as FALSE, the link "Drop
1462 mydatabase" will be rejected. Quite practical for
1464 customers.<br />
1466 SQL</abbr> queries is not as strict as when using MySQL privileges. This
1468 which might be quite complicated. So this choice should be viewed as
1469 help to avoid accidental dropping rather than strict privilege
1470 limitation.</dd>
1474 displayed when you're about to lose data.</dd>
1477 <dd>Define whether the previous login should be recalled or not in cookie
1478 authentication mode.<br /><br />
1480 This is automatically disabled if you do not have configured
1482 </dd>
1485 <dd>Define how long is login cookie valid. Please note that php
1486 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1487 might limit session validity and if session is lost, login cookie is
1489 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1493 means that it will be kept for existing session. This is recommended
1494 for not trusted environments.</dd>
1497 <dd>If enabled (default), logout deletes cookies for all servers,
1498 otherwise only for current one. Setting this to false makes it easy to
1499 forget to log out from other server, when you are using more of
1500 them.</dd>
1506 <dd>Define whether phpMyAdmin will continue executing a multi-query
1507 statement if one of the queries fails. Default is to abort execution.</dd>
1510 <dd>Define whether phpMyAdmin will output the results of each query of a
1511 multi-query statement embedded into the
1516 <dd>If enabled, allows you to log in to arbitrary servers using cookie auth and permits to specify servers of your choice in the Synchronize dialog.
1517 <br /><br />
1520 MySQL servers behind the firewall where your
1522 </dd>
1531 <dd>Defines whether to use a select-based menu and display only the current
1532 tables in the left frame (smaller page). Only in Non-Lightmode you can
1533 use the feature to display nested folders using
1535 </dd>
1538 <dd>Defines whether to display the names of databases (in the
1539 selector) using a tree, see also
1541 </dd>
1544 string or array</dt>
1545 <dd>The string used to separate the parts of the database name when showing
1546 them in a tree. Alternatively you can specify more strings in an array
1547 and all of them will be used as a separator.</dd>
1550 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1551 This means if you have tables like 'first__second__third' this will be
1553 If set to FALSE or empty, the feature is disabled. NOTE: You should
1554 not use this separator at the beginning or end of a
1555 table name or multiple times after another without any other
1556 characters in between.</dd>
1559 <dd>Defines how many sublevels should be displayed when splitting
1560 up tables by the above separator.</dd>
1563 <dd>The maximum number of recently used tables shown in the left navigation
1567 <dd>Defines whether to display table comment as tool-tip in left frame or
1568 not.</dd>
1571 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1572 comment and the real name. That means that if you have a table called
1573 'user0001' and add the comment 'MyName' on it, you will see the name
1574 'MyName' used consequently in the left frame and the tool-tip shows
1575 the real name of the DB.</dd>
1578 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1580 When setting this to 'nested', the Alias of the Tablename is only used
1581 to split/nest the tables according to the
1583 directive. So only the folder is called like the Alias, the tablename itself
1584 stays the real tablename.</dd>
1587 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1590 <dd>Enter <abbr title="Uniform Resource Locator">URL</abbr> where logo in the navigation frame will point to.
1591 For use especially with self made theme which changes this.
1600 integer</dt>
1601 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1602 list of tables in the left frame.
1607 <dd>Defines whether or not to display a server choice at the top of the left frame.
1608 Defaults to FALSE.</dd>
1610 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1611 Defaults to FALSE (drop-down).</dd>
1613 <dd>Defines whether to display database choice in light navigation frame as links
1614 instead of in a drop-down. Defaults to 'auto' - on main page list is
1615 shown, when database is selected, only drop down is displayed.</dd>
1618 <dd>Defines the tab displayed by default when clicking the small
1619 icon next to each table name in the navigation panel. Possible
1625 <dd>Defines whether or not to display space usage and statistics about databases
1626 and tables.<br />
1627 Note that statistics requires at least MySQL 3.23.3 and that, at this
1628 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1631 <dd>Defines whether to display detailed server information on main page.
1632 You can additionally hide more information by using
1634 </dd>
1639 </dt>
1642 not at the starting main (right) frame. This setting
1643 does not check MySQL commands entered directly.<br /><br />
1645 Please note that to block the usage of phpinfo() in scripts, you
1652 hard coded password value in the configuration file, end users can't
1653 be allowed to change their passwords.</dd>
1656 <dd>Defines whether to suggest a database name on the
1660 <dd>Defines whether navigation bar buttons and the right panel top menu
1661 contain text or symbols only. A value of TRUE displays icons, FALSE
1662 displays text and 'both' displays both icons and text.</dd>
1665 <dd>Defines whether a user should be displayed a
1669 issues while getting too many rows.</dd>
1672 <dd>Number of rows displayed when browsing a result set and no LIMIT
1673 clause is used. If the result set contains more rows, "Previous" and "Next" links will be shown.</dd>
1679 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1683 option is ticked by default.</dd>
1687 from editing when browsing a table's content. Valid values are:
1692 </ul>
1693 </dd>
1696 <dd>Defines whether or not MySQL functions fields should be initially
1697 displayed in edit/insert mode. Since version 2.10, the user can
1698 toggle this setting from the interface.
1699 </dd>
1702 <dd>Defines whether or not type fields should be initially
1703 displayed in edit/insert mode. The user can
1704 toggle this setting from the interface.
1705 </dd>
1708 <dd>Defines which type of editing controls should be used for CHAR and
1709 VARCHAR columns. Possible values are:
1710 <ul><li>input - this allows to limit size of text to size of columns in
1711 MySQL, but has problems with newlines in columns</li>
1712 <li>textarea - no problems with newlines in columns, but also no
1713 length limitations</li>
1714 </ul>
1715 Default is old behavior so input.</dd>
1718 <dd>Defines the minimum size for input fields generated for CHAR and
1719 VARCHAR columns.</dd>
1722 <dd>Defines the maximum size for input fields generated for CHAR and
1723 VARCHAR columns.</dd>
1729 <dd>If there are fewer items than this in the set of foreign keys, then a
1730 drop-down box of foreign keys is presented, in the style described by the
1732 setting.</dd>
1735 <dd>For the foreign key drop-down fields, there are several methods of
1736 display, offering both the key and value data. The contents of the
1737 array should be one or both of the following strings:
1743 </dt>
1744 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1745 creating a dump file</dd>
1748 </dt>
1749 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1750 compressed exports. This doesn't affect smaller dumps and allows users to
1751 create larger dumps that won't otherwise fit in memory due to php
1752 memory limit. Produced files contain more GZip/BZip2 headers, but all
1753 normal programs handle this correctly.</dd>
1757 mainframe.</dd>
1761 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1766 <dd>How many columns will be utilized to display the tables on the
1767 database property view? Default is 1 column. When setting this to a
1768 value larger than 1, the type of the database will be omitted for more
1769 display space.</dd>
1773 <dd>Defines the tab displayed by default on server view. Possible
1780 <dd>Defines the tab displayed by default on database view. Possible
1785 <dd>Defines the tab displayed by default on table view. Possible
1792 points to the MySQL documentation (type depends
1793 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1794 generated.<br />
1796 for more information about MySQL manuals and their types.</dd>
1799 <dd>Type of MySQL documentation:
1805 </ul>
1806 </dd>
1809 <dd>Defines the default language to use, if not browser-defined or
1810 user-defined.<br />
1811 The corresponding language file needs to be in
1813 </dd>
1816 <dd>Defines the default connection collation to use, if not
1817 user-defined.<br />
1819 documentation</a> for list of possible values. This setting is ignored when
1820 connected to Drizzle server.</dd>
1824 The corresponding language file needs to be in
1826 </dd>
1829 <dd>Limit list of available languages to those matching the given regular
1830 expression. For example if you want only Czech and English, you should
1834 <dd>You can select here which functions will be used for character set
1835 conversion. Possible values are:
1836 <ul><li>auto - automatically use available one (first is tested
1837 iconv, then recode)</li>
1841 </ul>
1842 Default is auto.</dd>
1843 <dd>
1844 Enabled charset conversion activates a pull-down menu
1845 in the Export and Import pages, to choose the character set when
1846 exporting a file. The default value in this menu comes from
1848 </dd>
1851 <dd>Specify some parameters for iconv used in charset conversion. See
1854 used, so that invalid characters will be transliterated.</dd>
1857 <dd>Available character sets for MySQL conversion. You can add your own (any of
1858 supported by recode/iconv) or remove these which you don't use.
1859 Character sets will be shown in same order as here listed, so if you
1860 frequently use some of these move them to the top.</dd>
1865 default empty, you need to fill in some trusted proxy servers if you
1866 want to use rules for IP addresses behind proxy.<br /><br />
1868 The following example specifies that phpMyAdmin should trust a
1870 <pre>
1871 $cfg['TrustedProxies'] =
1873 </pre>
1874 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1875 client's IP address as usual.
1876 </dd>
1880 MIME transformations.<br />
1881 Possible values are:
1885 </ul>
1886 Default is auto.
1887 </dd>
1890 <dd>
1891 We normally check the permissions on the configuration file to ensure
1892 it's not world writable. However, phpMyAdmin could be installed on
1893 a NTFS filesystem mounted on a non-Windows server, in which case the
1894 permissions seems wrong but in fact cannot be detected. In this case
1896 </dd>
1899 <dd>
1901 When length would be above this limit, it is replaced by form with button.
1905 </dd>
1907 <dt
1909 <dd>
1910 In the database Structure page, it's possible to mark some tables then
1911 choose an operation like optimizing for many tables. This can slow down
1914 </dd>
1918 </dd>
1920 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1922 </dt>
1923 <dd>The background styles used for both the frames.
1926 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1928 <dd>The style used for the pointer in the navi frame.
1937 </dd>
1941 <dd>The style used for table headers. See
1946 </dd>
1950 </dd>
1952 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1954 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1956 </dt>
1958 The former feature highlights the row over which your mouse is passing
1959 and the latter lets you visually mark/unmark rows by clicking on
1960 them. Highlighting / marking a column is done by hovering over /
1961 clicking the column's header (outside of the text).<br />
1966 <dd>You put here a valid CSS font family value, for example
1971 <dd>You put here a valid CSS font family value, for example
1985 </dt>
1987 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1989 The Char* values are used for CHAR and VARCHAR editing (if configured
1993 </dt>
1997 </dt>
1998 <dd>Defines if the whole textarea of the query box will be selected on
1999 click.</dd>
2002 <dd>Maximum number of characters shown in any non-numeric field on browse view.
2003 Can be turned off by a toggle button on the browse page.</dd>
2006 </dt>
2007 <dd>Defines the place where table row links (Edit, Copy,
2008 Delete) would be put when tables contents are displayed (you may
2009 have them displayed at the left side, right side, both sides or nowhere).
2015 Define which one is displayed by default. The first mode displays each
2016 row on a horizontal line, the second rotates the headers by 90
2017 degrees, so you can use descriptive headers even though columns only
2018 contain small values and still print them out. The vertical mode sorts
2019 each row on a vertical lineup.
2020 </dd>
2026 <dd>
2027 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
2028 'css' the rotation of the header for horizontalflipped is done via
2029 CSS. The CSS transformation currently works only in Internet
2030 Explorer.If set to 'fake' PHP does the transformation for you, but of
2031 course this does not look as good as CSS. The 'auto' option enables
2032 CSS transformation when browser supports it and use PHP based one
2033 otherwise.
2034 </dd>
2038 </dt>
2040 display of column comments in Browse or Property display. In browse
2041 mode, the comments are shown inside the header. In property mode,
2042 comments are displayed using a CSS-formatted dashed-line below the
2043 name of the column. The comment is shown as a tool-tip for that column.
2044 </dd>
2056 <dd>Whether to display a link to validate a query in any SQL Query box.
2063 <dd>
2064 The name of the directory where
2066 uploaded by other means than phpMyAdmin (for example, ftp). Those files
2067 are available under a drop-down box when you click the database or
2068 table name, then the Import tab.
2069 <br /><br />
2071 If you want different directory for each user, %u will be replaced
2072 with username.<br /><br />
2076 compressed formats is enabled).<br /><br />
2078 This feature is useful when your file is too big to be uploaded via
2080 uploads are disabled in PHP.<br /><br />
2082 Please note that if PHP is running in safe mode, this directory must
2083 be owned by the same user as the owner of the phpMyAdmin scripts.
2084 <br /><br />
2088 alternatives.
2089 </dd>
2092 <dd>
2093 The name of the directory where dumps can be saved.<br /><br />
2095 If you want different directory for each user, %u will be replaced
2096 with username.<br /><br />
2098 Please note that the directory must exist and has to be writable for
2099 the user running webserver.<br /><br />
2101 Please note that if PHP is running in safe mode, this directory must
2102 be owned by the same user as the owner of the phpMyAdmin scripts.
2103 </dd>
2106 <dd>
2107 The name of the directory where temporary files can be stored.
2108 <br /><br />
2110 This is needed for importing ESRI Shapefiles, see
2115 <br /><br />
2117 If the directory where phpMyAdmin is installed is subject to an
2119 temporary directory in some directory accessible by the web
2120 server. However for security reasons, this directory should be outside
2121 the tree published by webserver. If you cannot avoid having this
2122 directory published by webserver, place at least an empty
2124 possible.
2125 <br /><br />
2127 This directory should have as strict permissions as possible as the only
2128 user required to access this directory is the one who runs the
2129 webserver. If you have root privileges, simply make this user owner of
2130 this directory and make it accessible only by it:
2131 <br /><br />
2133 <pre>
2134 chown www-data:www-data tmp
2135 chmod 700 tmp
2136 </pre>
2138 If you cannot change owner of the directory, you can achieve a similar
2141 <pre>
2142 chmod 700 tmp
2143 setfacl -m "g:www-data:rwx" tmp
2144 setfacl -d -m "g:www-data:rwx" tmp
2145 </pre>
2147 If neither of above works for you, you can still make the directory
2149 system reading and writing data in this directory.
2150 </dd>
2153 <dd>
2154 In this array are defined default parameters for export, names of
2155 items are similar to texts seen on export page, so you can easily
2156 identify what they mean.
2157 </dd>
2160 <dd>
2161 Defines how the export form is displayed when it loads. Valid values are:
2162 <ul>
2165 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2166 </ul>
2167 </dd>
2170 <dd>
2171 In this array are defined default parameters for import, names of
2172 items are similar to texts seen on import page, so you can easily
2173 identify what they mean.
2174 </dd>
2177 <dd>
2178 Defines whether or not to save all edited cells at once in browse-mode.
2179 </dd>
2182 <dd>
2183 Defines whether or not type display direction option is shown
2184 when browsing a table.
2185 </dd>
2188 <dd>
2189 Repeat the headers every X cells, or 0 to deactivate.
2190 </dd>
2198 </dt>
2199 <dd>
2200 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2201 or icon is always displayed on the left panel. If JavaScript is enabled in
2202 your browser, a click on this opens a distinct query window, which is
2203 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2204 changes to display a query box.<br /><br />
2206 The size of this query window can be customized with
2208 - both integers for the size in pixels. Note that normally, those
2210 theme you are using.<br /><br />
2214 opens the query window and puts the current query
2215 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2216 query in the right panel's query box.
2217 <br /><br />
2218 The usage of the JavaScript query window is recommended if you have a
2219 JavaScript enabled browser. Basic functions are used to exchange quite
2220 a few variables, so most 4th generation browsers should be capable to
2221 use that feature. It currently is only tested with Internet Explorer 6
2222 and Mozilla 1.x.
2223 <br /><br />
2225 to a table, which has to be created by you (see <a
2227 all your queries will be appended to the form, but only as long as
2228 your window is opened they remain saved.
2229 <br /><br />
2230 When using the JavaScript based query window, it will always get
2231 updated when you click on a new table/db to browse and will focus if
2232 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2233 the query window by checking the box "Do not overwrite this query from
2234 outside the window" below the query textarea. Then you can browse
2235 tables/databases in the background without losing the contents of the
2236 textarea, so this is especially useful when composing a query with
2237 tables you first have to look in. The checkbox will get automatically
2238 checked whenever you change the contents of the textarea. Please
2239 uncheck the button whenever you definitely want the query window to
2240 get updated even though you have made alterations.
2241 <br /><br />
2244 <br /><br />
2245 The query window also has a custom tabbed look to group the features.
2247 default tab to be used when opening the query window. It can be set to
2248 either 'sql', 'files', 'history' or 'full'.</dd>
2254 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2256 If the approximate row count as returned by
2259 count will be used.
2260 </dd>
2262 <dd>For VIEWs, since obtaining the exact count could have an
2263 impact on performance, this value is the maximum to be displayed, using
2265 any row counting.
2266 </dd>
2269 <dd>Sorts database and table names according to natural order (for example,
2270 t1, t2, t10). Currently implemented in the left panel (Light mode)
2271 and in Database view, for the table list.</dd>
2280 that users can't set through user preferences. For possible values, refer
2284 <dd>Activates in the user preferences a tab containing options for
2285 developers of phpMyAdmin.</dd>
2291 <dd>Allows you to specify window's title bar. You can use
2293 </dd>
2303 </dd>
2306 <dd>If theme manager is active, use this as the path of the subdirectory
2307 containing all the themes.</dd>
2321 </dt>
2322 <dd>Default queries that will be displayed in query boxes when user didn't
2323 specify any. You can use standard
2325 </dd>
2328 <dd>
2329 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
2330 default we use HTML to format the query, but you can disable this by
2332 </dd>
2335 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2336 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2337 query inside a bracket is indented. By changing
2340 specifies the units of the indent amount that you specified. This is
2341 used via stylesheets.</dd>
2344 <dd>This array is used to define the colours for each type of element of
2345 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2347 If you specify an empty string for the color of a class, it is ignored
2348 in creating the stylesheet.
2349 You should not alter the class names, only the colour strings.<br />
2370 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2374 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2375 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2376 </ul>
2377 </dd>
2381 <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,
2382 as originally published on
2384 <br />
2385 For help in setting up your system to use the service, see the
2387 </dd>
2391 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2392 and any password, so we use those by default. Instead, if
2393 you have an account with them, you can put your login details
2394 here, and it will be used in place of the anonymous login.</dd>
2395 </dl>
2396 </dd>
2399 <dd><b>DEVELOPERS ONLY!</b></dd>
2402 <dd><b>DEVELOPERS ONLY!</b><br />
2403 Enable logging queries and execution times to be displayed in the bottom
2404 of main page (right frame).</dd>
2407 <dd>All possible types of a MySQL column. In most cases you don't need to
2408 edit this.</dd>
2411 <dd>Possible attributes for columns. In most cases you don't need to edit
2412 this.</dd>
2415 <dd>A list of functions MySQL supports. In most cases you don't need to
2416 edit this.</dd>
2419 <dd>Mapping of column types to meta types used for preferring displayed
2420 functions. In most cases you don't need to edit this.</dd>
2423 <dd>Functions preferred for column meta types as defined in
2424 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2425 to edit this.</dd>
2428 <dd>Functions selected by default when inserting/changing row, Functions
2429 are defined for meta types from
2431 <code>first_timestamp</code>, which is used for first timestamp column
2432 in table.</dd>
2434 </dl>
2436 <!-- TRANSFORMATIONS -->
2442 </ol>
2446 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2448 section</a> on how to do so.</p>
2450 <p> You can apply different transformations to the contents of each column. The
2451 transformation will take the content of each column and transform it with
2452 certain rules defined in the selected transformation.</p>
2454 <p> Say you have a column 'filename' which contains a filename. Normally you would
2455 see in phpMyAdmin only this filename. Using transformations you can transform
2456 that filename into a HTML link, so you can click inside of the phpMyAdmin
2457 structure on the column's link and will see the file displayed in a new browser
2458 window. Using transformation options you can also specify strings to
2459 append/prepend to a string or the format you want the output stored in.</p>
2461 <p> For a general overview of all available transformations and their options,
2462 you can consult your
2463 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2464 installation.</p>
2466 <p> For a tutorial on how to effectively use transformations, see our
2468 the official phpMyAdmin homepage.</p>
2472 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2473 clicking on the 'Structure' link for a table). There click on
2474 "Change" (or change icon) and there you will see three new
2475 fields at
2476 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2477 'Transformation options'.</p>
2479 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2480 that corresponds to the column's contents. Please note that
2481 transformations are inactive as long as no MIME-type is selected.</li>
2483 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2484 hopefully growing amount of pre-defined transformations. See below for information on
2485 how to build your own transformation.<br />
2487 There are global transformations and mimetype-bound transformations. Global transformations
2488 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2489 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2490 transformations which operate on the main mimetype (like 'image'), which will most likely
2491 take the subtype into regard, and those who only operate on a
2492 specific subtype (like 'image/jpeg').<br />
2494 You can use transformations on mimetypes for which the function was not defined for. There
2495 is no security check for you selected the right transformation, so take care of what the
2496 output will be like.</li>
2498 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2499 transform-function specific options here. Usually the transforms can operate with default
2500 options, but it is generally a good idea to look up the overview to see which options are
2501 necessary.<br />
2503 Much like the ENUM/SET-Fields, you have to split up several options using the format
2504 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2505 parsed as an array, leaving the first value the first element in the array, and so
2506 forth.<br />
2508 If you want to specify a MIME character set you can define it in the transformation_options.
2509 You have to put that outside of the pre-defined options of the specific mime-transform,
2511 for which you can specify 2 options and you want to append a character set, enter "'first
2512 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2514 </ul>
2518 <p> All mimetypes and their transformations are defined through single files in
2519 the directory 'libraries/transformations/'.</p>
2521 <p> They are stored in files to ease up customization and easy adding of new
2522 transformations.</p>
2524 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2525 always work. It makes no sense to apply a transformation to a mimetype the
2526 transform-function doesn't know to handle.</p>
2528 <p> One can, however, use empty mime-types and global transformations which should work
2529 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2530 for, but pay attention to option usage as well as what the transformation does to your
2531 column.</p>
2533 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2534 any other transform function and provides some basic functions.</p>
2536 <p> There are 5 possible file names:</p>
2538 <ol><li>A mimetype+subtype transform:<br /><br />
2540 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2542 Please not that mimetype and subtype are separated via '_', which shall
2543 not be contained in their names. The transform function/filename may
2544 contain only characters which cause no problems in the file system as
2545 well as the PHP function naming convention.<br /><br />
2547 The transform function will the be called
2548 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2550 <b>Example:</b><br /><br />
2552 <tt>text_html__formatted.inc.php</tt><br />
2553 <tt>PMA_transform_text_html__formatted()</tt></li>
2555 <li>A mimetype (w/o subtype) transform:<br /><br />
2557 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2559 Please note that there are no single '_' characters.
2560 The transform function/filename may contain only characters which cause
2561 no problems in the file system as well as the PHP function naming
2562 convention.<br /><br />
2564 The transform function will the be called
2565 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2567 <b>Example:</b><br /><br />
2569 <tt>text__formatted.inc.php</tt><br />
2570 <tt>PMA_transform_text__formatted()</tt></li>
2572 <li>A mimetype+subtype without specific transform function<br /><br />
2574 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2576 Please note that there are no '__' characters in the filename. Do not
2577 use special characters in the filename causing problems with the file
2578 system.<br /><br />
2580 No transformation function is defined in the file itself.<br /><br />
2582 <b>Example:</b><br /><br />
2584 <tt>text_plain.inc.php</tt><br />
2585 (No function)</li>
2587 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2589 <tt>[mimetype].inc.php</tt><br /><br />
2591 Please note that there are no '_' characters in the filename. Do not use
2592 special characters in the filename causing problems with the file system.
2593 <br /><br />
2595 No transformation function is defined in the file itself.<br /><br />
2597 <b>Example:</b><br /><br />
2599 <tt>text.inc.php</tt><br />
2600 (No function)</li>
2602 <li>A global transform function with no specific mimetype<br /><br />
2604 <tt>global__[transform].inc.php</tt><br /><br />
2606 The transform function will the be called
2607 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2609 <b>Example:</b><br /><br />
2611 <tt>global__formatted</tt><br />
2612 <tt>PMA_transform_global__formatted()</tt></li>
2613 </ol>
2615 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2616 transform function.</p>
2618 <p> All filenames containing no '__' in themselves are not shown as valid transform
2619 functions in the dropdown.</p>
2621 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2622 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2623 without a transform function.</p>
2625 <p> To create a new transform function please see
2626 <tt>libraries/transformations/template_generator.sh</tt>.
2627 To create a new, empty mimetype please see
2628 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2630 <p> A transform function always gets passed three variables:</p>
2632 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2633 you want to transform.</li>
2634 <li><b>$options</b> - Contains any user-passed options to a transform function
2635 as an array.</li>
2636 <li><b>$meta</b> - Contains an object with information about your column.
2637 The data is drawn from the output of the
2639 function. This means, all object properties described on the
2641 available in this variable and can be used to transform a column accordingly
2642 to unsigned/zerofill/not_null/... properties.<br />
2643 The $meta->mimetype variable contains the original MIME-type of the
2644 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2645 </ol>
2647 <p> Additionally you should also provide additional function to provide
2648 information about the transformation to the user. This function should
2649 have same name as transformation function just with appended
2650 <code>_info</code> suffix. This function accepts no parameters and returns
2651 array with information about the transformation. Currently following keys
2652 can be used:
2653 </p>
2654 <dl>
2655 <dt><code>info</code></dt>
2656 <dd>Long description of the transformation.</dd>
2657 </dl>
2659 <!-- FAQ -->
2666 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2671 </ol>
2673 <p> Please have a look at our
2675 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2676 features and or interface.</p>
2682 action is required or phpMyAdmin sends a blank page or a page full of
2683 cryptic characters to my browser, what can I do?</a></h4>
2686 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2687 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2688 configuration file.<br /></p>
2693 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2694 See also the
2696 entry about PHP bugs with output buffering.<br />
2697 If your server keeps crashing, please ask for help in the various Apache
2698 support groups.</p>
2707 application misbehaved by not returning a complete set of
2709 </h4>
2711 <p> You just forgot to read the <i>install.txt</i> file from the PHP distribution.
2712 Have a look at the last message in this
2714 official PHP bug database.</p>
2719 and/or many error messages with the
2722 <p> This is a known problem with the PHP
2724 filter: it's not so stable. Please use instead the cookie authentication mode.
2725 </p>
2730 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2731 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2732 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2733 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2734 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2739 work.</a></h4>
2741 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2742 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2743 or not, and so on). So, you must have Zlib/Bzip2
2744 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2748 an error about safe mode being in effect.</a></h4>
2750 <p> Your uploaded file is saved by PHP in the "upload dir", as
2751 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2752 the system default is <i>/tmp</i>).<br />
2753 We recommend the following setup for Apache servers running in safe mode,
2754 to enable uploads of files while being reasonably secure:</p>
2756 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2757 <li>give ownership to the Apache server's user.group:
2758 <tt>chown apache.apache /tmp/php</tt></li>
2759 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2760 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2761 <li>restart Apache</li>
2762 </ul>
2769 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2770 I'm using the Apache server.</a></h4>
2772 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2773 your <i>httpd.conf</i>:</p>
2777 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2781 uploading a file from the query box.</a></h4>
2783 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2784 restrictions. However you need to create temporary directory and
2786 The uploaded files will be moved there, and after execution of your
2792 <p> The MySQL manual explains how to
2794 reset the permissions</a>.</p>
2804 </h4>
2806 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2807 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2808 names to align with current standards.</p>
2813 </h4>
2815 <p> Starting with version 2.7.0, the import engine has been re–written and these
2816 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2817 to take advantage of the new import features.</p>
2819 <p> The first things to check (or ask your host provider to check) are the
2820 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2821 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2822 All of these three settings limit the maximum size of data that can be
2823 submitted and handled by PHP. One user also said that
2824 <tt>post_max_size</tt>
2825 and <tt>memory_limit</tt> need to be larger than <tt>upload_max_filesize</tt>.<br /> <br />
2827 There exist several workarounds if your upload is too big or your
2828 hosting provider is unwilling to change the settings:</p>
2831 feature. This allows one to
2832 upload a file to the server via scp, ftp, or your favorite file transfer
2833 method. PhpMyAdmin is then able to import the files from the temporary
2835 section</a> of this document.</li>
2837 BigDump</a>) to split the files before uploading. We cannot support this
2838 or any third party applications, but are aware of users having success
2839 with it.</li>
2840 <li>If you have shell (command line) access, use MySQL to import the files
2841 directly. You can do this by issuing the "source" command from
2842 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2843 </ul>
2847 support?</a></h4>
2849 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2850 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2851 connect to your MySQL server using PHP's classic
2854 is available in PHP 5.0. The latter one should be used unless you have a
2855 good reason not to do so.<br />
2856 When compiling PHP, we strongly recommend that you manually link the MySQL
2857 extension of your choice to a MySQL client library of at least the same
2858 minor version since the one that is bundled with some PHP distributions is
2862 (versions 5.1 and 5.2 were tested).<br /><br />
2864 </p>
2868 message, "Client does not support authentication protocol requested
2869 by server; consider upgrading MySQL client"</a></h5>
2871 <p> You tried to access MySQL with an old MySQL client library. The version of
2872 your MySQL client library can be checked in your phpinfo() output.
2873 In general, it should have at least the same minor version as your server
2877 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2878 changed the authentication hash and your PHP is trying to use the old method.
2880 with the proper client library to match your MySQL installation. Your
2881 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2882 More information (and several workarounds) are located in the
2884 </p>
2891 script seems not to know the font face I'm using!</a></h4>
2893 <p> The "FPDF" library we're using for this feature requires some
2894 special files to use font faces.<br />
2896 these files.</p>
2900 check PHP Configuration".</a></h4>
2902 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2903 "MySQL extension". This extension may be part of the PHP
2904 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2905 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2906 to load the extension but failed.<br /><br />
2908 Usually, the problem is solved by installing a software package called
2909 "PHP-MySQL" or something similar.</p>
2914 and I cannot log in using cookie auth.</a></h4>
2916 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2920 so I cannot upload.</a></h4>
2922 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2923 parameter is not set to "on".</p>
2927 a new table the table and column names are changed to lowercase!</a></h4>
2929 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2930 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2931 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2932 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2933 directory and add the following line to the group [mysqld]:</p>
2935 <pre>set-variable = lower_case_table_names=0</pre>
2937 <p> Next, save the file and restart the MySQL service. You can always check the
2938 value of this directive using the query</p>
2940 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2947 and I get problems, such as undefined variables when I run a
2950 <p> A tip from Jose Fandos: put a comment on the following two lines
2951 in httpd.conf, like this:</p>
2953 <pre>
2954 # mod_gzip_item_include file \.php$
2956 </pre>
2958 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2959 PHP scripts. Of course you have to restart Apache.</p>
2964 I get the error "No input file specified" when trying to
2965 run phpMyAdmin.</a></h4>
2967 <p> This is a permission problem. Right-click on the phpmyadmin folder
2968 and choose properties. Under the tab Security, click on "Add"
2969 and select the user "IUSR_machine" from the list. Now set his
2970 permissions and it should work.</p>
2974 db_structure.php with plenty of tables).</a></h4>
2977 GZIP output buffering is enabled. If you turn off it (by
2979 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2980 PHP 5.0.0.</p>
2984 message 'Errorcode: 13'. What does this mean?</a></h4>
2986 <p> This can happen due to a MySQL bug when having database / table names with
2987 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2988 To fix this, turn off this directive, convert all database and table names
2989 to lower case and turn it on again. Alternatively, there's a bug-fix
2990 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2994 and the columns are duplicated.</a></h4>
2996 <p> It is possible to configure Apache in such a way that PHP has problems
2997 interpreting .php files.</p>
2999 <p> The problems occur when two different (and conflicting) set of directives
3000 are used:</p>
3002 <pre>
3003 SetOutputFilter PHP
3004 SetInputFilter PHP
3005 </pre>
3007 <p> and</p>
3009 <pre>AddType application/x-httpd-php .php</pre>
3011 <p> In the case we saw, one set of directives was in
3012 <tt>/etc/httpd/conf/httpd.conf</tt>, while
3013 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
3014 The recommended way is with <tt>AddType</tt>, so just comment out
3015 the first set of lines and restart Apache:</p>
3017 <pre>
3018 #SetOutputFilter PHP
3019 #SetInputFilter PHP
3020 </pre>
3025 <p> This problem is known to happen when the server is running Turck MMCache
3026 but upgrading MMCache to version 2.3.21 solves the problem.</p>
3031 <p>Yes.</p>
3032 <p>
3033 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
3034 is still maintained.
3035 </p>
3038 <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>
3040 <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>
3043 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3044 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3045 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3046 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3047 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3048 enabled.) Click <tt>OK</tt>.</li>
3049 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3050 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3051 </ol>
3060 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
3061 the order of the server paragraph in <tt>config.inc.php</tt>.
3062 Table and script parts are optional. If you want
3063 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3064 some configuration. Following lines apply only for <a
3066 that you have enabled some features within global configuration. You need
3067 <code>Options FollowSymLinks</code> and <code>AllowOverride
3068 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3069 you need mod_rewrite to be enabled. Then you just need to create following
3071 (don't forget to change directory name inside of it):</p>
3073 <pre>
3074 RewriteEngine On
3075 RewriteBase /path_to_phpMyAdmin
3076 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3077 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3078 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3079 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3080 </pre>
3083 <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>
3085 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3086 following rewrite rule:</p>
3088 <pre>
3089 RewriteEngine On
3090 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3091 </pre>
3095 </h4>
3096 <p>
3097 There can be many explanations to this and a look at your server's
3098 error log file might give a clue.
3099 </p>
3103 password encryption in cookie auth doesn't work.</a></h4>
3105 <p> If your cluster consist of different architectures, PHP code used for
3106 encryption/decryption won't work correct. This is caused by use of
3107 pack/unpack functions in code. Only solution is to use mcrypt extension
3108 which works fine in this case.</p>
3113 <p> Yes but the default configuration values of Suhosin are known to cause
3114 problems with some operations, for example editing a table with many
3115 columns and no primary key or with textual primary key.
3116 </p>
3117 <p>
3118 Suhosin configuration might lead to malfunction in some cases and it can
3119 not be fully avoided as phpMyAdmin is kind of application which needs to
3120 transfer big amounts of columns in single HTTP request, what is something
3121 what Suhosin tries to prevent. Generally all
3122 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3123 <code>suhosin.get.*</code> directives can have negative effect on
3124 phpMyAdmin usability. You can always find in your error logs which limit
3125 did cause dropping of variable, so you can diagnose the problem and adjust
3126 matching configuration variable.
3127 </p>
3128 <p>
3129 The default values for most Suhosin configuration options will work in most
3130 scenarios, however you might want to adjust at least following parameters:
3131 </p>
3133 <ul>
3134 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_vars">suhosin.request.max_vars</a> should be increased (eg. 2048)</li>
3135 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_vars">suhosin.post.max_vars</a> should be increased (eg. 2048)</li>
3136 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_array_index_length">suhosin.request.max_array_index_length</a> should be increased (eg. 256)</li>
3137 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_array_index_length">suhosin.post.max_array_index_length</a> should be increased (eg. 256)</li>
3138 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_totalname_length">suhosin.request.max_totalname_length</a> should be increased (eg. 8192)</li>
3139 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_totalname_length">suhosin.post.max_totalname_length</a> should be increased (eg. 8192)</li>
3140 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.get.max_value_length">suhosin.get.max_value_length</a> should be increased (eg. 1024)</li>
3141 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.sql.bailout_on_error">suhosin.sql.bailout_on_error</a> needs to be disabled (the default)</li>
3142 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#logging_configuration">suhosin.log.*</a> should not include <abbr title="structured query language">SQL</abbr>, otherwise you get big slowdown</li>
3143 </ul>
3145 <p>
3147 <tt>SuhosinDisableWarning</tt> directive</a>.
3148 </p>
3152 but then my connection is redirected back to http. What can cause this
3153 behavior?</a></h4>
3155 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3156 in your Apache configuration. See <a href="http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions">http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions</a>.</p>
3159 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3161 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3162 Example from the Apache 2.2 documentation:</p>
3163 <pre>
3164 ProxyPass /mirror/foo/ http://backend.example.com/
3165 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3166 ProxyPassReverseCookieDomain backend.example.com public.example.com
3167 ProxyPassReverseCookiePath / /mirror/foo/
3168 </pre>
3170 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3171 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3172 This is not specific to phpmyadmin, it's just the behavior of Apache.
3173 </p>
3175 <pre>
3176 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3177 ProxyPassReverse /mirror/foo/
3178 http://backend.example.com/%7Euser/phpmyadmin
3179 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3180 </pre>
3182 <p>See <a href="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html">http://httpd.apache.org/docs/2.2/mod/mod_proxy.html</a>
3183 for more details.</p>
3187 privileges, I get an error about an unknown column.</a></h4>
3189 <p> The MySQL server's privilege tables are not up to date, you need to run
3190 the <tt>mysql_upgrade</tt> command on the server.</p>
3196 based on user agent field. This is quite easy to circumvent, but could prevent at least
3197 some robots accessing your installation.</p>
3199 <pre>
3200 RewriteEngine on
3202 # Allow only GET and POST verbs
3203 RewriteCond %{REQUEST_METHOD} !^(GET|POST)$ [NC,OR]
3205 # Ban Typical Vulnerability Scanners and others
3206 # Kick out Script Kiddies
3207 RewriteCond %{HTTP_USER_AGENT} ^(java|curl|wget).* [NC,OR]
3208 RewriteCond %{HTTP_USER_AGENT} ^.*(libwww-perl|curl|wget|python|nikto|wkito|pikto|scan|acunetix).* [NC,OR]
3209 RewriteCond %{HTTP_USER_AGENT} ^.*(winhttp|HTTrack|clshttp|archiver|loader|email|harvest|extract|grab|miner).* [NC,OR]
3211 # Ban Search Engines, Crawlers to your administrative panel
3212 # No reasons to access from bots
3213 # Ultimately Better than the useless robots.txt
3214 # Did google respect robots.txt?
3215 # Try google: intitle:phpMyAdmin intext:"Welcome to phpMyAdmin *.*.*" intext:"Log in" -wiki -forum -forums -questions intext:"Cookies must be enabled"
3216 RewriteCond %{HTTP_USER_AGENT} ^.*(AdsBot-Google|ia_archiver|Scooter|Ask.Jeeves|Baiduspider|Exabot|FAST.Enterprise.Crawler|FAST-WebCrawler|www\.neomo\.de|Gigabot|Mediapartners-Google|Google.Desktop|Feedfetcher-Google|Googlebot|heise-IT-Markt-Crawler|heritrix|ibm.com\cs/crawler|ICCrawler|ichiro|MJ12bot|MetagerBot|msnbot-NewsBlogs|msnbot|msnbot-media|NG-Search|lucene.apache.org|NutchCVS|OmniExplorer_Bot|online.link.validator|psbot0|Seekbot|Sensis.Web.Crawler|SEO.search.Crawler|Seoma.\[SEO.Crawler\]|SEOsearch|Snappy|www.urltrends.com|www.tkl.iis.u-tokyo.ac.jp/~crawler|SynooBot|crawleradmin.t-info@telekom.de|TurnitinBot|voyager|W3.SiteSearch.Crawler|W3C-checklink|W3C_Validator|www.WISEnutbot.com|yacybot|Yahoo-MMCrawler|Yahoo\!.DE.Slurp|Yahoo\!.Slurp|YahooSeeker).* [NC]
3217 RewriteRule .* - [F]
3218 </pre>
3226 headers already sent by ..." is displayed, what's the problem?</a></h4>
3228 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3229 (I.E. no blank lines, no spaces, no characters...) neither before the
3230 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3231 tag at the end. We also got a report from a user under
3233 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3234 contained an end-of-line character (hex 0A) at the end; removing this character
3235 cleared his errors.</p>
3240 <p> Either there is an error with your PHP setup or your username/password is
3241 wrong. Try to make a small script which uses mysql_connect and see if it
3242 works. If it doesn't, it may be you haven't even compiled MySQL support
3243 into PHP.</p>
3247 connect to local MySQL server through socket '/tmp/mysql.sock'
3248 (111) ..." is displayed. What can I do?</a></h4>
3250 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3252 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3253 In your <i>php.ini</i> you will find a line</p>
3255 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3257 <p> change it to</p>
3259 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3261 <p> Then restart apache and it will work.</p>
3263 <p> Here is a fix suggested by Brad Ummer:</p>
3265 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3266 To do this, telnet to your server and go to the MySQL bin directory. In
3267 this directory there should be a file named <i>mysqladmin</i>. Type
3268 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3269 info about your MySQL server, including the socket
3270 (<i>/tmp/mysql.sock</i>, for example).</li>
3271 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3272 phpMyAdmin, you need to complete the socket information in the
3273 <i>config.inc.php</i>.<br />
3274 For example:
3276 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3277 <br /><br />
3279 Please also make sure that the permissions of this file allow to be readable
3280 by your webserver (i.e. '0755').</li>
3281 </ul>
3283 <p> Have also a look at the
3285 corresponding section of the MySQL documentation</a>.</p>
3289 what can I do?</a></h4>
3292 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3293 sometime.<br />
3294 Also have a look at your PHP version number: if it contains "b" or "alpha"
3295 it means you're running a testing version of PHP. That's not a so good idea,
3296 please upgrade to a plain revision.</p>
3300 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3301 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3303 <p> Check the value you set for the
3305 directive in the phpMyAdmin configuration file.</p>
3309 password: YES)"-error when trying to access a MySQL-Server on a
3310 host which is port-forwarded for my localhost.</a></h4>
3312 <p> When you are using a port on your localhost, which you redirect via
3313 port-forwarding to another host, MySQL is not resolving the localhost
3314 as expected.<br />
3315 Erik Wasser explains: The solution is: if your host is "localhost"
3316 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3317 connection for speeding up things. And that doesn't work in this configuration
3318 with port forwarding.<br />
3324 <p> Themes are configured with
3328 <br />
3330 should not delete the directory "original" or its underlying
3331 structure, because this is the system theme used by phpMyAdmin.
3332 "original" contains all images and styles, for backwards
3333 compatibility and for all themes that would not include images or css-files.
3334 <br /><br />
3337 is enabled, you can select your favorite theme on the main page. Your
3338 selected theme will be stored in a cookie.<br /><br /></p>
3340 <p> To create a theme:</p>
3342 <ul><li>make a new subdirectory (for example "your_theme_name") under
3344 (by default <tt>themes</tt>)</li>
3345 <li>copy the files and directories from "original" to
3346 "your_theme_name"</li>
3347 <li>edit the css-files in "your_theme_name/css"</li>
3348 <li>put your new images in "your_theme_name/img"</li>
3349 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3350 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3351 contain your chosen theme name, that will be visible in user interface</li>
3352 <li>make a new screenshot of your theme and save it under
3353 "your_theme_name/screen.png"</li>
3354 </ul>
3356 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3357 theme verbose name, theme generation and theme version. These versions and
3358 generations are enumerated from 1 and do not have any direct dependence on
3359 phpMyAdmin version. Themes within same generation should be backwards
3360 compatible - theme with version 2 should work in phpMyAdmin requiring
3361 version 1. Themes with different generation are incompatible.</p>
3363 <p> If you do not want to use your own symbols and buttons, remove the
3364 directory "img" in "your_theme_name". phpMyAdmin will
3365 use the default icons and buttons (from the system-theme "original").
3366 </p>
3370 what can I do?</a></h4>
3372 <p> Here are a few points to check:</p>
3374 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3376 directive empty. See also
3378 </li>
3379 <li>Maybe you have a broken PHP installation or you need to upgrade
3380 your Zend Optimizer. See
3382 http://bugs.php.net/bug.php?id=31134</a>.
3383 </li>
3384 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3385 set to the default (200) or another low value, you could get this
3386 error if your table has a high number of columns. Adjust this setting
3387 accordingly. (Thanks to Klaus Dorninger for the hint).
3388 </li>
3389 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3390 of ";" will cause this error. Replace it with "&;".
3391 </li>
3393 you might want to increase
3395 </li>
3396 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3397 </li>
3398 </ul>
3403 <p> To be able to see a progress bar during your uploads, your server must
3406 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3407 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3414 who logged out can not log in again in with the same nick.</a></h4>
3416 <p> This is related to the authentication mechanism (protocol) used by
3417 phpMyAdmin. To bypass this problem: just close all the opened
3418 browser windows and then go back to phpMyAdmin. You should be able to
3419 log in again.</p>
3423 limit error or a time limit error.</a></h4>
3425 <p> Compressed dumps are built in memory and because of this are limited to
3426 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3427 using
3429 (enabled by default). Zip exports can not be handled this way, so if you need
3430 Zip files for larger dump, you have to use another way.</p>
3434 when I rename a table or a column.</a></h4>
3436 <p> This is an InnoDB bug, see <a href="http://bugs.mysql.com/bug.php?id=21704">http://bugs.mysql.com/bug.php?id=21704</a>.</p>
3440 bundled with the MySQL server distribution.</a></h4>
3442 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3444 <pre>
3445 -- MySQL dump 8.22
3446 --
3447 -- Host: localhost Database: database
3448 ---------------------------------------------------------
3449 -- Server version 3.23.54
3450 </pre>
3452 <p> The invalid part of the code is the horizontal line made of dashes that
3453 appears once in every dump created with mysqldump. If you want to run your
3454 dump you have to turn it into valid MySQL. This means, you have to add a
3455 whitespace after the first two dashes of the line or add a # before it:
3456 <br />
3457 <code>
3458 -- -------------------------------------------------------<br />
3459 </code>
3460 or<br />
3461 <code>
3462 #---------------------------------------------------------
3463 </code>
3464 </p>
3471 <p> Please note that you should not use the separating string multiple times
3472 without any characters between them, or at the beginning/end of your table
3473 name. If you have to, think about using another TableSeparator or disabling
3474 that feature</p>
3479 <p> In Relation view, being able to choose a table in another database,
3480 or having more than one index column in the foreign key.<br /><br/>
3481 In Query-by-example (Query), automatic generation of the query
3482 LEFT JOIN from the foreign table.<br /><br/>
3483 </p>
3487 I get series of errors like "Warning: unable to parse url". How
3488 can this be fixed?</a></h4>
3489 <p>
3490 Your table neither have a primary key nor an unique one, so we must use a
3491 long expression to identify this row. This causes problems to parse_url
3492 function. The workaround is to create a primary or unique key.
3493 <br />
3494 </p>
3498 a MIME-Transformation onto!</a></h4>
3500 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3501 nested forms can be put inside the table where phpMyAdmin displays the results.
3502 You can, however, use any form inside of a table if keep the parent
3503 form-container with the target to tbl_row_delete.php and just put your own
3504 input-elements inside. If you use a custom submit input field, the form will
3505 submit itself to the displaying page again, where you can validate the
3506 $HTTP_POST_VARS in a transformation.
3508 For a tutorial on how to effectively use transformations, see our
3510 on the official phpMyAdmin-homepage.</p>
3514 MySQL server</a></h4>
3516 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3519 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3520 the quote-character (") is interpreted as an identifier quote character and
3521 not as a string quote character, which makes many internal phpMyAdmin
3523 statements. There is no workaround to this behaviour. News to this item will
3524 be posted in Bug report
3525 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3526 </p>
3530 more that one column with the same value
3531 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3532 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3534 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3535 can use it for the Edit and Delete links.</p>
3540 <p> phpMyAdmin uses a quick method to get the row count, and this method
3541 only returns an approximate count in the case of InnoDB tables. See
3543 a way to modify those results, but
3544 this could have a serious impact on performance.</p>
3551 containing an hyphen.
3552 </a></h4>
3553 <p>
3554 The tests I have made with MySQL 5.1.49 shows that the
3555 API does not accept this syntax for the USE command.
3556 </p>
3559 <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>
3560 <p>
3561 This has been a known limitation of phpMyAdmin since the beginning and
3562 it's not likely to be solved in the future.
3563 </p>
3565 <!-- Begin: Excel import limitations -->
3576 <!-- End: Excel import limitations -->
3577 <!-- Begin: CSV import limitations -->
3581 CSV</abbr> file that contains multiple tables, they are lumped together into
3582 a single table.</a></h4>
3583 <p>
3585 CSV</abbr> format. For the time being, you will have to break apart
3587 </p>
3589 <!-- End: CSV import limitations -->
3590 <!-- Begin: Import type-detection limitations -->
3593 <a href="#faq3_19">3.19 When I import a file and have phpMyAdmin determine the appropriate data structure it only uses int, decimal, and varchar types.</a></h4>
3594 <p>
3595 Currently, the import type-detection system can only assign these MySQL types to columns. In future, more will likely be added but for the time being
3596 you will have to edit the structure to your liking post-import.
3597 <br /><br />
3598 Also, you should note the fact that phpMyAdmin will use the size of the largest item in any given column as the column size for the appropriate type. If you
3599 know you will be adding larger items to that column then you should manually adjust the column sizes accordingly. This is done for the sake of efficiency.
3600 </p>
3602 <!-- End: Import type-detection limitations -->
3604 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3607 <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
3608 need to install it for each customer.
3609 </a></h4>
3610 <p>
3611 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3612 your users. The development of this feature was kindly sponsored by
3613 NetCologne GmbH.
3614 This requires a properly setup MySQL user management and phpMyAdmin
3615 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3617 </p>
3621 access.
3622 </a></h4>
3623 <p>
3624 This depends on your system.<br />
3625 If you're running a server which cannot be accessed by other people, it's
3626 sufficient to use the directory protection bundled with your webserver
3628 If other people have telnet access to your server, you should use
3629 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3630 <br /><br />
3631 Suggestions:
3632 </p>
3633 <ul>
3634 <li>
3636 </li>
3637 <li>
3638 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3639 is a user whose password is only known to you, and apache is the
3640 group under which Apache runs.
3641 </li>
3642 <li>
3643 Follow security recommendations for PHP and your webserver.
3644 </li>
3645 </ul>
3650 </a></h4>
3651 <p>
3656 </p>
3659 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3660 authentication.
3661 </a></h4>
3665 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3666 and/or
3668 are wrong.</li>
3670 <li>You have already setup a security mechanism for the
3671 phpMyAdmin-directory, eg. a <a href="#glossary"><i>.htaccess</i></a> file. This would interfere with
3672 phpMyAdmin's authentication, so remove it.</li>
3673 </ul>
3680 and put the privileges you want. For example,
3682 would let a user create/manage his/her database(s).</p>
3687 <p> If you have existing rules from an old <a href="#glossary"><i>.htaccess</i></a> file, you can take them
3690 be a major benefit here if your installation is suited to using it. Then
3691 you can just add those updated lines into the
3695 <p> If you want a pre-made sample, you can try this fragment. It stops the
3696 'root' user from logging in from any networks other than the private
3699 <pre>
3700 //block root from logging in except from the private networks
3701 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3702 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3703 'deny root from all',
3704 'allow root from localhost',
3708 );
3709 </pre>
3714 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3715 different than the one set in your
3717 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3718 while a domain name is defined in the config file.</p>
3723 <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>
3729 when trying to create a table with more than 14 columns.
3730 </a></h4>
3731 <p>
3732 We could reproduce this problem only under Win98/98SE. Testing under
3733 WinNT4 or Win2K, we could easily create more than 60 columns.
3734 <br />
3735 A workaround is to create a smaller number of columns, then come back to
3736 your table properties and add the other columns.
3737 </p>
3741 <p>
3742 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3743 with each script/website that use forms.<br />
3744 Upgrade or downgrade your Xitami server.
3745 </p>
3748 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3749 <p>
3750 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3751 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3752 don't seem to work.<br />
3754 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3755 the user's temporary directory, so they must be moved before closing
3756 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3759 </p>
3763 Explorer never stores the cookies.
3764 </a></h4>
3765 <p>
3766 MS Internet Explorer seems to be really buggy about cookies, at least till
3767 version 6.
3768 </p>
3772 rows.
3773 </a></h4>
3774 <p>
3776 </p>
3779 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3780 when trying to modify a row in a table with many columns, or with a text
3781 column
3782 </a></h4>
3783 <p>
3784 Your table neither have a primary key nor an unique one, so we must use a
3785 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
3786 those browsers, and this not happen in Netscape, for example. The
3787 workaround is to create a primary or unique key, or use another browser.
3788 <br />
3789 </p>
3793 page.
3794 </a></h4>
3795 <p>
3796 Some browsers support right-clicking into the frame you want to refresh,
3797 just do this in the right frame.<br />
3798 </p>
3802 query box.
3803 </a></h4>
3804 <p>
3805 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3806 Mozilla versions.<br />
3807 </p>
3811 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3812 </a></h4>
3813 <p>
3814 This is a Mozilla bug (see bug #26882 at
3816 </p>
3821 </a></h4>
3822 <p>
3823 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3824 data in octet-stream mode. Since we can't detect the specific Netscape
3825 version, we cannot workaround this bug.
3826 </p>
3830 wrong.</a></h4>
3832 <p> Please ensure that you have set your browser's character set to the one of the
3833 language file you have selected on phpMyAdmin's start page.
3834 Alternatively, you can try the auto detection mode that is supported by the
3835 recent versions of the most browsers.</p>
3838 <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
3841 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3842 Netscape and Mozilla do not have this problem.</p>
3845 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3846 I cannot manage two servers: I log in to the first one, then the other one,
3847 but if I switch back to the first, I have to log in on each operation.</a></h4>
3853 but nothing happens after that, only a blank screen.</a></h4>
3864 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3869 address and you are starting
3871 containing a domain name, or the reverse situation.</li>
3872 <li>Security settings in IE and/or Microsoft Security Center are
3873 too high, thus blocking scripts execution.</li>
3874 <li>The Windows Firewall is blocking Apache and MySQL. You must
3878 </ul>
3881 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3882 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3883 installed in their Firefox is causing the problem.</p>
3887 clause is generated when I browse a table.</a></h4>
3888 <p> This happens only when both of these conditions are met: using the
3895 <p> Issues have been reported with some combinations of browser extensions.
3896 To troubleshoot, disable all extensions then clear your browser cache
3897 to see if the problem goes away.</p>
3904 </a></h4>
3905 <p>
3906 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3907 specifying a wrong column-type.<br />
3908 Common errors include:
3909 </p>
3910 <ul>
3913 </ul>
3914 <p>
3915 Also, look at the syntax chapter in the MySQL manual to confirm that your
3916 syntax is correct.
3917 </p>
3921 columns and
3922 phpMyAdmin generates only one index with those two columns.
3923 </a></h4>
3924 <p>
3925 This is the way to create a multi-columns
3926 index. If you want two indexes, create the first one when creating the
3927 table, save, then display the table properties and click the Index link to
3928 create the other index.
3929 </p>
3933 <p>
3934 Since version 2.2.3, you have a checkbox for each column that can be null.
3936 column's value. Since version 2.5.5, you have to use the checkbox to get
3938 a literal NULL in the column, and not a NULL value (this works in PHP4).
3939 </p>
3944 <p> Click on a database or table name in the left frame, the properties will be
3946 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3947 statements that can be used to recreate your database/table.
3948 <br /><br />
3950 transmit the resulting dump to your station. Depending on your PHP
3951 configuration, you will see options to compress the dump. See also the
3953 configuration variable.<br /><br />
3956 this document.</p>
3961 </a></h4>
3963 <p> Click on a database name in the left frame, the properties will be
3965 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3967 the path to your dump filename, or use the Browse button. Then click Go.
3968 <br /><br />
3970 that you upgrade to take advantage of the new features.
3971 <br /><br />
3973 in this document.
3974 </p>
3979 <p> Here is an example with the tables persons, towns and countries, all
3981 table, create it as explained in the configuration section. Then create the
3982 example tables:</p>
3984 <pre>
3985 CREATE TABLE REL_countries (
3986 country_code char(1) NOT NULL default '',
3987 description varchar(10) NOT NULL default '',
3988 PRIMARY KEY (country_code)
3989 ) TYPE=MyISAM;
3991 INSERT INTO REL_countries VALUES ('C', 'Canada');
3993 CREATE TABLE REL_persons (
3994 id tinyint(4) NOT NULL auto_increment,
3995 person_name varchar(32) NOT NULL default '',
3997 country_code char(1) NOT NULL default '',
3998 PRIMARY KEY (id)
3999 ) TYPE=MyISAM;
4001 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
4002 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
4004 CREATE TABLE REL_towns (
4006 description varchar(30) NOT NULL default '',
4007 PRIMARY KEY (town_code)
4008 ) TYPE=MyISAM;
4010 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
4011 INSERT INTO REL_towns VALUES ('M', 'Montréal');
4012 </pre>
4018 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
4022 </ul>
4030 <li>In the columns row, choose persons.person_name and click the
4032 <li>Do the same for towns.description and countries.descriptions in the
4035 the correct joins have been generated</li>
4037 </ul>
4041 <p>
4042 Starting from the previous example, create the pma_table_info as explained
4043 in the configuration section, then browse your persons table,
4044 and move the mouse over a town code or country code.
4045 <br /><br />
4046 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
4047 enables: drop-down list of possible values.
4048 </p>
4051 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
4052 <p>
4055 <br /><br />
4056 Then you need to think about your schema layout. Which tables will go on
4057 which pages?
4058 </p>
4059 <ul>
4065 page and click Go. If you like, you
4067 linked tables onto the new page.</li>
4068 <li>Select the name of the new page (making sure the Edit radio button
4069 is selected) and click Go.</li>
4071 Coordinates are relative; your diagram will
4072 be automatically scaled to fit the page. When initially placing tables
4073 on the page, just pick any coordinates -- say, 50x50. After clicking
4075 position the element correctly.</li>
4077 first be sure to click the Save
4078 button beneath the list of tables and coordinates, to save any changes
4079 you made there. Then scroll all the way down, select the
4081 you want, and click Go.</li>
4082 <li>Internet Explorer for Windows may suggest an incorrect filename when
4087 browsers on Windows, do not have this problem.</li>
4088 </ul>
4092 columns!</a></h4>
4094 <p> No, it's MySQL that is doing
4100 underscores in the database name?</a></h4>
4102 <p> If you do not put a backslash before the underscore, this is a wildcard
4105 john2db ...<br /><br />
4107 If you put a backslash before the underscore, it means that the database
4108 name will have a real underscore.</p>
4112 statistics pages?</a></h4>
4123 if it already exists during the import. It does NOT drop the table after
4124 your export, it only affects the import file.</li>
4126 Otherwise, you may get an error if the table name exists but has a
4127 different structure.</li>
4129 (if any) will be included in backup.</li>
4131 column and table names formed with special characters are protected.</li>
4133 types set in the pmadb in the dump as
4135 </li>
4136 </ul>
4141 command, for better documentation (but resulting file is bigger).</li>
4143 once the INSERT verb and the table name.</li>
4146 </li>
4148 more info is provided in the
4150 but basically with this selected, invalid values are adjusted and
4151 inserted rather than causing the entire statement to fail.</li>
4152 </ul>
4156 in its name.</a></h4>
4159 is the normal way to reference a database and table name. Worse, MySQL
4160 will usually let you create a database with a dot, but then you cannot
4161 work with it, nor delete it.</p>
4167 <p>
4168 To use SQL Validator, you need PHP with
4174 module.
4175 </p>
4177 <p>
4183 usage.
4184 </p>
4186 <p>
4187 If you use the Validator, you should be aware that any
4189 submit will be stored anonymously (database/table/column names,
4190 strings, numbers replaced with generic values). The Mimer
4193 We utilize it as free SOAP service.
4194 </p>
4198 it, but MySQL says "BLOB column '...' used in key specification without
4201 <p> The right way to do this, is to create the column without any indexes,
4203 dialog. On this page, you will be able to choose your BLOB column, and
4204 set a size to the index, which is the condition to create an index on
4205 a BLOB column.</p>
4209 editing fields?</a></h4>
4211 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4212 with many editing fields (table structure changes, row editing, etc.).</p>
4216 WTF is this feature then useful for?</a></h4>
4218 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4219 on them. Otherwise you could just put a comment on the column. Because entering
4220 your own mimetype will cause serious syntax checking issues and validation,
4221 this introduces a high-risk false-user-input situation. Instead you have to
4222 initialize mimetypes using functions or empty mimetype definitions.<br />
4223 Plus, you have a whole overview of available mimetypes. Who knows all those
4224 mimetypes by heart so he/she can enter it at will?</p>
4228 can't I see any bookmarks below the query box? What is this variable for?
4229 </a></h4>
4231 <p> Any query you have executed can be stored as a bookmark on the page where the
4232 results are displayed. You will find a button labeled 'Bookmark this query'
4233 just at the end of the page.<br />
4234 As soon as you have stored a bookmark, it is related to the database you run
4235 the query on. You can now access a bookmark dropdown on each page, the query
4236 box appears on for that database.<br /><br />
4238 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4242 aware of that you HAVE to create a valid query, otherwise your query won't be
4243 even able to be stored in the database.<br />
4245 for your query will remain the way it is, but will be stripped of the /**/
4246 chars. So you can use:<br /><br />
4250 which will be expanded to<br /><br />
4254 in your query, where VARIABLE is the string you entered in the input box. If
4255 an empty string is provided, no replacements are made.<br /><br />
4257 A more complex example. Say you have stored this query:<br /><br />
4259 <br /><br />
4262 the full query will be:<br /><br />
4265 <br /><br />
4267 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4269 spaces inserted there
4270 will be later also inserted as spaces in your query and may lead to unexpected
4271 results especially when
4273 Your initial query which is going to be stored as a bookmark has to yield at
4274 least one result row so
4275 you can store the bookmark. You may have that to work around using well
4279 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4280 include exported table?</a></h4>
4282 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4283 document should look like following one (assuming you have table
4286 <pre>
4287 \documentclass{article} % or any class you want
4288 \usepackage{longtable} % for displaying table
4289 \begin{document} % start of document
4290 \include{table} % including exported table
4291 \end{document} % end of document
4292 </pre>
4296 access them.
4297 </a></h4>
4299 <p> You have one of these global privileges: CREATE
4300 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4301 enable users to see all the database names.
4304 So if your users do not need those privileges, you can remove them and their
4305 databases list will shorten.</p>
4309 possible values for a column, based on some foreign table?</a></h4>
4311 <p> You have to setup appropriate links between the tables, and also
4315 foreign table, a drop-down list of values will be available.
4316 You will see two lists of values, the first list containing the key
4317 and the display column, the second list containing the display column
4318 and the key. The reason for this is to be able to type the first
4319 letter of either the key or the display column.<br /><br />
4321 For 100 values or more, a distinct window will appear, to browse foreign
4322 key values and choose one. To change the default limit of 100, see
4323 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4327 automatically when entering Browse mode for a table?</a></h4>
4329 <p> Yes. If a bookmark has the same label as a table name and it's not a public bookmark, it will be executed.
4330 </p>
4335 <p> You can use
4337 which works out of the box.<br />
4338 Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel
4339 version 97 and newer was dropped.
4340 </p>
4344 what happens to my column comments stored in pmadb?</a></h4>
4346 <p> Automatic migration of a table's pmadb-style column comments to the native
4347 ones is done whenever you enter Structure page for this table.</p>
4355 <p> Click the first row of the range, hold the shift key and click the last row of the range. This works everywhere you see rows, for example in Browse mode or on the Structure page.</p>
4361 <p>
4362 In all places where phpMyAdmin accepts format strings, you can use
4365 expanded variables depend on a context (for example, if you haven't chosen a
4366 table, you can not get the table name), but the following variables can be used:
4367 </p>
4368 <dl>
4374 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4385 </dl>
4390 <p>
4391 By clicking on the button 'toggle scratchboard' on the page
4392 where you edit x/y coordinates of those elements you can activate a
4393 scratchboard where all your elements are placed. By clicking on an
4394 element, you can move them around in the pre-defined area and the x/y
4395 coordinates will get updated dynamically. Likewise, when entering a
4396 new position directly into the input field, the new position in the
4397 scratchboard changes after your cursor leaves the input field.
4398 </p>
4399 <p>
4400 You have to click on the 'OK'-button below the tables to save the new
4401 positions. If you want to place a new element, first add it to the
4402 table of elements and then you can drag the new element around.
4403 </p>
4404 <p>
4405 By changing the paper size and the orientation you can change the size
4406 of the scratchboard as well. You can do so by just changing the
4407 dropdown field below, and the scratchboard will resize automatically,
4408 without interfering with the current placement of the elements.
4409 </p>
4410 <p>
4411 If ever an element gets out of range you can either enlarge the paper
4412 size or click on the 'reset' button to place all elements below each
4413 other.
4414 </p>
4419 <p> Not every table can be put to the chart. Only tables with one, two or three columns can be visualised as a chart. Moreover the table must be in a special format for chart script to understand it. Currently supported formats can be found in the <a href="http://wiki.phpmyadmin.net/pma/Charts#Data_formats_for_query_results_chart">wiki</a>.</p>
4424 <p>
4425 An ESRI Shapefile is actually a set of several files, where .shp file contains
4426 geometry data and .dbf file contains data related to those geometry data.
4427 To read data from .dbf file you need to have PHP compiled with the dBase extension
4428 (--enable-dbase). Otherwise only geometry data will be imported.
4429 </p>
4432 <ul>
4433 <li>
4434 <p>
4435 Configure upload directory with
4437 .shp and .dbf files with the same filename and chose the .shp file from the import page.
4438 </p>
4439 </li>
4440 <li>
4441 <p>
4442 Create a Zip archive with .shp and .dbf files and import it. For this to work,
4445 </p>
4448 <pre>
4449 cd phpMyAdmin
4450 mkdir tmp
4451 chmod o+rwx tmp
4452 </pre>
4453 </li>
4454 </ul>
4460 <img src="themes/original/img/pmd/help_relation.png" width="100" height="100" alt="[relation icon]" /><br />
4461 The display column is shown in pink. To set/unset a column as the display column, click the "Choose column to display" icon, then click on the appropriate column name.</p>
4466 <p> The Zoom search feature is an alternative to table search feature. It allows you to explore
4467 a table by representing its data in a scatter plot. You can locate this feature by selecting
4468 a table and clicking the 'Search' tab. One of the sub-tabs in the 'Table Search' page is
4469 'Zoom Search'. <br/><br/>
4473 for example, id and town_code. The id values will be represented on one axis and town_code
4474 values on the other axis. Each row will be represented as a point in a scatter plot based
4475 on its id and town_code. You can include two additional search criteria apart from the two
4476 fields to display.<br/><br/>
4478 You can choose which field should be displayed as label for each point. If a display
4481 You can also select the maximum number of rows you want to be displayed in the plot by
4482 specifing it in the 'Max rows to plot' field. Once you have decided over your criteria,
4483 click 'Go' to display the plot.<br/><br/>
4485 After the plot is generated, you can use the mousewheel to zoom in and out of the plot.
4486 In addition, panning feature is enabled to navigate through the plot. You can zoom-in to
4487 a certail level of detail and use panning to locate your area of interest. Clicking on a
4488 point opens a dialogue box, displaying field values of the data row represented by the point.
4489 You can edit the values if required and click on submit to issue an update query. Basic
4490 instructions on how to use can be viewed by clicking the 'How to use?' link located just above
4491 the plot.</p>
4498 <p> Our Bug Tracker is located at
4500 under the Bugs section.<br /><br />
4502 But please first discuss your bug with other users:<br />
4504 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4505 </p>
4509 existing language, where do I start?</a></h4>
4511 <p> Translations are very welcome and all you need to have are the language skills.
4513 translation service</a>.
4514 You can check out all the possibilities to translate in the
4515 <a href="http://www.phpmyadmin.net/home_page/translate.php">translate section on our website</a>.
4516 </p>
4520 phpMyAdmin. How should I proceed?</a></h4>
4522 <p>We welcome every contribution to the development of phpMyAdmin.
4523 You can check out all the possibilities to contribute in the
4524 <a href="http://www.phpmyadmin.net/home_page/improve.php">contribute section on our website</a>.
4525 </p>
4530 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4532 <p> Please refer to
4533 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4534 </p>
4539 <p> If you use Apache web server, phpMyAdmin exports information about
4540 authentication to the Apache environment and it can be used in Apache logs.
4541 Currently there are two variables available:
4542 </p>
4543 <dl>
4545 <dd>User name of currently active user (he does not have to be logged
4546 in).</dd>
4553 </dl>
4554 <p>
4556 </p>
4557 <pre>
4560 </pre>
4561 <p>
4562 You can then use any log analyzing tools to detect possible break-in
4563 attempts.
4564 </p>
4570 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4571 It allows you to connect to local as well as remote servers. This requires you to enter
4572 server host name, username, password, port and the name of the database. Therefore you can
4573 now synchronize your databases placed on the same server or some remote server.
4574 </p>
4576 <p>
4577 This feature is helpful for developers who need to replicate their
4578 database’s structure as well as data. Moreover, this feature not only
4579 helps replication but also facilitates the user to keep his/her database
4580 in sync with another database. Other than the full database, certain
4581 tables of the databases can also be synchronized.
4582 </p>
4584 <p>
4585 You need to fill in the host name of the server, the username and
4586 password of an user account already there in MySQL. Port is by default
4587 populated with 3306 (MySQL default port). Then the name of the database
4588 should be mentioned at the end. All the information other than the port
4589 needs to be filled explicitly for the source as well as target servers.
4590 </p>
4592 <p>
4593 After successfully passing through the authentication phase, the source and
4594 target database table names will be displayed. It will be a tabular
4595 representation.
4596 </p>
4598 <p>
4599 On the left, are listed the source database table names. Some of the
4601 are only present in source database and they need to be added to the
4602 target database in order to synchronize the target database. The tables
4604 target database.
4605 </p>
4607 <p>
4608 On the right, are listed the target database table names. There are few
4610 means that these tables are to be created in target database in order to
4611 synchronize target database with source database. Some table names
4613 only present in target database and they will remain unchanged in the
4614 target database. The column in the middle shows the difference between
4615 the source and target corresponding tables.
4616 </p>
4618 <p>
4620 letters, indicating that either Structure or Data are not up to date. By
4621 clicking on them, they will turn grey, what means that they will be synchronized.
4622 </p>
4626 tables?</a></h4>
4628 <p>
4629 Yes. This aspect of synchronization is currently limited to small tables, and they
4630 must have a primary key.
4631 </p>
4633 <!-- DEVELOPERS -->
4636 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4637 great features have been written by other people and you too can help to
4638 make phpMyAdmin a useful tool.</p>
4640 <p>You can check out all the possibilities to contribute in the
4641 <a href="http://www.phpmyadmin.net/home_page/improve.php">contribute section on our website</a>.
4642 </p>
4646 <pre>
4657 </pre>
4659 <p>
4660 This program is free software; you can redistribute it and/or modify
4661 it under the terms of the GNU General Public License version 2,
4662 as published by the Free Software Foundation.
4663 </p>
4665 <p>
4666 This program is distributed in the hope that it will be useful,
4667 but WITHOUT ANY WARRANTY; without even the implied warranty of
4668 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4669 GNU General Public License for more details.
4670 </p>
4672 <p>
4673 You should have received a copy of the GNU General Public License
4674 along with this program. If not, see <a href="http://www.gnu.org/licenses/">http://www.gnu.org/licenses/</a>.
4675 </p>
4677 <!-- CREDITS -->
4682 <ul>
4685 <ul>
4688 </ul></li>
4691 <ul>
4696 </ul></li>
4699 <ul>
4704 </ul></li>
4707 <ul>
4709 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4710 generate XHTML1.0 and CSS2 compliant codes</li>
4713 </ul></li>
4716 <ul>
4724 </ul></li>
4727 <ul>
4732 </ul></li>
4735 <ul>
4738 </ul></li>
4741 <ul>
4743 </ul></li>
4746 <ul>
4749 </ul></li>
4752 <ul>
4756 </ul></li>
4759 <ul>
4762 </ul></li>
4765 <ul>
4772 </ul></li>
4775 <ul>
4779 </ul></li>
4782 <ul>
4788 </ul></li>
4791 (http://sf.net/projects/phpmysqlformgen/)
4792 <ul>
4794 </ul></li>
4797 <ul>
4799 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4804 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4808 </ul></li>
4811 <ul>
4813 </ul></li>
4816 <ul>
4818 </ul></li>
4821 <ul>
4823 </ul></li>
4826 <ul>
4827 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4828 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4829 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4830 </ul></li>
4833 <ul>
4835 </ul></li>
4838 <ul>
4840 </ul></li>
4843 <ul>
4845 </ul></li>
4848 <ul>
4851 </ul></li>
4853 <li>Nicola Asuni (Tecnick.com)
4854 <ul>
4857 </ul></li>
4860 <ul>
4863 </ul></li>
4866 <ul>
4868 </ul></li>
4871 <ul>
4874 </ul></li>
4876 <li>Ivan A Kirillov
4877 <ul>
4879 </ul></li>
4882 <ul>
4884 </ul></li>
4887 <ul>
4891 </ul></li>
4894 <ul>
4896 </ul></li>
4899 <ul>
4901 </ul></li>
4904 <ul>
4906 </ul></li>
4909 <ul>
4911 </ul></li>
4914 <ul>
4916 </ul></li>
4919 <ul>
4923 </ul></li>
4926 <ul>
4928 </ul></li>
4931 <ul>
4933 </ul></li>
4935 <li>Barrie Leslie
4936 <ul>
4938 </ul></li>
4941 <ul>
4943 </ul></li>
4946 <ul>
4949 </ul></li>
4951 </ul>
4953 <p>
4954 And also to the following people who have contributed minor changes,
4955 enhancements, bugfixes or support for a new language since version 2.1.0:
4956 </p>
4958 <p>
4959 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4960 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4961 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4962 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4964 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4965 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4966 Luís V., Martijn W. van der Lee,
4967 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4969 </p>
4974 <p>
4975 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4976 to create a web-based interface to MySQL using PHP3. Although I have not
4977 used any of his source-code, there are some concepts I've borrowed from
4978 him. phpMyAdmin was created because Peter told me he wasn't going to
4979 further develop his (great) tool.
4980 </p>
4981 <p>
4982 Thanks go to
4983 </p>
4984 <ul>
4986 code for the check when dropping a table or database. He also suggested
4987 that you should be able to specify the primary key on tbl_create.php3. To
4988 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4989 well as a bug-report. Plus many smaller improvements.
4990 </li>
4992 were introduced in 1.3.0 (including quite significant ones like the
4993 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4994 bug-fixes and help.
4995 </li>
4997 language-independent by outsourcing the strings to a separate file. He
4998 also contributed the French translation.
4999 </li>
5001 tbl_select.php3, a feature to display only some columns from a table.
5002 </li>
5004 functions in tbl_change.php3. He also added the
5006 </li>
5008 servers and is a regular contributor for bug-fixes.
5009 </li>
5011 features for 2.0.6.
5012 </li>
5013 </ul>
5014 <p>
5015 The following people have contributed minor changes, enhancements, bugfixes
5016 or support for a new language:
5017 </p>
5018 <p>
5019 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
5020 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
5021 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
5022 G. Wieggers.
5023 </p>
5024 <p>
5025 And thanks to everyone else who sent me email with suggestions, bug-reports
5026 and or just some feedback.
5027 </p>
5033 <ul>
5035 - the default name of Apache's directory-level configuration file.</li>
5039 - a software application that enables a user to display and interact with
5040 text, images, and other information typically located on a web page at a
5041 website on the World Wide Web.</li>
5043 - a free software/open source data compression algorithm and program
5044 developed by Julian Seward.</li>
5046 - an important World Wide Web technology that enables a client web browser
5047 to request data from a program executed on the Web server.</li>
5049 - a log or record of changes made to a project.</li>
5051 - a computer system that accesses a (remote) service on another computer
5052 by some kind of network.</li>
5054 - a set of data values of a particular simple type, one for each row of
5055 the table.</li>
5057 - a packet of information sent by a server to a World Wide Web browser
5058 and then sent back by the browser each time it accesses that server.</li>
5060 - Comma-separated values</li>
5063 - an organized collection of data.</li>
5066 - a PHP module that extends PHP with additional functionality.</li>
5068 - a list of commonly asked question and there answers.</li>
5070 - one part of divided data/columns.</li>
5072 - a column or group of columns in a database row that point to a key
5073 column or group of columns forming a key of another database row in some
5074 (usually different) table.</li>
5076 - the free PDF library</li>
5078 GD Graphics Library</a> - a library by Thomas Boutell and others for
5079 dynamically manipulating images.</li>
5082 - gzip is short for GNU zip, a GNU free software file compression
5083 program.</li>
5085 - any machine connected to a computer network, a node that has a hostname.</li>
5087 - the unique name by which a network attached device is known on a network.</li>
5089 (HyperText Transfer Protocol)</a>
5090 - the primary method used to transfer or convey information on the World
5091 Wide Web.</li>
5094 additional security measures.</li>
5095 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5096 - a set of Internet-based services for servers using Microsoft Windows.</li>
5098 - a feature that allows quick access to the rows in a table.</li>
5100 - a data-oriented protocol used by source and destination hosts for
5101 communicating data across a packet-switched internetwork.</li>
5103 - a unique number that devices use in order to identify and communicate
5104 with each other on a network utilizing the Internet Protocol standard.</li>
5106 (Internet Server Application Programming Interface)</a>
5107 - the API of Internet Information Services (IIS).</li>
5109 - a business or organization that offers users access to the Internet and related services.</li>
5111 - a most commonly used standard method of lossy compression for
5112 photographic images.</li>
5118 - line of personal computers is designed, developed, manufactured, and
5119 marketed by Apple Computer.</li>
5120 <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>
5121 - the operating system which is included with all currently shipping Apple
5122 Macintosh computers in the consumer and professional markets.</li>
5124 - a cryptographic library.</li>
5126 - the MCrypt PHP extension.</li>
5127 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5128 - an Internet Standard for the format of e-mail.</li>
5130 - some sort of extension for the Apache Webserver.</li>
5132 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5133 Management System (DBMS).</li>
5135 - the improved MySQL client PHP extension.</li>
5137 - the MySQL client PHP extension.</li>
5139 - open standard for office documents.</li>
5140 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5141 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5143 (Portable Document Format)</a>
5144 - a file format developed by Adobe Systems for representing two
5145 dimensional documents in a device independent and resolution independent
5146 format.</li>
5148 - the PHP Extension and Application Repository.</li>
5150 - the perl-compatible regular expression functions for PHP</li>
5152 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5153 programming language used mainly for developing server-side applications
5154 and dynamic web content, and more recently, a broader range of software
5155 applications.</li>
5157 - a connection through which data is sent and received.</li>
5159 - Request for Comments (RFC) documents are a series of memoranda
5160 encompassing new research, innovations, and methodologies applicable to
5161 Internet technologies.</li>
5165 - represents a single, implicitly structured data item in a table.</li>
5167 - a computer system that provides services to other computing
5168 systems over a network.</li>
5169 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5170 - handlers for different table types</li>
5172 - a form of inter-process communication.</li>
5174 Sockets Layer)</a>
5175 - a cryptographic protocol which provides secure communication on the Internet.</li>
5177 - a subroutine available to applications accessing a relational database system</li>
5179 - Structured Query Language</li>
5181 - a set of data elements (cells) that is organized, defined and stored as
5182 horizontal rows and vertical columns where each item can be uniquely
5183 identified by a label or key or by it?s position in relation to other items.</li>
5186 - a type of archive file format: the Tape ARchive format.</li>
5188 - one of the core protocols of the Internet protocol suite.</li>
5190 - a procedural code that is automatically executed in response to
5191 certain events on a particular table or view in a database</li>
5195 - a sequence of characters, conforming to a standardized format, that is
5196 used for referring to resources, such as documents and images on the
5197 Internet, by their location.</li>
5199 - A computer (program) that is responsible for accepting HTTP requests
5200 from clients and serving them Web pages.</li>
5202 - a W3C-recommended general-purpose markup language for creating
5203 special-purpose markup languages, capable of describing many different
5204 kinds of data.</li>
5206 - a popular data compression and archival format.</li>
5208 - an open-source, cross-platform data compression library by Jean-loup
5209 Gailly and Mark Adler.</li>
5210 </ul>
5211 </div>
5214 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5217 <li class="last">Valid <a href="http://validator.w3.org/check/referer">HTML</a> and <a href="http://jigsaw.w3.org/css-validator/check/referer">CSS</a></li>
5218 </ul>
5220 </body>
5221 </html>