| blob | 13bdc90f219aec8a8900477795a1c83977bb630f |
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, fields 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 field 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 </li>
930 </ul>
934 future development of the cross-db relations.
935 </dd>
939 </dt>
940 <dd>
941 Since release 2.3.0 you can describe, in a special 'table_info'
942 table, which field is to be displayed as a tool-tip when moving the
943 cursor over the corresponding key.<br />
944 This configuration variable will hold the name of this special
945 table. To allow the usage of this functionality:
947 <li>put the table name in
949 <li>then for each table where you want to use this feature,
951 to choose the field.</li>
952 </ul>
954 </dd>
958 </dt>
961 the relations between your tables. To do this it needs two tables
966 schema output).<br /><br />
970 To allow the usage of this functionality:
973 infrastructure</li>
974 <li>put the correct table names in
977 </ul>
980 </dd>
984 </dt>
986 Since release 2.3.0 you can store comments to describe each column for
988 <br /><br />
990 Starting with release 2.5.0, comments are consequently used on the table
991 property pages and table browse view, showing up as tool-tips above the
992 column name (properties page) or embedded within the header of table in
993 browse view. They can also be shown in a table dump. Please see the
994 relevant configuration directives later on.<br /><br />
996 Also new in release 2.5.0 is a MIME-transformation system which is also
998 Transformations</a> for further information. To use the
999 MIME-transformation system, your column_info table has to have the three
1000 new fields 'mimetype', 'transformation', 'transformation_options'.
1001 <br /><br />
1003 To allow the usage of this functionality:
1005 infrastructure</li>
1006 <li>put the table name in
1010 <pre>
1011 ALTER TABLE `pma_column_comments`
1012 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1013 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1014 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1015 </pre>
1018 renamed from<br />
1021 </ul>
1022 </dd>
1026 </dt>
1029 all queries you entered manually into the phpMyAdmin interface. If you
1030 don't want to use a table-based history, you can use the JavaScript-based
1031 history. Using that, all your history items are deleted when closing the
1032 window.<br /><br />
1034 Using
1036 you can specify an amount of history items you want to have on hold. On
1037 every login, this list gets cut to the maximum amount.<br /><br />
1039 The query history is only available if JavaScript is enabled in your
1040 browser.<br /><br />
1042 To allow the usage of this functionality:
1045 infrastructure</li>
1047 </li>
1048 </ul>
1049 </dd>
1053 </dt>
1054 <dd>
1055 Since release 3.3.x a tracking mechanism is available.
1057 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1058 and data definition statements. After enabling it you can create versions of tables.
1059 <br/><br/>
1060 The creation of a version has two effects:
1062 <ul>
1064 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1065 </ul>
1067 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1068 For the report you can use filters, for example you can get a list of statements within a date range.
1069 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1070 In addition you can export the (filtered) report to a file or to a temporary database.
1071 <br/><br/>
1073 To allow the usage of this functionality:
1075 <ul>
1078 </ul>
1079 </dd>
1082 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1083 </dt>
1084 <dd>
1085 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1086 <br/><br/>
1087 If this is set to true and you create a table or view with
1089 <ul>
1092 </ul>
1094 and no version exists for it, the mechanism will
1095 create a version for you automatically.
1096 </dd>
1099 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1100 </dt>
1101 <dd>
1102 Defines the list of statements the auto-creation uses for new versions. Default value is
1103 <br/>
1105 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1106 CREATE INDEX,DROP INDEX,
1107 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1108 CREATE VIEW,ALTER VIEW,DROP VIEW,
1109 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1110 </dd>
1113 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1114 </dt>
1115 <dd>
1116 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1117 <br/><br/>
1118 </dd>
1122 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1123 </dt>
1124 <dd>
1125 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1126 <br/><br/>
1127 </dd>
1130 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1131 </dt>
1132 <dd>
1133 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1134 <br/><br/>
1135 </dd>
1140 </dt>
1142 to visually manage the relations.
1143 <br /><br />
1145 To allow the usage of this functionality:
1148 infrastructure</li>
1150 </li>
1151 </ul>
1152 </dd>
1155 </dt>
1157 column_info table got enhanced with three new fields. If the above variable
1159 latest table structure available. If not, it will emit a warning to the
1160 superuser.<br /><br />
1162 You can disable this checking behavior by setting the variable to false,
1163 which should offer a performance increase.<br /><br />
1165 Recommended to set to FALSE, when you are sure, your table structure is
1166 up to date.</dd>
1168 boolean</dt>
1169 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1170 </dd>
1172 boolean</dt>
1173 <dd>Whether to allow logins without a password. The default
1175 to a MySQL server with was left with an empty password for root or
1176 on which an anonymous (blank) user is defined.
1177 </dd>
1180 </dt>
1182 authentication is disabled.<br /><br />
1185 all deny rules followed by allow rules. Access is allowed by default. Any
1186 client which does not match a Deny command or does match an Allow command
1187 will be allowed access to the server. <br /><br />
1190 applies all allow rules followed by deny rules. Access is denied by
1191 default. Any client which does not match an Allow directive or does
1192 match a Deny directive will be denied access to the server.<br /><br />
1194 If your rule order is set to 'explicit', the authentication is
1195 performed in a similar fashion to rule order 'deny,allow', with the
1199 and was available in Apache by specifying allow and deny rules without
1200 setting any order.<br /><br />
1202 Please also see <a
1204 address behind proxies.
1205 </dd>
1207 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1208 </dt>
1209 <dd>The general format for the rules is as such:
1211 <pre>
1213 </pre>
1218 well (please note that those containing SERVER_ADDRESS might not be
1219 available on all webservers):
1220 <pre>
1226 </pre>
1228 Having an empty rule list is equivalent to either using
1234 following work:<br />
1236 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1237 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1238 But the following does not work:<br />
1241 Also IPv6 addresses are not supported.
1242 </dd>
1244 <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.
1245 </dd>
1246 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1248 DATABASES</tt> command used to fetch the name of available databases will
1249 probably be too slow, so it can be replaced by faster commands (see
1251 </dd>
1253 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1254 </dd>
1255 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1256 <dd>Name of session which will be used for signon authentication method.
1257 </dd>
1259 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1260 </dd>
1262 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1263 </dd>
1266 <dd>If you have more than one server configured, you can set
1268 that server when phpMyAdmin is started, or set it to 0 to be given a
1269 list of servers without logging in.<br />
1271 MUST be set to that server.</dd>
1274 <dd>The maximum number of database names to be displayed in the
1275 navigation frame and the database list.</dd>
1278 <dd>The maximum number of table names to be displayed in the
1279 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1280 when in Light mode.</dd>
1283 <dd>The maximum number of characters when a SQL query is displayed. The
1284 default limit of 1000 should be correct to avoid the display of tons
1285 of hexadecimal codes that represent BLOBs, but some users have real
1286 SQL queries that are longer than 1000 characters. Also, if a query's
1287 length exceeds this limit, this query is not saved in the history.</dd>
1290 <dd>Defines whether to use GZip output buffering for increased
1292 Set to true/false for enabling/disabling. When set to 'auto' (string),
1293 phpMyAdmin tries to enable output buffering and will automatically disable
1294 it if your browser has some problems with buffering. IE6 with a certain patch
1295 is known to cause data corruption when having enabled buffering.</dd>
1298 <dd>Whether persistent connections should be used or not (mysql_connect or
1299 mysql_pconnect).</dd>
1305 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1306 to zero, no time limit is imposed.<br />
1307 This setting is used while importing/exporting dump files and in the
1308 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1315 <dd>Set the number of bytes a script is allowed to allocate. If set
1316 to zero, no limit is imposed.<br />
1317 This setting is used while importing/exporting dump files and at some
1318 other places in phpMyAdmin so you definitely don't want to put here
1319 a too low value. It has no effect when PHP is running in safe mode.<br />
1320 You can also use any string as in php.ini, eg. '16M'. Ensure
1324 <dd>Mark used tables and make it possible to show databases with locked
1329 generated by phpMyAdmin should be displayed or not.</dd>
1332 <dd>Defines whether normal users (non-administrator) are allowed to
1333 delete their own database or not. If set as FALSE, the link "Drop
1335 mydatabase" will be rejected. Quite practical for
1337 customers.<br />
1338 Please note that this limitation of SQL queries is not as strict as
1339 when using MySQL privileges. This is due to nature of SQL queries
1340 which might be quite complicated. So this choice should be viewed as
1341 help to avoid accidental dropping rather than strict privilege
1342 limitation.</dd>
1346 displayed when you're about to lose data.</dd>
1349 <dd>Define whether the previous login should be recalled or not in cookie
1350 authentication mode.<br /><br />
1352 This is automatically disabled if you do not have configured
1354 </dd>
1357 <dd>Define how long is login cookie valid. Please note that php
1358 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1359 might limit session validity and if session is lost, login cookie is
1361 at least as high is $cfg['LoginCookieValidity'] is set.</dd>
1365 means that it will be kept for existing session. This is recommended
1366 for not trusted environments.</dd>
1369 <dd>If enabled (default), logout deletes cookies for all servers,
1370 otherwise only for current one. Setting this to false makes it easy to
1371 forget to log out from other server, when you are using more of
1372 them.</dd>
1378 <dd>Define whether phpMyAdmin will continue executing a multi-query
1379 statement if one of the queries fails. Default is to abort execution.</dd>
1382 <dd>Define whether phpMyAdmin will output the results of each query of a
1383 multi-query statement embedded into the
1388 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1389 <br /><br />
1392 MySQL servers behind the firewall where your
1394 </dd>
1403 <dd>Defines whether to use a select-based menu and display only the current
1404 tables in the left frame (smaller page). Only in Non-Lightmode you can
1405 use the feature to display nested folders using
1407 </dd>
1410 <dd>In light mode, defines whether to display the names of databases (in the
1411 selector) using a tree, see also
1413 </dd>
1416 string or array</dt>
1417 <dd>The string used to separate the parts of the database name when showing
1418 them in a tree. Alternatively you can specify more strings in an array
1419 and all of them will be used as a separator.</dd>
1422 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1423 This means if you have tables like 'first__second__third' this will be
1425 If set to FALSE or empty, the feature is disabled. NOTE: You should
1426 not use this separator at the beginning or end of a
1427 table name or multiple times after another without any other
1428 characters in between.</dd>
1431 <dd>Defines how many sublevels should be displayed when splitting
1432 up tables by the above separator.</dd>
1435 <dd>Defines whether to display table comment as tool-tip in left frame or
1436 not.</dd>
1439 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1440 comment and the real name. That means that if you have a table called
1441 'user0001' and add the comment 'MyName' on it, you will see the name
1442 'MyName' used consequently in the left frame and the tool-tip shows
1443 the real name of the DB.</dd>
1446 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1448 When setting this to 'nested', the Alias of the Tablename is only used
1449 to split/nest the tables according to the
1451 directive. So only the folder is called like the Alias, the tablename itself
1452 stays the real tablename.</dd>
1455 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1458 <dd>Enter URL where logo in the navigation frame will point to.
1459 For use especially with self made theme which changes this.
1468 <dd>Defines whether or not to display a server choice at the top of the left frame.
1469 Defaults to FALSE.</dd>
1471 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1472 Defaults to FALSE (drop-down).</dd>
1474 <dd>Defines whether to display database choice in light navigation frame as links
1475 instead of in a drop-down. Defaults to 'auto' - on main page list is
1476 shown, when database is selected, only drop down is displayed.</dd>
1479 <dd>Defines the tab displayed by default when clicking the small
1480 icon next to each table name in the navigation panel. Possible
1486 <dd>Defines whether or not to display space usage and statistics about databases
1487 and tables.<br />
1488 Note that statistics requires at least MySQL 3.23.3 and that, at this
1489 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1492 <dd>Defines whether to display detailed server information on main page.
1493 You can additionally hide more information by using
1495 </dd>
1500 </dt>
1503 not at the starting main (right) frame. This setting
1504 does not check MySQL commands entered directly.<br /><br />
1506 Please note that to block the usage of phpinfo() in scripts, you
1513 hard coded password value in the configuration file, end users can't
1514 be allowed to change their passwords.</dd>
1517 <dd>Defines whether to suggest a database name on the
1521 <dd>Defines whether navigation bar buttons and the right panel top menu
1522 contain text or symbols only. A value of TRUE displays icons, FALSE
1523 displays text and 'both' displays both icons and text.</dd>
1526 <dd>Defines whether a user should be displayed a
1530 <dd>Number of rows displayed when browsing a result set. If the result set
1537 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1541 option is ticked by default.</dd>
1545 from editing when browsing a table's content. Valid values are:
1550 </ul>
1551 </dd>
1554 <dd>Defines whether or not MySQL functions fields should be initially
1555 displayed in edit/insert mode. Since version 2.10, the user can
1556 toggle this setting from the interface.
1557 </dd>
1560 <dd>Defines whether or not type fields should be initially
1561 displayed in edit/insert mode. The user can
1562 toggle this setting from the interface.
1563 </dd>
1566 <dd>Defines which type of editing controls should be used for CHAR and
1567 VARCHAR fields. Possible values are:
1568 <ul><li>input - this allows to limit size of text to size of field in
1569 MySQL, but has problems with newlines in fields</li>
1570 <li>textarea - no problems with newlines in fields, but also no
1571 length limitations</li>
1572 </ul>
1573 Default is old behavior so input.</dd>
1579 <dd>If there are fewer items than this in the set of foreign keys, then a
1580 drop-down box of foreign keys is presented, in the style described by the
1582 setting.</dd>
1585 <dd>For the foreign key drop-down fields, there are several methods of
1586 display, offering both the key and value data. The contents of the
1587 array should be one or both of the following strings:
1593 </dt>
1594 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1595 creating a dump file</dd>
1598 </dt>
1599 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1600 compressed exports. This doesn't affect smaller dumps and allows users to
1601 create larger dumps that won't otherwise fit in memory due to php
1602 memory limit. Produced files contain more GZip/BZip2 headers, but all
1603 normal programs handle this correctly.</dd>
1607 mainframe.</dd>
1611 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1616 <dd>How many columns will be utilized to display the tables on the
1617 database property view? Default is 1 column. When setting this to a
1618 value larger than 1, the type of the database will be omitted for more
1619 display space.</dd>
1623 <dd>Defines the tab displayed by default on server view. Possible
1630 <dd>Defines the tab displayed by default on database view. Possible
1635 <dd>Defines the tab displayed by default on table view. Possible
1642 points to the MySQL documentation (type depends
1643 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1644 generated.<br />
1646 for more information about MySQL manuals and their types.</dd>
1649 <dd>Type of MySQL documentation:
1655 </ul>
1656 </dd>
1659 <dd>Defines the default language to use, if not browser-defined or
1660 user-defined.<br />
1661 The corresponding language file needs to be in
1663 </dd>
1666 <dd>Defines the default connection collation to use, if not
1667 user-defined.<br />
1673 The corresponding language file needs to be in
1675 </dd>
1678 <dd>Limit list of available languages to those matching the given regular
1679 expression. For example if you want only Czech and English, you should
1683 <dd>Default character set to use for recoding of MySQL queries. This must be
1684 enabled and it's described by
1686 option.<br />
1687 You can give here any character set which is in
1689 array and this is just default choice, user can select any of them.</dd>
1692 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1693 support (compiled in or module) in PHP to allow MySQL queries recoding
1694 and used language file must have it enabled (by default only these
1695 which are in Unicode, just to avoid losing some characters).<br /><br />
1698 in the Export and Import pages, to choose the character set when
1699 exporting a file. The default value in this menu comes from
1701 </dd>
1704 <dd>You can select here which functions will be used for character set
1705 conversion. Possible values are:
1706 <ul><li>auto - automatically use available one (first is tested
1707 iconv, then recode)</li>
1710 </ul>
1711 Default is auto.</dd>
1714 <dd>Specify some parameters for iconv used in charset conversion. See
1717 used, so that invalid characters will be transliterated.</dd>
1720 <dd>Available character sets for MySQL conversion. You can add your own (any of
1721 supported by recode/iconv) or remove these which you don't use.
1722 Character sets will be shown in same order as here listed, so if you
1723 frequently use some of these move them to the top.</dd>
1728 default empty, you need to fill in some trusted proxy servers if you
1729 want to use rules for IP addresses behind proxy.<br /><br />
1731 The following example specifies that phpMyAdmin should trust a
1733 <pre>
1734 $cfg['TrustedProxies'] =
1736 </pre>
1737 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1738 client's IP address as usual.
1739 </dd>
1743 MIME transformations.<br />
1744 Possible values are:
1745 <ul><li>auto - automatically detect, this is a bit expensive
1747 according to your server real possibilities</li>
1750 </ul>
1751 Default is auto.
1752 </dd>
1755 <dd>
1756 We normally check the permissions on the configuration file to ensure
1757 it's not world writable. However, phpMyAdmin could be installed on
1758 a NTFS filesystem mounted on a non-Windows server, in which case the
1759 permissions seems wrong but in fact cannot be detected. In this case
1761 </dd>
1764 <dd>
1765 Limit for length of URL in links. When length would be above this limit, it
1766 is replaced by form with button.
1767 This is required as some web servers (IIS) have problems with long URLs.
1769 </dd>
1773 </dd>
1775 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1776 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1777 </dt>
1778 <dd>The background styles used for both the frames.
1781 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1783 <dd>The style used for the pointer in the navi frame.
1787 </dt>
1788 <dd>The color used for the database name in the navi frame.
1797 </dd>
1801 <dd>The style used for table headers. See
1806 </dd>
1810 </dd>
1812 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1814 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1816 </dt>
1818 The former feature highlights the row over which your mouse is passing
1819 and the latter lets you visually mark/unmark rows by clicking on
1820 them.<br />
1825 <dd>You put here a valid CSS font family value, for example
1830 <dd>You put here a valid CSS font family value, for example
1844 </dt>
1846 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1848 The Char* values are used for CHAR and VARCHAR editing (if configured
1852 </dt>
1856 </dt>
1857 <dd>Defines if the whole textarea of the query box will be selected on
1858 click.</dd>
1861 </dt>
1862 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1863 editing.</dd>
1866 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1867 Can be turned off by a toggle button on the browse page.</dd>
1871 </dt>
1872 <dd>Defines the place where modify and delete links would be put when
1873 tables contents are displayed (you may have them displayed both at the
1874 left and at the right).
1880 Define which one is displayed by default. The first mode displays each
1881 row on a horizontal line, the second rotates the headers by 90
1882 degrees, so you can use descriptive headers even though fields only
1883 contain small values and still print them out. The vertical mode sorts
1884 each row on a vertical lineup.
1885 </dd>
1888 <dd>
1889 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1890 'css' the rotation of the header for horizontalflipped is done via
1891 CSS. The CSS transformation currently works only in Internet
1892 Explorer.If set to 'fake' PHP does the transformation for you, but of
1893 course this does not look as good as CSS. The 'auto' option enables
1894 CSS transformation when browser supports it and use PHP based one
1895 otherwise.
1896 </dd>
1900 string or integer</dt>
1901 <dd>When editing/creating new columns in a table all fields normally get
1902 lined up one field a line. (default: 'horizontal'). If you set this to
1903 'vertical' you can have each field lined up vertically beneath each
1904 other. You can save up a lot of place on the horizontal direction and
1905 no longer have to scroll. If you set this to integer, editing of fewer
1906 columns will appear in 'vertical' mode, while editing of more fields
1907 still in 'horizontal' mode. This way you can still effectively edit
1908 large number of fields, while having full view on few of them.</dd>
1912 </dt>
1914 display of column comments in Browse or Property display. In browse
1915 mode, the comments are shown inside the header. In property mode,
1916 comments are displayed using a CSS-formatted dashed-line below the
1917 name of the field. The comment is shown as a tool-tip for that field.
1918 </dd>
1930 <dd>Whether to display a link to validate a query in any SQL Query box.
1937 <dd>
1938 The name of the directory where
1940 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1941 are available under a drop-down box when you click the database or
1942 table name, then the Import tab.
1943 <br /><br />
1945 If you want different directory for each user, %u will be replaced
1946 with username.<br /><br />
1950 compressed formats is enabled).<br /><br />
1952 This feature is useful when your file is too big to be uploaded via
1954 uploads are disabled in PHP.<br /><br />
1956 Please note that if PHP is running in safe mode, this directory must
1957 be owned by the same user as the owner of the phpMyAdmin scripts.
1958 <br /><br />
1962 alternatives.
1963 </dd>
1966 <dd>
1967 The name of the directory where dumps can be saved.<br /><br />
1969 If you want different directory for each user, %u will be replaced
1970 with username.<br /><br />
1972 Please note that the directory must exist and has to be writable for
1973 the user running webserver.<br /><br />
1975 Please note that if PHP is running in safe mode, this directory must
1976 be owned by the same user as the owner of the phpMyAdmin scripts.
1977 </dd>
1980 <dd>
1981 The name of the directory where temporary files can be stored.
1982 <br /><br />
1984 This is needed for native MS Excel export, see
1990 <br /><br />
1992 If the directory where phpMyAdmin is installed is subject to an
1994 temporary directory in some directory accessible by the web
1995 server. However for security reasons, this directory should be outside
1996 the tree published by webserver. If you cannot avoid having this
1997 directory published by webserver, place at least an empty
1999 possible.
2000 <br /><br />
2002 This directory should have as strict permissions as possible as the only
2003 user required to access this directory is the one who runs the
2004 webserver. If you have root privileges, simply make this user owner of
2005 this directory and make it accessible only by it:
2006 <br /><br />
2008 <pre>
2009 chown www-data:www-data tmp
2010 chmod 700 tmp
2011 </pre>
2013 If you cannot change owner of the directory, you can achieve a similar
2016 <pre>
2017 chmod 700 tmp
2018 setfacl -m "g:www-data:rwx" tmp
2019 setfacl -d -m "g:www-data:rwx" tmp
2020 </pre>
2022 If neither of above works for you, you can still make the directory
2024 system reading and writing data in this directory.
2025 </dd>
2028 <dd>
2029 In this array are defined default parameters for export, names of
2030 items are similar to texts seen on export page, so you can easily
2031 identify what they mean.
2032 </dd>
2035 <dd>
2036 In this array are defined default parameters for import, names of
2037 items are similar to texts seen on import page, so you can easily
2038 identify what they mean.
2039 </dd>
2042 <dd>
2043 Repeat the headers every X cells, or 0 to deactivate.
2044 </dd>
2052 </dt>
2053 <dd>
2054 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2055 or icon is always displayed on the left panel. If JavaScript is enabled in
2056 your browser, a click on this opens a distinct query window, which is
2057 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2058 changes to display a query box.<br /><br />
2060 The size of this query window can be customized with
2062 - both integers for the size in pixels. Note that normally, those
2064 theme you are using.<br /><br />
2068 opens the query window and puts the current query
2069 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2070 query in the right panel's query box.
2071 <br /><br />
2072 The usage of the JavaScript query window is recommended if you have a
2073 JavaScript enabled browser. Basic functions are used to exchange quite
2074 a few variables, so most 4th generation browsers should be capable to
2075 use that feature. It currently is only tested with Internet Explorer 6
2076 and Mozilla 1.x.
2077 <br /><br />
2079 to a table, which has to be created by you (see <a
2081 all your queries will be appended to the form, but only as long as
2082 your window is opened they remain saved.
2083 <br /><br />
2084 When using the JavaScript based query window, it will always get
2085 updated when you click on a new table/db to browse and will focus if
2086 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2087 the query window by checking the box "Do not overwrite this query from
2088 outside the window" below the query textarea. Then you can browse
2089 tables/databases in the background without losing the contents of the
2090 textarea, so this is especially useful when composing a query with
2091 tables you first have to look in. The checkbox will get automatically
2092 checked whenever you change the contents of the textarea. Please
2093 uncheck the button whenever you definitely want the query window to
2094 get updated even though you have made alterations.
2095 <br /><br />
2098 <br /><br />
2099 The query window also has a custom tabbed look to group the features.
2101 default tab to be used when opening the query window. It can be set to
2102 either 'sql', 'files', 'history' or 'full'.</dd>
2108 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2110 If the approximate row count as returned by
2113 count will be used.
2114 </dd>
2116 <dd>For VIEWs, since obtaining the exact count could have an
2117 impact on performance, this value is the maximum to be displayed, using
2119 any row counting.
2120 </dd>
2124 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2126 page. By clicking on the button 'toggle scratchboard' on the page
2127 where you edit x/y coordinates of those elements you can activate a
2128 scratchboard where all your elements are placed. By clicking on an
2129 element, you can move them around in the pre-defined area and the x/y
2130 coordinates will get updated dynamically. Likewise, when entering a
2131 new position directly into the input field, the new position in the
2132 scratchboard changes after your cursor leaves the input field.<br />
2133 You have to click on the 'OK'-button below the tables to save the new
2134 positions. If you want to place a new element, first add it to the
2135 table of elements and then you can drag the new element around.<br />
2136 By changing the paper size and the orientation you can change the size
2137 of the scratchboard as well. You can do so by just changing the
2138 dropdown field below, and the scratchboard will resize automatically,
2139 without interfering with the current placement of the elements.<br />
2140 If ever an element gets out of range you can either enlarge the paper
2141 size or click on the 'reset' button to place all elements below each
2142 other.<br />
2144 get this control to work. The basic Drag&Drop script functionality
2145 was kindly borrowed from www.youngpup.net and is underlying so
2146 specific license.</dd>
2149 <dd>Sorts database and table names according to natural order (for example,
2150 t1, t2, t10). Currently implemented in the left panel (Light mode)
2151 and in Database view, for the table list.</dd>
2162 <dd>Allows you to specify window's title bar. Following magic string can
2163 be used to get special values:
2164 <dl>
2170 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2179 </dl>
2180 </dd>
2190 </dd>
2193 <dd>If theme manager is active, use this as the path of the subdirectory
2194 containing all the themes.</dd>
2208 </dt>
2209 <dd>Default queries that will be displayed in query boxes when user didn't
2210 specify any. Use %d for database name, %t for table name and %f for a
2211 comma separated list of field names. Note that %t and %f are only
2215 <dd>
2216 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
2217 default we use HTML to format the query, but you can disable this by
2219 </dd>
2222 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2223 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2224 query inside a bracket is indented. By changing
2227 specifies the units of the indent amount that you specified. This is
2228 used via stylesheets.</dd>
2231 <dd>This array is used to define the colours for each type of element of
2232 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2234 If you specify an empty string for the color of a class, it is ignored
2235 in creating the stylesheet.
2236 You should not alter the class names, only the colour strings.<br />
2257 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2261 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2262 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2263 </ul>
2264 </dd>
2268 <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,
2269 as originally published on
2271 <br />
2272 For help in setting up your system to use the service, see the
2274 </dd>
2278 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2279 and any password, so we use those by default. Instead, if
2280 you have an account with them, you can put your login details
2281 here, and it will be used in place of the anonymous login.</dd>
2282 </dl>
2283 </dd>
2286 <dd><b>DEVELOPERS ONLY!</b></dd>
2289 <dd><b>DEVELOPERS ONLY!</b><br />
2290 Enable logging queries and execution times to be displayed in the bottom
2291 of main page (right frame).</dd>
2294 <dd><b>DEVELOPERS ONLY!</b><br />
2295 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2296 the code.<br />
2297 For help in setting up your system to this, see the
2301 <dd><b>DEVELOPERS ONLY!</b><br />
2302 Enable profiling support for phpMyAdmin. This will append a chunk of data
2303 to the end of every page displayed in the main window with profiling
2304 statistics for that page.<br />
2305 You may need to increase the maximum execution time for this to
2306 complete successfully.<i>Profiling was removed from the code for
2307 version 2.9.0 due to licensing issues.</i></dd>
2309 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2310 <dd><b>DEVELOPERS ONLY!</b><br />
2311 When profiling data is displayed, this variable controls the threshold of
2312 display for any profiling data, based on the average time each time has
2313 taken. If it is over the threshold it is displayed, otherwise it is not
2314 displayed. This takes a value in milliseconds. In most cases you don't need
2315 to edit this.</dd>
2318 <dd>All possible types of a MySQL column. In most cases you don't need to
2319 edit this.</dd>
2322 <dd>Possible attributes for fields. In most cases you don't need to edit
2323 this.</dd>
2326 <dd>A list of functions MySQL supports. In most cases you don't need to
2327 edit this.</dd>
2330 <dd>Mapping of column types to meta types used for preferring displayed
2331 functions. In most cases you don't need to edit this.</dd>
2334 <dd>Functions preferred for column meta types as defined in
2335 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2336 to edit this.</dd>
2339 <dd>Functions selected by default when inserting/changing row, Functions
2340 are defined for meta types from
2342 <code>first_timestamp</code>, which is used for first timestamp column
2343 in table.</dd>
2346 <dd>Operators available for search operations on numeric and date fields.
2347 </dd>
2350 <dd>Operators available for search operations on character fields.
2351 Note that we put <code>LIKE</code> by default instead of
2352 <code>LIKE %...%</code>, to avoid unintended performance problems
2353 in case of huge tables.</dd>
2356 <dd>Operators available for search operations on enum fields.</dd>
2359 <dd>Additional operators available for search operations when the
2360 field can be null.</dd>
2362 </dl>
2364 <!-- TRANSFORMATIONS -->
2370 </ol>
2374 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2376 section</a> on how to do so.</p>
2378 <p> You can apply different transformations to the contents of each field. The
2379 transformation will take the content of each field and transform it with
2380 certain rules defined in the selected transformation.</p>
2382 <p> Say you have a field 'filename' which contains a filename. Normally you would
2383 see in phpMyAdmin only this filename. Using transformations you can transform
2384 that filename into a HTML link, so you can click inside of the phpMyAdmin
2385 structure on the field's link and will see the file displayed in a new browser
2386 window. Using transformation options you can also specify strings to
2387 append/prepend to a string or the format you want the output stored in.</p>
2389 <p> For a general overview of all available transformations and their options,
2390 you can consult your
2391 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2392 installation.</p>
2394 <p> For a tutorial on how to effectively use transformations, see our
2396 the official phpMyAdmin homepage.</p>
2400 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2401 clicking on the 'Structure' link for a table). There click on
2402 "Change" (or change icon) and there you will see three new fields at
2403 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2404 'Transformation options'.</p>
2406 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2407 that corresponds to the column's contents. Please note that
2408 transformations are inactive as long as no MIME-type is selected.</li>
2410 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2411 hopefully growing amount of pre-defined transformations. See below for information on
2412 how to build your own transformation.<br />
2414 There are global transformations and mimetype-bound transformations. Global transformations
2415 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2416 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2417 transformations which operate on the main mimetype (like 'image'), which will most likely
2418 take the subtype into regard, and those who only operate on a
2419 specific subtype (like 'image/jpeg').<br />
2421 You can use transformations on mimetypes for which the function was not defined for. There
2422 is no security check for you selected the right transformation, so take care of what the
2423 output will be like.</li>
2425 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2426 transform-function specific options here. Usually the transforms can operate with default
2427 options, but it is generally a good idea to look up the overview to see which options are
2428 necessary.<br />
2430 Much like the ENUM/SET-Fields, you have to split up several options using the format
2431 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2432 parsed as an array, leaving the first value the first element in the array, and so
2433 forth.<br />
2435 If you want to specify a MIME character set you can define it in the transformation_options.
2436 You have to put that outside of the pre-defined options of the specific mime-transform,
2438 for which you can specify 2 options and you want to append a character set, enter "'first
2439 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2441 </ul>
2445 <p> All mimetypes and their transformations are defined through single files in
2446 the directory 'libraries/transformations/'.</p>
2448 <p> They are stored in files to ease up customization and easy adding of new
2449 transformations.</p>
2451 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2452 always work. It makes no sense to apply a transformation to a mimetype, the
2453 transform-function doesn't know to handle.</p>
2455 <p> One can, however, use empty mime-types and global transformations which should work
2456 for many mimetypes. You can also use transforms on a different mimetype they where built
2457 for, but pay attention to option usage as well as what the transformation does to your
2458 field.</p>
2460 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2461 any other transform function and provides some basic functions.</p>
2463 <p> There are 5 possible file names:</p>
2465 <ol><li>A mimetype+subtype transform:<br /><br />
2467 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2469 Please not that mimetype and subtype are separated via '_', which shall
2470 not be contained in their names. The transform function/filename may
2471 contain only characters which cause no problems in the file system as
2472 well as the PHP function naming convention.<br /><br />
2474 The transform function will the be called
2475 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2477 <b>Example:</b><br /><br />
2479 <tt>text_html__formatted.inc.php</tt><br />
2480 <tt>PMA_transform_text_html__formatted()</tt></li>
2482 <li>A mimetype (w/o subtype) transform:<br /><br />
2484 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2486 Please note that there are no single '_' characters.
2487 The transform function/filename may contain only characters which cause
2488 no problems in the file system as well as the PHP function naming
2489 convention.<br /><br />
2491 The transform function will the be called
2492 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2494 <b>Example:</b><br /><br />
2496 <tt>text__formatted.inc.php</tt><br />
2497 <tt>PMA_transform_text__formatted()</tt></li>
2499 <li>A mimetype+subtype without specific transform function<br /><br />
2501 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2503 Please note that there are no '__' characters in the filename. Do not
2504 use special characters in the filename causing problems with the file
2505 system.<br /><br />
2507 No transformation function is defined in the file itself.<br /><br />
2509 <b>Example:</b><br /><br />
2511 <tt>text_plain.inc.php</tt><br />
2512 (No function)</li>
2514 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2516 <tt>[mimetype].inc.php</tt><br /><br />
2518 Please note that there are no '_' characters in the filename. Do not use
2519 special characters in the filename causing problems with the file system.
2520 <br /><br />
2522 No transformation function is defined in the file itself.<br /><br />
2524 <b>Example:</b><br /><br />
2526 <tt>text.inc.php</tt><br />
2527 (No function)</li>
2529 <li>A global transform function with no specific mimetype<br /><br />
2531 <tt>global__[transform].inc.php</tt><br /><br />
2533 The transform function will the be called
2534 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2536 <b>Example:</b><br /><br />
2538 <tt>global__formatted</tt><br />
2539 <tt>PMA_transform_global__formatted()</tt></li>
2540 </ol>
2542 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2543 transform function.</p>
2545 <p> All filenames containing no '__' in themselves are not shown as valid transform
2546 functions in the dropdown.</p>
2548 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2549 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2550 without a transform function. Also note the introduction of a function description in
2551 the language files. For each function a $strTransformation_[filename without .inc.php]
2552 has to exist.</p>
2554 <p> You can use the template generator to generate new functions and entries in the
2555 language file.</p>
2557 <p> To create a new transform function please see
2558 <tt>libraries/transformations/template_generator.sh</tt>.
2559 To create a new, empty mimetype please see
2560 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2562 <p> A transform function always gets passed three variables:</p>
2564 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2565 you want to transform.</li>
2566 <li><b>$options</b> - Contains any user-passed options to a transform function
2567 as an array.</li>
2568 <li><b>$meta</b> - Contains an object with field information to your column.
2569 The data is drawn from the output of the
2571 function. This means, all object properties described on the
2573 available in this variable and can be used to transform a field accordingly
2574 to unsigned/zerofill/not_null/... properties.<br />
2575 The $meta->mimetype variable contains the original MIME-type of the
2576 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2577 </ol>
2579 <!-- FAQ -->
2586 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2591 </ol>
2593 <p> Please have a look at our
2595 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2596 features and or interface.</p>
2602 action is required or phpMyAdmin sends a blank page or a page full of
2603 cryptic characters to my browser, what can I do?</a></h4>
2605 <p> There are some known PHP bugs with output buffering and compression.<br />
2607 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2608 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2609 configuration file.<br />
2610 Furthermore, we know about such problems connected to the release
2611 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2612 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2617 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2618 See also the
2620 entry about PHP bugs with output buffering.<br />
2621 If your server keeps crashing, please ask for help in the various Apache
2622 support groups.</p>
2626 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2627 script: I'm always displayed the login screen.</a></h4>
2629 <p> This is a known PHP bug (see this
2631 official PHP bug database. It means there is and won't be any phpMyAdmin
2632 fix against it because there is no way to code a fix.</p>
2638 application misbehaved by not returning a complete set of
2640 </h4>
2642 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2643 Have a look at the last message in this
2645 official PHP bug database.</p>
2650 and/or many error messages with the
2652 mode.</a></h4>
2654 <p> This is a known problem with the PHP
2656 filter: it's not so stable. Please use instead the cookie authentication mode.
2657 </p>
2662 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2663 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2664 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2665 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2666 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2671 work.</a></h4>
2673 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2674 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2675 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2676 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2677 We faced PHP crashes when trying to download a dump with MS Internet
2678 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2679 this case you should switch to the release version of PHP 4.2.0.</p>
2683 an error about safe mode being in effect.</a></h4>
2685 <p> Your uploaded file is saved by PHP in the "upload dir", as
2686 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2687 the system default is <i>/tmp</i>).<br />
2688 We recommend the following setup for Apache servers running in safe mode,
2689 to enable uploads of files while being reasonably secure:</p>
2691 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2692 <li>give ownership to the Apache server's user.group:
2693 <tt>chown apache.apache /tmp/php</tt></li>
2694 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2695 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2696 <li>restart Apache</li>
2697 </ul>
2701 general file uploads don't work on my system and uploaded files have a
2702 <tt>Content-Type:</tt> header in the first line.</a></h4>
2704 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2705 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2706 So the problem is that this package has a serious bug that was corrected
2707 ages ago in PHP (2001-01-28: see
2709 for more details). The problem is that the bugged package is still
2710 available though it was corrected (see
2712 for more details).<br />
2713 So please download
2714 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2715 and the problem should go away.<br />
2716 And that fixes the \r\n problem with file uploads!</p>
2720 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2721 I'm using the Apache server.</a></h4>
2723 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2724 your <i>httpd.conf</i>:</p>
2728 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2732 uploading a file from the query box.</a></h4>
2734 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2735 restrictions. However you need to create temporary directory and
2737 The uploaded files will be moved there, and after execution of your
2743 <p> The MySQL manual explains how to
2745 reset the permissions</a>.</p>
2750 execute a bookmark.</a></h4>
2752 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2753 cannot access the uploaded query.</p>
2758 submit a query from the convenient text area.</a></h4>
2760 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2761 and try to increase it.</p>
2765 </h4>
2767 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2768 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2769 names to align with current standards.</p>
2774 </h4>
2776 <p> Starting with version 2.7.0, the import engine has been re–written and these
2777 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2778 to take advantage of the new import features.</p>
2780 <p> The first things to check (or ask your host provider to check) are the
2781 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2782 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2783 All of these three settings limit the maximum size of data that can be
2784 submitted and handled by PHP. One user also said that post_max_size
2785 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2787 There exist several workarounds if your upload is too big or your
2788 hosting provider is unwilling to change the settings:</p>
2791 feature. This allows one to
2792 upload a file to the server via scp, ftp, or your favorite file transfer
2793 method. PhpMyAdmin is then able to import the files from the temporary
2795 section</a> of this document.</li>
2797 BigDump</a>) to split the files before uploading. We cannot support this
2798 or any third party applications, but are aware of users having success
2799 with it.</li>
2800 <li>If you have shell (command line) access, use MySQL to import the files
2801 directly. You can do this by issuing the "source" command from
2802 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2803 </ul>
2807 support?</a></h4>
2809 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2810 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2811 connect to your MySQL server using PHP's classic
2814 is available in php 5.0. The latter one should be used unless you have
2815 good reason not to do so.<br />
2816 When compiling php, we strongly recommend that you manually link the MySQL
2817 extension of your choice to a MySQL client library of at least the same
2818 minor version since the one that is bundled with some PHP distributions is
2821 If your webserver is running on a windows system, you might want to try
2822 MySQL's
2824 instead of the MySQL / MySQLi extensions that are bundled with the official
2825 php Win32 builds.</p>
2829 message, "Client does not support authentication protocol requested
2830 by server; consider upgrading MySQL client"</a></h5>
2832 <p> You tried to access MySQL with an old MySQL client library. The version of
2833 your MySQL client library can be checked in your phpinfo() output.
2834 In general, it should have at least the same minor version as your server
2838 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2839 changed the authentication hash and your PHP is trying to use the old method.
2841 with the proper client library to match your MySQL installation. Your
2842 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2843 More information (and several workarounds) are located in the
2845 </p>
2849 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2850 capital letter in its name it is changed to lowercase as it should. But
2851 if I try to DROP this table MySQL is unable to find the corresponding
2852 file.</a></h4>
2854 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2855 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2856 directive.</p>
2860 script seems not to know the font face I'm using!</a></h4>
2862 <p> The "FPDF" library we're using for this feature requires some
2863 special files to use font faces.<br />
2865 these files.</p>
2869 check PHP Configuration".</a></h4>
2871 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2872 "MySQL extension". This extension may be part of the PHP
2873 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2874 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2875 to load the extension but failed.<br /><br />
2877 Usually, the problem is solved by installing a software package called
2878 "PHP-MySQL" or something similar.</p>
2883 and I cannot log in using cookie auth.</a></h4>
2885 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2889 so I cannot upload.</a></h4>
2891 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2892 parameter is not set to "on".</p>
2896 a new table the table and field names are changed to lowercase!</a></h4>
2898 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2899 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2900 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2901 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2902 directory and add the following line to the group [mysqld]:</p>
2904 <pre>set-variable = lower_case_table_names=0</pre>
2906 <p> Next, save the file and restart the MySQL service. You can always check the
2907 value of this directive using the query</p>
2909 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2913 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2916 </p>
2920 and I get problems, such as undefined variables when I run a
2923 <p> A tip from Jose Fandos: put a comment on the following two lines
2924 in httpd.conf, like this:</p>
2926 <pre>
2927 # mod_gzip_item_include file \.php$
2929 </pre>
2931 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2932 PHP scripts. Of course you have to restart Apache.</p>
2937 I get the error "No input file specified" when trying to
2938 run phpMyAdmin.</a></h4>
2940 <p> This is a permission problem. Right-click on the phpmyadmin folder
2941 and choose properties. Under the tab Security, click on "Add"
2942 and select the user "IUSR_machine" from the list. Now set his
2943 permissions and it should work.</p>
2947 db_structure.php with plenty of tables).</a></h4>
2950 GZIP output buffering is enabled. If you turn off it (by
2952 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2953 PHP 5.0.0.</p>
2957 message 'Errorcode: 13'. What does this mean?</a></h4>
2959 <p> This can happen due to a MySQL bug when having database / table names with
2960 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2961 To fix this, turn off this directive, convert all database and table names
2962 to lower case and turn it on again. Alternatively, there's a bug-fix
2963 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2967 and the fields are duplicated.</a></h4>
2969 <p> It is possible to configure Apache in such a way that PHP has problems
2970 interpreting .php files.</p>
2972 <p> The problems occur when two different (and conflicting) set of directives
2973 are used:</p>
2975 <pre>
2976 SetOutputFilter PHP
2977 SetInputFilter PHP
2978 </pre>
2980 <p> and</p>
2982 <pre>AddType application/x-httpd-php .php</pre>
2984 <p> In the case we saw, one set of directives was in
2985 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2986 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2987 The recommended way is with <tt>AddType</tt>, so just comment out
2988 the first set of lines and restart Apache:</p>
2990 <pre>
2991 #SetOutputFilter PHP
2992 #SetInputFilter PHP
2993 </pre>
2998 <p> This problem is known to happen when the server is running Turck MMCache
2999 but upgrading MMCache to version 2.3.21 solves the problem.</p>
3004 <p>Yes.</p>
3005 <p>
3006 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
3007 is still maintained.
3008 </p>
3011 <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>
3013 <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>
3016 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3017 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3018 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3019 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3020 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3021 enabled.) Click <tt>OK</tt>.</li>
3022 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3023 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3024 </ol>
3028 PHP 5.0.4 on 64-bit systems?</a></h4>
3030 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3031 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3037 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
3038 the order of the server paragraph in <tt>config.inc.php</tt>.
3039 Table and script parts are optional. If you want
3040 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3041 some configuration. Following lines apply only for <a
3043 that you have enabled some features within global configuration. You need
3044 <code>Options FollowSymLinks</code> and <code>AllowOverride
3045 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3046 you need mod_rewrite to be enabled. Then you just need to create following
3047 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3048 (don't forget to change directory name inside of it):</p>
3050 <pre>
3051 RewriteEngine On
3052 RewriteBase /path_to_phpMyAdmin
3053 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3054 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3055 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3056 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3057 </pre>
3060 <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>
3062 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3063 following rewrite rule:</p>
3065 <pre>
3066 RewriteEngine On
3067 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3068 </pre>
3072 </h4>
3073 <p>
3074 There can be many explanations to this and a look at your server's
3075 error log file might give a clue.
3076 </p>
3080 password encryption in cookie auth doesn't work.</a></h4>
3082 <p> If your cluster consist of different architectures, PHP code used for
3083 encryption/decryption won't work correct. This is caused by use of
3084 pack/unpack functions in code. Only solution is to use mcrypt extension
3085 which works fine in this case.</p>
3090 <p> Yes but the default configuration values of Suhosin are known to cause
3091 problems with some operations, for example editing a table with many
3092 columns and no primary key or with textual primary key.
3093 </p>
3094 <p>
3095 Suhosin configuration might lead to malfunction in some cases and it can
3096 not be fully avoided as phpMyAdmin is kind of application which needs to
3097 transfer big amounts of fields in single HTTP request, what is something
3098 what Suhosin tries to prevent. Generally all
3099 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3100 <code>suhosin.get.*</code> directives can have negative effect on
3101 phpMyAdmin usability. You can always find in your error logs which limit
3102 did cause dropping of variable, so you can diagnose the problem and adjust
3103 matching configuration variable.
3104 </p>
3105 <p>
3106 The default values for most Suhosin configuration options will work in most
3107 scenarios, however you might want to adjust at least following parameters:
3108 </p>
3110 <ul>
3111 <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>
3112 <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>
3113 <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>
3114 <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>
3115 <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>
3116 <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>
3117 <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>
3118 <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>
3119 </ul>
3121 <p>
3123 <tt>SuhosinDisableWarning</tt> directive</a>.
3124 </p>
3128 but then my connection is redirected back to http. What can cause this
3129 behavior?</a></h4>
3131 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3132 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>
3135 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
3137 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3138 Example from the Apache 2.2 documentation:</p>
3139 <pre>
3140 ProxyPass /mirror/foo/ http://backend.example.com/
3141 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3142 ProxyPassReverseCookieDomain backend.example.com public.example.com
3143 ProxyPassReverseCookiePath / /mirror/foo/
3144 </pre>
3146 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3147 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3148 This is not specific to phpmyadmin, it's just the behavior of Apache.
3149 </p>
3151 <pre>
3152 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3153 ProxyPassReverse /mirror/foo/
3154 http://backend.example.com/%7Euser/phpmyadmin
3155 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3156 </pre>
3158 <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>
3159 for more details.</p>
3163 privileges, I get an error about an unknown column.</a></h4>
3165 <p> The MySQL server's privilege tables are not up to date, you need to run
3166 the <tt>mysql_upgrade</tt> command on the server.</p>
3173 headers already sent by ..." is displayed, what's the problem?</a></h4>
3175 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3176 (I.E. no blank lines, no spaces, no characters...) neither before the
3177 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3178 tag at the end. We also got a report from a user under IIS, that used
3179 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3180 contained an end-of-line character (hex 0A) at the end; removing this character
3181 cleared his errors.</p>
3186 <p> Either there is an error with your PHP setup or your username/password is
3187 wrong. Try to make a small script which uses mysql_connect and see if it
3188 works. If it doesn't, it may be you haven't even compiled MySQL support
3189 into PHP.</p>
3193 connect to local MySQL server through socket '/tmp/mysql.sock'
3194 (111) ..." is displayed. What can I do?</a></h4>
3196 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3198 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3199 In your <i>php.ini</i> you will find a line</p>
3201 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3203 <p> change it to</p>
3205 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3207 <p> Then restart apache and it will work.</p>
3209 <p> Here is a fix suggested by Brad Ummer:</p>
3211 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3212 To do this, telnet to your server and go to the MySQL bin directory. In
3213 this directory there should be a file named <i>mysqladmin</i>. Type
3214 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3215 info about your MySQL server, including the socket
3216 (<i>/tmp/mysql.sock</i>, for example).</li>
3217 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3218 phpMyAdmin, you need to complete the socket information in the
3219 <i>config.inc.php</i>.<br />
3220 For example:
3222 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3223 <br /><br />
3225 Please also make sure that the permissions of this file allow to be readable
3226 by your webserver (i.e. '0755').</li>
3227 </ul>
3229 <p> Have also a look at the
3231 corresponding section of the MySQL documentation</a>.</p>
3235 what can I do?</a></h4>
3238 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3239 sometime.<br />
3240 Also have a look at your PHP version number: if it contains "4.0b..."
3241 it means you're running a beta version of PHP. That's not a so good idea,
3242 please upgrade to a plain revision.</p>
3246 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3247 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3249 <p> Check the value you set for the
3251 directive in the phpMyAdmin configuration file.</p>
3255 password: YES)"-error when trying to access a MySQL-Server on a
3256 host which is port-forwarded for my localhost.</a></h4>
3258 <p> When you are using a port on your localhost, which you redirect via
3259 port-forwarding to another host, MySQL is not resolving the localhost
3260 as expected.<br />
3261 Erik Wasser explains: The solution is: if your host is "localhost"
3262 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3263 connection for speeding up things. And that doesn't work in this configuration
3264 with port forwarding.<br />
3270 <p> Themes are configured with
3274 <br />
3276 should not delete the directory "original" or its underlying
3277 structure, because this is the system theme used by phpMyAdmin.
3278 "original" contains all images and styles, for backwards
3279 compatibility and for all themes that would not include images or css-files.
3280 <br /><br />
3283 is enabled, you can select your favorite theme on the main page. Your
3284 selected theme will be stored in a cookie.<br /><br /></p>
3286 <p> To create a theme:</p>
3288 <ul><li>make a new subdirectory (for example "your_theme_name") under
3290 (by default <tt>themes</tt>)</li>
3291 <li>copy the files and directories from "original" to
3292 "your_theme_name"</li>
3293 <li>edit the css-files in "your_theme_name/css"</li>
3294 <li>put your new images in "your_theme_name/img"</li>
3295 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3296 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3297 contain your chosen theme name, that will be visible in user interface</li>
3298 <li>make a new screenshot of your theme and save it under
3299 "your_theme_name/screen.png"</li>
3300 </ul>
3302 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3303 theme verbose name, theme generation and theme version. These versions and
3304 generations are enumerated from 1 and do not have any direct dependence on
3305 phpMyAdmin version. Themes within same generation should be backwards
3306 compatible - theme with version 2 should work in phpMyAdmin requiring
3307 version 1. Themes with different generation are incompatible.</p>
3309 <p> If you do not want to use your own symbols and buttons, remove the
3310 directory "img" in "your_theme_name". phpMyAdmin will
3311 use the default icons and buttons (from the system-theme "original").
3312 </p>
3316 what can I do?</a></h4>
3318 <p> Here are a few points to check:</p>
3320 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3322 directive empty. See also
3324 </li>
3325 <li>Maybe you have a broken PHP installation or you need to upgrade
3326 your Zend Optimizer. See
3328 http://bugs.php.net/bug.php?id=31134</a>.
3329 </li>
3330 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3331 set to the default (200) or another low value, you could get this
3332 error if your table has a high number of columns. Adjust this setting
3333 accordingly. (Thanks to Klaus Dorninger for the hint).
3334 </li>
3335 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3336 of ";" will cause this error. Replace it with "&;".
3337 </li>
3339 you might want to increase
3341 </li>
3342 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3343 </li>
3344 </ul>
3349 <p> To be able to see a progress bar during your uploads, your server must
3352 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3353 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3360 who logged out can not log in again in with the same nick.</a></h4>
3362 <p> This is related to the authentication mechanism (protocol) used by
3363 phpMyAdmin. To bypass this problem: just close all the opened
3364 browser windows and then go back to phpMyAdmin. You should be able to
3365 log in again.</p>
3369 limit error or a time limit error.</a></h4>
3371 <p> Compressed dumps are built in memory and because of this are limited to
3372 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3373 using
3375 (enabled by default). Zip exports can not be handled this way, so if you need
3376 Zip files for larger dump, you have to use another way.</p>
3380 when I rename a table or a column.</a></h4>
3382 <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>
3386 bundled with the MySQL server distribution.</a></h4>
3388 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3390 <pre>
3391 -- MySQL dump 8.22
3392 --
3393 -- Host: localhost Database: database
3394 ---------------------------------------------------------
3395 -- Server version 3.23.54
3396 </pre>
3398 <p> The invalid part of the code is the horizontal line made of dashes that
3399 appears once in every dump created with mysqldump. If you want to run your
3400 dump you have to turn it into valid MySQL. This means, you have to add a
3401 whitespace after the first two dashes of the line or add a # before it:
3402 <br />
3403 <code>
3404 -- -------------------------------------------------------<br />
3405 </code>
3406 or<br />
3407 <code>
3408 #---------------------------------------------------------
3409 </code>
3410 </p>
3417 <p> Please note that you should not use the separating string multiple times
3418 without any characters between them, or at the beginning/end of your table
3419 name. If you have to, think about using another TableSeparator or disabling
3420 that feature</p>
3425 <p> In Relation view, being able to choose a table in another database,
3426 or having more than one index field in the foreign key.<br /><br/>
3427 In Query-by-example (Query), automatic generation of the query
3428 LEFT JOIN from the foreign table.<br /><br/>
3429 </p>
3433 I get series of errors like "Warning: unable to parse url". How
3434 can this be fixed?</a></h4>
3435 <p>
3436 Your table neither have a primary key nor an unique one, so we must use a
3437 long expression to identify this row. This causes problems to parse_url
3438 function. The workaround is to create a primary or unique key.
3439 <br />
3440 </p>
3444 a MIME-Transformation onto!</a></h4>
3446 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3447 nested forms can be put inside the table where phpMyAdmin displays the results.
3448 You can, however, use any form inside of a table if keep the parent
3449 form-container with the target to tbl_row_delete.php and just put your own
3450 input-elements inside. If you use a custom submit input field, the form will
3451 submit itself to the displaying page again, where you can validate the
3452 $HTTP_POST_VARS in a transformation.
3454 For a tutorial on how to effectively use transformations, see our
3456 on the official phpMyAdmin-homepage.</p>
3460 MySQL server</a></h4>
3462 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3465 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3466 the quote-character (") is interpreted as an identifier quote character and
3467 not as a string quote character, which makes many internal phpMyAdmin
3469 statements. There is no workaround to this behaviour. News to this item will
3470 be posted in Bug report
3471 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3472 </p>
3476 more that one column with the same value
3477 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3478 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3480 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3481 can use it for the Edit and Delete links.</p>
3486 <p> phpMyAdmin uses a quick method to get the row count, and this method
3487 only returns an approximate count in the case of InnoDB tables. See
3489 a way to modify those results, but
3490 this could have a serious impact on performance.</p>
3495 <p> The number of records in queries containing COUNT and GROUP BY is
3496 not correctly calculated. Also, sorting results of a query like
3501 containing an hyphen.
3502 </a></h4>
3503 <p>
3504 The tests I have made with current MySQL 4.1.11 API shows that the
3505 API does not accept this syntax for the USE command. Enclosing the
3506 db name with backquotes works. For further confusion, no backquotes
3507 are needed with command-line mysql.
3508 </p>
3511 <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>
3512 <p>
3513 This has been a known limitation of phpMyAdmin since the beginning and
3514 it's not likely to be solved in the future.
3515 </p>
3517 <!-- Begin: Excel import limitations -->
3520 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3521 <p>
3522 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target="_blank">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3523 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3524 <br /><br />
3525 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3526 </p>
3529 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3530 <p>
3531 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3532 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3533 </p>
3536 <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>
3537 <p>
3538 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3539 consider using a built-in type. These are almost always guarenteed to import correctly.
3540 </p>
3542 <!-- End: Excel import limitations -->
3543 <!-- Begin: CSV import limitations -->
3546 <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>
3547 <p>
3548 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.
3549 </p>
3551 <!-- End: CSV import limitations -->
3552 <!-- Begin: Import type-detection limitations -->
3555 <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>
3556 <p>
3557 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
3558 you will have to edit the structure to your liking post-import.
3559 <br /><br />
3560 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
3561 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.
3562 </p>
3564 <!-- End: Import type-detection limitations -->
3566 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3569 <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
3570 need to install it for each customer.
3571 </a></h4>
3572 <p>
3573 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3574 your users. The development of this feature was kindly sponsored by
3575 NetCologne GmbH.
3576 This requires a properly setup MySQL user management and phpMyAdmin
3577 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3579 </p>
3583 access.
3584 </a></h4>
3585 <p>
3586 This depends on your system.<br />
3587 If you're running a server which cannot be accessed by other people, it's
3588 sufficient to use the directory protection bundled with your webserver
3590 If other people have telnet access to your server, you should use
3591 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3592 <br /><br />
3593 Suggestions:
3594 </p>
3595 <ul>
3596 <li>
3598 </li>
3599 <li>
3600 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3601 is a user whose password is only known to you, and apache is the
3602 group under which Apache runs.
3603 </li>
3604 <li>
3605 You should use PHP safe mode, to protect from other users that try
3607 </li>
3608 </ul>
3613 </a></h4>
3614 <p>
3619 </p>
3622 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3623 authentication.
3624 </a></h4>
3628 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3629 and/or
3631 are wrong.</li>
3633 <li>You have already setup a security mechanism for the
3634 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3635 phpMyAdmin's authentication, so remove it.</li>
3636 </ul>
3643 and put the privileges you want. For example,
3645 would let a user create/manage his/her database(s).</p>
3650 <p> If you have existing rules from an old .htaccess file, you can take them
3653 be a major benefit here if your installation is suited to using it. Then
3654 you can just add those updated lines into the
3658 <p> If you want a pre-made sample, you can try this fragment. It stops the
3659 'root' user from logging in from any networks other than the private
3662 <pre>
3663 //block root from logging in except from the private networks
3664 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3665 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3666 'deny root from all',
3667 'allow root from localhost',
3671 );
3672 </pre>
3677 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3678 different than the one set in your
3680 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3681 while a domain name is defined in the config file.</p>
3686 <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>
3692 when trying to create a table with more than 14 fields.
3693 </a></h4>
3694 <p>
3695 We could reproduce this problem only under Win98/98SE. Testing under
3696 WinNT4 or Win2K, we could easily create more than 60 fields.
3697 <br />
3698 A workaround is to create a smaller number of fields, then come back to
3699 your table properties and add the other fields.
3700 </p>
3704 <p>
3705 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3706 with each script/website that use forms.<br />
3707 Upgrade or downgrade your Xitami server.
3708 </p>
3711 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3712 <p>
3713 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3714 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3715 don't seem to work.<br />
3717 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3718 the user's temporary directory, so they must be moved before closing
3719 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3722 </p>
3726 Explorer never stores the cookies.
3727 </a></h4>
3728 <p>
3729 MS Internet Explorer seems to be really buggy about cookies, at least till
3731 in this area!
3732 <br />
3733 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3734 work!
3735 </p>
3739 rows.
3740 </a></h4>
3741 <p>
3743 </p>
3746 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3747 when trying to modify a row in a table with many fields, or with a text field
3748 </a></h4>
3749 <p>
3750 Your table neither have a primary key nor an unique one, so we must use a
3751 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
3752 those browsers, and this not happen in Netscape, for example. The
3753 workaround is to create a primary or unique key, or use another browser.
3754 <br />
3755 </p>
3759 page.
3760 </a></h4>
3761 <p>
3762 Some browsers support right-clicking into the frame you want to refresh,
3763 just do this in the right frame.<br />
3764 </p>
3768 query box.
3769 </a></h4>
3770 <p>
3771 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3772 Mozilla versions.<br />
3773 </p>
3777 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3778 </a></h4>
3779 <p>
3780 This is a Mozilla bug (see bug #26882 at
3782 </p>
3787 </a></h4>
3788 <p>
3789 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3790 data in octet-stream mode. Since we can't detect the specific Netscape
3791 version, we cannot workaround this bug.
3792 </p>
3796 wrong.</a></h4>
3798 <p> Please ensure that you have set your browser's character set to the one of the
3799 language file you have selected on phpMyAdmin's start page.
3800 Alternatively, you can try the auto detection mode that is supported by the
3801 recent versions of the most browsers.</p>
3804 <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
3807 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3808 Netscape and Mozilla do not have this problem.</p>
3811 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3812 I cannot manage two servers: I log in to the first one, then the other one,
3813 but if I switch back to the first, I have to log in on each operation.</a></h4>
3819 but nothing happens after that, only a blank screen.</a></h4>
3830 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3835 address and you are starting
3837 containing a domain name, or the reverse situation.</li>
3838 <li>Security settings in IE and/or Microsoft Security Center are
3839 too high, thus blocking scripts execution.</li>
3840 <li>The Windows Firewall is blocking Apache and MySQL. You must
3844 </ul>
3847 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3848 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3849 installed in their Firefox is causing the problem.</p>
3853 clause is generated when I browse a table.</a></h4>
3854 <p> This happens only when both of these conditions are met: using the
3864 </a></h4>
3865 <p>
3866 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3867 specifying a wrong field-type.<br />
3868 Common errors include:
3869 </p>
3870 <ul>
3873 </ul>
3874 <p>
3875 Also, look at the syntax chapter in the MySQL manual to confirm that your
3876 syntax is correct.
3877 </p>
3881 phpMyAdmin generates only one index with those two fields.
3882 </a></h4>
3883 <p>
3884 This is the way to create a multi-fields
3885 index. If you want two indexes, create the first one when creating the
3886 table, save, then display the table properties and click the Index link to
3887 create the other index.
3888 </p>
3892 <p>
3893 Since version 2.2.3, you have a checkbox for each field that can be null.
3895 field's value. Since version 2.5.5, you have to use the checkbox to get
3897 a literal NULL in the field, and not a NULL value (this works in PHP4).
3898 </p>
3903 <p> Click on a database or table name in the left frame, the properties will be
3905 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3906 statements that can be used to recreate your database/table.
3907 <br /><br />
3909 transmit the resulting dump to your station. Depending on your PHP
3910 configuration, you will see options to compress the dump. See also the
3912 configuration variable.<br /><br />
3915 this document.</p>
3920 </a></h4>
3922 <p> Click on a database name in the left frame, the properties will be
3924 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3926 the path to your dump filename, or use the Browse button. Then click Go.
3927 <br /><br />
3929 that you upgrade to take advantage of the new features.
3930 <br /><br />
3932 in this document.
3933 </p>
3938 <p> Here is an example with the tables persons, towns and countries, all
3940 table, create it as explained in the configuration section. Then create the
3941 example tables:</p>
3943 <pre>
3944 CREATE TABLE REL_countries (
3945 country_code char(1) NOT NULL default '',
3946 description varchar(10) NOT NULL default '',
3947 PRIMARY KEY (country_code)
3948 ) TYPE=MyISAM;
3950 INSERT INTO REL_countries VALUES ('C', 'Canada');
3952 CREATE TABLE REL_persons (
3953 id tinyint(4) NOT NULL auto_increment,
3954 person_name varchar(32) NOT NULL default '',
3956 country_code char(1) NOT NULL default '',
3957 PRIMARY KEY (id)
3958 ) TYPE=MyISAM;
3960 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3961 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3963 CREATE TABLE REL_towns (
3965 description varchar(30) NOT NULL default '',
3966 PRIMARY KEY (town_code)
3967 ) TYPE=MyISAM;
3969 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3970 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3971 </pre>
3977 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3981 </ul>
3989 <li>In the fields row, choose persons.person_name and click the
3991 <li>Do the same for towns.description and countries.descriptions in the
3994 the correct joins have been generated</li>
3996 </ul>
4000 <p>
4001 Starting from the previous example, create the pma_table_info as explained
4002 in the configuration section, then browse your persons table,
4003 and move the mouse over a town code or country code.
4004 <br /><br />
4005 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
4006 enables: drop-down list of possible values.
4007 </p>
4010 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
4011 <p>
4014 <br /><br />
4015 Then you need to think about your schema layout. Which tables will go on
4016 which pages?
4017 </p>
4018 <ul>
4024 page and click Go. If you like, you
4026 linked tables onto the new page.</li>
4027 <li>Select the name of the new page (making sure the Edit radio button
4028 is selected) and click Go.</li>
4030 Coordinates are relative; your diagram will
4031 be automatically scaled to fit the page. When initially placing tables
4032 on the page, just pick any coordinates -- say, 50x50. After clicking
4034 position the element correctly.</li>
4036 first be sure to click the Save
4037 button beneath the list of tables and coordinates, to save any changes
4038 you made there. Then scroll all the way down, select the
4040 you want, and click Go.</li>
4041 <li>Internet Explorer for Windows may suggest an incorrect filename when
4046 browsers on Windows, do not have this problem.</li>
4047 </ul>
4051 columns!</a></h4>
4053 <p> No, it's MySQL that is doing
4059 underscores in the database name?</a></h4>
4061 <p> If you do not put a backslash before the underscore, this is a wildcard
4064 john2db ...<br /><br />
4066 If you put a backslash before the underscore, it means that the database
4067 name will have a real underscore.</p>
4071 statistics pages?</a></h4>
4082 if it already exists during the import. It does NOT drop the table after
4083 your export, it only affects the import file.</li>
4085 Otherwise, you may get an error if the table name exists but has a
4086 different structure.</li>
4088 (if any) will be included in backup.</li>
4090 field and table names formed with special characters are protected.</li>
4092 types set in the pmadb in the dump as
4094 </li>
4095 </ul>
4100 command, for better documentation (but resulting file is bigger).</li>
4102 once the INSERT verb and the table name.</li>
4105 </li>
4107 more info is provided in the
4109 but basically with this selected, invalid values are adjusted and
4110 inserted rather than causing the entire statement to fail.</li>
4111 </ul>
4115 in its name.</a></h4>
4118 is the normal way to reference a database and table name. Worse, MySQL
4119 will usually let you create a database with a dot, but then you cannot
4120 work with it, nor delete it.</p>
4133 for usage.<br />
4134 On a more recent pear version, I had problems with the state of Net_DIME
4135 being beta, so this single command
4137 needed modules.<br />
4138 If you use the Validator, you should be aware that any
4140 submit will be stored anonymously (database/table/column names,
4141 strings, numbers replaced with generic values). The Mimer
4144 We utilize it as free SOAP service.</p>
4148 it, but MySQL says "BLOB column '...' used in key specification without
4151 <p> The right way to do this, is to create the field without any indexes,
4153 dialog. On this page, you will be able to choose your BLOB field, and
4154 set a size to the index, which is the condition to create an index on
4155 a BLOB field.</p>
4159 editing fields?</a></h4>
4161 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4162 with many editing fields (table structure changes, row editing, etc.)
4163 (must be enabled in configuration - see.
4165 You can also have a look at the directive
4167 ('vertical') and see if this eases up editing for you.</p>
4171 WTF is this feature then useful for?</a></h4>
4173 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4174 on them. Otherwise you could just put a comment on the field. Because entering
4175 your own mimetype will cause serious syntax checking issues and validation,
4176 this introduces a high-risk false-user-input situation. Instead you have to
4177 initialize mimetypes using functions or empty mimetype definitions.<br />
4178 Plus, you have a whole overview of available mimetypes. Who knows all those
4179 mimetypes by heart so he/she can enter it at will?</p>
4183 can't I see any bookmarks below the query box? What is this variable for?
4184 </a></h4>
4186 <p> Any query you have executed can be stored as a bookmark on the page where the
4187 results are displayed. You will find a button labeled 'Bookmark this query'
4188 just at the end of the page.<br />
4189 As soon as you have stored a bookmark, it is related to the database you run
4190 the query on. You can now access a bookmark dropdown on each page, the query
4191 box appears on for that database.<br /><br />
4193 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4197 aware of that you HAVE to create a valid query, otherwise your query won't be
4198 even able to be stored in the database.<br />
4200 for your query will remain the way it is, but will be stripped of the /**/
4201 chars. So you can use:<br /><br />
4205 which will be expanded to<br /><br />
4209 in your query, where VARIABLE is the string you entered in the input box. If
4210 an empty string is provided, no replacements are made.<br /><br />
4212 A more complex example. Say you have stored this query:<br /><br />
4214 <br /><br />
4217 the full query will be:<br /><br />
4220 <br /><br />
4224 spaces inserted there
4225 will be later also inserted as spaces in your query and may lead to unexpected
4226 results especially when
4228 Your initial query which is going to be stored as a bookmark has to yield at
4229 least one result row so
4230 you can store the bookmark. You may have that to work around using well
4234 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4235 include exported table?</a></h4>
4237 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4238 document should look like following one (assuming you have table
4241 <pre>
4242 \documentclass{article} % or any class you want
4243 \usepackage{longtable} % for displaying table
4244 \begin{document} % start of document
4245 \include{table} % including exported table
4246 \end{document} % end of document
4247 </pre>
4251 access them.
4252 </a></h4>
4255 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4256 enable users to see all the database names.
4259 So if your users do not need those privileges, you can remove them and their
4260 databases list will shorten.</p>
4264 possible values for a field, based on some foreign table?</a></h4>
4266 <p> You have to setup appropriate links between the tables, and also
4270 foreign table, a drop-down list of values will be available.
4271 You will see two lists of values, the first list containing the key
4272 and the display field, the second list containing the display field
4273 and the key. The reason for this is to be able to type the first
4274 letter of either the key or the display field.<br /><br />
4276 For 100 values or more, a distinct window will appear, to browse foreign
4277 key values and choose one. To change the default limit of 100, see
4278 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4282 automatically when entering Browse mode for a table?</a></h4>
4284 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4285 </p>
4289 Excel files, how can I enable that?</a></h4>
4291 <p> You can use
4293 which works out of the box, but phpMyAdmin supports direct export
4294 to Microsoft Excel version 97 and newer. For this to work, you need to set
4299 <pre>
4300 cd phpMyAdmin
4301 mkdir tmp
4302 chmod o+rwx tmp
4303 </pre>
4307 what happens to my column comments stored in pmadb?</a></h4>
4309 <p> Automatic migration of a table's pmadb-style column comments to the native
4310 ones is done whenever you enter Structure page for this table.</p>
4315 <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>
4317 <ol>
4318 <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>
4319 <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>
4320 <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>
4321 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4322 <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>
4323 <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>
4324 </ol>
4331 <p> Our Bug Tracker is located at
4333 under the Bugs section.<br /><br />
4335 But please first discuss your bug with other users:<br />
4341 existing language, where do I start?</a></h4>
4343 <p> Always use latest Git version of po file to translate. You can optionally
4345 server</a> where you can also get latest po files and merge them
4346 with your translations. For creating new translation simply use
4350 to do this) or ask on mailing list to add the translation to the web
4351 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Gettext_for_translators">our wiki</a>.</p>
4352 </p>
4353 <p>
4354 Please note that we try not to use HTML entities like &eacute; in
4355 the translations, since we define the right character set in the file.
4356 With HTML entities, the text on JavaScript messages would not
4357 display correctly.
4358 However there are some entities that need to be there, for quotes
4359 ,non-breakable spaces, ampersands, less than, greater than.
4360 </p>
4361 <p>
4362 You can then put your translations, as a zip file to avoid losing special
4363 characters, on the sourceforge.net translation tracker.
4364 </p>
4365 <p>
4366 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4367 list, because this is where we ask for translations of new messages.
4368 </p>
4372 phpMyAdmin. How should I proceed?</a></h4>
4377 <tt>git clone
4378 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4379 </li>
4381 <li>generate patch with your changes:
4383 </li>
4386 tracker of the phpMyAdmin project</a>.
4387 </li>
4388 </ol>
4390 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4392 <p> Write access to the repository is granted only to experienced developers who
4393 have already contributed something useful to phpMyAdmin.<br />
4399 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4401 <p> Please refer to
4402 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4403 </p>
4408 <p> If you use Apache web server, phpMyAdmin exports information about
4409 authentication to Apache environment and it can be used in Apache logs.
4410 Currently there are two variables available:
4411 </p>
4412 <dl>
4414 <dd>User name of currently active user (he does not have to be logged
4415 in).</dd>
4422 </dl>
4423 <p>
4425 </p>
4426 <pre>
4429 </pre>
4430 <p>
4431 You can then use any log analyzing tools to detect possible break-in
4432 attempts.
4433 </p>
4439 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4440 It allows you to connect to local as well as remote servers.This requires you to enter
4441 server host name, username, password, port and the name of the database. Therefore you can
4442 now synchronize your databases placed on the same server or some remote server.
4443 </p>
4445 <p>
4446 This feature is helpful for developers who need to replicate their
4447 databases’ structure as well as data. Moreover, this feature not only
4448 helps replication but also facilitates the user to keep his/her database
4449 in sync with another database. Other than the full database, certain
4450 tables of the databases can also be synchronized.
4451 </p>
4453 <p>
4454 You need to fill in the host name of the server, the username and
4455 password of an user account already there in MySQL. Port is by default
4456 populated with 3306 (MySQL default port). Then the name of the database
4457 should be mentioned at the end. All the information other than the port
4458 needs to be filled explicitly for the source as well as target servers.
4459 </p>
4461 <p>
4462 After successfully passing through the authentication phase, the source and
4463 target database table names will be displayed. It will be a tabular
4464 representation.
4465 </p>
4467 <p>
4468 On the left, are listed the source database table names. Some of the
4469 names have a ‘+’ plus sign preceding them. This shows that these tables
4470 are only present in source database and they need to be added to the
4471 target database in order to synchronize the target database. The tables
4472 whose names are not preceded by a ‘+’ sign are already present in the
4473 target database.
4474 </p>
4476 <p>
4477 On the right, are listed the target database table names. There are few
4478 table names that have “(not present)” appended after their names. This
4479 means that these tables are to be created in target database in order to
4480 synchronize target database with source database. Some tables’ names
4481 have a ‘-’ minus sign preceding them. This shows that these tables are
4482 only present in target database and they will remain unchanged in the
4483 target database. The column in the middle shows the difference between
4484 the source and target corresponding tables.
4485 </p>
4487 <p>
4488 The difference is depicted by the red and green buttons with S and D
4489 letters, indicating that either Structure or Data are not up to date. By
4490 clicking on them, they will turn grey, what means that they will be synchronised.
4491 </p>
4493 <!-- DEVELOPERS -->
4496 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4497 great features have been written by other people and you too can help to
4498 make phpMyAdmin a useful tool.</p>
4500 <p> If you're planning to contribute source, please read the following
4501 information:</p>
4507 it free from other code.<br />
4508 Commonly used functions should be added to
4511 <li>Obviously, you're free to use whatever coding style you want. But
4512 please try to keep your code as simple as possible: beginners are
4513 using phpMyAdmin as an example application.<br />
4514 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4515 compliant on one hand, they fit the
4518 coding standards</a>
4519 on the other hand. Please pay attention to this.</li>
4520 <li>Please enable showing PHP errors and warnings by the
4522 configuration directive.</li>
4523 <li>Please try to keep up the file-naming conventions. Table-related stuff
4526 <li>Please use gettext wrappers around all messages
4529 script. To use translated messages, call
4531 Gettext.</li>
4535 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4536 better debug and profile their code.<br />
4537 Please see the
4539 options for more information.<br />
4540 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4541 lost during its re-entry into Earth's atmosphere and in memory of the
4542 brave men and women who gave their lives for the people of Earth.</li>
4543 </ul>
4547 <pre>
4558 </pre>
4560 <p>
4561 This program is free software; you can redistribute it and/or modify
4562 it under the terms of the GNU General Public License version 2,
4563 as published by the Free Software Foundation.
4564 </p>
4566 <p>
4567 This program is distributed in the hope that it will be useful,
4568 but WITHOUT ANY WARRANTY; without even the implied warranty of
4569 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4570 GNU General Public License for more details.
4571 </p>
4573 <p>
4574 You should have received a copy of the GNU General Public License
4575 along with this program; if not, write to the Free Software
4577 </p>
4579 <!-- CREDITS -->
4584 <ul>
4587 <ul>
4590 </ul></li>
4593 <ul>
4598 </ul></li>
4601 <ul>
4607 </ul></li>
4610 <ul>
4612 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4613 generate XHTML1.0 and CSS2 compliant codes</li>
4616 </ul></li>
4619 <ul>
4627 </ul></li>
4630 <ul>
4635 </ul></li>
4638 <ul>
4641 </ul></li>
4644 <ul>
4646 </ul></li>
4649 <ul>
4652 </ul></li>
4655 <ul>
4659 </ul></li>
4662 <ul>
4665 </ul></li>
4668 <ul>
4675 </ul></li>
4678 <ul>
4682 </ul></li>
4685 <ul>
4691 </ul></li>
4694 (http://sf.net/projects/phpmysqlformgen/)
4695 <ul>
4697 </ul></li>
4700 <ul>
4702 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4707 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4711 </ul></li>
4714 <ul>
4716 </ul></li>
4719 <ul>
4721 </ul></li>
4724 <ul>
4726 </ul></li>
4729 <ul>
4730 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4731 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4732 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4733 </ul></li>
4736 <ul>
4738 </ul></li>
4741 <ul>
4743 </ul></li>
4746 <ul>
4748 </ul></li>
4751 <ul>
4754 </ul></li>
4757 <ul>
4760 </ul></li>
4763 <ul>
4765 </ul></li>
4768 <ul>
4771 </ul></li>
4773 <li>Ivan A Kirillov
4774 <ul>
4776 </ul></li>
4779 <ul>
4781 </ul></li>
4784 <ul>
4786 </ul></li>
4789 <ul>
4791 </ul></li>
4794 <ul>
4796 </ul></li>
4799 <ul>
4801 </ul></li>
4804 <ul>
4806 </ul></li>
4808 </ul>
4810 <p>
4811 And also to the following people who have contributed minor changes,
4812 enhancements, bugfixes or support for a new language since version 2.1.0:
4813 </p>
4815 <p>
4816 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4817 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4818 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4819 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4821 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4822 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4823 Luís V., Martijn W. van der Lee,
4824 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4826 </p>
4831 <p>
4832 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4833 to create a web-based interface to MySQL using PHP3. Although I have not
4834 used any of his source-code, there are some concepts I've borrowed from
4835 him. phpMyAdmin was created because Peter told me he wasn't going to
4836 further develop his (great) tool.
4837 </p>
4838 <p>
4839 Thanks go to
4840 </p>
4841 <ul>
4843 code for the check when dropping a table or database. He also suggested
4844 that you should be able to specify the primary key on tbl_create.php3. To
4845 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4846 well as a bug-report. Plus many smaller improvements.
4847 </li>
4849 were introduced in 1.3.0 (including quite significant ones like the
4850 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4851 bug-fixes and help.
4852 </li>
4854 language-independent by outsourcing the strings to a separate file. He
4855 also contributed the French translation.
4856 </li>
4858 tbl_select.php3, a feature to display only some fields from a table.
4859 </li>
4861 functions in tbl_change.php3. He also added the
4863 </li>
4865 servers and is a regular contributor for bug-fixes.
4866 </li>
4868 features for 2.0.6.
4869 </li>
4870 </ul>
4871 <p>
4872 The following people have contributed minor changes, enhancements, bugfixes
4873 or support for a new language:
4874 </p>
4875 <p>
4876 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4877 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4878 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4879 G. Wieggers.
4880 </p>
4881 <p>
4882 And thanks to everyone else who sent me email with suggestions, bug-reports
4883 and or just some feedback.
4884 </p>
4890 <ul>
4892 - the default name of Apache's directory-level configuration file.</li>
4896 - a software application that enables a user to display and interact with
4897 text, images, and other information typically located on a web page at a
4898 website on the World Wide Web.</li>
4900 - a free software/open source data compression algorithm and program
4901 developed by Julian Seward.</li>
4903 - an important World Wide Web technology that enables a client web browser
4904 to request data from a program executed on the Web server.</li>
4906 - a log or record of changes made to a project.</li>
4908 - a computer system that accesses a (remote) service on another computer
4909 by some kind of network.</li>
4911 - a set of data values of a particular simple type, one for each row of
4912 the table.</li>
4914 - a packet of information sent by a server to a World Wide Web browser
4915 and then sent back by the browser each time it accesses that server.</li>
4917 - Comma-separated values</li>
4920 - an organized collection of data.</li>
4923 - a PHP module that extends PHP with additional functionality.</li>
4925 - a list of commonly asked question and there answers.</li>
4927 - one part of divided data/columns.</li>
4929 - a field or group of fields in a database record that point to a key
4930 field or group of fields forming a key of another database record in some
4931 (usually different) table.</li>
4933 - the free PDF library</li>
4935 GD Graphics Library</a> - a library by Thomas Boutell and others for
4936 dynamically manipulating images.</li>
4939 - gzip is short for GNU zip, a GNU free software file compression
4940 program.</li>
4942 - any machine connected to a computer network, a node that has a hostname.</li>
4944 - the unique name by which a network attached device is known on a network.</li>
4946 (HyperText Transfer Protocol)</a>
4947 - the primary method used to transfer or convey information on the World
4948 Wide Web.</li>
4951 additional security measures.</li>
4952 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4953 - a set of Internet-based services for servers using Microsoft Windows.</li>
4955 - a feature that allows quick access to the rows in a table.</li>
4957 - a data-oriented protocol used by source and destination hosts for
4958 communicating data across a packet-switched internetwork.</li>
4960 - a unique number that devices use in order to identify and communicate
4961 with each other on a network utilizing the Internet Protocol standard.</li>
4963 (Internet Server Application Programming Interface)</a>
4964 - the API of Internet Information Services (IIS).</li>
4966 - a business or organization that offers users access to the Internet and related services.</li>
4968 - a most commonly used standard method of lossy compression for
4969 photographic images.</li>
4975 - line of personal computers is designed, developed, manufactured, and
4976 marketed by Apple Computer.</li>
4977 <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>
4978 - the operating system which is included with all currently shipping Apple
4979 Macintosh computers in the consumer and professional markets.</li>
4981 - a cryptographic library.</li>
4983 - the MCrypt PHP extension.</li>
4984 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4985 - an Internet Standard for the format of e-mail.</li>
4987 - some sort of extension for the Apache Webserver.</li>
4989 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4990 Management System (DBMS).</li>
4992 - the improved MySQL client PHP extension.</li>
4994 - the MySQL client PHP extension.</li>
4996 - open standard for office documents.</li>
4997 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4998 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5000 (Portable Document Format)</a>
5001 - a file format developed by Adobe Systems for representing two
5002 dimensional documents in a device independent and resolution independent
5003 format.</li>
5005 - the PHP Extension and Application Repository.</li>
5007 - the perl-compatible regular expression functions for PHP</li>
5009 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5010 programming language used mainly for developing server-side applications
5011 and dynamic web content, and more recently, a broader range of software
5012 applications.</li>
5014 - a connection through which data is sent and received.</li>
5016 - Request for Comments (RFC) documents are a series of memoranda
5017 encompassing new research, innovations, and methodologies applicable to
5018 Internet technologies.</li>
5022 - represents a single, implicitly structured data item in a table.</li>
5024 - a computer system that provides services to other computing
5025 systems over a network.</li>
5026 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
5027 - handlers for different table types</li>
5029 - a form of inter-process communication.</li>
5031 Sockets Layer)</a>
5032 - a cryptographic protocol which provides secure communication on the Internet.</li>
5034 - Structured Query Language</li>
5036 - a set of data elements (cells) that is organized, defined and stored as
5037 horizontal rows and vertical columns where each item can be uniquely
5038 identified by a label or key or by it?s position in relation to other items.</li>
5041 - a type of archive file format: the Tape ARchive format.</li>
5043 - one of the core protocols of the Internet protocol suite.</li>
5047 - a sequence of characters, conforming to a standardized format, that is
5048 used for referring to resources, such as documents and images on the
5049 Internet, by their location.</li>
5051 - A computer (program) that is responsible for accepting HTTP requests
5052 from clients and serving them Web pages.</li>
5054 - a W3C-recommended general-purpose markup language for creating
5055 special-purpose markup languages, capable of describing many different
5056 kinds of data.</li>
5058 - a popular data compression and archival format.</li>
5060 - an open-source, cross-platform data compression library by Jean-loup
5061 Gailly and Mark Adler.</li>
5062 </ul>
5063 </div>
5066 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5069 <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>
5070 </ul>
5072 </body>
5073 </html>