| blob | cb49b2c15bd7e7e48d5d493055e8e93930500074 |
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).</dd>
717 </dt>
719 all relational features (see
721 and, for a MySQL server running with
724 authentication mode).<br /><br />
727 cookie authentication modes (or 'config'
728 authentication mode since phpMyAdmin 2.2.1), you need to supply the
733 This account is used to check what databases the user will see at
734 login.<br />
738 In phpMyAdmin versions before 2.2.5, those were called
742 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
743 <dd>Whether config or cookie or
745 should be used for this server.
747 is the plain old way: username and password are stored in
749 <li>'cookie' authentication mode
751 2.2.3 allows you to log in as any valid MySQL user with the
752 help of cookies. Username and password are stored in
753 cookies during the session and password is deleted when it
754 ends. This can also allow you to log in in arbitrary server if
755 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
756 </li>
757 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
758 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
759 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
760 <li>'signon' authentication mode
762 as introduced in 2.10.0 allows you to log in from prepared PHP
763 session data or using supplied PHP script. This is useful for implementing single signon
764 from another application.
770 You need to
776 </ul>
779 for more information.
780 </dd>
782 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
783 </dt>
784 <dd>
785 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
786 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
787 specified in your configuration, a string combined of "phpMyAdmin " and either
790 </dd>
792 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
793 </dt>
794 <dd>
796 names for hardware authentication. Leave empty to deactivate this feature.
797 </dd>
801 </dt>
802 <dd>
803 When using auth_type = 'config', this is the user/password-pair
804 which phpMyAdmin will use to connect to the
805 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
806 cookie authentication is used and should be empty.</dd>
808 <span
810 </dt>
811 <dd>
812 Allow attempt to log in without password when a login with password
813 fails. This can be used together with http authentication, when
814 authentication is done some other way and phpMyAdmin gets user name
815 from auth and uses empty password for connecting to MySQL. Password
816 login is still tried first, but as fallback, no password method is
817 tried.</dd>
820 </dt>
821 <dd>
822 If set to a (an array of) database name(s), only this (these) database(s)
823 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
824 database(s) name(s) may contain MySQL wildcards characters
828 This setting is an efficient way to lower the server load since the
829 latter does not need to send MySQL requests to build the available
831 privileges rules of the MySQL database server</span>. If set, it just
832 means only these databases will be displayed but
834 <br /><br />
836 An example of using more that one database:
838 <br /><br />
840 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
841 databases in the left frame, so that you can individually arrange your databases.<br />
842 If you want to have certain databases at the top, but don't care about the others, you do not
843 need to specify all other databases. Use:
845 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
846 order.</dd>
849 </dt>
850 <dd>Regular expression for hiding some databases from unprivileged users.
851 This only hides them
852 from listing, but a user is still able to access them (using, for example,
853 the SQL query area). To limit access, use the MySQL privilege system.
854 <br /><br />
859 More information on regular expressions can be found in the
861 PCRE pattern syntax</a> portion of the PHP reference manual.
862 </dd>
865 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
866 this string will be displayed instead of the hostname in the pull-down
867 menu on the main page. This can be useful if you want to show only
868 certain databases on your system, for example. For HTTP auth, all
869 non-US-ASCII characters will be stripped.</dd>
873 </dt>
874 <dd>The name of the database containing the phpMyAdmin configuration storage.
875 <br /><br />
878 section in this document to see the benefits of this feature,
879 and for a quick way of creating this database and the needed tables.
880 <br /><br />
882 If you are the only user of this phpMyAdmin installation, you can
883 use your current database to store those special tables; in this
884 case, just put your current database name in
886 set this parameter to the name of your central database containing
887 the phpMyAdmin configuration storage.</dd>
891 </dt>
893 useful for queries you often run.<br /><br />
895 To allow the usage of this functionality:
897 <li>enter the table name in
899 </ul>
900 </dd>
904 </dt>
906 which column is a key in another table (a foreign key). phpMyAdmin
907 currently uses this to
908 <ul><li>make clickable, when you browse the master table, the data values
909 that point to the foreign table;</li>
911 when browsing the master table, if you move the mouse to a column
912 containing a foreign key (use also the 'table_info' table);<br />
915 <li>in edit/insert mode, display a drop-down list of possible foreign
919 <li>display links on the table properties page, to check referential
920 integrity (display missing foreign keys) for each described key;
921 </li>
925 schema of your database (also uses the table_coords table).</li>
926 </ul>
928 The keys can be numeric or character.<br /><br />
930 To allow the usage of this functionality:
933 configuration storage</li>
934 <li>put the relation table name in
936 <li>now as normal user open phpMyAdmin and for each one of your
937 tables where you want to use this feature, click
939 columns.
940 </li>
941 </ul>
945 future development of the cross-db relations.
946 </dd>
950 </dt>
951 <dd>
952 Since release 2.3.0 you can describe, in a special 'table_info'
953 table, which column is to be displayed as a tool-tip when moving the
954 cursor over the corresponding key.<br />
955 This configuration variable will hold the name of this special
956 table. To allow the usage of this functionality:
958 <li>put the table name in
960 'pma_table_info')</li>
961 <li>then for each table where you want to use this feature,
963 to choose the column.</li>
964 </ul>
966 </dd>
970 </dt>
973 the relations between your tables. To do this it needs two tables
978 schema output).<br /><br />
982 To allow the usage of this functionality:
985 <li>put the correct table names in
988 </ul>
991 </dd>
995 </dt>
997 Since release 2.3.0 you can store comments to describe each column for
999 <br /><br />
1001 Starting with release 2.5.0, comments are consequently used on the table
1002 property pages and table browse view, showing up as tool-tips above the
1003 column name (properties page) or embedded within the header of table in
1004 browse view. They can also be shown in a table dump. Please see the
1005 relevant configuration directives later on.<br /><br />
1007 Also new in release 2.5.0 is a MIME-transformation system which is also
1009 Transformations</a> for further information. To use the
1010 MIME-transformation system, your column_info table has to have the three
1011 new columns 'mimetype', 'transformation', 'transformation_options'.
1012 <br /><br />
1014 To allow the usage of this functionality:
1016 <li>put the table name in
1018 'pma_column_info')</li>
1021 <pre>
1022 ALTER TABLE `pma_column_comments`
1023 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1024 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1025 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1026 </pre>
1029 renamed from<br />
1032 </ul>
1033 </dd>
1037 </dt>
1040 all queries you entered manually into the phpMyAdmin interface. If you
1041 don't want to use a table-based history, you can use the JavaScript-based
1042 history. Using that, all your history items are deleted when closing the
1043 window.<br /><br />
1045 Using
1047 you can specify an amount of history items you want to have on hold. On
1048 every login, this list gets cut to the maximum amount.<br /><br />
1050 The query history is only available if JavaScript is enabled in your
1051 browser.<br /><br />
1053 To allow the usage of this functionality:
1057 (e.g. 'pma_history')
1058 </li>
1059 </ul>
1060 </dd>
1064 </dt>
1065 <dd>
1066 Since release 3.5.0 you can show recently used tables in the left navigation frame.
1067 It helps you to jump across table directly, without the need to select the database,
1068 and then select the table. Using
1070 you can configure the maximum number of recent tables shown. When you select a table
1071 from the list, it will jump to the page specified in
1072 <a href="#cfg_LeftDefaultTabTable" class="configrule">$cfg['LeftDefaultTabTable']</a>.<br/><br/>
1074 Without configuring the storage, you can still access the recently used tables,
1075 but it will disappear after you logout.<br/><br/>
1077 To allow the usage of this functionality persistently:
1079 <ul>
1082 </ul>
1083 </dd>
1087 </dt>
1088 <dd>
1089 Since release 3.5.0 phpMyAdmin can be configured to remember several things
1090 (table sorting
1092 , etc.) for browsing tables.
1093 Without configuring the storage, these features still can be used,
1094 but the values will disappear after you logout.<br/><br/>
1096 To allow the usage of these functionality persistently:
1098 <ul>
1100 <li>put the table name in <tt>$cfg['Servers'][$i]['table_uiprefs']</tt> (e.g. 'pma_table_uiprefs')</li>
1101 </ul>
1102 </dd>
1106 </dt>
1107 <dd>
1108 Since release 3.3.x a tracking mechanism is available.
1110 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1111 and data definition statements. After enabling it you can create versions of tables.
1112 <br/><br/>
1113 The creation of a version has two effects:
1115 <ul>
1117 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1118 </ul>
1120 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1121 For the report you can use filters, for example you can get a list of statements within a date range.
1122 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1123 In addition you can export the (filtered) report to a file or to a temporary database.
1124 <br/><br/>
1126 To allow the usage of this functionality:
1128 <ul>
1131 </ul>
1132 </dd>
1135 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1136 </dt>
1137 <dd>
1138 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1139 <br/><br/>
1140 If this is set to true and you create a table or view with
1142 <ul>
1145 </ul>
1147 and no version exists for it, the mechanism will
1148 create a version for you automatically.
1149 </dd>
1152 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1153 </dt>
1154 <dd>
1155 Defines the list of statements the auto-creation uses for new versions. Default value is
1156 <br/>
1158 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1159 CREATE INDEX,DROP INDEX,
1160 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1161 CREATE VIEW,ALTER VIEW,DROP VIEW,
1162 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1163 </dd>
1166 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1167 </dt>
1168 <dd>
1169 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1170 <br/><br/>
1171 </dd>
1175 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1176 </dt>
1177 <dd>
1178 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1179 <br/><br/>
1180 </dd>
1183 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1184 </dt>
1185 <dd>
1186 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1187 <br/><br/>
1188 </dd>
1192 </dt>
1193 <dd>
1194 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1195 and store them in the database.
1196 <br /><br />
1199 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1200 or, it is is unavailable, until the end of session.
1201 <br /><br />
1203 To allow the usage of this functionality:
1205 <ul>
1207 configuration storage</li>
1209 </ul>
1210 </dd>
1214 </dt>
1216 to visually manage the relations.
1217 <br /><br />
1219 To allow the usage of this functionality:
1222 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1223 </li>
1224 </ul>
1225 </dd>
1228 </dt>
1230 column_info table got enhanced with three new columns. If the above variable
1232 latest table structure available. If not, it will emit a warning to the
1233 superuser.<br /><br />
1235 You can disable this checking behavior by setting the variable to false,
1236 which should offer a performance increase.<br /><br />
1238 Recommended to set to FALSE, when you are sure, your table structure is
1239 up to date.</dd>
1241 boolean</dt>
1242 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1243 </dd>
1245 boolean</dt>
1246 <dd>Whether to allow logins without a password. The default
1248 to a MySQL server with was left with an empty password for root or
1249 on which an anonymous (blank) user is defined.
1250 </dd>
1253 </dt>
1255 authorization is disabled.<br /><br />
1258 all deny rules followed by allow rules. Access is allowed by default. Any
1259 client which does not match a Deny command or does match an Allow command
1260 will be allowed access to the server. <br /><br />
1263 applies all allow rules followed by deny rules. Access is denied by
1264 default. Any client which does not match an Allow directive or does
1265 match a Deny directive will be denied access to the server.<br /><br />
1267 If your rule order is set to 'explicit', authorization is
1268 performed in a similar fashion to rule order 'deny,allow', with the
1272 and was available in Apache by specifying allow and deny rules without
1273 setting any order.<br /><br />
1275 Please also see <a
1277 address behind proxies.
1278 </dd>
1280 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1281 </dt>
1282 <dd>The general format for the rules is as such:
1284 <pre>
1286 </pre>
1291 well (please note that those containing SERVER_ADDRESS might not be
1292 available on all webservers):
1293 <pre>
1299 </pre>
1301 Having an empty rule list is equivalent to either using
1307 following work:<br />
1309 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1310 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1311 But the following does not work:<br />
1314 Also IPv6 addresses are not supported.
1315 </dd>
1317 <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.
1318 </dd>
1319 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1321 DATABASES</tt> command used to fetch the name of available databases will
1322 probably be too slow, so it can be replaced by faster commands (see
1324 </dd>
1326 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1327 </dd>
1329 <dd>Name of PHP script to be sourced and executed to obtain
1330 login credentials. This is alternative approach to session based single
1331 signon. The script needs to provide function
1333 password, accepting single parameter of existing username (can be empty).
1335 </dd>
1336 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1337 <dd>Name of session which will be used for signon authentication method.
1339 this is session which phpMyAdmin uses internally. Takes effect only if
1341 is not configured.
1342 </dd>
1344 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1345 </dd>
1347 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1348 </dd>
1351 <dd>If you have more than one server configured, you can set
1353 that server when phpMyAdmin is started, or set it to 0 to be given a
1354 list of servers without logging in.<br />
1356 MUST be set to that server.</dd>
1359 <dd>Defines whether to refresh only parts of certain pages using Ajax
1360 techniques. Applies only where a non-Ajax behavior is possible;
1361 for example, the Designer feature is Ajax-only so this directive
1362 does not apply to it.</dd>
1365 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1366 page.</dd>
1369 <dd>The maximum number of database names to be displayed in the
1370 navigation frame and the database list.</dd>
1373 <dd>The maximum number of table names to be displayed in the
1374 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1375 when in Light mode.</dd>
1378 <dd>The maximum number of characters when a SQL query is displayed. The
1379 default limit of 1000 should be correct to avoid the display of tons
1380 of hexadecimal codes that represent BLOBs, but some users have real
1381 SQL queries that are longer than 1000 characters. Also, if a query's
1382 length exceeds this limit, this query is not saved in the history.</dd>
1385 <dd>Defines whether to use GZip output buffering for increased
1387 Set to true/false for enabling/disabling. When set to 'auto' (string),
1388 phpMyAdmin tries to enable output buffering and will automatically disable
1389 it if your browser has some problems with buffering. IE6 with a certain patch
1390 is known to cause data corruption when having enabled buffering.</dd>
1393 <dd>Whether <a href="http://php.net/manual/en/features.persistent-connections.php">persistent connections</a>
1394 should be used or not. Works with following extensions:
1395 <ul>
1396 <li>mysql (<a href="http://php.net/manual/en/function.mysql-pconnect.php">mysql_pconnect</a>),</li>
1397 <li>mysqli (requires PHP 5.3.0 or newer, <a href="http://php.net/manual/en/mysqli.persistconns.php">more information</a>).</li>
1398 </ul></dd>
1404 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1405 to zero, no time limit is imposed.<br />
1406 This setting is used while importing/exporting dump files and in the
1407 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1414 <dd>Set the number of bytes a script is allowed to allocate. If set
1415 to zero, no limit is imposed.<br />
1416 This setting is used while importing/exporting dump files and at some
1417 other places in phpMyAdmin so you definitely don't want to put here
1418 a too low value. It has no effect when PHP is running in safe mode.<br />
1419 You can also use any string as in php.ini, eg. '16M'. Ensure
1423 <dd>Mark used tables and make it possible to show databases with locked
1428 generated by phpMyAdmin should be displayed or not.</dd>
1431 <dd>Defines whether normal users (non-administrator) are allowed to
1432 delete their own database or not. If set as FALSE, the link "Drop
1434 mydatabase" will be rejected. Quite practical for
1436 customers.<br />
1437 Please note that this limitation of SQL queries is not as strict as
1438 when using MySQL privileges. This is due to nature of SQL queries
1439 which might be quite complicated. So this choice should be viewed as
1440 help to avoid accidental dropping rather than strict privilege
1441 limitation.</dd>
1445 displayed when you're about to lose data.</dd>
1448 <dd>Define whether the previous login should be recalled or not in cookie
1449 authentication mode.<br /><br />
1451 This is automatically disabled if you do not have configured
1453 </dd>
1456 <dd>Define how long is login cookie valid. Please note that php
1457 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1458 might limit session validity and if session is lost, login cookie is
1460 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1464 means that it will be kept for existing session. This is recommended
1465 for not trusted environments.</dd>
1468 <dd>If enabled (default), logout deletes cookies for all servers,
1469 otherwise only for current one. Setting this to false makes it easy to
1470 forget to log out from other server, when you are using more of
1471 them.</dd>
1477 <dd>Define whether phpMyAdmin will continue executing a multi-query
1478 statement if one of the queries fails. Default is to abort execution.</dd>
1481 <dd>Define whether phpMyAdmin will output the results of each query of a
1482 multi-query statement embedded into the
1487 <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.
1488 <br /><br />
1491 MySQL servers behind the firewall where your
1493 </dd>
1502 <dd>Defines whether to use a select-based menu and display only the current
1503 tables in the left frame (smaller page). Only in Non-Lightmode you can
1504 use the feature to display nested folders using
1506 </dd>
1509 <dd>In light mode, defines whether to display the names of databases (in the
1510 selector) using a tree, see also
1512 </dd>
1515 string or array</dt>
1516 <dd>The string used to separate the parts of the database name when showing
1517 them in a tree. Alternatively you can specify more strings in an array
1518 and all of them will be used as a separator.</dd>
1521 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1522 This means if you have tables like 'first__second__third' this will be
1524 If set to FALSE or empty, the feature is disabled. NOTE: You should
1525 not use this separator at the beginning or end of a
1526 table name or multiple times after another without any other
1527 characters in between.</dd>
1530 <dd>Defines how many sublevels should be displayed when splitting
1531 up tables by the above separator.</dd>
1534 <dd>The maximum number of recently used tables shown in the left navigation
1538 <dd>Defines whether to display table comment as tool-tip in left frame or
1539 not.</dd>
1542 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1543 comment and the real name. That means that if you have a table called
1544 'user0001' and add the comment 'MyName' on it, you will see the name
1545 'MyName' used consequently in the left frame and the tool-tip shows
1546 the real name of the DB.</dd>
1549 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1551 When setting this to 'nested', the Alias of the Tablename is only used
1552 to split/nest the tables according to the
1554 directive. So only the folder is called like the Alias, the tablename itself
1555 stays the real tablename.</dd>
1558 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1561 <dd>Enter URL where logo in the navigation frame will point to.
1562 For use especially with self made theme which changes this.
1571 integer</dt>
1572 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1573 list of tables in the left frame.
1578 <dd>Defines whether or not to display a server choice at the top of the left frame.
1579 Defaults to FALSE.</dd>
1581 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1582 Defaults to FALSE (drop-down).</dd>
1584 <dd>Defines whether to display database choice in light navigation frame as links
1585 instead of in a drop-down. Defaults to 'auto' - on main page list is
1586 shown, when database is selected, only drop down is displayed.</dd>
1589 <dd>Defines the tab displayed by default when clicking the small
1590 icon next to each table name in the navigation panel. Possible
1596 <dd>Defines whether or not to display space usage and statistics about databases
1597 and tables.<br />
1598 Note that statistics requires at least MySQL 3.23.3 and that, at this
1599 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1602 <dd>Defines whether to display detailed server information on main page.
1603 You can additionally hide more information by using
1605 </dd>
1610 </dt>
1613 not at the starting main (right) frame. This setting
1614 does not check MySQL commands entered directly.<br /><br />
1616 Please note that to block the usage of phpinfo() in scripts, you
1623 hard coded password value in the configuration file, end users can't
1624 be allowed to change their passwords.</dd>
1627 <dd>Defines whether to suggest a database name on the
1631 <dd>Defines whether navigation bar buttons and the right panel top menu
1632 contain text or symbols only. A value of TRUE displays icons, FALSE
1633 displays text and 'both' displays both icons and text.</dd>
1636 <dd>Defines whether a user should be displayed a
1640 <dd>Number of rows displayed when browsing a result set. If the result set
1647 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1651 option is ticked by default.</dd>
1655 from editing when browsing a table's content. Valid values are:
1660 </ul>
1661 </dd>
1664 <dd>Defines whether or not MySQL functions fields should be initially
1665 displayed in edit/insert mode. Since version 2.10, the user can
1666 toggle this setting from the interface.
1667 </dd>
1670 <dd>Defines whether or not type fields should be initially
1671 displayed in edit/insert mode. The user can
1672 toggle this setting from the interface.
1673 </dd>
1676 <dd>Defines which type of editing controls should be used for CHAR and
1677 VARCHAR columns. Possible values are:
1678 <ul><li>input - this allows to limit size of text to size of columns in
1679 MySQL, but has problems with newlines in columns</li>
1680 <li>textarea - no problems with newlines in columns, but also no
1681 length limitations</li>
1682 </ul>
1683 Default is old behavior so input.</dd>
1689 <dd>If there are fewer items than this in the set of foreign keys, then a
1690 drop-down box of foreign keys is presented, in the style described by the
1692 setting.</dd>
1695 <dd>For the foreign key drop-down fields, there are several methods of
1696 display, offering both the key and value data. The contents of the
1697 array should be one or both of the following strings:
1703 </dt>
1704 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1705 creating a dump file</dd>
1708 </dt>
1709 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1710 compressed exports. This doesn't affect smaller dumps and allows users to
1711 create larger dumps that won't otherwise fit in memory due to php
1712 memory limit. Produced files contain more GZip/BZip2 headers, but all
1713 normal programs handle this correctly.</dd>
1717 mainframe.</dd>
1721 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1726 <dd>How many columns will be utilized to display the tables on the
1727 database property view? Default is 1 column. When setting this to a
1728 value larger than 1, the type of the database will be omitted for more
1729 display space.</dd>
1733 <dd>Defines the tab displayed by default on server view. Possible
1740 <dd>Defines the tab displayed by default on database view. Possible
1745 <dd>Defines the tab displayed by default on table view. Possible
1752 points to the MySQL documentation (type depends
1753 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1754 generated.<br />
1756 for more information about MySQL manuals and their types.</dd>
1759 <dd>Type of MySQL documentation:
1765 </ul>
1766 </dd>
1769 <dd>Defines the default language to use, if not browser-defined or
1770 user-defined.<br />
1771 The corresponding language file needs to be in
1773 </dd>
1776 <dd>Defines the default connection collation to use, if not
1777 user-defined.<br />
1783 The corresponding language file needs to be in
1785 </dd>
1788 <dd>Limit list of available languages to those matching the given regular
1789 expression. For example if you want only Czech and English, you should
1793 <dd>You can select here which functions will be used for character set
1794 conversion. Possible values are:
1795 <ul><li>auto - automatically use available one (first is tested
1796 iconv, then recode)</li>
1800 </ul>
1801 Default is auto.</dd>
1802 <dd>
1803 Enabled charset conversion activates a pull-down menu
1804 in the Export and Import pages, to choose the character set when
1805 exporting a file. The default value in this menu comes from
1807 </dd>
1810 <dd>Specify some parameters for iconv used in charset conversion. See
1813 used, so that invalid characters will be transliterated.</dd>
1816 <dd>Available character sets for MySQL conversion. You can add your own (any of
1817 supported by recode/iconv) or remove these which you don't use.
1818 Character sets will be shown in same order as here listed, so if you
1819 frequently use some of these move them to the top.</dd>
1824 default empty, you need to fill in some trusted proxy servers if you
1825 want to use rules for IP addresses behind proxy.<br /><br />
1827 The following example specifies that phpMyAdmin should trust a
1829 <pre>
1830 $cfg['TrustedProxies'] =
1832 </pre>
1833 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1834 client's IP address as usual.
1835 </dd>
1839 MIME transformations.<br />
1840 Possible values are:
1844 </ul>
1845 Default is auto.
1846 </dd>
1849 <dd>
1850 We normally check the permissions on the configuration file to ensure
1851 it's not world writable. However, phpMyAdmin could be installed on
1852 a NTFS filesystem mounted on a non-Windows server, in which case the
1853 permissions seems wrong but in fact cannot be detected. In this case
1855 </dd>
1858 <dd>
1859 Limit for length of URL in links. When length would be above this limit, it
1860 is replaced by form with button.
1861 This is required as some web servers (IIS) have problems with long URLs.
1863 </dd>
1865 <dt
1867 <dd>
1868 In the database Structure page, it's possible to mark some tables then
1869 choose an operation like optimizing for many tables. This can slow down
1872 </dd>
1876 </dd>
1878 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1880 </dt>
1881 <dd>The background styles used for both the frames.
1884 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1886 <dd>The style used for the pointer in the navi frame.
1895 </dd>
1899 <dd>The style used for table headers. See
1904 </dd>
1908 </dd>
1910 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1912 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1914 </dt>
1916 The former feature highlights the row over which your mouse is passing
1917 and the latter lets you visually mark/unmark rows by clicking on
1918 them. Highlighting / marking a column is done by hovering over /
1919 clicking the column's header (outside of the text).<br />
1924 <dd>You put here a valid CSS font family value, for example
1929 <dd>You put here a valid CSS font family value, for example
1943 </dt>
1945 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1947 The Char* values are used for CHAR and VARCHAR editing (if configured
1951 </dt>
1955 </dt>
1956 <dd>Defines if the whole textarea of the query box will be selected on
1957 click.</dd>
1960 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1961 Can be turned off by a toggle button on the browse page.</dd>
1964 </dt>
1965 <dd>Defines the place where table row links (Edit, Inline edit, Copy,
1966 Delete) would be put when tables contents are displayed (you may
1967 have them displayed at the left side, right side, both sides or nowhere).
1973 Define which one is displayed by default. The first mode displays each
1974 row on a horizontal line, the second rotates the headers by 90
1975 degrees, so you can use descriptive headers even though columns only
1976 contain small values and still print them out. The vertical mode sorts
1977 each row on a vertical lineup.
1978 </dd>
1984 <dd>
1985 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1986 'css' the rotation of the header for horizontalflipped is done via
1987 CSS. The CSS transformation currently works only in Internet
1988 Explorer.If set to 'fake' PHP does the transformation for you, but of
1989 course this does not look as good as CSS. The 'auto' option enables
1990 CSS transformation when browser supports it and use PHP based one
1991 otherwise.
1992 </dd>
1996 string or integer</dt>
1997 <dd>When editing/creating new columns in a table all fields normally get
1998 lined up one field a line. (default: 'horizontal'). If you set this to
1999 'vertical' you can have each field lined up vertically beneath each
2000 other. You can save up a lot of place on the horizontal direction and
2001 no longer have to scroll. If you set this to integer, editing of fewer
2002 columns will appear in 'vertical' mode, while editing of more columns
2003 still in 'horizontal' mode. This way you can still effectively edit
2004 large number of columns, while having full view on few of them.</dd>
2008 </dt>
2010 display of column comments in Browse or Property display. In browse
2011 mode, the comments are shown inside the header. In property mode,
2012 comments are displayed using a CSS-formatted dashed-line below the
2013 name of the column. The comment is shown as a tool-tip for that column.
2014 </dd>
2026 <dd>Whether to display a link to validate a query in any SQL Query box.
2033 <dd>
2034 The name of the directory where
2036 uploaded by other means than phpMyAdmin (for example, ftp). Those files
2037 are available under a drop-down box when you click the database or
2038 table name, then the Import tab.
2039 <br /><br />
2041 If you want different directory for each user, %u will be replaced
2042 with username.<br /><br />
2046 compressed formats is enabled).<br /><br />
2048 This feature is useful when your file is too big to be uploaded via
2050 uploads are disabled in PHP.<br /><br />
2052 Please note that if PHP is running in safe mode, this directory must
2053 be owned by the same user as the owner of the phpMyAdmin scripts.
2054 <br /><br />
2058 alternatives.
2059 </dd>
2062 <dd>
2063 The name of the directory where dumps can be saved.<br /><br />
2065 If you want different directory for each user, %u will be replaced
2066 with username.<br /><br />
2068 Please note that the directory must exist and has to be writable for
2069 the user running webserver.<br /><br />
2071 Please note that if PHP is running in safe mode, this directory must
2072 be owned by the same user as the owner of the phpMyAdmin scripts.
2073 </dd>
2076 <dd>
2077 The name of the directory where temporary files can be stored.
2078 <br /><br />
2080 This is needed for native MS Excel export, see
2086 <br /><br />
2088 If the directory where phpMyAdmin is installed is subject to an
2090 temporary directory in some directory accessible by the web
2091 server. However for security reasons, this directory should be outside
2092 the tree published by webserver. If you cannot avoid having this
2093 directory published by webserver, place at least an empty
2095 possible.
2096 <br /><br />
2098 This directory should have as strict permissions as possible as the only
2099 user required to access this directory is the one who runs the
2100 webserver. If you have root privileges, simply make this user owner of
2101 this directory and make it accessible only by it:
2102 <br /><br />
2104 <pre>
2105 chown www-data:www-data tmp
2106 chmod 700 tmp
2107 </pre>
2109 If you cannot change owner of the directory, you can achieve a similar
2112 <pre>
2113 chmod 700 tmp
2114 setfacl -m "g:www-data:rwx" tmp
2115 setfacl -d -m "g:www-data:rwx" tmp
2116 </pre>
2118 If neither of above works for you, you can still make the directory
2120 system reading and writing data in this directory.
2121 </dd>
2124 <dd>
2125 In this array are defined default parameters for export, names of
2126 items are similar to texts seen on export page, so you can easily
2127 identify what they mean.
2128 </dd>
2131 <dd>
2132 Defines how the export form is displayed when it loads. Valid values are:
2133 <ul>
2136 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2137 </ul>
2138 </dd>
2141 <dd>
2142 In this array are defined default parameters for import, names of
2143 items are similar to texts seen on import page, so you can easily
2144 identify what they mean.
2145 </dd>
2148 <dd>
2149 Defines whether or not type display direction option is shown
2150 when browsing a table.
2151 </dd>
2154 <dd>
2155 Repeat the headers every X cells, or 0 to deactivate.
2156 </dd>
2164 </dt>
2165 <dd>
2166 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2167 or icon is always displayed on the left panel. If JavaScript is enabled in
2168 your browser, a click on this opens a distinct query window, which is
2169 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2170 changes to display a query box.<br /><br />
2172 The size of this query window can be customized with
2174 - both integers for the size in pixels. Note that normally, those
2176 theme you are using.<br /><br />
2180 opens the query window and puts the current query
2181 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2182 query in the right panel's query box.
2183 <br /><br />
2184 The usage of the JavaScript query window is recommended if you have a
2185 JavaScript enabled browser. Basic functions are used to exchange quite
2186 a few variables, so most 4th generation browsers should be capable to
2187 use that feature. It currently is only tested with Internet Explorer 6
2188 and Mozilla 1.x.
2189 <br /><br />
2191 to a table, which has to be created by you (see <a
2193 all your queries will be appended to the form, but only as long as
2194 your window is opened they remain saved.
2195 <br /><br />
2196 When using the JavaScript based query window, it will always get
2197 updated when you click on a new table/db to browse and will focus if
2198 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2199 the query window by checking the box "Do not overwrite this query from
2200 outside the window" below the query textarea. Then you can browse
2201 tables/databases in the background without losing the contents of the
2202 textarea, so this is especially useful when composing a query with
2203 tables you first have to look in. The checkbox will get automatically
2204 checked whenever you change the contents of the textarea. Please
2205 uncheck the button whenever you definitely want the query window to
2206 get updated even though you have made alterations.
2207 <br /><br />
2210 <br /><br />
2211 The query window also has a custom tabbed look to group the features.
2213 default tab to be used when opening the query window. It can be set to
2214 either 'sql', 'files', 'history' or 'full'.</dd>
2220 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2222 If the approximate row count as returned by
2225 count will be used.
2226 </dd>
2228 <dd>For VIEWs, since obtaining the exact count could have an
2229 impact on performance, this value is the maximum to be displayed, using
2231 any row counting.
2232 </dd>
2235 <dd>Sorts database and table names according to natural order (for example,
2236 t1, t2, t10). Currently implemented in the left panel (Light mode)
2237 and in Database view, for the table list.</dd>
2246 that users can't set through user preferences. For possible values, refer
2253 <dd>Allows you to specify window's title bar. You can use
2255 </dd>
2265 </dd>
2268 <dd>If theme manager is active, use this as the path of the subdirectory
2269 containing all the themes.</dd>
2283 </dt>
2284 <dd>Default queries that will be displayed in query boxes when user didn't
2285 specify any. You can use standard
2287 </dd>
2290 <dd>
2291 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
2292 default we use HTML to format the query, but you can disable this by
2294 </dd>
2297 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2298 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2299 query inside a bracket is indented. By changing
2302 specifies the units of the indent amount that you specified. This is
2303 used via stylesheets.</dd>
2306 <dd>This array is used to define the colours for each type of element of
2307 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2309 If you specify an empty string for the color of a class, it is ignored
2310 in creating the stylesheet.
2311 You should not alter the class names, only the colour strings.<br />
2332 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2336 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2337 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2338 </ul>
2339 </dd>
2343 <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,
2344 as originally published on
2346 <br />
2347 For help in setting up your system to use the service, see the
2349 </dd>
2353 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2354 and any password, so we use those by default. Instead, if
2355 you have an account with them, you can put your login details
2356 here, and it will be used in place of the anonymous login.</dd>
2357 </dl>
2358 </dd>
2361 <dd><b>DEVELOPERS ONLY!</b></dd>
2364 <dd><b>DEVELOPERS ONLY!</b><br />
2365 Enable logging queries and execution times to be displayed in the bottom
2366 of main page (right frame).</dd>
2369 <dd>All possible types of a MySQL column. In most cases you don't need to
2370 edit this.</dd>
2373 <dd>Possible attributes for columns. In most cases you don't need to edit
2374 this.</dd>
2377 <dd>A list of functions MySQL supports. In most cases you don't need to
2378 edit this.</dd>
2381 <dd>Mapping of column types to meta types used for preferring displayed
2382 functions. In most cases you don't need to edit this.</dd>
2385 <dd>Functions preferred for column meta types as defined in
2386 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2387 to edit this.</dd>
2390 <dd>Functions selected by default when inserting/changing row, Functions
2391 are defined for meta types from
2393 <code>first_timestamp</code>, which is used for first timestamp column
2394 in table.</dd>
2396 </dl>
2398 <!-- TRANSFORMATIONS -->
2404 </ol>
2408 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2410 section</a> on how to do so.</p>
2412 <p> You can apply different transformations to the contents of each column. The
2413 transformation will take the content of each column and transform it with
2414 certain rules defined in the selected transformation.</p>
2416 <p> Say you have a column 'filename' which contains a filename. Normally you would
2417 see in phpMyAdmin only this filename. Using transformations you can transform
2418 that filename into a HTML link, so you can click inside of the phpMyAdmin
2419 structure on the column's link and will see the file displayed in a new browser
2420 window. Using transformation options you can also specify strings to
2421 append/prepend to a string or the format you want the output stored in.</p>
2423 <p> For a general overview of all available transformations and their options,
2424 you can consult your
2425 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2426 installation.</p>
2428 <p> For a tutorial on how to effectively use transformations, see our
2430 the official phpMyAdmin homepage.</p>
2434 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2435 clicking on the 'Structure' link for a table). There click on
2436 "Change" (or change icon) and there you will see three new
2437 fields at
2438 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2439 'Transformation options'.</p>
2441 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2442 that corresponds to the column's contents. Please note that
2443 transformations are inactive as long as no MIME-type is selected.</li>
2445 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2446 hopefully growing amount of pre-defined transformations. See below for information on
2447 how to build your own transformation.<br />
2449 There are global transformations and mimetype-bound transformations. Global transformations
2450 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2451 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2452 transformations which operate on the main mimetype (like 'image'), which will most likely
2453 take the subtype into regard, and those who only operate on a
2454 specific subtype (like 'image/jpeg').<br />
2456 You can use transformations on mimetypes for which the function was not defined for. There
2457 is no security check for you selected the right transformation, so take care of what the
2458 output will be like.</li>
2460 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2461 transform-function specific options here. Usually the transforms can operate with default
2462 options, but it is generally a good idea to look up the overview to see which options are
2463 necessary.<br />
2465 Much like the ENUM/SET-Fields, you have to split up several options using the format
2466 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2467 parsed as an array, leaving the first value the first element in the array, and so
2468 forth.<br />
2470 If you want to specify a MIME character set you can define it in the transformation_options.
2471 You have to put that outside of the pre-defined options of the specific mime-transform,
2473 for which you can specify 2 options and you want to append a character set, enter "'first
2474 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2476 </ul>
2480 <p> All mimetypes and their transformations are defined through single files in
2481 the directory 'libraries/transformations/'.</p>
2483 <p> They are stored in files to ease up customization and easy adding of new
2484 transformations.</p>
2486 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2487 always work. It makes no sense to apply a transformation to a mimetype the
2488 transform-function doesn't know to handle.</p>
2490 <p> One can, however, use empty mime-types and global transformations which should work
2491 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2492 for, but pay attention to option usage as well as what the transformation does to your
2493 column.</p>
2495 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2496 any other transform function and provides some basic functions.</p>
2498 <p> There are 5 possible file names:</p>
2500 <ol><li>A mimetype+subtype transform:<br /><br />
2502 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2504 Please not that mimetype and subtype are separated via '_', which shall
2505 not be contained in their names. The transform function/filename may
2506 contain only characters which cause no problems in the file system as
2507 well as the PHP function naming convention.<br /><br />
2509 The transform function will the be called
2510 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2512 <b>Example:</b><br /><br />
2514 <tt>text_html__formatted.inc.php</tt><br />
2515 <tt>PMA_transform_text_html__formatted()</tt></li>
2517 <li>A mimetype (w/o subtype) transform:<br /><br />
2519 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2521 Please note that there are no single '_' characters.
2522 The transform function/filename may contain only characters which cause
2523 no problems in the file system as well as the PHP function naming
2524 convention.<br /><br />
2526 The transform function will the be called
2527 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2529 <b>Example:</b><br /><br />
2531 <tt>text__formatted.inc.php</tt><br />
2532 <tt>PMA_transform_text__formatted()</tt></li>
2534 <li>A mimetype+subtype without specific transform function<br /><br />
2536 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2538 Please note that there are no '__' characters in the filename. Do not
2539 use special characters in the filename causing problems with the file
2540 system.<br /><br />
2542 No transformation function is defined in the file itself.<br /><br />
2544 <b>Example:</b><br /><br />
2546 <tt>text_plain.inc.php</tt><br />
2547 (No function)</li>
2549 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2551 <tt>[mimetype].inc.php</tt><br /><br />
2553 Please note that there are no '_' characters in the filename. Do not use
2554 special characters in the filename causing problems with the file system.
2555 <br /><br />
2557 No transformation function is defined in the file itself.<br /><br />
2559 <b>Example:</b><br /><br />
2561 <tt>text.inc.php</tt><br />
2562 (No function)</li>
2564 <li>A global transform function with no specific mimetype<br /><br />
2566 <tt>global__[transform].inc.php</tt><br /><br />
2568 The transform function will the be called
2569 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2571 <b>Example:</b><br /><br />
2573 <tt>global__formatted</tt><br />
2574 <tt>PMA_transform_global__formatted()</tt></li>
2575 </ol>
2577 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2578 transform function.</p>
2580 <p> All filenames containing no '__' in themselves are not shown as valid transform
2581 functions in the dropdown.</p>
2583 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2584 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2585 without a transform function.</p>
2587 <p> To create a new transform function please see
2588 <tt>libraries/transformations/template_generator.sh</tt>.
2589 To create a new, empty mimetype please see
2590 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2592 <p> A transform function always gets passed three variables:</p>
2594 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2595 you want to transform.</li>
2596 <li><b>$options</b> - Contains any user-passed options to a transform function
2597 as an array.</li>
2598 <li><b>$meta</b> - Contains an object with information about your column.
2599 The data is drawn from the output of the
2601 function. This means, all object properties described on the
2603 available in this variable and can be used to transform a column accordingly
2604 to unsigned/zerofill/not_null/... properties.<br />
2605 The $meta->mimetype variable contains the original MIME-type of the
2606 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2607 </ol>
2609 <p> Additionally you should also provide additional function to provide
2610 information about the transformation to the user. This function should
2611 have same name as transformation function just with appended
2612 <code>_info</code> suffix. This function accepts no parameters and returns
2613 array with information about the transformation. Currently following keys
2614 can be used:
2615 </p>
2616 <dl>
2617 <dt><code>info</code></dt>
2618 <dd>Long description of the transformation.</dd>
2619 </dl>
2621 <!-- FAQ -->
2628 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2633 </ol>
2635 <p> Please have a look at our
2637 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2638 features and or interface.</p>
2644 action is required or phpMyAdmin sends a blank page or a page full of
2645 cryptic characters to my browser, what can I do?</a></h4>
2648 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2649 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2650 configuration file.<br /></p>
2655 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2656 See also the
2658 entry about PHP bugs with output buffering.<br />
2659 If your server keeps crashing, please ask for help in the various Apache
2660 support groups.</p>
2669 application misbehaved by not returning a complete set of
2671 </h4>
2673 <p> You just forgot to read the <i>install.txt</i> file from the PHP distribution.
2674 Have a look at the last message in this
2676 official PHP bug database.</p>
2681 and/or many error messages with the
2684 <p> This is a known problem with the PHP
2686 filter: it's not so stable. Please use instead the cookie authentication mode.
2687 </p>
2692 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2693 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2694 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2695 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2696 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2701 work.</a></h4>
2703 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2704 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2705 or not, and so on). So, you must have Zlib/Bzip2
2706 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2710 an error about safe mode being in effect.</a></h4>
2712 <p> Your uploaded file is saved by PHP in the "upload dir", as
2713 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2714 the system default is <i>/tmp</i>).<br />
2715 We recommend the following setup for Apache servers running in safe mode,
2716 to enable uploads of files while being reasonably secure:</p>
2718 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2719 <li>give ownership to the Apache server's user.group:
2720 <tt>chown apache.apache /tmp/php</tt></li>
2721 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2722 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2723 <li>restart Apache</li>
2724 </ul>
2731 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2732 I'm using the Apache server.</a></h4>
2734 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2735 your <i>httpd.conf</i>:</p>
2739 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2743 uploading a file from the query box.</a></h4>
2745 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2746 restrictions. However you need to create temporary directory and
2748 The uploaded files will be moved there, and after execution of your
2754 <p> The MySQL manual explains how to
2756 reset the permissions</a>.</p>
2766 </h4>
2768 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2769 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2770 names to align with current standards.</p>
2775 </h4>
2777 <p> Starting with version 2.7.0, the import engine has been re–written and these
2778 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2779 to take advantage of the new import features.</p>
2781 <p> The first things to check (or ask your host provider to check) are the
2782 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2783 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2784 All of these three settings limit the maximum size of data that can be
2785 submitted and handled by PHP. One user also said that post_max_size
2786 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2788 There exist several workarounds if your upload is too big or your
2789 hosting provider is unwilling to change the settings:</p>
2792 feature. This allows one to
2793 upload a file to the server via scp, ftp, or your favorite file transfer
2794 method. PhpMyAdmin is then able to import the files from the temporary
2796 section</a> of this document.</li>
2798 BigDump</a>) to split the files before uploading. We cannot support this
2799 or any third party applications, but are aware of users having success
2800 with it.</li>
2801 <li>If you have shell (command line) access, use MySQL to import the files
2802 directly. You can do this by issuing the "source" command from
2803 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2804 </ul>
2808 support?</a></h4>
2810 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2811 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2812 connect to your MySQL server using PHP's classic
2815 is available in PHP 5.0. The latter one should be used unless you have a
2816 good reason not to do so.<br />
2817 When compiling PHP, we strongly recommend that you manually link the MySQL
2818 extension of your choice to a MySQL client library of at least the same
2819 minor version since the one that is bundled with some PHP distributions is
2822 MariaDB is also supported (versions 5.1 and 5.2 were tested).
2823 </p>
2827 message, "Client does not support authentication protocol requested
2828 by server; consider upgrading MySQL client"</a></h5>
2830 <p> You tried to access MySQL with an old MySQL client library. The version of
2831 your MySQL client library can be checked in your phpinfo() output.
2832 In general, it should have at least the same minor version as your server
2836 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2837 changed the authentication hash and your PHP is trying to use the old method.
2839 with the proper client library to match your MySQL installation. Your
2840 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2841 More information (and several workarounds) are located in the
2843 </p>
2850 script seems not to know the font face I'm using!</a></h4>
2852 <p> The "FPDF" library we're using for this feature requires some
2853 special files to use font faces.<br />
2855 these files.</p>
2859 check PHP Configuration".</a></h4>
2861 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2862 "MySQL extension". This extension may be part of the PHP
2863 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2864 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2865 to load the extension but failed.<br /><br />
2867 Usually, the problem is solved by installing a software package called
2868 "PHP-MySQL" or something similar.</p>
2873 and I cannot log in using cookie auth.</a></h4>
2875 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2879 so I cannot upload.</a></h4>
2881 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2882 parameter is not set to "on".</p>
2886 a new table the table and column names are changed to lowercase!</a></h4>
2888 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2889 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2890 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2891 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2892 directory and add the following line to the group [mysqld]:</p>
2894 <pre>set-variable = lower_case_table_names=0</pre>
2896 <p> Next, save the file and restart the MySQL service. You can always check the
2897 value of this directive using the query</p>
2899 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2906 and I get problems, such as undefined variables when I run a
2909 <p> A tip from Jose Fandos: put a comment on the following two lines
2910 in httpd.conf, like this:</p>
2912 <pre>
2913 # mod_gzip_item_include file \.php$
2915 </pre>
2917 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2918 PHP scripts. Of course you have to restart Apache.</p>
2923 I get the error "No input file specified" when trying to
2924 run phpMyAdmin.</a></h4>
2926 <p> This is a permission problem. Right-click on the phpmyadmin folder
2927 and choose properties. Under the tab Security, click on "Add"
2928 and select the user "IUSR_machine" from the list. Now set his
2929 permissions and it should work.</p>
2933 db_structure.php with plenty of tables).</a></h4>
2936 GZIP output buffering is enabled. If you turn off it (by
2938 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2939 PHP 5.0.0.</p>
2943 message 'Errorcode: 13'. What does this mean?</a></h4>
2945 <p> This can happen due to a MySQL bug when having database / table names with
2946 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2947 To fix this, turn off this directive, convert all database and table names
2948 to lower case and turn it on again. Alternatively, there's a bug-fix
2949 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2953 and the columns are duplicated.</a></h4>
2955 <p> It is possible to configure Apache in such a way that PHP has problems
2956 interpreting .php files.</p>
2958 <p> The problems occur when two different (and conflicting) set of directives
2959 are used:</p>
2961 <pre>
2962 SetOutputFilter PHP
2963 SetInputFilter PHP
2964 </pre>
2966 <p> and</p>
2968 <pre>AddType application/x-httpd-php .php</pre>
2970 <p> In the case we saw, one set of directives was in
2971 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2972 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2973 The recommended way is with <tt>AddType</tt>, so just comment out
2974 the first set of lines and restart Apache:</p>
2976 <pre>
2977 #SetOutputFilter PHP
2978 #SetInputFilter PHP
2979 </pre>
2984 <p> This problem is known to happen when the server is running Turck MMCache
2985 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2990 <p>Yes.</p>
2991 <p>
2992 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
2993 is still maintained.
2994 </p>
2997 <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>
2999 <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>
3002 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3003 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3004 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3005 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3006 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3007 enabled.) Click <tt>OK</tt>.</li>
3008 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3009 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3010 </ol>
3014 PHP 5.0.4 on 64-bit systems?</a></h4>
3016 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3017 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3023 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
3024 the order of the server paragraph in <tt>config.inc.php</tt>.
3025 Table and script parts are optional. If you want
3026 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3027 some configuration. Following lines apply only for <a
3029 that you have enabled some features within global configuration. You need
3030 <code>Options FollowSymLinks</code> and <code>AllowOverride
3031 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3032 you need mod_rewrite to be enabled. Then you just need to create following
3033 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3034 (don't forget to change directory name inside of it):</p>
3036 <pre>
3037 RewriteEngine On
3038 RewriteBase /path_to_phpMyAdmin
3039 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3040 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3041 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3042 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3043 </pre>
3046 <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>
3048 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3049 following rewrite rule:</p>
3051 <pre>
3052 RewriteEngine On
3053 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3054 </pre>
3058 </h4>
3059 <p>
3060 There can be many explanations to this and a look at your server's
3061 error log file might give a clue.
3062 </p>
3066 password encryption in cookie auth doesn't work.</a></h4>
3068 <p> If your cluster consist of different architectures, PHP code used for
3069 encryption/decryption won't work correct. This is caused by use of
3070 pack/unpack functions in code. Only solution is to use mcrypt extension
3071 which works fine in this case.</p>
3076 <p> Yes but the default configuration values of Suhosin are known to cause
3077 problems with some operations, for example editing a table with many
3078 columns and no primary key or with textual primary key.
3079 </p>
3080 <p>
3081 Suhosin configuration might lead to malfunction in some cases and it can
3082 not be fully avoided as phpMyAdmin is kind of application which needs to
3083 transfer big amounts of columns in single HTTP request, what is something
3084 what Suhosin tries to prevent. Generally all
3085 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3086 <code>suhosin.get.*</code> directives can have negative effect on
3087 phpMyAdmin usability. You can always find in your error logs which limit
3088 did cause dropping of variable, so you can diagnose the problem and adjust
3089 matching configuration variable.
3090 </p>
3091 <p>
3092 The default values for most Suhosin configuration options will work in most
3093 scenarios, however you might want to adjust at least following parameters:
3094 </p>
3096 <ul>
3097 <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>
3098 <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>
3099 <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>
3100 <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>
3101 <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>
3102 <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>
3103 <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>
3104 <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>
3105 </ul>
3107 <p>
3109 <tt>SuhosinDisableWarning</tt> directive</a>.
3110 </p>
3114 but then my connection is redirected back to http. What can cause this
3115 behavior?</a></h4>
3117 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3118 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>
3121 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3123 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3124 Example from the Apache 2.2 documentation:</p>
3125 <pre>
3126 ProxyPass /mirror/foo/ http://backend.example.com/
3127 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3128 ProxyPassReverseCookieDomain backend.example.com public.example.com
3129 ProxyPassReverseCookiePath / /mirror/foo/
3130 </pre>
3132 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3133 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3134 This is not specific to phpmyadmin, it's just the behavior of Apache.
3135 </p>
3137 <pre>
3138 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3139 ProxyPassReverse /mirror/foo/
3140 http://backend.example.com/%7Euser/phpmyadmin
3141 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3142 </pre>
3144 <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>
3145 for more details.</p>
3149 privileges, I get an error about an unknown column.</a></h4>
3151 <p> The MySQL server's privilege tables are not up to date, you need to run
3152 the <tt>mysql_upgrade</tt> command on the server.</p>
3159 headers already sent by ..." is displayed, what's the problem?</a></h4>
3161 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3162 (I.E. no blank lines, no spaces, no characters...) neither before the
3163 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3164 tag at the end. We also got a report from a user under IIS, that used
3165 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3166 contained an end-of-line character (hex 0A) at the end; removing this character
3167 cleared his errors.</p>
3172 <p> Either there is an error with your PHP setup or your username/password is
3173 wrong. Try to make a small script which uses mysql_connect and see if it
3174 works. If it doesn't, it may be you haven't even compiled MySQL support
3175 into PHP.</p>
3179 connect to local MySQL server through socket '/tmp/mysql.sock'
3180 (111) ..." is displayed. What can I do?</a></h4>
3182 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3184 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3185 In your <i>php.ini</i> you will find a line</p>
3187 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3189 <p> change it to</p>
3191 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3193 <p> Then restart apache and it will work.</p>
3195 <p> Here is a fix suggested by Brad Ummer:</p>
3197 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3198 To do this, telnet to your server and go to the MySQL bin directory. In
3199 this directory there should be a file named <i>mysqladmin</i>. Type
3200 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3201 info about your MySQL server, including the socket
3202 (<i>/tmp/mysql.sock</i>, for example).</li>
3203 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3204 phpMyAdmin, you need to complete the socket information in the
3205 <i>config.inc.php</i>.<br />
3206 For example:
3208 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3209 <br /><br />
3211 Please also make sure that the permissions of this file allow to be readable
3212 by your webserver (i.e. '0755').</li>
3213 </ul>
3215 <p> Have also a look at the
3217 corresponding section of the MySQL documentation</a>.</p>
3221 what can I do?</a></h4>
3224 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3225 sometime.<br />
3226 Also have a look at your PHP version number: if it contains "b" or "alpha"
3227 it means you're running a testing version of PHP. That's not a so good idea,
3228 please upgrade to a plain revision.</p>
3232 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3233 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3235 <p> Check the value you set for the
3237 directive in the phpMyAdmin configuration file.</p>
3241 password: YES)"-error when trying to access a MySQL-Server on a
3242 host which is port-forwarded for my localhost.</a></h4>
3244 <p> When you are using a port on your localhost, which you redirect via
3245 port-forwarding to another host, MySQL is not resolving the localhost
3246 as expected.<br />
3247 Erik Wasser explains: The solution is: if your host is "localhost"
3248 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3249 connection for speeding up things. And that doesn't work in this configuration
3250 with port forwarding.<br />
3256 <p> Themes are configured with
3260 <br />
3262 should not delete the directory "original" or its underlying
3263 structure, because this is the system theme used by phpMyAdmin.
3264 "original" contains all images and styles, for backwards
3265 compatibility and for all themes that would not include images or css-files.
3266 <br /><br />
3269 is enabled, you can select your favorite theme on the main page. Your
3270 selected theme will be stored in a cookie.<br /><br /></p>
3272 <p> To create a theme:</p>
3274 <ul><li>make a new subdirectory (for example "your_theme_name") under
3276 (by default <tt>themes</tt>)</li>
3277 <li>copy the files and directories from "original" to
3278 "your_theme_name"</li>
3279 <li>edit the css-files in "your_theme_name/css"</li>
3280 <li>put your new images in "your_theme_name/img"</li>
3281 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3282 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3283 contain your chosen theme name, that will be visible in user interface</li>
3284 <li>make a new screenshot of your theme and save it under
3285 "your_theme_name/screen.png"</li>
3286 </ul>
3288 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3289 theme verbose name, theme generation and theme version. These versions and
3290 generations are enumerated from 1 and do not have any direct dependence on
3291 phpMyAdmin version. Themes within same generation should be backwards
3292 compatible - theme with version 2 should work in phpMyAdmin requiring
3293 version 1. Themes with different generation are incompatible.</p>
3295 <p> If you do not want to use your own symbols and buttons, remove the
3296 directory "img" in "your_theme_name". phpMyAdmin will
3297 use the default icons and buttons (from the system-theme "original").
3298 </p>
3302 what can I do?</a></h4>
3304 <p> Here are a few points to check:</p>
3306 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3308 directive empty. See also
3310 </li>
3311 <li>Maybe you have a broken PHP installation or you need to upgrade
3312 your Zend Optimizer. See
3314 http://bugs.php.net/bug.php?id=31134</a>.
3315 </li>
3316 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3317 set to the default (200) or another low value, you could get this
3318 error if your table has a high number of columns. Adjust this setting
3319 accordingly. (Thanks to Klaus Dorninger for the hint).
3320 </li>
3321 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3322 of ";" will cause this error. Replace it with "&;".
3323 </li>
3325 you might want to increase
3327 </li>
3328 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3329 </li>
3330 </ul>
3335 <p> To be able to see a progress bar during your uploads, your server must
3338 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3339 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3346 who logged out can not log in again in with the same nick.</a></h4>
3348 <p> This is related to the authentication mechanism (protocol) used by
3349 phpMyAdmin. To bypass this problem: just close all the opened
3350 browser windows and then go back to phpMyAdmin. You should be able to
3351 log in again.</p>
3355 limit error or a time limit error.</a></h4>
3357 <p> Compressed dumps are built in memory and because of this are limited to
3358 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3359 using
3361 (enabled by default). Zip exports can not be handled this way, so if you need
3362 Zip files for larger dump, you have to use another way.</p>
3366 when I rename a table or a column.</a></h4>
3368 <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>
3372 bundled with the MySQL server distribution.</a></h4>
3374 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3376 <pre>
3377 -- MySQL dump 8.22
3378 --
3379 -- Host: localhost Database: database
3380 ---------------------------------------------------------
3381 -- Server version 3.23.54
3382 </pre>
3384 <p> The invalid part of the code is the horizontal line made of dashes that
3385 appears once in every dump created with mysqldump. If you want to run your
3386 dump you have to turn it into valid MySQL. This means, you have to add a
3387 whitespace after the first two dashes of the line or add a # before it:
3388 <br />
3389 <code>
3390 -- -------------------------------------------------------<br />
3391 </code>
3392 or<br />
3393 <code>
3394 #---------------------------------------------------------
3395 </code>
3396 </p>
3403 <p> Please note that you should not use the separating string multiple times
3404 without any characters between them, or at the beginning/end of your table
3405 name. If you have to, think about using another TableSeparator or disabling
3406 that feature</p>
3411 <p> In Relation view, being able to choose a table in another database,
3412 or having more than one index column in the foreign key.<br /><br/>
3413 In Query-by-example (Query), automatic generation of the query
3414 LEFT JOIN from the foreign table.<br /><br/>
3415 </p>
3419 I get series of errors like "Warning: unable to parse url". How
3420 can this be fixed?</a></h4>
3421 <p>
3422 Your table neither have a primary key nor an unique one, so we must use a
3423 long expression to identify this row. This causes problems to parse_url
3424 function. The workaround is to create a primary or unique key.
3425 <br />
3426 </p>
3430 a MIME-Transformation onto!</a></h4>
3432 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3433 nested forms can be put inside the table where phpMyAdmin displays the results.
3434 You can, however, use any form inside of a table if keep the parent
3435 form-container with the target to tbl_row_delete.php and just put your own
3436 input-elements inside. If you use a custom submit input field, the form will
3437 submit itself to the displaying page again, where you can validate the
3438 $HTTP_POST_VARS in a transformation.
3440 For a tutorial on how to effectively use transformations, see our
3442 on the official phpMyAdmin-homepage.</p>
3446 MySQL server</a></h4>
3448 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3451 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3452 the quote-character (") is interpreted as an identifier quote character and
3453 not as a string quote character, which makes many internal phpMyAdmin
3455 statements. There is no workaround to this behaviour. News to this item will
3456 be posted in Bug report
3457 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3458 </p>
3462 more that one column with the same value
3463 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3464 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3466 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3467 can use it for the Edit and Delete links.</p>
3472 <p> phpMyAdmin uses a quick method to get the row count, and this method
3473 only returns an approximate count in the case of InnoDB tables. See
3475 a way to modify those results, but
3476 this could have a serious impact on performance.</p>
3483 containing an hyphen.
3484 </a></h4>
3485 <p>
3486 The tests I have made with MySQL 5.1.49 shows that the
3487 API does not accept this syntax for the USE command.
3488 </p>
3491 <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>
3492 <p>
3493 This has been a known limitation of phpMyAdmin since the beginning and
3494 it's not likely to be solved in the future.
3495 </p>
3497 <!-- Begin: Excel import limitations -->
3500 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3501 <p>
3502 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3503 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3504 <br /><br />
3505 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3506 </p>
3509 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3510 <p>
3511 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3512 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3513 </p>
3516 <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>
3517 <p>
3518 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3519 consider using a built-in type. These are almost always guarenteed to import correctly.
3520 </p>
3522 <!-- End: Excel import limitations -->
3523 <!-- Begin: CSV import limitations -->
3526 <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>
3527 <p>
3528 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.
3529 </p>
3531 <!-- End: CSV import limitations -->
3532 <!-- Begin: Import type-detection limitations -->
3535 <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>
3536 <p>
3537 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
3538 you will have to edit the structure to your liking post-import.
3539 <br /><br />
3540 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
3541 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.
3542 </p>
3544 <!-- End: Import type-detection limitations -->
3546 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3549 <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
3550 need to install it for each customer.
3551 </a></h4>
3552 <p>
3553 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3554 your users. The development of this feature was kindly sponsored by
3555 NetCologne GmbH.
3556 This requires a properly setup MySQL user management and phpMyAdmin
3557 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3559 </p>
3563 access.
3564 </a></h4>
3565 <p>
3566 This depends on your system.<br />
3567 If you're running a server which cannot be accessed by other people, it's
3568 sufficient to use the directory protection bundled with your webserver
3570 If other people have telnet access to your server, you should use
3571 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3572 <br /><br />
3573 Suggestions:
3574 </p>
3575 <ul>
3576 <li>
3578 </li>
3579 <li>
3580 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3581 is a user whose password is only known to you, and apache is the
3582 group under which Apache runs.
3583 </li>
3584 <li>
3585 You should use PHP safe mode, to protect from other users that try
3587 </li>
3588 </ul>
3593 </a></h4>
3594 <p>
3599 </p>
3602 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3603 authentication.
3604 </a></h4>
3608 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3609 and/or
3611 are wrong.</li>
3613 <li>You have already setup a security mechanism for the
3614 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3615 phpMyAdmin's authentication, so remove it.</li>
3616 </ul>
3623 and put the privileges you want. For example,
3625 would let a user create/manage his/her database(s).</p>
3630 <p> If you have existing rules from an old .htaccess file, you can take them
3633 be a major benefit here if your installation is suited to using it. Then
3634 you can just add those updated lines into the
3638 <p> If you want a pre-made sample, you can try this fragment. It stops the
3639 'root' user from logging in from any networks other than the private
3642 <pre>
3643 //block root from logging in except from the private networks
3644 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3645 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3646 'deny root from all',
3647 'allow root from localhost',
3651 );
3652 </pre>
3657 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3658 different than the one set in your
3660 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3661 while a domain name is defined in the config file.</p>
3666 <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>
3672 when trying to create a table with more than 14 columns.
3673 </a></h4>
3674 <p>
3675 We could reproduce this problem only under Win98/98SE. Testing under
3676 WinNT4 or Win2K, we could easily create more than 60 columns.
3677 <br />
3678 A workaround is to create a smaller number of columns, then come back to
3679 your table properties and add the other columns.
3680 </p>
3684 <p>
3685 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3686 with each script/website that use forms.<br />
3687 Upgrade or downgrade your Xitami server.
3688 </p>
3691 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3692 <p>
3693 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3694 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3695 don't seem to work.<br />
3697 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3698 the user's temporary directory, so they must be moved before closing
3699 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3702 </p>
3706 Explorer never stores the cookies.
3707 </a></h4>
3708 <p>
3709 MS Internet Explorer seems to be really buggy about cookies, at least till
3710 version 6.
3711 </p>
3715 rows.
3716 </a></h4>
3717 <p>
3719 </p>
3722 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3723 when trying to modify a row in a table with many columns, or with a text
3724 column
3725 </a></h4>
3726 <p>
3727 Your table neither have a primary key nor an unique one, so we must use a
3728 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
3729 those browsers, and this not happen in Netscape, for example. The
3730 workaround is to create a primary or unique key, or use another browser.
3731 <br />
3732 </p>
3736 page.
3737 </a></h4>
3738 <p>
3739 Some browsers support right-clicking into the frame you want to refresh,
3740 just do this in the right frame.<br />
3741 </p>
3745 query box.
3746 </a></h4>
3747 <p>
3748 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3749 Mozilla versions.<br />
3750 </p>
3754 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3755 </a></h4>
3756 <p>
3757 This is a Mozilla bug (see bug #26882 at
3759 </p>
3764 </a></h4>
3765 <p>
3766 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3767 data in octet-stream mode. Since we can't detect the specific Netscape
3768 version, we cannot workaround this bug.
3769 </p>
3773 wrong.</a></h4>
3775 <p> Please ensure that you have set your browser's character set to the one of the
3776 language file you have selected on phpMyAdmin's start page.
3777 Alternatively, you can try the auto detection mode that is supported by the
3778 recent versions of the most browsers.</p>
3781 <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
3784 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3785 Netscape and Mozilla do not have this problem.</p>
3788 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3789 I cannot manage two servers: I log in to the first one, then the other one,
3790 but if I switch back to the first, I have to log in on each operation.</a></h4>
3796 but nothing happens after that, only a blank screen.</a></h4>
3807 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3812 address and you are starting
3814 containing a domain name, or the reverse situation.</li>
3815 <li>Security settings in IE and/or Microsoft Security Center are
3816 too high, thus blocking scripts execution.</li>
3817 <li>The Windows Firewall is blocking Apache and MySQL. You must
3821 </ul>
3824 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3825 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3826 installed in their Firefox is causing the problem.</p>
3830 clause is generated when I browse a table.</a></h4>
3831 <p> This happens only when both of these conditions are met: using the
3841 </a></h4>
3842 <p>
3843 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3844 specifying a wrong column-type.<br />
3845 Common errors include:
3846 </p>
3847 <ul>
3850 </ul>
3851 <p>
3852 Also, look at the syntax chapter in the MySQL manual to confirm that your
3853 syntax is correct.
3854 </p>
3858 columns and
3859 phpMyAdmin generates only one index with those two columns.
3860 </a></h4>
3861 <p>
3862 This is the way to create a multi-columns
3863 index. If you want two indexes, create the first one when creating the
3864 table, save, then display the table properties and click the Index link to
3865 create the other index.
3866 </p>
3870 <p>
3871 Since version 2.2.3, you have a checkbox for each column that can be null.
3873 column's value. Since version 2.5.5, you have to use the checkbox to get
3875 a literal NULL in the column, and not a NULL value (this works in PHP4).
3876 </p>
3881 <p> Click on a database or table name in the left frame, the properties will be
3883 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3884 statements that can be used to recreate your database/table.
3885 <br /><br />
3887 transmit the resulting dump to your station. Depending on your PHP
3888 configuration, you will see options to compress the dump. See also the
3890 configuration variable.<br /><br />
3893 this document.</p>
3898 </a></h4>
3900 <p> Click on a database name in the left frame, the properties will be
3902 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3904 the path to your dump filename, or use the Browse button. Then click Go.
3905 <br /><br />
3907 that you upgrade to take advantage of the new features.
3908 <br /><br />
3910 in this document.
3911 </p>
3916 <p> Here is an example with the tables persons, towns and countries, all
3918 table, create it as explained in the configuration section. Then create the
3919 example tables:</p>
3921 <pre>
3922 CREATE TABLE REL_countries (
3923 country_code char(1) NOT NULL default '',
3924 description varchar(10) NOT NULL default '',
3925 PRIMARY KEY (country_code)
3926 ) TYPE=MyISAM;
3928 INSERT INTO REL_countries VALUES ('C', 'Canada');
3930 CREATE TABLE REL_persons (
3931 id tinyint(4) NOT NULL auto_increment,
3932 person_name varchar(32) NOT NULL default '',
3934 country_code char(1) NOT NULL default '',
3935 PRIMARY KEY (id)
3936 ) TYPE=MyISAM;
3938 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3939 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3941 CREATE TABLE REL_towns (
3943 description varchar(30) NOT NULL default '',
3944 PRIMARY KEY (town_code)
3945 ) TYPE=MyISAM;
3947 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3948 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3949 </pre>
3955 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3959 </ul>
3967 <li>In the columns row, choose persons.person_name and click the
3969 <li>Do the same for towns.description and countries.descriptions in the
3972 the correct joins have been generated</li>
3974 </ul>
3978 <p>
3979 Starting from the previous example, create the pma_table_info as explained
3980 in the configuration section, then browse your persons table,
3981 and move the mouse over a town code or country code.
3982 <br /><br />
3983 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3984 enables: drop-down list of possible values.
3985 </p>
3988 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3989 <p>
3992 <br /><br />
3993 Then you need to think about your schema layout. Which tables will go on
3994 which pages?
3995 </p>
3996 <ul>
4002 page and click Go. If you like, you
4004 linked tables onto the new page.</li>
4005 <li>Select the name of the new page (making sure the Edit radio button
4006 is selected) and click Go.</li>
4008 Coordinates are relative; your diagram will
4009 be automatically scaled to fit the page. When initially placing tables
4010 on the page, just pick any coordinates -- say, 50x50. After clicking
4012 position the element correctly.</li>
4014 first be sure to click the Save
4015 button beneath the list of tables and coordinates, to save any changes
4016 you made there. Then scroll all the way down, select the
4018 you want, and click Go.</li>
4019 <li>Internet Explorer for Windows may suggest an incorrect filename when
4024 browsers on Windows, do not have this problem.</li>
4025 </ul>
4029 columns!</a></h4>
4031 <p> No, it's MySQL that is doing
4037 underscores in the database name?</a></h4>
4039 <p> If you do not put a backslash before the underscore, this is a wildcard
4042 john2db ...<br /><br />
4044 If you put a backslash before the underscore, it means that the database
4045 name will have a real underscore.</p>
4049 statistics pages?</a></h4>
4060 if it already exists during the import. It does NOT drop the table after
4061 your export, it only affects the import file.</li>
4063 Otherwise, you may get an error if the table name exists but has a
4064 different structure.</li>
4066 (if any) will be included in backup.</li>
4068 column and table names formed with special characters are protected.</li>
4070 types set in the pmadb in the dump as
4072 </li>
4073 </ul>
4078 command, for better documentation (but resulting file is bigger).</li>
4080 once the INSERT verb and the table name.</li>
4083 </li>
4085 more info is provided in the
4087 but basically with this selected, invalid values are adjusted and
4088 inserted rather than causing the entire statement to fail.</li>
4089 </ul>
4093 in its name.</a></h4>
4096 is the normal way to reference a database and table name. Worse, MySQL
4097 will usually let you create a database with a dot, but then you cannot
4098 work with it, nor delete it.</p>
4104 <p>
4105 To use SQL Validator, you need PHP with
4111 module.
4112 </p>
4114 <p>
4120 usage.
4121 </p>
4123 <p>
4124 If you use the Validator, you should be aware that any
4126 submit will be stored anonymously (database/table/column names,
4127 strings, numbers replaced with generic values). The Mimer
4130 We utilize it as free SOAP service.
4131 </p>
4135 it, but MySQL says "BLOB column '...' used in key specification without
4138 <p> The right way to do this, is to create the column without any indexes,
4140 dialog. On this page, you will be able to choose your BLOB column, and
4141 set a size to the index, which is the condition to create an index on
4142 a BLOB column.</p>
4146 editing fields?</a></h4>
4148 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4149 with many editing fields (table structure changes, row editing, etc.).
4150 You can also have a look at the directive
4152 ('vertical') and see if this eases up editing for you.</p>
4156 WTF is this feature then useful for?</a></h4>
4158 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4159 on them. Otherwise you could just put a comment on the column. Because entering
4160 your own mimetype will cause serious syntax checking issues and validation,
4161 this introduces a high-risk false-user-input situation. Instead you have to
4162 initialize mimetypes using functions or empty mimetype definitions.<br />
4163 Plus, you have a whole overview of available mimetypes. Who knows all those
4164 mimetypes by heart so he/she can enter it at will?</p>
4168 can't I see any bookmarks below the query box? What is this variable for?
4169 </a></h4>
4171 <p> Any query you have executed can be stored as a bookmark on the page where the
4172 results are displayed. You will find a button labeled 'Bookmark this query'
4173 just at the end of the page.<br />
4174 As soon as you have stored a bookmark, it is related to the database you run
4175 the query on. You can now access a bookmark dropdown on each page, the query
4176 box appears on for that database.<br /><br />
4178 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4182 aware of that you HAVE to create a valid query, otherwise your query won't be
4183 even able to be stored in the database.<br />
4185 for your query will remain the way it is, but will be stripped of the /**/
4186 chars. So you can use:<br /><br />
4190 which will be expanded to<br /><br />
4194 in your query, where VARIABLE is the string you entered in the input box. If
4195 an empty string is provided, no replacements are made.<br /><br />
4197 A more complex example. Say you have stored this query:<br /><br />
4199 <br /><br />
4202 the full query will be:<br /><br />
4205 <br /><br />
4207 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4209 spaces inserted there
4210 will be later also inserted as spaces in your query and may lead to unexpected
4211 results especially when
4213 Your initial query which is going to be stored as a bookmark has to yield at
4214 least one result row so
4215 you can store the bookmark. You may have that to work around using well
4219 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4220 include exported table?</a></h4>
4222 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4223 document should look like following one (assuming you have table
4226 <pre>
4227 \documentclass{article} % or any class you want
4228 \usepackage{longtable} % for displaying table
4229 \begin{document} % start of document
4230 \include{table} % including exported table
4231 \end{document} % end of document
4232 </pre>
4236 access them.
4237 </a></h4>
4239 <p> You have one of these global privileges: CREATE
4240 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4241 enable users to see all the database names.
4244 So if your users do not need those privileges, you can remove them and their
4245 databases list will shorten.</p>
4249 possible values for a column, based on some foreign table?</a></h4>
4251 <p> You have to setup appropriate links between the tables, and also
4255 foreign table, a drop-down list of values will be available.
4256 You will see two lists of values, the first list containing the key
4257 and the display column, the second list containing the display column
4258 and the key. The reason for this is to be able to type the first
4259 letter of either the key or the display column.<br /><br />
4261 For 100 values or more, a distinct window will appear, to browse foreign
4262 key values and choose one. To change the default limit of 100, see
4263 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4267 automatically when entering Browse mode for a table?</a></h4>
4269 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4270 </p>
4274 Excel files, how can I enable that?</a></h4>
4276 <p> You can use
4278 which works out of the box, but phpMyAdmin supports direct export
4279 to Microsoft Excel version 97 and newer. For this to work, you need to set
4284 <pre>
4285 cd phpMyAdmin
4286 mkdir tmp
4287 chmod o+rwx tmp
4288 </pre>
4292 what happens to my column comments stored in pmadb?</a></h4>
4294 <p> Automatic migration of a table's pmadb-style column comments to the native
4295 ones is done whenever you enter Structure page for this table.</p>
4300 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4301 <ul>
4304 later)</li>
4307 </ul>
4311 <ol>
4312 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4313 <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>
4314 <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>
4315 <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>
4316 </ol>
4321 <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>
4327 <p>
4328 In all places where phpMyAdmin accepts format strings, you can use
4331 expanded variables depend on a context (for example, if you haven't chosen a
4332 table, you can not get the table name), but the following variables can be used:
4333 </p>
4334 <dl>
4340 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4351 </dl>
4356 <p>
4357 By clicking on the button 'toggle scratchboard' on the page
4358 where you edit x/y coordinates of those elements you can activate a
4359 scratchboard where all your elements are placed. By clicking on an
4360 element, you can move them around in the pre-defined area and the x/y
4361 coordinates will get updated dynamically. Likewise, when entering a
4362 new position directly into the input field, the new position in the
4363 scratchboard changes after your cursor leaves the input field.
4364 </p>
4365 <p>
4366 You have to click on the 'OK'-button below the tables to save the new
4367 positions. If you want to place a new element, first add it to the
4368 table of elements and then you can drag the new element around.
4369 </p>
4370 <p>
4371 By changing the paper size and the orientation you can change the size
4372 of the scratchboard as well. You can do so by just changing the
4373 dropdown field below, and the scratchboard will resize automatically,
4374 without interfering with the current placement of the elements.
4375 </p>
4376 <p>
4377 If ever an element gets out of range you can either enlarge the paper
4378 size or click on the 'reset' button to place all elements below each
4379 other.
4380 </p>
4385 <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>
4392 <p> Our Bug Tracker is located at
4394 under the Bugs section.<br /><br />
4396 But please first discuss your bug with other users:<br />
4398 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4399 </p>
4403 existing language, where do I start?</a></h4>
4405 <p> Always use latest Git version of the po file to translate. You can optionally
4407 server</a> where you can also get the latest po files and merge them
4408 with your translations. For creating a new translation simply use
4412 to do this) or ask on the mailing list to add the translation to the web
4413 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4414 </p>
4415 <p>
4416 Please note that we try not to use HTML entities like &eacute; in
4417 the translations, since we define the right character set in the file.
4418 With HTML entities, the text on JavaScript messages would not
4419 display correctly.
4420 However there are some entities that need to be there: quotes,
4421 non-breakable spaces, ampersands, less than, greater than.
4422 </p>
4423 <p>
4424 You can then put your translations, as a zip file to avoid losing special
4425 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4426 </p>
4427 <p>
4428 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4429 list, because this is where we ask for translations of new messages.
4430 </p>
4432 <p>
4433 Documentation is being translated using po4a and gettext (see
4435 for existing translations). To start, checkout
4436 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4437 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4438 and translate it online. If your language is missing, just contact
4440 you prefer to directly translate the po files, please put updated ones into our
4441 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4442 </p>
4446 phpMyAdmin. How should I proceed?</a></h4>
4451 <tt>git clone
4452 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4453 </li>
4455 <li>generate patch with your changes:
4457 </li>
4460 tracker of the phpMyAdmin project</a>.
4461 </li>
4462 </ol>
4464 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Git">our wiki</a>.</p>
4466 <p> Write access to the repository is granted only to experienced developers who
4467 have already contributed something useful to phpMyAdmin.<br />
4473 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4475 <p> Please refer to
4476 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4477 </p>
4482 <p> If you use Apache web server, phpMyAdmin exports information about
4483 authentication to the Apache environment and it can be used in Apache logs.
4484 Currently there are two variables available:
4485 </p>
4486 <dl>
4488 <dd>User name of currently active user (he does not have to be logged
4489 in).</dd>
4496 </dl>
4497 <p>
4499 </p>
4500 <pre>
4503 </pre>
4504 <p>
4505 You can then use any log analyzing tools to detect possible break-in
4506 attempts.
4507 </p>
4513 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4514 It allows you to connect to local as well as remote servers. This requires you to enter
4515 server host name, username, password, port and the name of the database. Therefore you can
4516 now synchronize your databases placed on the same server or some remote server.
4517 </p>
4519 <p>
4520 This feature is helpful for developers who need to replicate their
4521 database’s structure as well as data. Moreover, this feature not only
4522 helps replication but also facilitates the user to keep his/her database
4523 in sync with another database. Other than the full database, certain
4524 tables of the databases can also be synchronized.
4525 </p>
4527 <p>
4528 You need to fill in the host name of the server, the username and
4529 password of an user account already there in MySQL. Port is by default
4530 populated with 3306 (MySQL default port). Then the name of the database
4531 should be mentioned at the end. All the information other than the port
4532 needs to be filled explicitly for the source as well as target servers.
4533 </p>
4535 <p>
4536 After successfully passing through the authentication phase, the source and
4537 target database table names will be displayed. It will be a tabular
4538 representation.
4539 </p>
4541 <p>
4542 On the left, are listed the source database table names. Some of the
4544 are only present in source database and they need to be added to the
4545 target database in order to synchronize the target database. The tables
4547 target database.
4548 </p>
4550 <p>
4551 On the right, are listed the target database table names. There are few
4553 means that these tables are to be created in target database in order to
4554 synchronize target database with source database. Some table names
4556 only present in target database and they will remain unchanged in the
4557 target database. The column in the middle shows the difference between
4558 the source and target corresponding tables.
4559 </p>
4561 <p>
4563 letters, indicating that either Structure or Data are not up to date. By
4564 clicking on them, they will turn grey, what means that they will be synchronized.
4565 </p>
4567 <!-- DEVELOPERS -->
4570 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4571 great features have been written by other people and you too can help to
4572 make phpMyAdmin a useful tool.</p>
4574 <p> If you're planning to contribute source, please read the following
4575 information:</p>
4581 it free from other code.<br />
4582 Commonly used functions should be added to
4585 <li>Obviously, you're free to use whatever coding style you want. But
4586 please try to keep your code as simple as possible: beginners are
4587 using phpMyAdmin as an example application.<br />
4588 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4589 compliant on one hand, they fit the
4592 coding standards</a>
4593 on the other hand. Please pay attention to this.</li>
4594 <li>Please enable showing PHP errors and warnings by the
4596 configuration directive.</li>
4597 <li>Please try to keep up the file-naming conventions. Table-related stuff
4600 <li>Please use gettext wrappers around all messages
4603 script. To use translated messages, call
4605 Gettext.</li>
4609 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4610 better debug and profile their code.<br />
4611 Please see the
4613 options for more information.<br />
4614 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4615 lost during its re-entry into Earth's atmosphere and in memory of the
4616 brave men and women who gave their lives for the people of Earth.</li>
4617 </ul>
4621 <pre>
4632 </pre>
4634 <p>
4635 This program is free software; you can redistribute it and/or modify
4636 it under the terms of the GNU General Public License version 2,
4637 as published by the Free Software Foundation.
4638 </p>
4640 <p>
4641 This program is distributed in the hope that it will be useful,
4642 but WITHOUT ANY WARRANTY; without even the implied warranty of
4643 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4644 GNU General Public License for more details.
4645 </p>
4647 <p>
4648 You should have received a copy of the GNU General Public License
4649 along with this program; if not, write to the Free Software
4651 </p>
4653 <!-- CREDITS -->
4658 <ul>
4661 <ul>
4664 </ul></li>
4667 <ul>
4672 </ul></li>
4675 <ul>
4681 </ul></li>
4684 <ul>
4686 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4687 generate XHTML1.0 and CSS2 compliant codes</li>
4690 </ul></li>
4693 <ul>
4701 </ul></li>
4704 <ul>
4709 </ul></li>
4712 <ul>
4715 </ul></li>
4718 <ul>
4720 </ul></li>
4723 <ul>
4726 </ul></li>
4729 <ul>
4733 </ul></li>
4736 <ul>
4739 </ul></li>
4742 <ul>
4749 </ul></li>
4752 <ul>
4756 </ul></li>
4759 <ul>
4765 </ul></li>
4768 (http://sf.net/projects/phpmysqlformgen/)
4769 <ul>
4771 </ul></li>
4774 <ul>
4776 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4781 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4785 </ul></li>
4788 <ul>
4790 </ul></li>
4793 <ul>
4795 </ul></li>
4798 <ul>
4800 </ul></li>
4803 <ul>
4804 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4805 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4806 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4807 </ul></li>
4810 <ul>
4812 </ul></li>
4815 <ul>
4817 </ul></li>
4820 <ul>
4822 </ul></li>
4825 <ul>
4828 </ul></li>
4830 <li>Nicola Asuni (Tecnick.com)
4831 <ul>
4834 </ul></li>
4837 <ul>
4840 </ul></li>
4843 <ul>
4845 </ul></li>
4848 <ul>
4851 </ul></li>
4853 <li>Ivan A Kirillov
4854 <ul>
4856 </ul></li>
4859 <ul>
4861 </ul></li>
4864 <ul>
4867 </ul></li>
4870 <ul>
4872 </ul></li>
4875 <ul>
4877 </ul></li>
4880 <ul>
4882 </ul></li>
4885 <ul>
4887 </ul></li>
4890 <ul>
4892 </ul></li>
4895 <ul>
4899 </ul></li>
4902 <ul>
4904 </ul></li>
4907 <ul>
4909 </ul></li>
4911 <li>Barrie Leslie
4912 <ul>
4914 </ul></li>
4917 <ul>
4919 </ul></li>
4922 </ul>
4924 <p>
4925 And also to the following people who have contributed minor changes,
4926 enhancements, bugfixes or support for a new language since version 2.1.0:
4927 </p>
4929 <p>
4930 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4931 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4932 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4933 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4935 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4936 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4937 Luís V., Martijn W. van der Lee,
4938 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4940 </p>
4945 <p>
4946 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4947 to create a web-based interface to MySQL using PHP3. Although I have not
4948 used any of his source-code, there are some concepts I've borrowed from
4949 him. phpMyAdmin was created because Peter told me he wasn't going to
4950 further develop his (great) tool.
4951 </p>
4952 <p>
4953 Thanks go to
4954 </p>
4955 <ul>
4957 code for the check when dropping a table or database. He also suggested
4958 that you should be able to specify the primary key on tbl_create.php3. To
4959 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4960 well as a bug-report. Plus many smaller improvements.
4961 </li>
4963 were introduced in 1.3.0 (including quite significant ones like the
4964 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4965 bug-fixes and help.
4966 </li>
4968 language-independent by outsourcing the strings to a separate file. He
4969 also contributed the French translation.
4970 </li>
4972 tbl_select.php3, a feature to display only some columns from a table.
4973 </li>
4975 functions in tbl_change.php3. He also added the
4977 </li>
4979 servers and is a regular contributor for bug-fixes.
4980 </li>
4982 features for 2.0.6.
4983 </li>
4984 </ul>
4985 <p>
4986 The following people have contributed minor changes, enhancements, bugfixes
4987 or support for a new language:
4988 </p>
4989 <p>
4990 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4991 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4992 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4993 G. Wieggers.
4994 </p>
4995 <p>
4996 And thanks to everyone else who sent me email with suggestions, bug-reports
4997 and or just some feedback.
4998 </p>
5004 <ul>
5006 - the default name of Apache's directory-level configuration file.</li>
5010 - a software application that enables a user to display and interact with
5011 text, images, and other information typically located on a web page at a
5012 website on the World Wide Web.</li>
5014 - a free software/open source data compression algorithm and program
5015 developed by Julian Seward.</li>
5017 - an important World Wide Web technology that enables a client web browser
5018 to request data from a program executed on the Web server.</li>
5020 - a log or record of changes made to a project.</li>
5022 - a computer system that accesses a (remote) service on another computer
5023 by some kind of network.</li>
5025 - a set of data values of a particular simple type, one for each row of
5026 the table.</li>
5028 - a packet of information sent by a server to a World Wide Web browser
5029 and then sent back by the browser each time it accesses that server.</li>
5031 - Comma-separated values</li>
5034 - an organized collection of data.</li>
5037 - a PHP module that extends PHP with additional functionality.</li>
5039 - a list of commonly asked question and there answers.</li>
5041 - one part of divided data/columns.</li>
5043 - a field or group of fields in a database record that point to a key
5044 field or group of fields forming a key of another database record in some
5045 (usually different) table.</li>
5047 - the free PDF library</li>
5049 GD Graphics Library</a> - a library by Thomas Boutell and others for
5050 dynamically manipulating images.</li>
5053 - gzip is short for GNU zip, a GNU free software file compression
5054 program.</li>
5056 - any machine connected to a computer network, a node that has a hostname.</li>
5058 - the unique name by which a network attached device is known on a network.</li>
5060 (HyperText Transfer Protocol)</a>
5061 - the primary method used to transfer or convey information on the World
5062 Wide Web.</li>
5065 additional security measures.</li>
5066 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5067 - a set of Internet-based services for servers using Microsoft Windows.</li>
5069 - a feature that allows quick access to the rows in a table.</li>
5071 - a data-oriented protocol used by source and destination hosts for
5072 communicating data across a packet-switched internetwork.</li>
5074 - a unique number that devices use in order to identify and communicate
5075 with each other on a network utilizing the Internet Protocol standard.</li>
5077 (Internet Server Application Programming Interface)</a>
5078 - the API of Internet Information Services (IIS).</li>
5080 - a business or organization that offers users access to the Internet and related services.</li>
5082 - a most commonly used standard method of lossy compression for
5083 photographic images.</li>
5089 - line of personal computers is designed, developed, manufactured, and
5090 marketed by Apple Computer.</li>
5091 <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>
5092 - the operating system which is included with all currently shipping Apple
5093 Macintosh computers in the consumer and professional markets.</li>
5095 - a cryptographic library.</li>
5097 - the MCrypt PHP extension.</li>
5098 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5099 - an Internet Standard for the format of e-mail.</li>
5101 - some sort of extension for the Apache Webserver.</li>
5103 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5104 Management System (DBMS).</li>
5106 - the improved MySQL client PHP extension.</li>
5108 - the MySQL client PHP extension.</li>
5110 - open standard for office documents.</li>
5111 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5112 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5114 (Portable Document Format)</a>
5115 - a file format developed by Adobe Systems for representing two
5116 dimensional documents in a device independent and resolution independent
5117 format.</li>
5119 - the PHP Extension and Application Repository.</li>
5121 - the perl-compatible regular expression functions for PHP</li>
5123 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5124 programming language used mainly for developing server-side applications
5125 and dynamic web content, and more recently, a broader range of software
5126 applications.</li>
5128 - a connection through which data is sent and received.</li>
5130 - Request for Comments (RFC) documents are a series of memoranda
5131 encompassing new research, innovations, and methodologies applicable to
5132 Internet technologies.</li>
5136 - represents a single, implicitly structured data item in a table.</li>
5138 - a computer system that provides services to other computing
5139 systems over a network.</li>
5140 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5141 - handlers for different table types</li>
5143 - a form of inter-process communication.</li>
5145 Sockets Layer)</a>
5146 - a cryptographic protocol which provides secure communication on the Internet.</li>
5148 - a subroutine available to applications accessing a relational database system</li>
5150 - Structured Query Language</li>
5152 - a set of data elements (cells) that is organized, defined and stored as
5153 horizontal rows and vertical columns where each item can be uniquely
5154 identified by a label or key or by it?s position in relation to other items.</li>
5157 - a type of archive file format: the Tape ARchive format.</li>
5159 - one of the core protocols of the Internet protocol suite.</li>
5161 - a procedural code that is automatically executed in response to
5162 certain events on a particular table or view in a database</li>
5166 - a sequence of characters, conforming to a standardized format, that is
5167 used for referring to resources, such as documents and images on the
5168 Internet, by their location.</li>
5170 - A computer (program) that is responsible for accepting HTTP requests
5171 from clients and serving them Web pages.</li>
5173 - a W3C-recommended general-purpose markup language for creating
5174 special-purpose markup languages, capable of describing many different
5175 kinds of data.</li>
5177 - a popular data compression and archival format.</li>
5179 - an open-source, cross-platform data compression library by Jean-loup
5180 Gailly and Mark Adler.</li>
5181 </ul>
5182 </div>
5185 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5188 <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>
5189 </ul>
5191 </body>
5192 </html>