| blob | 62dd51fcc030586efaa78421f3470b58446f5bf4 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.4.0-dev
22 Documentation
23 </h1>
24 </div>
26 <!-- TOP MENU -->
35 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
41 </ul>
46 phpMyAdmin homepage</a></li>
48 SourceForge phpMyAdmin project page</a></li>
50 Official phpMyAdmin wiki</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
58 </li>
59 </ul>
61 <!-- REQUIREMENTS -->
68 and the Standard PHP Library (SPL) extension.
69 </li>
72 currently the default), you should install the mbstring and ctype
73 extensions.
74 </li>
75 <li>You need GD2 support in PHP to display inline
77 original aspect ratio</li>
83 load pages significantly slower.
84 </li>
87 <li>To support BLOB streaming, see PHP and MySQL requirements
90 </ul>
91 </li>
94 </ul>
96 <!-- INTRODUCTION -->
99 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
100 a single database. To accomplish the latter you'll need a properly set up
101 MySQL user who can read/write only the desired database. It's up to you to
102 look up the appropriate part in the MySQL manual.
103 </p>
108 <li>create, copy, drop, rename and alter databases, tables, columns and
109 indexes</li>
110 <li>maintenance server, databases and tables, with proposals on server
111 configuration</li>
112 <li>execute, edit and bookmark any
114 batch-queries</li>
117 </li>
124 OpenDocument Text and Spreadsheet,
126 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
127 </li>
128 <li>import data and MySQL structures from <abbr title="Microsoft Excel 97-2003 and Excel 2007">Microsoft Excel</abbr> and 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>
132 <li>using Query-by-example (QBE), create complex queries automatically
133 connecting required tables</li>
135 your Database layout</li>
137 <li>transform stored data into any format using a set of predefined
138 functions, like displaying BLOB-data as image or download-link
139 </li>
146 </li>
147 <li>synchronize two databases residing on the same as well as remote servers
149 </li>
151 </ul>
154 <p> Many people have difficulty
155 understanding the concept of user management with regards to phpMyAdmin. When
156 a user logs in to phpMyAdmin, that username and password are passed directly
157 to MySQL. phpMyAdmin does no account management on its own (other than
158 allowing one to manipulate the MySQL user account information); all users
159 must be valid MySQL users.</p>
168 <!-- INSTALLATION -->
176 </ol>
179 phpMyAdmin does not apply any special security methods to the MySQL database
180 server. It is still the system administrator's job to grant permissions on
182 be used for this.
183 </p>
191 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
192 before uploading them to your server, as PHP seems not to like
197 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
198 Downloads page. Some kits contain only the English messages,
199 others contain all languages in UTF-8 format (this should be fine
200 in most situations), others contain all
201 languages and all character sets. We'll assume you chose a kit whose
203 </li>
204 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
206 document root. If you don't have direct access to your document root,
207 put the files in a directory on your local machine, and, after step 4,
208 transfer the directory on your web server using, for example, ftp.</li>
209 <li>Ensure that all the scripts have the appropriate owner (if PHP is
210 running in safe mode, having some scripts with an owner different
211 from the owner of other scripts will be a
216 <li>Now you must configure your installation. There are two methods that
217 can be used. Traditionally, users have hand-edited a copy of
219 provided for those who prefer a graphical installation. Creating a
220 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
221 <ul><li>To manually create the file, simply use your text editor to
224 file) in the main (top-level) phpMyAdmin directory (the one
228 default value is okay for a particular setting, there is no
230 few directives to get going, a simple configuration may look
231 like this:
232 <pre>
233 <?php
234 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
236 $i=0;
237 $i++;
238 $cfg['Servers'][$i]['auth_type'] = 'cookie';
239 ?>
240 </pre>
241 Or, if you prefer to not be prompted every time you log in:
242 <pre>
243 <?php
245 $i=0;
246 $i++;
247 $cfg['Servers'][$i]['user'] = 'root';
248 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
249 $cfg['Servers'][$i]['auth_type'] = 'config';
250 ?>
251 </pre>
252 For a full explanation of possible configuration values, see the
258 directory. This is a security measure. On a Linux/Unix system you
259 can use the following commands:
260 <pre>
261 cd phpMyAdmin
262 mkdir config # create directory for saving
263 chmod o+rw config # give it world writable permissions
264 </pre>
265 And to edit an existing configuration, copy it over first:
266 <pre>
267 cp config.inc.php config/ # copy current configuration for editing
268 chmod o+w config/config.inc.php # give it world writable permissions
269 </pre>
270 On other platforms, simply create the folder and ensure that your
279 the webserver does not have the proper permissions you may see the
281 config/</tt> directory exists and has the proper permissions -
283 and upload (via FTP or some similar means) to the proper location.<br /><br />
285 Once the file has been saved, it must be moved out of the <tt>
286 config/</tt> directory and the permissions must be reset, again
287 as a security measure:
288 <pre>
289 mv config/config.inc.php . # move file to current directory
290 chmod o-rw config.inc.php # remove world read and write permissions
291 rm -rf config # remove not needed directory
292 </pre>
293 Now the file is ready to be used. You can choose to review or edit
294 the file with your favorite editor, if you prefer to set some
295 advanced options which the setup script does not provide.</li></ul></li>
296 <li>If you are using the
298 protect the phpMyAdmin installation directory because using
299 config does not require a user to
300 enter a password to access the phpMyAdmin installation. Use of an alternate
301 authentication method is recommended, for example with
309 in your browser. phpMyAdmin should now display a welcome screen
310 and your databases, or a login dialog if using
312 authentication mode.</li>
315 Apache you can use supplied .htaccess file in that folder, for other
316 webservers, you should configure this yourself. Such configuration
317 prevents from possible path exposure and cross side scripting
318 vulnerabilities that might happen to be found in that code.</li>
319 <li>
320 It is generally good idea to protect public phpMyAdmin installation
321 against access by robots as they usually can not do anything good
323 your webserver or limit access by web server configuration. You can
326 </li>
327 </ol>
331 <p> For a whole set of new features (bookmarks, comments,
333 tracking mechanism,
335 transformation, etc.) you need to create a set of special tables. Those
336 tables can be located in your own database, or in a central database for a
337 multi-user installation (this database would then be accessed by the
338 controluser, so no other user should have rights to it).</p>
349 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
350 that you may need special (administrator) privileges to create the database
351 and tables, and that the script may need some tuning, depending on the
352 database name.</p>
357 section</a>. You will also need to have a controluser with the proper rights
364 unpacked one. Configuration files from old versions may
365 require some tweaking as some options have been changed or removed; in
367 so you better remove it from your file and just use the default one.
369 statement that you might find near the end of your configuration file.</p>
373 is version-specific.</p>
376 version 4.1.2 or newer and if you use the phpMyAdmin configuration storage,
377 you should run the SQL script found in
384 where you want to give users access to their own database and don't want
385 them to play around with others.<br />
386 Nevertheless be aware that MS Internet Explorer seems to be really buggy
388 in this area!<br />
391 that your user/password pair are not in clear in the configuration file.
392 </li>
395 authentication modes are more secure: the MySQL login information does
396 not need to be set in the phpMyAdmin configuration file (except possibly
398 However, keep in mind that the password travels in plain text, unless
399 you are using the HTTPS protocol.<br />
400 In cookie mode, the password is stored, encrypted with the blowfish
401 algorithm, in a temporary cookie.</li>
413 file under the
415 $cfg['Servers'][$i]['controluser']</a></tt> and
420 only an example: use something else in your file!</b> Input these
421 statements from the phpMyAdmin SQL Query window or mysql command–line
422 client.<br />
424 if it's not the same as the MySQL server's one.
426 <pre>
427 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
428 GRANT SELECT (
429 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
430 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
431 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
432 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
433 Execute_priv, Repl_slave_priv, Repl_client_priv
434 ) ON mysql.user TO 'pma'@'localhost';
435 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
436 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
437 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
438 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
440 If you want to use the many new relation and bookmark features:
442 <pre>
444 </pre>
447 configuration storage</a> be set up).
448 <br /></li>
451 on a set of particular databases. Normally you shouldn't give global
452 privileges to an ordinary user, unless you understand the impact of those
453 privileges (for example, you are creating a superuser).<br />
457 <pre>
458 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
459 </pre>
461 What the user may now do is controlled entirely by the MySQL user
462 management system.<br />
464 authentication mode, you don't need to fill the user/password fields
466 array.</li>
467 </ul>
472 method and allows you to log in as any valid MySQL user.</li>
473 <li>Is supported with most PHP configurations. For
486 mode.</li>
487 </ul>
491 <ul><li>You can use this method as a replacement for the
493 (for example, if you're running
495 <li>Obviously, the user must enable cookies in the browser, but this is
496 now a requirement for all authentication modes.</li>
497 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
498 with the same username.</li>
499 <li>If you want to log in to arbitrary server see
504 not required.</li>
505 </ul>
509 <ul><li>This mode is a convenient way of using credentials from another
510 application to authenticate to phpMyAdmin.</li>
511 <li>The other application has to store login information into
512 session data.</li>
514 section.</li>
515 </ul>
518 <ul><li>This mode is the less secure one because it requires you to fill the
520 $cfg['Servers'][$i]['user']</a> and
522 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
523 can read your config.inc.php can discover your username and password).
524 <br />
531 is an entry explaining how to protect your configuration file.</li>
532 <li>For additional security in this mode, you may wish to consider the Host
533 authentication
535 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
537 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
538 directives.</li>
539 <li>Unlike cookie and http, does not require a user to log in when first
540 loading the phpMyAdmin site. This is by design but could allow any
541 user to access your installation. Use of some restriction method is
543 HTTP-AUTH directive or disallowing incoming HTTP requests at
544 one’s router or firewall will suffice (both of which
545 are beyond the scope of this manual but easily searchable with Google).</li>
546 </ul>
548 <p>
549 The Swekey is a low cost authentication USB key that can be used in
550 web applications.<br /><br />
551 When Swekey authentication is activated, phpMyAdmin requires the
552 users's Swekey to be plugged before entering the login page (currently
553 supported for cookie authentication mode only). Swekey Authentication is
554 disabled by default.<br /><br />
556 </p>
557 <pre>
558 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
559 </pre>
560 <p>
562 each user with their Swekey Id. It is important to place this file outside
563 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
565 users' information.<br /><br />
566 If you want to purchase a Swekey please visit
568 since this link provides funding for phpMyAdmin.
569 </p>
570 <!-- CONFIGURATION -->
574 users:</span> PHP does not seem to like
578 before saving a script you have modified.</p>
583 section to create one. This file only needs to contain the parameters you want to
584 change from their corresponding default value in
587 <p> The parameters which relate to design (like colors) are placed in
590 your site specific code to be included on start and end of each page.</p>
594 (with full path) to your phpMyAdmin installation's directory.
597 some web servers are case–sensitive.
600 Starting with version 2.3.0, it is advisable to try leaving this
601 blank. In most cases phpMyAdmin automatically detects the proper
602 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
603 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
604 A good test is to browse a table, edit a row and save it. There should
605 be an error message if phpMyAdmin is having trouble auto–detecting
606 the correct value. If you get an error that this must be set or if
607 the autodetect code fails to detect your path, please post a bug
608 report on our bug tracker so we can improve the code.</dd>
612 with master / foreign – tables (see
614 <br />
615 If you tried to set this up and it does not work for you, have a look on
617 use it. You will find a link that will analyze why those features have
618 been disabled.<br />
619 If you do not want to use those features set this variable to
623 <dd>A warning is displayed on the main page if Suhosin is detected.
625 from appearing.</dd>
628 <dd>Disable the default warning that is displayed if mcrypt is missing for
629 cookie authentication.
631 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. This is the recommended and default
704 method at this time.<br /><br />
707 The improved MySQL extension. This extension became available
708 with php 5.0.0 and is the recommended way to connect to a server
712 <dd>Whether to use a compressed protocol for the MySQL server connection
713 or not (experimental).<br />
719 </dt>
721 all relational features (see
723 and, for a MySQL server running with
726 authentication mode).<br /><br />
729 cookie authentication modes (or 'config'
730 authentication mode since phpMyAdmin 2.2.1), you need to supply the
735 This account is used to check what databases the user will see at
736 login.<br />
740 In phpMyAdmin versions before 2.2.5, those were called
744 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
745 <dd>Whether config or cookie or
747 should be used for this server.
749 is the plain old way: username and password are stored in
751 <li>'cookie' authentication mode
753 2.2.3 allows you to log in as any valid MySQL user with the
754 help of cookies. Username and password are stored in
755 cookies during the session and password is deleted when it
756 ends. This can also allow you to log in in arbitrary server if
757 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
758 </li>
759 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
760 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
761 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
762 <li>'signon' authentication mode
764 as introduced in 2.10.0 allows you to log in from prepared PHP
765 session data. This is useful for implementing single signon
766 from another application. Sample way how to seed session is in
772 </ul>
775 for more information.
776 </dd>
778 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
779 </dt>
780 <dd>
781 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
782 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
783 specified in your configuration, a string combined of "phpMyAdmin " and either
786 </dd>
788 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
789 </dt>
790 <dd>
792 names for hardware authentication. Leave empty to deactivate this feature.
793 </dd>
797 </dt>
798 <dd>
799 When using auth_type = 'config', this is the user/password-pair
800 which phpMyAdmin will use to connect to the
801 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
802 cookie authentication is used and should be empty.</dd>
804 <span
806 </dt>
807 <dd>
808 Allow attempt to log in without password when a login with password
809 fails. This can be used together with http authentication, when
810 authentication is done some other way and phpMyAdmin gets user name
811 from auth and uses empty password for connecting to MySQL. Password
812 login is still tried first, but as fallback, no password method is
813 tried.</dd>
816 </dt>
817 <dd>
818 If set to a (an array of) database name(s), only this (these) database(s)
819 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
820 database(s) name(s) may contain MySQL wildcards characters
824 This setting is an efficient way to lower the server load since the
825 latter does not need to send MySQL requests to build the available
827 privileges rules of the MySQL database server</span>. If set, it just
828 means only these databases will be displayed but
830 <br /><br />
832 An example of using more that one database:
834 <br /><br />
836 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
837 databases in the left frame, so that you can individually arrange your databases.<br />
838 If you want to have certain databases at the top, but don't care about the others, you do not
839 need to specify all other databases. Use:
841 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
842 order.</dd>
845 </dt>
846 <dd>Regular expression for hiding some databases. This only hides them
847 from listing, but a user is still able to access them (using, for example,
848 the SQL query area). To limit access, use the MySQL privilege system.
849 <br /><br />
854 More information on regular expressions can be found in the
856 PCRE pattern syntax</a> portion of the PHP reference manual.
857 </dd>
860 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
861 this string will be displayed instead of the hostname in the pull-down
862 menu on the main page. This can be useful if you want to show only
863 certain databases on your system, for example. For HTTP auth, all
864 non-US-ASCII characters will be stripped.</dd>
868 </dt>
869 <dd>The name of the database containing the phpMyAdmin configuration storage.
870 <br /><br />
873 section in this document to see the benefits of this feature,
874 and for a quick way of creating this database and the needed tables.
875 <br /><br />
877 If you are the only user of this phpMyAdmin installation, you can
878 use your current database to store those special tables; in this
879 case, just put your current database name in
881 set this parameter to the name of your central database containing
882 the phpMyAdmin configuration storage.</dd>
886 </dt>
888 useful for queries you often run.<br /><br />
890 To allow the usage of this functionality:
892 <li>enter the table name in
894 </ul>
895 </dd>
899 </dt>
901 which column is a key in another table (a foreign key). phpMyAdmin
902 currently uses this to
903 <ul><li>make clickable, when you browse the master table, the data values
904 that point to the foreign table;</li>
906 when browsing the master table, if you move the mouse to a column
907 containing a foreign key (use also the 'table_info' table);<br />
910 <li>in edit/insert mode, display a drop-down list of possible foreign
914 <li>display links on the table properties page, to check referential
915 integrity (display missing foreign keys) for each described key;
916 </li>
920 schema of your database (also uses the table_coords table).</li>
921 </ul>
923 The keys can be numeric or character.<br /><br />
925 To allow the usage of this functionality:
928 configuration storage</li>
929 <li>put the relation table name in
931 <li>now as normal user open phpMyAdmin and for each one of your
932 tables where you want to use this feature, click
934 columns.
935 </li>
936 </ul>
940 future development of the cross-db relations.
941 </dd>
945 </dt>
946 <dd>
947 Since release 2.3.0 you can describe, in a special 'table_info'
948 table, which column is to be displayed as a tool-tip when moving the
949 cursor over the corresponding key.<br />
950 This configuration variable will hold the name of this special
951 table. To allow the usage of this functionality:
953 <li>put the table name in
955 'pma_table_info')</li>
956 <li>then for each table where you want to use this feature,
958 to choose the column.</li>
959 </ul>
961 </dd>
965 </dt>
968 the relations between your tables. To do this it needs two tables
973 schema output).<br /><br />
977 To allow the usage of this functionality:
980 <li>put the correct table names in
983 </ul>
986 </dd>
990 </dt>
992 Since release 2.3.0 you can store comments to describe each column for
994 <br /><br />
996 Starting with release 2.5.0, comments are consequently used on the table
997 property pages and table browse view, showing up as tool-tips above the
998 column name (properties page) or embedded within the header of table in
999 browse view. They can also be shown in a table dump. Please see the
1000 relevant configuration directives later on.<br /><br />
1002 Also new in release 2.5.0 is a MIME-transformation system which is also
1004 Transformations</a> for further information. To use the
1005 MIME-transformation system, your column_info table has to have the three
1006 new columns 'mimetype', 'transformation', 'transformation_options'.
1007 <br /><br />
1009 To allow the usage of this functionality:
1011 <li>put the table name in
1013 'pma_column_info')</li>
1016 <pre>
1017 ALTER TABLE `pma_column_comments`
1018 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1019 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1020 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1021 </pre>
1024 renamed from<br />
1027 </ul>
1028 </dd>
1032 </dt>
1035 all queries you entered manually into the phpMyAdmin interface. If you
1036 don't want to use a table-based history, you can use the JavaScript-based
1037 history. Using that, all your history items are deleted when closing the
1038 window.<br /><br />
1040 Using
1042 you can specify an amount of history items you want to have on hold. On
1043 every login, this list gets cut to the maximum amount.<br /><br />
1045 The query history is only available if JavaScript is enabled in your
1046 browser.<br /><br />
1048 To allow the usage of this functionality:
1052 (e.g. 'pma_history')
1053 </li>
1054 </ul>
1055 </dd>
1059 </dt>
1060 <dd>
1061 Since release 3.3.x a tracking mechanism is available.
1063 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1064 and data definition statements. After enabling it you can create versions of tables.
1065 <br/><br/>
1066 The creation of a version has two effects:
1068 <ul>
1070 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1071 </ul>
1073 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1074 For the report you can use filters, for example you can get a list of statements within a date range.
1075 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1076 In addition you can export the (filtered) report to a file or to a temporary database.
1077 <br/><br/>
1079 To allow the usage of this functionality:
1081 <ul>
1084 </ul>
1085 </dd>
1088 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1089 </dt>
1090 <dd>
1091 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1092 <br/><br/>
1093 If this is set to true and you create a table or view with
1095 <ul>
1098 </ul>
1100 and no version exists for it, the mechanism will
1101 create a version for you automatically.
1102 </dd>
1105 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1106 </dt>
1107 <dd>
1108 Defines the list of statements the auto-creation uses for new versions. Default value is
1109 <br/>
1111 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1112 CREATE INDEX,DROP INDEX,
1113 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1114 CREATE VIEW,ALTER VIEW,DROP VIEW,
1115 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1116 </dd>
1119 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1120 </dt>
1121 <dd>
1122 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1123 <br/><br/>
1124 </dd>
1128 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1129 </dt>
1130 <dd>
1131 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1132 <br/><br/>
1133 </dd>
1136 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1137 </dt>
1138 <dd>
1139 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1140 <br/><br/>
1141 </dd>
1146 </dt>
1148 to visually manage the relations.
1149 <br /><br />
1151 To allow the usage of this functionality:
1154 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1155 </li>
1156 </ul>
1157 </dd>
1160 </dt>
1162 column_info table got enhanced with three new columns. If the above variable
1164 latest table structure available. If not, it will emit a warning to the
1165 superuser.<br /><br />
1167 You can disable this checking behavior by setting the variable to false,
1168 which should offer a performance increase.<br /><br />
1170 Recommended to set to FALSE, when you are sure, your table structure is
1171 up to date.</dd>
1173 boolean</dt>
1174 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1175 </dd>
1177 boolean</dt>
1178 <dd>Whether to allow logins without a password. The default
1180 to a MySQL server with was left with an empty password for root or
1181 on which an anonymous (blank) user is defined.
1182 </dd>
1185 </dt>
1187 authentication is disabled.<br /><br />
1190 all deny rules followed by allow rules. Access is allowed by default. Any
1191 client which does not match a Deny command or does match an Allow command
1192 will be allowed access to the server. <br /><br />
1195 applies all allow rules followed by deny rules. Access is denied by
1196 default. Any client which does not match an Allow directive or does
1197 match a Deny directive will be denied access to the server.<br /><br />
1199 If your rule order is set to 'explicit', the authentication is
1200 performed in a similar fashion to rule order 'deny,allow', with the
1204 and was available in Apache by specifying allow and deny rules without
1205 setting any order.<br /><br />
1207 Please also see <a
1209 address behind proxies.
1210 </dd>
1212 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1213 </dt>
1214 <dd>The general format for the rules is as such:
1216 <pre>
1218 </pre>
1223 well (please note that those containing SERVER_ADDRESS might not be
1224 available on all webservers):
1225 <pre>
1231 </pre>
1233 Having an empty rule list is equivalent to either using
1239 following work:<br />
1241 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1242 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1243 But the following does not work:<br />
1246 Also IPv6 addresses are not supported.
1247 </dd>
1249 <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.
1250 </dd>
1251 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1253 DATABASES</tt> command used to fetch the name of available databases will
1254 probably be too slow, so it can be replaced by faster commands (see
1256 </dd>
1258 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1259 </dd>
1260 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1261 <dd>Name of session which will be used for signon authentication method.
1262 </dd>
1264 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1265 </dd>
1267 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1268 </dd>
1271 <dd>If you have more than one server configured, you can set
1273 that server when phpMyAdmin is started, or set it to 0 to be given a
1274 list of servers without logging in.<br />
1276 MUST be set to that server.</dd>
1279 <dd>The maximum number of database names to be displayed in the
1280 navigation frame and the database list.</dd>
1283 <dd>The maximum number of table names to be displayed in the
1284 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1285 when in Light mode.</dd>
1288 <dd>The maximum number of characters when a SQL query is displayed. The
1289 default limit of 1000 should be correct to avoid the display of tons
1290 of hexadecimal codes that represent BLOBs, but some users have real
1291 SQL queries that are longer than 1000 characters. Also, if a query's
1292 length exceeds this limit, this query is not saved in the history.</dd>
1295 <dd>Defines whether to use GZip output buffering for increased
1297 Set to true/false for enabling/disabling. When set to 'auto' (string),
1298 phpMyAdmin tries to enable output buffering and will automatically disable
1299 it if your browser has some problems with buffering. IE6 with a certain patch
1300 is known to cause data corruption when having enabled buffering.</dd>
1303 <dd>Whether persistent connections should be used or not (mysql_connect or
1304 mysql_pconnect).</dd>
1310 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1311 to zero, no time limit is imposed.<br />
1312 This setting is used while importing/exporting dump files and in the
1313 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1320 <dd>Set the number of bytes a script is allowed to allocate. If set
1321 to zero, no limit is imposed.<br />
1322 This setting is used while importing/exporting dump files and at some
1323 other places in phpMyAdmin so you definitely don't want to put here
1324 a too low value. It has no effect when PHP is running in safe mode.<br />
1325 You can also use any string as in php.ini, eg. '16M'. Ensure
1329 <dd>Mark used tables and make it possible to show databases with locked
1334 generated by phpMyAdmin should be displayed or not.</dd>
1337 <dd>Defines whether normal users (non-administrator) are allowed to
1338 delete their own database or not. If set as FALSE, the link "Drop
1340 mydatabase" will be rejected. Quite practical for
1342 customers.<br />
1343 Please note that this limitation of SQL queries is not as strict as
1344 when using MySQL privileges. This is due to nature of SQL queries
1345 which might be quite complicated. So this choice should be viewed as
1346 help to avoid accidental dropping rather than strict privilege
1347 limitation.</dd>
1351 displayed when you're about to lose data.</dd>
1354 <dd>Define whether the previous login should be recalled or not in cookie
1355 authentication mode.<br /><br />
1357 This is automatically disabled if you do not have configured
1359 </dd>
1362 <dd>Define how long is login cookie valid. Please note that php
1363 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1364 might limit session validity and if session is lost, login cookie is
1366 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1370 means that it will be kept for existing session. This is recommended
1371 for not trusted environments.</dd>
1374 <dd>If enabled (default), logout deletes cookies for all servers,
1375 otherwise only for current one. Setting this to false makes it easy to
1376 forget to log out from other server, when you are using more of
1377 them.</dd>
1383 <dd>Define whether phpMyAdmin will continue executing a multi-query
1384 statement if one of the queries fails. Default is to abort execution.</dd>
1387 <dd>Define whether phpMyAdmin will output the results of each query of a
1388 multi-query statement embedded into the
1393 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1394 <br /><br />
1397 MySQL servers behind the firewall where your
1399 </dd>
1408 <dd>Defines whether to use a select-based menu and display only the current
1409 tables in the left frame (smaller page). Only in Non-Lightmode you can
1410 use the feature to display nested folders using
1412 </dd>
1415 <dd>In light mode, defines whether to display the names of databases (in the
1416 selector) using a tree, see also
1418 </dd>
1421 string or array</dt>
1422 <dd>The string used to separate the parts of the database name when showing
1423 them in a tree. Alternatively you can specify more strings in an array
1424 and all of them will be used as a separator.</dd>
1427 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1428 This means if you have tables like 'first__second__third' this will be
1430 If set to FALSE or empty, the feature is disabled. NOTE: You should
1431 not use this separator at the beginning or end of a
1432 table name or multiple times after another without any other
1433 characters in between.</dd>
1436 <dd>Defines how many sublevels should be displayed when splitting
1437 up tables by the above separator.</dd>
1440 <dd>Defines whether to display table comment as tool-tip in left frame or
1441 not.</dd>
1444 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1445 comment and the real name. That means that if you have a table called
1446 'user0001' and add the comment 'MyName' on it, you will see the name
1447 'MyName' used consequently in the left frame and the tool-tip shows
1448 the real name of the DB.</dd>
1451 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1453 When setting this to 'nested', the Alias of the Tablename is only used
1454 to split/nest the tables according to the
1456 directive. So only the folder is called like the Alias, the tablename itself
1457 stays the real tablename.</dd>
1460 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1463 <dd>Enter URL where logo in the navigation frame will point to.
1464 For use especially with self made theme which changes this.
1473 <dd>Defines whether or not to display a server choice at the top of the left frame.
1474 Defaults to FALSE.</dd>
1476 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1477 Defaults to FALSE (drop-down).</dd>
1479 <dd>Defines whether to display database choice in light navigation frame as links
1480 instead of in a drop-down. Defaults to 'auto' - on main page list is
1481 shown, when database is selected, only drop down is displayed.</dd>
1484 <dd>Defines the tab displayed by default when clicking the small
1485 icon next to each table name in the navigation panel. Possible
1491 <dd>Defines whether or not to display space usage and statistics about databases
1492 and tables.<br />
1493 Note that statistics requires at least MySQL 3.23.3 and that, at this
1494 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1497 <dd>Defines whether to display detailed server information on main page.
1498 You can additionally hide more information by using
1500 </dd>
1505 </dt>
1508 not at the starting main (right) frame. This setting
1509 does not check MySQL commands entered directly.<br /><br />
1511 Please note that to block the usage of phpinfo() in scripts, you
1518 hard coded password value in the configuration file, end users can't
1519 be allowed to change their passwords.</dd>
1522 <dd>Defines whether to suggest a database name on the
1526 <dd>Defines whether navigation bar buttons and the right panel top menu
1527 contain text or symbols only. A value of TRUE displays icons, FALSE
1528 displays text and 'both' displays both icons and text.</dd>
1531 <dd>Defines whether a user should be displayed a
1535 <dd>Number of rows displayed when browsing a result set. If the result set
1542 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1546 option is ticked by default.</dd>
1550 from editing when browsing a table's content. Valid values are:
1555 </ul>
1556 </dd>
1559 <dd>Defines whether or not MySQL functions fields should be initially
1560 displayed in edit/insert mode. Since version 2.10, the user can
1561 toggle this setting from the interface.
1562 </dd>
1565 <dd>Defines whether or not type fields should be initially
1566 displayed in edit/insert mode. The user can
1567 toggle this setting from the interface.
1568 </dd>
1571 <dd>Defines which type of editing controls should be used for CHAR and
1572 VARCHAR columns. Possible values are:
1573 <ul><li>input - this allows to limit size of text to size of columns in
1574 MySQL, but has problems with newlines in columns</li>
1575 <li>textarea - no problems with newlines in columns, but also no
1576 length limitations</li>
1577 </ul>
1578 Default is old behavior so input.</dd>
1584 <dd>If there are fewer items than this in the set of foreign keys, then a
1585 drop-down box of foreign keys is presented, in the style described by the
1587 setting.</dd>
1590 <dd>For the foreign key drop-down fields, there are several methods of
1591 display, offering both the key and value data. The contents of the
1592 array should be one or both of the following strings:
1598 </dt>
1599 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1600 creating a dump file</dd>
1603 </dt>
1604 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1605 compressed exports. This doesn't affect smaller dumps and allows users to
1606 create larger dumps that won't otherwise fit in memory due to php
1607 memory limit. Produced files contain more GZip/BZip2 headers, but all
1608 normal programs handle this correctly.</dd>
1612 mainframe.</dd>
1616 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1621 <dd>How many columns will be utilized to display the tables on the
1622 database property view? Default is 1 column. When setting this to a
1623 value larger than 1, the type of the database will be omitted for more
1624 display space.</dd>
1628 <dd>Defines the tab displayed by default on server view. Possible
1635 <dd>Defines the tab displayed by default on database view. Possible
1640 <dd>Defines the tab displayed by default on table view. Possible
1647 points to the MySQL documentation (type depends
1648 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1649 generated.<br />
1651 for more information about MySQL manuals and their types.</dd>
1654 <dd>Type of MySQL documentation:
1660 </ul>
1661 </dd>
1664 <dd>Defines the default language to use, if not browser-defined or
1665 user-defined.<br />
1666 The corresponding language file needs to be in
1668 </dd>
1671 <dd>Defines the default connection collation to use, if not
1672 user-defined.<br />
1678 The corresponding language file needs to be in
1680 </dd>
1683 <dd>Limit list of available languages to those matching the given regular
1684 expression. For example if you want only Czech and English, you should
1688 <dd>You can select here which functions will be used for character set
1689 conversion. Possible values are:
1690 <ul><li>auto - automatically use available one (first is tested
1691 iconv, then recode)</li>
1695 </ul>
1696 Default is auto.</dd>
1697 <dd>
1698 Enabled charset conversion activates a pull-down menu
1699 in the Export and Import pages, to choose the character set when
1700 exporting a file. The default value in this menu comes from
1702 </dd>
1705 <dd>Specify some parameters for iconv used in charset conversion. See
1708 used, so that invalid characters will be transliterated.</dd>
1711 <dd>Available character sets for MySQL conversion. You can add your own (any of
1712 supported by recode/iconv) or remove these which you don't use.
1713 Character sets will be shown in same order as here listed, so if you
1714 frequently use some of these move them to the top.</dd>
1719 default empty, you need to fill in some trusted proxy servers if you
1720 want to use rules for IP addresses behind proxy.<br /><br />
1722 The following example specifies that phpMyAdmin should trust a
1724 <pre>
1725 $cfg['TrustedProxies'] =
1727 </pre>
1728 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1729 client's IP address as usual.
1730 </dd>
1734 MIME transformations.<br />
1735 Possible values are:
1736 <ul><li>auto - automatically detect, this is a bit expensive
1738 according to your server real possibilities</li>
1741 </ul>
1742 Default is auto.
1743 </dd>
1746 <dd>
1747 We normally check the permissions on the configuration file to ensure
1748 it's not world writable. However, phpMyAdmin could be installed on
1749 a NTFS filesystem mounted on a non-Windows server, in which case the
1750 permissions seems wrong but in fact cannot be detected. In this case
1752 </dd>
1755 <dd>
1756 Limit for length of URL in links. When length would be above this limit, it
1757 is replaced by form with button.
1758 This is required as some web servers (IIS) have problems with long URLs.
1760 </dd>
1764 </dd>
1766 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1767 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1768 </dt>
1769 <dd>The background styles used for both the frames.
1772 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1774 <dd>The style used for the pointer in the navi frame.
1778 </dt>
1779 <dd>The color used for the database name in the navi frame.
1788 </dd>
1792 <dd>The style used for table headers. See
1797 </dd>
1801 </dd>
1803 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1805 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1807 </dt>
1809 The former feature highlights the row over which your mouse is passing
1810 and the latter lets you visually mark/unmark rows by clicking on
1811 them.<br />
1816 <dd>You put here a valid CSS font family value, for example
1821 <dd>You put here a valid CSS font family value, for example
1835 </dt>
1837 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1839 The Char* values are used for CHAR and VARCHAR editing (if configured
1843 </dt>
1847 </dt>
1848 <dd>Defines if the whole textarea of the query box will be selected on
1849 click.</dd>
1852 </dt>
1853 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1854 editing.</dd>
1857 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1858 Can be turned off by a toggle button on the browse page.</dd>
1862 </dt>
1863 <dd>Defines the place where modify and delete links would be put when
1864 tables contents are displayed (you may have them displayed both at the
1865 left and at the right).
1871 Define which one is displayed by default. The first mode displays each
1872 row on a horizontal line, the second rotates the headers by 90
1873 degrees, so you can use descriptive headers even though columns only
1874 contain small values and still print them out. The vertical mode sorts
1875 each row on a vertical lineup.
1876 </dd>
1879 <dd>
1880 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1881 'css' the rotation of the header for horizontalflipped is done via
1882 CSS. The CSS transformation currently works only in Internet
1883 Explorer.If set to 'fake' PHP does the transformation for you, but of
1884 course this does not look as good as CSS. The 'auto' option enables
1885 CSS transformation when browser supports it and use PHP based one
1886 otherwise.
1887 </dd>
1891 string or integer</dt>
1892 <dd>When editing/creating new columns in a table all fields normally get
1893 lined up one field a line. (default: 'horizontal'). If you set this to
1894 'vertical' you can have each field lined up vertically beneath each
1895 other. You can save up a lot of place on the horizontal direction and
1896 no longer have to scroll. If you set this to integer, editing of fewer
1897 columns will appear in 'vertical' mode, while editing of more columns
1898 still in 'horizontal' mode. This way you can still effectively edit
1899 large number of columns, while having full view on few of them.</dd>
1903 </dt>
1905 display of column comments in Browse or Property display. In browse
1906 mode, the comments are shown inside the header. In property mode,
1907 comments are displayed using a CSS-formatted dashed-line below the
1908 name of the column. The comment is shown as a tool-tip for that column.
1909 </dd>
1921 <dd>Whether to display a link to validate a query in any SQL Query box.
1928 <dd>
1929 The name of the directory where
1931 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1932 are available under a drop-down box when you click the database or
1933 table name, then the Import tab.
1934 <br /><br />
1936 If you want different directory for each user, %u will be replaced
1937 with username.<br /><br />
1941 compressed formats is enabled).<br /><br />
1943 This feature is useful when your file is too big to be uploaded via
1945 uploads are disabled in PHP.<br /><br />
1947 Please note that if PHP is running in safe mode, this directory must
1948 be owned by the same user as the owner of the phpMyAdmin scripts.
1949 <br /><br />
1953 alternatives.
1954 </dd>
1957 <dd>
1958 The name of the directory where dumps can be saved.<br /><br />
1960 If you want different directory for each user, %u will be replaced
1961 with username.<br /><br />
1963 Please note that the directory must exist and has to be writable for
1964 the user running webserver.<br /><br />
1966 Please note that if PHP is running in safe mode, this directory must
1967 be owned by the same user as the owner of the phpMyAdmin scripts.
1968 </dd>
1971 <dd>
1972 The name of the directory where temporary files can be stored.
1973 <br /><br />
1975 This is needed for native MS Excel export, see
1981 <br /><br />
1983 If the directory where phpMyAdmin is installed is subject to an
1985 temporary directory in some directory accessible by the web
1986 server. However for security reasons, this directory should be outside
1987 the tree published by webserver. If you cannot avoid having this
1988 directory published by webserver, place at least an empty
1990 possible.
1991 <br /><br />
1993 This directory should have as strict permissions as possible as the only
1994 user required to access this directory is the one who runs the
1995 webserver. If you have root privileges, simply make this user owner of
1996 this directory and make it accessible only by it:
1997 <br /><br />
1999 <pre>
2000 chown www-data:www-data tmp
2001 chmod 700 tmp
2002 </pre>
2004 If you cannot change owner of the directory, you can achieve a similar
2007 <pre>
2008 chmod 700 tmp
2009 setfacl -m "g:www-data:rwx" tmp
2010 setfacl -d -m "g:www-data:rwx" tmp
2011 </pre>
2013 If neither of above works for you, you can still make the directory
2015 system reading and writing data in this directory.
2016 </dd>
2019 <dd>
2020 In this array are defined default parameters for export, names of
2021 items are similar to texts seen on export page, so you can easily
2022 identify what they mean.
2023 </dd>
2026 <dd>
2027 In this array are defined default parameters for import, names of
2028 items are similar to texts seen on import page, so you can easily
2029 identify what they mean.
2030 </dd>
2033 <dd>
2034 Repeat the headers every X cells, or 0 to deactivate.
2035 </dd>
2043 </dt>
2044 <dd>
2045 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2046 or icon is always displayed on the left panel. If JavaScript is enabled in
2047 your browser, a click on this opens a distinct query window, which is
2048 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2049 changes to display a query box.<br /><br />
2051 The size of this query window can be customized with
2053 - both integers for the size in pixels. Note that normally, those
2055 theme you are using.<br /><br />
2059 opens the query window and puts the current query
2060 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2061 query in the right panel's query box.
2062 <br /><br />
2063 The usage of the JavaScript query window is recommended if you have a
2064 JavaScript enabled browser. Basic functions are used to exchange quite
2065 a few variables, so most 4th generation browsers should be capable to
2066 use that feature. It currently is only tested with Internet Explorer 6
2067 and Mozilla 1.x.
2068 <br /><br />
2070 to a table, which has to be created by you (see <a
2072 all your queries will be appended to the form, but only as long as
2073 your window is opened they remain saved.
2074 <br /><br />
2075 When using the JavaScript based query window, it will always get
2076 updated when you click on a new table/db to browse and will focus if
2077 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2078 the query window by checking the box "Do not overwrite this query from
2079 outside the window" below the query textarea. Then you can browse
2080 tables/databases in the background without losing the contents of the
2081 textarea, so this is especially useful when composing a query with
2082 tables you first have to look in. The checkbox will get automatically
2083 checked whenever you change the contents of the textarea. Please
2084 uncheck the button whenever you definitely want the query window to
2085 get updated even though you have made alterations.
2086 <br /><br />
2089 <br /><br />
2090 The query window also has a custom tabbed look to group the features.
2092 default tab to be used when opening the query window. It can be set to
2093 either 'sql', 'files', 'history' or 'full'.</dd>
2099 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2101 If the approximate row count as returned by
2104 count will be used.
2105 </dd>
2107 <dd>For VIEWs, since obtaining the exact count could have an
2108 impact on performance, this value is the maximum to be displayed, using
2110 any row counting.
2111 </dd>
2115 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2117 page. By clicking on the button 'toggle scratchboard' on the page
2118 where you edit x/y coordinates of those elements you can activate a
2119 scratchboard where all your elements are placed. By clicking on an
2120 element, you can move them around in the pre-defined area and the x/y
2121 coordinates will get updated dynamically. Likewise, when entering a
2122 new position directly into the input field, the new position in the
2123 scratchboard changes after your cursor leaves the input field.<br />
2124 You have to click on the 'OK'-button below the tables to save the new
2125 positions. If you want to place a new element, first add it to the
2126 table of elements and then you can drag the new element around.<br />
2127 By changing the paper size and the orientation you can change the size
2128 of the scratchboard as well. You can do so by just changing the
2129 dropdown field below, and the scratchboard will resize automatically,
2130 without interfering with the current placement of the elements.<br />
2131 If ever an element gets out of range you can either enlarge the paper
2132 size or click on the 'reset' button to place all elements below each
2133 other.<br />
2135 get this control to work. The basic Drag&Drop script functionality
2136 was kindly borrowed from www.youngpup.net and is underlying so
2137 specific license.</dd>
2140 <dd>Sorts database and table names according to natural order (for example,
2141 t1, t2, t10). Currently implemented in the left panel (Light mode)
2142 and in Database view, for the table list.</dd>
2153 <dd>Allows you to specify window's title bar. You can use
2155 </dd>
2165 </dd>
2168 <dd>If theme manager is active, use this as the path of the subdirectory
2169 containing all the themes.</dd>
2183 </dt>
2184 <dd>Default queries that will be displayed in query boxes when user didn't
2185 specify any. You can use standard
2187 </dd>
2190 <dd>
2191 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
2192 default we use HTML to format the query, but you can disable this by
2194 </dd>
2197 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2198 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2199 query inside a bracket is indented. By changing
2202 specifies the units of the indent amount that you specified. This is
2203 used via stylesheets.</dd>
2206 <dd>This array is used to define the colours for each type of element of
2207 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2209 If you specify an empty string for the color of a class, it is ignored
2210 in creating the stylesheet.
2211 You should not alter the class names, only the colour strings.<br />
2232 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2236 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2237 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2238 </ul>
2239 </dd>
2243 <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,
2244 as originally published on
2246 <br />
2247 For help in setting up your system to use the service, see the
2249 </dd>
2253 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2254 and any password, so we use those by default. Instead, if
2255 you have an account with them, you can put your login details
2256 here, and it will be used in place of the anonymous login.</dd>
2257 </dl>
2258 </dd>
2261 <dd><b>DEVELOPERS ONLY!</b></dd>
2264 <dd><b>DEVELOPERS ONLY!</b><br />
2265 Enable logging queries and execution times to be displayed in the bottom
2266 of main page (right frame).</dd>
2269 <dd><b>DEVELOPERS ONLY!</b><br />
2270 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2271 the code.<br />
2272 For help in setting up your system to this, see the
2276 <dd><b>DEVELOPERS ONLY!</b><br />
2277 Enable profiling support for phpMyAdmin. This will append a chunk of data
2278 to the end of every page displayed in the main window with profiling
2279 statistics for that page.<br />
2280 You may need to increase the maximum execution time for this to
2281 complete successfully.<i>Profiling was removed from the code for
2282 version 2.9.0 due to licensing issues.</i></dd>
2284 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2285 <dd><b>DEVELOPERS ONLY!</b><br />
2286 When profiling data is displayed, this variable controls the threshold of
2287 display for any profiling data, based on the average time each time has
2288 taken. If it is over the threshold it is displayed, otherwise it is not
2289 displayed. This takes a value in milliseconds. In most cases you don't need
2290 to edit this.</dd>
2293 <dd>All possible types of a MySQL column. In most cases you don't need to
2294 edit this.</dd>
2297 <dd>Possible attributes for columns. In most cases you don't need to edit
2298 this.</dd>
2301 <dd>A list of functions MySQL supports. In most cases you don't need to
2302 edit this.</dd>
2305 <dd>Mapping of column types to meta types used for preferring displayed
2306 functions. In most cases you don't need to edit this.</dd>
2309 <dd>Functions preferred for column meta types as defined in
2310 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2311 to edit this.</dd>
2314 <dd>Functions selected by default when inserting/changing row, Functions
2315 are defined for meta types from
2317 <code>first_timestamp</code>, which is used for first timestamp column
2318 in table.</dd>
2321 <dd>Operators available for search operations on numeric and date columns.
2322 </dd>
2325 <dd>Operators available for search operations on character columns.
2326 Note that we put <code>LIKE</code> by default instead of
2327 <code>LIKE %...%</code>, to avoid unintended performance problems
2328 in case of huge tables.</dd>
2331 <dd>Operators available for search operations on ENUM columns.</dd>
2334 <dd>Additional operators available for search operations when the
2335 column can be null.</dd>
2337 </dl>
2339 <!-- TRANSFORMATIONS -->
2345 </ol>
2349 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2351 section</a> on how to do so.</p>
2353 <p> You can apply different transformations to the contents of each column. The
2354 transformation will take the content of each column and transform it with
2355 certain rules defined in the selected transformation.</p>
2357 <p> Say you have a column 'filename' which contains a filename. Normally you would
2358 see in phpMyAdmin only this filename. Using transformations you can transform
2359 that filename into a HTML link, so you can click inside of the phpMyAdmin
2360 structure on the column's link and will see the file displayed in a new browser
2361 window. Using transformation options you can also specify strings to
2362 append/prepend to a string or the format you want the output stored in.</p>
2364 <p> For a general overview of all available transformations and their options,
2365 you can consult your
2366 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2367 installation.</p>
2369 <p> For a tutorial on how to effectively use transformations, see our
2371 the official phpMyAdmin homepage.</p>
2375 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2376 clicking on the 'Structure' link for a table). There click on
2377 "Change" (or change icon) and there you will see three new
2378 fields at
2379 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2380 'Transformation options'.</p>
2382 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2383 that corresponds to the column's contents. Please note that
2384 transformations are inactive as long as no MIME-type is selected.</li>
2386 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2387 hopefully growing amount of pre-defined transformations. See below for information on
2388 how to build your own transformation.<br />
2390 There are global transformations and mimetype-bound transformations. Global transformations
2391 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2392 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2393 transformations which operate on the main mimetype (like 'image'), which will most likely
2394 take the subtype into regard, and those who only operate on a
2395 specific subtype (like 'image/jpeg').<br />
2397 You can use transformations on mimetypes for which the function was not defined for. There
2398 is no security check for you selected the right transformation, so take care of what the
2399 output will be like.</li>
2401 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2402 transform-function specific options here. Usually the transforms can operate with default
2403 options, but it is generally a good idea to look up the overview to see which options are
2404 necessary.<br />
2406 Much like the ENUM/SET-Fields, you have to split up several options using the format
2407 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2408 parsed as an array, leaving the first value the first element in the array, and so
2409 forth.<br />
2411 If you want to specify a MIME character set you can define it in the transformation_options.
2412 You have to put that outside of the pre-defined options of the specific mime-transform,
2414 for which you can specify 2 options and you want to append a character set, enter "'first
2415 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2417 </ul>
2421 <p> All mimetypes and their transformations are defined through single files in
2422 the directory 'libraries/transformations/'.</p>
2424 <p> They are stored in files to ease up customization and easy adding of new
2425 transformations.</p>
2427 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2428 always work. It makes no sense to apply a transformation to a mimetype, the
2429 transform-function doesn't know to handle.</p>
2431 <p> One can, however, use empty mime-types and global transformations which should work
2432 for many mimetypes. You can also use transforms on a different mimetype they where built
2433 for, but pay attention to option usage as well as what the transformation does to your
2434 column.</p>
2436 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2437 any other transform function and provides some basic functions.</p>
2439 <p> There are 5 possible file names:</p>
2441 <ol><li>A mimetype+subtype transform:<br /><br />
2443 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2445 Please not that mimetype and subtype are separated via '_', which shall
2446 not be contained in their names. The transform function/filename may
2447 contain only characters which cause no problems in the file system as
2448 well as the PHP function naming convention.<br /><br />
2450 The transform function will the be called
2451 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2453 <b>Example:</b><br /><br />
2455 <tt>text_html__formatted.inc.php</tt><br />
2456 <tt>PMA_transform_text_html__formatted()</tt></li>
2458 <li>A mimetype (w/o subtype) transform:<br /><br />
2460 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2462 Please note that there are no single '_' characters.
2463 The transform function/filename may contain only characters which cause
2464 no problems in the file system as well as the PHP function naming
2465 convention.<br /><br />
2467 The transform function will the be called
2468 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2470 <b>Example:</b><br /><br />
2472 <tt>text__formatted.inc.php</tt><br />
2473 <tt>PMA_transform_text__formatted()</tt></li>
2475 <li>A mimetype+subtype without specific transform function<br /><br />
2477 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2479 Please note that there are no '__' characters in the filename. Do not
2480 use special characters in the filename causing problems with the file
2481 system.<br /><br />
2483 No transformation function is defined in the file itself.<br /><br />
2485 <b>Example:</b><br /><br />
2487 <tt>text_plain.inc.php</tt><br />
2488 (No function)</li>
2490 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2492 <tt>[mimetype].inc.php</tt><br /><br />
2494 Please note that there are no '_' characters in the filename. Do not use
2495 special characters in the filename causing problems with the file system.
2496 <br /><br />
2498 No transformation function is defined in the file itself.<br /><br />
2500 <b>Example:</b><br /><br />
2502 <tt>text.inc.php</tt><br />
2503 (No function)</li>
2505 <li>A global transform function with no specific mimetype<br /><br />
2507 <tt>global__[transform].inc.php</tt><br /><br />
2509 The transform function will the be called
2510 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2512 <b>Example:</b><br /><br />
2514 <tt>global__formatted</tt><br />
2515 <tt>PMA_transform_global__formatted()</tt></li>
2516 </ol>
2518 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2519 transform function.</p>
2521 <p> All filenames containing no '__' in themselves are not shown as valid transform
2522 functions in the dropdown.</p>
2524 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2525 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2526 without a transform function.</p>
2528 <p> To create a new transform function please see
2529 <tt>libraries/transformations/template_generator.sh</tt>.
2530 To create a new, empty mimetype please see
2531 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2533 <p> A transform function always gets passed three variables:</p>
2535 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2536 you want to transform.</li>
2537 <li><b>$options</b> - Contains any user-passed options to a transform function
2538 as an array.</li>
2539 <li><b>$meta</b> - Contains an object with information about your column.
2540 The data is drawn from the output of the
2542 function. This means, all object properties described on the
2544 available in this variable and can be used to transform a column accordingly
2545 to unsigned/zerofill/not_null/... properties.<br />
2546 The $meta->mimetype variable contains the original MIME-type of the
2547 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2548 </ol>
2550 <p> Additionally you should also provide additional function to provide
2551 information about the transformation to the user. This function should
2552 have same name as transformation function just with appended
2553 <code>_info</code> suffix. This function accepts no parameters and returns
2554 array with information about the transformation. Currently following keys
2555 can be used:
2556 </p>
2557 <dl>
2558 <dt><code>info</code></dt>
2559 <dd>Long description of the transformation.</dd>
2560 </dl>
2562 <!-- FAQ -->
2569 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2574 </ol>
2576 <p> Please have a look at our
2578 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2579 features and or interface.</p>
2585 action is required or phpMyAdmin sends a blank page or a page full of
2586 cryptic characters to my browser, what can I do?</a></h4>
2588 <p> There are some known PHP bugs with output buffering and compression.<br />
2590 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2591 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2592 configuration file.<br />
2593 Furthermore, we know about such problems connected to the release
2594 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2595 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2600 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2601 See also the
2603 entry about PHP bugs with output buffering.<br />
2604 If your server keeps crashing, please ask for help in the various Apache
2605 support groups.</p>
2609 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2610 script: I'm always displayed the login screen.</a></h4>
2612 <p> This is a known PHP bug (see this
2614 official PHP bug database. It means there is and won't be any phpMyAdmin
2615 fix against it because there is no way to code a fix.</p>
2621 application misbehaved by not returning a complete set of
2623 </h4>
2625 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2626 Have a look at the last message in this
2628 official PHP bug database.</p>
2633 and/or many error messages with the
2635 mode.</a></h4>
2637 <p> This is a known problem with the PHP
2639 filter: it's not so stable. Please use instead the cookie authentication mode.
2640 </p>
2645 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2646 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2647 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2648 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2649 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2654 work.</a></h4>
2656 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2657 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2658 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2659 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2660 We faced PHP crashes when trying to download a dump with MS Internet
2661 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2662 this case you should switch to the release version of PHP 4.2.0.</p>
2666 an error about safe mode being in effect.</a></h4>
2668 <p> Your uploaded file is saved by PHP in the "upload dir", as
2669 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2670 the system default is <i>/tmp</i>).<br />
2671 We recommend the following setup for Apache servers running in safe mode,
2672 to enable uploads of files while being reasonably secure:</p>
2674 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2675 <li>give ownership to the Apache server's user.group:
2676 <tt>chown apache.apache /tmp/php</tt></li>
2677 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2678 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2679 <li>restart Apache</li>
2680 </ul>
2684 general file uploads don't work on my system and uploaded files have a
2685 <tt>Content-Type:</tt> header in the first line.</a></h4>
2687 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2688 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2689 So the problem is that this package has a serious bug that was corrected
2690 ages ago in PHP (2001-01-28: see
2692 for more details). The problem is that the bugged package is still
2693 available though it was corrected (see
2695 for more details).<br />
2696 So please download
2697 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2698 and the problem should go away.<br />
2699 And that fixes the \r\n problem with file uploads!</p>
2703 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2704 I'm using the Apache server.</a></h4>
2706 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2707 your <i>httpd.conf</i>:</p>
2711 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2715 uploading a file from the query box.</a></h4>
2717 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2718 restrictions. However you need to create temporary directory and
2720 The uploaded files will be moved there, and after execution of your
2726 <p> The MySQL manual explains how to
2728 reset the permissions</a>.</p>
2733 execute a bookmark.</a></h4>
2735 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2736 cannot access the uploaded query.</p>
2741 submit a query from the convenient text area.</a></h4>
2743 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2744 and try to increase it.</p>
2748 </h4>
2750 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2751 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2752 names to align with current standards.</p>
2757 </h4>
2759 <p> Starting with version 2.7.0, the import engine has been re–written and these
2760 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2761 to take advantage of the new import features.</p>
2763 <p> The first things to check (or ask your host provider to check) are the
2764 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2765 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2766 All of these three settings limit the maximum size of data that can be
2767 submitted and handled by PHP. One user also said that post_max_size
2768 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2770 There exist several workarounds if your upload is too big or your
2771 hosting provider is unwilling to change the settings:</p>
2774 feature. This allows one to
2775 upload a file to the server via scp, ftp, or your favorite file transfer
2776 method. PhpMyAdmin is then able to import the files from the temporary
2778 section</a> of this document.</li>
2780 BigDump</a>) to split the files before uploading. We cannot support this
2781 or any third party applications, but are aware of users having success
2782 with it.</li>
2783 <li>If you have shell (command line) access, use MySQL to import the files
2784 directly. You can do this by issuing the "source" command from
2785 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2786 </ul>
2790 support?</a></h4>
2792 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2793 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2794 connect to your MySQL server using PHP's classic
2797 is available in php 5.0. The latter one should be used unless you have
2798 good reason not to do so.<br />
2799 When compiling php, we strongly recommend that you manually link the MySQL
2800 extension of your choice to a MySQL client library of at least the same
2801 minor version since the one that is bundled with some PHP distributions is
2804 If your webserver is running on a windows system, you might want to try
2805 MySQL's
2807 instead of the MySQL / MySQLi extensions that are bundled with the official
2808 php Win32 builds.</p>
2812 message, "Client does not support authentication protocol requested
2813 by server; consider upgrading MySQL client"</a></h5>
2815 <p> You tried to access MySQL with an old MySQL client library. The version of
2816 your MySQL client library can be checked in your phpinfo() output.
2817 In general, it should have at least the same minor version as your server
2821 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2822 changed the authentication hash and your PHP is trying to use the old method.
2824 with the proper client library to match your MySQL installation. Your
2825 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2826 More information (and several workarounds) are located in the
2828 </p>
2832 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2833 capital letter in its name it is changed to lowercase as it should. But
2834 if I try to DROP this table MySQL is unable to find the corresponding
2835 file.</a></h4>
2837 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2838 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2839 directive.</p>
2843 script seems not to know the font face I'm using!</a></h4>
2845 <p> The "FPDF" library we're using for this feature requires some
2846 special files to use font faces.<br />
2848 these files.</p>
2852 check PHP Configuration".</a></h4>
2854 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2855 "MySQL extension". This extension may be part of the PHP
2856 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2857 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2858 to load the extension but failed.<br /><br />
2860 Usually, the problem is solved by installing a software package called
2861 "PHP-MySQL" or something similar.</p>
2866 and I cannot log in using cookie auth.</a></h4>
2868 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2872 so I cannot upload.</a></h4>
2874 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2875 parameter is not set to "on".</p>
2879 a new table the table and column names are changed to lowercase!</a></h4>
2881 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2882 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2883 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2884 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2885 directory and add the following line to the group [mysqld]:</p>
2887 <pre>set-variable = lower_case_table_names=0</pre>
2889 <p> Next, save the file and restart the MySQL service. You can always check the
2890 value of this directive using the query</p>
2892 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2896 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2899 </p>
2903 and I get problems, such as undefined variables when I run a
2906 <p> A tip from Jose Fandos: put a comment on the following two lines
2907 in httpd.conf, like this:</p>
2909 <pre>
2910 # mod_gzip_item_include file \.php$
2912 </pre>
2914 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2915 PHP scripts. Of course you have to restart Apache.</p>
2920 I get the error "No input file specified" when trying to
2921 run phpMyAdmin.</a></h4>
2923 <p> This is a permission problem. Right-click on the phpmyadmin folder
2924 and choose properties. Under the tab Security, click on "Add"
2925 and select the user "IUSR_machine" from the list. Now set his
2926 permissions and it should work.</p>
2930 db_structure.php with plenty of tables).</a></h4>
2933 GZIP output buffering is enabled. If you turn off it (by
2935 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2936 PHP 5.0.0.</p>
2940 message 'Errorcode: 13'. What does this mean?</a></h4>
2942 <p> This can happen due to a MySQL bug when having database / table names with
2943 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2944 To fix this, turn off this directive, convert all database and table names
2945 to lower case and turn it on again. Alternatively, there's a bug-fix
2946 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2950 and the columns are duplicated.</a></h4>
2952 <p> It is possible to configure Apache in such a way that PHP has problems
2953 interpreting .php files.</p>
2955 <p> The problems occur when two different (and conflicting) set of directives
2956 are used:</p>
2958 <pre>
2959 SetOutputFilter PHP
2960 SetInputFilter PHP
2961 </pre>
2963 <p> and</p>
2965 <pre>AddType application/x-httpd-php .php</pre>
2967 <p> In the case we saw, one set of directives was in
2968 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2969 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2970 The recommended way is with <tt>AddType</tt>, so just comment out
2971 the first set of lines and restart Apache:</p>
2973 <pre>
2974 #SetOutputFilter PHP
2975 #SetInputFilter PHP
2976 </pre>
2981 <p> This problem is known to happen when the server is running Turck MMCache
2982 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2987 <p>Yes.</p>
2988 <p>
2989 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
2990 is still maintained.
2991 </p>
2994 <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>
2996 <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>
2999 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3000 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3001 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3002 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3003 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3004 enabled.) Click <tt>OK</tt>.</li>
3005 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3006 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3007 </ol>
3011 PHP 5.0.4 on 64-bit systems?</a></h4>
3013 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3014 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3020 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
3021 the order of the server paragraph in <tt>config.inc.php</tt>.
3022 Table and script parts are optional. If you want
3023 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3024 some configuration. Following lines apply only for <a
3026 that you have enabled some features within global configuration. You need
3027 <code>Options FollowSymLinks</code> and <code>AllowOverride
3028 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3029 you need mod_rewrite to be enabled. Then you just need to create following
3030 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3031 (don't forget to change directory name inside of it):</p>
3033 <pre>
3034 RewriteEngine On
3035 RewriteBase /path_to_phpMyAdmin
3036 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3037 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3038 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3039 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3040 </pre>
3043 <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>
3045 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3046 following rewrite rule:</p>
3048 <pre>
3049 RewriteEngine On
3050 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3051 </pre>
3055 </h4>
3056 <p>
3057 There can be many explanations to this and a look at your server's
3058 error log file might give a clue.
3059 </p>
3063 password encryption in cookie auth doesn't work.</a></h4>
3065 <p> If your cluster consist of different architectures, PHP code used for
3066 encryption/decryption won't work correct. This is caused by use of
3067 pack/unpack functions in code. Only solution is to use mcrypt extension
3068 which works fine in this case.</p>
3073 <p> Yes but the default configuration values of Suhosin are known to cause
3074 problems with some operations, for example editing a table with many
3075 columns and no primary key or with textual primary key.
3076 </p>
3077 <p>
3078 Suhosin configuration might lead to malfunction in some cases and it can
3079 not be fully avoided as phpMyAdmin is kind of application which needs to
3080 transfer big amounts of columns in single HTTP request, what is something
3081 what Suhosin tries to prevent. Generally all
3082 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3083 <code>suhosin.get.*</code> directives can have negative effect on
3084 phpMyAdmin usability. You can always find in your error logs which limit
3085 did cause dropping of variable, so you can diagnose the problem and adjust
3086 matching configuration variable.
3087 </p>
3088 <p>
3089 The default values for most Suhosin configuration options will work in most
3090 scenarios, however you might want to adjust at least following parameters:
3091 </p>
3093 <ul>
3094 <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>
3095 <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>
3096 <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>
3097 <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>
3098 <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>
3099 <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>
3100 <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>
3101 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#logging_configuration">suhosin.log.*</a> should not include SQL, otherwise you get big slowdown</li>
3102 </ul>
3104 <p>
3106 <tt>SuhosinDisableWarning</tt> directive</a>.
3107 </p>
3111 but then my connection is redirected back to http. What can cause this
3112 behavior?</a></h4>
3114 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3115 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>
3118 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3120 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3121 Example from the Apache 2.2 documentation:</p>
3122 <pre>
3123 ProxyPass /mirror/foo/ http://backend.example.com/
3124 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3125 ProxyPassReverseCookieDomain backend.example.com public.example.com
3126 ProxyPassReverseCookiePath / /mirror/foo/
3127 </pre>
3129 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3130 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3131 This is not specific to phpmyadmin, it's just the behavior of Apache.
3132 </p>
3134 <pre>
3135 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3136 ProxyPassReverse /mirror/foo/
3137 http://backend.example.com/%7Euser/phpmyadmin
3138 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3139 </pre>
3141 <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>
3142 for more details.</p>
3146 privileges, I get an error about an unknown column.</a></h4>
3148 <p> The MySQL server's privilege tables are not up to date, you need to run
3149 the <tt>mysql_upgrade</tt> command on the server.</p>
3156 headers already sent by ..." is displayed, what's the problem?</a></h4>
3158 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3159 (I.E. no blank lines, no spaces, no characters...) neither before the
3160 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3161 tag at the end. We also got a report from a user under IIS, that used
3162 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3163 contained an end-of-line character (hex 0A) at the end; removing this character
3164 cleared his errors.</p>
3169 <p> Either there is an error with your PHP setup or your username/password is
3170 wrong. Try to make a small script which uses mysql_connect and see if it
3171 works. If it doesn't, it may be you haven't even compiled MySQL support
3172 into PHP.</p>
3176 connect to local MySQL server through socket '/tmp/mysql.sock'
3177 (111) ..." is displayed. What can I do?</a></h4>
3179 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3181 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3182 In your <i>php.ini</i> you will find a line</p>
3184 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3186 <p> change it to</p>
3188 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3190 <p> Then restart apache and it will work.</p>
3192 <p> Here is a fix suggested by Brad Ummer:</p>
3194 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3195 To do this, telnet to your server and go to the MySQL bin directory. In
3196 this directory there should be a file named <i>mysqladmin</i>. Type
3197 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3198 info about your MySQL server, including the socket
3199 (<i>/tmp/mysql.sock</i>, for example).</li>
3200 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3201 phpMyAdmin, you need to complete the socket information in the
3202 <i>config.inc.php</i>.<br />
3203 For example:
3205 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3206 <br /><br />
3208 Please also make sure that the permissions of this file allow to be readable
3209 by your webserver (i.e. '0755').</li>
3210 </ul>
3212 <p> Have also a look at the
3214 corresponding section of the MySQL documentation</a>.</p>
3218 what can I do?</a></h4>
3221 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3222 sometime.<br />
3223 Also have a look at your PHP version number: if it contains "4.0b..."
3224 it means you're running a beta version of PHP. That's not a so good idea,
3225 please upgrade to a plain revision.</p>
3229 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3230 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3232 <p> Check the value you set for the
3234 directive in the phpMyAdmin configuration file.</p>
3238 password: YES)"-error when trying to access a MySQL-Server on a
3239 host which is port-forwarded for my localhost.</a></h4>
3241 <p> When you are using a port on your localhost, which you redirect via
3242 port-forwarding to another host, MySQL is not resolving the localhost
3243 as expected.<br />
3244 Erik Wasser explains: The solution is: if your host is "localhost"
3245 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3246 connection for speeding up things. And that doesn't work in this configuration
3247 with port forwarding.<br />
3253 <p> Themes are configured with
3257 <br />
3259 should not delete the directory "original" or its underlying
3260 structure, because this is the system theme used by phpMyAdmin.
3261 "original" contains all images and styles, for backwards
3262 compatibility and for all themes that would not include images or css-files.
3263 <br /><br />
3266 is enabled, you can select your favorite theme on the main page. Your
3267 selected theme will be stored in a cookie.<br /><br /></p>
3269 <p> To create a theme:</p>
3271 <ul><li>make a new subdirectory (for example "your_theme_name") under
3273 (by default <tt>themes</tt>)</li>
3274 <li>copy the files and directories from "original" to
3275 "your_theme_name"</li>
3276 <li>edit the css-files in "your_theme_name/css"</li>
3277 <li>put your new images in "your_theme_name/img"</li>
3278 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3279 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3280 contain your chosen theme name, that will be visible in user interface</li>
3281 <li>make a new screenshot of your theme and save it under
3282 "your_theme_name/screen.png"</li>
3283 </ul>
3285 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3286 theme verbose name, theme generation and theme version. These versions and
3287 generations are enumerated from 1 and do not have any direct dependence on
3288 phpMyAdmin version. Themes within same generation should be backwards
3289 compatible - theme with version 2 should work in phpMyAdmin requiring
3290 version 1. Themes with different generation are incompatible.</p>
3292 <p> If you do not want to use your own symbols and buttons, remove the
3293 directory "img" in "your_theme_name". phpMyAdmin will
3294 use the default icons and buttons (from the system-theme "original").
3295 </p>
3299 what can I do?</a></h4>
3301 <p> Here are a few points to check:</p>
3303 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3305 directive empty. See also
3307 </li>
3308 <li>Maybe you have a broken PHP installation or you need to upgrade
3309 your Zend Optimizer. See
3311 http://bugs.php.net/bug.php?id=31134</a>.
3312 </li>
3313 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3314 set to the default (200) or another low value, you could get this
3315 error if your table has a high number of columns. Adjust this setting
3316 accordingly. (Thanks to Klaus Dorninger for the hint).
3317 </li>
3318 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3319 of ";" will cause this error. Replace it with "&;".
3320 </li>
3322 you might want to increase
3324 </li>
3325 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3326 </li>
3327 </ul>
3332 <p> To be able to see a progress bar during your uploads, your server must
3335 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3336 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3343 who logged out can not log in again in with the same nick.</a></h4>
3345 <p> This is related to the authentication mechanism (protocol) used by
3346 phpMyAdmin. To bypass this problem: just close all the opened
3347 browser windows and then go back to phpMyAdmin. You should be able to
3348 log in again.</p>
3352 limit error or a time limit error.</a></h4>
3354 <p> Compressed dumps are built in memory and because of this are limited to
3355 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3356 using
3358 (enabled by default). Zip exports can not be handled this way, so if you need
3359 Zip files for larger dump, you have to use another way.</p>
3363 when I rename a table or a column.</a></h4>
3365 <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>
3369 bundled with the MySQL server distribution.</a></h4>
3371 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3373 <pre>
3374 -- MySQL dump 8.22
3375 --
3376 -- Host: localhost Database: database
3377 ---------------------------------------------------------
3378 -- Server version 3.23.54
3379 </pre>
3381 <p> The invalid part of the code is the horizontal line made of dashes that
3382 appears once in every dump created with mysqldump. If you want to run your
3383 dump you have to turn it into valid MySQL. This means, you have to add a
3384 whitespace after the first two dashes of the line or add a # before it:
3385 <br />
3386 <code>
3387 -- -------------------------------------------------------<br />
3388 </code>
3389 or<br />
3390 <code>
3391 #---------------------------------------------------------
3392 </code>
3393 </p>
3400 <p> Please note that you should not use the separating string multiple times
3401 without any characters between them, or at the beginning/end of your table
3402 name. If you have to, think about using another TableSeparator or disabling
3403 that feature</p>
3408 <p> In Relation view, being able to choose a table in another database,
3409 or having more than one index column in the foreign key.<br /><br/>
3410 In Query-by-example (Query), automatic generation of the query
3411 LEFT JOIN from the foreign table.<br /><br/>
3412 </p>
3416 I get series of errors like "Warning: unable to parse url". How
3417 can this be fixed?</a></h4>
3418 <p>
3419 Your table neither have a primary key nor an unique one, so we must use a
3420 long expression to identify this row. This causes problems to parse_url
3421 function. The workaround is to create a primary or unique key.
3422 <br />
3423 </p>
3427 a MIME-Transformation onto!</a></h4>
3429 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3430 nested forms can be put inside the table where phpMyAdmin displays the results.
3431 You can, however, use any form inside of a table if keep the parent
3432 form-container with the target to tbl_row_delete.php and just put your own
3433 input-elements inside. If you use a custom submit input field, the form will
3434 submit itself to the displaying page again, where you can validate the
3435 $HTTP_POST_VARS in a transformation.
3437 For a tutorial on how to effectively use transformations, see our
3439 on the official phpMyAdmin-homepage.</p>
3443 MySQL server</a></h4>
3445 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3448 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3449 the quote-character (") is interpreted as an identifier quote character and
3450 not as a string quote character, which makes many internal phpMyAdmin
3452 statements. There is no workaround to this behaviour. News to this item will
3453 be posted in Bug report
3454 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3455 </p>
3459 more that one column with the same value
3460 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3461 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3463 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3464 can use it for the Edit and Delete links.</p>
3469 <p> phpMyAdmin uses a quick method to get the row count, and this method
3470 only returns an approximate count in the case of InnoDB tables. See
3472 a way to modify those results, but
3473 this could have a serious impact on performance.</p>
3478 <p> The number of records in queries containing COUNT and GROUP BY is
3479 not correctly calculated. Also, sorting results of a query like
3484 containing an hyphen.
3485 </a></h4>
3486 <p>
3487 The tests I have made with current MySQL 4.1.11 API shows that the
3488 API does not accept this syntax for the USE command. Enclosing the
3489 db name with backquotes works. For further confusion, no backquotes
3490 are needed with command-line mysql.
3491 </p>
3494 <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>
3495 <p>
3496 This has been a known limitation of phpMyAdmin since the beginning and
3497 it's not likely to be solved in the future.
3498 </p>
3500 <!-- Begin: Excel import limitations -->
3503 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3504 <p>
3505 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target="_blank">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3506 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3507 <br /><br />
3508 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3509 </p>
3512 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3513 <p>
3514 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3515 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3516 </p>
3519 <a href="#faq3_17">3.17 When I import an Excel spreadsheet, my custom cell types are not represented as they are in Excel.</a></h4>
3520 <p>
3521 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3522 consider using a built-in type. These are almost always guarenteed to import correctly.
3523 </p>
3525 <!-- End: Excel import limitations -->
3526 <!-- Begin: CSV import limitations -->
3529 <a href="#faq3_18">3.18 When I import a CSV file that contains multiple tables, they are lumped together into a single table.</a></h4>
3530 <p>
3531 There is no reliable way to differetiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3532 </p>
3534 <!-- End: CSV import limitations -->
3535 <!-- Begin: Import type-detection limitations -->
3538 <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>
3539 <p>
3540 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
3541 you will have to edit the structure to your liking post-import.
3542 <br /><br />
3543 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
3544 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.
3545 </p>
3547 <!-- End: Import type-detection limitations -->
3549 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3552 <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
3553 need to install it for each customer.
3554 </a></h4>
3555 <p>
3556 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3557 your users. The development of this feature was kindly sponsored by
3558 NetCologne GmbH.
3559 This requires a properly setup MySQL user management and phpMyAdmin
3560 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3562 </p>
3566 access.
3567 </a></h4>
3568 <p>
3569 This depends on your system.<br />
3570 If you're running a server which cannot be accessed by other people, it's
3571 sufficient to use the directory protection bundled with your webserver
3573 If other people have telnet access to your server, you should use
3574 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3575 <br /><br />
3576 Suggestions:
3577 </p>
3578 <ul>
3579 <li>
3581 </li>
3582 <li>
3583 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3584 is a user whose password is only known to you, and apache is the
3585 group under which Apache runs.
3586 </li>
3587 <li>
3588 You should use PHP safe mode, to protect from other users that try
3590 </li>
3591 </ul>
3596 </a></h4>
3597 <p>
3602 </p>
3605 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3606 authentication.
3607 </a></h4>
3611 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3612 and/or
3614 are wrong.</li>
3616 <li>You have already setup a security mechanism for the
3617 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3618 phpMyAdmin's authentication, so remove it.</li>
3619 </ul>
3626 and put the privileges you want. For example,
3628 would let a user create/manage his/her database(s).</p>
3633 <p> If you have existing rules from an old .htaccess file, you can take them
3636 be a major benefit here if your installation is suited to using it. Then
3637 you can just add those updated lines into the
3641 <p> If you want a pre-made sample, you can try this fragment. It stops the
3642 'root' user from logging in from any networks other than the private
3645 <pre>
3646 //block root from logging in except from the private networks
3647 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3648 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3649 'deny root from all',
3650 'allow root from localhost',
3654 );
3655 </pre>
3660 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3661 different than the one set in your
3663 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3664 while a domain name is defined in the config file.</p>
3669 <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>
3675 when trying to create a table with more than 14 columns.
3676 </a></h4>
3677 <p>
3678 We could reproduce this problem only under Win98/98SE. Testing under
3679 WinNT4 or Win2K, we could easily create more than 60 columns.
3680 <br />
3681 A workaround is to create a smaller number of columns, then come back to
3682 your table properties and add the other columns.
3683 </p>
3687 <p>
3688 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3689 with each script/website that use forms.<br />
3690 Upgrade or downgrade your Xitami server.
3691 </p>
3694 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3695 <p>
3696 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3697 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3698 don't seem to work.<br />
3700 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3701 the user's temporary directory, so they must be moved before closing
3702 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3705 </p>
3709 Explorer never stores the cookies.
3710 </a></h4>
3711 <p>
3712 MS Internet Explorer seems to be really buggy about cookies, at least till
3714 in this area!
3715 <br />
3716 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3717 work!
3718 </p>
3722 rows.
3723 </a></h4>
3724 <p>
3726 </p>
3729 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3730 when trying to modify a row in a table with many columns, or with a text
3731 column
3732 </a></h4>
3733 <p>
3734 Your table neither have a primary key nor an unique one, so we must use a
3735 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
3736 those browsers, and this not happen in Netscape, for example. The
3737 workaround is to create a primary or unique key, or use another browser.
3738 <br />
3739 </p>
3743 page.
3744 </a></h4>
3745 <p>
3746 Some browsers support right-clicking into the frame you want to refresh,
3747 just do this in the right frame.<br />
3748 </p>
3752 query box.
3753 </a></h4>
3754 <p>
3755 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3756 Mozilla versions.<br />
3757 </p>
3761 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3762 </a></h4>
3763 <p>
3764 This is a Mozilla bug (see bug #26882 at
3766 </p>
3771 </a></h4>
3772 <p>
3773 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3774 data in octet-stream mode. Since we can't detect the specific Netscape
3775 version, we cannot workaround this bug.
3776 </p>
3780 wrong.</a></h4>
3782 <p> Please ensure that you have set your browser's character set to the one of the
3783 language file you have selected on phpMyAdmin's start page.
3784 Alternatively, you can try the auto detection mode that is supported by the
3785 recent versions of the most browsers.</p>
3788 <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
3791 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3792 Netscape and Mozilla do not have this problem.</p>
3795 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3796 I cannot manage two servers: I log in to the first one, then the other one,
3797 but if I switch back to the first, I have to log in on each operation.</a></h4>
3803 but nothing happens after that, only a blank screen.</a></h4>
3814 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3819 address and you are starting
3821 containing a domain name, or the reverse situation.</li>
3822 <li>Security settings in IE and/or Microsoft Security Center are
3823 too high, thus blocking scripts execution.</li>
3824 <li>The Windows Firewall is blocking Apache and MySQL. You must
3828 </ul>
3831 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3832 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3833 installed in their Firefox is causing the problem.</p>
3837 clause is generated when I browse a table.</a></h4>
3838 <p> This happens only when both of these conditions are met: using the
3848 </a></h4>
3849 <p>
3850 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3851 specifying a wrong column-type.<br />
3852 Common errors include:
3853 </p>
3854 <ul>
3857 </ul>
3858 <p>
3859 Also, look at the syntax chapter in the MySQL manual to confirm that your
3860 syntax is correct.
3861 </p>
3865 columns and
3866 phpMyAdmin generates only one index with those two columns.
3867 </a></h4>
3868 <p>
3869 This is the way to create a multi-columns
3870 index. If you want two indexes, create the first one when creating the
3871 table, save, then display the table properties and click the Index link to
3872 create the other index.
3873 </p>
3877 <p>
3878 Since version 2.2.3, you have a checkbox for each column that can be null.
3880 column's value. Since version 2.5.5, you have to use the checkbox to get
3882 a literal NULL in the column, and not a NULL value (this works in PHP4).
3883 </p>
3888 <p> Click on a database or table name in the left frame, the properties will be
3890 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3891 statements that can be used to recreate your database/table.
3892 <br /><br />
3894 transmit the resulting dump to your station. Depending on your PHP
3895 configuration, you will see options to compress the dump. See also the
3897 configuration variable.<br /><br />
3900 this document.</p>
3905 </a></h4>
3907 <p> Click on a database name in the left frame, the properties will be
3909 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3911 the path to your dump filename, or use the Browse button. Then click Go.
3912 <br /><br />
3914 that you upgrade to take advantage of the new features.
3915 <br /><br />
3917 in this document.
3918 </p>
3923 <p> Here is an example with the tables persons, towns and countries, all
3925 table, create it as explained in the configuration section. Then create the
3926 example tables:</p>
3928 <pre>
3929 CREATE TABLE REL_countries (
3930 country_code char(1) NOT NULL default '',
3931 description varchar(10) NOT NULL default '',
3932 PRIMARY KEY (country_code)
3933 ) TYPE=MyISAM;
3935 INSERT INTO REL_countries VALUES ('C', 'Canada');
3937 CREATE TABLE REL_persons (
3938 id tinyint(4) NOT NULL auto_increment,
3939 person_name varchar(32) NOT NULL default '',
3941 country_code char(1) NOT NULL default '',
3942 PRIMARY KEY (id)
3943 ) TYPE=MyISAM;
3945 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3946 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3948 CREATE TABLE REL_towns (
3950 description varchar(30) NOT NULL default '',
3951 PRIMARY KEY (town_code)
3952 ) TYPE=MyISAM;
3954 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3955 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3956 </pre>
3962 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3966 </ul>
3974 <li>In the columns row, choose persons.person_name and click the
3976 <li>Do the same for towns.description and countries.descriptions in the
3979 the correct joins have been generated</li>
3981 </ul>
3985 <p>
3986 Starting from the previous example, create the pma_table_info as explained
3987 in the configuration section, then browse your persons table,
3988 and move the mouse over a town code or country code.
3989 <br /><br />
3990 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3991 enables: drop-down list of possible values.
3992 </p>
3995 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3996 <p>
3999 <br /><br />
4000 Then you need to think about your schema layout. Which tables will go on
4001 which pages?
4002 </p>
4003 <ul>
4009 page and click Go. If you like, you
4011 linked tables onto the new page.</li>
4012 <li>Select the name of the new page (making sure the Edit radio button
4013 is selected) and click Go.</li>
4015 Coordinates are relative; your diagram will
4016 be automatically scaled to fit the page. When initially placing tables
4017 on the page, just pick any coordinates -- say, 50x50. After clicking
4019 position the element correctly.</li>
4021 first be sure to click the Save
4022 button beneath the list of tables and coordinates, to save any changes
4023 you made there. Then scroll all the way down, select the
4025 you want, and click Go.</li>
4026 <li>Internet Explorer for Windows may suggest an incorrect filename when
4031 browsers on Windows, do not have this problem.</li>
4032 </ul>
4036 columns!</a></h4>
4038 <p> No, it's MySQL that is doing
4044 underscores in the database name?</a></h4>
4046 <p> If you do not put a backslash before the underscore, this is a wildcard
4049 john2db ...<br /><br />
4051 If you put a backslash before the underscore, it means that the database
4052 name will have a real underscore.</p>
4056 statistics pages?</a></h4>
4067 if it already exists during the import. It does NOT drop the table after
4068 your export, it only affects the import file.</li>
4070 Otherwise, you may get an error if the table name exists but has a
4071 different structure.</li>
4073 (if any) will be included in backup.</li>
4075 column and table names formed with special characters are protected.</li>
4077 types set in the pmadb in the dump as
4079 </li>
4080 </ul>
4085 command, for better documentation (but resulting file is bigger).</li>
4087 once the INSERT verb and the table name.</li>
4090 </li>
4092 more info is provided in the
4094 but basically with this selected, invalid values are adjusted and
4095 inserted rather than causing the entire statement to fail.</li>
4096 </ul>
4100 in its name.</a></h4>
4103 is the normal way to reference a database and table name. Worse, MySQL
4104 will usually let you create a database with a dot, but then you cannot
4105 work with it, nor delete it.</p>
4111 <p>
4112 To use SQL Validator, you need PHP with
4118 module.
4119 </p>
4121 <p>
4127 usage.
4128 </p>
4130 <p>
4131 If you use the Validator, you should be aware that any
4133 submit will be stored anonymously (database/table/column names,
4134 strings, numbers replaced with generic values). The Mimer
4137 We utilize it as free SOAP service.
4138 </p>
4142 it, but MySQL says "BLOB column '...' used in key specification without
4145 <p> The right way to do this, is to create the column without any indexes,
4147 dialog. On this page, you will be able to choose your BLOB column, and
4148 set a size to the index, which is the condition to create an index on
4149 a BLOB column.</p>
4153 editing fields?</a></h4>
4155 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4156 with many editing fields (table structure changes, row editing, etc.)
4157 (must be enabled in configuration - see.
4159 You can also have a look at the directive
4161 ('vertical') and see if this eases up editing for you.</p>
4165 WTF is this feature then useful for?</a></h4>
4167 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4168 on them. Otherwise you could just put a comment on the column. Because entering
4169 your own mimetype will cause serious syntax checking issues and validation,
4170 this introduces a high-risk false-user-input situation. Instead you have to
4171 initialize mimetypes using functions or empty mimetype definitions.<br />
4172 Plus, you have a whole overview of available mimetypes. Who knows all those
4173 mimetypes by heart so he/she can enter it at will?</p>
4177 can't I see any bookmarks below the query box? What is this variable for?
4178 </a></h4>
4180 <p> Any query you have executed can be stored as a bookmark on the page where the
4181 results are displayed. You will find a button labeled 'Bookmark this query'
4182 just at the end of the page.<br />
4183 As soon as you have stored a bookmark, it is related to the database you run
4184 the query on. You can now access a bookmark dropdown on each page, the query
4185 box appears on for that database.<br /><br />
4187 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4191 aware of that you HAVE to create a valid query, otherwise your query won't be
4192 even able to be stored in the database.<br />
4194 for your query will remain the way it is, but will be stripped of the /**/
4195 chars. So you can use:<br /><br />
4199 which will be expanded to<br /><br />
4203 in your query, where VARIABLE is the string you entered in the input box. If
4204 an empty string is provided, no replacements are made.<br /><br />
4206 A more complex example. Say you have stored this query:<br /><br />
4208 <br /><br />
4211 the full query will be:<br /><br />
4214 <br /><br />
4218 spaces inserted there
4219 will be later also inserted as spaces in your query and may lead to unexpected
4220 results especially when
4222 Your initial query which is going to be stored as a bookmark has to yield at
4223 least one result row so
4224 you can store the bookmark. You may have that to work around using well
4228 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4229 include exported table?</a></h4>
4231 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4232 document should look like following one (assuming you have table
4235 <pre>
4236 \documentclass{article} % or any class you want
4237 \usepackage{longtable} % for displaying table
4238 \begin{document} % start of document
4239 \include{table} % including exported table
4240 \end{document} % end of document
4241 </pre>
4245 access them.
4246 </a></h4>
4249 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4250 enable users to see all the database names.
4253 So if your users do not need those privileges, you can remove them and their
4254 databases list will shorten.</p>
4258 possible values for a column, based on some foreign table?</a></h4>
4260 <p> You have to setup appropriate links between the tables, and also
4264 foreign table, a drop-down list of values will be available.
4265 You will see two lists of values, the first list containing the key
4266 and the display column, the second list containing the display column
4267 and the key. The reason for this is to be able to type the first
4268 letter of either the key or the display column.<br /><br />
4270 For 100 values or more, a distinct window will appear, to browse foreign
4271 key values and choose one. To change the default limit of 100, see
4272 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4276 automatically when entering Browse mode for a table?</a></h4>
4278 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4279 </p>
4283 Excel files, how can I enable that?</a></h4>
4285 <p> You can use
4287 which works out of the box, but phpMyAdmin supports direct export
4288 to Microsoft Excel version 97 and newer. For this to work, you need to set
4293 <pre>
4294 cd phpMyAdmin
4295 mkdir tmp
4296 chmod o+rwx tmp
4297 </pre>
4301 what happens to my column comments stored in pmadb?</a></h4>
4303 <p> Automatic migration of a table's pmadb-style column comments to the native
4304 ones is done whenever you enter Structure page for this table.</p>
4309 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4310 <ul>
4313 later)</li>
4316 </ul>
4320 <ol>
4321 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4322 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4323 <li>When you insert or update a row in this table, put a checkmark on the "Upload to BLOB repository" optional choice; otherwise, the upload will be done directly in your LONGBLOB column instead of the repository.</li>
4324 <li>Finally when you browse your table, you'll see in your column a link to stream your data, for example "View image". A header containing the correct MIME-type will be sent to your browser; this MIME-type was stored at upload time but in case it's incorrect, it's possible to edit it by clicking on the displayed MIME-type.</li>
4325 </ol>
4330 <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>
4336 <p>
4337 In all places where phpMyAdmin accepts format strings, you can use
4340 expanded variables depend on a context (eg. if you don't have chosen
4341 table, you can not get table name), but following variables can be used:
4342 </p>
4343 <dl>
4349 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4360 </dl>
4367 <p> Our Bug Tracker is located at
4369 under the Bugs section.<br /><br />
4371 But please first discuss your bug with other users:<br />
4373 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4374 </p>
4378 existing language, where do I start?</a></h4>
4380 <p> Always use latest Git version of the po file to translate. You can optionally
4382 server</a> where you can also get the latest po files and merge them
4383 with your translations. For creating a new translation simply use
4387 to do this) or ask on the mailing list to add the translation to the web
4388 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Gettext_for_translators">our wiki</a>.
4389 </p>
4390 <p>
4391 Please note that we try not to use HTML entities like &eacute; in
4392 the translations, since we define the right character set in the file.
4393 With HTML entities, the text on JavaScript messages would not
4394 display correctly.
4395 However there are some entities that need to be there: quotes,
4396 non-breakable spaces, ampersands, less than, greater than.
4397 </p>
4398 <p>
4399 You can then put your translations, as a zip file to avoid losing special
4400 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4401 </p>
4402 <p>
4403 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4404 list, because this is where we ask for translations of new messages.
4405 </p>
4407 <p>
4408 Documentation is being translated using po4a and gettext (see
4410 for existing translations). To start, checkout
4411 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4412 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4413 and translate it online. If your language is missing, just contact
4415 you prefer to directly translate the po files, please put updated ones into our
4416 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4417 </p>
4421 phpMyAdmin. How should I proceed?</a></h4>
4426 <tt>git clone
4427 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4428 </li>
4430 <li>generate patch with your changes:
4432 </li>
4435 tracker of the phpMyAdmin project</a>.
4436 </li>
4437 </ol>
4439 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4441 <p> Write access to the repository is granted only to experienced developers who
4442 have already contributed something useful to phpMyAdmin.<br />
4448 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4450 <p> Please refer to
4451 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4452 </p>
4457 <p> If you use Apache web server, phpMyAdmin exports information about
4458 authentication to the Apache environment and it can be used in Apache logs.
4459 Currently there are two variables available:
4460 </p>
4461 <dl>
4463 <dd>User name of currently active user (he does not have to be logged
4464 in).</dd>
4471 </dl>
4472 <p>
4474 </p>
4475 <pre>
4478 </pre>
4479 <p>
4480 You can then use any log analyzing tools to detect possible break-in
4481 attempts.
4482 </p>
4488 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4489 It allows you to connect to local as well as remote servers. This requires you to enter
4490 server host name, username, password, port and the name of the database. Therefore you can
4491 now synchronize your databases placed on the same server or some remote server.
4492 </p>
4494 <p>
4495 This feature is helpful for developers who need to replicate their
4496 database’s structure as well as data. Moreover, this feature not only
4497 helps replication but also facilitates the user to keep his/her database
4498 in sync with another database. Other than the full database, certain
4499 tables of the databases can also be synchronized.
4500 </p>
4502 <p>
4503 You need to fill in the host name of the server, the username and
4504 password of an user account already there in MySQL. Port is by default
4505 populated with 3306 (MySQL default port). Then the name of the database
4506 should be mentioned at the end. All the information other than the port
4507 needs to be filled explicitly for the source as well as target servers.
4508 </p>
4510 <p>
4511 After successfully passing through the authentication phase, the source and
4512 target database table names will be displayed. It will be a tabular
4513 representation.
4514 </p>
4516 <p>
4517 On the left, are listed the source database table names. Some of the
4519 are only present in source database and they need to be added to the
4520 target database in order to synchronize the target database. The tables
4522 target database.
4523 </p>
4525 <p>
4526 On the right, are listed the target database table names. There are few
4528 means that these tables are to be created in target database in order to
4529 synchronize target database with source database. Some table names
4531 only present in target database and they will remain unchanged in the
4532 target database. The column in the middle shows the difference between
4533 the source and target corresponding tables.
4534 </p>
4536 <p>
4538 letters, indicating that either Structure or Data are not up to date. By
4539 clicking on them, they will turn grey, what means that they will be synchronized.
4540 </p>
4542 <!-- DEVELOPERS -->
4545 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4546 great features have been written by other people and you too can help to
4547 make phpMyAdmin a useful tool.</p>
4549 <p> If you're planning to contribute source, please read the following
4550 information:</p>
4556 it free from other code.<br />
4557 Commonly used functions should be added to
4560 <li>Obviously, you're free to use whatever coding style you want. But
4561 please try to keep your code as simple as possible: beginners are
4562 using phpMyAdmin as an example application.<br />
4563 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4564 compliant on one hand, they fit the
4567 coding standards</a>
4568 on the other hand. Please pay attention to this.</li>
4569 <li>Please enable showing PHP errors and warnings by the
4571 configuration directive.</li>
4572 <li>Please try to keep up the file-naming conventions. Table-related stuff
4575 <li>Please use gettext wrappers around all messages
4578 script. To use translated messages, call
4580 Gettext.</li>
4584 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4585 better debug and profile their code.<br />
4586 Please see the
4588 options for more information.<br />
4589 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4590 lost during its re-entry into Earth's atmosphere and in memory of the
4591 brave men and women who gave their lives for the people of Earth.</li>
4592 </ul>
4596 <pre>
4607 </pre>
4609 <p>
4610 This program is free software; you can redistribute it and/or modify
4611 it under the terms of the GNU General Public License version 2,
4612 as published by the Free Software Foundation.
4613 </p>
4615 <p>
4616 This program is distributed in the hope that it will be useful,
4617 but WITHOUT ANY WARRANTY; without even the implied warranty of
4618 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4619 GNU General Public License for more details.
4620 </p>
4622 <p>
4623 You should have received a copy of the GNU General Public License
4624 along with this program; if not, write to the Free Software
4626 </p>
4628 <!-- CREDITS -->
4633 <ul>
4636 <ul>
4639 </ul></li>
4642 <ul>
4647 </ul></li>
4650 <ul>
4656 </ul></li>
4659 <ul>
4661 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4662 generate XHTML1.0 and CSS2 compliant codes</li>
4665 </ul></li>
4668 <ul>
4676 </ul></li>
4679 <ul>
4684 </ul></li>
4687 <ul>
4690 </ul></li>
4693 <ul>
4695 </ul></li>
4698 <ul>
4701 </ul></li>
4704 <ul>
4708 </ul></li>
4711 <ul>
4714 </ul></li>
4717 <ul>
4724 </ul></li>
4727 <ul>
4731 </ul></li>
4734 <ul>
4740 </ul></li>
4743 (http://sf.net/projects/phpmysqlformgen/)
4744 <ul>
4746 </ul></li>
4749 <ul>
4751 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4756 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4760 </ul></li>
4763 <ul>
4765 </ul></li>
4768 <ul>
4770 </ul></li>
4773 <ul>
4775 </ul></li>
4778 <ul>
4779 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4780 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4781 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4782 </ul></li>
4785 <ul>
4787 </ul></li>
4790 <ul>
4792 </ul></li>
4795 <ul>
4797 </ul></li>
4800 <ul>
4803 </ul></li>
4806 <ul>
4809 </ul></li>
4812 <ul>
4814 </ul></li>
4817 <ul>
4820 </ul></li>
4822 <li>Ivan A Kirillov
4823 <ul>
4825 </ul></li>
4828 <ul>
4830 </ul></li>
4833 <ul>
4835 </ul></li>
4838 <ul>
4840 </ul></li>
4843 <ul>
4845 </ul></li>
4848 <ul>
4850 </ul></li>
4853 <ul>
4855 </ul></li>
4857 <li>Barrie Leslie
4858 <ul>
4860 </ul></li>
4862 </ul>
4864 <p>
4865 And also to the following people who have contributed minor changes,
4866 enhancements, bugfixes or support for a new language since version 2.1.0:
4867 </p>
4869 <p>
4870 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4871 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4872 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4873 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4875 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4876 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4877 Luís V., Martijn W. van der Lee,
4878 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4880 </p>
4885 <p>
4886 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4887 to create a web-based interface to MySQL using PHP3. Although I have not
4888 used any of his source-code, there are some concepts I've borrowed from
4889 him. phpMyAdmin was created because Peter told me he wasn't going to
4890 further develop his (great) tool.
4891 </p>
4892 <p>
4893 Thanks go to
4894 </p>
4895 <ul>
4897 code for the check when dropping a table or database. He also suggested
4898 that you should be able to specify the primary key on tbl_create.php3. To
4899 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4900 well as a bug-report. Plus many smaller improvements.
4901 </li>
4903 were introduced in 1.3.0 (including quite significant ones like the
4904 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4905 bug-fixes and help.
4906 </li>
4908 language-independent by outsourcing the strings to a separate file. He
4909 also contributed the French translation.
4910 </li>
4912 tbl_select.php3, a feature to display only some columns from a table.
4913 </li>
4915 functions in tbl_change.php3. He also added the
4917 </li>
4919 servers and is a regular contributor for bug-fixes.
4920 </li>
4922 features for 2.0.6.
4923 </li>
4924 </ul>
4925 <p>
4926 The following people have contributed minor changes, enhancements, bugfixes
4927 or support for a new language:
4928 </p>
4929 <p>
4930 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4931 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4932 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4933 G. Wieggers.
4934 </p>
4935 <p>
4936 And thanks to everyone else who sent me email with suggestions, bug-reports
4937 and or just some feedback.
4938 </p>
4944 <ul>
4946 - the default name of Apache's directory-level configuration file.</li>
4950 - a software application that enables a user to display and interact with
4951 text, images, and other information typically located on a web page at a
4952 website on the World Wide Web.</li>
4954 - a free software/open source data compression algorithm and program
4955 developed by Julian Seward.</li>
4957 - an important World Wide Web technology that enables a client web browser
4958 to request data from a program executed on the Web server.</li>
4960 - a log or record of changes made to a project.</li>
4962 - a computer system that accesses a (remote) service on another computer
4963 by some kind of network.</li>
4965 - a set of data values of a particular simple type, one for each row of
4966 the table.</li>
4968 - a packet of information sent by a server to a World Wide Web browser
4969 and then sent back by the browser each time it accesses that server.</li>
4971 - Comma-separated values</li>
4974 - an organized collection of data.</li>
4977 - a PHP module that extends PHP with additional functionality.</li>
4979 - a list of commonly asked question and there answers.</li>
4981 - one part of divided data/columns.</li>
4983 - a field or group of fields in a database record that point to a key
4984 field or group of fields forming a key of another database record in some
4985 (usually different) table.</li>
4987 - the free PDF library</li>
4989 GD Graphics Library</a> - a library by Thomas Boutell and others for
4990 dynamically manipulating images.</li>
4993 - gzip is short for GNU zip, a GNU free software file compression
4994 program.</li>
4996 - any machine connected to a computer network, a node that has a hostname.</li>
4998 - the unique name by which a network attached device is known on a network.</li>
5000 (HyperText Transfer Protocol)</a>
5001 - the primary method used to transfer or convey information on the World
5002 Wide Web.</li>
5005 additional security measures.</li>
5006 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5007 - a set of Internet-based services for servers using Microsoft Windows.</li>
5009 - a feature that allows quick access to the rows in a table.</li>
5011 - a data-oriented protocol used by source and destination hosts for
5012 communicating data across a packet-switched internetwork.</li>
5014 - a unique number that devices use in order to identify and communicate
5015 with each other on a network utilizing the Internet Protocol standard.</li>
5017 (Internet Server Application Programming Interface)</a>
5018 - the API of Internet Information Services (IIS).</li>
5020 - a business or organization that offers users access to the Internet and related services.</li>
5022 - a most commonly used standard method of lossy compression for
5023 photographic images.</li>
5029 - line of personal computers is designed, developed, manufactured, and
5030 marketed by Apple Computer.</li>
5031 <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>
5032 - the operating system which is included with all currently shipping Apple
5033 Macintosh computers in the consumer and professional markets.</li>
5035 - a cryptographic library.</li>
5037 - the MCrypt PHP extension.</li>
5038 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5039 - an Internet Standard for the format of e-mail.</li>
5041 - some sort of extension for the Apache Webserver.</li>
5043 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5044 Management System (DBMS).</li>
5046 - the improved MySQL client PHP extension.</li>
5048 - the MySQL client PHP extension.</li>
5050 - open standard for office documents.</li>
5051 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5052 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5054 (Portable Document Format)</a>
5055 - a file format developed by Adobe Systems for representing two
5056 dimensional documents in a device independent and resolution independent
5057 format.</li>
5059 - the PHP Extension and Application Repository.</li>
5061 - the perl-compatible regular expression functions for PHP</li>
5063 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5064 programming language used mainly for developing server-side applications
5065 and dynamic web content, and more recently, a broader range of software
5066 applications.</li>
5068 - a connection through which data is sent and received.</li>
5070 - Request for Comments (RFC) documents are a series of memoranda
5071 encompassing new research, innovations, and methodologies applicable to
5072 Internet technologies.</li>
5076 - represents a single, implicitly structured data item in a table.</li>
5078 - a computer system that provides services to other computing
5079 systems over a network.</li>
5080 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
5081 - handlers for different table types</li>
5083 - a form of inter-process communication.</li>
5085 Sockets Layer)</a>
5086 - a cryptographic protocol which provides secure communication on the Internet.</li>
5088 - Structured Query Language</li>
5090 - a set of data elements (cells) that is organized, defined and stored as
5091 horizontal rows and vertical columns where each item can be uniquely
5092 identified by a label or key or by it?s position in relation to other items.</li>
5095 - a type of archive file format: the Tape ARchive format.</li>
5097 - one of the core protocols of the Internet protocol suite.</li>
5101 - a sequence of characters, conforming to a standardized format, that is
5102 used for referring to resources, such as documents and images on the
5103 Internet, by their location.</li>
5105 - A computer (program) that is responsible for accepting HTTP requests
5106 from clients and serving them Web pages.</li>
5108 - a W3C-recommended general-purpose markup language for creating
5109 special-purpose markup languages, capable of describing many different
5110 kinds of data.</li>
5112 - a popular data compression and archival format.</li>
5114 - an open-source, cross-platform data compression library by Jean-loup
5115 Gailly and Mark Adler.</li>
5116 </ul>
5117 </div>
5120 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5123 <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>
5124 </ul>
5126 </body>
5127 </html>