| blob | 0b3bd922c5cb64fdeff43106e1e810b27fd4b135 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <head>
14 </head>
18 <h1>
20 3.5.0-dev
21 Documentation
22 </h1>
23 </div>
25 <!-- TOP MENU -->
34 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
39 </ul>
44 phpMyAdmin homepage</a></li>
46 SourceForge phpMyAdmin project page</a></li>
48 Official phpMyAdmin wiki</a></li>
49 <li>Local documents:
52 </ul>
53 </li>
54 </ul>
56 <!-- REQUIREMENTS -->
63 , the Standard PHP Library (SPL) extension and JSON support.
64 </li>
67 currently the default), you should install the mbstring and ctype
68 extensions.
69 </li>
70 <li>You need GD2 support in PHP to display inline
72 original aspect ratio</li>
78 load pages significantly slower.
79 </li>
82 <li>To support BLOB streaming, see PHP and MySQL requirements
85 </ul>
86 </li>
89 </ul>
91 <!-- INTRODUCTION -->
94 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
95 a single database. To accomplish the latter you'll need a properly set up
96 MySQL user who can read/write only the desired database. It's up to you to
97 look up the appropriate part in the MySQL manual.
98 </p>
103 <li>create, copy, drop, rename and alter databases, tables, columns and
104 indexes</li>
105 <li>maintenance server, databases and tables, with proposals on server
106 configuration</li>
107 <li>execute, edit and bookmark any
109 batch-queries</li>
112 </li>
119 OpenDocument Text and Spreadsheet,
121 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
122 </li>
123 <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>
127 <li>using Query-by-example (QBE), create complex queries automatically
128 connecting required tables</li>
130 your Database layout</li>
132 <li>transform stored data into any format using a set of predefined
133 functions, like displaying BLOB-data as image or download-link
134 </li>
142 <li>communicate in <a href="http://www.phpmyadmin.net/home_page/translations.php">62 different languages</a>
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>
346 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
347 that you may need special (administrator) privileges to create the database
348 and tables, and that the script may need some tuning, depending on the
349 database name.</p>
354 section</a>. You will also need to have a controluser with the proper rights
361 unpacked one. Configuration files from old versions may
362 require some tweaking as some options have been changed or removed; in
364 so you better remove it from your file and just use the default one.
366 statement that you might find near the end of your configuration file.</p>
370 is version-specific.</p>
373 version 5.x or newer and if you use the phpMyAdmin configuration storage,
374 you should run the SQL script found in
381 where you want to give users access to their own database and don't want
382 them to play around with others.<br />
383 Nevertheless be aware that MS Internet Explorer seems to be really buggy
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>
443 configuration storage</a> be set up).
444 <br /></li>
447 on a set of particular databases. Normally you shouldn't give global
448 privileges to an ordinary user, unless you understand the impact of those
449 privileges (for example, you are creating a superuser).<br />
453 <pre>
454 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
455 </pre>
457 What the user may now do is controlled entirely by the MySQL user
458 management system.<br />
460 authentication mode, you don't need to fill the user/password fields
462 array.</li>
463 </ul>
468 method and allows you to log in as any valid MySQL user.</li>
469 <li>Is supported with most PHP configurations. For
482 mode.</li>
483 </ul>
487 <ul><li>You can use this method as a replacement for the
489 (for example, if you're running
491 <li>Obviously, the user must enable cookies in the browser, but this is
492 now a requirement for all authentication modes.</li>
493 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
494 with the same username.</li>
495 <li>If you want to log in to arbitrary server see
500 not required.</li>
501 </ul>
505 <ul><li>This mode is a convenient way of using credentials from another
506 application to authenticate to phpMyAdmin.</li>
507 <li>The other application has to store login information into
508 session data.</li>
510 section.</li>
511 </ul>
514 <ul><li>This mode is the less secure one because it requires you to fill the
516 $cfg['Servers'][$i]['user']</a> and
518 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
519 can read your config.inc.php can discover your username and password).
520 <br />
527 is an entry explaining how to protect your configuration file.</li>
528 <li>For additional security in this mode, you may wish to consider the Host
529 authentication
531 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
533 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
534 directives.</li>
535 <li>Unlike cookie and http, does not require a user to log in when first
536 loading the phpMyAdmin site. This is by design but could allow any
537 user to access your installation. Use of some restriction method is
539 HTTP-AUTH directive or disallowing incoming HTTP requests at
540 one’s router or firewall will suffice (both of which
541 are beyond the scope of this manual but easily searchable with Google).</li>
542 </ul>
544 <p>
545 The Swekey is a low cost authentication USB key that can be used in
546 web applications.<br /><br />
547 When Swekey authentication is activated, phpMyAdmin requires the
548 users's Swekey to be plugged before entering the login page (currently
549 supported for cookie authentication mode only). Swekey Authentication is
550 disabled by default.<br /><br />
552 </p>
553 <pre>
554 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
555 </pre>
556 <p>
558 each user with their Swekey Id. It is important to place this file outside
559 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
561 users' information.<br /><br />
562 If you want to purchase a Swekey please visit
564 since this link provides funding for phpMyAdmin.
565 </p>
566 <!-- CONFIGURATION -->
570 users:</span> PHP does not seem to like
574 before saving a script you have modified.</p>
579 section to create one. This file only needs to contain the parameters you want to
580 change from their corresponding default value in
583 <p> The parameters which relate to design (like colors) are placed in
586 your site specific code to be included on start and end of each page.</p>
590 (with full path) to your phpMyAdmin installation's directory.
593 some web servers are case–sensitive.
596 Starting with version 2.3.0, it is advisable to try leaving this
597 blank. In most cases phpMyAdmin automatically detects the proper
598 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
599 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
600 A good test is to browse a table, edit a row and save it. There should
601 be an error message if phpMyAdmin is having trouble auto–detecting
602 the correct value. If you get an error that this must be set or if
603 the autodetect code fails to detect your path, please post a bug
604 report on our bug tracker so we can improve the code.</dd>
608 with master / foreign – tables (see
610 <br />
611 If you tried to set this up and it does not work for you, have a look on
613 use it. You will find a link that will analyze why those features have
614 been disabled.<br />
615 If you do not want to use those features set this variable to
619 <dd>A warning is displayed on the main page if Suhosin is detected.
621 from appearing.</dd>
624 <dd>Disable the default warning that is displayed if mcrypt is missing for
625 cookie authentication.
627 from appearing.</dd>
634 domain to call phpMyAdmin inside a frame, and is a potential security
635 hole allowing cross-frame scripting attacks.</dd>
639 algorithm to encrypt the password.<br />
641 passphrase of your choice. It will be used internally by the blowfish
642 algorithm: you won’t be prompted for this passphrase. There is
643 no maximum length for this secret.<br /><br />
645 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
646 makes a bit weaker security as this generated secret is stored in
647 session and furthermore it makes impossible to recall user name from
648 cookie.</dd>
652 MySQL servers. Therefore, a
654 been added which contains the login information for the different servers.
655 The first
657 contains the hostname of the first server, the second
659 the hostname of the second server, etc. In
661 server definition, however you can put as many as you need in
663 have to define all settings, just those you need to change).</dd>
667 $i-th MySQL-server. E.g. localhost.</dd>
672 ignores this port number and connects with the socket, so if you want
673 to connect to a port different from the default port, use
676 </dd>
680 To determine the correct socket, check your MySQL configuration or, using the
682 Among the resulting information displayed will be the socket used.</dd>
685 <dd>Whether to enable SSL for connection to MySQL server.
686 </dd>
689 <dd>What type connection to use with the MySQL server. Your options are
691 is nearly guaranteed to be available on all MySQL servers, while
692 sockets are not supported on some platforms.<br /><br />
694 To use the socket mode, your MySQL server must be on the same machine
695 as the Web server.</dd>
698 <dd>What php MySQL extension to use for the connection. Valid options are:
699 <br /><br />
702 The classic MySQL extension. This is the recommended and default
703 method at this time.<br /><br />
706 The improved MySQL extension. This extension became available
707 with php 5.0.0 and is the recommended way to connect to a server
711 <dd>Whether to use a compressed protocol for the MySQL server connection
712 or not (experimental).<br />
718 </dt>
720 all relational features (see
722 and, for a MySQL server running with
725 authentication mode).<br /><br />
728 cookie authentication modes (or 'config'
729 authentication mode since phpMyAdmin 2.2.1), you need to supply the
734 This account is used to check what databases the user will see at
735 login.<br />
739 In phpMyAdmin versions before 2.2.5, those were called
743 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
744 <dd>Whether config or cookie or
746 should be used for this server.
748 is the plain old way: username and password are stored in
750 <li>'cookie' authentication mode
752 2.2.3 allows you to log in as any valid MySQL user with the
753 help of cookies. Username and password are stored in
754 cookies during the session and password is deleted when it
755 ends. This can also allow you to log in in arbitrary server if
756 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
757 </li>
758 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
759 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
760 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
761 <li>'signon' authentication mode
763 as introduced in 2.10.0 allows you to log in from prepared PHP
764 session data or using supplied PHP script. This is useful for implementing single signon
765 from another application.
771 You need to
777 </ul>
780 for more information.
781 </dd>
783 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
784 </dt>
785 <dd>
786 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
787 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
788 specified in your configuration, a string combined of "phpMyAdmin " and either
791 </dd>
793 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
794 </dt>
795 <dd>
797 names for hardware authentication. Leave empty to deactivate this feature.
798 </dd>
802 </dt>
803 <dd>
804 When using auth_type = 'config', this is the user/password-pair
805 which phpMyAdmin will use to connect to the
806 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
807 cookie authentication is used and should be empty.</dd>
809 <span
811 </dt>
812 <dd>
813 Allow attempt to log in without password when a login with password
814 fails. This can be used together with http authentication, when
815 authentication is done some other way and phpMyAdmin gets user name
816 from auth and uses empty password for connecting to MySQL. Password
817 login is still tried first, but as fallback, no password method is
818 tried.</dd>
821 </dt>
822 <dd>
823 If set to a (an array of) database name(s), only this (these) database(s)
824 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
825 database(s) name(s) may contain MySQL wildcards characters
829 This setting is an efficient way to lower the server load since the
830 latter does not need to send MySQL requests to build the available
832 privileges rules of the MySQL database server</span>. If set, it just
833 means only these databases will be displayed but
835 <br /><br />
837 An example of using more that one database:
839 <br /><br />
841 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
842 databases in the left frame, so that you can individually arrange your databases.<br />
843 If you want to have certain databases at the top, but don't care about the others, you do not
844 need to specify all other databases. Use:
846 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
847 order.</dd>
850 </dt>
851 <dd>Regular expression for hiding some databases from unprivileged users.
852 This only hides them
853 from listing, but a user is still able to access them (using, for example,
854 the SQL query area). To limit access, use the MySQL privilege system.
855 <br /><br />
860 More information on regular expressions can be found in the
862 PCRE pattern syntax</a> portion of the PHP reference manual.
863 </dd>
866 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
867 this string will be displayed instead of the hostname in the pull-down
868 menu on the main page. This can be useful if you want to show only
869 certain databases on your system, for example. For HTTP auth, all
870 non-US-ASCII characters will be stripped.</dd>
874 </dt>
875 <dd>The name of the database containing the phpMyAdmin configuration storage.
876 <br /><br />
879 section in this document to see the benefits of this feature,
880 and for a quick way of creating this database and the needed tables.
881 <br /><br />
883 If you are the only user of this phpMyAdmin installation, you can
884 use your current database to store those special tables; in this
885 case, just put your current database name in
887 set this parameter to the name of your central database containing
888 the phpMyAdmin configuration storage.</dd>
892 </dt>
894 useful for queries you often run.<br /><br />
896 To allow the usage of this functionality:
898 <li>enter the table name in
900 </ul>
901 </dd>
905 </dt>
907 which column is a key in another table (a foreign key). phpMyAdmin
908 currently uses this to
909 <ul><li>make clickable, when you browse the master table, the data values
910 that point to the foreign table;</li>
912 when browsing the master table, if you move the mouse to a column
913 containing a foreign key (use also the 'table_info' table);<br />
916 <li>in edit/insert mode, display a drop-down list of possible foreign
920 <li>display links on the table properties page, to check referential
921 integrity (display missing foreign keys) for each described key;
922 </li>
926 schema of your database (also uses the table_coords table).</li>
927 </ul>
929 The keys can be numeric or character.<br /><br />
931 To allow the usage of this functionality:
934 configuration storage</li>
935 <li>put the relation table name in
937 <li>now as normal user open phpMyAdmin and for each one of your
938 tables where you want to use this feature, click
940 columns.
941 </li>
942 </ul>
946 future development of the cross-db relations.
947 </dd>
951 </dt>
952 <dd>
953 Since release 2.3.0 you can describe, in a special 'table_info'
954 table, which column is to be displayed as a tool-tip when moving the
955 cursor over the corresponding key.<br />
956 This configuration variable will hold the name of this special
957 table. To allow the usage of this functionality:
959 <li>put the table name in
961 'pma_table_info')</li>
962 <li>then for each table where you want to use this feature,
964 to choose the column.</li>
965 </ul>
967 </dd>
971 </dt>
974 the relations between your tables. To do this it needs two tables
979 schema output).<br /><br />
983 To allow the usage of this functionality:
986 <li>put the correct table names in
989 </ul>
992 </dd>
996 </dt>
998 Since release 2.3.0 you can store comments to describe each column for
1000 <br /><br />
1002 Starting with release 2.5.0, comments are consequently used on the table
1003 property pages and table browse view, showing up as tool-tips above the
1004 column name (properties page) or embedded within the header of table in
1005 browse view. They can also be shown in a table dump. Please see the
1006 relevant configuration directives later on.<br /><br />
1008 Also new in release 2.5.0 is a MIME-transformation system which is also
1010 Transformations</a> for further information. To use the
1011 MIME-transformation system, your column_info table has to have the three
1012 new columns 'mimetype', 'transformation', 'transformation_options'.
1013 <br /><br />
1015 To allow the usage of this functionality:
1017 <li>put the table name in
1019 'pma_column_info')</li>
1022 <pre>
1023 ALTER TABLE `pma_column_comments`
1024 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1025 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1026 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1027 </pre>
1030 renamed from<br />
1033 </ul>
1034 </dd>
1038 </dt>
1041 all queries you entered manually into the phpMyAdmin interface. If you
1042 don't want to use a table-based history, you can use the JavaScript-based
1043 history. Using that, all your history items are deleted when closing the
1044 window.<br /><br />
1046 Using
1048 you can specify an amount of history items you want to have on hold. On
1049 every login, this list gets cut to the maximum amount.<br /><br />
1051 The query history is only available if JavaScript is enabled in your
1052 browser.<br /><br />
1054 To allow the usage of this functionality:
1058 (e.g. 'pma_history')
1059 </li>
1060 </ul>
1061 </dd>
1065 </dt>
1066 <dd>
1067 Since release 3.5.0 you can show recently used tables in the left navigation frame.
1068 It helps you to jump across table directly, without the need to select the database,
1069 and then select the table. Using
1071 you can configure the maximum number of recent tables shown. When you select a table
1072 from the list, it will jump to the page specified in
1073 <a href="#cfg_LeftDefaultTabTable" class="configrule">$cfg['LeftDefaultTabTable']</a>.<br/><br/>
1075 Without configuring the storage, you can still access the recently used tables,
1076 but it will disappear after you logout.<br/><br/>
1078 To allow the usage of this functionality persistently:
1080 <ul>
1083 </ul>
1084 </dd>
1088 </dt>
1089 <dd>
1090 Since release 3.5.0 phpMyAdmin can be configured to remember several things
1091 (table sorting
1093 , etc.) for browsing tables.
1094 Without configuring the storage, these features still can be used,
1095 but the values will disappear after you logout.<br/><br/>
1097 To allow the usage of these functionality persistently:
1099 <ul>
1101 <li>put the table name in <tt>$cfg['Servers'][$i]['table_uiprefs']</tt> (e.g. 'pma_table_uiprefs')</li>
1102 </ul>
1103 </dd>
1107 </dt>
1108 <dd>
1109 Since release 3.3.x a tracking mechanism is available.
1111 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1112 and data definition statements. After enabling it you can create versions of tables.
1113 <br/><br/>
1114 The creation of a version has two effects:
1116 <ul>
1118 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1119 </ul>
1121 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1122 For the report you can use filters, for example you can get a list of statements within a date range.
1123 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1124 In addition you can export the (filtered) report to a file or to a temporary database.
1125 <br/><br/>
1127 To allow the usage of this functionality:
1129 <ul>
1132 </ul>
1133 </dd>
1136 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1137 </dt>
1138 <dd>
1139 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1140 <br/><br/>
1141 If this is set to true and you create a table or view with
1143 <ul>
1146 </ul>
1148 and no version exists for it, the mechanism will
1149 create a version for you automatically.
1150 </dd>
1153 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1154 </dt>
1155 <dd>
1156 Defines the list of statements the auto-creation uses for new versions. Default value is
1157 <br/>
1159 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1160 CREATE INDEX,DROP INDEX,
1161 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1162 CREATE VIEW,ALTER VIEW,DROP VIEW,
1163 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1164 </dd>
1167 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1168 </dt>
1169 <dd>
1170 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1171 <br/><br/>
1172 </dd>
1176 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1177 </dt>
1178 <dd>
1179 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1180 <br/><br/>
1181 </dd>
1184 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1185 </dt>
1186 <dd>
1187 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1188 <br/><br/>
1189 </dd>
1193 </dt>
1194 <dd>
1195 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1196 and store them in the database.
1197 <br /><br />
1200 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1201 or, it is is unavailable, until the end of session.
1202 <br /><br />
1204 To allow the usage of this functionality:
1206 <ul>
1208 configuration storage</li>
1210 </ul>
1211 </dd>
1215 </dt>
1217 to visually manage the relations.
1218 <br /><br />
1220 To allow the usage of this functionality:
1223 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1224 </li>
1225 </ul>
1226 </dd>
1229 </dt>
1231 column_info table got enhanced with three new columns. If the above variable
1233 latest table structure available. If not, it will emit a warning to the
1234 superuser.<br /><br />
1236 You can disable this checking behavior by setting the variable to false,
1237 which should offer a performance increase.<br /><br />
1239 Recommended to set to FALSE, when you are sure, your table structure is
1240 up to date.</dd>
1242 boolean</dt>
1243 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1244 </dd>
1246 boolean</dt>
1247 <dd>Whether to allow logins without a password. The default
1249 to a MySQL server with was left with an empty password for root or
1250 on which an anonymous (blank) user is defined.
1251 </dd>
1254 </dt>
1256 authorization is disabled.<br /><br />
1259 all deny rules followed by allow rules. Access is allowed by default. Any
1260 client which does not match a Deny command or does match an Allow command
1261 will be allowed access to the server. <br /><br />
1264 applies all allow rules followed by deny rules. Access is denied by
1265 default. Any client which does not match an Allow directive or does
1266 match a Deny directive will be denied access to the server.<br /><br />
1268 If your rule order is set to 'explicit', authorization is
1269 performed in a similar fashion to rule order 'deny,allow', with the
1273 and was available in Apache by specifying allow and deny rules without
1274 setting any order.<br /><br />
1276 Please also see <a
1278 address behind proxies.
1279 </dd>
1281 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1282 </dt>
1283 <dd>The general format for the rules is as such:
1285 <pre>
1287 </pre>
1292 well (please note that those containing SERVER_ADDRESS might not be
1293 available on all webservers):
1294 <pre>
1300 </pre>
1302 Having an empty rule list is equivalent to either using
1308 following work:<br />
1310 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1311 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1312 But the following does not work:<br />
1315 Also IPv6 addresses are not supported.
1316 </dd>
1318 <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.
1319 </dd>
1320 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1322 DATABASES</tt> command used to fetch the name of available databases will
1323 probably be too slow, so it can be replaced by faster commands (see
1325 </dd>
1327 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1328 </dd>
1330 <dd>Name of PHP script to be sourced and executed to obtain
1331 login credentials. This is alternative approach to session based single
1332 signon. The script needs to provide function
1334 password, accepting single parameter of existing username (can be empty).
1336 </dd>
1337 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1338 <dd>Name of session which will be used for signon authentication method.
1340 this is session which phpMyAdmin uses internally. Takes effect only if
1342 is not configured.
1343 </dd>
1345 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1346 </dd>
1348 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1349 </dd>
1352 <dd>If you have more than one server configured, you can set
1354 that server when phpMyAdmin is started, or set it to 0 to be given a
1355 list of servers without logging in.<br />
1357 MUST be set to that server.</dd>
1360 <dd>Defines whether to refresh only parts of certain pages using Ajax
1361 techniques. Applies only where a non-Ajax behavior is possible;
1362 for example, the Designer feature is Ajax-only so this directive
1363 does not apply to it.</dd>
1366 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1367 page.</dd>
1370 <dd>The maximum number of database names to be displayed in the
1371 navigation frame and the database list.</dd>
1374 <dd>The maximum number of table names to be displayed in the
1375 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1376 when in Light mode.</dd>
1379 <dd>The maximum number of characters when a SQL query is displayed. The
1380 default limit of 1000 should be correct to avoid the display of tons
1381 of hexadecimal codes that represent BLOBs, but some users have real
1382 SQL queries that are longer than 1000 characters. Also, if a query's
1383 length exceeds this limit, this query is not saved in the history.</dd>
1386 <dd>Defines whether to use GZip output buffering for increased
1388 Set to true/false for enabling/disabling. When set to 'auto' (string),
1389 phpMyAdmin tries to enable output buffering and will automatically disable
1390 it if your browser has some problems with buffering. IE6 with a certain patch
1391 is known to cause data corruption when having enabled buffering.</dd>
1394 <dd>Whether persistent connections should be used or not (mysql_connect or
1395 mysql_pconnect).</dd>
1401 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1402 to zero, no time limit is imposed.<br />
1403 This setting is used while importing/exporting dump files and in the
1404 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1411 <dd>Set the number of bytes a script is allowed to allocate. If set
1412 to zero, no limit is imposed.<br />
1413 This setting is used while importing/exporting dump files and at some
1414 other places in phpMyAdmin so you definitely don't want to put here
1415 a too low value. It has no effect when PHP is running in safe mode.<br />
1416 You can also use any string as in php.ini, eg. '16M'. Ensure
1420 <dd>Mark used tables and make it possible to show databases with locked
1425 generated by phpMyAdmin should be displayed or not.</dd>
1428 <dd>Defines whether normal users (non-administrator) are allowed to
1429 delete their own database or not. If set as FALSE, the link "Drop
1431 mydatabase" will be rejected. Quite practical for
1433 customers.<br />
1434 Please note that this limitation of SQL queries is not as strict as
1435 when using MySQL privileges. This is due to nature of SQL queries
1436 which might be quite complicated. So this choice should be viewed as
1437 help to avoid accidental dropping rather than strict privilege
1438 limitation.</dd>
1442 displayed when you're about to lose data.</dd>
1445 <dd>Define whether the previous login should be recalled or not in cookie
1446 authentication mode.<br /><br />
1448 This is automatically disabled if you do not have configured
1450 </dd>
1453 <dd>Define how long is login cookie valid. Please note that php
1454 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1455 might limit session validity and if session is lost, login cookie is
1457 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1461 means that it will be kept for existing session. This is recommended
1462 for not trusted environments.</dd>
1465 <dd>If enabled (default), logout deletes cookies for all servers,
1466 otherwise only for current one. Setting this to false makes it easy to
1467 forget to log out from other server, when you are using more of
1468 them.</dd>
1474 <dd>Define whether phpMyAdmin will continue executing a multi-query
1475 statement if one of the queries fails. Default is to abort execution.</dd>
1478 <dd>Define whether phpMyAdmin will output the results of each query of a
1479 multi-query statement embedded into the
1484 <dd>If enabled, allows you to log in to arbitrary servers using cookie auth and permits to specify servers of your choice in the Synchronize dialog.
1485 <br /><br />
1488 MySQL servers behind the firewall where your
1490 </dd>
1499 <dd>Defines whether to use a select-based menu and display only the current
1500 tables in the left frame (smaller page). Only in Non-Lightmode you can
1501 use the feature to display nested folders using
1503 </dd>
1506 <dd>In light mode, defines whether to display the names of databases (in the
1507 selector) using a tree, see also
1509 </dd>
1512 string or array</dt>
1513 <dd>The string used to separate the parts of the database name when showing
1514 them in a tree. Alternatively you can specify more strings in an array
1515 and all of them will be used as a separator.</dd>
1518 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1519 This means if you have tables like 'first__second__third' this will be
1521 If set to FALSE or empty, the feature is disabled. NOTE: You should
1522 not use this separator at the beginning or end of a
1523 table name or multiple times after another without any other
1524 characters in between.</dd>
1527 <dd>Defines how many sublevels should be displayed when splitting
1528 up tables by the above separator.</dd>
1531 <dd>The maximum number of recently used tables shown in the left navigation
1535 <dd>Defines whether to display table comment as tool-tip in left frame or
1536 not.</dd>
1539 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1540 comment and the real name. That means that if you have a table called
1541 'user0001' and add the comment 'MyName' on it, you will see the name
1542 'MyName' used consequently in the left frame and the tool-tip shows
1543 the real name of the DB.</dd>
1546 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1548 When setting this to 'nested', the Alias of the Tablename is only used
1549 to split/nest the tables according to the
1551 directive. So only the folder is called like the Alias, the tablename itself
1552 stays the real tablename.</dd>
1555 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1558 <dd>Enter URL where logo in the navigation frame will point to.
1559 For use especially with self made theme which changes this.
1568 integer</dt>
1569 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1570 list of tables in the left frame.
1575 <dd>Defines whether or not to display a server choice at the top of the left frame.
1576 Defaults to FALSE.</dd>
1578 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1579 Defaults to FALSE (drop-down).</dd>
1581 <dd>Defines whether to display database choice in light navigation frame as links
1582 instead of in a drop-down. Defaults to 'auto' - on main page list is
1583 shown, when database is selected, only drop down is displayed.</dd>
1586 <dd>Defines the tab displayed by default when clicking the small
1587 icon next to each table name in the navigation panel. Possible
1593 <dd>Defines whether or not to display space usage and statistics about databases
1594 and tables.<br />
1595 Note that statistics requires at least MySQL 3.23.3 and that, at this
1596 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1599 <dd>Defines whether to display detailed server information on main page.
1600 You can additionally hide more information by using
1602 </dd>
1607 </dt>
1610 not at the starting main (right) frame. This setting
1611 does not check MySQL commands entered directly.<br /><br />
1613 Please note that to block the usage of phpinfo() in scripts, you
1620 hard coded password value in the configuration file, end users can't
1621 be allowed to change their passwords.</dd>
1624 <dd>Defines whether to suggest a database name on the
1628 <dd>Defines whether navigation bar buttons and the right panel top menu
1629 contain text or symbols only. A value of TRUE displays icons, FALSE
1630 displays text and 'both' displays both icons and text.</dd>
1633 <dd>Defines whether a user should be displayed a
1637 <dd>Number of rows displayed when browsing a result set. If the result set
1644 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1648 option is ticked by default.</dd>
1652 from editing when browsing a table's content. Valid values are:
1657 </ul>
1658 </dd>
1661 <dd>Defines whether or not MySQL functions fields should be initially
1662 displayed in edit/insert mode. Since version 2.10, the user can
1663 toggle this setting from the interface.
1664 </dd>
1667 <dd>Defines whether or not type fields should be initially
1668 displayed in edit/insert mode. The user can
1669 toggle this setting from the interface.
1670 </dd>
1673 <dd>Defines which type of editing controls should be used for CHAR and
1674 VARCHAR columns. Possible values are:
1675 <ul><li>input - this allows to limit size of text to size of columns in
1676 MySQL, but has problems with newlines in columns</li>
1677 <li>textarea - no problems with newlines in columns, but also no
1678 length limitations</li>
1679 </ul>
1680 Default is old behavior so input.</dd>
1686 <dd>If there are fewer items than this in the set of foreign keys, then a
1687 drop-down box of foreign keys is presented, in the style described by the
1689 setting.</dd>
1692 <dd>For the foreign key drop-down fields, there are several methods of
1693 display, offering both the key and value data. The contents of the
1694 array should be one or both of the following strings:
1700 </dt>
1701 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1702 creating a dump file</dd>
1705 </dt>
1706 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1707 compressed exports. This doesn't affect smaller dumps and allows users to
1708 create larger dumps that won't otherwise fit in memory due to php
1709 memory limit. Produced files contain more GZip/BZip2 headers, but all
1710 normal programs handle this correctly.</dd>
1714 mainframe.</dd>
1718 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1723 <dd>How many columns will be utilized to display the tables on the
1724 database property view? Default is 1 column. When setting this to a
1725 value larger than 1, the type of the database will be omitted for more
1726 display space.</dd>
1730 <dd>Defines the tab displayed by default on server view. Possible
1737 <dd>Defines the tab displayed by default on database view. Possible
1742 <dd>Defines the tab displayed by default on table view. Possible
1749 points to the MySQL documentation (type depends
1750 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1751 generated.<br />
1753 for more information about MySQL manuals and their types.</dd>
1756 <dd>Type of MySQL documentation:
1762 </ul>
1763 </dd>
1766 <dd>Defines the default language to use, if not browser-defined or
1767 user-defined.<br />
1768 The corresponding language file needs to be in
1770 </dd>
1773 <dd>Defines the default connection collation to use, if not
1774 user-defined.<br />
1780 The corresponding language file needs to be in
1782 </dd>
1785 <dd>Limit list of available languages to those matching the given regular
1786 expression. For example if you want only Czech and English, you should
1790 <dd>You can select here which functions will be used for character set
1791 conversion. Possible values are:
1792 <ul><li>auto - automatically use available one (first is tested
1793 iconv, then recode)</li>
1797 </ul>
1798 Default is auto.</dd>
1799 <dd>
1800 Enabled charset conversion activates a pull-down menu
1801 in the Export and Import pages, to choose the character set when
1802 exporting a file. The default value in this menu comes from
1804 </dd>
1807 <dd>Specify some parameters for iconv used in charset conversion. See
1810 used, so that invalid characters will be transliterated.</dd>
1813 <dd>Available character sets for MySQL conversion. You can add your own (any of
1814 supported by recode/iconv) or remove these which you don't use.
1815 Character sets will be shown in same order as here listed, so if you
1816 frequently use some of these move them to the top.</dd>
1821 default empty, you need to fill in some trusted proxy servers if you
1822 want to use rules for IP addresses behind proxy.<br /><br />
1824 The following example specifies that phpMyAdmin should trust a
1826 <pre>
1827 $cfg['TrustedProxies'] =
1829 </pre>
1830 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1831 client's IP address as usual.
1832 </dd>
1836 MIME transformations.<br />
1837 Possible values are:
1838 <ul><li>auto - automatically detect, this is a bit expensive
1840 according to your server real possibilities</li>
1843 </ul>
1844 Default is auto.
1845 </dd>
1848 <dd>
1849 We normally check the permissions on the configuration file to ensure
1850 it's not world writable. However, phpMyAdmin could be installed on
1851 a NTFS filesystem mounted on a non-Windows server, in which case the
1852 permissions seems wrong but in fact cannot be detected. In this case
1854 </dd>
1857 <dd>
1858 Limit for length of URL in links. When length would be above this limit, it
1859 is replaced by form with button.
1860 This is required as some web servers (IIS) have problems with long URLs.
1862 </dd>
1864 <dt
1866 <dd>
1867 In the database Structure page, it's possible to mark some tables then
1868 choose an operation like optimizing for many tables. This can slow down
1871 </dd>
1875 </dd>
1877 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1879 </dt>
1880 <dd>The background styles used for both the frames.
1883 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1885 <dd>The style used for the pointer in the navi frame.
1894 </dd>
1898 <dd>The style used for table headers. See
1903 </dd>
1907 </dd>
1909 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1911 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1913 </dt>
1915 The former feature highlights the row over which your mouse is passing
1916 and the latter lets you visually mark/unmark rows by clicking on
1917 them. Highlighting / marking a column is done by hovering over /
1918 clicking the column's header (outside of the text).<br />
1923 <dd>You put here a valid CSS font family value, for example
1928 <dd>You put here a valid CSS font family value, for example
1942 </dt>
1944 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1946 The Char* values are used for CHAR and VARCHAR editing (if configured
1950 </dt>
1954 </dt>
1955 <dd>Defines if the whole textarea of the query box will be selected on
1956 click.</dd>
1959 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1960 Can be turned off by a toggle button on the browse page.</dd>
1963 </dt>
1964 <dd>Defines the place where table row links (Edit, Inline edit, Copy,
1965 Delete) would be put when tables contents are displayed (you may
1966 have them displayed at the left side, right side, both sides or nowhere).
1972 Define which one is displayed by default. The first mode displays each
1973 row on a horizontal line, the second rotates the headers by 90
1974 degrees, so you can use descriptive headers even though columns only
1975 contain small values and still print them out. The vertical mode sorts
1976 each row on a vertical lineup.
1977 </dd>
1983 <dd>
1984 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1985 'css' the rotation of the header for horizontalflipped is done via
1986 CSS. The CSS transformation currently works only in Internet
1987 Explorer.If set to 'fake' PHP does the transformation for you, but of
1988 course this does not look as good as CSS. The 'auto' option enables
1989 CSS transformation when browser supports it and use PHP based one
1990 otherwise.
1991 </dd>
1995 string or integer</dt>
1996 <dd>When editing/creating new columns in a table all fields normally get
1997 lined up one field a line. (default: 'horizontal'). If you set this to
1998 'vertical' you can have each field lined up vertically beneath each
1999 other. You can save up a lot of place on the horizontal direction and
2000 no longer have to scroll. If you set this to integer, editing of fewer
2001 columns will appear in 'vertical' mode, while editing of more columns
2002 still in 'horizontal' mode. This way you can still effectively edit
2003 large number of columns, while having full view on few of them.</dd>
2007 </dt>
2009 display of column comments in Browse or Property display. In browse
2010 mode, the comments are shown inside the header. In property mode,
2011 comments are displayed using a CSS-formatted dashed-line below the
2012 name of the column. The comment is shown as a tool-tip for that column.
2013 </dd>
2025 <dd>Whether to display a link to validate a query in any SQL Query box.
2032 <dd>
2033 The name of the directory where
2035 uploaded by other means than phpMyAdmin (for example, ftp). Those files
2036 are available under a drop-down box when you click the database or
2037 table name, then the Import tab.
2038 <br /><br />
2040 If you want different directory for each user, %u will be replaced
2041 with username.<br /><br />
2045 compressed formats is enabled).<br /><br />
2047 This feature is useful when your file is too big to be uploaded via
2049 uploads are disabled in PHP.<br /><br />
2051 Please note that if PHP is running in safe mode, this directory must
2052 be owned by the same user as the owner of the phpMyAdmin scripts.
2053 <br /><br />
2057 alternatives.
2058 </dd>
2061 <dd>
2062 The name of the directory where dumps can be saved.<br /><br />
2064 If you want different directory for each user, %u will be replaced
2065 with username.<br /><br />
2067 Please note that the directory must exist and has to be writable for
2068 the user running webserver.<br /><br />
2070 Please note that if PHP is running in safe mode, this directory must
2071 be owned by the same user as the owner of the phpMyAdmin scripts.
2072 </dd>
2075 <dd>
2076 The name of the directory where temporary files can be stored.
2077 <br /><br />
2079 This is needed for native MS Excel export, see
2085 <br /><br />
2087 If the directory where phpMyAdmin is installed is subject to an
2089 temporary directory in some directory accessible by the web
2090 server. However for security reasons, this directory should be outside
2091 the tree published by webserver. If you cannot avoid having this
2092 directory published by webserver, place at least an empty
2094 possible.
2095 <br /><br />
2097 This directory should have as strict permissions as possible as the only
2098 user required to access this directory is the one who runs the
2099 webserver. If you have root privileges, simply make this user owner of
2100 this directory and make it accessible only by it:
2101 <br /><br />
2103 <pre>
2104 chown www-data:www-data tmp
2105 chmod 700 tmp
2106 </pre>
2108 If you cannot change owner of the directory, you can achieve a similar
2111 <pre>
2112 chmod 700 tmp
2113 setfacl -m "g:www-data:rwx" tmp
2114 setfacl -d -m "g:www-data:rwx" tmp
2115 </pre>
2117 If neither of above works for you, you can still make the directory
2119 system reading and writing data in this directory.
2120 </dd>
2123 <dd>
2124 In this array are defined default parameters for export, names of
2125 items are similar to texts seen on export page, so you can easily
2126 identify what they mean.
2127 </dd>
2130 <dd>
2131 Defines how the export form is displayed when it loads. Valid values are:
2132 <ul>
2135 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2136 </ul>
2137 </dd>
2140 <dd>
2141 In this array are defined default parameters for import, names of
2142 items are similar to texts seen on import page, so you can easily
2143 identify what they mean.
2144 </dd>
2147 <dd>
2148 Defines whether or not type display direction option is shown
2149 when browsing a table.
2150 </dd>
2153 <dd>
2154 Repeat the headers every X cells, or 0 to deactivate.
2155 </dd>
2163 </dt>
2164 <dd>
2165 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2166 or icon is always displayed on the left panel. If JavaScript is enabled in
2167 your browser, a click on this opens a distinct query window, which is
2168 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2169 changes to display a query box.<br /><br />
2171 The size of this query window can be customized with
2173 - both integers for the size in pixels. Note that normally, those
2175 theme you are using.<br /><br />
2179 opens the query window and puts the current query
2180 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2181 query in the right panel's query box.
2182 <br /><br />
2183 The usage of the JavaScript query window is recommended if you have a
2184 JavaScript enabled browser. Basic functions are used to exchange quite
2185 a few variables, so most 4th generation browsers should be capable to
2186 use that feature. It currently is only tested with Internet Explorer 6
2187 and Mozilla 1.x.
2188 <br /><br />
2190 to a table, which has to be created by you (see <a
2192 all your queries will be appended to the form, but only as long as
2193 your window is opened they remain saved.
2194 <br /><br />
2195 When using the JavaScript based query window, it will always get
2196 updated when you click on a new table/db to browse and will focus if
2197 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2198 the query window by checking the box "Do not overwrite this query from
2199 outside the window" below the query textarea. Then you can browse
2200 tables/databases in the background without losing the contents of the
2201 textarea, so this is especially useful when composing a query with
2202 tables you first have to look in. The checkbox will get automatically
2203 checked whenever you change the contents of the textarea. Please
2204 uncheck the button whenever you definitely want the query window to
2205 get updated even though you have made alterations.
2206 <br /><br />
2209 <br /><br />
2210 The query window also has a custom tabbed look to group the features.
2212 default tab to be used when opening the query window. It can be set to
2213 either 'sql', 'files', 'history' or 'full'.</dd>
2219 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2221 If the approximate row count as returned by
2224 count will be used.
2225 </dd>
2227 <dd>For VIEWs, since obtaining the exact count could have an
2228 impact on performance, this value is the maximum to be displayed, using
2230 any row counting.
2231 </dd>
2234 <dd>Sorts database and table names according to natural order (for example,
2235 t1, t2, t10). Currently implemented in the left panel (Light mode)
2236 and in Database view, for the table list.</dd>
2245 that users can't set through user preferences. For possible values, refer
2252 <dd>Allows you to specify window's title bar. You can use
2254 </dd>
2264 </dd>
2267 <dd>If theme manager is active, use this as the path of the subdirectory
2268 containing all the themes.</dd>
2282 </dt>
2283 <dd>Default queries that will be displayed in query boxes when user didn't
2284 specify any. You can use standard
2286 </dd>
2289 <dd>
2290 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
2291 default we use HTML to format the query, but you can disable this by
2293 </dd>
2296 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2297 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2298 query inside a bracket is indented. By changing
2301 specifies the units of the indent amount that you specified. This is
2302 used via stylesheets.</dd>
2305 <dd>This array is used to define the colours for each type of element of
2306 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2308 If you specify an empty string for the color of a class, it is ignored
2309 in creating the stylesheet.
2310 You should not alter the class names, only the colour strings.<br />
2331 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2335 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2336 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2337 </ul>
2338 </dd>
2342 <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,
2343 as originally published on
2345 <br />
2346 For help in setting up your system to use the service, see the
2348 </dd>
2352 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2353 and any password, so we use those by default. Instead, if
2354 you have an account with them, you can put your login details
2355 here, and it will be used in place of the anonymous login.</dd>
2356 </dl>
2357 </dd>
2360 <dd><b>DEVELOPERS ONLY!</b></dd>
2363 <dd><b>DEVELOPERS ONLY!</b><br />
2364 Enable logging queries and execution times to be displayed in the bottom
2365 of main page (right frame).</dd>
2368 <dd>All possible types of a MySQL column. In most cases you don't need to
2369 edit this.</dd>
2372 <dd>Possible attributes for columns. In most cases you don't need to edit
2373 this.</dd>
2376 <dd>A list of functions MySQL supports. In most cases you don't need to
2377 edit this.</dd>
2380 <dd>Mapping of column types to meta types used for preferring displayed
2381 functions. In most cases you don't need to edit this.</dd>
2384 <dd>Functions preferred for column meta types as defined in
2385 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2386 to edit this.</dd>
2389 <dd>Functions selected by default when inserting/changing row, Functions
2390 are defined for meta types from
2392 <code>first_timestamp</code>, which is used for first timestamp column
2393 in table.</dd>
2395 </dl>
2397 <!-- TRANSFORMATIONS -->
2403 </ol>
2407 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2409 section</a> on how to do so.</p>
2411 <p> You can apply different transformations to the contents of each column. The
2412 transformation will take the content of each column and transform it with
2413 certain rules defined in the selected transformation.</p>
2415 <p> Say you have a column 'filename' which contains a filename. Normally you would
2416 see in phpMyAdmin only this filename. Using transformations you can transform
2417 that filename into a HTML link, so you can click inside of the phpMyAdmin
2418 structure on the column's link and will see the file displayed in a new browser
2419 window. Using transformation options you can also specify strings to
2420 append/prepend to a string or the format you want the output stored in.</p>
2422 <p> For a general overview of all available transformations and their options,
2423 you can consult your
2424 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2425 installation.</p>
2427 <p> For a tutorial on how to effectively use transformations, see our
2429 the official phpMyAdmin homepage.</p>
2433 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2434 clicking on the 'Structure' link for a table). There click on
2435 "Change" (or change icon) and there you will see three new
2436 fields at
2437 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2438 'Transformation options'.</p>
2440 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2441 that corresponds to the column's contents. Please note that
2442 transformations are inactive as long as no MIME-type is selected.</li>
2444 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2445 hopefully growing amount of pre-defined transformations. See below for information on
2446 how to build your own transformation.<br />
2448 There are global transformations and mimetype-bound transformations. Global transformations
2449 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2450 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2451 transformations which operate on the main mimetype (like 'image'), which will most likely
2452 take the subtype into regard, and those who only operate on a
2453 specific subtype (like 'image/jpeg').<br />
2455 You can use transformations on mimetypes for which the function was not defined for. There
2456 is no security check for you selected the right transformation, so take care of what the
2457 output will be like.</li>
2459 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2460 transform-function specific options here. Usually the transforms can operate with default
2461 options, but it is generally a good idea to look up the overview to see which options are
2462 necessary.<br />
2464 Much like the ENUM/SET-Fields, you have to split up several options using the format
2465 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2466 parsed as an array, leaving the first value the first element in the array, and so
2467 forth.<br />
2469 If you want to specify a MIME character set you can define it in the transformation_options.
2470 You have to put that outside of the pre-defined options of the specific mime-transform,
2472 for which you can specify 2 options and you want to append a character set, enter "'first
2473 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2475 </ul>
2479 <p> All mimetypes and their transformations are defined through single files in
2480 the directory 'libraries/transformations/'.</p>
2482 <p> They are stored in files to ease up customization and easy adding of new
2483 transformations.</p>
2485 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2486 always work. It makes no sense to apply a transformation to a mimetype the
2487 transform-function doesn't know to handle.</p>
2489 <p> One can, however, use empty mime-types and global transformations which should work
2490 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2491 for, but pay attention to option usage as well as what the transformation does to your
2492 column.</p>
2494 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2495 any other transform function and provides some basic functions.</p>
2497 <p> There are 5 possible file names:</p>
2499 <ol><li>A mimetype+subtype transform:<br /><br />
2501 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2503 Please not that mimetype and subtype are separated via '_', which shall
2504 not be contained in their names. The transform function/filename may
2505 contain only characters which cause no problems in the file system as
2506 well as the PHP function naming convention.<br /><br />
2508 The transform function will the be called
2509 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2511 <b>Example:</b><br /><br />
2513 <tt>text_html__formatted.inc.php</tt><br />
2514 <tt>PMA_transform_text_html__formatted()</tt></li>
2516 <li>A mimetype (w/o subtype) transform:<br /><br />
2518 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2520 Please note that there are no single '_' characters.
2521 The transform function/filename may contain only characters which cause
2522 no problems in the file system as well as the PHP function naming
2523 convention.<br /><br />
2525 The transform function will the be called
2526 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2528 <b>Example:</b><br /><br />
2530 <tt>text__formatted.inc.php</tt><br />
2531 <tt>PMA_transform_text__formatted()</tt></li>
2533 <li>A mimetype+subtype without specific transform function<br /><br />
2535 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2537 Please note that there are no '__' characters in the filename. Do not
2538 use special characters in the filename causing problems with the file
2539 system.<br /><br />
2541 No transformation function is defined in the file itself.<br /><br />
2543 <b>Example:</b><br /><br />
2545 <tt>text_plain.inc.php</tt><br />
2546 (No function)</li>
2548 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2550 <tt>[mimetype].inc.php</tt><br /><br />
2552 Please note that there are no '_' characters in the filename. Do not use
2553 special characters in the filename causing problems with the file system.
2554 <br /><br />
2556 No transformation function is defined in the file itself.<br /><br />
2558 <b>Example:</b><br /><br />
2560 <tt>text.inc.php</tt><br />
2561 (No function)</li>
2563 <li>A global transform function with no specific mimetype<br /><br />
2565 <tt>global__[transform].inc.php</tt><br /><br />
2567 The transform function will the be called
2568 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2570 <b>Example:</b><br /><br />
2572 <tt>global__formatted</tt><br />
2573 <tt>PMA_transform_global__formatted()</tt></li>
2574 </ol>
2576 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2577 transform function.</p>
2579 <p> All filenames containing no '__' in themselves are not shown as valid transform
2580 functions in the dropdown.</p>
2582 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2583 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2584 without a transform function.</p>
2586 <p> To create a new transform function please see
2587 <tt>libraries/transformations/template_generator.sh</tt>.
2588 To create a new, empty mimetype please see
2589 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2591 <p> A transform function always gets passed three variables:</p>
2593 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2594 you want to transform.</li>
2595 <li><b>$options</b> - Contains any user-passed options to a transform function
2596 as an array.</li>
2597 <li><b>$meta</b> - Contains an object with information about your column.
2598 The data is drawn from the output of the
2600 function. This means, all object properties described on the
2602 available in this variable and can be used to transform a column accordingly
2603 to unsigned/zerofill/not_null/... properties.<br />
2604 The $meta->mimetype variable contains the original MIME-type of the
2605 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2606 </ol>
2608 <p> Additionally you should also provide additional function to provide
2609 information about the transformation to the user. This function should
2610 have same name as transformation function just with appended
2611 <code>_info</code> suffix. This function accepts no parameters and returns
2612 array with information about the transformation. Currently following keys
2613 can be used:
2614 </p>
2615 <dl>
2616 <dt><code>info</code></dt>
2617 <dd>Long description of the transformation.</dd>
2618 </dl>
2620 <!-- FAQ -->
2627 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2632 </ol>
2634 <p> Please have a look at our
2636 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2637 features and or interface.</p>
2643 action is required or phpMyAdmin sends a blank page or a page full of
2644 cryptic characters to my browser, what can I do?</a></h4>
2647 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2648 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2649 configuration file.<br /></p>
2654 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2655 See also the
2657 entry about PHP bugs with output buffering.<br />
2658 If your server keeps crashing, please ask for help in the various Apache
2659 support groups.</p>
2668 application misbehaved by not returning a complete set of
2670 </h4>
2672 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2673 Have a look at the last message in this
2675 official PHP bug database.</p>
2680 and/or many error messages with the
2683 <p> This is a known problem with the PHP
2685 filter: it's not so stable. Please use instead the cookie authentication mode.
2686 </p>
2691 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2692 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2693 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2694 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2695 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2700 work.</a></h4>
2702 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2703 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2704 or not, and so on). So, you must have Zlib/Bzip2
2705 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2709 an error about safe mode being in effect.</a></h4>
2711 <p> Your uploaded file is saved by PHP in the "upload dir", as
2712 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2713 the system default is <i>/tmp</i>).<br />
2714 We recommend the following setup for Apache servers running in safe mode,
2715 to enable uploads of files while being reasonably secure:</p>
2717 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2718 <li>give ownership to the Apache server's user.group:
2719 <tt>chown apache.apache /tmp/php</tt></li>
2720 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2721 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2722 <li>restart Apache</li>
2723 </ul>
2730 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2731 I'm using the Apache server.</a></h4>
2733 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2734 your <i>httpd.conf</i>:</p>
2738 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2742 uploading a file from the query box.</a></h4>
2744 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2745 restrictions. However you need to create temporary directory and
2747 The uploaded files will be moved there, and after execution of your
2753 <p> The MySQL manual explains how to
2755 reset the permissions</a>.</p>
2765 </h4>
2767 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2768 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2769 names to align with current standards.</p>
2774 </h4>
2776 <p> Starting with version 2.7.0, the import engine has been re–written and these
2777 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2778 to take advantage of the new import features.</p>
2780 <p> The first things to check (or ask your host provider to check) are the
2781 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2782 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2783 All of these three settings limit the maximum size of data that can be
2784 submitted and handled by PHP. One user also said that post_max_size
2785 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2787 There exist several workarounds if your upload is too big or your
2788 hosting provider is unwilling to change the settings:</p>
2791 feature. This allows one to
2792 upload a file to the server via scp, ftp, or your favorite file transfer
2793 method. PhpMyAdmin is then able to import the files from the temporary
2795 section</a> of this document.</li>
2797 BigDump</a>) to split the files before uploading. We cannot support this
2798 or any third party applications, but are aware of users having success
2799 with it.</li>
2800 <li>If you have shell (command line) access, use MySQL to import the files
2801 directly. You can do this by issuing the "source" command from
2802 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2803 </ul>
2807 support?</a></h4>
2809 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2810 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2811 connect to your MySQL server using PHP's classic
2814 is available in php 5.0. The latter one should be used unless you have a
2815 good reason not to do so.<br />
2816 When compiling PHP, we strongly recommend that you manually link the MySQL
2817 extension of your choice to a MySQL client library of at least the same
2818 minor version since the one that is bundled with some PHP distributions is
2821 MariaDB is also supported (versions 5.1 and 5.2 were tested).
2822 </p>
2826 message, "Client does not support authentication protocol requested
2827 by server; consider upgrading MySQL client"</a></h5>
2829 <p> You tried to access MySQL with an old MySQL client library. The version of
2830 your MySQL client library can be checked in your phpinfo() output.
2831 In general, it should have at least the same minor version as your server
2835 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2836 changed the authentication hash and your PHP is trying to use the old method.
2838 with the proper client library to match your MySQL installation. Your
2839 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2840 More information (and several workarounds) are located in the
2842 </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 column 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>
2905 and I get problems, such as undefined variables when I run a
2908 <p> A tip from Jose Fandos: put a comment on the following two lines
2909 in httpd.conf, like this:</p>
2911 <pre>
2912 # mod_gzip_item_include file \.php$
2914 </pre>
2916 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2917 PHP scripts. Of course you have to restart Apache.</p>
2922 I get the error "No input file specified" when trying to
2923 run phpMyAdmin.</a></h4>
2925 <p> This is a permission problem. Right-click on the phpmyadmin folder
2926 and choose properties. Under the tab Security, click on "Add"
2927 and select the user "IUSR_machine" from the list. Now set his
2928 permissions and it should work.</p>
2932 db_structure.php with plenty of tables).</a></h4>
2935 GZIP output buffering is enabled. If you turn off it (by
2937 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2938 PHP 5.0.0.</p>
2942 message 'Errorcode: 13'. What does this mean?</a></h4>
2944 <p> This can happen due to a MySQL bug when having database / table names with
2945 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2946 To fix this, turn off this directive, convert all database and table names
2947 to lower case and turn it on again. Alternatively, there's a bug-fix
2948 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2952 and the columns are duplicated.</a></h4>
2954 <p> It is possible to configure Apache in such a way that PHP has problems
2955 interpreting .php files.</p>
2957 <p> The problems occur when two different (and conflicting) set of directives
2958 are used:</p>
2960 <pre>
2961 SetOutputFilter PHP
2962 SetInputFilter PHP
2963 </pre>
2965 <p> and</p>
2967 <pre>AddType application/x-httpd-php .php</pre>
2969 <p> In the case we saw, one set of directives was in
2970 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2971 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2972 The recommended way is with <tt>AddType</tt>, so just comment out
2973 the first set of lines and restart Apache:</p>
2975 <pre>
2976 #SetOutputFilter PHP
2977 #SetInputFilter PHP
2978 </pre>
2983 <p> This problem is known to happen when the server is running Turck MMCache
2984 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2989 <p>Yes.</p>
2990 <p>
2991 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
2992 is still maintained.
2993 </p>
2996 <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>
2998 <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>
3001 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3002 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3003 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3004 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3005 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3006 enabled.) Click <tt>OK</tt>.</li>
3007 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3008 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3009 </ol>
3013 PHP 5.0.4 on 64-bit systems?</a></h4>
3015 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3016 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3022 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
3023 the order of the server paragraph in <tt>config.inc.php</tt>.
3024 Table and script parts are optional. If you want
3025 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3026 some configuration. Following lines apply only for <a
3028 that you have enabled some features within global configuration. You need
3029 <code>Options FollowSymLinks</code> and <code>AllowOverride
3030 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3031 you need mod_rewrite to be enabled. Then you just need to create following
3032 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3033 (don't forget to change directory name inside of it):</p>
3035 <pre>
3036 RewriteEngine On
3037 RewriteBase /path_to_phpMyAdmin
3038 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3039 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3040 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3041 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3042 </pre>
3045 <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>
3047 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3048 following rewrite rule:</p>
3050 <pre>
3051 RewriteEngine On
3052 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3053 </pre>
3057 </h4>
3058 <p>
3059 There can be many explanations to this and a look at your server's
3060 error log file might give a clue.
3061 </p>
3065 password encryption in cookie auth doesn't work.</a></h4>
3067 <p> If your cluster consist of different architectures, PHP code used for
3068 encryption/decryption won't work correct. This is caused by use of
3069 pack/unpack functions in code. Only solution is to use mcrypt extension
3070 which works fine in this case.</p>
3075 <p> Yes but the default configuration values of Suhosin are known to cause
3076 problems with some operations, for example editing a table with many
3077 columns and no primary key or with textual primary key.
3078 </p>
3079 <p>
3080 Suhosin configuration might lead to malfunction in some cases and it can
3081 not be fully avoided as phpMyAdmin is kind of application which needs to
3082 transfer big amounts of columns in single HTTP request, what is something
3083 what Suhosin tries to prevent. Generally all
3084 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3085 <code>suhosin.get.*</code> directives can have negative effect on
3086 phpMyAdmin usability. You can always find in your error logs which limit
3087 did cause dropping of variable, so you can diagnose the problem and adjust
3088 matching configuration variable.
3089 </p>
3090 <p>
3091 The default values for most Suhosin configuration options will work in most
3092 scenarios, however you might want to adjust at least following parameters:
3093 </p>
3095 <ul>
3096 <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>
3097 <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>
3098 <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>
3099 <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>
3100 <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>
3101 <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>
3102 <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>
3103 <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>
3104 </ul>
3106 <p>
3108 <tt>SuhosinDisableWarning</tt> directive</a>.
3109 </p>
3113 but then my connection is redirected back to http. What can cause this
3114 behavior?</a></h4>
3116 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3117 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>
3120 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3122 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3123 Example from the Apache 2.2 documentation:</p>
3124 <pre>
3125 ProxyPass /mirror/foo/ http://backend.example.com/
3126 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3127 ProxyPassReverseCookieDomain backend.example.com public.example.com
3128 ProxyPassReverseCookiePath / /mirror/foo/
3129 </pre>
3131 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3132 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3133 This is not specific to phpmyadmin, it's just the behavior of Apache.
3134 </p>
3136 <pre>
3137 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3138 ProxyPassReverse /mirror/foo/
3139 http://backend.example.com/%7Euser/phpmyadmin
3140 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3141 </pre>
3143 <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>
3144 for more details.</p>
3148 privileges, I get an error about an unknown column.</a></h4>
3150 <p> The MySQL server's privilege tables are not up to date, you need to run
3151 the <tt>mysql_upgrade</tt> command on the server.</p>
3158 headers already sent by ..." is displayed, what's the problem?</a></h4>
3160 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3161 (I.E. no blank lines, no spaces, no characters...) neither before the
3162 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3163 tag at the end. We also got a report from a user under IIS, that used
3164 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3165 contained an end-of-line character (hex 0A) at the end; removing this character
3166 cleared his errors.</p>
3171 <p> Either there is an error with your PHP setup or your username/password is
3172 wrong. Try to make a small script which uses mysql_connect and see if it
3173 works. If it doesn't, it may be you haven't even compiled MySQL support
3174 into PHP.</p>
3178 connect to local MySQL server through socket '/tmp/mysql.sock'
3179 (111) ..." is displayed. What can I do?</a></h4>
3181 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3183 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3184 In your <i>php.ini</i> you will find a line</p>
3186 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3188 <p> change it to</p>
3190 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3192 <p> Then restart apache and it will work.</p>
3194 <p> Here is a fix suggested by Brad Ummer:</p>
3196 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3197 To do this, telnet to your server and go to the MySQL bin directory. In
3198 this directory there should be a file named <i>mysqladmin</i>. Type
3199 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3200 info about your MySQL server, including the socket
3201 (<i>/tmp/mysql.sock</i>, for example).</li>
3202 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3203 phpMyAdmin, you need to complete the socket information in the
3204 <i>config.inc.php</i>.<br />
3205 For example:
3207 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3208 <br /><br />
3210 Please also make sure that the permissions of this file allow to be readable
3211 by your webserver (i.e. '0755').</li>
3212 </ul>
3214 <p> Have also a look at the
3216 corresponding section of the MySQL documentation</a>.</p>
3220 what can I do?</a></h4>
3223 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3224 sometime.<br />
3225 Also have a look at your PHP version number: if it contains "4.0b..."
3226 it means you're running a beta version of PHP. That's not a so good idea,
3227 please upgrade to a plain revision.</p>
3231 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3232 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3234 <p> Check the value you set for the
3236 directive in the phpMyAdmin configuration file.</p>
3240 password: YES)"-error when trying to access a MySQL-Server on a
3241 host which is port-forwarded for my localhost.</a></h4>
3243 <p> When you are using a port on your localhost, which you redirect via
3244 port-forwarding to another host, MySQL is not resolving the localhost
3245 as expected.<br />
3246 Erik Wasser explains: The solution is: if your host is "localhost"
3247 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3248 connection for speeding up things. And that doesn't work in this configuration
3249 with port forwarding.<br />
3255 <p> Themes are configured with
3259 <br />
3261 should not delete the directory "original" or its underlying
3262 structure, because this is the system theme used by phpMyAdmin.
3263 "original" contains all images and styles, for backwards
3264 compatibility and for all themes that would not include images or css-files.
3265 <br /><br />
3268 is enabled, you can select your favorite theme on the main page. Your
3269 selected theme will be stored in a cookie.<br /><br /></p>
3271 <p> To create a theme:</p>
3273 <ul><li>make a new subdirectory (for example "your_theme_name") under
3275 (by default <tt>themes</tt>)</li>
3276 <li>copy the files and directories from "original" to
3277 "your_theme_name"</li>
3278 <li>edit the css-files in "your_theme_name/css"</li>
3279 <li>put your new images in "your_theme_name/img"</li>
3280 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3281 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3282 contain your chosen theme name, that will be visible in user interface</li>
3283 <li>make a new screenshot of your theme and save it under
3284 "your_theme_name/screen.png"</li>
3285 </ul>
3287 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3288 theme verbose name, theme generation and theme version. These versions and
3289 generations are enumerated from 1 and do not have any direct dependence on
3290 phpMyAdmin version. Themes within same generation should be backwards
3291 compatible - theme with version 2 should work in phpMyAdmin requiring
3292 version 1. Themes with different generation are incompatible.</p>
3294 <p> If you do not want to use your own symbols and buttons, remove the
3295 directory "img" in "your_theme_name". phpMyAdmin will
3296 use the default icons and buttons (from the system-theme "original").
3297 </p>
3301 what can I do?</a></h4>
3303 <p> Here are a few points to check:</p>
3305 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3307 directive empty. See also
3309 </li>
3310 <li>Maybe you have a broken PHP installation or you need to upgrade
3311 your Zend Optimizer. See
3313 http://bugs.php.net/bug.php?id=31134</a>.
3314 </li>
3315 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3316 set to the default (200) or another low value, you could get this
3317 error if your table has a high number of columns. Adjust this setting
3318 accordingly. (Thanks to Klaus Dorninger for the hint).
3319 </li>
3320 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3321 of ";" will cause this error. Replace it with "&;".
3322 </li>
3324 you might want to increase
3326 </li>
3327 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3328 </li>
3329 </ul>
3334 <p> To be able to see a progress bar during your uploads, your server must
3337 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3338 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3345 who logged out can not log in again in with the same nick.</a></h4>
3347 <p> This is related to the authentication mechanism (protocol) used by
3348 phpMyAdmin. To bypass this problem: just close all the opened
3349 browser windows and then go back to phpMyAdmin. You should be able to
3350 log in again.</p>
3354 limit error or a time limit error.</a></h4>
3356 <p> Compressed dumps are built in memory and because of this are limited to
3357 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3358 using
3360 (enabled by default). Zip exports can not be handled this way, so if you need
3361 Zip files for larger dump, you have to use another way.</p>
3365 when I rename a table or a column.</a></h4>
3367 <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>
3371 bundled with the MySQL server distribution.</a></h4>
3373 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3375 <pre>
3376 -- MySQL dump 8.22
3377 --
3378 -- Host: localhost Database: database
3379 ---------------------------------------------------------
3380 -- Server version 3.23.54
3381 </pre>
3383 <p> The invalid part of the code is the horizontal line made of dashes that
3384 appears once in every dump created with mysqldump. If you want to run your
3385 dump you have to turn it into valid MySQL. This means, you have to add a
3386 whitespace after the first two dashes of the line or add a # before it:
3387 <br />
3388 <code>
3389 -- -------------------------------------------------------<br />
3390 </code>
3391 or<br />
3392 <code>
3393 #---------------------------------------------------------
3394 </code>
3395 </p>
3402 <p> Please note that you should not use the separating string multiple times
3403 without any characters between them, or at the beginning/end of your table
3404 name. If you have to, think about using another TableSeparator or disabling
3405 that feature</p>
3410 <p> In Relation view, being able to choose a table in another database,
3411 or having more than one index column in the foreign key.<br /><br/>
3412 In Query-by-example (Query), automatic generation of the query
3413 LEFT JOIN from the foreign table.<br /><br/>
3414 </p>
3418 I get series of errors like "Warning: unable to parse url". How
3419 can this be fixed?</a></h4>
3420 <p>
3421 Your table neither have a primary key nor an unique one, so we must use a
3422 long expression to identify this row. This causes problems to parse_url
3423 function. The workaround is to create a primary or unique key.
3424 <br />
3425 </p>
3429 a MIME-Transformation onto!</a></h4>
3431 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3432 nested forms can be put inside the table where phpMyAdmin displays the results.
3433 You can, however, use any form inside of a table if keep the parent
3434 form-container with the target to tbl_row_delete.php and just put your own
3435 input-elements inside. If you use a custom submit input field, the form will
3436 submit itself to the displaying page again, where you can validate the
3437 $HTTP_POST_VARS in a transformation.
3439 For a tutorial on how to effectively use transformations, see our
3441 on the official phpMyAdmin-homepage.</p>
3445 MySQL server</a></h4>
3447 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3450 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3451 the quote-character (") is interpreted as an identifier quote character and
3452 not as a string quote character, which makes many internal phpMyAdmin
3454 statements. There is no workaround to this behaviour. News to this item will
3455 be posted in Bug report
3456 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3457 </p>
3461 more that one column with the same value
3462 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3463 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3465 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3466 can use it for the Edit and Delete links.</p>
3471 <p> phpMyAdmin uses a quick method to get the row count, and this method
3472 only returns an approximate count in the case of InnoDB tables. See
3474 a way to modify those results, but
3475 this could have a serious impact on performance.</p>
3482 containing an hyphen.
3483 </a></h4>
3484 <p>
3485 The tests I have made with MySQL 5.1.49 shows that the
3486 API does not accept this syntax for the USE command.
3487 </p>
3490 <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>
3491 <p>
3492 This has been a known limitation of phpMyAdmin since the beginning and
3493 it's not likely to be solved in the future.
3494 </p>
3496 <!-- Begin: Excel import limitations -->
3499 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3500 <p>
3501 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3502 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3503 <br /><br />
3504 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3505 </p>
3508 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3509 <p>
3510 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3511 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3512 </p>
3515 <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>
3516 <p>
3517 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3518 consider using a built-in type. These are almost always guarenteed to import correctly.
3519 </p>
3521 <!-- End: Excel import limitations -->
3522 <!-- Begin: CSV import limitations -->
3525 <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>
3526 <p>
3527 There is no reliable way to differentiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3528 </p>
3530 <!-- End: CSV import limitations -->
3531 <!-- Begin: Import type-detection limitations -->
3534 <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>
3535 <p>
3536 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
3537 you will have to edit the structure to your liking post-import.
3538 <br /><br />
3539 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
3540 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.
3541 </p>
3543 <!-- End: Import type-detection limitations -->
3545 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3548 <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
3549 need to install it for each customer.
3550 </a></h4>
3551 <p>
3552 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3553 your users. The development of this feature was kindly sponsored by
3554 NetCologne GmbH.
3555 This requires a properly setup MySQL user management and phpMyAdmin
3556 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3558 </p>
3562 access.
3563 </a></h4>
3564 <p>
3565 This depends on your system.<br />
3566 If you're running a server which cannot be accessed by other people, it's
3567 sufficient to use the directory protection bundled with your webserver
3569 If other people have telnet access to your server, you should use
3570 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3571 <br /><br />
3572 Suggestions:
3573 </p>
3574 <ul>
3575 <li>
3577 </li>
3578 <li>
3579 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3580 is a user whose password is only known to you, and apache is the
3581 group under which Apache runs.
3582 </li>
3583 <li>
3584 You should use PHP safe mode, to protect from other users that try
3586 </li>
3587 </ul>
3592 </a></h4>
3593 <p>
3598 </p>
3601 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3602 authentication.
3603 </a></h4>
3607 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3608 and/or
3610 are wrong.</li>
3612 <li>You have already setup a security mechanism for the
3613 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3614 phpMyAdmin's authentication, so remove it.</li>
3615 </ul>
3622 and put the privileges you want. For example,
3624 would let a user create/manage his/her database(s).</p>
3629 <p> If you have existing rules from an old .htaccess file, you can take them
3632 be a major benefit here if your installation is suited to using it. Then
3633 you can just add those updated lines into the
3637 <p> If you want a pre-made sample, you can try this fragment. It stops the
3638 'root' user from logging in from any networks other than the private
3641 <pre>
3642 //block root from logging in except from the private networks
3643 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3644 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3645 'deny root from all',
3646 'allow root from localhost',
3650 );
3651 </pre>
3656 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3657 different than the one set in your
3659 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3660 while a domain name is defined in the config file.</p>
3665 <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>
3671 when trying to create a table with more than 14 columns.
3672 </a></h4>
3673 <p>
3674 We could reproduce this problem only under Win98/98SE. Testing under
3675 WinNT4 or Win2K, we could easily create more than 60 columns.
3676 <br />
3677 A workaround is to create a smaller number of columns, then come back to
3678 your table properties and add the other columns.
3679 </p>
3683 <p>
3684 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3685 with each script/website that use forms.<br />
3686 Upgrade or downgrade your Xitami server.
3687 </p>
3690 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3691 <p>
3692 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3693 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3694 don't seem to work.<br />
3696 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3697 the user's temporary directory, so they must be moved before closing
3698 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3701 </p>
3705 Explorer never stores the cookies.
3706 </a></h4>
3707 <p>
3708 MS Internet Explorer seems to be really buggy about cookies, at least till
3709 version 6.
3710 </p>
3714 rows.
3715 </a></h4>
3716 <p>
3718 </p>
3721 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3722 when trying to modify a row in a table with many columns, or with a text
3723 column
3724 </a></h4>
3725 <p>
3726 Your table neither have a primary key nor an unique one, so we must use a
3727 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
3728 those browsers, and this not happen in Netscape, for example. The
3729 workaround is to create a primary or unique key, or use another browser.
3730 <br />
3731 </p>
3735 page.
3736 </a></h4>
3737 <p>
3738 Some browsers support right-clicking into the frame you want to refresh,
3739 just do this in the right frame.<br />
3740 </p>
3744 query box.
3745 </a></h4>
3746 <p>
3747 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3748 Mozilla versions.<br />
3749 </p>
3753 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3754 </a></h4>
3755 <p>
3756 This is a Mozilla bug (see bug #26882 at
3758 </p>
3763 </a></h4>
3764 <p>
3765 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3766 data in octet-stream mode. Since we can't detect the specific Netscape
3767 version, we cannot workaround this bug.
3768 </p>
3772 wrong.</a></h4>
3774 <p> Please ensure that you have set your browser's character set to the one of the
3775 language file you have selected on phpMyAdmin's start page.
3776 Alternatively, you can try the auto detection mode that is supported by the
3777 recent versions of the most browsers.</p>
3780 <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
3783 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3784 Netscape and Mozilla do not have this problem.</p>
3787 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3788 I cannot manage two servers: I log in to the first one, then the other one,
3789 but if I switch back to the first, I have to log in on each operation.</a></h4>
3795 but nothing happens after that, only a blank screen.</a></h4>
3806 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3811 address and you are starting
3813 containing a domain name, or the reverse situation.</li>
3814 <li>Security settings in IE and/or Microsoft Security Center are
3815 too high, thus blocking scripts execution.</li>
3816 <li>The Windows Firewall is blocking Apache and MySQL. You must
3820 </ul>
3823 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3824 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3825 installed in their Firefox is causing the problem.</p>
3829 clause is generated when I browse a table.</a></h4>
3830 <p> This happens only when both of these conditions are met: using the
3840 </a></h4>
3841 <p>
3842 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3843 specifying a wrong column-type.<br />
3844 Common errors include:
3845 </p>
3846 <ul>
3849 </ul>
3850 <p>
3851 Also, look at the syntax chapter in the MySQL manual to confirm that your
3852 syntax is correct.
3853 </p>
3857 columns and
3858 phpMyAdmin generates only one index with those two columns.
3859 </a></h4>
3860 <p>
3861 This is the way to create a multi-columns
3862 index. If you want two indexes, create the first one when creating the
3863 table, save, then display the table properties and click the Index link to
3864 create the other index.
3865 </p>
3869 <p>
3870 Since version 2.2.3, you have a checkbox for each column that can be null.
3872 column's value. Since version 2.5.5, you have to use the checkbox to get
3874 a literal NULL in the column, and not a NULL value (this works in PHP4).
3875 </p>
3880 <p> Click on a database or table name in the left frame, the properties will be
3882 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3883 statements that can be used to recreate your database/table.
3884 <br /><br />
3886 transmit the resulting dump to your station. Depending on your PHP
3887 configuration, you will see options to compress the dump. See also the
3889 configuration variable.<br /><br />
3892 this document.</p>
3897 </a></h4>
3899 <p> Click on a database name in the left frame, the properties will be
3901 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3903 the path to your dump filename, or use the Browse button. Then click Go.
3904 <br /><br />
3906 that you upgrade to take advantage of the new features.
3907 <br /><br />
3909 in this document.
3910 </p>
3915 <p> Here is an example with the tables persons, towns and countries, all
3917 table, create it as explained in the configuration section. Then create the
3918 example tables:</p>
3920 <pre>
3921 CREATE TABLE REL_countries (
3922 country_code char(1) NOT NULL default '',
3923 description varchar(10) NOT NULL default '',
3924 PRIMARY KEY (country_code)
3925 ) TYPE=MyISAM;
3927 INSERT INTO REL_countries VALUES ('C', 'Canada');
3929 CREATE TABLE REL_persons (
3930 id tinyint(4) NOT NULL auto_increment,
3931 person_name varchar(32) NOT NULL default '',
3933 country_code char(1) NOT NULL default '',
3934 PRIMARY KEY (id)
3935 ) TYPE=MyISAM;
3937 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3938 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3940 CREATE TABLE REL_towns (
3942 description varchar(30) NOT NULL default '',
3943 PRIMARY KEY (town_code)
3944 ) TYPE=MyISAM;
3946 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3947 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3948 </pre>
3954 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3958 </ul>
3966 <li>In the columns row, choose persons.person_name and click the
3968 <li>Do the same for towns.description and countries.descriptions in the
3971 the correct joins have been generated</li>
3973 </ul>
3977 <p>
3978 Starting from the previous example, create the pma_table_info as explained
3979 in the configuration section, then browse your persons table,
3980 and move the mouse over a town code or country code.
3981 <br /><br />
3982 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3983 enables: drop-down list of possible values.
3984 </p>
3987 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3988 <p>
3991 <br /><br />
3992 Then you need to think about your schema layout. Which tables will go on
3993 which pages?
3994 </p>
3995 <ul>
4001 page and click Go. If you like, you
4003 linked tables onto the new page.</li>
4004 <li>Select the name of the new page (making sure the Edit radio button
4005 is selected) and click Go.</li>
4007 Coordinates are relative; your diagram will
4008 be automatically scaled to fit the page. When initially placing tables
4009 on the page, just pick any coordinates -- say, 50x50. After clicking
4011 position the element correctly.</li>
4013 first be sure to click the Save
4014 button beneath the list of tables and coordinates, to save any changes
4015 you made there. Then scroll all the way down, select the
4017 you want, and click Go.</li>
4018 <li>Internet Explorer for Windows may suggest an incorrect filename when
4023 browsers on Windows, do not have this problem.</li>
4024 </ul>
4028 columns!</a></h4>
4030 <p> No, it's MySQL that is doing
4036 underscores in the database name?</a></h4>
4038 <p> If you do not put a backslash before the underscore, this is a wildcard
4041 john2db ...<br /><br />
4043 If you put a backslash before the underscore, it means that the database
4044 name will have a real underscore.</p>
4048 statistics pages?</a></h4>
4059 if it already exists during the import. It does NOT drop the table after
4060 your export, it only affects the import file.</li>
4062 Otherwise, you may get an error if the table name exists but has a
4063 different structure.</li>
4065 (if any) will be included in backup.</li>
4067 column and table names formed with special characters are protected.</li>
4069 types set in the pmadb in the dump as
4071 </li>
4072 </ul>
4077 command, for better documentation (but resulting file is bigger).</li>
4079 once the INSERT verb and the table name.</li>
4082 </li>
4084 more info is provided in the
4086 but basically with this selected, invalid values are adjusted and
4087 inserted rather than causing the entire statement to fail.</li>
4088 </ul>
4092 in its name.</a></h4>
4095 is the normal way to reference a database and table name. Worse, MySQL
4096 will usually let you create a database with a dot, but then you cannot
4097 work with it, nor delete it.</p>
4103 <p>
4104 To use SQL Validator, you need PHP with
4110 module.
4111 </p>
4113 <p>
4119 usage.
4120 </p>
4122 <p>
4123 If you use the Validator, you should be aware that any
4125 submit will be stored anonymously (database/table/column names,
4126 strings, numbers replaced with generic values). The Mimer
4129 We utilize it as free SOAP service.
4130 </p>
4134 it, but MySQL says "BLOB column '...' used in key specification without
4137 <p> The right way to do this, is to create the column without any indexes,
4139 dialog. On this page, you will be able to choose your BLOB column, and
4140 set a size to the index, which is the condition to create an index on
4141 a BLOB column.</p>
4145 editing fields?</a></h4>
4147 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4148 with many editing fields (table structure changes, row editing, etc.).
4149 You can also have a look at the directive
4151 ('vertical') and see if this eases up editing for you.</p>
4155 WTF is this feature then useful for?</a></h4>
4157 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4158 on them. Otherwise you could just put a comment on the column. Because entering
4159 your own mimetype will cause serious syntax checking issues and validation,
4160 this introduces a high-risk false-user-input situation. Instead you have to
4161 initialize mimetypes using functions or empty mimetype definitions.<br />
4162 Plus, you have a whole overview of available mimetypes. Who knows all those
4163 mimetypes by heart so he/she can enter it at will?</p>
4167 can't I see any bookmarks below the query box? What is this variable for?
4168 </a></h4>
4170 <p> Any query you have executed can be stored as a bookmark on the page where the
4171 results are displayed. You will find a button labeled 'Bookmark this query'
4172 just at the end of the page.<br />
4173 As soon as you have stored a bookmark, it is related to the database you run
4174 the query on. You can now access a bookmark dropdown on each page, the query
4175 box appears on for that database.<br /><br />
4177 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4181 aware of that you HAVE to create a valid query, otherwise your query won't be
4182 even able to be stored in the database.<br />
4184 for your query will remain the way it is, but will be stripped of the /**/
4185 chars. So you can use:<br /><br />
4189 which will be expanded to<br /><br />
4193 in your query, where VARIABLE is the string you entered in the input box. If
4194 an empty string is provided, no replacements are made.<br /><br />
4196 A more complex example. Say you have stored this query:<br /><br />
4198 <br /><br />
4201 the full query will be:<br /><br />
4204 <br /><br />
4206 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4208 spaces inserted there
4209 will be later also inserted as spaces in your query and may lead to unexpected
4210 results especially when
4212 Your initial query which is going to be stored as a bookmark has to yield at
4213 least one result row so
4214 you can store the bookmark. You may have that to work around using well
4218 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4219 include exported table?</a></h4>
4221 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4222 document should look like following one (assuming you have table
4225 <pre>
4226 \documentclass{article} % or any class you want
4227 \usepackage{longtable} % for displaying table
4228 \begin{document} % start of document
4229 \include{table} % including exported table
4230 \end{document} % end of document
4231 </pre>
4235 access them.
4236 </a></h4>
4238 <p> You have one of these global privileges: CREATE
4239 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4240 enable users to see all the database names.
4243 So if your users do not need those privileges, you can remove them and their
4244 databases list will shorten.</p>
4248 possible values for a column, based on some foreign table?</a></h4>
4250 <p> You have to setup appropriate links between the tables, and also
4254 foreign table, a drop-down list of values will be available.
4255 You will see two lists of values, the first list containing the key
4256 and the display column, the second list containing the display column
4257 and the key. The reason for this is to be able to type the first
4258 letter of either the key or the display column.<br /><br />
4260 For 100 values or more, a distinct window will appear, to browse foreign
4261 key values and choose one. To change the default limit of 100, see
4262 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4266 automatically when entering Browse mode for a table?</a></h4>
4268 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4269 </p>
4273 Excel files, how can I enable that?</a></h4>
4275 <p> You can use
4277 which works out of the box, but phpMyAdmin supports direct export
4278 to Microsoft Excel version 97 and newer. For this to work, you need to set
4283 <pre>
4284 cd phpMyAdmin
4285 mkdir tmp
4286 chmod o+rwx tmp
4287 </pre>
4291 what happens to my column comments stored in pmadb?</a></h4>
4293 <p> Automatic migration of a table's pmadb-style column comments to the native
4294 ones is done whenever you enter Structure page for this table.</p>
4299 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4300 <ul>
4303 later)</li>
4306 </ul>
4310 <ol>
4311 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4312 <li>Ensure that your target table is under the <tt>PBXT</tt> storage engine and has a <tt>LONGBLOB</tt> column (which must be nullable if you want to remove the BLOB reference from it).</li>
4313 <li>When you insert or update a row in this table, put a checkmark on the "Upload to BLOB repository" optional choice; otherwise, the upload will be done directly in your LONGBLOB column instead of the repository.</li>
4314 <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.</li>
4315 </ol>
4320 <p> Click the first row of the range, hold the shift key and click the last row of the range. This works everywhere you see rows, for example in Browse mode or on the Structure page.</p>
4326 <p>
4327 In all places where phpMyAdmin accepts format strings, you can use
4330 expanded variables depend on a context (for example, if you haven't chosen a
4331 table, you can not get the table name), but the following variables can be used:
4332 </p>
4333 <dl>
4339 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4350 </dl>
4355 <p>
4356 By clicking on the button 'toggle scratchboard' on the page
4357 where you edit x/y coordinates of those elements you can activate a
4358 scratchboard where all your elements are placed. By clicking on an
4359 element, you can move them around in the pre-defined area and the x/y
4360 coordinates will get updated dynamically. Likewise, when entering a
4361 new position directly into the input field, the new position in the
4362 scratchboard changes after your cursor leaves the input field.
4363 </p>
4364 <p>
4365 You have to click on the 'OK'-button below the tables to save the new
4366 positions. If you want to place a new element, first add it to the
4367 table of elements and then you can drag the new element around.
4368 </p>
4369 <p>
4370 By changing the paper size and the orientation you can change the size
4371 of the scratchboard as well. You can do so by just changing the
4372 dropdown field below, and the scratchboard will resize automatically,
4373 without interfering with the current placement of the elements.
4374 </p>
4375 <p>
4376 If ever an element gets out of range you can either enlarge the paper
4377 size or click on the 'reset' button to place all elements below each
4378 other.
4379 </p>
4384 <p> Not every table can be put to the chart. Only tables with one, two or three columns can be visualised as a chart. Moreover the table must be in a special format for chart script to understand it. Currently supported formats can be found in the <a href="http://wiki.phpmyadmin.net/pma/Charts#Data_formats_for_query_results_chart">wiki</a>.</p>
4391 <p> Our Bug Tracker is located at
4393 under the Bugs section.<br /><br />
4395 But please first discuss your bug with other users:<br />
4397 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4398 </p>
4402 existing language, where do I start?</a></h4>
4404 <p> Always use latest Git version of the po file to translate. You can optionally
4406 server</a> where you can also get the latest po files and merge them
4407 with your translations. For creating a new translation simply use
4411 to do this) or ask on the mailing list to add the translation to the web
4412 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4413 </p>
4414 <p>
4415 Please note that we try not to use HTML entities like &eacute; in
4416 the translations, since we define the right character set in the file.
4417 With HTML entities, the text on JavaScript messages would not
4418 display correctly.
4419 However there are some entities that need to be there: quotes,
4420 non-breakable spaces, ampersands, less than, greater than.
4421 </p>
4422 <p>
4423 You can then put your translations, as a zip file to avoid losing special
4424 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4425 </p>
4426 <p>
4427 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4428 list, because this is where we ask for translations of new messages.
4429 </p>
4431 <p>
4432 Documentation is being translated using po4a and gettext (see
4434 for existing translations). To start, checkout
4435 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4436 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4437 and translate it online. If your language is missing, just contact
4439 you prefer to directly translate the po files, please put updated ones into our
4440 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4441 </p>
4445 phpMyAdmin. How should I proceed?</a></h4>
4450 <tt>git clone
4451 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4452 </li>
4454 <li>generate patch with your changes:
4456 </li>
4459 tracker of the phpMyAdmin project</a>.
4460 </li>
4461 </ol>
4463 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Git">our wiki</a>.</p>
4465 <p> Write access to the repository is granted only to experienced developers who
4466 have already contributed something useful to phpMyAdmin.<br />
4472 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4474 <p> Please refer to
4475 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4476 </p>
4481 <p> If you use Apache web server, phpMyAdmin exports information about
4482 authentication to the Apache environment and it can be used in Apache logs.
4483 Currently there are two variables available:
4484 </p>
4485 <dl>
4487 <dd>User name of currently active user (he does not have to be logged
4488 in).</dd>
4495 </dl>
4496 <p>
4498 </p>
4499 <pre>
4502 </pre>
4503 <p>
4504 You can then use any log analyzing tools to detect possible break-in
4505 attempts.
4506 </p>
4512 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4513 It allows you to connect to local as well as remote servers. This requires you to enter
4514 server host name, username, password, port and the name of the database. Therefore you can
4515 now synchronize your databases placed on the same server or some remote server.
4516 </p>
4518 <p>
4519 This feature is helpful for developers who need to replicate their
4520 database’s structure as well as data. Moreover, this feature not only
4521 helps replication but also facilitates the user to keep his/her database
4522 in sync with another database. Other than the full database, certain
4523 tables of the databases can also be synchronized.
4524 </p>
4526 <p>
4527 You need to fill in the host name of the server, the username and
4528 password of an user account already there in MySQL. Port is by default
4529 populated with 3306 (MySQL default port). Then the name of the database
4530 should be mentioned at the end. All the information other than the port
4531 needs to be filled explicitly for the source as well as target servers.
4532 </p>
4534 <p>
4535 After successfully passing through the authentication phase, the source and
4536 target database table names will be displayed. It will be a tabular
4537 representation.
4538 </p>
4540 <p>
4541 On the left, are listed the source database table names. Some of the
4543 are only present in source database and they need to be added to the
4544 target database in order to synchronize the target database. The tables
4546 target database.
4547 </p>
4549 <p>
4550 On the right, are listed the target database table names. There are few
4552 means that these tables are to be created in target database in order to
4553 synchronize target database with source database. Some table names
4555 only present in target database and they will remain unchanged in the
4556 target database. The column in the middle shows the difference between
4557 the source and target corresponding tables.
4558 </p>
4560 <p>
4562 letters, indicating that either Structure or Data are not up to date. By
4563 clicking on them, they will turn grey, what means that they will be synchronized.
4564 </p>
4566 <!-- DEVELOPERS -->
4569 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4570 great features have been written by other people and you too can help to
4571 make phpMyAdmin a useful tool.</p>
4573 <p> If you're planning to contribute source, please read the following
4574 information:</p>
4580 it free from other code.<br />
4581 Commonly used functions should be added to
4584 <li>Obviously, you're free to use whatever coding style you want. But
4585 please try to keep your code as simple as possible: beginners are
4586 using phpMyAdmin as an example application.<br />
4587 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4588 compliant on one hand, they fit the
4591 coding standards</a>
4592 on the other hand. Please pay attention to this.</li>
4593 <li>Please enable showing PHP errors and warnings by the
4595 configuration directive.</li>
4596 <li>Please try to keep up the file-naming conventions. Table-related stuff
4599 <li>Please use gettext wrappers around all messages
4602 script. To use translated messages, call
4604 Gettext.</li>
4608 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4609 better debug and profile their code.<br />
4610 Please see the
4612 options for more information.<br />
4613 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4614 lost during its re-entry into Earth's atmosphere and in memory of the
4615 brave men and women who gave their lives for the people of Earth.</li>
4616 </ul>
4620 <pre>
4631 </pre>
4633 <p>
4634 This program is free software; you can redistribute it and/or modify
4635 it under the terms of the GNU General Public License version 2,
4636 as published by the Free Software Foundation.
4637 </p>
4639 <p>
4640 This program is distributed in the hope that it will be useful,
4641 but WITHOUT ANY WARRANTY; without even the implied warranty of
4642 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4643 GNU General Public License for more details.
4644 </p>
4646 <p>
4647 You should have received a copy of the GNU General Public License
4648 along with this program; if not, write to the Free Software
4650 </p>
4652 <!-- CREDITS -->
4657 <ul>
4660 <ul>
4663 </ul></li>
4666 <ul>
4671 </ul></li>
4674 <ul>
4680 </ul></li>
4683 <ul>
4685 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4686 generate XHTML1.0 and CSS2 compliant codes</li>
4689 </ul></li>
4692 <ul>
4700 </ul></li>
4703 <ul>
4708 </ul></li>
4711 <ul>
4714 </ul></li>
4717 <ul>
4719 </ul></li>
4722 <ul>
4725 </ul></li>
4728 <ul>
4732 </ul></li>
4735 <ul>
4738 </ul></li>
4741 <ul>
4748 </ul></li>
4751 <ul>
4755 </ul></li>
4758 <ul>
4764 </ul></li>
4767 (http://sf.net/projects/phpmysqlformgen/)
4768 <ul>
4770 </ul></li>
4773 <ul>
4775 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4780 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4784 </ul></li>
4787 <ul>
4789 </ul></li>
4792 <ul>
4794 </ul></li>
4797 <ul>
4799 </ul></li>
4802 <ul>
4803 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4804 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4805 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4806 </ul></li>
4809 <ul>
4811 </ul></li>
4814 <ul>
4816 </ul></li>
4819 <ul>
4821 </ul></li>
4824 <ul>
4827 </ul></li>
4829 <li>Nicola Asuni (Tecnick.com)
4830 <ul>
4833 </ul></li>
4836 <ul>
4839 </ul></li>
4842 <ul>
4844 </ul></li>
4847 <ul>
4850 </ul></li>
4852 <li>Ivan A Kirillov
4853 <ul>
4855 </ul></li>
4858 <ul>
4860 </ul></li>
4863 <ul>
4866 </ul></li>
4869 <ul>
4871 </ul></li>
4874 <ul>
4876 </ul></li>
4879 <ul>
4881 </ul></li>
4884 <ul>
4886 </ul></li>
4889 <ul>
4891 </ul></li>
4894 <ul>
4898 </ul></li>
4901 <ul>
4903 </ul></li>
4906 <ul>
4908 </ul></li>
4910 <li>Barrie Leslie
4911 <ul>
4913 </ul></li>
4916 <ul>
4918 </ul></li>
4921 </ul>
4923 <p>
4924 And also to the following people who have contributed minor changes,
4925 enhancements, bugfixes or support for a new language since version 2.1.0:
4926 </p>
4928 <p>
4929 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4930 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4931 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4932 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4934 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4935 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4936 Luís V., Martijn W. van der Lee,
4937 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4939 </p>
4944 <p>
4945 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4946 to create a web-based interface to MySQL using PHP3. Although I have not
4947 used any of his source-code, there are some concepts I've borrowed from
4948 him. phpMyAdmin was created because Peter told me he wasn't going to
4949 further develop his (great) tool.
4950 </p>
4951 <p>
4952 Thanks go to
4953 </p>
4954 <ul>
4956 code for the check when dropping a table or database. He also suggested
4957 that you should be able to specify the primary key on tbl_create.php3. To
4958 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4959 well as a bug-report. Plus many smaller improvements.
4960 </li>
4962 were introduced in 1.3.0 (including quite significant ones like the
4963 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4964 bug-fixes and help.
4965 </li>
4967 language-independent by outsourcing the strings to a separate file. He
4968 also contributed the French translation.
4969 </li>
4971 tbl_select.php3, a feature to display only some columns from a table.
4972 </li>
4974 functions in tbl_change.php3. He also added the
4976 </li>
4978 servers and is a regular contributor for bug-fixes.
4979 </li>
4981 features for 2.0.6.
4982 </li>
4983 </ul>
4984 <p>
4985 The following people have contributed minor changes, enhancements, bugfixes
4986 or support for a new language:
4987 </p>
4988 <p>
4989 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4990 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4991 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4992 G. Wieggers.
4993 </p>
4994 <p>
4995 And thanks to everyone else who sent me email with suggestions, bug-reports
4996 and or just some feedback.
4997 </p>
5003 <ul>
5005 - the default name of Apache's directory-level configuration file.</li>
5009 - a software application that enables a user to display and interact with
5010 text, images, and other information typically located on a web page at a
5011 website on the World Wide Web.</li>
5013 - a free software/open source data compression algorithm and program
5014 developed by Julian Seward.</li>
5016 - an important World Wide Web technology that enables a client web browser
5017 to request data from a program executed on the Web server.</li>
5019 - a log or record of changes made to a project.</li>
5021 - a computer system that accesses a (remote) service on another computer
5022 by some kind of network.</li>
5024 - a set of data values of a particular simple type, one for each row of
5025 the table.</li>
5027 - a packet of information sent by a server to a World Wide Web browser
5028 and then sent back by the browser each time it accesses that server.</li>
5030 - Comma-separated values</li>
5033 - an organized collection of data.</li>
5036 - a PHP module that extends PHP with additional functionality.</li>
5038 - a list of commonly asked question and there answers.</li>
5040 - one part of divided data/columns.</li>
5042 - a field or group of fields in a database record that point to a key
5043 field or group of fields forming a key of another database record in some
5044 (usually different) table.</li>
5046 - the free PDF library</li>
5048 GD Graphics Library</a> - a library by Thomas Boutell and others for
5049 dynamically manipulating images.</li>
5052 - gzip is short for GNU zip, a GNU free software file compression
5053 program.</li>
5055 - any machine connected to a computer network, a node that has a hostname.</li>
5057 - the unique name by which a network attached device is known on a network.</li>
5059 (HyperText Transfer Protocol)</a>
5060 - the primary method used to transfer or convey information on the World
5061 Wide Web.</li>
5064 additional security measures.</li>
5065 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5066 - a set of Internet-based services for servers using Microsoft Windows.</li>
5068 - a feature that allows quick access to the rows in a table.</li>
5070 - a data-oriented protocol used by source and destination hosts for
5071 communicating data across a packet-switched internetwork.</li>
5073 - a unique number that devices use in order to identify and communicate
5074 with each other on a network utilizing the Internet Protocol standard.</li>
5076 (Internet Server Application Programming Interface)</a>
5077 - the API of Internet Information Services (IIS).</li>
5079 - a business or organization that offers users access to the Internet and related services.</li>
5081 - a most commonly used standard method of lossy compression for
5082 photographic images.</li>
5088 - line of personal computers is designed, developed, manufactured, and
5089 marketed by Apple Computer.</li>
5090 <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>
5091 - the operating system which is included with all currently shipping Apple
5092 Macintosh computers in the consumer and professional markets.</li>
5094 - a cryptographic library.</li>
5096 - the MCrypt PHP extension.</li>
5097 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5098 - an Internet Standard for the format of e-mail.</li>
5100 - some sort of extension for the Apache Webserver.</li>
5102 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5103 Management System (DBMS).</li>
5105 - the improved MySQL client PHP extension.</li>
5107 - the MySQL client PHP extension.</li>
5109 - open standard for office documents.</li>
5110 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5111 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5113 (Portable Document Format)</a>
5114 - a file format developed by Adobe Systems for representing two
5115 dimensional documents in a device independent and resolution independent
5116 format.</li>
5118 - the PHP Extension and Application Repository.</li>
5120 - the perl-compatible regular expression functions for PHP</li>
5122 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5123 programming language used mainly for developing server-side applications
5124 and dynamic web content, and more recently, a broader range of software
5125 applications.</li>
5127 - a connection through which data is sent and received.</li>
5129 - Request for Comments (RFC) documents are a series of memoranda
5130 encompassing new research, innovations, and methodologies applicable to
5131 Internet technologies.</li>
5135 - represents a single, implicitly structured data item in a table.</li>
5137 - a computer system that provides services to other computing
5138 systems over a network.</li>
5139 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5140 - handlers for different table types</li>
5142 - a form of inter-process communication.</li>
5144 Sockets Layer)</a>
5145 - a cryptographic protocol which provides secure communication on the Internet.</li>
5147 - a subroutine available to applications accessing a relational database system</li>
5149 - Structured Query Language</li>
5151 - a set of data elements (cells) that is organized, defined and stored as
5152 horizontal rows and vertical columns where each item can be uniquely
5153 identified by a label or key or by it?s position in relation to other items.</li>
5156 - a type of archive file format: the Tape ARchive format.</li>
5158 - one of the core protocols of the Internet protocol suite.</li>
5160 - a procedural code that is automatically executed in response to
5161 certain events on a particular table or view in a database</li>
5165 - a sequence of characters, conforming to a standardized format, that is
5166 used for referring to resources, such as documents and images on the
5167 Internet, by their location.</li>
5169 - A computer (program) that is responsible for accepting HTTP requests
5170 from clients and serving them Web pages.</li>
5172 - a W3C-recommended general-purpose markup language for creating
5173 special-purpose markup languages, capable of describing many different
5174 kinds of data.</li>
5176 - a popular data compression and archival format.</li>
5178 - an open-source, cross-platform data compression library by Jean-loup
5179 Gailly and Mark Adler.</li>
5180 </ul>
5181 </div>
5184 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5187 <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>
5188 </ul>
5190 </body>
5191 </html>