| blob | d2dea878ac92b0b45ecf3ac2978759b03d83378f |
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>
140 <li>communicate in <a href="http://www.phpmyadmin.net/home_page/translations.php">62 different languages</a>
141 </li>
142 <li>synchronize two databases residing on the same as well as remote servers
144 </li>
146 </ul>
149 <p> Many people have difficulty
150 understanding the concept of user management with regards to phpMyAdmin. When
151 a user logs in to phpMyAdmin, that username and password are passed directly
152 to MySQL. phpMyAdmin does no account management on its own (other than
153 allowing one to manipulate the MySQL user account information); all users
154 must be valid MySQL users.</p>
163 <!-- INSTALLATION -->
171 </ol>
174 phpMyAdmin does not apply any special security methods to the MySQL database
175 server. It is still the system administrator's job to grant permissions on
177 be used for this.
178 </p>
186 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
187 before uploading them to your server, as PHP seems not to like
192 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
193 Downloads page. Some kits contain only the English messages,
194 others contain all languages in UTF-8 format (this should be fine
195 in most situations), others contain all
196 languages and all character sets. We'll assume you chose a kit whose
198 </li>
199 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
201 document root. If you don't have direct access to your document root,
202 put the files in a directory on your local machine, and, after step 4,
203 transfer the directory on your web server using, for example, ftp.</li>
204 <li>Ensure that all the scripts have the appropriate owner (if PHP is
205 running in safe mode, having some scripts with an owner different
206 from the owner of other scripts will be a
211 <li>Now you must configure your installation. There are two methods that
212 can be used. Traditionally, users have hand-edited a copy of
214 provided for those who prefer a graphical installation. Creating a
215 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
216 <ul><li>To manually create the file, simply use your text editor to
219 file) in the main (top-level) phpMyAdmin directory (the one
223 default value is okay for a particular setting, there is no
225 few directives to get going, a simple configuration may look
226 like this:
227 <pre>
228 <?php
229 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
231 $i=0;
232 $i++;
233 $cfg['Servers'][$i]['auth_type'] = 'cookie';
234 ?>
235 </pre>
236 Or, if you prefer to not be prompted every time you log in:
237 <pre>
238 <?php
240 $i=0;
241 $i++;
242 $cfg['Servers'][$i]['user'] = 'root';
243 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
244 $cfg['Servers'][$i]['auth_type'] = 'config';
245 ?>
246 </pre>
247 For a full explanation of possible configuration values, see the
253 directory. This is a security measure. On a Linux/Unix system you
254 can use the following commands:
255 <pre>
256 cd phpMyAdmin
257 mkdir config # create directory for saving
258 chmod o+rw config # give it world writable permissions
259 </pre>
260 And to edit an existing configuration, copy it over first:
261 <pre>
262 cp config.inc.php config/ # copy current configuration for editing
263 chmod o+w config/config.inc.php # give it world writable permissions
264 </pre>
265 On other platforms, simply create the folder and ensure that your
274 the webserver does not have the proper permissions you may see the
276 config/</tt> directory exists and has the proper permissions -
278 and upload (via FTP or some similar means) to the proper location.<br /><br />
280 Once the file has been saved, it must be moved out of the <tt>
281 config/</tt> directory and the permissions must be reset, again
282 as a security measure:
283 <pre>
284 mv config/config.inc.php . # move file to current directory
285 chmod o-rw config.inc.php # remove world read and write permissions
286 rm -rf config # remove not needed directory
287 </pre>
288 Now the file is ready to be used. You can choose to review or edit
289 the file with your favorite editor, if you prefer to set some
290 advanced options which the setup script does not provide.</li></ul></li>
291 <li>If you are using the
293 protect the phpMyAdmin installation directory because using
294 config does not require a user to
295 enter a password to access the phpMyAdmin installation. Use of an alternate
296 authentication method is recommended, for example with
304 in your browser. phpMyAdmin should now display a welcome screen
305 and your databases, or a login dialog if using
307 authentication mode.</li>
310 Apache you can use supplied .htaccess file in that folder, for other
311 webservers, you should configure this yourself. Such configuration
312 prevents from possible path exposure and cross side scripting
313 vulnerabilities that might happen to be found in that code.</li>
314 <li>
315 It is generally good idea to protect public phpMyAdmin installation
316 against access by robots as they usually can not do anything good
318 your webserver or limit access by web server configuration. You can
321 </li>
322 </ol>
326 <p> For a whole set of new features (bookmarks, comments,
328 tracking mechanism,
330 transformation, etc.) you need to create a set of special tables. Those
331 tables can be located in your own database, or in a central database for a
332 multi-user installation (this database would then be accessed by the
333 controluser, so no other user should have rights to it).</p>
344 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
345 that you may need special (administrator) privileges to create the database
346 and tables, and that the script may need some tuning, depending on the
347 database name.</p>
352 section</a>. You will also need to have a controluser with the proper rights
359 unpacked one. Configuration files from old versions may
360 require some tweaking as some options have been changed or removed; in
362 so you better remove it from your file and just use the default one.
364 statement that you might find near the end of your configuration file.</p>
368 is version-specific.</p>
371 version 5.x or newer and if you use the phpMyAdmin configuration storage,
372 you should run the SQL script found in
379 where you want to give users access to their own database and don't want
380 them to play around with others.<br />
381 Nevertheless be aware that MS Internet Explorer seems to be really buggy
385 that your user/password pair are not in clear in the configuration file.
386 </li>
389 authentication modes are more secure: the MySQL login information does
390 not need to be set in the phpMyAdmin configuration file (except possibly
392 However, keep in mind that the password travels in plain text, unless
393 you are using the HTTPS protocol.<br />
394 In cookie mode, the password is stored, encrypted with the blowfish
395 algorithm, in a temporary cookie.</li>
407 file under the
409 $cfg['Servers'][$i]['controluser']</a></tt> and
414 only an example: use something else in your file!</b> Input these
415 statements from the phpMyAdmin SQL Query window or mysql command–line
416 client.<br />
418 if it's not the same as the MySQL server's one.
420 <pre>
421 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
422 GRANT SELECT (
423 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
424 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
425 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
426 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
427 Execute_priv, Repl_slave_priv, Repl_client_priv
428 ) ON mysql.user TO 'pma'@'localhost';
429 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
430 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
431 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
432 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
434 If you want to use the many new relation and bookmark features:
436 <pre>
438 </pre>
441 configuration storage</a> be set up).
442 <br /></li>
445 on a set of particular databases. Normally you shouldn't give global
446 privileges to an ordinary user, unless you understand the impact of those
447 privileges (for example, you are creating a superuser).<br />
451 <pre>
452 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
453 </pre>
455 What the user may now do is controlled entirely by the MySQL user
456 management system.<br />
458 authentication mode, you don't need to fill the user/password fields
460 array.</li>
461 </ul>
466 method and allows you to log in as any valid MySQL user.</li>
467 <li>Is supported with most PHP configurations. For
480 mode.</li>
481 </ul>
485 <ul><li>You can use this method as a replacement for the
487 (for example, if you're running
489 <li>Obviously, the user must enable cookies in the browser, but this is
490 now a requirement for all authentication modes.</li>
491 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
492 with the same username.</li>
493 <li>If you want to log in to arbitrary server see
498 not required.</li>
499 </ul>
503 <ul><li>This mode is a convenient way of using credentials from another
504 application to authenticate to phpMyAdmin.</li>
505 <li>The other application has to store login information into
506 session data.</li>
508 section.</li>
509 </ul>
512 <ul><li>This mode is the less secure one because it requires you to fill the
514 $cfg['Servers'][$i]['user']</a> and
516 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
517 can read your config.inc.php can discover your username and password).
518 <br />
525 is an entry explaining how to protect your configuration file.</li>
526 <li>For additional security in this mode, you may wish to consider the Host
527 authentication
529 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
531 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
532 directives.</li>
533 <li>Unlike cookie and http, does not require a user to log in when first
534 loading the phpMyAdmin site. This is by design but could allow any
535 user to access your installation. Use of some restriction method is
537 HTTP-AUTH directive or disallowing incoming HTTP requests at
538 one’s router or firewall will suffice (both of which
539 are beyond the scope of this manual but easily searchable with Google).</li>
540 </ul>
542 <p>
543 The Swekey is a low cost authentication USB key that can be used in
544 web applications.<br /><br />
545 When Swekey authentication is activated, phpMyAdmin requires the
546 users's Swekey to be plugged before entering the login page (currently
547 supported for cookie authentication mode only). Swekey Authentication is
548 disabled by default.<br /><br />
550 </p>
551 <pre>
552 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
553 </pre>
554 <p>
556 each user with their Swekey Id. It is important to place this file outside
557 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
559 users' information.<br /><br />
560 If you want to purchase a Swekey please visit
562 since this link provides funding for phpMyAdmin.
563 </p>
564 <!-- CONFIGURATION -->
568 users:</span> PHP does not seem to like
572 before saving a script you have modified.</p>
577 section to create one. This file only needs to contain the parameters you want to
578 change from their corresponding default value in
581 <p> The parameters which relate to design (like colors) are placed in
584 your site specific code to be included on start and end of each page.</p>
588 (with full path) to your phpMyAdmin installation's directory.
591 some web servers are case–sensitive.
594 Starting with version 2.3.0, it is advisable to try leaving this
595 blank. In most cases phpMyAdmin automatically detects the proper
596 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
597 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
598 A good test is to browse a table, edit a row and save it. There should
599 be an error message if phpMyAdmin is having trouble auto–detecting
600 the correct value. If you get an error that this must be set or if
601 the autodetect code fails to detect your path, please post a bug
602 report on our bug tracker so we can improve the code.</dd>
606 with master / foreign – tables (see
608 <br />
609 If you tried to set this up and it does not work for you, have a look on
611 use it. You will find a link that will analyze why those features have
612 been disabled.<br />
613 If you do not want to use those features set this variable to
617 <dd>A warning is displayed on the main page if Suhosin is detected.
619 from appearing.</dd>
622 <dd>Disable the default warning that is displayed if mcrypt is missing for
623 cookie authentication.
625 from appearing.</dd>
632 domain to call phpMyAdmin inside a frame, and is a potential security
633 hole allowing cross-frame scripting attacks.</dd>
637 algorithm to encrypt the password.<br />
639 passphrase of your choice. It will be used internally by the blowfish
640 algorithm: you won’t be prompted for this passphrase. There is
641 no maximum length for this secret.<br /><br />
643 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
644 makes a bit weaker security as this generated secret is stored in
645 session and furthermore it makes impossible to recall user name from
646 cookie.</dd>
650 MySQL servers. Therefore, a
652 been added which contains the login information for the different servers.
653 The first
655 contains the hostname of the first server, the second
657 the hostname of the second server, etc. In
659 server definition, however you can put as many as you need in
661 have to define all settings, just those you need to change).</dd>
665 $i-th MySQL-server. E.g. localhost.</dd>
670 ignores this port number and connects with the socket, so if you want
671 to connect to a port different from the default port, use
674 </dd>
678 To determine the correct socket, check your MySQL configuration or, using the
680 Among the resulting information displayed will be the socket used.</dd>
683 <dd>Whether to enable SSL for connection to MySQL server.
684 </dd>
687 <dd>What type connection to use with the MySQL server. Your options are
689 is nearly guaranteed to be available on all MySQL servers, while
690 sockets are not supported on some platforms.<br /><br />
692 To use the socket mode, your MySQL server must be on the same machine
693 as the Web server.</dd>
696 <dd>What php MySQL extension to use for the connection. Valid options are:
697 <br /><br />
700 The classic MySQL extension. This is the recommended and default
701 method at this time.<br /><br />
704 The improved MySQL extension. This extension became available
705 with php 5.0.0 and is the recommended way to connect to a server
709 <dd>Whether to use a compressed protocol for the MySQL server connection
710 or not (experimental).<br />
716 </dt>
718 all relational features (see
720 and, for a MySQL server running with
723 authentication mode).<br /><br />
726 cookie authentication modes (or 'config'
727 authentication mode since phpMyAdmin 2.2.1), you need to supply the
732 This account is used to check what databases the user will see at
733 login.<br />
737 In phpMyAdmin versions before 2.2.5, those were called
741 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
742 <dd>Whether config or cookie or
744 should be used for this server.
746 is the plain old way: username and password are stored in
748 <li>'cookie' authentication mode
750 2.2.3 allows you to log in as any valid MySQL user with the
751 help of cookies. Username and password are stored in
752 cookies during the session and password is deleted when it
753 ends. This can also allow you to log in in arbitrary server if
754 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
755 </li>
756 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
757 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
758 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
759 <li>'signon' authentication mode
761 as introduced in 2.10.0 allows you to log in from prepared PHP
762 session data or using supplied PHP script. This is useful for implementing single signon
763 from another application.
769 You need to
775 </ul>
778 for more information.
779 </dd>
781 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
782 </dt>
783 <dd>
784 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
785 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
786 specified in your configuration, a string combined of "phpMyAdmin " and either
789 </dd>
791 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
792 </dt>
793 <dd>
795 names for hardware authentication. Leave empty to deactivate this feature.
796 </dd>
800 </dt>
801 <dd>
802 When using auth_type = 'config', this is the user/password-pair
803 which phpMyAdmin will use to connect to the
804 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
805 cookie authentication is used and should be empty.</dd>
807 <span
809 </dt>
810 <dd>
811 Allow attempt to log in without password when a login with password
812 fails. This can be used together with http authentication, when
813 authentication is done some other way and phpMyAdmin gets user name
814 from auth and uses empty password for connecting to MySQL. Password
815 login is still tried first, but as fallback, no password method is
816 tried.</dd>
819 </dt>
820 <dd>
821 If set to a (an array of) database name(s), only this (these) database(s)
822 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
823 database(s) name(s) may contain MySQL wildcards characters
827 This setting is an efficient way to lower the server load since the
828 latter does not need to send MySQL requests to build the available
830 privileges rules of the MySQL database server</span>. If set, it just
831 means only these databases will be displayed but
833 <br /><br />
835 An example of using more that one database:
837 <br /><br />
839 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
840 databases in the left frame, so that you can individually arrange your databases.<br />
841 If you want to have certain databases at the top, but don't care about the others, you do not
842 need to specify all other databases. Use:
844 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
845 order.</dd>
848 </dt>
849 <dd>Regular expression for hiding some databases from unprivileged users.
850 This only hides them
851 from listing, but a user is still able to access them (using, for example,
852 the SQL query area). To limit access, use the MySQL privilege system.
853 <br /><br />
858 More information on regular expressions can be found in the
860 PCRE pattern syntax</a> portion of the PHP reference manual.
861 </dd>
864 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
865 this string will be displayed instead of the hostname in the pull-down
866 menu on the main page. This can be useful if you want to show only
867 certain databases on your system, for example. For HTTP auth, all
868 non-US-ASCII characters will be stripped.</dd>
872 </dt>
873 <dd>The name of the database containing the phpMyAdmin configuration storage.
874 <br /><br />
877 section in this document to see the benefits of this feature,
878 and for a quick way of creating this database and the needed tables.
879 <br /><br />
881 If you are the only user of this phpMyAdmin installation, you can
882 use your current database to store those special tables; in this
883 case, just put your current database name in
885 set this parameter to the name of your central database containing
886 the phpMyAdmin configuration storage.</dd>
890 </dt>
892 useful for queries you often run.<br /><br />
894 To allow the usage of this functionality:
896 <li>enter the table name in
898 </ul>
899 </dd>
903 </dt>
905 which column is a key in another table (a foreign key). phpMyAdmin
906 currently uses this to
907 <ul><li>make clickable, when you browse the master table, the data values
908 that point to the foreign table;</li>
910 when browsing the master table, if you move the mouse to a column
911 containing a foreign key (use also the 'table_info' table);<br />
914 <li>in edit/insert mode, display a drop-down list of possible foreign
918 <li>display links on the table properties page, to check referential
919 integrity (display missing foreign keys) for each described key;
920 </li>
924 schema of your database (also uses the table_coords table).</li>
925 </ul>
927 The keys can be numeric or character.<br /><br />
929 To allow the usage of this functionality:
932 configuration storage</li>
933 <li>put the relation table name in
935 <li>now as normal user open phpMyAdmin and for each one of your
936 tables where you want to use this feature, click
938 columns.
939 </li>
940 </ul>
944 future development of the cross-db relations.
945 </dd>
949 </dt>
950 <dd>
951 Since release 2.3.0 you can describe, in a special 'table_info'
952 table, which column is to be displayed as a tool-tip when moving the
953 cursor over the corresponding key.<br />
954 This configuration variable will hold the name of this special
955 table. To allow the usage of this functionality:
957 <li>put the table name in
959 'pma_table_info')</li>
960 <li>then for each table where you want to use this feature,
962 to choose the column.</li>
963 </ul>
965 </dd>
969 </dt>
972 the relations between your tables. To do this it needs two tables
977 schema output).<br /><br />
981 To allow the usage of this functionality:
984 <li>put the correct table names in
987 </ul>
990 </dd>
994 </dt>
996 Since release 2.3.0 you can store comments to describe each column for
998 <br /><br />
1000 Starting with release 2.5.0, comments are consequently used on the table
1001 property pages and table browse view, showing up as tool-tips above the
1002 column name (properties page) or embedded within the header of table in
1003 browse view. They can also be shown in a table dump. Please see the
1004 relevant configuration directives later on.<br /><br />
1006 Also new in release 2.5.0 is a MIME-transformation system which is also
1008 Transformations</a> for further information. To use the
1009 MIME-transformation system, your column_info table has to have the three
1010 new columns 'mimetype', 'transformation', 'transformation_options'.
1011 <br /><br />
1013 To allow the usage of this functionality:
1015 <li>put the table name in
1017 'pma_column_info')</li>
1020 <pre>
1021 ALTER TABLE `pma_column_comments`
1022 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1023 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1024 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1025 </pre>
1028 renamed from<br />
1031 </ul>
1032 </dd>
1036 </dt>
1039 all queries you entered manually into the phpMyAdmin interface. If you
1040 don't want to use a table-based history, you can use the JavaScript-based
1041 history. Using that, all your history items are deleted when closing the
1042 window.<br /><br />
1044 Using
1046 you can specify an amount of history items you want to have on hold. On
1047 every login, this list gets cut to the maximum amount.<br /><br />
1049 The query history is only available if JavaScript is enabled in your
1050 browser.<br /><br />
1052 To allow the usage of this functionality:
1056 (e.g. 'pma_history')
1057 </li>
1058 </ul>
1059 </dd>
1063 </dt>
1064 <dd>
1065 Since release 3.5.0 you can show recently used tables in the left navigation frame.
1066 It helps you to jump across table directly, without the need to select the database,
1067 and then select the table. Using
1069 you can configure the maximum number of recent tables shown. When you select a table
1070 from the list, it will jump to the page specified in
1071 <a href="#cfg_LeftDefaultTabTable" class="configrule">$cfg['LeftDefaultTabTable']</a>.<br/><br/>
1073 Without configuring the storage, you can still access the recently used tables,
1074 but it will disappear after you logout.<br/><br/>
1076 To allow the usage of this functionality persistently:
1078 <ul>
1081 </ul>
1082 </dd>
1086 </dt>
1087 <dd>
1088 Since release 3.5.0 phpMyAdmin can be configured to remember several things
1089 (table sorting
1091 , etc.) for browsing tables.
1092 Without configuring the storage, these features still can be used,
1093 but the values will disappear after you logout.<br/><br/>
1095 To allow the usage of these functionality persistently:
1097 <ul>
1099 <li>put the table name in <tt>$cfg['Servers'][$i]['table_uiprefs']</tt> (e.g. 'pma_table_uiprefs')</li>
1100 </ul>
1101 </dd>
1105 </dt>
1106 <dd>
1107 Since release 3.3.x a tracking mechanism is available.
1109 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1110 and data definition statements. After enabling it you can create versions of tables.
1111 <br/><br/>
1112 The creation of a version has two effects:
1114 <ul>
1116 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1117 </ul>
1119 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1120 For the report you can use filters, for example you can get a list of statements within a date range.
1121 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1122 In addition you can export the (filtered) report to a file or to a temporary database.
1123 <br/><br/>
1125 To allow the usage of this functionality:
1127 <ul>
1130 </ul>
1131 </dd>
1134 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1135 </dt>
1136 <dd>
1137 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1138 <br/><br/>
1139 If this is set to true and you create a table or view with
1141 <ul>
1144 </ul>
1146 and no version exists for it, the mechanism will
1147 create a version for you automatically.
1148 </dd>
1151 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1152 </dt>
1153 <dd>
1154 Defines the list of statements the auto-creation uses for new versions. Default value is
1155 <br/>
1157 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1158 CREATE INDEX,DROP INDEX,
1159 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1160 CREATE VIEW,ALTER VIEW,DROP VIEW,
1161 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1162 </dd>
1165 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1166 </dt>
1167 <dd>
1168 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1169 <br/><br/>
1170 </dd>
1174 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1175 </dt>
1176 <dd>
1177 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1178 <br/><br/>
1179 </dd>
1182 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1183 </dt>
1184 <dd>
1185 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1186 <br/><br/>
1187 </dd>
1191 </dt>
1192 <dd>
1193 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1194 and store them in the database.
1195 <br /><br />
1198 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1199 or, it is is unavailable, until the end of session.
1200 <br /><br />
1202 To allow the usage of this functionality:
1204 <ul>
1206 configuration storage</li>
1208 </ul>
1209 </dd>
1213 </dt>
1215 to visually manage the relations.
1216 <br /><br />
1218 To allow the usage of this functionality:
1221 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1222 </li>
1223 </ul>
1224 </dd>
1227 </dt>
1229 column_info table got enhanced with three new columns. If the above variable
1231 latest table structure available. If not, it will emit a warning to the
1232 superuser.<br /><br />
1234 You can disable this checking behavior by setting the variable to false,
1235 which should offer a performance increase.<br /><br />
1237 Recommended to set to FALSE, when you are sure, your table structure is
1238 up to date.</dd>
1240 boolean</dt>
1241 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1242 </dd>
1244 boolean</dt>
1245 <dd>Whether to allow logins without a password. The default
1247 to a MySQL server with was left with an empty password for root or
1248 on which an anonymous (blank) user is defined.
1249 </dd>
1252 </dt>
1254 authorization is disabled.<br /><br />
1257 all deny rules followed by allow rules. Access is allowed by default. Any
1258 client which does not match a Deny command or does match an Allow command
1259 will be allowed access to the server. <br /><br />
1262 applies all allow rules followed by deny rules. Access is denied by
1263 default. Any client which does not match an Allow directive or does
1264 match a Deny directive will be denied access to the server.<br /><br />
1266 If your rule order is set to 'explicit', authorization is
1267 performed in a similar fashion to rule order 'deny,allow', with the
1271 and was available in Apache by specifying allow and deny rules without
1272 setting any order.<br /><br />
1274 Please also see <a
1276 address behind proxies.
1277 </dd>
1279 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1280 </dt>
1281 <dd>The general format for the rules is as such:
1283 <pre>
1285 </pre>
1290 well (please note that those containing SERVER_ADDRESS might not be
1291 available on all webservers):
1292 <pre>
1298 </pre>
1300 Having an empty rule list is equivalent to either using
1306 following work:<br />
1308 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1309 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1310 But the following does not work:<br />
1313 Also IPv6 addresses are not supported.
1314 </dd>
1316 <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.
1317 </dd>
1318 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1320 DATABASES</tt> command used to fetch the name of available databases will
1321 probably be too slow, so it can be replaced by faster commands (see
1323 </dd>
1325 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1326 </dd>
1328 <dd>Name of PHP script to be sourced and executed to obtain
1329 login credentials. This is alternative approach to session based single
1330 signon. The script needs to provide function
1332 password, accepting single parameter of existing username (can be empty).
1334 </dd>
1335 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1336 <dd>Name of session which will be used for signon authentication method.
1338 this is session which phpMyAdmin uses internally. Takes effect only if
1340 is not configured.
1341 </dd>
1343 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1344 </dd>
1346 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1347 </dd>
1350 <dd>If you have more than one server configured, you can set
1352 that server when phpMyAdmin is started, or set it to 0 to be given a
1353 list of servers without logging in.<br />
1355 MUST be set to that server.</dd>
1358 <dd>Defines whether to refresh only parts of certain pages using Ajax
1359 techniques. Applies only where a non-Ajax behavior is possible;
1360 for example, the Designer feature is Ajax-only so this directive
1361 does not apply to it.</dd>
1364 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1365 page.</dd>
1368 <dd>The maximum number of database names to be displayed in the
1369 navigation frame and the database list.</dd>
1372 <dd>The maximum number of table names to be displayed in the
1373 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1374 when in Light mode.</dd>
1377 <dd>The maximum number of characters when a SQL query is displayed. The
1378 default limit of 1000 should be correct to avoid the display of tons
1379 of hexadecimal codes that represent BLOBs, but some users have real
1380 SQL queries that are longer than 1000 characters. Also, if a query's
1381 length exceeds this limit, this query is not saved in the history.</dd>
1384 <dd>Defines whether to use GZip output buffering for increased
1386 Set to true/false for enabling/disabling. When set to 'auto' (string),
1387 phpMyAdmin tries to enable output buffering and will automatically disable
1388 it if your browser has some problems with buffering. IE6 with a certain patch
1389 is known to cause data corruption when having enabled buffering.</dd>
1392 <dd>Whether persistent connections should be used or not (mysql_connect or
1393 mysql_pconnect).</dd>
1399 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1400 to zero, no time limit is imposed.<br />
1401 This setting is used while importing/exporting dump files and in the
1402 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1409 <dd>Set the number of bytes a script is allowed to allocate. If set
1410 to zero, no limit is imposed.<br />
1411 This setting is used while importing/exporting dump files and at some
1412 other places in phpMyAdmin so you definitely don't want to put here
1413 a too low value. It has no effect when PHP is running in safe mode.<br />
1414 You can also use any string as in php.ini, eg. '16M'. Ensure
1418 <dd>Mark used tables and make it possible to show databases with locked
1423 generated by phpMyAdmin should be displayed or not.</dd>
1426 <dd>Defines whether normal users (non-administrator) are allowed to
1427 delete their own database or not. If set as FALSE, the link "Drop
1429 mydatabase" will be rejected. Quite practical for
1431 customers.<br />
1432 Please note that this limitation of SQL queries is not as strict as
1433 when using MySQL privileges. This is due to nature of SQL queries
1434 which might be quite complicated. So this choice should be viewed as
1435 help to avoid accidental dropping rather than strict privilege
1436 limitation.</dd>
1440 displayed when you're about to lose data.</dd>
1443 <dd>Define whether the previous login should be recalled or not in cookie
1444 authentication mode.<br /><br />
1446 This is automatically disabled if you do not have configured
1448 </dd>
1451 <dd>Define how long is login cookie valid. Please note that php
1452 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1453 might limit session validity and if session is lost, login cookie is
1455 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1459 means that it will be kept for existing session. This is recommended
1460 for not trusted environments.</dd>
1463 <dd>If enabled (default), logout deletes cookies for all servers,
1464 otherwise only for current one. Setting this to false makes it easy to
1465 forget to log out from other server, when you are using more of
1466 them.</dd>
1472 <dd>Define whether phpMyAdmin will continue executing a multi-query
1473 statement if one of the queries fails. Default is to abort execution.</dd>
1476 <dd>Define whether phpMyAdmin will output the results of each query of a
1477 multi-query statement embedded into the
1482 <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.
1483 <br /><br />
1486 MySQL servers behind the firewall where your
1488 </dd>
1497 <dd>Defines whether to use a select-based menu and display only the current
1498 tables in the left frame (smaller page). Only in Non-Lightmode you can
1499 use the feature to display nested folders using
1501 </dd>
1504 <dd>In light mode, defines whether to display the names of databases (in the
1505 selector) using a tree, see also
1507 </dd>
1510 string or array</dt>
1511 <dd>The string used to separate the parts of the database name when showing
1512 them in a tree. Alternatively you can specify more strings in an array
1513 and all of them will be used as a separator.</dd>
1516 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1517 This means if you have tables like 'first__second__third' this will be
1519 If set to FALSE or empty, the feature is disabled. NOTE: You should
1520 not use this separator at the beginning or end of a
1521 table name or multiple times after another without any other
1522 characters in between.</dd>
1525 <dd>Defines how many sublevels should be displayed when splitting
1526 up tables by the above separator.</dd>
1529 <dd>The maximum number of recently used tables shown in the left navigation
1533 <dd>Defines whether to display table comment as tool-tip in left frame or
1534 not.</dd>
1537 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1538 comment and the real name. That means that if you have a table called
1539 'user0001' and add the comment 'MyName' on it, you will see the name
1540 'MyName' used consequently in the left frame and the tool-tip shows
1541 the real name of the DB.</dd>
1544 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1546 When setting this to 'nested', the Alias of the Tablename is only used
1547 to split/nest the tables according to the
1549 directive. So only the folder is called like the Alias, the tablename itself
1550 stays the real tablename.</dd>
1553 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1556 <dd>Enter URL where logo in the navigation frame will point to.
1557 For use especially with self made theme which changes this.
1566 integer</dt>
1567 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1568 list of tables in the left frame.
1573 <dd>Defines whether or not to display a server choice at the top of the left frame.
1574 Defaults to FALSE.</dd>
1576 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1577 Defaults to FALSE (drop-down).</dd>
1579 <dd>Defines whether to display database choice in light navigation frame as links
1580 instead of in a drop-down. Defaults to 'auto' - on main page list is
1581 shown, when database is selected, only drop down is displayed.</dd>
1584 <dd>Defines the tab displayed by default when clicking the small
1585 icon next to each table name in the navigation panel. Possible
1591 <dd>Defines whether or not to display space usage and statistics about databases
1592 and tables.<br />
1593 Note that statistics requires at least MySQL 3.23.3 and that, at this
1594 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1597 <dd>Defines whether to display detailed server information on main page.
1598 You can additionally hide more information by using
1600 </dd>
1605 </dt>
1608 not at the starting main (right) frame. This setting
1609 does not check MySQL commands entered directly.<br /><br />
1611 Please note that to block the usage of phpinfo() in scripts, you
1618 hard coded password value in the configuration file, end users can't
1619 be allowed to change their passwords.</dd>
1622 <dd>Defines whether to suggest a database name on the
1626 <dd>Defines whether navigation bar buttons and the right panel top menu
1627 contain text or symbols only. A value of TRUE displays icons, FALSE
1628 displays text and 'both' displays both icons and text.</dd>
1631 <dd>Defines whether a user should be displayed a
1635 <dd>Number of rows displayed when browsing a result set. If the result set
1642 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1646 option is ticked by default.</dd>
1650 from editing when browsing a table's content. Valid values are:
1655 </ul>
1656 </dd>
1659 <dd>Defines whether or not MySQL functions fields should be initially
1660 displayed in edit/insert mode. Since version 2.10, the user can
1661 toggle this setting from the interface.
1662 </dd>
1665 <dd>Defines whether or not type fields should be initially
1666 displayed in edit/insert mode. The user can
1667 toggle this setting from the interface.
1668 </dd>
1671 <dd>Defines which type of editing controls should be used for CHAR and
1672 VARCHAR columns. Possible values are:
1673 <ul><li>input - this allows to limit size of text to size of columns in
1674 MySQL, but has problems with newlines in columns</li>
1675 <li>textarea - no problems with newlines in columns, but also no
1676 length limitations</li>
1677 </ul>
1678 Default is old behavior so input.</dd>
1684 <dd>If there are fewer items than this in the set of foreign keys, then a
1685 drop-down box of foreign keys is presented, in the style described by the
1687 setting.</dd>
1690 <dd>For the foreign key drop-down fields, there are several methods of
1691 display, offering both the key and value data. The contents of the
1692 array should be one or both of the following strings:
1698 </dt>
1699 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1700 creating a dump file</dd>
1703 </dt>
1704 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1705 compressed exports. This doesn't affect smaller dumps and allows users to
1706 create larger dumps that won't otherwise fit in memory due to php
1707 memory limit. Produced files contain more GZip/BZip2 headers, but all
1708 normal programs handle this correctly.</dd>
1712 mainframe.</dd>
1716 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1721 <dd>How many columns will be utilized to display the tables on the
1722 database property view? Default is 1 column. When setting this to a
1723 value larger than 1, the type of the database will be omitted for more
1724 display space.</dd>
1728 <dd>Defines the tab displayed by default on server view. Possible
1735 <dd>Defines the tab displayed by default on database view. Possible
1740 <dd>Defines the tab displayed by default on table view. Possible
1747 points to the MySQL documentation (type depends
1748 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1749 generated.<br />
1751 for more information about MySQL manuals and their types.</dd>
1754 <dd>Type of MySQL documentation:
1760 </ul>
1761 </dd>
1764 <dd>Defines the default language to use, if not browser-defined or
1765 user-defined.<br />
1766 The corresponding language file needs to be in
1768 </dd>
1771 <dd>Defines the default connection collation to use, if not
1772 user-defined.<br />
1778 The corresponding language file needs to be in
1780 </dd>
1783 <dd>Limit list of available languages to those matching the given regular
1784 expression. For example if you want only Czech and English, you should
1788 <dd>You can select here which functions will be used for character set
1789 conversion. Possible values are:
1790 <ul><li>auto - automatically use available one (first is tested
1791 iconv, then recode)</li>
1795 </ul>
1796 Default is auto.</dd>
1797 <dd>
1798 Enabled charset conversion activates a pull-down menu
1799 in the Export and Import pages, to choose the character set when
1800 exporting a file. The default value in this menu comes from
1802 </dd>
1805 <dd>Specify some parameters for iconv used in charset conversion. See
1808 used, so that invalid characters will be transliterated.</dd>
1811 <dd>Available character sets for MySQL conversion. You can add your own (any of
1812 supported by recode/iconv) or remove these which you don't use.
1813 Character sets will be shown in same order as here listed, so if you
1814 frequently use some of these move them to the top.</dd>
1819 default empty, you need to fill in some trusted proxy servers if you
1820 want to use rules for IP addresses behind proxy.<br /><br />
1822 The following example specifies that phpMyAdmin should trust a
1824 <pre>
1825 $cfg['TrustedProxies'] =
1827 </pre>
1828 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1829 client's IP address as usual.
1830 </dd>
1834 MIME transformations.<br />
1835 Possible values are:
1836 <ul><li>auto - automatically detect, this is a bit expensive
1838 according to your server real possibilities</li>
1841 </ul>
1842 Default is auto.
1843 </dd>
1846 <dd>
1847 We normally check the permissions on the configuration file to ensure
1848 it's not world writable. However, phpMyAdmin could be installed on
1849 a NTFS filesystem mounted on a non-Windows server, in which case the
1850 permissions seems wrong but in fact cannot be detected. In this case
1852 </dd>
1855 <dd>
1856 Limit for length of URL in links. When length would be above this limit, it
1857 is replaced by form with button.
1858 This is required as some web servers (IIS) have problems with long URLs.
1860 </dd>
1862 <dt
1864 <dd>
1865 In the database Structure page, it's possible to mark some tables then
1866 choose an operation like optimizing for many tables. This can slow down
1869 </dd>
1873 </dd>
1875 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1877 </dt>
1878 <dd>The background styles used for both the frames.
1881 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1883 <dd>The style used for the pointer in the navi frame.
1892 </dd>
1896 <dd>The style used for table headers. See
1901 </dd>
1905 </dd>
1907 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1909 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1911 </dt>
1913 The former feature highlights the row over which your mouse is passing
1914 and the latter lets you visually mark/unmark rows by clicking on
1915 them. Highlighting / marking a column is done by hovering over /
1916 clicking the column's header (outside of the text).<br />
1921 <dd>You put here a valid CSS font family value, for example
1926 <dd>You put here a valid CSS font family value, for example
1940 </dt>
1942 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1944 The Char* values are used for CHAR and VARCHAR editing (if configured
1948 </dt>
1952 </dt>
1953 <dd>Defines if the whole textarea of the query box will be selected on
1954 click.</dd>
1957 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1958 Can be turned off by a toggle button on the browse page.</dd>
1961 </dt>
1962 <dd>Defines the place where table row links (Edit, Inline edit, Copy,
1963 Delete) would be put when tables contents are displayed (you may
1964 have them displayed at the left side, right side, both sides or nowhere).
1970 Define which one is displayed by default. The first mode displays each
1971 row on a horizontal line, the second rotates the headers by 90
1972 degrees, so you can use descriptive headers even though columns only
1973 contain small values and still print them out. The vertical mode sorts
1974 each row on a vertical lineup.
1975 </dd>
1981 <dd>
1982 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1983 'css' the rotation of the header for horizontalflipped is done via
1984 CSS. The CSS transformation currently works only in Internet
1985 Explorer.If set to 'fake' PHP does the transformation for you, but of
1986 course this does not look as good as CSS. The 'auto' option enables
1987 CSS transformation when browser supports it and use PHP based one
1988 otherwise.
1989 </dd>
1993 string or integer</dt>
1994 <dd>When editing/creating new columns in a table all fields normally get
1995 lined up one field a line. (default: 'horizontal'). If you set this to
1996 'vertical' you can have each field lined up vertically beneath each
1997 other. You can save up a lot of place on the horizontal direction and
1998 no longer have to scroll. If you set this to integer, editing of fewer
1999 columns will appear in 'vertical' mode, while editing of more columns
2000 still in 'horizontal' mode. This way you can still effectively edit
2001 large number of columns, while having full view on few of them.</dd>
2005 </dt>
2007 display of column comments in Browse or Property display. In browse
2008 mode, the comments are shown inside the header. In property mode,
2009 comments are displayed using a CSS-formatted dashed-line below the
2010 name of the column. The comment is shown as a tool-tip for that column.
2011 </dd>
2023 <dd>Whether to display a link to validate a query in any SQL Query box.
2030 <dd>
2031 The name of the directory where
2033 uploaded by other means than phpMyAdmin (for example, ftp). Those files
2034 are available under a drop-down box when you click the database or
2035 table name, then the Import tab.
2036 <br /><br />
2038 If you want different directory for each user, %u will be replaced
2039 with username.<br /><br />
2043 compressed formats is enabled).<br /><br />
2045 This feature is useful when your file is too big to be uploaded via
2047 uploads are disabled in PHP.<br /><br />
2049 Please note that if PHP is running in safe mode, this directory must
2050 be owned by the same user as the owner of the phpMyAdmin scripts.
2051 <br /><br />
2055 alternatives.
2056 </dd>
2059 <dd>
2060 The name of the directory where dumps can be saved.<br /><br />
2062 If you want different directory for each user, %u will be replaced
2063 with username.<br /><br />
2065 Please note that the directory must exist and has to be writable for
2066 the user running webserver.<br /><br />
2068 Please note that if PHP is running in safe mode, this directory must
2069 be owned by the same user as the owner of the phpMyAdmin scripts.
2070 </dd>
2073 <dd>
2074 The name of the directory where temporary files can be stored.
2075 <br /><br />
2077 This is needed for native MS Excel export, see
2083 <br /><br />
2085 If the directory where phpMyAdmin is installed is subject to an
2087 temporary directory in some directory accessible by the web
2088 server. However for security reasons, this directory should be outside
2089 the tree published by webserver. If you cannot avoid having this
2090 directory published by webserver, place at least an empty
2092 possible.
2093 <br /><br />
2095 This directory should have as strict permissions as possible as the only
2096 user required to access this directory is the one who runs the
2097 webserver. If you have root privileges, simply make this user owner of
2098 this directory and make it accessible only by it:
2099 <br /><br />
2101 <pre>
2102 chown www-data:www-data tmp
2103 chmod 700 tmp
2104 </pre>
2106 If you cannot change owner of the directory, you can achieve a similar
2109 <pre>
2110 chmod 700 tmp
2111 setfacl -m "g:www-data:rwx" tmp
2112 setfacl -d -m "g:www-data:rwx" tmp
2113 </pre>
2115 If neither of above works for you, you can still make the directory
2117 system reading and writing data in this directory.
2118 </dd>
2121 <dd>
2122 In this array are defined default parameters for export, names of
2123 items are similar to texts seen on export page, so you can easily
2124 identify what they mean.
2125 </dd>
2128 <dd>
2129 Defines how the export form is displayed when it loads. Valid values are:
2130 <ul>
2133 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2134 </ul>
2135 </dd>
2138 <dd>
2139 In this array are defined default parameters for import, names of
2140 items are similar to texts seen on import page, so you can easily
2141 identify what they mean.
2142 </dd>
2145 <dd>
2146 Repeat the headers every X cells, or 0 to deactivate.
2147 </dd>
2155 </dt>
2156 <dd>
2157 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2158 or icon is always displayed on the left panel. If JavaScript is enabled in
2159 your browser, a click on this opens a distinct query window, which is
2160 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2161 changes to display a query box.<br /><br />
2163 The size of this query window can be customized with
2165 - both integers for the size in pixels. Note that normally, those
2167 theme you are using.<br /><br />
2171 opens the query window and puts the current query
2172 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2173 query in the right panel's query box.
2174 <br /><br />
2175 The usage of the JavaScript query window is recommended if you have a
2176 JavaScript enabled browser. Basic functions are used to exchange quite
2177 a few variables, so most 4th generation browsers should be capable to
2178 use that feature. It currently is only tested with Internet Explorer 6
2179 and Mozilla 1.x.
2180 <br /><br />
2182 to a table, which has to be created by you (see <a
2184 all your queries will be appended to the form, but only as long as
2185 your window is opened they remain saved.
2186 <br /><br />
2187 When using the JavaScript based query window, it will always get
2188 updated when you click on a new table/db to browse and will focus if
2189 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2190 the query window by checking the box "Do not overwrite this query from
2191 outside the window" below the query textarea. Then you can browse
2192 tables/databases in the background without losing the contents of the
2193 textarea, so this is especially useful when composing a query with
2194 tables you first have to look in. The checkbox will get automatically
2195 checked whenever you change the contents of the textarea. Please
2196 uncheck the button whenever you definitely want the query window to
2197 get updated even though you have made alterations.
2198 <br /><br />
2201 <br /><br />
2202 The query window also has a custom tabbed look to group the features.
2204 default tab to be used when opening the query window. It can be set to
2205 either 'sql', 'files', 'history' or 'full'.</dd>
2211 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2213 If the approximate row count as returned by
2216 count will be used.
2217 </dd>
2219 <dd>For VIEWs, since obtaining the exact count could have an
2220 impact on performance, this value is the maximum to be displayed, using
2222 any row counting.
2223 </dd>
2226 <dd>Sorts database and table names according to natural order (for example,
2227 t1, t2, t10). Currently implemented in the left panel (Light mode)
2228 and in Database view, for the table list.</dd>
2237 that users can't set through user preferences. For possible values, refer
2244 <dd>Allows you to specify window's title bar. You can use
2246 </dd>
2256 </dd>
2259 <dd>If theme manager is active, use this as the path of the subdirectory
2260 containing all the themes.</dd>
2274 </dt>
2275 <dd>Default queries that will be displayed in query boxes when user didn't
2276 specify any. You can use standard
2278 </dd>
2281 <dd>
2282 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
2283 default we use HTML to format the query, but you can disable this by
2285 </dd>
2288 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2289 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2290 query inside a bracket is indented. By changing
2293 specifies the units of the indent amount that you specified. This is
2294 used via stylesheets.</dd>
2297 <dd>This array is used to define the colours for each type of element of
2298 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2300 If you specify an empty string for the color of a class, it is ignored
2301 in creating the stylesheet.
2302 You should not alter the class names, only the colour strings.<br />
2323 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2327 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2328 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2329 </ul>
2330 </dd>
2334 <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,
2335 as originally published on
2337 <br />
2338 For help in setting up your system to use the service, see the
2340 </dd>
2344 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2345 and any password, so we use those by default. Instead, if
2346 you have an account with them, you can put your login details
2347 here, and it will be used in place of the anonymous login.</dd>
2348 </dl>
2349 </dd>
2352 <dd><b>DEVELOPERS ONLY!</b></dd>
2355 <dd><b>DEVELOPERS ONLY!</b><br />
2356 Enable logging queries and execution times to be displayed in the bottom
2357 of main page (right frame).</dd>
2360 <dd>All possible types of a MySQL column. In most cases you don't need to
2361 edit this.</dd>
2364 <dd>Possible attributes for columns. In most cases you don't need to edit
2365 this.</dd>
2368 <dd>A list of functions MySQL supports. In most cases you don't need to
2369 edit this.</dd>
2372 <dd>Mapping of column types to meta types used for preferring displayed
2373 functions. In most cases you don't need to edit this.</dd>
2376 <dd>Functions preferred for column meta types as defined in
2377 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2378 to edit this.</dd>
2381 <dd>Functions selected by default when inserting/changing row, Functions
2382 are defined for meta types from
2384 <code>first_timestamp</code>, which is used for first timestamp column
2385 in table.</dd>
2388 <dd>Operators available for search operations on numeric and date columns.
2389 </dd>
2392 <dd>Operators available for search operations on character columns.
2393 Note that we put <code>LIKE</code> by default instead of
2394 <code>LIKE %...%</code>, to avoid unintended performance problems
2395 in case of huge tables.</dd>
2398 <dd>Operators available for search operations on ENUM columns.</dd>
2401 <dd>Additional operators available for search operations when the
2402 column can be null.</dd>
2404 </dl>
2406 <!-- TRANSFORMATIONS -->
2412 </ol>
2416 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2418 section</a> on how to do so.</p>
2420 <p> You can apply different transformations to the contents of each column. The
2421 transformation will take the content of each column and transform it with
2422 certain rules defined in the selected transformation.</p>
2424 <p> Say you have a column 'filename' which contains a filename. Normally you would
2425 see in phpMyAdmin only this filename. Using transformations you can transform
2426 that filename into a HTML link, so you can click inside of the phpMyAdmin
2427 structure on the column's link and will see the file displayed in a new browser
2428 window. Using transformation options you can also specify strings to
2429 append/prepend to a string or the format you want the output stored in.</p>
2431 <p> For a general overview of all available transformations and their options,
2432 you can consult your
2433 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2434 installation.</p>
2436 <p> For a tutorial on how to effectively use transformations, see our
2438 the official phpMyAdmin homepage.</p>
2442 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2443 clicking on the 'Structure' link for a table). There click on
2444 "Change" (or change icon) and there you will see three new
2445 fields at
2446 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2447 'Transformation options'.</p>
2449 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2450 that corresponds to the column's contents. Please note that
2451 transformations are inactive as long as no MIME-type is selected.</li>
2453 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2454 hopefully growing amount of pre-defined transformations. See below for information on
2455 how to build your own transformation.<br />
2457 There are global transformations and mimetype-bound transformations. Global transformations
2458 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2459 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2460 transformations which operate on the main mimetype (like 'image'), which will most likely
2461 take the subtype into regard, and those who only operate on a
2462 specific subtype (like 'image/jpeg').<br />
2464 You can use transformations on mimetypes for which the function was not defined for. There
2465 is no security check for you selected the right transformation, so take care of what the
2466 output will be like.</li>
2468 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2469 transform-function specific options here. Usually the transforms can operate with default
2470 options, but it is generally a good idea to look up the overview to see which options are
2471 necessary.<br />
2473 Much like the ENUM/SET-Fields, you have to split up several options using the format
2474 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2475 parsed as an array, leaving the first value the first element in the array, and so
2476 forth.<br />
2478 If you want to specify a MIME character set you can define it in the transformation_options.
2479 You have to put that outside of the pre-defined options of the specific mime-transform,
2481 for which you can specify 2 options and you want to append a character set, enter "'first
2482 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2484 </ul>
2488 <p> All mimetypes and their transformations are defined through single files in
2489 the directory 'libraries/transformations/'.</p>
2491 <p> They are stored in files to ease up customization and easy adding of new
2492 transformations.</p>
2494 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2495 always work. It makes no sense to apply a transformation to a mimetype the
2496 transform-function doesn't know to handle.</p>
2498 <p> One can, however, use empty mime-types and global transformations which should work
2499 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2500 for, but pay attention to option usage as well as what the transformation does to your
2501 column.</p>
2503 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2504 any other transform function and provides some basic functions.</p>
2506 <p> There are 5 possible file names:</p>
2508 <ol><li>A mimetype+subtype transform:<br /><br />
2510 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2512 Please not that mimetype and subtype are separated via '_', which shall
2513 not be contained in their names. The transform function/filename may
2514 contain only characters which cause no problems in the file system as
2515 well as the PHP function naming convention.<br /><br />
2517 The transform function will the be called
2518 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2520 <b>Example:</b><br /><br />
2522 <tt>text_html__formatted.inc.php</tt><br />
2523 <tt>PMA_transform_text_html__formatted()</tt></li>
2525 <li>A mimetype (w/o subtype) transform:<br /><br />
2527 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2529 Please note that there are no single '_' characters.
2530 The transform function/filename may contain only characters which cause
2531 no problems in the file system as well as the PHP function naming
2532 convention.<br /><br />
2534 The transform function will the be called
2535 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2537 <b>Example:</b><br /><br />
2539 <tt>text__formatted.inc.php</tt><br />
2540 <tt>PMA_transform_text__formatted()</tt></li>
2542 <li>A mimetype+subtype without specific transform function<br /><br />
2544 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2546 Please note that there are no '__' characters in the filename. Do not
2547 use special characters in the filename causing problems with the file
2548 system.<br /><br />
2550 No transformation function is defined in the file itself.<br /><br />
2552 <b>Example:</b><br /><br />
2554 <tt>text_plain.inc.php</tt><br />
2555 (No function)</li>
2557 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2559 <tt>[mimetype].inc.php</tt><br /><br />
2561 Please note that there are no '_' characters in the filename. Do not use
2562 special characters in the filename causing problems with the file system.
2563 <br /><br />
2565 No transformation function is defined in the file itself.<br /><br />
2567 <b>Example:</b><br /><br />
2569 <tt>text.inc.php</tt><br />
2570 (No function)</li>
2572 <li>A global transform function with no specific mimetype<br /><br />
2574 <tt>global__[transform].inc.php</tt><br /><br />
2576 The transform function will the be called
2577 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2579 <b>Example:</b><br /><br />
2581 <tt>global__formatted</tt><br />
2582 <tt>PMA_transform_global__formatted()</tt></li>
2583 </ol>
2585 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2586 transform function.</p>
2588 <p> All filenames containing no '__' in themselves are not shown as valid transform
2589 functions in the dropdown.</p>
2591 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2592 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2593 without a transform function.</p>
2595 <p> To create a new transform function please see
2596 <tt>libraries/transformations/template_generator.sh</tt>.
2597 To create a new, empty mimetype please see
2598 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2600 <p> A transform function always gets passed three variables:</p>
2602 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2603 you want to transform.</li>
2604 <li><b>$options</b> - Contains any user-passed options to a transform function
2605 as an array.</li>
2606 <li><b>$meta</b> - Contains an object with information about your column.
2607 The data is drawn from the output of the
2609 function. This means, all object properties described on the
2611 available in this variable and can be used to transform a column accordingly
2612 to unsigned/zerofill/not_null/... properties.<br />
2613 The $meta->mimetype variable contains the original MIME-type of the
2614 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2615 </ol>
2617 <p> Additionally you should also provide additional function to provide
2618 information about the transformation to the user. This function should
2619 have same name as transformation function just with appended
2620 <code>_info</code> suffix. This function accepts no parameters and returns
2621 array with information about the transformation. Currently following keys
2622 can be used:
2623 </p>
2624 <dl>
2625 <dt><code>info</code></dt>
2626 <dd>Long description of the transformation.</dd>
2627 </dl>
2629 <!-- FAQ -->
2636 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2641 </ol>
2643 <p> Please have a look at our
2645 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2646 features and or interface.</p>
2652 action is required or phpMyAdmin sends a blank page or a page full of
2653 cryptic characters to my browser, what can I do?</a></h4>
2656 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2657 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2658 configuration file.<br /></p>
2663 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2664 See also the
2666 entry about PHP bugs with output buffering.<br />
2667 If your server keeps crashing, please ask for help in the various Apache
2668 support groups.</p>
2677 application misbehaved by not returning a complete set of
2679 </h4>
2681 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2682 Have a look at the last message in this
2684 official PHP bug database.</p>
2689 and/or many error messages with the
2692 <p> This is a known problem with the PHP
2694 filter: it's not so stable. Please use instead the cookie authentication mode.
2695 </p>
2700 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2701 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2702 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2703 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2704 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2709 work.</a></h4>
2711 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2712 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2713 or not, and so on). So, you must have Zlib/Bzip2
2714 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2718 an error about safe mode being in effect.</a></h4>
2720 <p> Your uploaded file is saved by PHP in the "upload dir", as
2721 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2722 the system default is <i>/tmp</i>).<br />
2723 We recommend the following setup for Apache servers running in safe mode,
2724 to enable uploads of files while being reasonably secure:</p>
2726 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2727 <li>give ownership to the Apache server's user.group:
2728 <tt>chown apache.apache /tmp/php</tt></li>
2729 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2730 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2731 <li>restart Apache</li>
2732 </ul>
2739 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2740 I'm using the Apache server.</a></h4>
2742 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2743 your <i>httpd.conf</i>:</p>
2747 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2751 uploading a file from the query box.</a></h4>
2753 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2754 restrictions. However you need to create temporary directory and
2756 The uploaded files will be moved there, and after execution of your
2762 <p> The MySQL manual explains how to
2764 reset the permissions</a>.</p>
2774 </h4>
2776 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2777 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2778 names to align with current standards.</p>
2783 </h4>
2785 <p> Starting with version 2.7.0, the import engine has been re–written and these
2786 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2787 to take advantage of the new import features.</p>
2789 <p> The first things to check (or ask your host provider to check) are the
2790 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2791 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2792 All of these three settings limit the maximum size of data that can be
2793 submitted and handled by PHP. One user also said that post_max_size
2794 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2796 There exist several workarounds if your upload is too big or your
2797 hosting provider is unwilling to change the settings:</p>
2800 feature. This allows one to
2801 upload a file to the server via scp, ftp, or your favorite file transfer
2802 method. PhpMyAdmin is then able to import the files from the temporary
2804 section</a> of this document.</li>
2806 BigDump</a>) to split the files before uploading. We cannot support this
2807 or any third party applications, but are aware of users having success
2808 with it.</li>
2809 <li>If you have shell (command line) access, use MySQL to import the files
2810 directly. You can do this by issuing the "source" command from
2811 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2812 </ul>
2816 support?</a></h4>
2818 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2819 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2820 connect to your MySQL server using PHP's classic
2823 is available in php 5.0. The latter one should be used unless you have a
2824 good reason not to do so.<br />
2825 When compiling PHP, we strongly recommend that you manually link the MySQL
2826 extension of your choice to a MySQL client library of at least the same
2827 minor version since the one that is bundled with some PHP distributions is
2830 MariaDB is also supported (versions 5.1 and 5.2 were tested).
2831 </p>
2835 message, "Client does not support authentication protocol requested
2836 by server; consider upgrading MySQL client"</a></h5>
2838 <p> You tried to access MySQL with an old MySQL client library. The version of
2839 your MySQL client library can be checked in your phpinfo() output.
2840 In general, it should have at least the same minor version as your server
2844 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2845 changed the authentication hash and your PHP is trying to use the old method.
2847 with the proper client library to match your MySQL installation. Your
2848 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2849 More information (and several workarounds) are located in the
2851 </p>
2858 script seems not to know the font face I'm using!</a></h4>
2860 <p> The "FPDF" library we're using for this feature requires some
2861 special files to use font faces.<br />
2863 these files.</p>
2867 check PHP Configuration".</a></h4>
2869 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2870 "MySQL extension". This extension may be part of the PHP
2871 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2872 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2873 to load the extension but failed.<br /><br />
2875 Usually, the problem is solved by installing a software package called
2876 "PHP-MySQL" or something similar.</p>
2881 and I cannot log in using cookie auth.</a></h4>
2883 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2887 so I cannot upload.</a></h4>
2889 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2890 parameter is not set to "on".</p>
2894 a new table the table and column names are changed to lowercase!</a></h4>
2896 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2897 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2898 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2899 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2900 directory and add the following line to the group [mysqld]:</p>
2902 <pre>set-variable = lower_case_table_names=0</pre>
2904 <p> Next, save the file and restart the MySQL service. You can always check the
2905 value of this directive using the query</p>
2907 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2914 and I get problems, such as undefined variables when I run a
2917 <p> A tip from Jose Fandos: put a comment on the following two lines
2918 in httpd.conf, like this:</p>
2920 <pre>
2921 # mod_gzip_item_include file \.php$
2923 </pre>
2925 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2926 PHP scripts. Of course you have to restart Apache.</p>
2931 I get the error "No input file specified" when trying to
2932 run phpMyAdmin.</a></h4>
2934 <p> This is a permission problem. Right-click on the phpmyadmin folder
2935 and choose properties. Under the tab Security, click on "Add"
2936 and select the user "IUSR_machine" from the list. Now set his
2937 permissions and it should work.</p>
2941 db_structure.php with plenty of tables).</a></h4>
2944 GZIP output buffering is enabled. If you turn off it (by
2946 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2947 PHP 5.0.0.</p>
2951 message 'Errorcode: 13'. What does this mean?</a></h4>
2953 <p> This can happen due to a MySQL bug when having database / table names with
2954 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2955 To fix this, turn off this directive, convert all database and table names
2956 to lower case and turn it on again. Alternatively, there's a bug-fix
2957 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2961 and the columns are duplicated.</a></h4>
2963 <p> It is possible to configure Apache in such a way that PHP has problems
2964 interpreting .php files.</p>
2966 <p> The problems occur when two different (and conflicting) set of directives
2967 are used:</p>
2969 <pre>
2970 SetOutputFilter PHP
2971 SetInputFilter PHP
2972 </pre>
2974 <p> and</p>
2976 <pre>AddType application/x-httpd-php .php</pre>
2978 <p> In the case we saw, one set of directives was in
2979 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2980 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2981 The recommended way is with <tt>AddType</tt>, so just comment out
2982 the first set of lines and restart Apache:</p>
2984 <pre>
2985 #SetOutputFilter PHP
2986 #SetInputFilter PHP
2987 </pre>
2992 <p> This problem is known to happen when the server is running Turck MMCache
2993 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2998 <p>Yes.</p>
2999 <p>
3000 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
3001 is still maintained.
3002 </p>
3005 <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>
3007 <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>
3010 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3011 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3012 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3013 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3014 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3015 enabled.) Click <tt>OK</tt>.</li>
3016 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3017 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3018 </ol>
3022 PHP 5.0.4 on 64-bit systems?</a></h4>
3024 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3025 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3031 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
3032 the order of the server paragraph in <tt>config.inc.php</tt>.
3033 Table and script parts are optional. If you want
3034 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3035 some configuration. Following lines apply only for <a
3037 that you have enabled some features within global configuration. You need
3038 <code>Options FollowSymLinks</code> and <code>AllowOverride
3039 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3040 you need mod_rewrite to be enabled. Then you just need to create following
3041 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3042 (don't forget to change directory name inside of it):</p>
3044 <pre>
3045 RewriteEngine On
3046 RewriteBase /path_to_phpMyAdmin
3047 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3048 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3049 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3050 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3051 </pre>
3054 <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>
3056 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3057 following rewrite rule:</p>
3059 <pre>
3060 RewriteEngine On
3061 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3062 </pre>
3066 </h4>
3067 <p>
3068 There can be many explanations to this and a look at your server's
3069 error log file might give a clue.
3070 </p>
3074 password encryption in cookie auth doesn't work.</a></h4>
3076 <p> If your cluster consist of different architectures, PHP code used for
3077 encryption/decryption won't work correct. This is caused by use of
3078 pack/unpack functions in code. Only solution is to use mcrypt extension
3079 which works fine in this case.</p>
3084 <p> Yes but the default configuration values of Suhosin are known to cause
3085 problems with some operations, for example editing a table with many
3086 columns and no primary key or with textual primary key.
3087 </p>
3088 <p>
3089 Suhosin configuration might lead to malfunction in some cases and it can
3090 not be fully avoided as phpMyAdmin is kind of application which needs to
3091 transfer big amounts of columns in single HTTP request, what is something
3092 what Suhosin tries to prevent. Generally all
3093 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3094 <code>suhosin.get.*</code> directives can have negative effect on
3095 phpMyAdmin usability. You can always find in your error logs which limit
3096 did cause dropping of variable, so you can diagnose the problem and adjust
3097 matching configuration variable.
3098 </p>
3099 <p>
3100 The default values for most Suhosin configuration options will work in most
3101 scenarios, however you might want to adjust at least following parameters:
3102 </p>
3104 <ul>
3105 <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>
3106 <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>
3107 <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>
3108 <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>
3109 <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>
3110 <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>
3111 <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>
3112 <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>
3113 </ul>
3115 <p>
3117 <tt>SuhosinDisableWarning</tt> directive</a>.
3118 </p>
3122 but then my connection is redirected back to http. What can cause this
3123 behavior?</a></h4>
3125 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3126 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>
3129 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3131 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3132 Example from the Apache 2.2 documentation:</p>
3133 <pre>
3134 ProxyPass /mirror/foo/ http://backend.example.com/
3135 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3136 ProxyPassReverseCookieDomain backend.example.com public.example.com
3137 ProxyPassReverseCookiePath / /mirror/foo/
3138 </pre>
3140 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3141 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3142 This is not specific to phpmyadmin, it's just the behavior of Apache.
3143 </p>
3145 <pre>
3146 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3147 ProxyPassReverse /mirror/foo/
3148 http://backend.example.com/%7Euser/phpmyadmin
3149 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3150 </pre>
3152 <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>
3153 for more details.</p>
3157 privileges, I get an error about an unknown column.</a></h4>
3159 <p> The MySQL server's privilege tables are not up to date, you need to run
3160 the <tt>mysql_upgrade</tt> command on the server.</p>
3167 headers already sent by ..." is displayed, what's the problem?</a></h4>
3169 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3170 (I.E. no blank lines, no spaces, no characters...) neither before the
3171 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3172 tag at the end. We also got a report from a user under IIS, that used
3173 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3174 contained an end-of-line character (hex 0A) at the end; removing this character
3175 cleared his errors.</p>
3180 <p> Either there is an error with your PHP setup or your username/password is
3181 wrong. Try to make a small script which uses mysql_connect and see if it
3182 works. If it doesn't, it may be you haven't even compiled MySQL support
3183 into PHP.</p>
3187 connect to local MySQL server through socket '/tmp/mysql.sock'
3188 (111) ..." is displayed. What can I do?</a></h4>
3190 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3192 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3193 In your <i>php.ini</i> you will find a line</p>
3195 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3197 <p> change it to</p>
3199 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3201 <p> Then restart apache and it will work.</p>
3203 <p> Here is a fix suggested by Brad Ummer:</p>
3205 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3206 To do this, telnet to your server and go to the MySQL bin directory. In
3207 this directory there should be a file named <i>mysqladmin</i>. Type
3208 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3209 info about your MySQL server, including the socket
3210 (<i>/tmp/mysql.sock</i>, for example).</li>
3211 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3212 phpMyAdmin, you need to complete the socket information in the
3213 <i>config.inc.php</i>.<br />
3214 For example:
3216 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3217 <br /><br />
3219 Please also make sure that the permissions of this file allow to be readable
3220 by your webserver (i.e. '0755').</li>
3221 </ul>
3223 <p> Have also a look at the
3225 corresponding section of the MySQL documentation</a>.</p>
3229 what can I do?</a></h4>
3232 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3233 sometime.<br />
3234 Also have a look at your PHP version number: if it contains "4.0b..."
3235 it means you're running a beta version of PHP. That's not a so good idea,
3236 please upgrade to a plain revision.</p>
3240 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3241 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3243 <p> Check the value you set for the
3245 directive in the phpMyAdmin configuration file.</p>
3249 password: YES)"-error when trying to access a MySQL-Server on a
3250 host which is port-forwarded for my localhost.</a></h4>
3252 <p> When you are using a port on your localhost, which you redirect via
3253 port-forwarding to another host, MySQL is not resolving the localhost
3254 as expected.<br />
3255 Erik Wasser explains: The solution is: if your host is "localhost"
3256 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3257 connection for speeding up things. And that doesn't work in this configuration
3258 with port forwarding.<br />
3264 <p> Themes are configured with
3268 <br />
3270 should not delete the directory "original" or its underlying
3271 structure, because this is the system theme used by phpMyAdmin.
3272 "original" contains all images and styles, for backwards
3273 compatibility and for all themes that would not include images or css-files.
3274 <br /><br />
3277 is enabled, you can select your favorite theme on the main page. Your
3278 selected theme will be stored in a cookie.<br /><br /></p>
3280 <p> To create a theme:</p>
3282 <ul><li>make a new subdirectory (for example "your_theme_name") under
3284 (by default <tt>themes</tt>)</li>
3285 <li>copy the files and directories from "original" to
3286 "your_theme_name"</li>
3287 <li>edit the css-files in "your_theme_name/css"</li>
3288 <li>put your new images in "your_theme_name/img"</li>
3289 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3290 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3291 contain your chosen theme name, that will be visible in user interface</li>
3292 <li>make a new screenshot of your theme and save it under
3293 "your_theme_name/screen.png"</li>
3294 </ul>
3296 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3297 theme verbose name, theme generation and theme version. These versions and
3298 generations are enumerated from 1 and do not have any direct dependence on
3299 phpMyAdmin version. Themes within same generation should be backwards
3300 compatible - theme with version 2 should work in phpMyAdmin requiring
3301 version 1. Themes with different generation are incompatible.</p>
3303 <p> If you do not want to use your own symbols and buttons, remove the
3304 directory "img" in "your_theme_name". phpMyAdmin will
3305 use the default icons and buttons (from the system-theme "original").
3306 </p>
3310 what can I do?</a></h4>
3312 <p> Here are a few points to check:</p>
3314 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3316 directive empty. See also
3318 </li>
3319 <li>Maybe you have a broken PHP installation or you need to upgrade
3320 your Zend Optimizer. See
3322 http://bugs.php.net/bug.php?id=31134</a>.
3323 </li>
3324 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3325 set to the default (200) or another low value, you could get this
3326 error if your table has a high number of columns. Adjust this setting
3327 accordingly. (Thanks to Klaus Dorninger for the hint).
3328 </li>
3329 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3330 of ";" will cause this error. Replace it with "&;".
3331 </li>
3333 you might want to increase
3335 </li>
3336 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3337 </li>
3338 </ul>
3343 <p> To be able to see a progress bar during your uploads, your server must
3346 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3347 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3354 who logged out can not log in again in with the same nick.</a></h4>
3356 <p> This is related to the authentication mechanism (protocol) used by
3357 phpMyAdmin. To bypass this problem: just close all the opened
3358 browser windows and then go back to phpMyAdmin. You should be able to
3359 log in again.</p>
3363 limit error or a time limit error.</a></h4>
3365 <p> Compressed dumps are built in memory and because of this are limited to
3366 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3367 using
3369 (enabled by default). Zip exports can not be handled this way, so if you need
3370 Zip files for larger dump, you have to use another way.</p>
3374 when I rename a table or a column.</a></h4>
3376 <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>
3380 bundled with the MySQL server distribution.</a></h4>
3382 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3384 <pre>
3385 -- MySQL dump 8.22
3386 --
3387 -- Host: localhost Database: database
3388 ---------------------------------------------------------
3389 -- Server version 3.23.54
3390 </pre>
3392 <p> The invalid part of the code is the horizontal line made of dashes that
3393 appears once in every dump created with mysqldump. If you want to run your
3394 dump you have to turn it into valid MySQL. This means, you have to add a
3395 whitespace after the first two dashes of the line or add a # before it:
3396 <br />
3397 <code>
3398 -- -------------------------------------------------------<br />
3399 </code>
3400 or<br />
3401 <code>
3402 #---------------------------------------------------------
3403 </code>
3404 </p>
3411 <p> Please note that you should not use the separating string multiple times
3412 without any characters between them, or at the beginning/end of your table
3413 name. If you have to, think about using another TableSeparator or disabling
3414 that feature</p>
3419 <p> In Relation view, being able to choose a table in another database,
3420 or having more than one index column in the foreign key.<br /><br/>
3421 In Query-by-example (Query), automatic generation of the query
3422 LEFT JOIN from the foreign table.<br /><br/>
3423 </p>
3427 I get series of errors like "Warning: unable to parse url". How
3428 can this be fixed?</a></h4>
3429 <p>
3430 Your table neither have a primary key nor an unique one, so we must use a
3431 long expression to identify this row. This causes problems to parse_url
3432 function. The workaround is to create a primary or unique key.
3433 <br />
3434 </p>
3438 a MIME-Transformation onto!</a></h4>
3440 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3441 nested forms can be put inside the table where phpMyAdmin displays the results.
3442 You can, however, use any form inside of a table if keep the parent
3443 form-container with the target to tbl_row_delete.php and just put your own
3444 input-elements inside. If you use a custom submit input field, the form will
3445 submit itself to the displaying page again, where you can validate the
3446 $HTTP_POST_VARS in a transformation.
3448 For a tutorial on how to effectively use transformations, see our
3450 on the official phpMyAdmin-homepage.</p>
3454 MySQL server</a></h4>
3456 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3459 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3460 the quote-character (") is interpreted as an identifier quote character and
3461 not as a string quote character, which makes many internal phpMyAdmin
3463 statements. There is no workaround to this behaviour. News to this item will
3464 be posted in Bug report
3465 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3466 </p>
3470 more that one column with the same value
3471 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3472 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3474 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3475 can use it for the Edit and Delete links.</p>
3480 <p> phpMyAdmin uses a quick method to get the row count, and this method
3481 only returns an approximate count in the case of InnoDB tables. See
3483 a way to modify those results, but
3484 this could have a serious impact on performance.</p>
3491 containing an hyphen.
3492 </a></h4>
3493 <p>
3494 The tests I have made with MySQL 5.1.49 shows that the
3495 API does not accept this syntax for the USE command.
3496 </p>
3499 <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>
3500 <p>
3501 This has been a known limitation of phpMyAdmin since the beginning and
3502 it's not likely to be solved in the future.
3503 </p>
3505 <!-- Begin: Excel import limitations -->
3508 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3509 <p>
3510 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3511 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3512 <br /><br />
3513 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3514 </p>
3517 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3518 <p>
3519 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3520 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3521 </p>
3524 <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>
3525 <p>
3526 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3527 consider using a built-in type. These are almost always guarenteed to import correctly.
3528 </p>
3530 <!-- End: Excel import limitations -->
3531 <!-- Begin: CSV import limitations -->
3534 <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>
3535 <p>
3536 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.
3537 </p>
3539 <!-- End: CSV import limitations -->
3540 <!-- Begin: Import type-detection limitations -->
3543 <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>
3544 <p>
3545 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
3546 you will have to edit the structure to your liking post-import.
3547 <br /><br />
3548 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
3549 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.
3550 </p>
3552 <!-- End: Import type-detection limitations -->
3554 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3557 <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
3558 need to install it for each customer.
3559 </a></h4>
3560 <p>
3561 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3562 your users. The development of this feature was kindly sponsored by
3563 NetCologne GmbH.
3564 This requires a properly setup MySQL user management and phpMyAdmin
3565 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3567 </p>
3571 access.
3572 </a></h4>
3573 <p>
3574 This depends on your system.<br />
3575 If you're running a server which cannot be accessed by other people, it's
3576 sufficient to use the directory protection bundled with your webserver
3578 If other people have telnet access to your server, you should use
3579 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3580 <br /><br />
3581 Suggestions:
3582 </p>
3583 <ul>
3584 <li>
3586 </li>
3587 <li>
3588 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3589 is a user whose password is only known to you, and apache is the
3590 group under which Apache runs.
3591 </li>
3592 <li>
3593 You should use PHP safe mode, to protect from other users that try
3595 </li>
3596 </ul>
3601 </a></h4>
3602 <p>
3607 </p>
3610 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3611 authentication.
3612 </a></h4>
3616 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3617 and/or
3619 are wrong.</li>
3621 <li>You have already setup a security mechanism for the
3622 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3623 phpMyAdmin's authentication, so remove it.</li>
3624 </ul>
3631 and put the privileges you want. For example,
3633 would let a user create/manage his/her database(s).</p>
3638 <p> If you have existing rules from an old .htaccess file, you can take them
3641 be a major benefit here if your installation is suited to using it. Then
3642 you can just add those updated lines into the
3646 <p> If you want a pre-made sample, you can try this fragment. It stops the
3647 'root' user from logging in from any networks other than the private
3650 <pre>
3651 //block root from logging in except from the private networks
3652 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3653 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3654 'deny root from all',
3655 'allow root from localhost',
3659 );
3660 </pre>
3665 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3666 different than the one set in your
3668 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3669 while a domain name is defined in the config file.</p>
3674 <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>
3680 when trying to create a table with more than 14 columns.
3681 </a></h4>
3682 <p>
3683 We could reproduce this problem only under Win98/98SE. Testing under
3684 WinNT4 or Win2K, we could easily create more than 60 columns.
3685 <br />
3686 A workaround is to create a smaller number of columns, then come back to
3687 your table properties and add the other columns.
3688 </p>
3692 <p>
3693 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3694 with each script/website that use forms.<br />
3695 Upgrade or downgrade your Xitami server.
3696 </p>
3699 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3700 <p>
3701 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3702 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3703 don't seem to work.<br />
3705 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3706 the user's temporary directory, so they must be moved before closing
3707 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3710 </p>
3714 Explorer never stores the cookies.
3715 </a></h4>
3716 <p>
3717 MS Internet Explorer seems to be really buggy about cookies, at least till
3718 version 6.
3719 </p>
3723 rows.
3724 </a></h4>
3725 <p>
3727 </p>
3730 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3731 when trying to modify a row in a table with many columns, or with a text
3732 column
3733 </a></h4>
3734 <p>
3735 Your table neither have a primary key nor an unique one, so we must use a
3736 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
3737 those browsers, and this not happen in Netscape, for example. The
3738 workaround is to create a primary or unique key, or use another browser.
3739 <br />
3740 </p>
3744 page.
3745 </a></h4>
3746 <p>
3747 Some browsers support right-clicking into the frame you want to refresh,
3748 just do this in the right frame.<br />
3749 </p>
3753 query box.
3754 </a></h4>
3755 <p>
3756 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3757 Mozilla versions.<br />
3758 </p>
3762 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3763 </a></h4>
3764 <p>
3765 This is a Mozilla bug (see bug #26882 at
3767 </p>
3772 </a></h4>
3773 <p>
3774 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3775 data in octet-stream mode. Since we can't detect the specific Netscape
3776 version, we cannot workaround this bug.
3777 </p>
3781 wrong.</a></h4>
3783 <p> Please ensure that you have set your browser's character set to the one of the
3784 language file you have selected on phpMyAdmin's start page.
3785 Alternatively, you can try the auto detection mode that is supported by the
3786 recent versions of the most browsers.</p>
3789 <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
3792 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3793 Netscape and Mozilla do not have this problem.</p>
3796 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3797 I cannot manage two servers: I log in to the first one, then the other one,
3798 but if I switch back to the first, I have to log in on each operation.</a></h4>
3804 but nothing happens after that, only a blank screen.</a></h4>
3815 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3820 address and you are starting
3822 containing a domain name, or the reverse situation.</li>
3823 <li>Security settings in IE and/or Microsoft Security Center are
3824 too high, thus blocking scripts execution.</li>
3825 <li>The Windows Firewall is blocking Apache and MySQL. You must
3829 </ul>
3832 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3833 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3834 installed in their Firefox is causing the problem.</p>
3838 clause is generated when I browse a table.</a></h4>
3839 <p> This happens only when both of these conditions are met: using the
3849 </a></h4>
3850 <p>
3851 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3852 specifying a wrong column-type.<br />
3853 Common errors include:
3854 </p>
3855 <ul>
3858 </ul>
3859 <p>
3860 Also, look at the syntax chapter in the MySQL manual to confirm that your
3861 syntax is correct.
3862 </p>
3866 columns and
3867 phpMyAdmin generates only one index with those two columns.
3868 </a></h4>
3869 <p>
3870 This is the way to create a multi-columns
3871 index. If you want two indexes, create the first one when creating the
3872 table, save, then display the table properties and click the Index link to
3873 create the other index.
3874 </p>
3878 <p>
3879 Since version 2.2.3, you have a checkbox for each column that can be null.
3881 column's value. Since version 2.5.5, you have to use the checkbox to get
3883 a literal NULL in the column, and not a NULL value (this works in PHP4).
3884 </p>
3889 <p> Click on a database or table name in the left frame, the properties will be
3891 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3892 statements that can be used to recreate your database/table.
3893 <br /><br />
3895 transmit the resulting dump to your station. Depending on your PHP
3896 configuration, you will see options to compress the dump. See also the
3898 configuration variable.<br /><br />
3901 this document.</p>
3906 </a></h4>
3908 <p> Click on a database name in the left frame, the properties will be
3910 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3912 the path to your dump filename, or use the Browse button. Then click Go.
3913 <br /><br />
3915 that you upgrade to take advantage of the new features.
3916 <br /><br />
3918 in this document.
3919 </p>
3924 <p> Here is an example with the tables persons, towns and countries, all
3926 table, create it as explained in the configuration section. Then create the
3927 example tables:</p>
3929 <pre>
3930 CREATE TABLE REL_countries (
3931 country_code char(1) NOT NULL default '',
3932 description varchar(10) NOT NULL default '',
3933 PRIMARY KEY (country_code)
3934 ) TYPE=MyISAM;
3936 INSERT INTO REL_countries VALUES ('C', 'Canada');
3938 CREATE TABLE REL_persons (
3939 id tinyint(4) NOT NULL auto_increment,
3940 person_name varchar(32) NOT NULL default '',
3942 country_code char(1) NOT NULL default '',
3943 PRIMARY KEY (id)
3944 ) TYPE=MyISAM;
3946 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3947 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3949 CREATE TABLE REL_towns (
3951 description varchar(30) NOT NULL default '',
3952 PRIMARY KEY (town_code)
3953 ) TYPE=MyISAM;
3955 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3956 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3957 </pre>
3963 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3967 </ul>
3975 <li>In the columns row, choose persons.person_name and click the
3977 <li>Do the same for towns.description and countries.descriptions in the
3980 the correct joins have been generated</li>
3982 </ul>
3986 <p>
3987 Starting from the previous example, create the pma_table_info as explained
3988 in the configuration section, then browse your persons table,
3989 and move the mouse over a town code or country code.
3990 <br /><br />
3991 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3992 enables: drop-down list of possible values.
3993 </p>
3996 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3997 <p>
4000 <br /><br />
4001 Then you need to think about your schema layout. Which tables will go on
4002 which pages?
4003 </p>
4004 <ul>
4010 page and click Go. If you like, you
4012 linked tables onto the new page.</li>
4013 <li>Select the name of the new page (making sure the Edit radio button
4014 is selected) and click Go.</li>
4016 Coordinates are relative; your diagram will
4017 be automatically scaled to fit the page. When initially placing tables
4018 on the page, just pick any coordinates -- say, 50x50. After clicking
4020 position the element correctly.</li>
4022 first be sure to click the Save
4023 button beneath the list of tables and coordinates, to save any changes
4024 you made there. Then scroll all the way down, select the
4026 you want, and click Go.</li>
4027 <li>Internet Explorer for Windows may suggest an incorrect filename when
4032 browsers on Windows, do not have this problem.</li>
4033 </ul>
4037 columns!</a></h4>
4039 <p> No, it's MySQL that is doing
4045 underscores in the database name?</a></h4>
4047 <p> If you do not put a backslash before the underscore, this is a wildcard
4050 john2db ...<br /><br />
4052 If you put a backslash before the underscore, it means that the database
4053 name will have a real underscore.</p>
4057 statistics pages?</a></h4>
4068 if it already exists during the import. It does NOT drop the table after
4069 your export, it only affects the import file.</li>
4071 Otherwise, you may get an error if the table name exists but has a
4072 different structure.</li>
4074 (if any) will be included in backup.</li>
4076 column and table names formed with special characters are protected.</li>
4078 types set in the pmadb in the dump as
4080 </li>
4081 </ul>
4086 command, for better documentation (but resulting file is bigger).</li>
4088 once the INSERT verb and the table name.</li>
4091 </li>
4093 more info is provided in the
4095 but basically with this selected, invalid values are adjusted and
4096 inserted rather than causing the entire statement to fail.</li>
4097 </ul>
4101 in its name.</a></h4>
4104 is the normal way to reference a database and table name. Worse, MySQL
4105 will usually let you create a database with a dot, but then you cannot
4106 work with it, nor delete it.</p>
4112 <p>
4113 To use SQL Validator, you need PHP with
4119 module.
4120 </p>
4122 <p>
4128 usage.
4129 </p>
4131 <p>
4132 If you use the Validator, you should be aware that any
4134 submit will be stored anonymously (database/table/column names,
4135 strings, numbers replaced with generic values). The Mimer
4138 We utilize it as free SOAP service.
4139 </p>
4143 it, but MySQL says "BLOB column '...' used in key specification without
4146 <p> The right way to do this, is to create the column without any indexes,
4148 dialog. On this page, you will be able to choose your BLOB column, and
4149 set a size to the index, which is the condition to create an index on
4150 a BLOB column.</p>
4154 editing fields?</a></h4>
4156 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4157 with many editing fields (table structure changes, row editing, etc.).
4158 You can also have a look at the directive
4160 ('vertical') and see if this eases up editing for you.</p>
4164 WTF is this feature then useful for?</a></h4>
4166 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4167 on them. Otherwise you could just put a comment on the column. Because entering
4168 your own mimetype will cause serious syntax checking issues and validation,
4169 this introduces a high-risk false-user-input situation. Instead you have to
4170 initialize mimetypes using functions or empty mimetype definitions.<br />
4171 Plus, you have a whole overview of available mimetypes. Who knows all those
4172 mimetypes by heart so he/she can enter it at will?</p>
4176 can't I see any bookmarks below the query box? What is this variable for?
4177 </a></h4>
4179 <p> Any query you have executed can be stored as a bookmark on the page where the
4180 results are displayed. You will find a button labeled 'Bookmark this query'
4181 just at the end of the page.<br />
4182 As soon as you have stored a bookmark, it is related to the database you run
4183 the query on. You can now access a bookmark dropdown on each page, the query
4184 box appears on for that database.<br /><br />
4186 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4190 aware of that you HAVE to create a valid query, otherwise your query won't be
4191 even able to be stored in the database.<br />
4193 for your query will remain the way it is, but will be stripped of the /**/
4194 chars. So you can use:<br /><br />
4198 which will be expanded to<br /><br />
4202 in your query, where VARIABLE is the string you entered in the input box. If
4203 an empty string is provided, no replacements are made.<br /><br />
4205 A more complex example. Say you have stored this query:<br /><br />
4207 <br /><br />
4210 the full query will be:<br /><br />
4213 <br /><br />
4215 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4217 spaces inserted there
4218 will be later also inserted as spaces in your query and may lead to unexpected
4219 results especially when
4221 Your initial query which is going to be stored as a bookmark has to yield at
4222 least one result row so
4223 you can store the bookmark. You may have that to work around using well
4227 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4228 include exported table?</a></h4>
4230 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4231 document should look like following one (assuming you have table
4234 <pre>
4235 \documentclass{article} % or any class you want
4236 \usepackage{longtable} % for displaying table
4237 \begin{document} % start of document
4238 \include{table} % including exported table
4239 \end{document} % end of document
4240 </pre>
4244 access them.
4245 </a></h4>
4247 <p> You have one of these global privileges: CREATE
4248 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4249 enable users to see all the database names.
4252 So if your users do not need those privileges, you can remove them and their
4253 databases list will shorten.</p>
4257 possible values for a column, based on some foreign table?</a></h4>
4259 <p> You have to setup appropriate links between the tables, and also
4263 foreign table, a drop-down list of values will be available.
4264 You will see two lists of values, the first list containing the key
4265 and the display column, the second list containing the display column
4266 and the key. The reason for this is to be able to type the first
4267 letter of either the key or the display column.<br /><br />
4269 For 100 values or more, a distinct window will appear, to browse foreign
4270 key values and choose one. To change the default limit of 100, see
4271 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4275 automatically when entering Browse mode for a table?</a></h4>
4277 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4278 </p>
4282 Excel files, how can I enable that?</a></h4>
4284 <p> You can use
4286 which works out of the box, but phpMyAdmin supports direct export
4287 to Microsoft Excel version 97 and newer. For this to work, you need to set
4292 <pre>
4293 cd phpMyAdmin
4294 mkdir tmp
4295 chmod o+rwx tmp
4296 </pre>
4300 what happens to my column comments stored in pmadb?</a></h4>
4302 <p> Automatic migration of a table's pmadb-style column comments to the native
4303 ones is done whenever you enter Structure page for this table.</p>
4308 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4309 <ul>
4312 later)</li>
4315 </ul>
4319 <ol>
4320 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4321 <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>
4322 <li>When you insert or update a row in this table, put a checkmark on the "Upload to BLOB repository" optional choice; otherwise, the upload will be done directly in your LONGBLOB column instead of the repository.</li>
4323 <li>Finally when you browse your table, you'll see in your column a link to stream your data, for example "View image". A header containing the correct MIME-type will be sent to your browser; this MIME-type was stored at upload time.</li>
4324 </ol>
4329 <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>
4335 <p>
4336 In all places where phpMyAdmin accepts format strings, you can use
4339 expanded variables depend on a context (for example, if you haven't chosen a
4340 table, you can not get the table name), but the following variables can be used:
4341 </p>
4342 <dl>
4348 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4359 </dl>
4364 <p>
4365 By clicking on the button 'toggle scratchboard' on the page
4366 where you edit x/y coordinates of those elements you can activate a
4367 scratchboard where all your elements are placed. By clicking on an
4368 element, you can move them around in the pre-defined area and the x/y
4369 coordinates will get updated dynamically. Likewise, when entering a
4370 new position directly into the input field, the new position in the
4371 scratchboard changes after your cursor leaves the input field.
4372 </p>
4373 <p>
4374 You have to click on the 'OK'-button below the tables to save the new
4375 positions. If you want to place a new element, first add it to the
4376 table of elements and then you can drag the new element around.
4377 </p>
4378 <p>
4379 By changing the paper size and the orientation you can change the size
4380 of the scratchboard as well. You can do so by just changing the
4381 dropdown field below, and the scratchboard will resize automatically,
4382 without interfering with the current placement of the elements.
4383 </p>
4384 <p>
4385 If ever an element gets out of range you can either enlarge the paper
4386 size or click on the 'reset' button to place all elements below each
4387 other.
4388 </p>
4393 <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>
4400 <p> Our Bug Tracker is located at
4402 under the Bugs section.<br /><br />
4404 But please first discuss your bug with other users:<br />
4406 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4407 </p>
4411 existing language, where do I start?</a></h4>
4413 <p> Always use latest Git version of the po file to translate. You can optionally
4415 server</a> where you can also get the latest po files and merge them
4416 with your translations. For creating a new translation simply use
4420 to do this) or ask on the mailing list to add the translation to the web
4421 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4422 </p>
4423 <p>
4424 Please note that we try not to use HTML entities like &eacute; in
4425 the translations, since we define the right character set in the file.
4426 With HTML entities, the text on JavaScript messages would not
4427 display correctly.
4428 However there are some entities that need to be there: quotes,
4429 non-breakable spaces, ampersands, less than, greater than.
4430 </p>
4431 <p>
4432 You can then put your translations, as a zip file to avoid losing special
4433 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4434 </p>
4435 <p>
4436 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4437 list, because this is where we ask for translations of new messages.
4438 </p>
4440 <p>
4441 Documentation is being translated using po4a and gettext (see
4443 for existing translations). To start, checkout
4444 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4445 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4446 and translate it online. If your language is missing, just contact
4448 you prefer to directly translate the po files, please put updated ones into our
4449 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4450 </p>
4454 phpMyAdmin. How should I proceed?</a></h4>
4459 <tt>git clone
4460 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4461 </li>
4463 <li>generate patch with your changes:
4465 </li>
4468 tracker of the phpMyAdmin project</a>.
4469 </li>
4470 </ol>
4472 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Git">our wiki</a>.</p>
4474 <p> Write access to the repository is granted only to experienced developers who
4475 have already contributed something useful to phpMyAdmin.<br />
4481 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4483 <p> Please refer to
4484 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4485 </p>
4490 <p> If you use Apache web server, phpMyAdmin exports information about
4491 authentication to the Apache environment and it can be used in Apache logs.
4492 Currently there are two variables available:
4493 </p>
4494 <dl>
4496 <dd>User name of currently active user (he does not have to be logged
4497 in).</dd>
4504 </dl>
4505 <p>
4507 </p>
4508 <pre>
4511 </pre>
4512 <p>
4513 You can then use any log analyzing tools to detect possible break-in
4514 attempts.
4515 </p>
4521 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4522 It allows you to connect to local as well as remote servers. This requires you to enter
4523 server host name, username, password, port and the name of the database. Therefore you can
4524 now synchronize your databases placed on the same server or some remote server.
4525 </p>
4527 <p>
4528 This feature is helpful for developers who need to replicate their
4529 database’s structure as well as data. Moreover, this feature not only
4530 helps replication but also facilitates the user to keep his/her database
4531 in sync with another database. Other than the full database, certain
4532 tables of the databases can also be synchronized.
4533 </p>
4535 <p>
4536 You need to fill in the host name of the server, the username and
4537 password of an user account already there in MySQL. Port is by default
4538 populated with 3306 (MySQL default port). Then the name of the database
4539 should be mentioned at the end. All the information other than the port
4540 needs to be filled explicitly for the source as well as target servers.
4541 </p>
4543 <p>
4544 After successfully passing through the authentication phase, the source and
4545 target database table names will be displayed. It will be a tabular
4546 representation.
4547 </p>
4549 <p>
4550 On the left, are listed the source database table names. Some of the
4552 are only present in source database and they need to be added to the
4553 target database in order to synchronize the target database. The tables
4555 target database.
4556 </p>
4558 <p>
4559 On the right, are listed the target database table names. There are few
4561 means that these tables are to be created in target database in order to
4562 synchronize target database with source database. Some table names
4564 only present in target database and they will remain unchanged in the
4565 target database. The column in the middle shows the difference between
4566 the source and target corresponding tables.
4567 </p>
4569 <p>
4571 letters, indicating that either Structure or Data are not up to date. By
4572 clicking on them, they will turn grey, what means that they will be synchronized.
4573 </p>
4575 <!-- DEVELOPERS -->
4578 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4579 great features have been written by other people and you too can help to
4580 make phpMyAdmin a useful tool.</p>
4582 <p> If you're planning to contribute source, please read the following
4583 information:</p>
4589 it free from other code.<br />
4590 Commonly used functions should be added to
4593 <li>Obviously, you're free to use whatever coding style you want. But
4594 please try to keep your code as simple as possible: beginners are
4595 using phpMyAdmin as an example application.<br />
4596 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4597 compliant on one hand, they fit the
4600 coding standards</a>
4601 on the other hand. Please pay attention to this.</li>
4602 <li>Please enable showing PHP errors and warnings by the
4604 configuration directive.</li>
4605 <li>Please try to keep up the file-naming conventions. Table-related stuff
4608 <li>Please use gettext wrappers around all messages
4611 script. To use translated messages, call
4613 Gettext.</li>
4617 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4618 better debug and profile their code.<br />
4619 Please see the
4621 options for more information.<br />
4622 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4623 lost during its re-entry into Earth's atmosphere and in memory of the
4624 brave men and women who gave their lives for the people of Earth.</li>
4625 </ul>
4629 <pre>
4640 </pre>
4642 <p>
4643 This program is free software; you can redistribute it and/or modify
4644 it under the terms of the GNU General Public License version 2,
4645 as published by the Free Software Foundation.
4646 </p>
4648 <p>
4649 This program is distributed in the hope that it will be useful,
4650 but WITHOUT ANY WARRANTY; without even the implied warranty of
4651 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4652 GNU General Public License for more details.
4653 </p>
4655 <p>
4656 You should have received a copy of the GNU General Public License
4657 along with this program; if not, write to the Free Software
4659 </p>
4661 <!-- CREDITS -->
4666 <ul>
4669 <ul>
4672 </ul></li>
4675 <ul>
4680 </ul></li>
4683 <ul>
4689 </ul></li>
4692 <ul>
4694 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4695 generate XHTML1.0 and CSS2 compliant codes</li>
4698 </ul></li>
4701 <ul>
4709 </ul></li>
4712 <ul>
4717 </ul></li>
4720 <ul>
4723 </ul></li>
4726 <ul>
4728 </ul></li>
4731 <ul>
4734 </ul></li>
4737 <ul>
4741 </ul></li>
4744 <ul>
4747 </ul></li>
4750 <ul>
4757 </ul></li>
4760 <ul>
4764 </ul></li>
4767 <ul>
4773 </ul></li>
4776 (http://sf.net/projects/phpmysqlformgen/)
4777 <ul>
4779 </ul></li>
4782 <ul>
4784 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4789 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4793 </ul></li>
4796 <ul>
4798 </ul></li>
4801 <ul>
4803 </ul></li>
4806 <ul>
4808 </ul></li>
4811 <ul>
4812 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4813 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4814 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4815 </ul></li>
4818 <ul>
4820 </ul></li>
4823 <ul>
4825 </ul></li>
4828 <ul>
4830 </ul></li>
4833 <ul>
4836 </ul></li>
4838 <li>Nicola Asuni (Tecnick.com)
4839 <ul>
4842 </ul></li>
4845 <ul>
4848 </ul></li>
4851 <ul>
4853 </ul></li>
4856 <ul>
4859 </ul></li>
4861 <li>Ivan A Kirillov
4862 <ul>
4864 </ul></li>
4867 <ul>
4869 </ul></li>
4872 <ul>
4875 </ul></li>
4878 <ul>
4880 </ul></li>
4883 <ul>
4885 </ul></li>
4888 <ul>
4890 </ul></li>
4893 <ul>
4895 </ul></li>
4898 <ul>
4900 </ul></li>
4903 <ul>
4907 </ul></li>
4910 <ul>
4912 </ul></li>
4915 <ul>
4917 </ul></li>
4919 <li>Barrie Leslie
4920 <ul>
4922 </ul></li>
4925 <ul>
4927 </ul></li>
4930 </ul>
4932 <p>
4933 And also to the following people who have contributed minor changes,
4934 enhancements, bugfixes or support for a new language since version 2.1.0:
4935 </p>
4937 <p>
4938 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4939 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4940 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4941 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4943 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4944 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4945 Luís V., Martijn W. van der Lee,
4946 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4948 </p>
4953 <p>
4954 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4955 to create a web-based interface to MySQL using PHP3. Although I have not
4956 used any of his source-code, there are some concepts I've borrowed from
4957 him. phpMyAdmin was created because Peter told me he wasn't going to
4958 further develop his (great) tool.
4959 </p>
4960 <p>
4961 Thanks go to
4962 </p>
4963 <ul>
4965 code for the check when dropping a table or database. He also suggested
4966 that you should be able to specify the primary key on tbl_create.php3. To
4967 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4968 well as a bug-report. Plus many smaller improvements.
4969 </li>
4971 were introduced in 1.3.0 (including quite significant ones like the
4972 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4973 bug-fixes and help.
4974 </li>
4976 language-independent by outsourcing the strings to a separate file. He
4977 also contributed the French translation.
4978 </li>
4980 tbl_select.php3, a feature to display only some columns from a table.
4981 </li>
4983 functions in tbl_change.php3. He also added the
4985 </li>
4987 servers and is a regular contributor for bug-fixes.
4988 </li>
4990 features for 2.0.6.
4991 </li>
4992 </ul>
4993 <p>
4994 The following people have contributed minor changes, enhancements, bugfixes
4995 or support for a new language:
4996 </p>
4997 <p>
4998 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4999 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
5000 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
5001 G. Wieggers.
5002 </p>
5003 <p>
5004 And thanks to everyone else who sent me email with suggestions, bug-reports
5005 and or just some feedback.
5006 </p>
5012 <ul>
5014 - the default name of Apache's directory-level configuration file.</li>
5018 - a software application that enables a user to display and interact with
5019 text, images, and other information typically located on a web page at a
5020 website on the World Wide Web.</li>
5022 - a free software/open source data compression algorithm and program
5023 developed by Julian Seward.</li>
5025 - an important World Wide Web technology that enables a client web browser
5026 to request data from a program executed on the Web server.</li>
5028 - a log or record of changes made to a project.</li>
5030 - a computer system that accesses a (remote) service on another computer
5031 by some kind of network.</li>
5033 - a set of data values of a particular simple type, one for each row of
5034 the table.</li>
5036 - a packet of information sent by a server to a World Wide Web browser
5037 and then sent back by the browser each time it accesses that server.</li>
5039 - Comma-separated values</li>
5042 - an organized collection of data.</li>
5045 - a PHP module that extends PHP with additional functionality.</li>
5047 - a list of commonly asked question and there answers.</li>
5049 - one part of divided data/columns.</li>
5051 - a field or group of fields in a database record that point to a key
5052 field or group of fields forming a key of another database record in some
5053 (usually different) table.</li>
5055 - the free PDF library</li>
5057 GD Graphics Library</a> - a library by Thomas Boutell and others for
5058 dynamically manipulating images.</li>
5061 - gzip is short for GNU zip, a GNU free software file compression
5062 program.</li>
5064 - any machine connected to a computer network, a node that has a hostname.</li>
5066 - the unique name by which a network attached device is known on a network.</li>
5068 (HyperText Transfer Protocol)</a>
5069 - the primary method used to transfer or convey information on the World
5070 Wide Web.</li>
5073 additional security measures.</li>
5074 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5075 - a set of Internet-based services for servers using Microsoft Windows.</li>
5077 - a feature that allows quick access to the rows in a table.</li>
5079 - a data-oriented protocol used by source and destination hosts for
5080 communicating data across a packet-switched internetwork.</li>
5082 - a unique number that devices use in order to identify and communicate
5083 with each other on a network utilizing the Internet Protocol standard.</li>
5085 (Internet Server Application Programming Interface)</a>
5086 - the API of Internet Information Services (IIS).</li>
5088 - a business or organization that offers users access to the Internet and related services.</li>
5090 - a most commonly used standard method of lossy compression for
5091 photographic images.</li>
5097 - line of personal computers is designed, developed, manufactured, and
5098 marketed by Apple Computer.</li>
5099 <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>
5100 - the operating system which is included with all currently shipping Apple
5101 Macintosh computers in the consumer and professional markets.</li>
5103 - a cryptographic library.</li>
5105 - the MCrypt PHP extension.</li>
5106 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5107 - an Internet Standard for the format of e-mail.</li>
5109 - some sort of extension for the Apache Webserver.</li>
5111 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5112 Management System (DBMS).</li>
5114 - the improved MySQL client PHP extension.</li>
5116 - the MySQL client PHP extension.</li>
5118 - open standard for office documents.</li>
5119 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5120 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5122 (Portable Document Format)</a>
5123 - a file format developed by Adobe Systems for representing two
5124 dimensional documents in a device independent and resolution independent
5125 format.</li>
5127 - the PHP Extension and Application Repository.</li>
5129 - the perl-compatible regular expression functions for PHP</li>
5131 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5132 programming language used mainly for developing server-side applications
5133 and dynamic web content, and more recently, a broader range of software
5134 applications.</li>
5136 - a connection through which data is sent and received.</li>
5138 - Request for Comments (RFC) documents are a series of memoranda
5139 encompassing new research, innovations, and methodologies applicable to
5140 Internet technologies.</li>
5144 - represents a single, implicitly structured data item in a table.</li>
5146 - a computer system that provides services to other computing
5147 systems over a network.</li>
5148 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5149 - handlers for different table types</li>
5151 - a form of inter-process communication.</li>
5153 Sockets Layer)</a>
5154 - a cryptographic protocol which provides secure communication on the Internet.</li>
5156 - Structured Query Language</li>
5158 - a set of data elements (cells) that is organized, defined and stored as
5159 horizontal rows and vertical columns where each item can be uniquely
5160 identified by a label or key or by it?s position in relation to other items.</li>
5163 - a type of archive file format: the Tape ARchive format.</li>
5165 - one of the core protocols of the Internet protocol suite.</li>
5169 - a sequence of characters, conforming to a standardized format, that is
5170 used for referring to resources, such as documents and images on the
5171 Internet, by their location.</li>
5173 - A computer (program) that is responsible for accepting HTTP requests
5174 from clients and serving them Web pages.</li>
5176 - a W3C-recommended general-purpose markup language for creating
5177 special-purpose markup languages, capable of describing many different
5178 kinds of data.</li>
5180 - a popular data compression and archival format.</li>
5182 - an open-source, cross-platform data compression library by Jean-loup
5183 Gailly and Mark Adler.</li>
5184 </ul>
5185 </div>
5188 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5191 <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>
5192 </ul>
5194 </body>
5195 </html>