| blob | 467a599ed01eab29089578b20907b05a0b93912f |
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>
1397 <dd>Defines whether to use a select-based menu and display only the current
1398 tables in the left frame (smaller page). Only in Non-Lightmode you can
1399 use the feature to display nested folders using
1401 </dd>
1404 <dd>In light mode, defines whether to display the names of databases (in the
1405 selector) using a tree, see also
1407 </dd>
1410 string or array</dt>
1411 <dd>The string used to separate the parts of the database name when showing
1412 them in a tree. Alternatively you can specify more strings in an array
1413 and all of them will be used as a separator.</dd>
1416 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1417 This means if you have tables like 'first__second__third' this will be
1419 If set to FALSE or empty, the feature is disabled. NOTE: You should
1420 not use this separator at the beginning or end of a
1421 table name or multiple times after another without any other
1422 characters in between.</dd>
1425 <dd>Defines how many sublevels should be displayed when splitting
1426 up tables by the above separator.</dd>
1429 <dd>Defines whether to display table comment as tool-tip in left frame or
1430 not.</dd>
1433 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1434 comment and the real name. That means that if you have a table called
1435 'user0001' and add the comment 'MyName' on it, you will see the name
1436 'MyName' used consequently in the left frame and the tool-tip shows
1437 the real name of the DB.</dd>
1440 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1442 When setting this to 'nested', the Alias of the Tablename is only used
1443 to split/nest the tables according to the
1445 directive. So only the folder is called like the Alias, the tablename itself
1446 stays the real tablename.</dd>
1449 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1452 <dd>Enter URL where logo in the navigation frame will point to.
1453 For use especially with self made theme which changes this.
1462 <dd>Defines whether or not to display a server choice at the top of the left frame.
1463 Defaults to FALSE.</dd>
1465 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1466 Defaults to FALSE (drop-down).</dd>
1468 <dd>Defines whether to display database choice in light navigation frame as links
1469 instead of in a drop-down. Defaults to 'auto' - on main page list is
1470 shown, when database is selected, only drop down is displayed.</dd>
1473 <dd>Defines the tab displayed by default when clicking the small
1474 icon next to each table name in the navigation panel. Possible
1480 <dd>Defines whether or not to display space usage and statistics about databases
1481 and tables.<br />
1482 Note that statistics requires at least MySQL 3.23.3 and that, at this
1483 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1486 <dd>Defines whether to display detailed server information on main page.
1487 You can additionally hide more information by using
1489 </dd>
1494 </dt>
1497 not at the starting main (right) frame. This setting
1498 does not check MySQL commands entered directly.<br /><br />
1500 Please note that to block the usage of phpinfo() in scripts, you
1507 hard coded password value in the configuration file, end users can't
1508 be allowed to change their passwords.</dd>
1511 <dd>Defines whether to suggest a database name on the
1515 <dd>Defines whether navigation bar buttons and the right panel top menu
1516 contain text or symbols only. A value of TRUE displays icons, FALSE
1517 displays text and 'both' displays both icons and text.</dd>
1520 <dd>Defines whether a user should be displayed a
1524 <dd>Number of rows displayed when browsing a result set. If the result set
1531 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1535 option is ticked by default.</dd>
1539 from editing when browsing a table's content. Valid values are:
1544 </ul>
1545 </dd>
1548 <dd>Defines whether or not MySQL functions fields should be initially
1549 displayed in edit/insert mode. Since version 2.10, the user can
1550 toggle this setting from the interface.
1551 </dd>
1554 <dd>Defines whether or not type fields should be initially
1555 displayed in edit/insert mode. The user can
1556 toggle this setting from the interface.
1557 </dd>
1560 <dd>Defines which type of editing controls should be used for CHAR and
1561 VARCHAR fields. Possible values are:
1562 <ul><li>input - this allows to limit size of text to size of field in
1563 MySQL, but has problems with newlines in fields</li>
1564 <li>textarea - no problems with newlines in fields, but also no
1565 length limitations</li>
1566 </ul>
1567 Default is old behavior so input.</dd>
1573 <dd>If there are fewer items than this in the set of foreign keys, then a
1574 drop-down box of foreign keys is presented, in the style described by the
1576 setting.</dd>
1579 <dd>For the foreign key drop-down fields, there are several methods of
1580 display, offering both the key and value data. The contents of the
1581 array should be one or both of the following strings:
1587 </dt>
1588 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1589 creating a dump file</dd>
1592 </dt>
1593 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1594 compressed exports. This doesn't affect smaller dumps and allows users to
1595 create larger dumps that won't otherwise fit in memory due to php
1596 memory limit. Produced files contain more GZip/BZip2 headers, but all
1597 normal programs handle this correctly.</dd>
1601 mainframe.</dd>
1605 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1610 <dd>How many columns will be utilized to display the tables on the
1611 database property view? Default is 1 column. When setting this to a
1612 value larger than 1, the type of the database will be omitted for more
1613 display space.</dd>
1617 <dd>Defines the tab displayed by default on server view. Possible
1624 <dd>Defines the tab displayed by default on database view. Possible
1629 <dd>Defines the tab displayed by default on table view. Possible
1636 points to the MySQL documentation (type depends
1637 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1638 generated.<br />
1640 for more information about MySQL manuals and their types.</dd>
1643 <dd>Type of MySQL documentation:
1649 </ul>
1650 </dd>
1653 <dd>Defines the default language to use, if not browser-defined or
1654 user-defined.<br />
1655 The corresponding language file needs to be in
1657 </dd>
1660 <dd>Defines the default connection collation to use, if not
1661 user-defined.<br />
1667 The corresponding language file needs to be in
1669 </dd>
1672 <dd>Limit list of available languages to those matching the given regular
1673 expression. For example if you want only Czech and English, you should
1677 <dd>Default character set to use for recoding of MySQL queries. This must be
1678 enabled and it's described by
1680 option.<br />
1681 You can give here any character set which is in
1683 array and this is just default choice, user can select any of them.</dd>
1686 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1687 support (compiled in or module) in PHP to allow MySQL queries recoding
1688 and used language file must have it enabled (by default only these
1689 which are in Unicode, just to avoid losing some characters).<br /><br />
1692 in the Export and Import pages, to choose the character set when
1693 exporting a file. The default value in this menu comes from
1695 </dd>
1698 <dd>You can select here which functions will be used for character set
1699 conversion. Possible values are:
1700 <ul><li>auto - automatically use available one (first is tested
1701 iconv, then recode)</li>
1704 </ul>
1705 Default is auto.</dd>
1708 <dd>Specify some parameters for iconv used in charset conversion. See
1711 used, so that invalid characters will be transliterated.</dd>
1714 <dd>Available character sets for MySQL conversion. You can add your own (any of
1715 supported by recode/iconv) or remove these which you don't use.
1716 Character sets will be shown in same order as here listed, so if you
1717 frequently use some of these move them to the top.</dd>
1722 default empty, you need to fill in some trusted proxy servers if you
1723 want to use rules for IP addresses behind proxy.<br /><br />
1725 The following example specifies that phpMyAdmin should trust a
1727 <pre>
1728 $cfg['TrustedProxies'] =
1730 </pre>
1731 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1732 client's IP address as usual.
1733 </dd>
1737 MIME transformations.<br />
1738 Possible values are:
1739 <ul><li>auto - automatically detect, this is a bit expensive
1741 according to your server real possibilities</li>
1744 </ul>
1745 Default is auto.
1746 </dd>
1749 <dd>
1750 We normally check the permissions on the configuration file to ensure
1751 it's not world writable. However, phpMyAdmin could be installed on
1752 a NTFS filesystem mounted on a non-Windows server, in which case the
1753 permissions seems wrong but in fact cannot be detected. In this case
1755 </dd>
1758 <dd>
1759 Limit for length of URL in links. When length would be above this limit, it
1760 is replaced by form with button.
1761 This is required as some web servers (IIS) have problems with long URLs.
1763 </dd>
1767 </dd>
1769 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1770 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1771 </dt>
1772 <dd>The background styles used for both the frames.
1775 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1777 <dd>The style used for the pointer in the navi frame.
1781 </dt>
1782 <dd>The color used for the database name in the navi frame.
1791 </dd>
1795 <dd>The style used for table headers. See
1800 </dd>
1804 </dd>
1806 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1808 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1810 </dt>
1812 The former feature highlights the row over which your mouse is passing
1813 and the latter lets you visually mark/unmark rows by clicking on
1814 them.<br />
1819 <dd>You put here a valid CSS font family value, for example
1824 <dd>You put here a valid CSS font family value, for example
1838 </dt>
1840 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1842 The Char* values are used for CHAR and VARCHAR editing (if configured
1846 </dt>
1850 </dt>
1851 <dd>Defines if the whole textarea of the query box will be selected on
1852 click.</dd>
1855 </dt>
1856 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1857 editing.</dd>
1860 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1861 Can be turned off by a toggle button on the browse page.</dd>
1865 </dt>
1866 <dd>Defines the place where modify and delete links would be put when
1867 tables contents are displayed (you may have them displayed both at the
1868 left and at the right).
1874 </dt>
1876 Define which one is displayed by default. The first mode displays each
1877 row on a horizontal line, the second rotates the headers by 90
1878 degrees, so you can use descriptive headers even though fields only
1879 contain small values and still print them out. The vertical mode sorts
1880 each row on a vertical lineup.<br /><br />
1882 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1883 the rotation of the header for horizontalflipped is done via CSS. If
1884 set to 'fake' PHP does the transformation for you, but of course this
1885 does not look as good as CSS.</dd>
1889 string or integer</dt>
1890 <dd>When editing/creating new columns in a table all fields normally get
1891 lined up one field a line. (default: 'horizontal'). If you set this to
1892 'vertical' you can have each field lined up vertically beneath each
1893 other. You can save up a lot of place on the horizontal direction and
1894 no longer have to scroll. If you set this to integer, editing of fewer
1895 columns will appear in 'vertical' mode, while editing of more fields
1896 still in 'horizontal' mode. This way you can still effectively edit
1897 large number of fields, while having full view on few of them.</dd>
1901 </dt>
1903 display of column comments in Browse or Property display. In browse
1904 mode, the comments are shown inside the header. In property mode,
1905 comments are displayed using a CSS-formatted dashed-line below the
1906 name of the field. The comment is shown as a tool-tip for that field.
1907 </dd>
1919 <dd>Whether to display a link to validate a query in any SQL Query box.
1926 <dd>
1927 The name of the directory where
1929 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1930 are available under a drop-down box when you click the database or
1931 table name, then the Import tab.
1932 <br /><br />
1934 If you want different directory for each user, %u will be replaced
1935 with username.<br /><br />
1939 compressed formats is enabled).<br /><br />
1941 This feature is useful when your file is too big to be uploaded via
1943 uploads are disabled in PHP.<br /><br />
1945 Please note that if PHP is running in safe mode, this directory must
1946 be owned by the same user as the owner of the phpMyAdmin scripts.
1947 <br /><br />
1951 alternatives.
1952 </dd>
1955 <dd>
1956 The name of the directory where dumps can be saved.<br /><br />
1958 If you want different directory for each user, %u will be replaced
1959 with username.<br /><br />
1961 Please note that the directory must exist and has to be writable for
1962 the user running webserver.<br /><br />
1964 Please note that if PHP is running in safe mode, this directory must
1965 be owned by the same user as the owner of the phpMyAdmin scripts.
1966 </dd>
1969 <dd>
1970 The name of the directory where temporary files can be stored.
1971 <br /><br />
1973 This is needed for native MS Excel export, see
1979 <br /><br />
1981 If the directory where phpMyAdmin is installed is subject to an
1983 temporary directory in some directory accessible by the web
1984 server. However for security reasons, this directory should be outside
1985 the tree published by webserver. If you cannot avoid having this
1986 directory published by webserver, place at least an empty
1988 possible.
1989 <br /><br />
1991 This directory should have as strict permissions as possible as the only
1992 user required to access this directory is the one who runs the
1993 webserver. If you have root privileges, simply make this user owner of
1994 this directory and make it accessible only by it:
1995 <br /><br />
1997 <pre>
1998 chown www-data:www-data tmp
1999 chmod 700 tmp
2000 </pre>
2002 If you cannot change owner of the directory, you can achieve a similar
2005 <pre>
2006 chmod 700 tmp
2007 setfacl -m "g:www-data:rwx" tmp
2008 setfacl -d -m "g:www-data:rwx" tmp
2009 </pre>
2011 If neither of above works for you, you can still make the directory
2013 system reading and writing data in this directory.
2014 </dd>
2017 <dd>
2018 In this array are defined default parameters for export, names of
2019 items are similar to texts seen on export page, so you can easily
2020 identify what they mean.
2021 </dd>
2024 <dd>
2025 In this array are defined default parameters for import, names of
2026 items are similar to texts seen on import page, so you can easily
2027 identify what they mean.
2028 </dd>
2031 <dd>
2032 Repeat the headers every X cells, or 0 to deactivate.
2033 </dd>
2041 </dt>
2042 <dd>
2043 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2044 or icon is always displayed on the left panel. If JavaScript is enabled in
2045 your browser, a click on this opens a distinct query window, which is
2046 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2047 changes to display a query box.<br /><br />
2049 The size of this query window can be customized with
2051 - both integers for the size in pixels. Note that normally, those
2053 theme you are using.<br /><br />
2057 opens the query window and puts the current query
2058 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2059 query in the right panel's query box.
2060 <br /><br />
2061 The usage of the JavaScript query window is recommended if you have a
2062 JavaScript enabled browser. Basic functions are used to exchange quite
2063 a few variables, so most 4th generation browsers should be capable to
2064 use that feature. It currently is only tested with Internet Explorer 6
2065 and Mozilla 1.x.
2066 <br /><br />
2068 to a table, which has to be created by you (see <a
2070 all your queries will be appended to the form, but only as long as
2071 your window is opened they remain saved.
2072 <br /><br />
2073 When using the JavaScript based query window, it will always get
2074 updated when you click on a new table/db to browse and will focus if
2075 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2076 the query window by checking the box "Do not overwrite this query from
2077 outside the window" below the query textarea. Then you can browse
2078 tables/databases in the background without losing the contents of the
2079 textarea, so this is especially useful when composing a query with
2080 tables you first have to look in. The checkbox will get automatically
2081 checked whenever you change the contents of the textarea. Please
2082 uncheck the button whenever you definitely want the query window to
2083 get updated even though you have made alterations.
2084 <br /><br />
2087 <br /><br />
2088 The query window also has a custom tabbed look to group the features.
2090 default tab to be used when opening the query window. It can be set to
2091 either 'sql', 'files', 'history' or 'full'.</dd>
2097 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2099 If the approximate row count as returned by
2102 count will be used.
2103 </dd>
2105 <dd>For VIEWs, since obtaining the exact count could have an
2106 impact on performance, this value is the maximum to be displayed, using
2108 any row counting.
2109 </dd>
2113 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2115 page. By clicking on the button 'toggle scratchboard' on the page
2116 where you edit x/y coordinates of those elements you can activate a
2117 scratchboard where all your elements are placed. By clicking on an
2118 element, you can move them around in the pre-defined area and the x/y
2119 coordinates will get updated dynamically. Likewise, when entering a
2120 new position directly into the input field, the new position in the
2121 scratchboard changes after your cursor leaves the input field.<br />
2122 You have to click on the 'OK'-button below the tables to save the new
2123 positions. If you want to place a new element, first add it to the
2124 table of elements and then you can drag the new element around.<br />
2125 By changing the paper size and the orientation you can change the size
2126 of the scratchboard as well. You can do so by just changing the
2127 dropdown field below, and the scratchboard will resize automatically,
2128 without interfering with the current placement of the elements.<br />
2129 If ever an element gets out of range you can either enlarge the paper
2130 size or click on the 'reset' button to place all elements below each
2131 other.<br />
2133 get this control to work. The basic Drag&Drop script functionality
2134 was kindly borrowed from www.youngpup.net and is underlying so
2135 specific license.</dd>
2138 <dd>Sorts database and table names according to natural order (for example,
2139 t1, t2, t10). Currently implemented in the left panel (Light mode)
2140 and in Database view, for the table list.</dd>
2151 <dd>Allows you to specify window's title bar. Following magic string can
2152 be used to get special values:
2153 <dl>
2159 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2168 </dl>
2169 </dd>
2179 </dd>
2182 <dd>If theme manager is active, use this as the path of the subdirectory
2183 containing all the themes.</dd>
2197 </dt>
2198 <dd>Default queries that will be displayed in query boxes when user didn't
2199 specify any. Use %d for database name, %t for table name and %f for a
2200 comma separated list of field names. Note that %t and %f are only
2204 <dd>
2205 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
2206 default we use HTML to format the query, but you can disable this by
2208 </dd>
2211 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2212 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2213 query inside a bracket is indented. By changing
2216 specifies the units of the indent amount that you specified. This is
2217 used via stylesheets.</dd>
2220 <dd>This array is used to define the colours for each type of element of
2221 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2223 If you specify an empty string for the color of a class, it is ignored
2224 in creating the stylesheet.
2225 You should not alter the class names, only the colour strings.<br />
2246 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2250 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2251 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2252 </ul>
2253 </dd>
2257 <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,
2258 as originally published on
2260 <br />
2261 For help in setting up your system to use the service, see the
2263 </dd>
2267 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2268 and any password, so we use those by default. Instead, if
2269 you have an account with them, you can put your login details
2270 here, and it will be used in place of the anonymous login.</dd>
2271 </dl>
2272 </dd>
2275 <dd><b>DEVELOPERS ONLY!</b></dd>
2278 <dd><b>DEVELOPERS ONLY!</b><br />
2279 Enable logging queries and execution times to be displayed in the bottom
2280 of main page (right frame).</dd>
2283 <dd><b>DEVELOPERS ONLY!</b><br />
2284 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2285 the code.<br />
2286 For help in setting up your system to this, see the
2290 <dd><b>DEVELOPERS ONLY!</b><br />
2291 Enable profiling support for phpMyAdmin. This will append a chunk of data
2292 to the end of every page displayed in the main window with profiling
2293 statistics for that page.<br />
2294 You may need to increase the maximum execution time for this to
2295 complete successfully.<i>Profiling was removed from the code for
2296 version 2.9.0 due to licensing issues.</i></dd>
2298 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2299 <dd><b>DEVELOPERS ONLY!</b><br />
2300 When profiling data is displayed, this variable controls the threshold of
2301 display for any profiling data, based on the average time each time has
2302 taken. If it is over the threshold it is displayed, otherwise it is not
2303 displayed. This takes a value in milliseconds. In most cases you don't need
2304 to edit this.</dd>
2307 <dd>All possible types of a MySQL column. In most cases you don't need to
2308 edit this.</dd>
2311 <dd>Possible attributes for fields. In most cases you don't need to edit
2312 this.</dd>
2315 <dd>A list of functions MySQL supports. In most cases you don't need to
2316 edit this.</dd>
2319 <dd>Mapping of column types to meta types used for preferring displayed
2320 functions. In most cases you don't need to edit this.</dd>
2323 <dd>Functions preferred for column meta types as defined in
2324 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2325 to edit this.</dd>
2328 <dd>Functions selected by default when inserting/changing row, Functions
2329 are defined for meta types from
2331 <code>first_timestamp</code>, which is used for first timestamp column
2332 in table.</dd>
2335 <dd>Operators available for search operations on numeric and date fields.
2336 </dd>
2339 <dd>Operators available for search operations on character fields.
2340 Note that we put <code>LIKE</code> by default instead of
2341 <code>LIKE %...%</code>, to avoid unintended performance problems
2342 in case of huge tables.</dd>
2345 <dd>Operators available for search operations on enum fields.</dd>
2348 <dd>Additional operators available for search operations when the
2349 field can be null.</dd>
2351 </dl>
2353 <!-- TRANSFORMATIONS -->
2359 </ol>
2363 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2365 section</a> on how to do so.</p>
2367 <p> You can apply different transformations to the contents of each field. The
2368 transformation will take the content of each field and transform it with
2369 certain rules defined in the selected transformation.</p>
2371 <p> Say you have a field 'filename' which contains a filename. Normally you would
2372 see in phpMyAdmin only this filename. Using transformations you can transform
2373 that filename into a HTML link, so you can click inside of the phpMyAdmin
2374 structure on the field's link and will see the file displayed in a new browser
2375 window. Using transformation options you can also specify strings to
2376 append/prepend to a string or the format you want the output stored in.</p>
2378 <p> For a general overview of all available transformations and their options,
2379 you can consult your
2380 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2381 installation.</p>
2383 <p> For a tutorial on how to effectively use transformations, see our
2385 the official phpMyAdmin homepage.</p>
2389 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2390 clicking on the 'Structure' link for a table). There click on
2391 "Change" (or change icon) and there you will see three new fields at
2392 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2393 'Transformation options'.</p>
2395 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2396 that corresponds to the column's contents. Please note that
2397 transformations are inactive as long as no MIME-type is selected.</li>
2399 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2400 hopefully growing amount of pre-defined transformations. See below for information on
2401 how to build your own transformation.<br />
2403 There are global transformations and mimetype-bound transformations. Global transformations
2404 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2405 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2406 transformations which operate on the main mimetype (like 'image'), which will most likely
2407 take the subtype into regard, and those who only operate on a
2408 specific subtype (like 'image/jpeg').<br />
2410 You can use transformations on mimetypes for which the function was not defined for. There
2411 is no security check for you selected the right transformation, so take care of what the
2412 output will be like.</li>
2414 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2415 transform-function specific options here. Usually the transforms can operate with default
2416 options, but it is generally a good idea to look up the overview to see which options are
2417 necessary.<br />
2419 Much like the ENUM/SET-Fields, you have to split up several options using the format
2420 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2421 parsed as an array, leaving the first value the first element in the array, and so
2422 forth.<br />
2424 If you want to specify a MIME character set you can define it in the transformation_options.
2425 You have to put that outside of the pre-defined options of the specific mime-transform,
2427 for which you can specify 2 options and you want to append a character set, enter "'first
2428 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2430 </ul>
2434 <p> All mimetypes and their transformations are defined through single files in
2435 the directory 'libraries/transformations/'.</p>
2437 <p> They are stored in files to ease up customization and easy adding of new
2438 transformations.</p>
2440 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2441 always work. It makes no sense to apply a transformation to a mimetype, the
2442 transform-function doesn't know to handle.</p>
2444 <p> One can, however, use empty mime-types and global transformations which should work
2445 for many mimetypes. You can also use transforms on a different mimetype they where built
2446 for, but pay attention to option usage as well as what the transformation does to your
2447 field.</p>
2449 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2450 any other transform function and provides some basic functions.</p>
2452 <p> There are 5 possible file names:</p>
2454 <ol><li>A mimetype+subtype transform:<br /><br />
2456 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2458 Please not that mimetype and subtype are separated via '_', which shall
2459 not be contained in their names. The transform function/filename may
2460 contain only characters which cause no problems in the file system as
2461 well as the PHP function naming convention.<br /><br />
2463 The transform function will the be called
2464 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2466 <b>Example:</b><br /><br />
2468 <tt>text_html__formatted.inc.php</tt><br />
2469 <tt>PMA_transform_text_html__formatted()</tt></li>
2471 <li>A mimetype (w/o subtype) transform:<br /><br />
2473 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2475 Please note that there are no single '_' characters.
2476 The transform function/filename may contain only characters which cause
2477 no problems in the file system as well as the PHP function naming
2478 convention.<br /><br />
2480 The transform function will the be called
2481 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2483 <b>Example:</b><br /><br />
2485 <tt>text__formatted.inc.php</tt><br />
2486 <tt>PMA_transform_text__formatted()</tt></li>
2488 <li>A mimetype+subtype without specific transform function<br /><br />
2490 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2492 Please note that there are no '__' characters in the filename. Do not
2493 use special characters in the filename causing problems with the file
2494 system.<br /><br />
2496 No transformation function is defined in the file itself.<br /><br />
2498 <b>Example:</b><br /><br />
2500 <tt>text_plain.inc.php</tt><br />
2501 (No function)</li>
2503 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2505 <tt>[mimetype].inc.php</tt><br /><br />
2507 Please note that there are no '_' characters in the filename. Do not use
2508 special characters in the filename causing problems with the file system.
2509 <br /><br />
2511 No transformation function is defined in the file itself.<br /><br />
2513 <b>Example:</b><br /><br />
2515 <tt>text.inc.php</tt><br />
2516 (No function)</li>
2518 <li>A global transform function with no specific mimetype<br /><br />
2520 <tt>global__[transform].inc.php</tt><br /><br />
2522 The transform function will the be called
2523 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2525 <b>Example:</b><br /><br />
2527 <tt>global__formatted</tt><br />
2528 <tt>PMA_transform_global__formatted()</tt></li>
2529 </ol>
2531 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2532 transform function.</p>
2534 <p> All filenames containing no '__' in themselves are not shown as valid transform
2535 functions in the dropdown.</p>
2537 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2538 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2539 without a transform function. Also note the introduction of a function description in
2540 the language files. For each function a $strTransformation_[filename without .inc.php]
2541 has to exist.</p>
2543 <p> You can use the template generator to generate new functions and entries in the
2544 language file.</p>
2546 <p> To create a new transform function please see
2547 <tt>libraries/transformations/template_generator.sh</tt>.
2548 To create a new, empty mimetype please see
2549 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2551 <p> A transform function always gets passed three variables:</p>
2553 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2554 you want to transform.</li>
2555 <li><b>$options</b> - Contains any user-passed options to a transform function
2556 as an array.</li>
2557 <li><b>$meta</b> - Contains an object with field information to your column.
2558 The data is drawn from the output of the
2560 function. This means, all object properties described on the
2562 available in this variable and can be used to transform a field accordingly
2563 to unsigned/zerofill/not_null/... properties.<br />
2564 The $meta->mimetype variable contains the original MIME-type of the
2565 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2566 </ol>
2568 <!-- FAQ -->
2575 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2580 </ol>
2582 <p> Please have a look at our
2584 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2585 features and or interface.</p>
2591 action is required or phpMyAdmin sends a blank page or a page full of
2592 cryptic characters to my browser, what can I do?</a></h4>
2594 <p> There are some known PHP bugs with output buffering and compression.<br />
2596 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2597 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2598 configuration file.<br />
2599 Furthermore, we know about such problems connected to the release
2600 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2601 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2606 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2607 See also the
2609 entry about PHP bugs with output buffering.<br />
2610 If your server keeps crashing, please ask for help in the various Apache
2611 support groups.</p>
2615 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2616 script: I'm always displayed the login screen.</a></h4>
2618 <p> This is a known PHP bug (see this
2620 official PHP bug database. It means there is and won't be any phpMyAdmin
2621 fix against it because there is no way to code a fix.</p>
2627 application misbehaved by not returning a complete set of
2629 </h4>
2631 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2632 Have a look at the last message in this
2634 official PHP bug database.</p>
2639 and/or many error messages with the
2641 mode.</a></h4>
2643 <p> This is a known problem with the PHP
2645 filter: it's not so stable. Please use instead the cookie authentication mode.
2646 </p>
2651 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2652 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2653 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2654 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2655 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2660 work.</a></h4>
2662 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2663 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2664 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2665 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2666 We faced PHP crashes when trying to download a dump with MS Internet
2667 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2668 this case you should switch to the release version of PHP 4.2.0.</p>
2672 an error about safe mode being in effect.</a></h4>
2674 <p> Your uploaded file is saved by PHP in the "upload dir", as
2675 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2676 the system default is <i>/tmp</i>).<br />
2677 We recommend the following setup for Apache servers running in safe mode,
2678 to enable uploads of files while being reasonably secure:</p>
2680 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2681 <li>give ownership to the Apache server's user.group:
2682 <tt>chown apache.apache /tmp/php</tt></li>
2683 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2684 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2685 <li>restart Apache</li>
2686 </ul>
2690 general file uploads don't work on my system and uploaded files have a
2691 <tt>Content-Type:</tt> header in the first line.</a></h4>
2693 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2694 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2695 So the problem is that this package has a serious bug that was corrected
2696 ages ago in PHP (2001-01-28: see
2698 for more details). The problem is that the bugged package is still
2699 available though it was corrected (see
2701 for more details).<br />
2702 So please download
2703 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2704 and the problem should go away.<br />
2705 And that fixes the \r\n problem with file uploads!</p>
2709 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2710 I'm using the Apache server.</a></h4>
2712 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2713 your <i>httpd.conf</i>:</p>
2717 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2721 uploading a file from the query box.</a></h4>
2723 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2724 restrictions. However you need to create temporary directory and
2726 The uploaded files will be moved there, and after execution of your
2732 <p> The MySQL manual explains how to
2734 reset the permissions</a>.</p>
2739 execute a bookmark.</a></h4>
2741 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2742 cannot access the uploaded query.</p>
2747 submit a query from the convenient text area.</a></h4>
2749 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2750 and try to increase it.</p>
2754 </h4>
2756 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2757 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2758 names to align with current standards.</p>
2763 </h4>
2765 <p> Starting with version 2.7.0, the import engine has been re–written and these
2766 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2767 to take advantage of the new import features.</p>
2769 <p> The first things to check (or ask your host provider to check) are the
2770 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2771 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2772 All of these three settings limit the maximum size of data that can be
2773 submitted and handled by PHP. One user also said that post_max_size
2774 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2776 There exist several workarounds if your upload is too big or your
2777 hosting provider is unwilling to change the settings:</p>
2780 feature. This allows one to
2781 upload a file to the server via scp, ftp, or your favorite file transfer
2782 method. PhpMyAdmin is then able to import the files from the temporary
2784 section</a> of this document.</li>
2786 BigDump</a>) to split the files before uploading. We cannot support this
2787 or any third party applications, but are aware of users having success
2788 with it.</li>
2789 <li>If you have shell (command line) access, use MySQL to import the files
2790 directly. You can do this by issuing the "source" command from
2791 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2792 </ul>
2796 support?</a></h4>
2798 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2799 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2800 connect to your MySQL server using PHP's classic
2803 is available in php 5.0. The latter one should be used unless you have
2804 good reason not to do so.<br />
2805 When compiling php, we strongly recommend that you manually link the MySQL
2806 extension of your choice to a MySQL client library of at least the same
2807 minor version since the one that is bundled with some PHP distributions is
2810 If your webserver is running on a windows system, you might want to try
2811 MySQL's
2813 instead of the MySQL / MySQLi extensions that are bundled with the official
2814 php Win32 builds.</p>
2818 message, "Client does not support authentication protocol requested
2819 by server; consider upgrading MySQL client"</a></h5>
2821 <p> You tried to access MySQL with an old MySQL client library. The version of
2822 your MySQL client library can be checked in your phpinfo() output.
2823 In general, it should have at least the same minor version as your server
2827 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2828 changed the authentication hash and your PHP is trying to use the old method.
2830 with the proper client library to match your MySQL installation. Your
2831 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2832 More information (and several workarounds) are located in the
2834 </p>
2838 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2839 capital letter in its name it is changed to lowercase as it should. But
2840 if I try to DROP this table MySQL is unable to find the corresponding
2841 file.</a></h4>
2843 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2844 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2845 directive.</p>
2849 script seems not to know the font face I'm using!</a></h4>
2851 <p> The "FPDF" library we're using for this feature requires some
2852 special files to use font faces.<br />
2854 these files.</p>
2858 check PHP Configuration".</a></h4>
2860 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2861 "MySQL extension". This extension may be part of the PHP
2862 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2863 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2864 to load the extension but failed.<br /><br />
2866 Usually, the problem is solved by installing a software package called
2867 "PHP-MySQL" or something similar.</p>
2872 and I cannot log in using cookie auth.</a></h4>
2874 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2878 so I cannot upload.</a></h4>
2880 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2881 parameter is not set to "on".</p>
2885 a new table the table and field names are changed to lowercase!</a></h4>
2887 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2888 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2889 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2890 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2891 directory and add the following line to the group [mysqld]:</p>
2893 <pre>set-variable = lower_case_table_names=0</pre>
2895 <p> Next, save the file and restart the MySQL service. You can always check the
2896 value of this directive using the query</p>
2898 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2902 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2905 </p>
2909 and I get problems, such as undefined variables when I run a
2912 <p> A tip from Jose Fandos: put a comment on the following two lines
2913 in httpd.conf, like this:</p>
2915 <pre>
2916 # mod_gzip_item_include file \.php$
2918 </pre>
2920 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2921 PHP scripts. Of course you have to restart Apache.</p>
2926 I get the error "No input file specified" when trying to
2927 run phpMyAdmin.</a></h4>
2929 <p> This is a permission problem. Right-click on the phpmyadmin folder
2930 and choose properties. Under the tab Security, click on "Add"
2931 and select the user "IUSR_machine" from the list. Now set his
2932 permissions and it should work.</p>
2936 db_structure.php with plenty of tables).</a></h4>
2939 GZIP output buffering is enabled. If you turn off it (by
2941 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2942 PHP 5.0.0.</p>
2946 message 'Errorcode: 13'. What does this mean?</a></h4>
2948 <p> This can happen due to a MySQL bug when having database / table names with
2949 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2950 To fix this, turn off this directive, convert all database and table names
2951 to lower case and turn it on again. Alternatively, there's a bug-fix
2952 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2956 and the fields are duplicated.</a></h4>
2958 <p> It is possible to configure Apache in such a way that PHP has problems
2959 interpreting .php files.</p>
2961 <p> The problems occur when two different (and conflicting) set of directives
2962 are used:</p>
2964 <pre>
2965 SetOutputFilter PHP
2966 SetInputFilter PHP
2967 </pre>
2969 <p> and</p>
2971 <pre>AddType application/x-httpd-php .php</pre>
2973 <p> In the case we saw, one set of directives was in
2974 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2975 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2976 The recommended way is with <tt>AddType</tt>, so just comment out
2977 the first set of lines and restart Apache:</p>
2979 <pre>
2980 #SetOutputFilter PHP
2981 #SetInputFilter PHP
2982 </pre>
2987 <p> This problem is known to happen when the server is running Turck MMCache
2988 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2993 <p>Yes.</p>
2994 <p>
2995 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
2996 is still maintained.
2997 </p>
3000 <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>
3002 <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>
3005 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3006 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3007 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3008 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3009 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3010 enabled.) Click <tt>OK</tt>.</li>
3011 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3012 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3013 </ol>
3017 PHP 5.0.4 on 64-bit systems?</a></h4>
3019 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3020 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3026 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
3027 the order of the server paragraph in <tt>config.inc.php</tt>.
3028 Table and script parts are optional. If you want
3029 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3030 some configuration. Following lines apply only for <a
3032 that you have enabled some features within global configuration. You need
3033 <code>Options FollowSymLinks</code> and <code>AllowOverride
3034 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3035 you need mod_rewrite to be enabled. Then you just need to create following
3036 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3037 (don't forget to change directory name inside of it):</p>
3039 <pre>
3040 RewriteEngine On
3041 RewriteBase /path_to_phpMyAdmin
3042 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3043 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3044 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3045 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3046 </pre>
3049 <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>
3051 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3052 following rewrite rule:</p>
3054 <pre>
3055 RewriteEngine On
3056 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3057 </pre>
3061 </h4>
3062 <p>
3063 There can be many explanations to this and a look at your server's
3064 error log file might give a clue.
3065 </p>
3069 password encryption in cookie auth doesn't work.</a></h4>
3071 <p> If your cluster consist of different architectures, PHP code used for
3072 encryption/decryption won't work correct. This is caused by use of
3073 pack/unpack functions in code. Only solution is to use mcrypt extension
3074 which works fine in this case.</p>
3079 <p> Yes but the default configuration values of Suhosin are known to cause
3080 problems with some operations, for example editing a table with many
3081 columns and no primary key or with textual primary key.
3082 </p>
3083 <p>
3084 Suhosin configuration might lead to malfunction in some cases and it can
3085 not be fully avoided as phpMyAdmin is kind of application which needs to
3086 transfer big amounts of fields in single HTTP request, what is something
3087 what Suhosin tries to prevent. Generally all
3088 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3089 <code>suhosin.get.*</code> directives can have negative effect on
3090 phpMyAdmin usability. You can always find in your error logs which limit
3091 did cause dropping of variable, so you can diagnose the problem and adjust
3092 matching configuration variable.
3093 </p>
3094 <p>
3095 The default values for most Suhosin configuration options will work in most
3096 scenarios, however you might want to adjust at least following parameters:
3097 </p>
3099 <ul>
3100 <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>
3101 <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>
3102 <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>
3103 <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>
3104 <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>
3105 <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>
3106 <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>
3107 <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>
3108 </ul>
3110 <p>
3112 <tt>SuhosinDisableWarning</tt> directive</a>.
3113 </p>
3117 but then my connection is redirected back to http. What can cause this
3118 behavior?</a></h4>
3120 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3121 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>
3124 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
3126 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3127 Example from the Apache 2.2 documentation:</p>
3128 <pre>
3129 ProxyPass /mirror/foo/ http://backend.example.com/
3130 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3131 ProxyPassReverseCookieDomain backend.example.com public.example.com
3132 ProxyPassReverseCookiePath / /mirror/foo/
3133 </pre>
3135 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3136 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3137 This is not specific to phpmyadmin, it's just the behavior of Apache.
3138 </p>
3140 <pre>
3141 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3142 ProxyPassReverse /mirror/foo/
3143 http://backend.example.com/%7Euser/phpmyadmin
3144 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3145 </pre>
3147 <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>
3148 for more details.</p>
3152 privileges, I get an error about an unknown column.</a></h4>
3154 <p> The MySQL server's privilege tables are not up to date, you need to run
3155 the <tt>mysql_upgrade</tt> command on the server.</p>
3162 headers already sent by ..." is displayed, what's the problem?</a></h4>
3164 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3165 (I.E. no blank lines, no spaces, no characters...) neither before the
3166 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3167 tag at the end. We also got a report from a user under IIS, that used
3168 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3169 contained an end-of-line character (hex 0A) at the end; removing this character
3170 cleared his errors.</p>
3175 <p> Either there is an error with your PHP setup or your username/password is
3176 wrong. Try to make a small script which uses mysql_connect and see if it
3177 works. If it doesn't, it may be you haven't even compiled MySQL support
3178 into PHP.</p>
3182 connect to local MySQL server through socket '/tmp/mysql.sock'
3183 (111) ..." is displayed. What can I do?</a></h4>
3185 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3187 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3188 In your <i>php.ini</i> you will find a line</p>
3190 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3192 <p> change it to</p>
3194 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3196 <p> Then restart apache and it will work.</p>
3198 <p> Here is a fix suggested by Brad Ummer:</p>
3200 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3201 To do this, telnet to your server and go to the MySQL bin directory. In
3202 this directory there should be a file named <i>mysqladmin</i>. Type
3203 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3204 info about your MySQL server, including the socket
3205 (<i>/tmp/mysql.sock</i>, for example).</li>
3206 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3207 phpMyAdmin, you need to complete the socket information in the
3208 <i>config.inc.php</i>.<br />
3209 For example:
3211 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3212 <br /><br />
3214 Please also make sure that the permissions of this file allow to be readable
3215 by your webserver (i.e. '0755').</li>
3216 </ul>
3218 <p> Have also a look at the
3220 corresponding section of the MySQL documentation</a>.</p>
3224 what can I do?</a></h4>
3227 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3228 sometime.<br />
3229 Also have a look at your PHP version number: if it contains "4.0b..."
3230 it means you're running a beta version of PHP. That's not a so good idea,
3231 please upgrade to a plain revision.</p>
3235 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3236 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3238 <p> Check the value you set for the
3240 directive in the phpMyAdmin configuration file.</p>
3244 password: YES)"-error when trying to access a MySQL-Server on a
3245 host which is port-forwarded for my localhost.</a></h4>
3247 <p> When you are using a port on your localhost, which you redirect via
3248 port-forwarding to another host, MySQL is not resolving the localhost
3249 as expected.<br />
3250 Erik Wasser explains: The solution is: if your host is "localhost"
3251 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3252 connection for speeding up things. And that doesn't work in this configuration
3253 with port forwarding.<br />
3259 <p> Themes are configured with
3263 <br />
3265 should not delete the directory "original" or its underlying
3266 structure, because this is the system theme used by phpMyAdmin.
3267 "original" contains all images and styles, for backwards
3268 compatibility and for all themes that would not include images or css-files.
3269 <br /><br />
3272 is enabled, you can select your favorite theme on the main page. Your
3273 selected theme will be stored in a cookie.<br /><br /></p>
3275 <p> To create a theme:</p>
3277 <ul><li>make a new subdirectory (for example "your_theme_name") under
3279 (by default <tt>themes</tt>)</li>
3280 <li>copy the files and directories from "original" to
3281 "your_theme_name"</li>
3282 <li>edit the css-files in "your_theme_name/css"</li>
3283 <li>put your new images in "your_theme_name/img"</li>
3284 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3285 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3286 contain your chosen theme name, that will be visible in user interface</li>
3287 <li>make a new screenshot of your theme and save it under
3288 "your_theme_name/screen.png"</li>
3289 </ul>
3291 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3292 theme verbose name, theme generation and theme version. These versions and
3293 generations are enumerated from 1 and do not have any direct dependence on
3294 phpMyAdmin version. Themes within same generation should be backwards
3295 compatible - theme with version 2 should work in phpMyAdmin requiring
3296 version 1. Themes with different generation are incompatible.</p>
3298 <p> If you do not want to use your own symbols and buttons, remove the
3299 directory "img" in "your_theme_name". phpMyAdmin will
3300 use the default icons and buttons (from the system-theme "original").
3301 </p>
3305 what can I do?</a></h4>
3307 <p> Here are a few points to check:</p>
3309 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3311 directive empty. See also
3313 </li>
3314 <li>Maybe you have a broken PHP installation or you need to upgrade
3315 your Zend Optimizer. See
3317 http://bugs.php.net/bug.php?id=31134</a>.
3318 </li>
3319 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3320 set to the default (200) or another low value, you could get this
3321 error if your table has a high number of columns. Adjust this setting
3322 accordingly. (Thanks to Klaus Dorninger for the hint).
3323 </li>
3324 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3325 of ";" will cause this error. Replace it with "&;".
3326 </li>
3328 you might want to increase
3330 </li>
3331 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3332 </li>
3333 </ul>
3338 <p> To be able to see a progress bar during your uploads, your server must
3341 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3342 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3349 who logged out can not log in again in with the same nick.</a></h4>
3351 <p> This is related to the authentication mechanism (protocol) used by
3352 phpMyAdmin. To bypass this problem: just close all the opened
3353 browser windows and then go back to phpMyAdmin. You should be able to
3354 log in again.</p>
3358 limit error or a time limit error.</a></h4>
3360 <p> Compressed dumps are built in memory and because of this are limited to
3361 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3362 using
3364 (enabled by default). Zip exports can not be handled this way, so if you need
3365 Zip files for larger dump, you have to use another way.</p>
3369 when I rename a table or a column.</a></h4>
3371 <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>
3375 bundled with the MySQL server distribution.</a></h4>
3377 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3379 <pre>
3380 -- MySQL dump 8.22
3381 --
3382 -- Host: localhost Database: database
3383 ---------------------------------------------------------
3384 -- Server version 3.23.54
3385 </pre>
3387 <p> The invalid part of the code is the horizontal line made of dashes that
3388 appears once in every dump created with mysqldump. If you want to run your
3389 dump you have to turn it into valid MySQL. This means, you have to add a
3390 whitespace after the first two dashes of the line or add a # before it:
3391 <br />
3392 <code>
3393 -- -------------------------------------------------------<br />
3394 </code>
3395 or<br />
3396 <code>
3397 #---------------------------------------------------------
3398 </code>
3399 </p>
3406 <p> Please note that you should not use the separating string multiple times
3407 without any characters between them, or at the beginning/end of your table
3408 name. If you have to, think about using another TableSeparator or disabling
3409 that feature</p>
3414 <p> In Relation view, being able to choose a table in another database,
3415 or having more than one index field in the foreign key.<br /><br/>
3416 In Query-by-example (Query), automatic generation of the query
3417 LEFT JOIN from the foreign table.<br /><br/>
3418 </p>
3422 I get series of errors like "Warning: unable to parse url". How
3423 can this be fixed?</a></h4>
3424 <p>
3425 Your table neither have a primary key nor an unique one, so we must use a
3426 long expression to identify this row. This causes problems to parse_url
3427 function. The workaround is to create a primary or unique key.
3428 <br />
3429 </p>
3433 a MIME-Transformation onto!</a></h4>
3435 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3436 nested forms can be put inside the table where phpMyAdmin displays the results.
3437 You can, however, use any form inside of a table if keep the parent
3438 form-container with the target to tbl_row_delete.php and just put your own
3439 input-elements inside. If you use a custom submit input field, the form will
3440 submit itself to the displaying page again, where you can validate the
3441 $HTTP_POST_VARS in a transformation.
3443 For a tutorial on how to effectively use transformations, see our
3445 on the official phpMyAdmin-homepage.</p>
3449 MySQL server</a></h4>
3451 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3454 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3455 the quote-character (") is interpreted as an identifier quote character and
3456 not as a string quote character, which makes many internal phpMyAdmin
3458 statements. There is no workaround to this behaviour. News to this item will
3459 be posted in Bug report
3460 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3461 </p>
3465 more that one column with the same value
3466 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3467 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3469 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3470 can use it for the Edit and Delete links.</p>
3475 <p> phpMyAdmin uses a quick method to get the row count, and this method
3476 only returns an approximate count in the case of InnoDB tables. See
3478 a way to modify those results, but
3479 this could have a serious impact on performance.</p>
3484 <p> The number of records in queries containing COUNT and GROUP BY is
3485 not correctly calculated. Also, sorting results of a query like
3490 containing an hyphen.
3491 </a></h4>
3492 <p>
3493 The tests I have made with current MySQL 4.1.11 API shows that the
3494 API does not accept this syntax for the USE command. Enclosing the
3495 db name with backquotes works. For further confusion, no backquotes
3496 are needed with command-line mysql.
3497 </p>
3500 <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>
3501 <p>
3502 This has been a known limitation of phpMyAdmin since the beginning and
3503 it's not likely to be solved in the future.
3504 </p>
3506 <!-- Begin: Excel import limitations -->
3509 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3510 <p>
3511 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target="_blank">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3512 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3513 <br /><br />
3514 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3515 </p>
3518 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3519 <p>
3520 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3521 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3522 </p>
3525 <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>
3526 <p>
3527 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3528 consider using a built-in type. These are almost always guarenteed to import correctly.
3529 </p>
3531 <!-- End: Excel import limitations -->
3532 <!-- Begin: CSV import limitations -->
3535 <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>
3536 <p>
3537 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.
3538 </p>
3540 <!-- End: CSV import limitations -->
3541 <!-- Begin: Import type-detection limitations -->
3544 <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>
3545 <p>
3546 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
3547 you will have to edit the structure to your liking post-import.
3548 <br /><br />
3549 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
3550 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.
3551 </p>
3553 <!-- End: Import type-detection limitations -->
3555 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3558 <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
3559 need to install it for each customer.
3560 </a></h4>
3561 <p>
3562 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3563 your users. The development of this feature was kindly sponsored by
3564 NetCologne GmbH.
3565 This requires a properly setup MySQL user management and phpMyAdmin
3566 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3568 </p>
3572 access.
3573 </a></h4>
3574 <p>
3575 This depends on your system.<br />
3576 If you're running a server which cannot be accessed by other people, it's
3577 sufficient to use the directory protection bundled with your webserver
3579 If other people have telnet access to your server, you should use
3580 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3581 <br /><br />
3582 Suggestions:
3583 </p>
3584 <ul>
3585 <li>
3587 </li>
3588 <li>
3589 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3590 is a user whose password is only known to you, and apache is the
3591 group under which Apache runs.
3592 </li>
3593 <li>
3594 You should use PHP safe mode, to protect from other users that try
3596 </li>
3597 </ul>
3602 </a></h4>
3603 <p>
3608 </p>
3611 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3612 authentication.
3613 </a></h4>
3617 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3618 and/or
3620 are wrong.</li>
3622 <li>You have already setup a security mechanism for the
3623 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3624 phpMyAdmin's authentication, so remove it.</li>
3625 </ul>
3632 and put the privileges you want. For example,
3634 would let a user create/manage his/her database(s).</p>
3639 <p> If you have existing rules from an old .htaccess file, you can take them
3642 be a major benefit here if your installation is suited to using it. Then
3643 you can just add those updated lines into the
3647 <p> If you want a pre-made sample, you can try this fragment. It stops the
3648 'root' user from logging in from any networks other than the private
3651 <pre>
3652 //block root from logging in except from the private networks
3653 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3654 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3655 'deny root from all',
3656 'allow root from localhost',
3660 );
3661 </pre>
3666 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3667 different than the one set in your
3669 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3670 while a domain name is defined in the config file.</p>
3675 <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>
3681 when trying to create a table with more than 14 fields.
3682 </a></h4>
3683 <p>
3684 We could reproduce this problem only under Win98/98SE. Testing under
3685 WinNT4 or Win2K, we could easily create more than 60 fields.
3686 <br />
3687 A workaround is to create a smaller number of fields, then come back to
3688 your table properties and add the other fields.
3689 </p>
3693 <p>
3694 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3695 with each script/website that use forms.<br />
3696 Upgrade or downgrade your Xitami server.
3697 </p>
3700 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3701 <p>
3702 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3703 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3704 don't seem to work.<br />
3706 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3707 the user's temporary directory, so they must be moved before closing
3708 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3711 </p>
3715 Explorer never stores the cookies.
3716 </a></h4>
3717 <p>
3718 MS Internet Explorer seems to be really buggy about cookies, at least till
3720 in this area!
3721 <br />
3722 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3723 work!
3724 </p>
3728 rows.
3729 </a></h4>
3730 <p>
3732 </p>
3735 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3736 when trying to modify a row in a table with many fields, or with a text field
3737 </a></h4>
3738 <p>
3739 Your table neither have a primary key nor an unique one, so we must use a
3740 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
3741 those browsers, and this not happen in Netscape, for example. The
3742 workaround is to create a primary or unique key, or use another browser.
3743 <br />
3744 </p>
3748 page.
3749 </a></h4>
3750 <p>
3751 Some browsers support right-clicking into the frame you want to refresh,
3752 just do this in the right frame.<br />
3753 </p>
3757 query box.
3758 </a></h4>
3759 <p>
3760 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3761 Mozilla versions.<br />
3762 </p>
3766 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3767 </a></h4>
3768 <p>
3769 This is a Mozilla bug (see bug #26882 at
3771 </p>
3776 </a></h4>
3777 <p>
3778 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3779 data in octet-stream mode. Since we can't detect the specific Netscape
3780 version, we cannot workaround this bug.
3781 </p>
3785 wrong.</a></h4>
3787 <p> Please ensure that you have set your browser's character set to the one of the
3788 language file you have selected on phpMyAdmin's start page.
3789 Alternatively, you can try the auto detection mode that is supported by the
3790 recent versions of the most browsers.</p>
3793 <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
3796 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3797 Netscape and Mozilla do not have this problem.</p>
3800 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3801 I cannot manage two servers: I log in to the first one, then the other one,
3802 but if I switch back to the first, I have to log in on each operation.</a></h4>
3808 but nothing happens after that, only a blank screen.</a></h4>
3819 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3824 address and you are starting
3826 containing a domain name, or the reverse situation.</li>
3827 <li>Security settings in IE and/or Microsoft Security Center are
3828 too high, thus blocking scripts execution.</li>
3829 <li>The Windows Firewall is blocking Apache and MySQL. You must
3833 </ul>
3836 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3837 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3838 installed in their Firefox is causing the problem.</p>
3842 clause is generated when I browse a table.</a></h4>
3843 <p> This happens only when both of these conditions are met: using the
3853 </a></h4>
3854 <p>
3855 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3856 specifying a wrong field-type.<br />
3857 Common errors include:
3858 </p>
3859 <ul>
3862 </ul>
3863 <p>
3864 Also, look at the syntax chapter in the MySQL manual to confirm that your
3865 syntax is correct.
3866 </p>
3870 phpMyAdmin generates only one index with those two fields.
3871 </a></h4>
3872 <p>
3873 This is the way to create a multi-fields
3874 index. If you want two indexes, create the first one when creating the
3875 table, save, then display the table properties and click the Index link to
3876 create the other index.
3877 </p>
3881 <p>
3882 Since version 2.2.3, you have a checkbox for each field that can be null.
3884 field's value. Since version 2.5.5, you have to use the checkbox to get
3886 a literal NULL in the field, and not a NULL value (this works in PHP4).
3887 </p>
3892 <p> Click on a database or table name in the left frame, the properties will be
3894 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3895 statements that can be used to recreate your database/table.
3896 <br /><br />
3898 transmit the resulting dump to your station. Depending on your PHP
3899 configuration, you will see options to compress the dump. See also the
3901 configuration variable.<br /><br />
3904 this document.</p>
3909 </a></h4>
3911 <p> Click on a database name in the left frame, the properties will be
3913 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3915 the path to your dump filename, or use the Browse button. Then click Go.
3916 <br /><br />
3918 that you upgrade to take advantage of the new features.
3919 <br /><br />
3921 in this document.
3922 </p>
3927 <p> Here is an example with the tables persons, towns and countries, all
3929 table, create it as explained in the configuration section. Then create the
3930 example tables:</p>
3932 <pre>
3933 CREATE TABLE REL_countries (
3934 country_code char(1) NOT NULL default '',
3935 description varchar(10) NOT NULL default '',
3936 PRIMARY KEY (country_code)
3937 ) TYPE=MyISAM;
3939 INSERT INTO REL_countries VALUES ('C', 'Canada');
3941 CREATE TABLE REL_persons (
3942 id tinyint(4) NOT NULL auto_increment,
3943 person_name varchar(32) NOT NULL default '',
3945 country_code char(1) NOT NULL default '',
3946 PRIMARY KEY (id)
3947 ) TYPE=MyISAM;
3949 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3950 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3952 CREATE TABLE REL_towns (
3954 description varchar(30) NOT NULL default '',
3955 PRIMARY KEY (town_code)
3956 ) TYPE=MyISAM;
3958 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3959 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3960 </pre>
3966 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3970 </ul>
3978 <li>In the fields row, choose persons.person_name and click the
3980 <li>Do the same for towns.description and countries.descriptions in the
3983 the correct joins have been generated</li>
3985 </ul>
3989 <p>
3990 Starting from the previous example, create the pma_table_info as explained
3991 in the configuration section, then browse your persons table,
3992 and move the mouse over a town code or country code.
3993 <br /><br />
3994 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3995 enables: drop-down list of possible values.
3996 </p>
3999 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
4000 <p>
4003 <br /><br />
4004 Then you need to think about your schema layout. Which tables will go on
4005 which pages?
4006 </p>
4007 <ul>
4013 page and click Go. If you like, you
4015 linked tables onto the new page.</li>
4016 <li>Select the name of the new page (making sure the Edit radio button
4017 is selected) and click Go.</li>
4019 Coordinates are relative; your diagram will
4020 be automatically scaled to fit the page. When initially placing tables
4021 on the page, just pick any coordinates -- say, 50x50. After clicking
4023 position the element correctly.</li>
4025 first be sure to click the Save
4026 button beneath the list of tables and coordinates, to save any changes
4027 you made there. Then scroll all the way down, select the
4029 you want, and click Go.</li>
4030 <li>Internet Explorer for Windows may suggest an incorrect filename when
4035 browsers on Windows, do not have this problem.</li>
4036 </ul>
4040 columns!</a></h4>
4042 <p> No, it's MySQL that is doing
4048 underscores in the database name?</a></h4>
4050 <p> If you do not put a backslash before the underscore, this is a wildcard
4053 john2db ...<br /><br />
4055 If you put a backslash before the underscore, it means that the database
4056 name will have a real underscore.</p>
4060 statistics pages?</a></h4>
4071 if it already exists during the import. It does NOT drop the table after
4072 your export, it only affects the import file.</li>
4074 Otherwise, you may get an error if the table name exists but has a
4075 different structure.</li>
4077 (if any) will be included in backup.</li>
4079 field and table names formed with special characters are protected.</li>
4081 types set in the pmadb in the dump as
4083 </li>
4084 </ul>
4089 command, for better documentation (but resulting file is bigger).</li>
4091 once the INSERT verb and the table name.</li>
4094 </li>
4096 more info is provided in the
4098 but basically with this selected, invalid values are adjusted and
4099 inserted rather than causing the entire statement to fail.</li>
4100 </ul>
4104 in its name.</a></h4>
4107 is the normal way to reference a database and table name. Worse, MySQL
4108 will usually let you create a database with a dot, but then you cannot
4109 work with it, nor delete it.</p>
4122 for usage.<br />
4123 On a more recent pear version, I had problems with the state of Net_DIME
4124 being beta, so this single command
4126 needed modules.<br />
4127 If you use the Validator, you should be aware that any
4129 submit will be stored anonymously (database/table/column names,
4130 strings, numbers replaced with generic values). The Mimer
4133 We utilize it as free SOAP service.</p>
4137 it, but MySQL says "BLOB column '...' used in key specification without
4140 <p> The right way to do this, is to create the field without any indexes,
4142 dialog. On this page, you will be able to choose your BLOB field, and
4143 set a size to the index, which is the condition to create an index on
4144 a BLOB field.</p>
4148 editing fields?</a></h4>
4150 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4151 with many editing fields (table structure changes, row editing, etc.)
4152 (must be enabled in configuration - see.
4154 You can also have a look at the directive
4156 ('vertical') and see if this eases up editing for you.</p>
4160 WTF is this feature then useful for?</a></h4>
4162 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4163 on them. Otherwise you could just put a comment on the field. Because entering
4164 your own mimetype will cause serious syntax checking issues and validation,
4165 this introduces a high-risk false-user-input situation. Instead you have to
4166 initialize mimetypes using functions or empty mimetype definitions.<br />
4167 Plus, you have a whole overview of available mimetypes. Who knows all those
4168 mimetypes by heart so he/she can enter it at will?</p>
4172 can't I see any bookmarks below the query box? What is this variable for?
4173 </a></h4>
4175 <p> Any query you have executed can be stored as a bookmark on the page where the
4176 results are displayed. You will find a button labeled 'Bookmark this query'
4177 just at the end of the page.<br />
4178 As soon as you have stored a bookmark, it is related to the database you run
4179 the query on. You can now access a bookmark dropdown on each page, the query
4180 box appears on for that database.<br /><br />
4182 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4186 aware of that you HAVE to create a valid query, otherwise your query won't be
4187 even able to be stored in the database.<br />
4189 for your query will remain the way it is, but will be stripped of the /**/
4190 chars. So you can use:<br /><br />
4194 which will be expanded to<br /><br />
4198 in your query, where VARIABLE is the string you entered in the input box. If
4199 an empty string is provided, no replacements are made.<br /><br />
4201 A more complex example. Say you have stored this query:<br /><br />
4203 <br /><br />
4206 the full query will be:<br /><br />
4209 <br /><br />
4213 spaces inserted there
4214 will be later also inserted as spaces in your query and may lead to unexpected
4215 results especially when
4217 Your initial query which is going to be stored as a bookmark has to yield at
4218 least one result row so
4219 you can store the bookmark. You may have that to work around using well
4223 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4224 include exported table?</a></h4>
4226 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4227 document should look like following one (assuming you have table
4230 <pre>
4231 \documentclass{article} % or any class you want
4232 \usepackage{longtable} % for displaying table
4233 \begin{document} % start of document
4234 \include{table} % including exported table
4235 \end{document} % end of document
4236 </pre>
4240 access them.
4241 </a></h4>
4244 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4245 enable users to see all the database names.
4248 So if your users do not need those privileges, you can remove them and their
4249 databases list will shorten.</p>
4253 possible values for a field, based on some foreign table?</a></h4>
4255 <p> You have to setup appropriate links between the tables, and also
4259 foreign table, a drop-down list of values will be available.
4260 You will see two lists of values, the first list containing the key
4261 and the display field, the second list containing the display field
4262 and the key. The reason for this is to be able to type the first
4263 letter of either the key or the display field.<br /><br />
4265 For 100 values or more, a distinct window will appear, to browse foreign
4266 key values and choose one. To change the default limit of 100, see
4267 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4271 automatically when entering Browse mode for a table?</a></h4>
4273 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4274 </p>
4278 Excel files, how can I enable that?</a></h4>
4280 <p> Current version does support direct export to Microsoft Excel and Word
4281 versions 2000 and newer. If you need export older versions, you can use
4283 which works out of the box or you can
4285 several problems, most important are limitation of cell content to 255
4286 chars and no support for charsets, so think carefully whether you want to
4287 enable this.</b>. For enabling this you need to set
4291 module Spreadsheet_Excel_Writer into php include path. The
4292 installation can be done by following command:</p>
4294 <pre>
4295 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
4296 </pre>
4298 <p> First part of switches set we want to install beta version of that module
4299 (no stable version available yet) and then we tell pear we want to satisfy
4300 dependencies.</p>
4302 <p> If you are running in PHP safe mode, you will have to set
4305 modules are located, for example:</p>
4307 <pre>
4308 safe_mode_include_dir = /usr/local/lib/php
4309 </pre>
4313 <pre>
4314 cd phpMyAdmin
4315 mkdir tmp
4316 chmod o+rwx tmp
4317 </pre>
4321 what happens to my column comments stored in pmadb?</a></h4>
4323 <p> Automatic migration of a table's pmadb-style column comments to the native
4324 ones is done whenever you enter Structure page for this table.</p>
4329 <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>
4331 <ol>
4332 <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>
4333 <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>
4334 <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>
4335 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4336 <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>
4337 <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>
4338 </ol>
4345 <p> Our Bug Tracker is located at
4347 under the Bugs section.<br /><br />
4349 But please first discuss your bug with other users:<br />
4355 existing language, where do I start?</a></h4>
4357 <p> Always use the current SVN version of your language file.
4359 don't know how to get the SVN version, please ask one of the developers.
4360 <br />
4361 Please note that we try not to use HTML entities like &eacute; in
4362 the translations, since we define the right character set in the file.
4363 With HTML entities, the text on JavaScript messages would not
4364 display correctly.
4365 However there are some entities that need to be there, for quotes
4366 ,non-breakable spaces, ampersands, less than, greater than.<br />
4367 You can then put your translations, as a zip file to avoid losing special
4368 characters, on the sourceforge.net translation tracker.<br />
4369 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4370 list, because this is where we ask for translations of new messages.</p>
4374 phpMyAdmin. How should I proceed?</a></h4>
4379 <tt>git clone
4380 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4381 </li>
4383 <li>generate patch with your changes:
4385 </li>
4388 tracker of the phpMyAdmin project</a>.
4389 </li>
4390 </ol>
4392 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4394 <p> Write access to the repository is granted only to experienced developers who
4395 have already contributed something useful to phpMyAdmin.<br />
4401 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4403 <p> Please refer to
4404 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4405 </p>
4410 <p> If you use Apache web server, phpMyAdmin exports information about
4411 authentication to Apache environment and it can be used in Apache logs.
4412 Currently there are two variables available:
4413 </p>
4414 <dl>
4416 <dd>User name of currently active user (he does not have to be logged
4417 in).</dd>
4424 </dl>
4425 <p>
4427 </p>
4428 <pre>
4431 </pre>
4432 <p>
4433 You can then use any log analyzing tools to detect possible break-in
4434 attempts.
4435 </p>
4441 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4442 It allows you to connect to local as well as remote servers.This requires you to enter
4443 server host name, username, password, port and the name of the database. Therefore you can
4444 now synchronize your databases placed on the same server or some remote server.
4445 </p>
4447 <p>For more details see <a href="./documentation-gsoc/Synchronization_User_Manual.htm">How to synchronize</a>
4448 </p>
4450 <!-- DEVELOPERS -->
4453 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4454 great features have been written by other people and you too can help to
4455 make phpMyAdmin a useful tool.</p>
4457 <p> If you're planning to contribute source, please read the following
4458 information:</p>
4464 it free from other code.<br />
4465 Commonly used functions should be added to
4468 <li>Obviously, you're free to use whatever coding style you want. But
4469 please try to keep your code as simple as possible: beginners are
4470 using phpMyAdmin as an example application.<br />
4471 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4472 compliant on one hand, they fit the
4475 coding standards</a>
4476 on the other hand. Please pay attention to this.</li>
4477 <li>Please try to keep up the file-naming conventions. Table-related stuff
4480 <li>Please don't put message strings in your code, instead add the string
4485 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4486 better debug and profile their code.<br />
4487 Please see the
4489 options for more information.<br />
4490 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4491 lost during its re-entry into Earth's atmosphere and in memory of the
4492 brave men and women who gave their lives for the people of Earth.</li>
4493 </ul>
4497 <pre>
4508 </pre>
4510 <p>
4511 This program is free software; you can redistribute it and/or modify
4512 it under the terms of the GNU General Public License version 2,
4513 as published by the Free Software Foundation.
4514 </p>
4516 <p>
4517 This program is distributed in the hope that it will be useful,
4518 but WITHOUT ANY WARRANTY; without even the implied warranty of
4519 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4520 GNU General Public License for more details.
4521 </p>
4523 <p>
4524 You should have received a copy of the GNU General Public License
4525 along with this program; if not, write to the Free Software
4527 </p>
4529 <!-- CREDITS -->
4534 <ul>
4537 <ul>
4540 </ul></li>
4543 <ul>
4548 </ul></li>
4551 <ul>
4557 </ul></li>
4560 <ul>
4562 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4563 generate XHTML1.0 and CSS2 compliant codes</li>
4566 </ul></li>
4569 <ul>
4577 </ul></li>
4580 <ul>
4585 </ul></li>
4588 <ul>
4591 </ul></li>
4594 <ul>
4596 </ul></li>
4599 <ul>
4602 </ul></li>
4605 <ul>
4609 </ul></li>
4612 <ul>
4615 </ul></li>
4618 <ul>
4625 </ul></li>
4628 <ul>
4632 </ul></li>
4635 <ul>
4641 </ul></li>
4644 (http://sf.net/projects/phpmysqlformgen/)
4645 <ul>
4647 </ul></li>
4650 <ul>
4652 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4657 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4661 </ul></li>
4664 <ul>
4666 </ul></li>
4669 <ul>
4671 </ul></li>
4674 <ul>
4676 </ul></li>
4679 <ul>
4680 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4681 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4682 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4683 </ul></li>
4686 <ul>
4688 </ul></li>
4691 <ul>
4693 </ul></li>
4696 <ul>
4698 </ul></li>
4701 <ul>
4704 </ul></li>
4707 <ul>
4710 </ul></li>
4713 <ul>
4715 </ul></li>
4718 <ul>
4721 </ul></li>
4723 <li>Ivan A Kirillov
4724 <ul>
4726 </ul></li>
4729 <ul>
4731 </ul></li>
4734 <ul>
4736 </ul></li>
4739 <ul>
4741 </ul></li>
4744 <ul>
4746 </ul></li>
4749 <ul>
4751 </ul></li>
4754 <ul>
4756 </ul></li>
4758 </ul>
4760 <p>
4761 And also to the following people who have contributed minor changes,
4762 enhancements, bugfixes or support for a new language since version 2.1.0:
4763 </p>
4765 <p>
4766 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4767 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4768 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4769 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4771 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4772 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4773 Luís V., Martijn W. van der Lee,
4774 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4776 </p>
4781 <p>
4782 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4783 to create a web-based interface to MySQL using PHP3. Although I have not
4784 used any of his source-code, there are some concepts I've borrowed from
4785 him. phpMyAdmin was created because Peter told me he wasn't going to
4786 further develop his (great) tool.
4787 </p>
4788 <p>
4789 Thanks go to
4790 </p>
4791 <ul>
4793 code for the check when dropping a table or database. He also suggested
4794 that you should be able to specify the primary key on tbl_create.php3. To
4795 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4796 well as a bug-report. Plus many smaller improvements.
4797 </li>
4799 were introduced in 1.3.0 (including quite significant ones like the
4800 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4801 bug-fixes and help.
4802 </li>
4804 language-independent by outsourcing the strings to a separate file. He
4805 also contributed the French translation.
4806 </li>
4808 tbl_select.php3, a feature to display only some fields from a table.
4809 </li>
4811 functions in tbl_change.php3. He also added the
4813 </li>
4815 servers and is a regular contributor for bug-fixes.
4816 </li>
4818 features for 2.0.6.
4819 </li>
4820 </ul>
4821 <p>
4822 The following people have contributed minor changes, enhancements, bugfixes
4823 or support for a new language:
4824 </p>
4825 <p>
4826 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4827 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4828 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4829 G. Wieggers.
4830 </p>
4831 <p>
4832 And thanks to everyone else who sent me email with suggestions, bug-reports
4833 and or just some feedback.
4834 </p>
4840 <ul>
4842 - the default name of Apache's directory-level configuration file.</li>
4846 - a software application that enables a user to display and interact with
4847 text, images, and other information typically located on a web page at a
4848 website on the World Wide Web.</li>
4850 - a free software/open source data compression algorithm and program
4851 developed by Julian Seward.</li>
4853 - an important World Wide Web technology that enables a client web browser
4854 to request data from a program executed on the Web server.</li>
4856 - a log or record of changes made to a project.</li>
4858 - a computer system that accesses a (remote) service on another computer
4859 by some kind of network.</li>
4861 - a set of data values of a particular simple type, one for each row of
4862 the table.</li>
4864 - a packet of information sent by a server to a World Wide Web browser
4865 and then sent back by the browser each time it accesses that server.</li>
4867 - Comma-separated values</li>
4870 - an organized collection of data.</li>
4873 - a PHP module that extends PHP with additional functionality.</li>
4875 - a list of commonly asked question and there answers.</li>
4877 - one part of divided data/columns.</li>
4879 - a field or group of fields in a database record that point to a key
4880 field or group of fields forming a key of another database record in some
4881 (usually different) table.</li>
4883 - the free PDF library</li>
4885 GD Graphics Library</a> - a library by Thomas Boutell and others for
4886 dynamically manipulating images.</li>
4889 - gzip is short for GNU zip, a GNU free software file compression
4890 program.</li>
4892 - any machine connected to a computer network, a node that has a hostname.</li>
4894 - the unique name by which a network attached device is known on a network.</li>
4896 (HyperText Transfer Protocol)</a>
4897 - the primary method used to transfer or convey information on the World
4898 Wide Web.</li>
4901 additional security measures.</li>
4902 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4903 - a set of Internet-based services for servers using Microsoft Windows.</li>
4905 - a feature that allows quick access to the rows in a table.</li>
4907 - a data-oriented protocol used by source and destination hosts for
4908 communicating data across a packet-switched internetwork.</li>
4910 - a unique number that devices use in order to identify and communicate
4911 with each other on a network utilizing the Internet Protocol standard.</li>
4913 (Internet Server Application Programming Interface)</a>
4914 - the API of Internet Information Services (IIS).</li>
4916 - a business or organization that offers users access to the Internet and related services.</li>
4918 - a most commonly used standard method of lossy compression for
4919 photographic images.</li>
4925 - line of personal computers is designed, developed, manufactured, and
4926 marketed by Apple Computer.</li>
4927 <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>
4928 - the operating system which is included with all currently shipping Apple
4929 Macintosh computers in the consumer and professional markets.</li>
4931 - a cryptographic library.</li>
4933 - the MCrypt PHP extension.</li>
4934 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4935 - an Internet Standard for the format of e-mail.</li>
4937 - some sort of extension for the Apache Webserver.</li>
4939 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4940 Management System (DBMS).</li>
4942 - the improved MySQL client PHP extension.</li>
4944 - the MySQL client PHP extension.</li>
4946 - open standard for office documents.</li>
4947 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4948 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4950 (Portable Document Format)</a>
4951 - a file format developed by Adobe Systems for representing two
4952 dimensional documents in a device independent and resolution independent
4953 format.</li>
4955 - the PHP Extension and Application Repository.</li>
4957 - the perl-compatible regular expression functions for PHP</li>
4959 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4960 programming language used mainly for developing server-side applications
4961 and dynamic web content, and more recently, a broader range of software
4962 applications.</li>
4964 - a connection through which data is sent and received.</li>
4966 - Request for Comments (RFC) documents are a series of memoranda
4967 encompassing new research, innovations, and methodologies applicable to
4968 Internet technologies.</li>
4972 - represents a single, implicitly structured data item in a table.</li>
4974 - a computer system that provides services to other computing
4975 systems over a network.</li>
4976 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4977 - handlers for different table types</li>
4979 - a form of inter-process communication.</li>
4981 Sockets Layer)</a>
4982 - a cryptographic protocol which provides secure communication on the Internet.</li>
4984 - Structured Query Language</li>
4986 - a set of data elements (cells) that is organized, defined and stored as
4987 horizontal rows and vertical columns where each item can be uniquely
4988 identified by a label or key or by it?s position in relation to other items.</li>
4991 - a type of archive file format: the Tape ARchive format.</li>
4993 - one of the core protocols of the Internet protocol suite.</li>
4997 - a sequence of characters, conforming to a standardized format, that is
4998 used for referring to resources, such as documents and images on the
4999 Internet, by their location.</li>
5001 - A computer (program) that is responsible for accepting HTTP requests
5002 from clients and serving them Web pages.</li>
5004 - a W3C-recommended general-purpose markup language for creating
5005 special-purpose markup languages, capable of describing many different
5006 kinds of data.</li>
5008 - a popular data compression and archival format.</li>
5010 - an open-source, cross-platform data compression library by Jean-loup
5011 Gailly and Mark Adler.</li>
5012 </ul>
5013 </div>
5016 <li>Copyright © 2003 - 2009 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5019 <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>
5020 </ul>
5022 </body>
5023 </html>