| blob | b2b5f085a7936a985b3b89fed6b25c19597cb8cc |
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 default), you should install 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 </ul>
88 </li>
91 </ul>
93 <!-- INTRODUCTION -->
96 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
97 a single database. To accomplish the latter you'll need a properly set up
98 MySQL user who can read/write only the desired database. It's up to you to
99 look up the appropriate part in the MySQL manual.
100 </p>
105 <li>create, copy, drop, rename and alter databases, tables, columns and
106 indexes</li>
107 <li>maintenance server, databases and tables, with proposals on server
108 configuration</li>
109 <li>execute, edit and bookmark any
111 batch-queries</li>
114 </li>
121 OpenDocument Text and Spreadsheet,
123 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
124 </li>
125 <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>
129 <li>using Query-by-example (QBE), create complex queries automatically
130 connecting required tables</li>
132 your Database layout</li>
134 <li>transform stored data into any format using a set of predefined
135 functions, like displaying BLOB-data as image or download-link
136 </li>
143 </li>
144 <li>synchronize two databases residing on the same as well as remote servers
146 </li>
148 </ul>
151 <p> Many people have difficulty
152 understanding the concept of user management with regards to phpMyAdmin. When
153 a user logs in to phpMyAdmin, that username and password are passed directly
154 to MySQL. phpMyAdmin does no account management on its own (other than
155 allowing one to manipulate the MySQL user account information); all users
156 must be valid MySQL users.</p>
165 <!-- INSTALLATION -->
173 </ol>
176 phpMyAdmin does not apply any special security methods to the MySQL database
177 server. It is still the system administrator's job to grant permissions on
179 be used for this.
180 </p>
188 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
189 before uploading them to your server, as PHP seems not to like
194 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
195 Downloads page. Some kits contain only the English messages,
196 others contain all languages in UTF-8 format (this should be fine
197 in most situations), others contain all
198 languages and all character sets. We'll assume you chose a kit whose
200 </li>
201 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
203 document root. If you don't have direct access to your document root,
204 put the files in a directory on your local machine, and, after step 4,
205 transfer the directory on your web server using, for example, ftp.</li>
206 <li>Ensure that all the scripts have the appropriate owner (if PHP is
207 running in safe mode, having some scripts with an owner different
208 from the owner of other scripts will be a
213 <li>Now you must configure your installation. There are two methods that
214 can be used. Traditionally, users have hand-edited a copy of
216 provided for those who prefer a graphical installation. Creating a
217 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
218 <ul><li>To manually create the file, simply use your text editor to
221 file) in the main (top-level) phpMyAdmin directory (the one
225 default value is okay for a particular setting, there is no
227 few directives to get going, a simple configuration may look
228 like this:
229 <pre>
230 <?php
231 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
233 $i=0;
234 $i++;
235 $cfg['Servers'][$i]['auth_type'] = 'cookie';
236 ?>
237 </pre>
238 Or, if you prefer to not be prompted every time you log in:
239 <pre>
240 <?php
242 $i=0;
243 $i++;
244 $cfg['Servers'][$i]['user'] = 'root';
245 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
246 $cfg['Servers'][$i]['auth_type'] = 'config';
247 ?>
248 </pre>
249 For a full explanation of possible configuration values, see the
255 directory. This is a security measure. On a Linux/Unix system you
256 can use the following commands:
257 <pre>
258 cd phpMyAdmin
259 mkdir config # create directory for saving
260 chmod o+rw config # give it world writable permissions
261 </pre>
262 And to edit an existing configuration, copy it over first:
263 <pre>
264 cp config.inc.php config/ # copy current configuration for editing
265 chmod o+w config/config.inc.php # give it world writable permissions
266 </pre>
267 On other platforms, simply create the folder and ensure that your
276 the webserver does not have the proper permissions you may see the
278 config/</tt> directory exists and has the proper permissions -
280 and upload (via FTP or some similar means) to the proper location.<br /><br />
282 Once the file has been saved, it must be moved out of the <tt>
283 config/</tt> directory and the permissions must be reset, again
284 as a security measure:
285 <pre>
286 mv config/config.inc.php . # move file to current directory
287 chmod o-rw config.inc.php # remove world read and write permissions
288 rm -rf config # remove not needed directory
289 </pre>
290 Now the file is ready to be used. You can choose to review or edit
291 the file with your favorite editor, if you prefer to set some
292 advanced options which the setup script does not provide.</li></ul></li>
293 <li>If you are using the
295 protect the phpMyAdmin installation directory because using
296 config does not require a user to
297 enter a password to access the phpMyAdmin installation. Use of an alternate
298 authentication method is recommended, for example with
306 in your browser. phpMyAdmin should now display a welcome screen
307 and your databases, or a login dialog if using
309 authentication mode.</li>
312 Apache you can use supplied .htaccess file in that folder, for other
313 webservers, you should configure this yourself. Such configuration
314 prevents from possible path exposure and cross side scripting
315 vulnerabilities that might happen to be found in that code.</li>
316 <li>
317 It is generally good idea to protect public phpMyAdmin installation
318 against access by robots as they usually can not do anything good
320 your webserver or limit access by web server configuration. You can
323 </li>
324 </ol>
328 <p> For a whole set of new features (bookmarks, comments,
330 tracking mechanism,
332 transformation, etc.) you need to create a set of special tables. Those
333 tables can be located in your own database, or in a central database for a
334 multi-user installation (this database would then be accessed by the
335 controluser, so no other user should have rights to it).</p>
345 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
346 that you may need special (administrator) privileges to create the database
347 and tables, and that the script may need some tuning, depending on the
348 database name.</p>
353 section</a>. You will also need to have a controluser with the proper rights
360 unpacked one. Configuration files from old versions may
361 require some tweaking as some options have been changed or removed; in
363 so you better remove it from your file and just use the default one.
365 statement that you might find near the end of your configuration file.</p>
369 is version-specific.</p>
372 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
373 you should run the SQL script found in
380 where you want to give users access to their own database and don't want
381 them to play around with others.<br />
382 Nevertheless be aware that MS Internet Explorer seems to be really buggy
384 in this area!<br />
387 that your user/password pair are not in clear in the configuration file.
388 </li>
391 authentication modes are more secure: the MySQL login information does
392 not need to be set in the phpMyAdmin configuration file (except possibly
394 However, keep in mind that the password travels in plain text, unless
395 you are using the HTTPS protocol.<br />
396 In cookie mode, the password is stored, encrypted with the blowfish
397 algorithm, in a temporary cookie.</li>
409 file under the
411 $cfg['Servers'][$i]['controluser']</a></tt> and
416 only an example: use something else in your file!</b> Input these
417 statements from the phpMyAdmin SQL Query window or mysql command–line
418 client.<br />
420 if it's not the same as the MySQL server's one.
422 <pre>
423 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
424 GRANT SELECT (
425 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
426 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
427 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
428 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
429 Execute_priv, Repl_slave_priv, Repl_client_priv
430 ) ON mysql.user TO 'pma'@'localhost';
431 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
432 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
433 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
434 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
436 If you want to use the many new relation and bookmark features:
438 <pre>
440 </pre>
446 on a set of particular databases. Normally you shouldn't give global
447 privileges to an ordinary user, unless you understand the impact of those
448 privileges (for example, you are creating a superuser).<br />
452 <pre>
453 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
454 </pre>
456 What the user may now do is controlled entirely by the MySQL user
457 management system.<br />
459 authentication mode, you don't need to fill the user/password fields
461 array.</li>
462 </ul>
467 method and allows you to log in as any valid MySQL user.</li>
468 <li>Is supported with most PHP configurations. For
481 mode.</li>
482 </ul>
486 <ul><li>You can use this method as a replacement for the
488 (for example, if you're running
490 <li>Obviously, the user must enable cookies in the browser, but this is
491 now a requirement for all authentication modes.</li>
492 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
493 with the same username.</li>
494 <li>If you want to log in to arbitrary server see
499 not required.</li>
500 </ul>
504 <ul><li>This mode is a convenient way of using credentials from another
505 application to authenticate to phpMyAdmin.</li>
506 <li>The other application has to store login information into
507 session data.</li>
509 section.</li>
510 </ul>
513 <ul><li>This mode is the less secure one because it requires you to fill the
515 $cfg['Servers'][$i]['user']</a> and
517 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
518 can read your config.inc.php can discover your username and password).
519 <br />
526 is an entry explaining how to protect your configuration file.</li>
527 <li>For additional security in this mode, you may wish to consider the Host
528 authentication
530 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
532 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
533 directives.</li>
534 <li>Unlike cookie and http, does not require a user to log in when first
535 loading the phpMyAdmin site. This is by design but could allow any
536 user to access your installation. Use of some restriction method is
538 HTTP-AUTH directive or disallowing incoming HTTP requests at
539 one’s router or firewall will suffice (both of which
540 are beyond the scope of this manual but easily searchable with Google).</li>
541 </ul>
543 <p>
544 The Swekey is a low cost authentication USB key that can be used in
545 web applications.<br /><br />
546 When Swekey authentication is activated, phpMyAdmin requires the
547 users's Swekey to be plugged before entering the login page (currently
548 supported for cookie authentication mode only). Swekey Authentication is
549 disabled by default.<br /><br />
551 </p>
552 <pre>
553 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
554 </pre>
555 <p>
557 each user with their Swekey Id. It is important to place this file outside
558 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
560 users' information.<br /><br />
561 If you want to purchase a Swekey please visit
563 since this link provides funding for phpMyAdmin.
564 </p>
565 <!-- CONFIGURATION -->
569 users:</span> PHP does not seem to like
573 before saving a script you have modified.</p>
578 section to create one. This file only needs to contain the parameters you want to
579 change from their corresponding default value in
582 <p> The parameters which relate to design (like colors) are placed in
585 your site specific code to be included on start and end of each page.</p>
589 (with full path) to your phpMyAdmin installation's directory.
592 some web servers are case–sensitive.
595 Starting with version 2.3.0, it is advisable to try leaving this
596 blank. In most cases phpMyAdmin automatically detects the proper
597 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
598 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
599 A good test is to browse a table, edit a row and save it. There should
600 be an error message if phpMyAdmin is having trouble auto–detecting
601 the correct value. If you get an error that this must be set or if
602 the autodetect code fails to detect your path, please post a bug
603 report on our bug tracker so we can improve the code.</dd>
607 with master / foreign – tables (see
609 <br />
610 If you tried to set this up and it does not work for you, have a look on
612 use it. You will find a link that will analyze why those features have
613 been disabled.<br />
614 If you do not want to use those features set this variable to
618 <dd>A warning is displayed on the main page if Suhosin is detected.
620 from appearing.</dd>
623 <dd>Disable the default warning that is displayed if mcrypt is missing for
624 cookie authentication.
626 from appearing.</dd>
630 domain to call phpMyAdmin inside a frame, and is a potential security
631 hole allowing cross-frame scripting attacks.</dd>
635 algorithm to encrypt the password.<br />
637 passphrase of your choice. It will be used internally by the blowfish
638 algorithm: you won’t be prompted for this passphrase. There is
639 no maximum length for this secret.<br /><br />
641 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
642 makes a bit weaker security as this generated secret is stored in
643 session and furthermore it makes impossible to recall user name from
644 cookie.</dd>
648 MySQL servers. Therefore, a
650 been added which contains the login information for the different servers.
651 The first
653 contains the hostname of the first server, the second
655 the hostname of the second server, etc. In
657 server definition, however you can put as many as you need in
659 have to define all settings, just those you need to change).</dd>
663 $i-th MySQL-server. E.g. localhost.</dd>
668 ignores this port number and connects with the socket, so if you want
669 to connect to a port different from the default port, use
672 </dd>
676 To determine the correct socket, check your MySQL configuration or, using the
678 Among the resulting information displayed will be the socket used.</dd>
681 <dd>Whether to enable SSL for connection to MySQL server.
682 </dd>
685 <dd>What type connection to use with the MySQL server. Your options are
687 is nearly guaranteed to be available on all MySQL servers, while
688 sockets are not supported on some platforms.<br /><br />
690 To use the socket mode, your MySQL server must be on the same machine
691 as the Web server.</dd>
694 <dd>What php MySQL extension to use for the connection. Valid options are:
695 <br /><br />
698 The classic MySQL extension. This is the recommended and default
699 method at this time.<br /><br />
702 The improved MySQL extension. This extension became available
703 with php 5.0.0 and is the recommended way to connect to a server
707 <dd>Whether to use a compressed protocol for the MySQL server connection
708 or not (experimental).<br />
714 </dt>
716 all relational features (see
718 and, for a MySQL server previous to 4.1.2 or running with
721 authentication mode).<br /><br />
724 cookie authentication modes (or 'config'
725 authentication mode since phpMyAdmin 2.2.1), you need to supply the
730 This account is used to check what databases the user will see at
731 login.<br />
735 In phpMyAdmin versions before 2.2.5, those were called
739 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
740 <dd>Whether config or cookie or
742 should be used for this server.
744 is the plain old way: username and password are stored in
746 <li>'cookie' authentication mode
748 2.2.3 allows you to log in as any valid MySQL user with the
749 help of cookies. Username and password are stored in
750 cookies during the session and password is deleted when it
751 ends. This can also allow you to log in in arbitrary server if
752 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
753 </li>
754 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
755 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
756 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
757 <li>'signon' authentication mode
759 as introduced in 2.10.0 allows you to log in from prepared PHP
760 session data. This is useful for implementing single signon
761 from another application. Sample way how to seed session is in
767 </ul>
770 for more information.
771 </dd>
773 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
774 </dt>
775 <dd>
776 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
777 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
778 specified in your configuration, a string combined of "phpMyAdmin " and either
781 </dd>
783 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
784 </dt>
785 <dd>
787 names for hardware authentication. Leave empty to deactivate this feature.
788 </dd>
792 </dt>
793 <dd>
794 When using auth_type = 'config', this is the user/password-pair
795 which phpMyAdmin will use to connect to the
796 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
797 cookie authentication is used and should be empty.</dd>
799 <span
801 </dt>
802 <dd>
803 Allow attempt to log in without password when a login with password
804 fails. This can be used together with http authentication, when
805 authentication is done some other way and phpMyAdmin gets user name
806 from auth and uses empty password for connecting to MySQL. Password
807 login is still tried first, but as fallback, no password method is
808 tried.</dd>
811 </dt>
812 <dd>
813 If set to a (an array of) database name(s), only this (these) database(s)
814 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
815 database(s) name(s) may contain MySQL wildcards characters
819 This setting is an efficient way to lower the server load since the
820 latter does not need to send MySQL requests to build the available
822 privileges rules of the MySQL database server</span>. If set, it just
823 means only these databases will be displayed but
825 <br /><br />
827 An example of using more that one database:
829 <br /><br />
831 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
832 databases in the left frame, so that you can individually arrange your databases.<br />
833 If you want to have certain databases at the top, but don't care about the others, you do not
834 need to specify all other databases. Use:
836 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
837 order.</dd>
840 </dt>
841 <dd>Regular expression for hiding some databases. This only hides them
842 from listing, but a user is still able to access them (using, for example,
843 the SQL query area). To limit access, use the MySQL privilege system.
844 <br /><br />
849 More information on regular expressions can be found in the
851 PCRE pattern syntax</a> portion of the PHP reference manual.
852 </dd>
855 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
856 this string will be displayed instead of the hostname in the pull-down
857 menu on the main page. This can be useful if you want to show only
858 certain databases on your system, for example. For HTTP auth, all
859 non-US-ASCII characters will be stripped.</dd>
863 </dt>
864 <dd>The name of the database containing the linked-tables infrastructure.
865 <br /><br />
868 section in this document to see the benefits of this infrastructure,
869 and for a quick way of creating this database and the needed tables.
870 <br /><br />
872 If you are the only user of this phpMyAdmin installation, you can
873 use your current database to store those special tables; in this
874 case, just put your current database name in
876 set this parameter to the name of your central database containing
877 the linked-tables infrastructure.</dd>
881 </dt>
883 useful for queries you often run.<br /><br />
885 To allow the usage of this functionality:
887 <li>enter the table name in
889 </ul>
890 </dd>
894 </dt>
896 which column is a key in another table (a foreign key). phpMyAdmin
897 currently uses this to
898 <ul><li>make clickable, when you browse the master table, the data values
899 that point to the foreign table;</li>
901 when browsing the master table, if you move the mouse to a column
902 containing a foreign key (use also the 'table_info' table);<br />
905 <li>in edit/insert mode, display a drop-down list of possible foreign
909 <li>display links on the table properties page, to check referential
910 integrity (display missing foreign keys) for each described key;
911 </li>
915 schema of your database (also uses the table_coords table).</li>
916 </ul>
918 The keys can be numeric or character.<br /><br />
920 To allow the usage of this functionality:
923 infrastructure</li>
924 <li>put the relation table name in
926 <li>now as normal user open phpMyAdmin and for each one of your
927 tables where you want to use this feature, click
929 columns.
930 </li>
931 </ul>
935 future development of the cross-db relations.
936 </dd>
940 </dt>
941 <dd>
942 Since release 2.3.0 you can describe, in a special 'table_info'
943 table, which column is to be displayed as a tool-tip when moving the
944 cursor over the corresponding key.<br />
945 This configuration variable will hold the name of this special
946 table. To allow the usage of this functionality:
948 <li>put the table name in
950 <li>then for each table where you want to use this feature,
952 to choose the column.</li>
953 </ul>
955 </dd>
959 </dt>
962 the relations between your tables. To do this it needs two tables
967 schema output).<br /><br />
971 To allow the usage of this functionality:
974 infrastructure</li>
975 <li>put the correct table names in
978 </ul>
981 </dd>
985 </dt>
987 Since release 2.3.0 you can store comments to describe each column for
989 <br /><br />
991 Starting with release 2.5.0, comments are consequently used on the table
992 property pages and table browse view, showing up as tool-tips above the
993 column name (properties page) or embedded within the header of table in
994 browse view. They can also be shown in a table dump. Please see the
995 relevant configuration directives later on.<br /><br />
997 Also new in release 2.5.0 is a MIME-transformation system which is also
999 Transformations</a> for further information. To use the
1000 MIME-transformation system, your column_info table has to have the three
1001 new columns 'mimetype', 'transformation', 'transformation_options'.
1002 <br /><br />
1004 To allow the usage of this functionality:
1006 infrastructure</li>
1007 <li>put the table name in
1011 <pre>
1012 ALTER TABLE `pma_column_comments`
1013 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1014 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1015 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1016 </pre>
1019 renamed from<br />
1022 </ul>
1023 </dd>
1027 </dt>
1030 all queries you entered manually into the phpMyAdmin interface. If you
1031 don't want to use a table-based history, you can use the JavaScript-based
1032 history. Using that, all your history items are deleted when closing the
1033 window.<br /><br />
1035 Using
1037 you can specify an amount of history items you want to have on hold. On
1038 every login, this list gets cut to the maximum amount.<br /><br />
1040 The query history is only available if JavaScript is enabled in your
1041 browser.<br /><br />
1043 To allow the usage of this functionality:
1046 infrastructure</li>
1048 </li>
1049 </ul>
1050 </dd>
1054 </dt>
1055 <dd>
1056 Since release 3.3.x a tracking mechanism is available.
1058 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1059 and data definition statements. After enabling it you can create versions of tables.
1060 <br/><br/>
1061 The creation of a version has two effects:
1063 <ul>
1065 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1066 </ul>
1068 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1069 For the report you can use filters, for example you can get a list of statements within a date range.
1070 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1071 In addition you can export the (filtered) report to a file or to a temporary database.
1072 <br/><br/>
1074 To allow the usage of this functionality:
1076 <ul>
1079 </ul>
1080 </dd>
1083 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1084 </dt>
1085 <dd>
1086 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1087 <br/><br/>
1088 If this is set to true and you create a table or view with
1090 <ul>
1093 </ul>
1095 and no version exists for it, the mechanism will
1096 create a version for you automatically.
1097 </dd>
1100 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1101 </dt>
1102 <dd>
1103 Defines the list of statements the auto-creation uses for new versions. Default value is
1104 <br/>
1106 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1107 CREATE INDEX,DROP INDEX,
1108 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1109 CREATE VIEW,ALTER VIEW,DROP VIEW,
1110 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1111 </dd>
1114 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1115 </dt>
1116 <dd>
1117 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1118 <br/><br/>
1119 </dd>
1123 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1124 </dt>
1125 <dd>
1126 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1127 <br/><br/>
1128 </dd>
1131 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1132 </dt>
1133 <dd>
1134 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1135 <br/><br/>
1136 </dd>
1141 </dt>
1143 to visually manage the relations.
1144 <br /><br />
1146 To allow the usage of this functionality:
1149 infrastructure</li>
1151 </li>
1152 </ul>
1153 </dd>
1156 </dt>
1158 column_info table got enhanced with three new columns. If the above variable
1160 latest table structure available. If not, it will emit a warning to the
1161 superuser.<br /><br />
1163 You can disable this checking behavior by setting the variable to false,
1164 which should offer a performance increase.<br /><br />
1166 Recommended to set to FALSE, when you are sure, your table structure is
1167 up to date.</dd>
1169 boolean</dt>
1170 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1171 </dd>
1173 boolean</dt>
1174 <dd>Whether to allow logins without a password. The default
1176 to a MySQL server with was left with an empty password for root or
1177 on which an anonymous (blank) user is defined.
1178 </dd>
1181 </dt>
1183 authentication is disabled.<br /><br />
1186 all deny rules followed by allow rules. Access is allowed by default. Any
1187 client which does not match a Deny command or does match an Allow command
1188 will be allowed access to the server. <br /><br />
1191 applies all allow rules followed by deny rules. Access is denied by
1192 default. Any client which does not match an Allow directive or does
1193 match a Deny directive will be denied access to the server.<br /><br />
1195 If your rule order is set to 'explicit', the authentication is
1196 performed in a similar fashion to rule order 'deny,allow', with the
1200 and was available in Apache by specifying allow and deny rules without
1201 setting any order.<br /><br />
1203 Please also see <a
1205 address behind proxies.
1206 </dd>
1208 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1209 </dt>
1210 <dd>The general format for the rules is as such:
1212 <pre>
1214 </pre>
1219 well (please note that those containing SERVER_ADDRESS might not be
1220 available on all webservers):
1221 <pre>
1227 </pre>
1229 Having an empty rule list is equivalent to either using
1235 following work:<br />
1237 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1238 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1239 But the following does not work:<br />
1242 Also IPv6 addresses are not supported.
1243 </dd>
1245 <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.
1246 </dd>
1247 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1249 DATABASES</tt> command used to fetch the name of available databases will
1250 probably be too slow, so it can be replaced by faster commands (see
1252 </dd>
1254 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1255 </dd>
1256 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1257 <dd>Name of session which will be used for signon authentication method.
1258 </dd>
1260 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1261 </dd>
1263 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1264 </dd>
1267 <dd>If you have more than one server configured, you can set
1269 that server when phpMyAdmin is started, or set it to 0 to be given a
1270 list of servers without logging in.<br />
1272 MUST be set to that server.</dd>
1275 <dd>The maximum number of database names to be displayed in the
1276 navigation frame and the database list.</dd>
1279 <dd>The maximum number of table names to be displayed in the
1280 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1281 when in Light mode.</dd>
1284 <dd>The maximum number of characters when a SQL query is displayed. The
1285 default limit of 1000 should be correct to avoid the display of tons
1286 of hexadecimal codes that represent BLOBs, but some users have real
1287 SQL queries that are longer than 1000 characters. Also, if a query's
1288 length exceeds this limit, this query is not saved in the history.</dd>
1291 <dd>Defines whether to use GZip output buffering for increased
1293 Set to true/false for enabling/disabling. When set to 'auto' (string),
1294 phpMyAdmin tries to enable output buffering and will automatically disable
1295 it if your browser has some problems with buffering. IE6 with a certain patch
1296 is known to cause data corruption when having enabled buffering.</dd>
1299 <dd>Whether persistent connections should be used or not (mysql_connect or
1300 mysql_pconnect).</dd>
1306 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1307 to zero, no time limit is imposed.<br />
1308 This setting is used while importing/exporting dump files and in the
1309 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1316 <dd>Set the number of bytes a script is allowed to allocate. If set
1317 to zero, no limit is imposed.<br />
1318 This setting is used while importing/exporting dump files and at some
1319 other places in phpMyAdmin so you definitely don't want to put here
1320 a too low value. It has no effect when PHP is running in safe mode.<br />
1321 You can also use any string as in php.ini, eg. '16M'. Ensure
1325 <dd>Mark used tables and make it possible to show databases with locked
1330 generated by phpMyAdmin should be displayed or not.</dd>
1333 <dd>Defines whether normal users (non-administrator) are allowed to
1334 delete their own database or not. If set as FALSE, the link "Drop
1336 mydatabase" will be rejected. Quite practical for
1338 customers.<br />
1339 Please note that this limitation of SQL queries is not as strict as
1340 when using MySQL privileges. This is due to nature of SQL queries
1341 which might be quite complicated. So this choice should be viewed as
1342 help to avoid accidental dropping rather than strict privilege
1343 limitation.</dd>
1347 displayed when you're about to lose data.</dd>
1350 <dd>Define whether the previous login should be recalled or not in cookie
1351 authentication mode.<br /><br />
1353 This is automatically disabled if you do not have configured
1355 </dd>
1358 <dd>Define how long is login cookie valid. Please note that php
1359 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1360 might limit session validity and if session is lost, login cookie is
1362 at least as high is $cfg['LoginCookieValidity'] is set.</dd>
1366 means that it will be kept for existing session. This is recommended
1367 for not trusted environments.</dd>
1370 <dd>If enabled (default), logout deletes cookies for all servers,
1371 otherwise only for current one. Setting this to false makes it easy to
1372 forget to log out from other server, when you are using more of
1373 them.</dd>
1379 <dd>Define whether phpMyAdmin will continue executing a multi-query
1380 statement if one of the queries fails. Default is to abort execution.</dd>
1383 <dd>Define whether phpMyAdmin will output the results of each query of a
1384 multi-query statement embedded into the
1389 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1390 <br /><br />
1393 MySQL servers behind the firewall where your
1395 </dd>
1404 <dd>Defines whether to use a select-based menu and display only the current
1405 tables in the left frame (smaller page). Only in Non-Lightmode you can
1406 use the feature to display nested folders using
1408 </dd>
1411 <dd>In light mode, defines whether to display the names of databases (in the
1412 selector) using a tree, see also
1414 </dd>
1417 string or array</dt>
1418 <dd>The string used to separate the parts of the database name when showing
1419 them in a tree. Alternatively you can specify more strings in an array
1420 and all of them will be used as a separator.</dd>
1423 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1424 This means if you have tables like 'first__second__third' this will be
1426 If set to FALSE or empty, the feature is disabled. NOTE: You should
1427 not use this separator at the beginning or end of a
1428 table name or multiple times after another without any other
1429 characters in between.</dd>
1432 <dd>Defines how many sublevels should be displayed when splitting
1433 up tables by the above separator.</dd>
1436 <dd>Defines whether to display table comment as tool-tip in left frame or
1437 not.</dd>
1440 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1441 comment and the real name. That means that if you have a table called
1442 'user0001' and add the comment 'MyName' on it, you will see the name
1443 'MyName' used consequently in the left frame and the tool-tip shows
1444 the real name of the DB.</dd>
1447 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1449 When setting this to 'nested', the Alias of the Tablename is only used
1450 to split/nest the tables according to the
1452 directive. So only the folder is called like the Alias, the tablename itself
1453 stays the real tablename.</dd>
1456 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1459 <dd>Enter URL where logo in the navigation frame will point to.
1460 For use especially with self made theme which changes this.
1469 <dd>Defines whether or not to display a server choice at the top of the left frame.
1470 Defaults to FALSE.</dd>
1472 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1473 Defaults to FALSE (drop-down).</dd>
1475 <dd>Defines whether to display database choice in light navigation frame as links
1476 instead of in a drop-down. Defaults to 'auto' - on main page list is
1477 shown, when database is selected, only drop down is displayed.</dd>
1480 <dd>Defines the tab displayed by default when clicking the small
1481 icon next to each table name in the navigation panel. Possible
1487 <dd>Defines whether or not to display space usage and statistics about databases
1488 and tables.<br />
1489 Note that statistics requires at least MySQL 3.23.3 and that, at this
1490 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1493 <dd>Defines whether to display detailed server information on main page.
1494 You can additionally hide more information by using
1496 </dd>
1501 </dt>
1504 not at the starting main (right) frame. This setting
1505 does not check MySQL commands entered directly.<br /><br />
1507 Please note that to block the usage of phpinfo() in scripts, you
1514 hard coded password value in the configuration file, end users can't
1515 be allowed to change their passwords.</dd>
1518 <dd>Defines whether to suggest a database name on the
1522 <dd>Defines whether navigation bar buttons and the right panel top menu
1523 contain text or symbols only. A value of TRUE displays icons, FALSE
1524 displays text and 'both' displays both icons and text.</dd>
1527 <dd>Defines whether a user should be displayed a
1531 <dd>Number of rows displayed when browsing a result set. If the result set
1538 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1542 option is ticked by default.</dd>
1546 from editing when browsing a table's content. Valid values are:
1551 </ul>
1552 </dd>
1555 <dd>Defines whether or not MySQL functions fields should be initially
1556 displayed in edit/insert mode. Since version 2.10, the user can
1557 toggle this setting from the interface.
1558 </dd>
1561 <dd>Defines whether or not type fields should be initially
1562 displayed in edit/insert mode. The user can
1563 toggle this setting from the interface.
1564 </dd>
1567 <dd>Defines which type of editing controls should be used for CHAR and
1568 VARCHAR columns. Possible values are:
1569 <ul><li>input - this allows to limit size of text to size of columns in
1570 MySQL, but has problems with newlines in columns</li>
1571 <li>textarea - no problems with newlines in columns, but also no
1572 length limitations</li>
1573 </ul>
1574 Default is old behavior so input.</dd>
1580 <dd>If there are fewer items than this in the set of foreign keys, then a
1581 drop-down box of foreign keys is presented, in the style described by the
1583 setting.</dd>
1586 <dd>For the foreign key drop-down fields, there are several methods of
1587 display, offering both the key and value data. The contents of the
1588 array should be one or both of the following strings:
1594 </dt>
1595 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1596 creating a dump file</dd>
1599 </dt>
1600 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1601 compressed exports. This doesn't affect smaller dumps and allows users to
1602 create larger dumps that won't otherwise fit in memory due to php
1603 memory limit. Produced files contain more GZip/BZip2 headers, but all
1604 normal programs handle this correctly.</dd>
1608 mainframe.</dd>
1612 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1617 <dd>How many columns will be utilized to display the tables on the
1618 database property view? Default is 1 column. When setting this to a
1619 value larger than 1, the type of the database will be omitted for more
1620 display space.</dd>
1624 <dd>Defines the tab displayed by default on server view. Possible
1631 <dd>Defines the tab displayed by default on database view. Possible
1636 <dd>Defines the tab displayed by default on table view. Possible
1643 points to the MySQL documentation (type depends
1644 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1645 generated.<br />
1647 for more information about MySQL manuals and their types.</dd>
1650 <dd>Type of MySQL documentation:
1656 </ul>
1657 </dd>
1660 <dd>Defines the default language to use, if not browser-defined or
1661 user-defined.<br />
1662 The corresponding language file needs to be in
1664 </dd>
1667 <dd>Defines the default connection collation to use, if not
1668 user-defined.<br />
1674 The corresponding language file needs to be in
1676 </dd>
1679 <dd>Limit list of available languages to those matching the given regular
1680 expression. For example if you want only Czech and English, you should
1684 <dd>Default character set to use for recoding of MySQL queries. This must be
1685 enabled and it's described by
1687 option.<br />
1688 You can give here any character set which is in
1690 array and this is just default choice, user can select any of them.</dd>
1693 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1694 support (compiled in or module) in PHP to allow MySQL queries recoding
1695 and used language file must have it enabled (by default only these
1696 which are in Unicode, just to avoid losing some characters).<br /><br />
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>You can select here which functions will be used for character set
1706 conversion. Possible values are:
1707 <ul><li>auto - automatically use available one (first is tested
1708 iconv, then recode)</li>
1711 </ul>
1712 Default is auto.</dd>
1715 <dd>Specify some parameters for iconv used in charset conversion. See
1718 used, so that invalid characters will be transliterated.</dd>
1721 <dd>Available character sets for MySQL conversion. You can add your own (any of
1722 supported by recode/iconv) or remove these which you don't use.
1723 Character sets will be shown in same order as here listed, so if you
1724 frequently use some of these move them to the top.</dd>
1729 default empty, you need to fill in some trusted proxy servers if you
1730 want to use rules for IP addresses behind proxy.<br /><br />
1732 The following example specifies that phpMyAdmin should trust a
1734 <pre>
1735 $cfg['TrustedProxies'] =
1737 </pre>
1738 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1739 client's IP address as usual.
1740 </dd>
1744 MIME transformations.<br />
1745 Possible values are:
1746 <ul><li>auto - automatically detect, this is a bit expensive
1748 according to your server real possibilities</li>
1751 </ul>
1752 Default is auto.
1753 </dd>
1756 <dd>
1757 We normally check the permissions on the configuration file to ensure
1758 it's not world writable. However, phpMyAdmin could be installed on
1759 a NTFS filesystem mounted on a non-Windows server, in which case the
1760 permissions seems wrong but in fact cannot be detected. In this case
1762 </dd>
1765 <dd>
1766 Limit for length of URL in links. When length would be above this limit, it
1767 is replaced by form with button.
1768 This is required as some web servers (IIS) have problems with long URLs.
1770 </dd>
1774 </dd>
1776 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1777 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1778 </dt>
1779 <dd>The background styles used for both the frames.
1782 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1784 <dd>The style used for the pointer in the navi frame.
1788 </dt>
1789 <dd>The color used for the database name in the navi frame.
1798 </dd>
1802 <dd>The style used for table headers. See
1807 </dd>
1811 </dd>
1813 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1815 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1817 </dt>
1819 The former feature highlights the row over which your mouse is passing
1820 and the latter lets you visually mark/unmark rows by clicking on
1821 them.<br />
1826 <dd>You put here a valid CSS font family value, for example
1831 <dd>You put here a valid CSS font family value, for example
1845 </dt>
1847 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1849 The Char* values are used for CHAR and VARCHAR editing (if configured
1853 </dt>
1857 </dt>
1858 <dd>Defines if the whole textarea of the query box will be selected on
1859 click.</dd>
1862 </dt>
1863 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1864 editing.</dd>
1867 <dd>Maximum number of characters showen in any non-numeric column on browse view.
1868 Can be turned off by a toggle button on the browse page.</dd>
1872 </dt>
1873 <dd>Defines the place where modify and delete links would be put when
1874 tables contents are displayed (you may have them displayed both at the
1875 left and at the right).
1881 Define which one is displayed by default. The first mode displays each
1882 row on a horizontal line, the second rotates the headers by 90
1883 degrees, so you can use descriptive headers even though columns only
1884 contain small values and still print them out. The vertical mode sorts
1885 each row on a vertical lineup.
1886 </dd>
1889 <dd>
1890 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1891 'css' the rotation of the header for horizontalflipped is done via
1892 CSS. The CSS transformation currently works only in Internet
1893 Explorer.If set to 'fake' PHP does the transformation for you, but of
1894 course this does not look as good as CSS. The 'auto' option enables
1895 CSS transformation when browser supports it and use PHP based one
1896 otherwise.
1897 </dd>
1901 string or integer</dt>
1902 <dd>When editing/creating new columns in a table all fields normally get
1903 lined up one field a line. (default: 'horizontal'). If you set this to
1904 'vertical' you can have each field lined up vertically beneath each
1905 other. You can save up a lot of place on the horizontal direction and
1906 no longer have to scroll. If you set this to integer, editing of fewer
1907 columns will appear in 'vertical' mode, while editing of more columns
1908 still in 'horizontal' mode. This way you can still effectively edit
1909 large number of columns, while having full view on few of them.</dd>
1913 </dt>
1915 display of column comments in Browse or Property display. In browse
1916 mode, the comments are shown inside the header. In property mode,
1917 comments are displayed using a CSS-formatted dashed-line below the
1918 name of the column. The comment is shown as a tool-tip for that column.
1919 </dd>
1931 <dd>Whether to display a link to validate a query in any SQL Query box.
1938 <dd>
1939 The name of the directory where
1941 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1942 are available under a drop-down box when you click the database or
1943 table name, then the Import tab.
1944 <br /><br />
1946 If you want different directory for each user, %u will be replaced
1947 with username.<br /><br />
1951 compressed formats is enabled).<br /><br />
1953 This feature is useful when your file is too big to be uploaded via
1955 uploads are disabled in PHP.<br /><br />
1957 Please note that if PHP is running in safe mode, this directory must
1958 be owned by the same user as the owner of the phpMyAdmin scripts.
1959 <br /><br />
1963 alternatives.
1964 </dd>
1967 <dd>
1968 The name of the directory where dumps can be saved.<br /><br />
1970 If you want different directory for each user, %u will be replaced
1971 with username.<br /><br />
1973 Please note that the directory must exist and has to be writable for
1974 the user running webserver.<br /><br />
1976 Please note that if PHP is running in safe mode, this directory must
1977 be owned by the same user as the owner of the phpMyAdmin scripts.
1978 </dd>
1981 <dd>
1982 The name of the directory where temporary files can be stored.
1983 <br /><br />
1985 This is needed for native MS Excel export, see
1991 <br /><br />
1993 If the directory where phpMyAdmin is installed is subject to an
1995 temporary directory in some directory accessible by the web
1996 server. However for security reasons, this directory should be outside
1997 the tree published by webserver. If you cannot avoid having this
1998 directory published by webserver, place at least an empty
2000 possible.
2001 <br /><br />
2003 This directory should have as strict permissions as possible as the only
2004 user required to access this directory is the one who runs the
2005 webserver. If you have root privileges, simply make this user owner of
2006 this directory and make it accessible only by it:
2007 <br /><br />
2009 <pre>
2010 chown www-data:www-data tmp
2011 chmod 700 tmp
2012 </pre>
2014 If you cannot change owner of the directory, you can achieve a similar
2017 <pre>
2018 chmod 700 tmp
2019 setfacl -m "g:www-data:rwx" tmp
2020 setfacl -d -m "g:www-data:rwx" tmp
2021 </pre>
2023 If neither of above works for you, you can still make the directory
2025 system reading and writing data in this directory.
2026 </dd>
2029 <dd>
2030 In this array are defined default parameters for export, names of
2031 items are similar to texts seen on export page, so you can easily
2032 identify what they mean.
2033 </dd>
2036 <dd>
2037 In this array are defined default parameters for import, names of
2038 items are similar to texts seen on import page, so you can easily
2039 identify what they mean.
2040 </dd>
2043 <dd>
2044 Repeat the headers every X cells, or 0 to deactivate.
2045 </dd>
2053 </dt>
2054 <dd>
2055 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2056 or icon is always displayed on the left panel. If JavaScript is enabled in
2057 your browser, a click on this opens a distinct query window, which is
2058 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2059 changes to display a query box.<br /><br />
2061 The size of this query window can be customized with
2063 - both integers for the size in pixels. Note that normally, those
2065 theme you are using.<br /><br />
2069 opens the query window and puts the current query
2070 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2071 query in the right panel's query box.
2072 <br /><br />
2073 The usage of the JavaScript query window is recommended if you have a
2074 JavaScript enabled browser. Basic functions are used to exchange quite
2075 a few variables, so most 4th generation browsers should be capable to
2076 use that feature. It currently is only tested with Internet Explorer 6
2077 and Mozilla 1.x.
2078 <br /><br />
2080 to a table, which has to be created by you (see <a
2082 all your queries will be appended to the form, but only as long as
2083 your window is opened they remain saved.
2084 <br /><br />
2085 When using the JavaScript based query window, it will always get
2086 updated when you click on a new table/db to browse and will focus if
2087 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2088 the query window by checking the box "Do not overwrite this query from
2089 outside the window" below the query textarea. Then you can browse
2090 tables/databases in the background without losing the contents of the
2091 textarea, so this is especially useful when composing a query with
2092 tables you first have to look in. The checkbox will get automatically
2093 checked whenever you change the contents of the textarea. Please
2094 uncheck the button whenever you definitely want the query window to
2095 get updated even though you have made alterations.
2096 <br /><br />
2099 <br /><br />
2100 The query window also has a custom tabbed look to group the features.
2102 default tab to be used when opening the query window. It can be set to
2103 either 'sql', 'files', 'history' or 'full'.</dd>
2109 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2111 If the approximate row count as returned by
2114 count will be used.
2115 </dd>
2117 <dd>For VIEWs, since obtaining the exact count could have an
2118 impact on performance, this value is the maximum to be displayed, using
2120 any row counting.
2121 </dd>
2125 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2127 page. By clicking on the button 'toggle scratchboard' on the page
2128 where you edit x/y coordinates of those elements you can activate a
2129 scratchboard where all your elements are placed. By clicking on an
2130 element, you can move them around in the pre-defined area and the x/y
2131 coordinates will get updated dynamically. Likewise, when entering a
2132 new position directly into the input field, the new position in the
2133 scratchboard changes after your cursor leaves the input field.<br />
2134 You have to click on the 'OK'-button below the tables to save the new
2135 positions. If you want to place a new element, first add it to the
2136 table of elements and then you can drag the new element around.<br />
2137 By changing the paper size and the orientation you can change the size
2138 of the scratchboard as well. You can do so by just changing the
2139 dropdown field below, and the scratchboard will resize automatically,
2140 without interfering with the current placement of the elements.<br />
2141 If ever an element gets out of range you can either enlarge the paper
2142 size or click on the 'reset' button to place all elements below each
2143 other.<br />
2145 get this control to work. The basic Drag&Drop script functionality
2146 was kindly borrowed from www.youngpup.net and is underlying so
2147 specific license.</dd>
2150 <dd>Sorts database and table names according to natural order (for example,
2151 t1, t2, t10). Currently implemented in the left panel (Light mode)
2152 and in Database view, for the table list.</dd>
2163 <dd>Allows you to specify window's title bar. Following magic string can
2164 be used to get special values:
2165 <dl>
2171 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2180 </dl>
2181 </dd>
2191 </dd>
2194 <dd>If theme manager is active, use this as the path of the subdirectory
2195 containing all the themes.</dd>
2209 </dt>
2210 <dd>Default queries that will be displayed in query boxes when user didn't
2211 specify any. Use %d for database name, %t for table name and %f for a
2212 comma separated list of column names. Note that %t and %f are only
2216 <dd>
2217 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
2218 default we use HTML to format the query, but you can disable this by
2220 </dd>
2223 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2224 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2225 query inside a bracket is indented. By changing
2228 specifies the units of the indent amount that you specified. This is
2229 used via stylesheets.</dd>
2232 <dd>This array is used to define the colours for each type of element of
2233 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2235 If you specify an empty string for the color of a class, it is ignored
2236 in creating the stylesheet.
2237 You should not alter the class names, only the colour strings.<br />
2258 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2262 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2263 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2264 </ul>
2265 </dd>
2269 <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,
2270 as originally published on
2272 <br />
2273 For help in setting up your system to use the service, see the
2275 </dd>
2279 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2280 and any password, so we use those by default. Instead, if
2281 you have an account with them, you can put your login details
2282 here, and it will be used in place of the anonymous login.</dd>
2283 </dl>
2284 </dd>
2287 <dd><b>DEVELOPERS ONLY!</b></dd>
2290 <dd><b>DEVELOPERS ONLY!</b><br />
2291 Enable logging queries and execution times to be displayed in the bottom
2292 of main page (right frame).</dd>
2295 <dd><b>DEVELOPERS ONLY!</b><br />
2296 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2297 the code.<br />
2298 For help in setting up your system to this, see the
2302 <dd><b>DEVELOPERS ONLY!</b><br />
2303 Enable profiling support for phpMyAdmin. This will append a chunk of data
2304 to the end of every page displayed in the main window with profiling
2305 statistics for that page.<br />
2306 You may need to increase the maximum execution time for this to
2307 complete successfully.<i>Profiling was removed from the code for
2308 version 2.9.0 due to licensing issues.</i></dd>
2310 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2311 <dd><b>DEVELOPERS ONLY!</b><br />
2312 When profiling data is displayed, this variable controls the threshold of
2313 display for any profiling data, based on the average time each time has
2314 taken. If it is over the threshold it is displayed, otherwise it is not
2315 displayed. This takes a value in milliseconds. In most cases you don't need
2316 to edit this.</dd>
2319 <dd>All possible types of a MySQL column. In most cases you don't need to
2320 edit this.</dd>
2323 <dd>Possible attributes for columns. In most cases you don't need to edit
2324 this.</dd>
2327 <dd>A list of functions MySQL supports. In most cases you don't need to
2328 edit this.</dd>
2331 <dd>Mapping of column types to meta types used for preferring displayed
2332 functions. In most cases you don't need to edit this.</dd>
2335 <dd>Functions preferred for column meta types as defined in
2336 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2337 to edit this.</dd>
2340 <dd>Functions selected by default when inserting/changing row, Functions
2341 are defined for meta types from
2343 <code>first_timestamp</code>, which is used for first timestamp column
2344 in table.</dd>
2347 <dd>Operators available for search operations on numeric and date columns.
2348 </dd>
2351 <dd>Operators available for search operations on character columns.
2352 Note that we put <code>LIKE</code> by default instead of
2353 <code>LIKE %...%</code>, to avoid unintended performance problems
2354 in case of huge tables.</dd>
2357 <dd>Operators available for search operations on ENUM columns.</dd>
2360 <dd>Additional operators available for search operations when the
2361 column can be null.</dd>
2363 </dl>
2365 <!-- TRANSFORMATIONS -->
2371 </ol>
2375 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2377 section</a> on how to do so.</p>
2379 <p> You can apply different transformations to the contents of each column. The
2380 transformation will take the content of each column and transform it with
2381 certain rules defined in the selected transformation.</p>
2383 <p> Say you have a column 'filename' which contains a filename. Normally you would
2384 see in phpMyAdmin only this filename. Using transformations you can transform
2385 that filename into a HTML link, so you can click inside of the phpMyAdmin
2386 structure on the column's link and will see the file displayed in a new browser
2387 window. Using transformation options you can also specify strings to
2388 append/prepend to a string or the format you want the output stored in.</p>
2390 <p> For a general overview of all available transformations and their options,
2391 you can consult your
2392 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2393 installation.</p>
2395 <p> For a tutorial on how to effectively use transformations, see our
2397 the official phpMyAdmin homepage.</p>
2401 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2402 clicking on the 'Structure' link for a table). There click on
2403 "Change" (or change icon) and there you will see three new
2404 fields at
2405 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2406 'Transformation options'.</p>
2408 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2409 that corresponds to the column's contents. Please note that
2410 transformations are inactive as long as no MIME-type is selected.</li>
2412 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2413 hopefully growing amount of pre-defined transformations. See below for information on
2414 how to build your own transformation.<br />
2416 There are global transformations and mimetype-bound transformations. Global transformations
2417 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2418 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2419 transformations which operate on the main mimetype (like 'image'), which will most likely
2420 take the subtype into regard, and those who only operate on a
2421 specific subtype (like 'image/jpeg').<br />
2423 You can use transformations on mimetypes for which the function was not defined for. There
2424 is no security check for you selected the right transformation, so take care of what the
2425 output will be like.</li>
2427 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2428 transform-function specific options here. Usually the transforms can operate with default
2429 options, but it is generally a good idea to look up the overview to see which options are
2430 necessary.<br />
2432 Much like the ENUM/SET-Fields, you have to split up several options using the format
2433 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2434 parsed as an array, leaving the first value the first element in the array, and so
2435 forth.<br />
2437 If you want to specify a MIME character set you can define it in the transformation_options.
2438 You have to put that outside of the pre-defined options of the specific mime-transform,
2440 for which you can specify 2 options and you want to append a character set, enter "'first
2441 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2443 </ul>
2447 <p> All mimetypes and their transformations are defined through single files in
2448 the directory 'libraries/transformations/'.</p>
2450 <p> They are stored in files to ease up customization and easy adding of new
2451 transformations.</p>
2453 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2454 always work. It makes no sense to apply a transformation to a mimetype, the
2455 transform-function doesn't know to handle.</p>
2457 <p> One can, however, use empty mime-types and global transformations which should work
2458 for many mimetypes. You can also use transforms on a different mimetype they where built
2459 for, but pay attention to option usage as well as what the transformation does to your
2460 column.</p>
2462 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2463 any other transform function and provides some basic functions.</p>
2465 <p> There are 5 possible file names:</p>
2467 <ol><li>A mimetype+subtype transform:<br /><br />
2469 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2471 Please not that mimetype and subtype are separated via '_', which shall
2472 not be contained in their names. The transform function/filename may
2473 contain only characters which cause no problems in the file system as
2474 well as the PHP function naming convention.<br /><br />
2476 The transform function will the be called
2477 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2479 <b>Example:</b><br /><br />
2481 <tt>text_html__formatted.inc.php</tt><br />
2482 <tt>PMA_transform_text_html__formatted()</tt></li>
2484 <li>A mimetype (w/o subtype) transform:<br /><br />
2486 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2488 Please note that there are no single '_' characters.
2489 The transform function/filename may contain only characters which cause
2490 no problems in the file system as well as the PHP function naming
2491 convention.<br /><br />
2493 The transform function will the be called
2494 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2496 <b>Example:</b><br /><br />
2498 <tt>text__formatted.inc.php</tt><br />
2499 <tt>PMA_transform_text__formatted()</tt></li>
2501 <li>A mimetype+subtype without specific transform function<br /><br />
2503 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2505 Please note that there are no '__' characters in the filename. Do not
2506 use special characters in the filename causing problems with the file
2507 system.<br /><br />
2509 No transformation function is defined in the file itself.<br /><br />
2511 <b>Example:</b><br /><br />
2513 <tt>text_plain.inc.php</tt><br />
2514 (No function)</li>
2516 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2518 <tt>[mimetype].inc.php</tt><br /><br />
2520 Please note that there are no '_' characters in the filename. Do not use
2521 special characters in the filename causing problems with the file system.
2522 <br /><br />
2524 No transformation function is defined in the file itself.<br /><br />
2526 <b>Example:</b><br /><br />
2528 <tt>text.inc.php</tt><br />
2529 (No function)</li>
2531 <li>A global transform function with no specific mimetype<br /><br />
2533 <tt>global__[transform].inc.php</tt><br /><br />
2535 The transform function will the be called
2536 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2538 <b>Example:</b><br /><br />
2540 <tt>global__formatted</tt><br />
2541 <tt>PMA_transform_global__formatted()</tt></li>
2542 </ol>
2544 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2545 transform function.</p>
2547 <p> All filenames containing no '__' in themselves are not shown as valid transform
2548 functions in the dropdown.</p>
2550 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2551 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2552 without a transform function.</p>
2554 <p> To create a new transform function please see
2555 <tt>libraries/transformations/template_generator.sh</tt>.
2556 To create a new, empty mimetype please see
2557 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2559 <p> A transform function always gets passed three variables:</p>
2561 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2562 you want to transform.</li>
2563 <li><b>$options</b> - Contains any user-passed options to a transform function
2564 as an array.</li>
2565 <li><b>$meta</b> - Contains an object with information about your column.
2566 The data is drawn from the output of the
2568 function. This means, all object properties described on the
2570 available in this variable and can be used to transform a column accordingly
2571 to unsigned/zerofill/not_null/... properties.<br />
2572 The $meta->mimetype variable contains the original MIME-type of the
2573 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2574 </ol>
2576 <p> Additionally you should also provide additional function to provide
2577 information about the transformation to the user. This function should
2578 have same name as transformation function just with appended
2579 <code>_info</code> suffix. This function accepts no parameters and returns
2580 array with information about the transformation. Currently following keys
2581 can be used:
2582 </p>
2583 <dl>
2584 <dt><code>info</code></dt>
2585 <dd>Long description of the transformation.</dd>
2586 </dl>
2588 <!-- FAQ -->
2595 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2600 </ol>
2602 <p> Please have a look at our
2604 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2605 features and or interface.</p>
2611 action is required or phpMyAdmin sends a blank page or a page full of
2612 cryptic characters to my browser, what can I do?</a></h4>
2614 <p> There are some known PHP bugs with output buffering and compression.<br />
2616 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2617 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2618 configuration file.<br />
2619 Furthermore, we know about such problems connected to the release
2620 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2621 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2626 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2627 See also the
2629 entry about PHP bugs with output buffering.<br />
2630 If your server keeps crashing, please ask for help in the various Apache
2631 support groups.</p>
2635 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2636 script: I'm always displayed the login screen.</a></h4>
2638 <p> This is a known PHP bug (see this
2640 official PHP bug database. It means there is and won't be any phpMyAdmin
2641 fix against it because there is no way to code a fix.</p>
2647 application misbehaved by not returning a complete set of
2649 </h4>
2651 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2652 Have a look at the last message in this
2654 official PHP bug database.</p>
2659 and/or many error messages with the
2661 mode.</a></h4>
2663 <p> This is a known problem with the PHP
2665 filter: it's not so stable. Please use instead the cookie authentication mode.
2666 </p>
2671 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2672 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2673 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2674 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2675 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2680 work.</a></h4>
2682 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2683 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2684 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2685 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2686 We faced PHP crashes when trying to download a dump with MS Internet
2687 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2688 this case you should switch to the release version of PHP 4.2.0.</p>
2692 an error about safe mode being in effect.</a></h4>
2694 <p> Your uploaded file is saved by PHP in the "upload dir", as
2695 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2696 the system default is <i>/tmp</i>).<br />
2697 We recommend the following setup for Apache servers running in safe mode,
2698 to enable uploads of files while being reasonably secure:</p>
2700 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2701 <li>give ownership to the Apache server's user.group:
2702 <tt>chown apache.apache /tmp/php</tt></li>
2703 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2704 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2705 <li>restart Apache</li>
2706 </ul>
2710 general file uploads don't work on my system and uploaded files have a
2711 <tt>Content-Type:</tt> header in the first line.</a></h4>
2713 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2714 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2715 So the problem is that this package has a serious bug that was corrected
2716 ages ago in PHP (2001-01-28: see
2718 for more details). The problem is that the bugged package is still
2719 available though it was corrected (see
2721 for more details).<br />
2722 So please download
2723 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2724 and the problem should go away.<br />
2725 And that fixes the \r\n problem with file uploads!</p>
2729 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2730 I'm using the Apache server.</a></h4>
2732 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2733 your <i>httpd.conf</i>:</p>
2737 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2741 uploading a file from the query box.</a></h4>
2743 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2744 restrictions. However you need to create temporary directory and
2746 The uploaded files will be moved there, and after execution of your
2752 <p> The MySQL manual explains how to
2754 reset the permissions</a>.</p>
2759 execute a bookmark.</a></h4>
2761 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2762 cannot access the uploaded query.</p>
2767 submit a query from the convenient text area.</a></h4>
2769 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2770 and try to increase it.</p>
2774 </h4>
2776 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2777 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2778 names to align with current standards.</p>
2783 </h4>
2785 <p> Starting with version 2.7.0, the import engine has been re–written and these
2786 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2787 to take advantage of the new import features.</p>
2789 <p> The first things to check (or ask your host provider to check) are the
2790 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2791 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2792 All of these three settings limit the maximum size of data that can be
2793 submitted and handled by PHP. One user also said that post_max_size
2794 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2796 There exist several workarounds if your upload is too big or your
2797 hosting provider is unwilling to change the settings:</p>
2800 feature. This allows one to
2801 upload a file to the server via scp, ftp, or your favorite file transfer
2802 method. PhpMyAdmin is then able to import the files from the temporary
2804 section</a> of this document.</li>
2806 BigDump</a>) to split the files before uploading. We cannot support this
2807 or any third party applications, but are aware of users having success
2808 with it.</li>
2809 <li>If you have shell (command line) access, use MySQL to import the files
2810 directly. You can do this by issuing the "source" command from
2811 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2812 </ul>
2816 support?</a></h4>
2818 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2819 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2820 connect to your MySQL server using PHP's classic
2823 is available in php 5.0. The latter one should be used unless you have
2824 good reason not to do so.<br />
2825 When compiling php, we strongly recommend that you manually link the MySQL
2826 extension of your choice to a MySQL client library of at least the same
2827 minor version since the one that is bundled with some PHP distributions is
2830 If your webserver is running on a windows system, you might want to try
2831 MySQL's
2833 instead of the MySQL / MySQLi extensions that are bundled with the official
2834 php Win32 builds.</p>
2838 message, "Client does not support authentication protocol requested
2839 by server; consider upgrading MySQL client"</a></h5>
2841 <p> You tried to access MySQL with an old MySQL client library. The version of
2842 your MySQL client library can be checked in your phpinfo() output.
2843 In general, it should have at least the same minor version as your server
2847 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2848 changed the authentication hash and your PHP is trying to use the old method.
2850 with the proper client library to match your MySQL installation. Your
2851 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2852 More information (and several workarounds) are located in the
2854 </p>
2858 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2859 capital letter in its name it is changed to lowercase as it should. But
2860 if I try to DROP this table MySQL is unable to find the corresponding
2861 file.</a></h4>
2863 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2864 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2865 directive.</p>
2869 script seems not to know the font face I'm using!</a></h4>
2871 <p> The "FPDF" library we're using for this feature requires some
2872 special files to use font faces.<br />
2874 these files.</p>
2878 check PHP Configuration".</a></h4>
2880 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2881 "MySQL extension". This extension may be part of the PHP
2882 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2883 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2884 to load the extension but failed.<br /><br />
2886 Usually, the problem is solved by installing a software package called
2887 "PHP-MySQL" or something similar.</p>
2892 and I cannot log in using cookie auth.</a></h4>
2894 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2898 so I cannot upload.</a></h4>
2900 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2901 parameter is not set to "on".</p>
2905 a new table the table and column names are changed to lowercase!</a></h4>
2907 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2908 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2909 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2910 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2911 directory and add the following line to the group [mysqld]:</p>
2913 <pre>set-variable = lower_case_table_names=0</pre>
2915 <p> Next, save the file and restart the MySQL service. You can always check the
2916 value of this directive using the query</p>
2918 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2922 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2925 </p>
2929 and I get problems, such as undefined variables when I run a
2932 <p> A tip from Jose Fandos: put a comment on the following two lines
2933 in httpd.conf, like this:</p>
2935 <pre>
2936 # mod_gzip_item_include file \.php$
2938 </pre>
2940 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2941 PHP scripts. Of course you have to restart Apache.</p>
2946 I get the error "No input file specified" when trying to
2947 run phpMyAdmin.</a></h4>
2949 <p> This is a permission problem. Right-click on the phpmyadmin folder
2950 and choose properties. Under the tab Security, click on "Add"
2951 and select the user "IUSR_machine" from the list. Now set his
2952 permissions and it should work.</p>
2956 db_structure.php with plenty of tables).</a></h4>
2959 GZIP output buffering is enabled. If you turn off it (by
2961 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2962 PHP 5.0.0.</p>
2966 message 'Errorcode: 13'. What does this mean?</a></h4>
2968 <p> This can happen due to a MySQL bug when having database / table names with
2969 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2970 To fix this, turn off this directive, convert all database and table names
2971 to lower case and turn it on again. Alternatively, there's a bug-fix
2972 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2976 and the columns are duplicated.</a></h4>
2978 <p> It is possible to configure Apache in such a way that PHP has problems
2979 interpreting .php files.</p>
2981 <p> The problems occur when two different (and conflicting) set of directives
2982 are used:</p>
2984 <pre>
2985 SetOutputFilter PHP
2986 SetInputFilter PHP
2987 </pre>
2989 <p> and</p>
2991 <pre>AddType application/x-httpd-php .php</pre>
2993 <p> In the case we saw, one set of directives was in
2994 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2995 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2996 The recommended way is with <tt>AddType</tt>, so just comment out
2997 the first set of lines and restart Apache:</p>
2999 <pre>
3000 #SetOutputFilter PHP
3001 #SetInputFilter PHP
3002 </pre>
3007 <p> This problem is known to happen when the server is running Turck MMCache
3008 but upgrading MMCache to version 2.3.21 solves the problem.</p>
3013 <p>Yes.</p>
3014 <p>
3015 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
3016 is still maintained.
3017 </p>
3020 <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>
3022 <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>
3025 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3026 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3027 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3028 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3029 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3030 enabled.) Click <tt>OK</tt>.</li>
3031 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3032 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3033 </ol>
3037 PHP 5.0.4 on 64-bit systems?</a></h4>
3039 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3040 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3046 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
3047 the order of the server paragraph in <tt>config.inc.php</tt>.
3048 Table and script parts are optional. If you want
3049 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3050 some configuration. Following lines apply only for <a
3052 that you have enabled some features within global configuration. You need
3053 <code>Options FollowSymLinks</code> and <code>AllowOverride
3054 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3055 you need mod_rewrite to be enabled. Then you just need to create following
3056 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3057 (don't forget to change directory name inside of it):</p>
3059 <pre>
3060 RewriteEngine On
3061 RewriteBase /path_to_phpMyAdmin
3062 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3063 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3064 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3065 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3066 </pre>
3069 <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>
3071 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3072 following rewrite rule:</p>
3074 <pre>
3075 RewriteEngine On
3076 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3077 </pre>
3081 </h4>
3082 <p>
3083 There can be many explanations to this and a look at your server's
3084 error log file might give a clue.
3085 </p>
3089 password encryption in cookie auth doesn't work.</a></h4>
3091 <p> If your cluster consist of different architectures, PHP code used for
3092 encryption/decryption won't work correct. This is caused by use of
3093 pack/unpack functions in code. Only solution is to use mcrypt extension
3094 which works fine in this case.</p>
3099 <p> Yes but the default configuration values of Suhosin are known to cause
3100 problems with some operations, for example editing a table with many
3101 columns and no primary key or with textual primary key.
3102 </p>
3103 <p>
3104 Suhosin configuration might lead to malfunction in some cases and it can
3105 not be fully avoided as phpMyAdmin is kind of application which needs to
3106 transfer big amounts of columns in single HTTP request, what is something
3107 what Suhosin tries to prevent. Generally all
3108 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3109 <code>suhosin.get.*</code> directives can have negative effect on
3110 phpMyAdmin usability. You can always find in your error logs which limit
3111 did cause dropping of variable, so you can diagnose the problem and adjust
3112 matching configuration variable.
3113 </p>
3114 <p>
3115 The default values for most Suhosin configuration options will work in most
3116 scenarios, however you might want to adjust at least following parameters:
3117 </p>
3119 <ul>
3120 <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>
3121 <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>
3122 <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>
3123 <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>
3124 <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>
3125 <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>
3126 <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>
3127 <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>
3128 </ul>
3130 <p>
3132 <tt>SuhosinDisableWarning</tt> directive</a>.
3133 </p>
3137 but then my connection is redirected back to http. What can cause this
3138 behavior?</a></h4>
3140 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3141 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>
3144 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
3146 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3147 Example from the Apache 2.2 documentation:</p>
3148 <pre>
3149 ProxyPass /mirror/foo/ http://backend.example.com/
3150 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3151 ProxyPassReverseCookieDomain backend.example.com public.example.com
3152 ProxyPassReverseCookiePath / /mirror/foo/
3153 </pre>
3155 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3156 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3157 This is not specific to phpmyadmin, it's just the behavior of Apache.
3158 </p>
3160 <pre>
3161 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3162 ProxyPassReverse /mirror/foo/
3163 http://backend.example.com/%7Euser/phpmyadmin
3164 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3165 </pre>
3167 <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>
3168 for more details.</p>
3172 privileges, I get an error about an unknown column.</a></h4>
3174 <p> The MySQL server's privilege tables are not up to date, you need to run
3175 the <tt>mysql_upgrade</tt> command on the server.</p>
3182 headers already sent by ..." is displayed, what's the problem?</a></h4>
3184 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3185 (I.E. no blank lines, no spaces, no characters...) neither before the
3186 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3187 tag at the end. We also got a report from a user under IIS, that used
3188 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3189 contained an end-of-line character (hex 0A) at the end; removing this character
3190 cleared his errors.</p>
3195 <p> Either there is an error with your PHP setup or your username/password is
3196 wrong. Try to make a small script which uses mysql_connect and see if it
3197 works. If it doesn't, it may be you haven't even compiled MySQL support
3198 into PHP.</p>
3202 connect to local MySQL server through socket '/tmp/mysql.sock'
3203 (111) ..." is displayed. What can I do?</a></h4>
3205 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3207 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3208 In your <i>php.ini</i> you will find a line</p>
3210 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3212 <p> change it to</p>
3214 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3216 <p> Then restart apache and it will work.</p>
3218 <p> Here is a fix suggested by Brad Ummer:</p>
3220 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3221 To do this, telnet to your server and go to the MySQL bin directory. In
3222 this directory there should be a file named <i>mysqladmin</i>. Type
3223 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3224 info about your MySQL server, including the socket
3225 (<i>/tmp/mysql.sock</i>, for example).</li>
3226 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3227 phpMyAdmin, you need to complete the socket information in the
3228 <i>config.inc.php</i>.<br />
3229 For example:
3231 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3232 <br /><br />
3234 Please also make sure that the permissions of this file allow to be readable
3235 by your webserver (i.e. '0755').</li>
3236 </ul>
3238 <p> Have also a look at the
3240 corresponding section of the MySQL documentation</a>.</p>
3244 what can I do?</a></h4>
3247 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3248 sometime.<br />
3249 Also have a look at your PHP version number: if it contains "4.0b..."
3250 it means you're running a beta version of PHP. That's not a so good idea,
3251 please upgrade to a plain revision.</p>
3255 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3256 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3258 <p> Check the value you set for the
3260 directive in the phpMyAdmin configuration file.</p>
3264 password: YES)"-error when trying to access a MySQL-Server on a
3265 host which is port-forwarded for my localhost.</a></h4>
3267 <p> When you are using a port on your localhost, which you redirect via
3268 port-forwarding to another host, MySQL is not resolving the localhost
3269 as expected.<br />
3270 Erik Wasser explains: The solution is: if your host is "localhost"
3271 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3272 connection for speeding up things. And that doesn't work in this configuration
3273 with port forwarding.<br />
3279 <p> Themes are configured with
3283 <br />
3285 should not delete the directory "original" or its underlying
3286 structure, because this is the system theme used by phpMyAdmin.
3287 "original" contains all images and styles, for backwards
3288 compatibility and for all themes that would not include images or css-files.
3289 <br /><br />
3292 is enabled, you can select your favorite theme on the main page. Your
3293 selected theme will be stored in a cookie.<br /><br /></p>
3295 <p> To create a theme:</p>
3297 <ul><li>make a new subdirectory (for example "your_theme_name") under
3299 (by default <tt>themes</tt>)</li>
3300 <li>copy the files and directories from "original" to
3301 "your_theme_name"</li>
3302 <li>edit the css-files in "your_theme_name/css"</li>
3303 <li>put your new images in "your_theme_name/img"</li>
3304 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3305 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3306 contain your chosen theme name, that will be visible in user interface</li>
3307 <li>make a new screenshot of your theme and save it under
3308 "your_theme_name/screen.png"</li>
3309 </ul>
3311 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3312 theme verbose name, theme generation and theme version. These versions and
3313 generations are enumerated from 1 and do not have any direct dependence on
3314 phpMyAdmin version. Themes within same generation should be backwards
3315 compatible - theme with version 2 should work in phpMyAdmin requiring
3316 version 1. Themes with different generation are incompatible.</p>
3318 <p> If you do not want to use your own symbols and buttons, remove the
3319 directory "img" in "your_theme_name". phpMyAdmin will
3320 use the default icons and buttons (from the system-theme "original").
3321 </p>
3325 what can I do?</a></h4>
3327 <p> Here are a few points to check:</p>
3329 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3331 directive empty. See also
3333 </li>
3334 <li>Maybe you have a broken PHP installation or you need to upgrade
3335 your Zend Optimizer. See
3337 http://bugs.php.net/bug.php?id=31134</a>.
3338 </li>
3339 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3340 set to the default (200) or another low value, you could get this
3341 error if your table has a high number of columns. Adjust this setting
3342 accordingly. (Thanks to Klaus Dorninger for the hint).
3343 </li>
3344 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3345 of ";" will cause this error. Replace it with "&;".
3346 </li>
3348 you might want to increase
3350 </li>
3351 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3352 </li>
3353 </ul>
3358 <p> To be able to see a progress bar during your uploads, your server must
3361 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3362 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3369 who logged out can not log in again in with the same nick.</a></h4>
3371 <p> This is related to the authentication mechanism (protocol) used by
3372 phpMyAdmin. To bypass this problem: just close all the opened
3373 browser windows and then go back to phpMyAdmin. You should be able to
3374 log in again.</p>
3378 limit error or a time limit error.</a></h4>
3380 <p> Compressed dumps are built in memory and because of this are limited to
3381 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3382 using
3384 (enabled by default). Zip exports can not be handled this way, so if you need
3385 Zip files for larger dump, you have to use another way.</p>
3389 when I rename a table or a column.</a></h4>
3391 <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>
3395 bundled with the MySQL server distribution.</a></h4>
3397 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3399 <pre>
3400 -- MySQL dump 8.22
3401 --
3402 -- Host: localhost Database: database
3403 ---------------------------------------------------------
3404 -- Server version 3.23.54
3405 </pre>
3407 <p> The invalid part of the code is the horizontal line made of dashes that
3408 appears once in every dump created with mysqldump. If you want to run your
3409 dump you have to turn it into valid MySQL. This means, you have to add a
3410 whitespace after the first two dashes of the line or add a # before it:
3411 <br />
3412 <code>
3413 -- -------------------------------------------------------<br />
3414 </code>
3415 or<br />
3416 <code>
3417 #---------------------------------------------------------
3418 </code>
3419 </p>
3426 <p> Please note that you should not use the separating string multiple times
3427 without any characters between them, or at the beginning/end of your table
3428 name. If you have to, think about using another TableSeparator or disabling
3429 that feature</p>
3434 <p> In Relation view, being able to choose a table in another database,
3435 or having more than one index column in the foreign key.<br /><br/>
3436 In Query-by-example (Query), automatic generation of the query
3437 LEFT JOIN from the foreign table.<br /><br/>
3438 </p>
3442 I get series of errors like "Warning: unable to parse url". How
3443 can this be fixed?</a></h4>
3444 <p>
3445 Your table neither have a primary key nor an unique one, so we must use a
3446 long expression to identify this row. This causes problems to parse_url
3447 function. The workaround is to create a primary or unique key.
3448 <br />
3449 </p>
3453 a MIME-Transformation onto!</a></h4>
3455 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3456 nested forms can be put inside the table where phpMyAdmin displays the results.
3457 You can, however, use any form inside of a table if keep the parent
3458 form-container with the target to tbl_row_delete.php and just put your own
3459 input-elements inside. If you use a custom submit input field, the form will
3460 submit itself to the displaying page again, where you can validate the
3461 $HTTP_POST_VARS in a transformation.
3463 For a tutorial on how to effectively use transformations, see our
3465 on the official phpMyAdmin-homepage.</p>
3469 MySQL server</a></h4>
3471 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3474 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3475 the quote-character (") is interpreted as an identifier quote character and
3476 not as a string quote character, which makes many internal phpMyAdmin
3478 statements. There is no workaround to this behaviour. News to this item will
3479 be posted in Bug report
3480 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3481 </p>
3485 more that one column with the same value
3486 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3487 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3489 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3490 can use it for the Edit and Delete links.</p>
3495 <p> phpMyAdmin uses a quick method to get the row count, and this method
3496 only returns an approximate count in the case of InnoDB tables. See
3498 a way to modify those results, but
3499 this could have a serious impact on performance.</p>
3504 <p> The number of records in queries containing COUNT and GROUP BY is
3505 not correctly calculated. Also, sorting results of a query like
3510 containing an hyphen.
3511 </a></h4>
3512 <p>
3513 The tests I have made with current MySQL 4.1.11 API shows that the
3514 API does not accept this syntax for the USE command. Enclosing the
3515 db name with backquotes works. For further confusion, no backquotes
3516 are needed with command-line mysql.
3517 </p>
3520 <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>
3521 <p>
3522 This has been a known limitation of phpMyAdmin since the beginning and
3523 it's not likely to be solved in the future.
3524 </p>
3526 <!-- Begin: Excel import limitations -->
3529 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3530 <p>
3531 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3532 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3533 <br /><br />
3534 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3535 </p>
3538 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3539 <p>
3540 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3541 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3542 </p>
3545 <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>
3546 <p>
3547 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3548 consider using a built-in type. These are almost always guarenteed to import correctly.
3549 </p>
3551 <!-- End: Excel import limitations -->
3552 <!-- Begin: CSV import limitations -->
3555 <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>
3556 <p>
3557 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.
3558 </p>
3560 <!-- End: CSV import limitations -->
3561 <!-- Begin: Import type-detection limitations -->
3564 <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>
3565 <p>
3566 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
3567 you will have to edit the structure to your liking post-import.
3568 <br /><br />
3569 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
3570 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.
3571 </p>
3573 <!-- End: Import type-detection limitations -->
3575 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3578 <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
3579 need to install it for each customer.
3580 </a></h4>
3581 <p>
3582 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3583 your users. The development of this feature was kindly sponsored by
3584 NetCologne GmbH.
3585 This requires a properly setup MySQL user management and phpMyAdmin
3586 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3588 </p>
3592 access.
3593 </a></h4>
3594 <p>
3595 This depends on your system.<br />
3596 If you're running a server which cannot be accessed by other people, it's
3597 sufficient to use the directory protection bundled with your webserver
3599 If other people have telnet access to your server, you should use
3600 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3601 <br /><br />
3602 Suggestions:
3603 </p>
3604 <ul>
3605 <li>
3607 </li>
3608 <li>
3609 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3610 is a user whose password is only known to you, and apache is the
3611 group under which Apache runs.
3612 </li>
3613 <li>
3614 You should use PHP safe mode, to protect from other users that try
3616 </li>
3617 </ul>
3622 </a></h4>
3623 <p>
3628 </p>
3631 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3632 authentication.
3633 </a></h4>
3637 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3638 and/or
3640 are wrong.</li>
3642 <li>You have already setup a security mechanism for the
3643 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3644 phpMyAdmin's authentication, so remove it.</li>
3645 </ul>
3652 and put the privileges you want. For example,
3654 would let a user create/manage his/her database(s).</p>
3659 <p> If you have existing rules from an old .htaccess file, you can take them
3662 be a major benefit here if your installation is suited to using it. Then
3663 you can just add those updated lines into the
3667 <p> If you want a pre-made sample, you can try this fragment. It stops the
3668 'root' user from logging in from any networks other than the private
3671 <pre>
3672 //block root from logging in except from the private networks
3673 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3674 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3675 'deny root from all',
3676 'allow root from localhost',
3680 );
3681 </pre>
3686 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3687 different than the one set in your
3689 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3690 while a domain name is defined in the config file.</p>
3695 <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>
3701 when trying to create a table with more than 14 columns.
3702 </a></h4>
3703 <p>
3704 We could reproduce this problem only under Win98/98SE. Testing under
3705 WinNT4 or Win2K, we could easily create more than 60 columns.
3706 <br />
3707 A workaround is to create a smaller number of columns, then come back to
3708 your table properties and add the other columns.
3709 </p>
3713 <p>
3714 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3715 with each script/website that use forms.<br />
3716 Upgrade or downgrade your Xitami server.
3717 </p>
3720 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3721 <p>
3722 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3723 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3724 don't seem to work.<br />
3726 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3727 the user's temporary directory, so they must be moved before closing
3728 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3731 </p>
3735 Explorer never stores the cookies.
3736 </a></h4>
3737 <p>
3738 MS Internet Explorer seems to be really buggy about cookies, at least till
3740 in this area!
3741 <br />
3742 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3743 work!
3744 </p>
3748 rows.
3749 </a></h4>
3750 <p>
3752 </p>
3755 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3756 when trying to modify a row in a table with many columns, or with a text
3757 column
3758 </a></h4>
3759 <p>
3760 Your table neither have a primary key nor an unique one, so we must use a
3761 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
3762 those browsers, and this not happen in Netscape, for example. The
3763 workaround is to create a primary or unique key, or use another browser.
3764 <br />
3765 </p>
3769 page.
3770 </a></h4>
3771 <p>
3772 Some browsers support right-clicking into the frame you want to refresh,
3773 just do this in the right frame.<br />
3774 </p>
3778 query box.
3779 </a></h4>
3780 <p>
3781 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3782 Mozilla versions.<br />
3783 </p>
3787 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3788 </a></h4>
3789 <p>
3790 This is a Mozilla bug (see bug #26882 at
3792 </p>
3797 </a></h4>
3798 <p>
3799 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3800 data in octet-stream mode. Since we can't detect the specific Netscape
3801 version, we cannot workaround this bug.
3802 </p>
3806 wrong.</a></h4>
3808 <p> Please ensure that you have set your browser's character set to the one of the
3809 language file you have selected on phpMyAdmin's start page.
3810 Alternatively, you can try the auto detection mode that is supported by the
3811 recent versions of the most browsers.</p>
3814 <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
3817 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3818 Netscape and Mozilla do not have this problem.</p>
3821 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3822 I cannot manage two servers: I log in to the first one, then the other one,
3823 but if I switch back to the first, I have to log in on each operation.</a></h4>
3829 but nothing happens after that, only a blank screen.</a></h4>
3840 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3845 address and you are starting
3847 containing a domain name, or the reverse situation.</li>
3848 <li>Security settings in IE and/or Microsoft Security Center are
3849 too high, thus blocking scripts execution.</li>
3850 <li>The Windows Firewall is blocking Apache and MySQL. You must
3854 </ul>
3857 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3858 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3859 installed in their Firefox is causing the problem.</p>
3863 clause is generated when I browse a table.</a></h4>
3864 <p> This happens only when both of these conditions are met: using the
3874 </a></h4>
3875 <p>
3876 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3877 specifying a wrong column-type.<br />
3878 Common errors include:
3879 </p>
3880 <ul>
3883 </ul>
3884 <p>
3885 Also, look at the syntax chapter in the MySQL manual to confirm that your
3886 syntax is correct.
3887 </p>
3891 columns and
3892 phpMyAdmin generates only one index with those two columns.
3893 </a></h4>
3894 <p>
3895 This is the way to create a multi-columns
3896 index. If you want two indexes, create the first one when creating the
3897 table, save, then display the table properties and click the Index link to
3898 create the other index.
3899 </p>
3903 <p>
3904 Since version 2.2.3, you have a checkbox for each column that can be null.
3906 column's value. Since version 2.5.5, you have to use the checkbox to get
3908 a literal NULL in the column, and not a NULL value (this works in PHP4).
3909 </p>
3914 <p> Click on a database or table name in the left frame, the properties will be
3916 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3917 statements that can be used to recreate your database/table.
3918 <br /><br />
3920 transmit the resulting dump to your station. Depending on your PHP
3921 configuration, you will see options to compress the dump. See also the
3923 configuration variable.<br /><br />
3926 this document.</p>
3931 </a></h4>
3933 <p> Click on a database name in the left frame, the properties will be
3935 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3937 the path to your dump filename, or use the Browse button. Then click Go.
3938 <br /><br />
3940 that you upgrade to take advantage of the new features.
3941 <br /><br />
3943 in this document.
3944 </p>
3949 <p> Here is an example with the tables persons, towns and countries, all
3951 table, create it as explained in the configuration section. Then create the
3952 example tables:</p>
3954 <pre>
3955 CREATE TABLE REL_countries (
3956 country_code char(1) NOT NULL default '',
3957 description varchar(10) NOT NULL default '',
3958 PRIMARY KEY (country_code)
3959 ) TYPE=MyISAM;
3961 INSERT INTO REL_countries VALUES ('C', 'Canada');
3963 CREATE TABLE REL_persons (
3964 id tinyint(4) NOT NULL auto_increment,
3965 person_name varchar(32) NOT NULL default '',
3967 country_code char(1) NOT NULL default '',
3968 PRIMARY KEY (id)
3969 ) TYPE=MyISAM;
3971 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3972 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3974 CREATE TABLE REL_towns (
3976 description varchar(30) NOT NULL default '',
3977 PRIMARY KEY (town_code)
3978 ) TYPE=MyISAM;
3980 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3981 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3982 </pre>
3988 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3992 </ul>
4000 <li>In the columns row, choose persons.person_name and click the
4002 <li>Do the same for towns.description and countries.descriptions in the
4005 the correct joins have been generated</li>
4007 </ul>
4011 <p>
4012 Starting from the previous example, create the pma_table_info as explained
4013 in the configuration section, then browse your persons table,
4014 and move the mouse over a town code or country code.
4015 <br /><br />
4016 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
4017 enables: drop-down list of possible values.
4018 </p>
4021 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
4022 <p>
4025 <br /><br />
4026 Then you need to think about your schema layout. Which tables will go on
4027 which pages?
4028 </p>
4029 <ul>
4035 page and click Go. If you like, you
4037 linked tables onto the new page.</li>
4038 <li>Select the name of the new page (making sure the Edit radio button
4039 is selected) and click Go.</li>
4041 Coordinates are relative; your diagram will
4042 be automatically scaled to fit the page. When initially placing tables
4043 on the page, just pick any coordinates -- say, 50x50. After clicking
4045 position the element correctly.</li>
4047 first be sure to click the Save
4048 button beneath the list of tables and coordinates, to save any changes
4049 you made there. Then scroll all the way down, select the
4051 you want, and click Go.</li>
4052 <li>Internet Explorer for Windows may suggest an incorrect filename when
4057 browsers on Windows, do not have this problem.</li>
4058 </ul>
4062 columns!</a></h4>
4064 <p> No, it's MySQL that is doing
4070 underscores in the database name?</a></h4>
4072 <p> If you do not put a backslash before the underscore, this is a wildcard
4075 john2db ...<br /><br />
4077 If you put a backslash before the underscore, it means that the database
4078 name will have a real underscore.</p>
4082 statistics pages?</a></h4>
4093 if it already exists during the import. It does NOT drop the table after
4094 your export, it only affects the import file.</li>
4096 Otherwise, you may get an error if the table name exists but has a
4097 different structure.</li>
4099 (if any) will be included in backup.</li>
4101 column and table names formed with special characters are protected.</li>
4103 types set in the pmadb in the dump as
4105 </li>
4106 </ul>
4111 command, for better documentation (but resulting file is bigger).</li>
4113 once the INSERT verb and the table name.</li>
4116 </li>
4118 more info is provided in the
4120 but basically with this selected, invalid values are adjusted and
4121 inserted rather than causing the entire statement to fail.</li>
4122 </ul>
4126 in its name.</a></h4>
4129 is the normal way to reference a database and table name. Worse, MySQL
4130 will usually let you create a database with a dot, but then you cannot
4131 work with it, nor delete it.</p>
4144 for usage.<br />
4145 On a more recent pear version, I had problems with the state of Net_DIME
4146 being beta, so this single command
4148 needed modules.<br />
4149 If you use the Validator, you should be aware that any
4151 submit will be stored anonymously (database/table/column names,
4152 strings, numbers replaced with generic values). The Mimer
4155 We utilize it as free SOAP service.</p>
4159 it, but MySQL says "BLOB column '...' used in key specification without
4162 <p> The right way to do this, is to create the column without any indexes,
4164 dialog. On this page, you will be able to choose your BLOB column, and
4165 set a size to the index, which is the condition to create an index on
4166 a BLOB column.</p>
4170 editing fields?</a></h4>
4172 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4173 with many editing fields (table structure changes, row editing, etc.)
4174 (must be enabled in configuration - see.
4176 You can also have a look at the directive
4178 ('vertical') and see if this eases up editing for you.</p>
4182 WTF is this feature then useful for?</a></h4>
4184 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4185 on them. Otherwise you could just put a comment on the column. Because entering
4186 your own mimetype will cause serious syntax checking issues and validation,
4187 this introduces a high-risk false-user-input situation. Instead you have to
4188 initialize mimetypes using functions or empty mimetype definitions.<br />
4189 Plus, you have a whole overview of available mimetypes. Who knows all those
4190 mimetypes by heart so he/she can enter it at will?</p>
4194 can't I see any bookmarks below the query box? What is this variable for?
4195 </a></h4>
4197 <p> Any query you have executed can be stored as a bookmark on the page where the
4198 results are displayed. You will find a button labeled 'Bookmark this query'
4199 just at the end of the page.<br />
4200 As soon as you have stored a bookmark, it is related to the database you run
4201 the query on. You can now access a bookmark dropdown on each page, the query
4202 box appears on for that database.<br /><br />
4204 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4208 aware of that you HAVE to create a valid query, otherwise your query won't be
4209 even able to be stored in the database.<br />
4211 for your query will remain the way it is, but will be stripped of the /**/
4212 chars. So you can use:<br /><br />
4216 which will be expanded to<br /><br />
4220 in your query, where VARIABLE is the string you entered in the input box. If
4221 an empty string is provided, no replacements are made.<br /><br />
4223 A more complex example. Say you have stored this query:<br /><br />
4225 <br /><br />
4228 the full query will be:<br /><br />
4231 <br /><br />
4235 spaces inserted there
4236 will be later also inserted as spaces in your query and may lead to unexpected
4237 results especially when
4239 Your initial query which is going to be stored as a bookmark has to yield at
4240 least one result row so
4241 you can store the bookmark. You may have that to work around using well
4245 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4246 include exported table?</a></h4>
4248 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4249 document should look like following one (assuming you have table
4252 <pre>
4253 \documentclass{article} % or any class you want
4254 \usepackage{longtable} % for displaying table
4255 \begin{document} % start of document
4256 \include{table} % including exported table
4257 \end{document} % end of document
4258 </pre>
4262 access them.
4263 </a></h4>
4266 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4267 enable users to see all the database names.
4270 So if your users do not need those privileges, you can remove them and their
4271 databases list will shorten.</p>
4275 possible values for a column, based on some foreign table?</a></h4>
4277 <p> You have to setup appropriate links between the tables, and also
4281 foreign table, a drop-down list of values will be available.
4282 You will see two lists of values, the first list containing the key
4283 and the display column, the second list containing the display column
4284 and the key. The reason for this is to be able to type the first
4285 letter of either the key or the display column.<br /><br />
4287 For 100 values or more, a distinct window will appear, to browse foreign
4288 key values and choose one. To change the default limit of 100, see
4289 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4293 automatically when entering Browse mode for a table?</a></h4>
4295 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4296 </p>
4300 Excel files, how can I enable that?</a></h4>
4302 <p> You can use
4304 which works out of the box, but phpMyAdmin supports direct export
4305 to Microsoft Excel version 97 and newer. For this to work, you need to set
4310 <pre>
4311 cd phpMyAdmin
4312 mkdir tmp
4313 chmod o+rwx tmp
4314 </pre>
4318 what happens to my column comments stored in pmadb?</a></h4>
4320 <p> Automatic migration of a table's pmadb-style column comments to the native
4321 ones is done whenever you enter Structure page for this table.</p>
4326 <p> First, for general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. We currently support streaming if you are running MySQL 5.1 with the PBXT and PBMS storage engines.</p>
4328 <ol>
4329 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of something like "localhost".</li>
4330 <li>A current limitation is that your first login via phpMyAdmin to a freshly-started server must be done with an account that has the SUPER privilege.</li>
4331 <li>On your target database, go to Operations and in the "BLOB Repository" section, click "Enable". This creates the PBMS system tables inside your database.</li>
4332 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4333 <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 column instead of the repository.</li>
4334 <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>
4335 </ol>
4342 <p> Our Bug Tracker is located at
4344 under the Bugs section.<br /><br />
4346 But please first discuss your bug with other users:<br />
4352 existing language, where do I start?</a></h4>
4354 <p> Always use latest Git version of po file to translate. You can optionally
4356 server</a> where you can also get latest po files and merge them
4357 with your translations. For creating new translation simply use
4361 to do this) or ask on mailing list to add the translation to the web
4362 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Gettext_for_translators">our wiki</a>.
4363 </p>
4364 <p>
4365 Please note that we try not to use HTML entities like &eacute; in
4366 the translations, since we define the right character set in the file.
4367 With HTML entities, the text on JavaScript messages would not
4368 display correctly.
4369 However there are some entities that need to be there, for quotes
4370 ,non-breakable spaces, ampersands, less than, greater than.
4371 </p>
4372 <p>
4373 You can then put your translations, as a zip file to avoid losing special
4374 characters, on the sourceforge.net translation tracker.
4375 </p>
4376 <p>
4377 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4378 list, because this is where we ask for translations of new messages.
4379 </p>
4383 phpMyAdmin. How should I proceed?</a></h4>
4388 <tt>git clone
4389 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4390 </li>
4392 <li>generate patch with your changes:
4394 </li>
4397 tracker of the phpMyAdmin project</a>.
4398 </li>
4399 </ol>
4401 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4403 <p> Write access to the repository is granted only to experienced developers who
4404 have already contributed something useful to phpMyAdmin.<br />
4410 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4412 <p> Please refer to
4413 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4414 </p>
4419 <p> If you use Apache web server, phpMyAdmin exports information about
4420 authentication to Apache environment and it can be used in Apache logs.
4421 Currently there are two variables available:
4422 </p>
4423 <dl>
4425 <dd>User name of currently active user (he does not have to be logged
4426 in).</dd>
4433 </dl>
4434 <p>
4436 </p>
4437 <pre>
4440 </pre>
4441 <p>
4442 You can then use any log analyzing tools to detect possible break-in
4443 attempts.
4444 </p>
4450 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4451 It allows you to connect to local as well as remote servers.This requires you to enter
4452 server host name, username, password, port and the name of the database. Therefore you can
4453 now synchronize your databases placed on the same server or some remote server.
4454 </p>
4456 <p>
4457 This feature is helpful for developers who need to replicate their
4458 databases’ structure as well as data. Moreover, this feature not only
4459 helps replication but also facilitates the user to keep his/her database
4460 in sync with another database. Other than the full database, certain
4461 tables of the databases can also be synchronized.
4462 </p>
4464 <p>
4465 You need to fill in the host name of the server, the username and
4466 password of an user account already there in MySQL. Port is by default
4467 populated with 3306 (MySQL default port). Then the name of the database
4468 should be mentioned at the end. All the information other than the port
4469 needs to be filled explicitly for the source as well as target servers.
4470 </p>
4472 <p>
4473 After successfully passing through the authentication phase, the source and
4474 target database table names will be displayed. It will be a tabular
4475 representation.
4476 </p>
4478 <p>
4479 On the left, are listed the source database table names. Some of the
4480 names have a ‘+’ plus sign preceding them. This shows that these tables
4481 are only present in source database and they need to be added to the
4482 target database in order to synchronize the target database. The tables
4483 whose names are not preceded by a ‘+’ sign are already present in the
4484 target database.
4485 </p>
4487 <p>
4488 On the right, are listed the target database table names. There are few
4489 table names that have “(not present)” appended after their names. This
4490 means that these tables are to be created in target database in order to
4491 synchronize target database with source database. Some tables’ names
4492 have a ‘-’ minus sign preceding them. This shows that these tables are
4493 only present in target database and they will remain unchanged in the
4494 target database. The column in the middle shows the difference between
4495 the source and target corresponding tables.
4496 </p>
4498 <p>
4499 The difference is depicted by the red and green buttons with S and D
4500 letters, indicating that either Structure or Data are not up to date. By
4501 clicking on them, they will turn grey, what means that they will be synchronised.
4502 </p>
4504 <!-- DEVELOPERS -->
4507 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4508 great features have been written by other people and you too can help to
4509 make phpMyAdmin a useful tool.</p>
4511 <p> If you're planning to contribute source, please read the following
4512 information:</p>
4518 it free from other code.<br />
4519 Commonly used functions should be added to
4522 <li>Obviously, you're free to use whatever coding style you want. But
4523 please try to keep your code as simple as possible: beginners are
4524 using phpMyAdmin as an example application.<br />
4525 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4526 compliant on one hand, they fit the
4529 coding standards</a>
4530 on the other hand. Please pay attention to this.</li>
4531 <li>Please enable showing PHP errors and warnings by the
4533 configuration directive.</li>
4534 <li>Please try to keep up the file-naming conventions. Table-related stuff
4537 <li>Please use gettext wrappers around all messages
4540 script. To use translated messages, call
4542 Gettext.</li>
4546 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4547 better debug and profile their code.<br />
4548 Please see the
4550 options for more information.<br />
4551 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4552 lost during its re-entry into Earth's atmosphere and in memory of the
4553 brave men and women who gave their lives for the people of Earth.</li>
4554 </ul>
4558 <pre>
4569 </pre>
4571 <p>
4572 This program is free software; you can redistribute it and/or modify
4573 it under the terms of the GNU General Public License version 2,
4574 as published by the Free Software Foundation.
4575 </p>
4577 <p>
4578 This program is distributed in the hope that it will be useful,
4579 but WITHOUT ANY WARRANTY; without even the implied warranty of
4580 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4581 GNU General Public License for more details.
4582 </p>
4584 <p>
4585 You should have received a copy of the GNU General Public License
4586 along with this program; if not, write to the Free Software
4588 </p>
4590 <!-- CREDITS -->
4595 <ul>
4598 <ul>
4601 </ul></li>
4604 <ul>
4609 </ul></li>
4612 <ul>
4618 </ul></li>
4621 <ul>
4623 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4624 generate XHTML1.0 and CSS2 compliant codes</li>
4627 </ul></li>
4630 <ul>
4638 </ul></li>
4641 <ul>
4646 </ul></li>
4649 <ul>
4652 </ul></li>
4655 <ul>
4657 </ul></li>
4660 <ul>
4663 </ul></li>
4666 <ul>
4670 </ul></li>
4673 <ul>
4676 </ul></li>
4679 <ul>
4686 </ul></li>
4689 <ul>
4693 </ul></li>
4696 <ul>
4702 </ul></li>
4705 (http://sf.net/projects/phpmysqlformgen/)
4706 <ul>
4708 </ul></li>
4711 <ul>
4713 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4718 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4722 </ul></li>
4725 <ul>
4727 </ul></li>
4730 <ul>
4732 </ul></li>
4735 <ul>
4737 </ul></li>
4740 <ul>
4741 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4742 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4743 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4744 </ul></li>
4747 <ul>
4749 </ul></li>
4752 <ul>
4754 </ul></li>
4757 <ul>
4759 </ul></li>
4762 <ul>
4765 </ul></li>
4768 <ul>
4771 </ul></li>
4774 <ul>
4776 </ul></li>
4779 <ul>
4782 </ul></li>
4784 <li>Ivan A Kirillov
4785 <ul>
4787 </ul></li>
4790 <ul>
4792 </ul></li>
4795 <ul>
4797 </ul></li>
4800 <ul>
4802 </ul></li>
4805 <ul>
4807 </ul></li>
4810 <ul>
4812 </ul></li>
4815 <ul>
4817 </ul></li>
4819 </ul>
4821 <p>
4822 And also to the following people who have contributed minor changes,
4823 enhancements, bugfixes or support for a new language since version 2.1.0:
4824 </p>
4826 <p>
4827 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4828 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4829 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4830 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4832 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4833 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4834 Luís V., Martijn W. van der Lee,
4835 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4837 </p>
4842 <p>
4843 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4844 to create a web-based interface to MySQL using PHP3. Although I have not
4845 used any of his source-code, there are some concepts I've borrowed from
4846 him. phpMyAdmin was created because Peter told me he wasn't going to
4847 further develop his (great) tool.
4848 </p>
4849 <p>
4850 Thanks go to
4851 </p>
4852 <ul>
4854 code for the check when dropping a table or database. He also suggested
4855 that you should be able to specify the primary key on tbl_create.php3. To
4856 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4857 well as a bug-report. Plus many smaller improvements.
4858 </li>
4860 were introduced in 1.3.0 (including quite significant ones like the
4861 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4862 bug-fixes and help.
4863 </li>
4865 language-independent by outsourcing the strings to a separate file. He
4866 also contributed the French translation.
4867 </li>
4869 tbl_select.php3, a feature to display only some columns from a table.
4870 </li>
4872 functions in tbl_change.php3. He also added the
4874 </li>
4876 servers and is a regular contributor for bug-fixes.
4877 </li>
4879 features for 2.0.6.
4880 </li>
4881 </ul>
4882 <p>
4883 The following people have contributed minor changes, enhancements, bugfixes
4884 or support for a new language:
4885 </p>
4886 <p>
4887 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4888 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4889 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4890 G. Wieggers.
4891 </p>
4892 <p>
4893 And thanks to everyone else who sent me email with suggestions, bug-reports
4894 and or just some feedback.
4895 </p>
4901 <ul>
4903 - the default name of Apache's directory-level configuration file.</li>
4907 - a software application that enables a user to display and interact with
4908 text, images, and other information typically located on a web page at a
4909 website on the World Wide Web.</li>
4911 - a free software/open source data compression algorithm and program
4912 developed by Julian Seward.</li>
4914 - an important World Wide Web technology that enables a client web browser
4915 to request data from a program executed on the Web server.</li>
4917 - a log or record of changes made to a project.</li>
4919 - a computer system that accesses a (remote) service on another computer
4920 by some kind of network.</li>
4922 - a set of data values of a particular simple type, one for each row of
4923 the table.</li>
4925 - a packet of information sent by a server to a World Wide Web browser
4926 and then sent back by the browser each time it accesses that server.</li>
4928 - Comma-separated values</li>
4931 - an organized collection of data.</li>
4934 - a PHP module that extends PHP with additional functionality.</li>
4936 - a list of commonly asked question and there answers.</li>
4938 - one part of divided data/columns.</li>
4940 - a field or group of fields in a database record that point to a key
4941 field or group of fields forming a key of another database record in some
4942 (usually different) table.</li>
4944 - the free PDF library</li>
4946 GD Graphics Library</a> - a library by Thomas Boutell and others for
4947 dynamically manipulating images.</li>
4950 - gzip is short for GNU zip, a GNU free software file compression
4951 program.</li>
4953 - any machine connected to a computer network, a node that has a hostname.</li>
4955 - the unique name by which a network attached device is known on a network.</li>
4957 (HyperText Transfer Protocol)</a>
4958 - the primary method used to transfer or convey information on the World
4959 Wide Web.</li>
4962 additional security measures.</li>
4963 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4964 - a set of Internet-based services for servers using Microsoft Windows.</li>
4966 - a feature that allows quick access to the rows in a table.</li>
4968 - a data-oriented protocol used by source and destination hosts for
4969 communicating data across a packet-switched internetwork.</li>
4971 - a unique number that devices use in order to identify and communicate
4972 with each other on a network utilizing the Internet Protocol standard.</li>
4974 (Internet Server Application Programming Interface)</a>
4975 - the API of Internet Information Services (IIS).</li>
4977 - a business or organization that offers users access to the Internet and related services.</li>
4979 - a most commonly used standard method of lossy compression for
4980 photographic images.</li>
4986 - line of personal computers is designed, developed, manufactured, and
4987 marketed by Apple Computer.</li>
4988 <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>
4989 - the operating system which is included with all currently shipping Apple
4990 Macintosh computers in the consumer and professional markets.</li>
4992 - a cryptographic library.</li>
4994 - the MCrypt PHP extension.</li>
4995 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4996 - an Internet Standard for the format of e-mail.</li>
4998 - some sort of extension for the Apache Webserver.</li>
5000 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5001 Management System (DBMS).</li>
5003 - the improved MySQL client PHP extension.</li>
5005 - the MySQL client PHP extension.</li>
5007 - open standard for office documents.</li>
5008 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5009 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5011 (Portable Document Format)</a>
5012 - a file format developed by Adobe Systems for representing two
5013 dimensional documents in a device independent and resolution independent
5014 format.</li>
5016 - the PHP Extension and Application Repository.</li>
5018 - the perl-compatible regular expression functions for PHP</li>
5020 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5021 programming language used mainly for developing server-side applications
5022 and dynamic web content, and more recently, a broader range of software
5023 applications.</li>
5025 - a connection through which data is sent and received.</li>
5027 - Request for Comments (RFC) documents are a series of memoranda
5028 encompassing new research, innovations, and methodologies applicable to
5029 Internet technologies.</li>
5033 - represents a single, implicitly structured data item in a table.</li>
5035 - a computer system that provides services to other computing
5036 systems over a network.</li>
5037 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
5038 - handlers for different table types</li>
5040 - a form of inter-process communication.</li>
5042 Sockets Layer)</a>
5043 - a cryptographic protocol which provides secure communication on the Internet.</li>
5045 - Structured Query Language</li>
5047 - a set of data elements (cells) that is organized, defined and stored as
5048 horizontal rows and vertical columns where each item can be uniquely
5049 identified by a label or key or by it?s position in relation to other items.</li>
5052 - a type of archive file format: the Tape ARchive format.</li>
5054 - one of the core protocols of the Internet protocol suite.</li>
5058 - a sequence of characters, conforming to a standardized format, that is
5059 used for referring to resources, such as documents and images on the
5060 Internet, by their location.</li>
5062 - A computer (program) that is responsible for accepting HTTP requests
5063 from clients and serving them Web pages.</li>
5065 - a W3C-recommended general-purpose markup language for creating
5066 special-purpose markup languages, capable of describing many different
5067 kinds of data.</li>
5069 - a popular data compression and archival format.</li>
5071 - an open-source, cross-platform data compression library by Jean-loup
5072 Gailly and Mark Adler.</li>
5073 </ul>
5074 </div>
5077 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5080 <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>
5081 </ul>
5083 </body>
5084 </html>