| blob | 0b0a29b214f7e3a97337e9b3f047209864f5412e |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.4.0-dev
22 Documentation
23 </h1>
24 </div>
26 <!-- TOP MENU -->
35 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
41 </ul>
46 phpMyAdmin homepage</a></li>
48 SourceForge phpMyAdmin project page</a></li>
50 Official phpMyAdmin wiki</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
58 </li>
59 </ul>
61 <!-- REQUIREMENTS -->
68 and the Standard PHP Library (SPL) extension.
69 </li>
72 currently the default), you should install the mbstring and ctype
73 extensions.
74 </li>
75 <li>You need GD2 support in PHP to display inline
77 original aspect ratio</li>
83 load pages significantly slower.
84 </li>
87 <li>To support BLOB streaming, see PHP and MySQL requirements
90 </ul>
91 </li>
94 </ul>
96 <!-- INTRODUCTION -->
99 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
100 a single database. To accomplish the latter you'll need a properly set up
101 MySQL user who can read/write only the desired database. It's up to you to
102 look up the appropriate part in the MySQL manual.
103 </p>
108 <li>create, copy, drop, rename and alter databases, tables, columns and
109 indexes</li>
110 <li>maintenance server, databases and tables, with proposals on server
111 configuration</li>
112 <li>execute, edit and bookmark any
114 batch-queries</li>
117 </li>
124 OpenDocument Text and Spreadsheet,
126 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
127 </li>
128 <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>
132 <li>using Query-by-example (QBE), create complex queries automatically
133 connecting required tables</li>
135 your Database layout</li>
137 <li>transform stored data into any format using a set of predefined
138 functions, like displaying BLOB-data as image or download-link
139 </li>
146 </li>
147 <li>synchronize two databases residing on the same as well as remote servers
149 </li>
151 </ul>
154 <p> Many people have difficulty
155 understanding the concept of user management with regards to phpMyAdmin. When
156 a user logs in to phpMyAdmin, that username and password are passed directly
157 to MySQL. phpMyAdmin does no account management on its own (other than
158 allowing one to manipulate the MySQL user account information); all users
159 must be valid MySQL users.</p>
168 <!-- INSTALLATION -->
176 </ol>
179 phpMyAdmin does not apply any special security methods to the MySQL database
180 server. It is still the system administrator's job to grant permissions on
182 be used for this.
183 </p>
191 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
192 before uploading them to your server, as PHP seems not to like
197 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
198 Downloads page. Some kits contain only the English messages,
199 others contain all languages in UTF-8 format (this should be fine
200 in most situations), others contain all
201 languages and all character sets. We'll assume you chose a kit whose
203 </li>
204 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
206 document root. If you don't have direct access to your document root,
207 put the files in a directory on your local machine, and, after step 4,
208 transfer the directory on your web server using, for example, ftp.</li>
209 <li>Ensure that all the scripts have the appropriate owner (if PHP is
210 running in safe mode, having some scripts with an owner different
211 from the owner of other scripts will be a
216 <li>Now you must configure your installation. There are two methods that
217 can be used. Traditionally, users have hand-edited a copy of
219 provided for those who prefer a graphical installation. Creating a
220 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
221 <ul><li>To manually create the file, simply use your text editor to
224 file) in the main (top-level) phpMyAdmin directory (the one
228 default value is okay for a particular setting, there is no
230 few directives to get going, a simple configuration may look
231 like this:
232 <pre>
233 <?php
234 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
236 $i=0;
237 $i++;
238 $cfg['Servers'][$i]['auth_type'] = 'cookie';
239 ?>
240 </pre>
241 Or, if you prefer to not be prompted every time you log in:
242 <pre>
243 <?php
245 $i=0;
246 $i++;
247 $cfg['Servers'][$i]['user'] = 'root';
248 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
249 $cfg['Servers'][$i]['auth_type'] = 'config';
250 ?>
251 </pre>
252 For a full explanation of possible configuration values, see the
258 directory. This is a security measure. On a Linux/Unix system you
259 can use the following commands:
260 <pre>
261 cd phpMyAdmin
262 mkdir config # create directory for saving
263 chmod o+rw config # give it world writable permissions
264 </pre>
265 And to edit an existing configuration, copy it over first:
266 <pre>
267 cp config.inc.php config/ # copy current configuration for editing
268 chmod o+w config/config.inc.php # give it world writable permissions
269 </pre>
270 On other platforms, simply create the folder and ensure that your
279 the webserver does not have the proper permissions you may see the
281 config/</tt> directory exists and has the proper permissions -
283 and upload (via FTP or some similar means) to the proper location.<br /><br />
285 Once the file has been saved, it must be moved out of the <tt>
286 config/</tt> directory and the permissions must be reset, again
287 as a security measure:
288 <pre>
289 mv config/config.inc.php . # move file to current directory
290 chmod o-rw config.inc.php # remove world read and write permissions
291 rm -rf config # remove not needed directory
292 </pre>
293 Now the file is ready to be used. You can choose to review or edit
294 the file with your favorite editor, if you prefer to set some
295 advanced options which the setup script does not provide.</li></ul></li>
296 <li>If you are using the
298 protect the phpMyAdmin installation directory because using
299 config does not require a user to
300 enter a password to access the phpMyAdmin installation. Use of an alternate
301 authentication method is recommended, for example with
309 in your browser. phpMyAdmin should now display a welcome screen
310 and your databases, or a login dialog if using
312 authentication mode.</li>
315 Apache you can use supplied .htaccess file in that folder, for other
316 webservers, you should configure this yourself. Such configuration
317 prevents from possible path exposure and cross side scripting
318 vulnerabilities that might happen to be found in that code.</li>
319 <li>
320 It is generally good idea to protect public phpMyAdmin installation
321 against access by robots as they usually can not do anything good
323 your webserver or limit access by web server configuration. You can
326 </li>
327 </ol>
331 <p> For a whole set of new features (bookmarks, comments,
333 tracking mechanism,
335 transformation, etc.) you need to create a set of special tables. Those
336 tables can be located in your own database, or in a central database for a
337 multi-user installation (this database would then be accessed by the
338 controluser, so no other user should have rights to it).</p>
349 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
350 that you may need special (administrator) privileges to create the database
351 and tables, and that the script may need some tuning, depending on the
352 database name.</p>
357 section</a>. You will also need to have a controluser with the proper rights
364 unpacked one. Configuration files from old versions may
365 require some tweaking as some options have been changed or removed; in
367 so you better remove it from your file and just use the default one.
369 statement that you might find near the end of your configuration file.</p>
373 is version-specific.</p>
376 version 5.x or newer and if you use the phpMyAdmin configuration storage,
377 you should run the SQL script found in
384 where you want to give users access to their own database and don't want
385 them to play around with others.<br />
386 Nevertheless be aware that MS Internet Explorer seems to be really buggy
390 that your user/password pair are not in clear in the configuration file.
391 </li>
394 authentication modes are more secure: the MySQL login information does
395 not need to be set in the phpMyAdmin configuration file (except possibly
397 However, keep in mind that the password travels in plain text, unless
398 you are using the HTTPS protocol.<br />
399 In cookie mode, the password is stored, encrypted with the blowfish
400 algorithm, in a temporary cookie.</li>
412 file under the
414 $cfg['Servers'][$i]['controluser']</a></tt> and
419 only an example: use something else in your file!</b> Input these
420 statements from the phpMyAdmin SQL Query window or mysql command–line
421 client.<br />
423 if it's not the same as the MySQL server's one.
425 <pre>
426 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
427 GRANT SELECT (
428 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
429 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
430 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
431 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
432 Execute_priv, Repl_slave_priv, Repl_client_priv
433 ) ON mysql.user TO 'pma'@'localhost';
434 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
435 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
436 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
437 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
439 If you want to use the many new relation and bookmark features:
441 <pre>
443 </pre>
446 configuration storage</a> be set up).
447 <br /></li>
450 on a set of particular databases. Normally you shouldn't give global
451 privileges to an ordinary user, unless you understand the impact of those
452 privileges (for example, you are creating a superuser).<br />
456 <pre>
457 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
458 </pre>
460 What the user may now do is controlled entirely by the MySQL user
461 management system.<br />
463 authentication mode, you don't need to fill the user/password fields
465 array.</li>
466 </ul>
471 method and allows you to log in as any valid MySQL user.</li>
472 <li>Is supported with most PHP configurations. For
485 mode.</li>
486 </ul>
490 <ul><li>You can use this method as a replacement for the
492 (for example, if you're running
494 <li>Obviously, the user must enable cookies in the browser, but this is
495 now a requirement for all authentication modes.</li>
496 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
497 with the same username.</li>
498 <li>If you want to log in to arbitrary server see
503 not required.</li>
504 </ul>
508 <ul><li>This mode is a convenient way of using credentials from another
509 application to authenticate to phpMyAdmin.</li>
510 <li>The other application has to store login information into
511 session data.</li>
513 section.</li>
514 </ul>
517 <ul><li>This mode is the less secure one because it requires you to fill the
519 $cfg['Servers'][$i]['user']</a> and
521 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
522 can read your config.inc.php can discover your username and password).
523 <br />
530 is an entry explaining how to protect your configuration file.</li>
531 <li>For additional security in this mode, you may wish to consider the Host
532 authentication
534 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
536 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
537 directives.</li>
538 <li>Unlike cookie and http, does not require a user to log in when first
539 loading the phpMyAdmin site. This is by design but could allow any
540 user to access your installation. Use of some restriction method is
542 HTTP-AUTH directive or disallowing incoming HTTP requests at
543 one’s router or firewall will suffice (both of which
544 are beyond the scope of this manual but easily searchable with Google).</li>
545 </ul>
547 <p>
548 The Swekey is a low cost authentication USB key that can be used in
549 web applications.<br /><br />
550 When Swekey authentication is activated, phpMyAdmin requires the
551 users's Swekey to be plugged before entering the login page (currently
552 supported for cookie authentication mode only). Swekey Authentication is
553 disabled by default.<br /><br />
555 </p>
556 <pre>
557 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
558 </pre>
559 <p>
561 each user with their Swekey Id. It is important to place this file outside
562 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
564 users' information.<br /><br />
565 If you want to purchase a Swekey please visit
567 since this link provides funding for phpMyAdmin.
568 </p>
569 <!-- CONFIGURATION -->
573 users:</span> PHP does not seem to like
577 before saving a script you have modified.</p>
582 section to create one. This file only needs to contain the parameters you want to
583 change from their corresponding default value in
586 <p> The parameters which relate to design (like colors) are placed in
589 your site specific code to be included on start and end of each page.</p>
593 (with full path) to your phpMyAdmin installation's directory.
596 some web servers are case–sensitive.
599 Starting with version 2.3.0, it is advisable to try leaving this
600 blank. In most cases phpMyAdmin automatically detects the proper
601 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
602 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
603 A good test is to browse a table, edit a row and save it. There should
604 be an error message if phpMyAdmin is having trouble auto–detecting
605 the correct value. If you get an error that this must be set or if
606 the autodetect code fails to detect your path, please post a bug
607 report on our bug tracker so we can improve the code.</dd>
611 with master / foreign – tables (see
613 <br />
614 If you tried to set this up and it does not work for you, have a look on
616 use it. You will find a link that will analyze why those features have
617 been disabled.<br />
618 If you do not want to use those features set this variable to
622 <dd>A warning is displayed on the main page if Suhosin is detected.
624 from appearing.</dd>
627 <dd>Disable the default warning that is displayed if mcrypt is missing for
628 cookie authentication.
630 from appearing.</dd>
634 domain to call phpMyAdmin inside a frame, and is a potential security
635 hole allowing cross-frame scripting attacks.</dd>
639 algorithm to encrypt the password.<br />
641 passphrase of your choice. It will be used internally by the blowfish
642 algorithm: you won’t be prompted for this passphrase. There is
643 no maximum length for this secret.<br /><br />
645 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
646 makes a bit weaker security as this generated secret is stored in
647 session and furthermore it makes impossible to recall user name from
648 cookie.</dd>
652 MySQL servers. Therefore, a
654 been added which contains the login information for the different servers.
655 The first
657 contains the hostname of the first server, the second
659 the hostname of the second server, etc. In
661 server definition, however you can put as many as you need in
663 have to define all settings, just those you need to change).</dd>
667 $i-th MySQL-server. E.g. localhost.</dd>
672 ignores this port number and connects with the socket, so if you want
673 to connect to a port different from the default port, use
676 </dd>
680 To determine the correct socket, check your MySQL configuration or, using the
682 Among the resulting information displayed will be the socket used.</dd>
685 <dd>Whether to enable SSL for connection to MySQL server.
686 </dd>
689 <dd>What type connection to use with the MySQL server. Your options are
691 is nearly guaranteed to be available on all MySQL servers, while
692 sockets are not supported on some platforms.<br /><br />
694 To use the socket mode, your MySQL server must be on the same machine
695 as the Web server.</dd>
698 <dd>What php MySQL extension to use for the connection. Valid options are:
699 <br /><br />
702 The classic MySQL extension. This is the recommended and default
703 method at this time.<br /><br />
706 The improved MySQL extension. This extension became available
707 with php 5.0.0 and is the recommended way to connect to a server
711 <dd>Whether to use a compressed protocol for the MySQL server connection
712 or not (experimental).<br />
718 </dt>
720 all relational features (see
722 and, for a MySQL server running with
725 authentication mode).<br /><br />
728 cookie authentication modes (or 'config'
729 authentication mode since phpMyAdmin 2.2.1), you need to supply the
734 This account is used to check what databases the user will see at
735 login.<br />
739 In phpMyAdmin versions before 2.2.5, those were called
743 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
744 <dd>Whether config or cookie or
746 should be used for this server.
748 is the plain old way: username and password are stored in
750 <li>'cookie' authentication mode
752 2.2.3 allows you to log in as any valid MySQL user with the
753 help of cookies. Username and password are stored in
754 cookies during the session and password is deleted when it
755 ends. This can also allow you to log in in arbitrary server if
756 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
757 </li>
758 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
759 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
760 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
761 <li>'signon' authentication mode
763 as introduced in 2.10.0 allows you to log in from prepared PHP
764 session data. This is useful for implementing single signon
765 from another application. Sample way how to seed session is in
771 </ul>
774 for more information.
775 </dd>
777 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
778 </dt>
779 <dd>
780 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
781 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
782 specified in your configuration, a string combined of "phpMyAdmin " and either
785 </dd>
787 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
788 </dt>
789 <dd>
791 names for hardware authentication. Leave empty to deactivate this feature.
792 </dd>
796 </dt>
797 <dd>
798 When using auth_type = 'config', this is the user/password-pair
799 which phpMyAdmin will use to connect to the
800 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
801 cookie authentication is used and should be empty.</dd>
803 <span
805 </dt>
806 <dd>
807 Allow attempt to log in without password when a login with password
808 fails. This can be used together with http authentication, when
809 authentication is done some other way and phpMyAdmin gets user name
810 from auth and uses empty password for connecting to MySQL. Password
811 login is still tried first, but as fallback, no password method is
812 tried.</dd>
815 </dt>
816 <dd>
817 If set to a (an array of) database name(s), only this (these) database(s)
818 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
819 database(s) name(s) may contain MySQL wildcards characters
823 This setting is an efficient way to lower the server load since the
824 latter does not need to send MySQL requests to build the available
826 privileges rules of the MySQL database server</span>. If set, it just
827 means only these databases will be displayed but
829 <br /><br />
831 An example of using more that one database:
833 <br /><br />
835 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
836 databases in the left frame, so that you can individually arrange your databases.<br />
837 If you want to have certain databases at the top, but don't care about the others, you do not
838 need to specify all other databases. Use:
840 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
841 order.</dd>
844 </dt>
845 <dd>Regular expression for hiding some databases. This only hides them
846 from listing, but a user is still able to access them (using, for example,
847 the SQL query area). To limit access, use the MySQL privilege system.
848 <br /><br />
853 More information on regular expressions can be found in the
855 PCRE pattern syntax</a> portion of the PHP reference manual.
856 </dd>
859 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
860 this string will be displayed instead of the hostname in the pull-down
861 menu on the main page. This can be useful if you want to show only
862 certain databases on your system, for example. For HTTP auth, all
863 non-US-ASCII characters will be stripped.</dd>
867 </dt>
868 <dd>The name of the database containing the phpMyAdmin configuration storage.
869 <br /><br />
872 section in this document to see the benefits of this feature,
873 and for a quick way of creating this database and the needed tables.
874 <br /><br />
876 If you are the only user of this phpMyAdmin installation, you can
877 use your current database to store those special tables; in this
878 case, just put your current database name in
880 set this parameter to the name of your central database containing
881 the phpMyAdmin configuration storage.</dd>
885 </dt>
887 useful for queries you often run.<br /><br />
889 To allow the usage of this functionality:
891 <li>enter the table name in
893 </ul>
894 </dd>
898 </dt>
900 which column is a key in another table (a foreign key). phpMyAdmin
901 currently uses this to
902 <ul><li>make clickable, when you browse the master table, the data values
903 that point to the foreign table;</li>
905 when browsing the master table, if you move the mouse to a column
906 containing a foreign key (use also the 'table_info' table);<br />
909 <li>in edit/insert mode, display a drop-down list of possible foreign
913 <li>display links on the table properties page, to check referential
914 integrity (display missing foreign keys) for each described key;
915 </li>
919 schema of your database (also uses the table_coords table).</li>
920 </ul>
922 The keys can be numeric or character.<br /><br />
924 To allow the usage of this functionality:
927 configuration storage</li>
928 <li>put the relation table name in
930 <li>now as normal user open phpMyAdmin and for each one of your
931 tables where you want to use this feature, click
933 columns.
934 </li>
935 </ul>
939 future development of the cross-db relations.
940 </dd>
944 </dt>
945 <dd>
946 Since release 2.3.0 you can describe, in a special 'table_info'
947 table, which column is to be displayed as a tool-tip when moving the
948 cursor over the corresponding key.<br />
949 This configuration variable will hold the name of this special
950 table. To allow the usage of this functionality:
952 <li>put the table name in
954 'pma_table_info')</li>
955 <li>then for each table where you want to use this feature,
957 to choose the column.</li>
958 </ul>
960 </dd>
964 </dt>
967 the relations between your tables. To do this it needs two tables
972 schema output).<br /><br />
976 To allow the usage of this functionality:
979 <li>put the correct table names in
982 </ul>
985 </dd>
989 </dt>
991 Since release 2.3.0 you can store comments to describe each column for
993 <br /><br />
995 Starting with release 2.5.0, comments are consequently used on the table
996 property pages and table browse view, showing up as tool-tips above the
997 column name (properties page) or embedded within the header of table in
998 browse view. They can also be shown in a table dump. Please see the
999 relevant configuration directives later on.<br /><br />
1001 Also new in release 2.5.0 is a MIME-transformation system which is also
1003 Transformations</a> for further information. To use the
1004 MIME-transformation system, your column_info table has to have the three
1005 new columns 'mimetype', 'transformation', 'transformation_options'.
1006 <br /><br />
1008 To allow the usage of this functionality:
1010 <li>put the table name in
1012 'pma_column_info')</li>
1015 <pre>
1016 ALTER TABLE `pma_column_comments`
1017 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1018 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1019 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1020 </pre>
1023 renamed from<br />
1026 </ul>
1027 </dd>
1031 </dt>
1034 all queries you entered manually into the phpMyAdmin interface. If you
1035 don't want to use a table-based history, you can use the JavaScript-based
1036 history. Using that, all your history items are deleted when closing the
1037 window.<br /><br />
1039 Using
1041 you can specify an amount of history items you want to have on hold. On
1042 every login, this list gets cut to the maximum amount.<br /><br />
1044 The query history is only available if JavaScript is enabled in your
1045 browser.<br /><br />
1047 To allow the usage of this functionality:
1051 (e.g. 'pma_history')
1052 </li>
1053 </ul>
1054 </dd>
1058 </dt>
1059 <dd>
1060 Since release 3.3.x a tracking mechanism is available.
1062 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1063 and data definition statements. After enabling it you can create versions of tables.
1064 <br/><br/>
1065 The creation of a version has two effects:
1067 <ul>
1069 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1070 </ul>
1072 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1073 For the report you can use filters, for example you can get a list of statements within a date range.
1074 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1075 In addition you can export the (filtered) report to a file or to a temporary database.
1076 <br/><br/>
1078 To allow the usage of this functionality:
1080 <ul>
1083 </ul>
1084 </dd>
1087 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1088 </dt>
1089 <dd>
1090 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1091 <br/><br/>
1092 If this is set to true and you create a table or view with
1094 <ul>
1097 </ul>
1099 and no version exists for it, the mechanism will
1100 create a version for you automatically.
1101 </dd>
1104 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1105 </dt>
1106 <dd>
1107 Defines the list of statements the auto-creation uses for new versions. Default value is
1108 <br/>
1110 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1111 CREATE INDEX,DROP INDEX,
1112 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1113 CREATE VIEW,ALTER VIEW,DROP VIEW,
1114 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1115 </dd>
1118 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1119 </dt>
1120 <dd>
1121 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1122 <br/><br/>
1123 </dd>
1127 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1128 </dt>
1129 <dd>
1130 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1131 <br/><br/>
1132 </dd>
1135 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1136 </dt>
1137 <dd>
1138 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1139 <br/><br/>
1140 </dd>
1144 </dt>
1145 <dd>
1146 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1147 and store them in the database.
1148 <br /><br />
1151 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1152 or, it is is unavailable, until the end of session.
1153 <br /><br />
1155 To allow the usage of this functionality:
1157 <ul>
1159 configuration storage</li>
1161 </ul>
1162 </dd>
1166 </dt>
1168 to visually manage the relations.
1169 <br /><br />
1171 To allow the usage of this functionality:
1174 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1175 </li>
1176 </ul>
1177 </dd>
1180 </dt>
1182 column_info table got enhanced with three new columns. If the above variable
1184 latest table structure available. If not, it will emit a warning to the
1185 superuser.<br /><br />
1187 You can disable this checking behavior by setting the variable to false,
1188 which should offer a performance increase.<br /><br />
1190 Recommended to set to FALSE, when you are sure, your table structure is
1191 up to date.</dd>
1193 boolean</dt>
1194 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1195 </dd>
1197 boolean</dt>
1198 <dd>Whether to allow logins without a password. The default
1200 to a MySQL server with was left with an empty password for root or
1201 on which an anonymous (blank) user is defined.
1202 </dd>
1205 </dt>
1207 authorization is disabled.<br /><br />
1210 all deny rules followed by allow rules. Access is allowed by default. Any
1211 client which does not match a Deny command or does match an Allow command
1212 will be allowed access to the server. <br /><br />
1215 applies all allow rules followed by deny rules. Access is denied by
1216 default. Any client which does not match an Allow directive or does
1217 match a Deny directive will be denied access to the server.<br /><br />
1219 If your rule order is set to 'explicit', authorization is
1220 performed in a similar fashion to rule order 'deny,allow', with the
1224 and was available in Apache by specifying allow and deny rules without
1225 setting any order.<br /><br />
1227 Please also see <a
1229 address behind proxies.
1230 </dd>
1232 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1233 </dt>
1234 <dd>The general format for the rules is as such:
1236 <pre>
1238 </pre>
1243 well (please note that those containing SERVER_ADDRESS might not be
1244 available on all webservers):
1245 <pre>
1251 </pre>
1253 Having an empty rule list is equivalent to either using
1259 following work:<br />
1261 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1262 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1263 But the following does not work:<br />
1266 Also IPv6 addresses are not supported.
1267 </dd>
1269 <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.
1270 </dd>
1271 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1273 DATABASES</tt> command used to fetch the name of available databases will
1274 probably be too slow, so it can be replaced by faster commands (see
1276 </dd>
1278 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1279 </dd>
1280 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1281 <dd>Name of session which will be used for signon authentication method.
1282 </dd>
1284 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1285 </dd>
1287 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1288 </dd>
1291 <dd>If you have more than one server configured, you can set
1293 that server when phpMyAdmin is started, or set it to 0 to be given a
1294 list of servers without logging in.<br />
1296 MUST be set to that server.</dd>
1299 <dd>The maximum number of database names to be displayed in the
1300 navigation frame and the database list.</dd>
1303 <dd>The maximum number of table names to be displayed in the
1304 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1305 when in Light mode.</dd>
1308 <dd>The maximum number of characters when a SQL query is displayed. The
1309 default limit of 1000 should be correct to avoid the display of tons
1310 of hexadecimal codes that represent BLOBs, but some users have real
1311 SQL queries that are longer than 1000 characters. Also, if a query's
1312 length exceeds this limit, this query is not saved in the history.</dd>
1315 <dd>Defines whether to use GZip output buffering for increased
1317 Set to true/false for enabling/disabling. When set to 'auto' (string),
1318 phpMyAdmin tries to enable output buffering and will automatically disable
1319 it if your browser has some problems with buffering. IE6 with a certain patch
1320 is known to cause data corruption when having enabled buffering.</dd>
1323 <dd>Whether persistent connections should be used or not (mysql_connect or
1324 mysql_pconnect).</dd>
1330 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1331 to zero, no time limit is imposed.<br />
1332 This setting is used while importing/exporting dump files and in the
1333 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1340 <dd>Set the number of bytes a script is allowed to allocate. If set
1341 to zero, no limit is imposed.<br />
1342 This setting is used while importing/exporting dump files and at some
1343 other places in phpMyAdmin so you definitely don't want to put here
1344 a too low value. It has no effect when PHP is running in safe mode.<br />
1345 You can also use any string as in php.ini, eg. '16M'. Ensure
1349 <dd>Mark used tables and make it possible to show databases with locked
1354 generated by phpMyAdmin should be displayed or not.</dd>
1357 <dd>Defines whether normal users (non-administrator) are allowed to
1358 delete their own database or not. If set as FALSE, the link "Drop
1360 mydatabase" will be rejected. Quite practical for
1362 customers.<br />
1363 Please note that this limitation of SQL queries is not as strict as
1364 when using MySQL privileges. This is due to nature of SQL queries
1365 which might be quite complicated. So this choice should be viewed as
1366 help to avoid accidental dropping rather than strict privilege
1367 limitation.</dd>
1371 displayed when you're about to lose data.</dd>
1374 <dd>Define whether the previous login should be recalled or not in cookie
1375 authentication mode.<br /><br />
1377 This is automatically disabled if you do not have configured
1379 </dd>
1382 <dd>Define how long is login cookie valid. Please note that php
1383 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1384 might limit session validity and if session is lost, login cookie is
1386 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1390 means that it will be kept for existing session. This is recommended
1391 for not trusted environments.</dd>
1394 <dd>If enabled (default), logout deletes cookies for all servers,
1395 otherwise only for current one. Setting this to false makes it easy to
1396 forget to log out from other server, when you are using more of
1397 them.</dd>
1403 <dd>Define whether phpMyAdmin will continue executing a multi-query
1404 statement if one of the queries fails. Default is to abort execution.</dd>
1407 <dd>Define whether phpMyAdmin will output the results of each query of a
1408 multi-query statement embedded into the
1413 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1414 <br /><br />
1417 MySQL servers behind the firewall where your
1419 </dd>
1428 <dd>Defines whether to use a select-based menu and display only the current
1429 tables in the left frame (smaller page). Only in Non-Lightmode you can
1430 use the feature to display nested folders using
1432 </dd>
1435 <dd>In light mode, defines whether to display the names of databases (in the
1436 selector) using a tree, see also
1438 </dd>
1441 string or array</dt>
1442 <dd>The string used to separate the parts of the database name when showing
1443 them in a tree. Alternatively you can specify more strings in an array
1444 and all of them will be used as a separator.</dd>
1447 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1448 This means if you have tables like 'first__second__third' this will be
1450 If set to FALSE or empty, the feature is disabled. NOTE: You should
1451 not use this separator at the beginning or end of a
1452 table name or multiple times after another without any other
1453 characters in between.</dd>
1456 <dd>Defines how many sublevels should be displayed when splitting
1457 up tables by the above separator.</dd>
1460 <dd>Defines whether to display table comment as tool-tip in left frame or
1461 not.</dd>
1464 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1465 comment and the real name. That means that if you have a table called
1466 'user0001' and add the comment 'MyName' on it, you will see the name
1467 'MyName' used consequently in the left frame and the tool-tip shows
1468 the real name of the DB.</dd>
1471 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1473 When setting this to 'nested', the Alias of the Tablename is only used
1474 to split/nest the tables according to the
1476 directive. So only the folder is called like the Alias, the tablename itself
1477 stays the real tablename.</dd>
1480 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1483 <dd>Enter URL where logo in the navigation frame will point to.
1484 For use especially with self made theme which changes this.
1493 <dd>Defines whether or not to display a server choice at the top of the left frame.
1494 Defaults to FALSE.</dd>
1496 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1497 Defaults to FALSE (drop-down).</dd>
1499 <dd>Defines whether to display database choice in light navigation frame as links
1500 instead of in a drop-down. Defaults to 'auto' - on main page list is
1501 shown, when database is selected, only drop down is displayed.</dd>
1504 <dd>Defines the tab displayed by default when clicking the small
1505 icon next to each table name in the navigation panel. Possible
1511 <dd>Defines whether or not to display space usage and statistics about databases
1512 and tables.<br />
1513 Note that statistics requires at least MySQL 3.23.3 and that, at this
1514 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1517 <dd>Defines whether to display detailed server information on main page.
1518 You can additionally hide more information by using
1520 </dd>
1525 </dt>
1528 not at the starting main (right) frame. This setting
1529 does not check MySQL commands entered directly.<br /><br />
1531 Please note that to block the usage of phpinfo() in scripts, you
1538 hard coded password value in the configuration file, end users can't
1539 be allowed to change their passwords.</dd>
1542 <dd>Defines whether to suggest a database name on the
1546 <dd>Defines whether navigation bar buttons and the right panel top menu
1547 contain text or symbols only. A value of TRUE displays icons, FALSE
1548 displays text and 'both' displays both icons and text.</dd>
1551 <dd>Defines whether a user should be displayed a
1555 <dd>Number of rows displayed when browsing a result set. If the result set
1562 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1566 option is ticked by default.</dd>
1570 from editing when browsing a table's content. Valid values are:
1575 </ul>
1576 </dd>
1579 <dd>Defines whether or not MySQL functions fields should be initially
1580 displayed in edit/insert mode. Since version 2.10, the user can
1581 toggle this setting from the interface.
1582 </dd>
1585 <dd>Defines whether or not type fields should be initially
1586 displayed in edit/insert mode. The user can
1587 toggle this setting from the interface.
1588 </dd>
1591 <dd>Defines which type of editing controls should be used for CHAR and
1592 VARCHAR columns. Possible values are:
1593 <ul><li>input - this allows to limit size of text to size of columns in
1594 MySQL, but has problems with newlines in columns</li>
1595 <li>textarea - no problems with newlines in columns, but also no
1596 length limitations</li>
1597 </ul>
1598 Default is old behavior so input.</dd>
1604 <dd>If there are fewer items than this in the set of foreign keys, then a
1605 drop-down box of foreign keys is presented, in the style described by the
1607 setting.</dd>
1610 <dd>For the foreign key drop-down fields, there are several methods of
1611 display, offering both the key and value data. The contents of the
1612 array should be one or both of the following strings:
1618 </dt>
1619 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1620 creating a dump file</dd>
1623 </dt>
1624 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1625 compressed exports. This doesn't affect smaller dumps and allows users to
1626 create larger dumps that won't otherwise fit in memory due to php
1627 memory limit. Produced files contain more GZip/BZip2 headers, but all
1628 normal programs handle this correctly.</dd>
1632 mainframe.</dd>
1636 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1641 <dd>How many columns will be utilized to display the tables on the
1642 database property view? Default is 1 column. When setting this to a
1643 value larger than 1, the type of the database will be omitted for more
1644 display space.</dd>
1648 <dd>Defines the tab displayed by default on server view. Possible
1655 <dd>Defines the tab displayed by default on database view. Possible
1660 <dd>Defines the tab displayed by default on table view. Possible
1667 points to the MySQL documentation (type depends
1668 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1669 generated.<br />
1671 for more information about MySQL manuals and their types.</dd>
1674 <dd>Type of MySQL documentation:
1680 </ul>
1681 </dd>
1684 <dd>Defines the default language to use, if not browser-defined or
1685 user-defined.<br />
1686 The corresponding language file needs to be in
1688 </dd>
1691 <dd>Defines the default connection collation to use, if not
1692 user-defined.<br />
1698 The corresponding language file needs to be in
1700 </dd>
1703 <dd>Limit list of available languages to those matching the given regular
1704 expression. For example if you want only Czech and English, you should
1708 <dd>You can select here which functions will be used for character set
1709 conversion. Possible values are:
1710 <ul><li>auto - automatically use available one (first is tested
1711 iconv, then recode)</li>
1715 </ul>
1716 Default is auto.</dd>
1717 <dd>
1718 Enabled charset conversion activates a pull-down menu
1719 in the Export and Import pages, to choose the character set when
1720 exporting a file. The default value in this menu comes from
1722 </dd>
1725 <dd>Specify some parameters for iconv used in charset conversion. See
1728 used, so that invalid characters will be transliterated.</dd>
1731 <dd>Available character sets for MySQL conversion. You can add your own (any of
1732 supported by recode/iconv) or remove these which you don't use.
1733 Character sets will be shown in same order as here listed, so if you
1734 frequently use some of these move them to the top.</dd>
1739 default empty, you need to fill in some trusted proxy servers if you
1740 want to use rules for IP addresses behind proxy.<br /><br />
1742 The following example specifies that phpMyAdmin should trust a
1744 <pre>
1745 $cfg['TrustedProxies'] =
1747 </pre>
1748 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1749 client's IP address as usual.
1750 </dd>
1754 MIME transformations.<br />
1755 Possible values are:
1756 <ul><li>auto - automatically detect, this is a bit expensive
1758 according to your server real possibilities</li>
1761 </ul>
1762 Default is auto.
1763 </dd>
1766 <dd>
1767 We normally check the permissions on the configuration file to ensure
1768 it's not world writable. However, phpMyAdmin could be installed on
1769 a NTFS filesystem mounted on a non-Windows server, in which case the
1770 permissions seems wrong but in fact cannot be detected. In this case
1772 </dd>
1775 <dd>
1776 Limit for length of URL in links. When length would be above this limit, it
1777 is replaced by form with button.
1778 This is required as some web servers (IIS) have problems with long URLs.
1780 </dd>
1784 </dd>
1786 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1787 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1788 </dt>
1789 <dd>The background styles used for both the frames.
1792 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1794 <dd>The style used for the pointer in the navi frame.
1798 </dt>
1799 <dd>The color used for the database name in the navi frame.
1808 </dd>
1812 <dd>The style used for table headers. See
1817 </dd>
1821 </dd>
1823 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1825 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1827 </dt>
1829 The former feature highlights the row over which your mouse is passing
1830 and the latter lets you visually mark/unmark rows by clicking on
1831 them.<br />
1836 <dd>You put here a valid CSS font family value, for example
1841 <dd>You put here a valid CSS font family value, for example
1855 </dt>
1857 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1859 The Char* values are used for CHAR and VARCHAR editing (if configured
1863 </dt>
1867 </dt>
1868 <dd>Defines if the whole textarea of the query box will be selected on
1869 click.</dd>
1872 </dt>
1873 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1874 editing.</dd>
1877 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1878 Can be turned off by a toggle button on the browse page.</dd>
1882 </dt>
1883 <dd>Defines the place where modify and delete links would be put when
1884 tables contents are displayed (you may have them displayed both at the
1885 left and at the right).
1891 Define which one is displayed by default. The first mode displays each
1892 row on a horizontal line, the second rotates the headers by 90
1893 degrees, so you can use descriptive headers even though columns only
1894 contain small values and still print them out. The vertical mode sorts
1895 each row on a vertical lineup.
1896 </dd>
1899 <dd>
1900 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1901 'css' the rotation of the header for horizontalflipped is done via
1902 CSS. The CSS transformation currently works only in Internet
1903 Explorer.If set to 'fake' PHP does the transformation for you, but of
1904 course this does not look as good as CSS. The 'auto' option enables
1905 CSS transformation when browser supports it and use PHP based one
1906 otherwise.
1907 </dd>
1911 string or integer</dt>
1912 <dd>When editing/creating new columns in a table all fields normally get
1913 lined up one field a line. (default: 'horizontal'). If you set this to
1914 'vertical' you can have each field lined up vertically beneath each
1915 other. You can save up a lot of place on the horizontal direction and
1916 no longer have to scroll. If you set this to integer, editing of fewer
1917 columns will appear in 'vertical' mode, while editing of more columns
1918 still in 'horizontal' mode. This way you can still effectively edit
1919 large number of columns, while having full view on few of them.</dd>
1923 </dt>
1925 display of column comments in Browse or Property display. In browse
1926 mode, the comments are shown inside the header. In property mode,
1927 comments are displayed using a CSS-formatted dashed-line below the
1928 name of the column. The comment is shown as a tool-tip for that column.
1929 </dd>
1941 <dd>Whether to display a link to validate a query in any SQL Query box.
1948 <dd>
1949 The name of the directory where
1951 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1952 are available under a drop-down box when you click the database or
1953 table name, then the Import tab.
1954 <br /><br />
1956 If you want different directory for each user, %u will be replaced
1957 with username.<br /><br />
1961 compressed formats is enabled).<br /><br />
1963 This feature is useful when your file is too big to be uploaded via
1965 uploads are disabled in PHP.<br /><br />
1967 Please note that if PHP is running in safe mode, this directory must
1968 be owned by the same user as the owner of the phpMyAdmin scripts.
1969 <br /><br />
1973 alternatives.
1974 </dd>
1977 <dd>
1978 The name of the directory where dumps can be saved.<br /><br />
1980 If you want different directory for each user, %u will be replaced
1981 with username.<br /><br />
1983 Please note that the directory must exist and has to be writable for
1984 the user running webserver.<br /><br />
1986 Please note that if PHP is running in safe mode, this directory must
1987 be owned by the same user as the owner of the phpMyAdmin scripts.
1988 </dd>
1991 <dd>
1992 The name of the directory where temporary files can be stored.
1993 <br /><br />
1995 This is needed for native MS Excel export, see
2001 <br /><br />
2003 If the directory where phpMyAdmin is installed is subject to an
2005 temporary directory in some directory accessible by the web
2006 server. However for security reasons, this directory should be outside
2007 the tree published by webserver. If you cannot avoid having this
2008 directory published by webserver, place at least an empty
2010 possible.
2011 <br /><br />
2013 This directory should have as strict permissions as possible as the only
2014 user required to access this directory is the one who runs the
2015 webserver. If you have root privileges, simply make this user owner of
2016 this directory and make it accessible only by it:
2017 <br /><br />
2019 <pre>
2020 chown www-data:www-data tmp
2021 chmod 700 tmp
2022 </pre>
2024 If you cannot change owner of the directory, you can achieve a similar
2027 <pre>
2028 chmod 700 tmp
2029 setfacl -m "g:www-data:rwx" tmp
2030 setfacl -d -m "g:www-data:rwx" tmp
2031 </pre>
2033 If neither of above works for you, you can still make the directory
2035 system reading and writing data in this directory.
2036 </dd>
2039 <dd>
2040 In this array are defined default parameters for export, names of
2041 items are similar to texts seen on export page, so you can easily
2042 identify what they mean.
2043 </dd>
2046 <dd>
2047 Defines how the export form is displayed when it loads. Valid values are:
2050 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2051 </dd>
2054 <dd>
2055 In this array are defined default parameters for import, names of
2056 items are similar to texts seen on import page, so you can easily
2057 identify what they mean.
2058 </dd>
2061 <dd>
2062 Repeat the headers every X cells, or 0 to deactivate.
2063 </dd>
2071 </dt>
2072 <dd>
2073 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2074 or icon is always displayed on the left panel. If JavaScript is enabled in
2075 your browser, a click on this opens a distinct query window, which is
2076 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2077 changes to display a query box.<br /><br />
2079 The size of this query window can be customized with
2081 - both integers for the size in pixels. Note that normally, those
2083 theme you are using.<br /><br />
2087 opens the query window and puts the current query
2088 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2089 query in the right panel's query box.
2090 <br /><br />
2091 The usage of the JavaScript query window is recommended if you have a
2092 JavaScript enabled browser. Basic functions are used to exchange quite
2093 a few variables, so most 4th generation browsers should be capable to
2094 use that feature. It currently is only tested with Internet Explorer 6
2095 and Mozilla 1.x.
2096 <br /><br />
2098 to a table, which has to be created by you (see <a
2100 all your queries will be appended to the form, but only as long as
2101 your window is opened they remain saved.
2102 <br /><br />
2103 When using the JavaScript based query window, it will always get
2104 updated when you click on a new table/db to browse and will focus if
2105 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2106 the query window by checking the box "Do not overwrite this query from
2107 outside the window" below the query textarea. Then you can browse
2108 tables/databases in the background without losing the contents of the
2109 textarea, so this is especially useful when composing a query with
2110 tables you first have to look in. The checkbox will get automatically
2111 checked whenever you change the contents of the textarea. Please
2112 uncheck the button whenever you definitely want the query window to
2113 get updated even though you have made alterations.
2114 <br /><br />
2117 <br /><br />
2118 The query window also has a custom tabbed look to group the features.
2120 default tab to be used when opening the query window. It can be set to
2121 either 'sql', 'files', 'history' or 'full'.</dd>
2127 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2129 If the approximate row count as returned by
2132 count will be used.
2133 </dd>
2135 <dd>For VIEWs, since obtaining the exact count could have an
2136 impact on performance, this value is the maximum to be displayed, using
2138 any row counting.
2139 </dd>
2143 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2145 page. By clicking on the button 'toggle scratchboard' on the page
2146 where you edit x/y coordinates of those elements you can activate a
2147 scratchboard where all your elements are placed. By clicking on an
2148 element, you can move them around in the pre-defined area and the x/y
2149 coordinates will get updated dynamically. Likewise, when entering a
2150 new position directly into the input field, the new position in the
2151 scratchboard changes after your cursor leaves the input field.<br />
2152 You have to click on the 'OK'-button below the tables to save the new
2153 positions. If you want to place a new element, first add it to the
2154 table of elements and then you can drag the new element around.<br />
2155 By changing the paper size and the orientation you can change the size
2156 of the scratchboard as well. You can do so by just changing the
2157 dropdown field below, and the scratchboard will resize automatically,
2158 without interfering with the current placement of the elements.<br />
2159 If ever an element gets out of range you can either enlarge the paper
2160 size or click on the 'reset' button to place all elements below each
2161 other.<br />
2163 get this control to work. The basic Drag&Drop script functionality
2164 was kindly borrowed from www.youngpup.net and is underlying so
2165 specific license.</dd>
2168 <dd>Sorts database and table names according to natural order (for example,
2169 t1, t2, t10). Currently implemented in the left panel (Light mode)
2170 and in Database view, for the table list.</dd>
2179 that users can't set through user preferences. For possible values, refer
2186 <dd>Allows you to specify window's title bar. You can use
2188 </dd>
2198 </dd>
2201 <dd>If theme manager is active, use this as the path of the subdirectory
2202 containing all the themes.</dd>
2216 </dt>
2217 <dd>Default queries that will be displayed in query boxes when user didn't
2218 specify any. You can use standard
2220 </dd>
2223 <dd>
2224 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
2225 default we use HTML to format the query, but you can disable this by
2227 </dd>
2230 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2231 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2232 query inside a bracket is indented. By changing
2235 specifies the units of the indent amount that you specified. This is
2236 used via stylesheets.</dd>
2239 <dd>This array is used to define the colours for each type of element of
2240 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2242 If you specify an empty string for the color of a class, it is ignored
2243 in creating the stylesheet.
2244 You should not alter the class names, only the colour strings.<br />
2265 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2269 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2270 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2271 </ul>
2272 </dd>
2276 <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,
2277 as originally published on
2279 <br />
2280 For help in setting up your system to use the service, see the
2282 </dd>
2286 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2287 and any password, so we use those by default. Instead, if
2288 you have an account with them, you can put your login details
2289 here, and it will be used in place of the anonymous login.</dd>
2290 </dl>
2291 </dd>
2294 <dd><b>DEVELOPERS ONLY!</b></dd>
2297 <dd><b>DEVELOPERS ONLY!</b><br />
2298 Enable logging queries and execution times to be displayed in the bottom
2299 of main page (right frame).</dd>
2302 <dd><b>DEVELOPERS ONLY!</b><br />
2303 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2304 the code.<br />
2305 For help in setting up your system to this, see the
2309 <dd><b>DEVELOPERS ONLY!</b><br />
2310 Enable profiling support for phpMyAdmin. This will append a chunk of data
2311 to the end of every page displayed in the main window with profiling
2312 statistics for that page.<br />
2313 You may need to increase the maximum execution time for this to
2314 complete successfully.<i>Profiling was removed from the code for
2315 version 2.9.0 due to licensing issues.</i></dd>
2317 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2318 <dd><b>DEVELOPERS ONLY!</b><br />
2319 When profiling data is displayed, this variable controls the threshold of
2320 display for any profiling data, based on the average time each time has
2321 taken. If it is over the threshold it is displayed, otherwise it is not
2322 displayed. This takes a value in milliseconds. In most cases you don't need
2323 to edit this.</dd>
2326 <dd>All possible types of a MySQL column. In most cases you don't need to
2327 edit this.</dd>
2330 <dd>Possible attributes for columns. In most cases you don't need to edit
2331 this.</dd>
2334 <dd>A list of functions MySQL supports. In most cases you don't need to
2335 edit this.</dd>
2338 <dd>Mapping of column types to meta types used for preferring displayed
2339 functions. In most cases you don't need to edit this.</dd>
2342 <dd>Functions preferred for column meta types as defined in
2343 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2344 to edit this.</dd>
2347 <dd>Functions selected by default when inserting/changing row, Functions
2348 are defined for meta types from
2350 <code>first_timestamp</code>, which is used for first timestamp column
2351 in table.</dd>
2354 <dd>Operators available for search operations on numeric and date columns.
2355 </dd>
2358 <dd>Operators available for search operations on character columns.
2359 Note that we put <code>LIKE</code> by default instead of
2360 <code>LIKE %...%</code>, to avoid unintended performance problems
2361 in case of huge tables.</dd>
2364 <dd>Operators available for search operations on ENUM columns.</dd>
2367 <dd>Additional operators available for search operations when the
2368 column can be null.</dd>
2370 </dl>
2372 <!-- TRANSFORMATIONS -->
2378 </ol>
2382 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2384 section</a> on how to do so.</p>
2386 <p> You can apply different transformations to the contents of each column. The
2387 transformation will take the content of each column and transform it with
2388 certain rules defined in the selected transformation.</p>
2390 <p> Say you have a column 'filename' which contains a filename. Normally you would
2391 see in phpMyAdmin only this filename. Using transformations you can transform
2392 that filename into a HTML link, so you can click inside of the phpMyAdmin
2393 structure on the column's link and will see the file displayed in a new browser
2394 window. Using transformation options you can also specify strings to
2395 append/prepend to a string or the format you want the output stored in.</p>
2397 <p> For a general overview of all available transformations and their options,
2398 you can consult your
2399 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2400 installation.</p>
2402 <p> For a tutorial on how to effectively use transformations, see our
2404 the official phpMyAdmin homepage.</p>
2408 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2409 clicking on the 'Structure' link for a table). There click on
2410 "Change" (or change icon) and there you will see three new
2411 fields at
2412 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2413 'Transformation options'.</p>
2415 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2416 that corresponds to the column's contents. Please note that
2417 transformations are inactive as long as no MIME-type is selected.</li>
2419 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2420 hopefully growing amount of pre-defined transformations. See below for information on
2421 how to build your own transformation.<br />
2423 There are global transformations and mimetype-bound transformations. Global transformations
2424 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2425 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2426 transformations which operate on the main mimetype (like 'image'), which will most likely
2427 take the subtype into regard, and those who only operate on a
2428 specific subtype (like 'image/jpeg').<br />
2430 You can use transformations on mimetypes for which the function was not defined for. There
2431 is no security check for you selected the right transformation, so take care of what the
2432 output will be like.</li>
2434 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2435 transform-function specific options here. Usually the transforms can operate with default
2436 options, but it is generally a good idea to look up the overview to see which options are
2437 necessary.<br />
2439 Much like the ENUM/SET-Fields, you have to split up several options using the format
2440 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2441 parsed as an array, leaving the first value the first element in the array, and so
2442 forth.<br />
2444 If you want to specify a MIME character set you can define it in the transformation_options.
2445 You have to put that outside of the pre-defined options of the specific mime-transform,
2447 for which you can specify 2 options and you want to append a character set, enter "'first
2448 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2450 </ul>
2454 <p> All mimetypes and their transformations are defined through single files in
2455 the directory 'libraries/transformations/'.</p>
2457 <p> They are stored in files to ease up customization and easy adding of new
2458 transformations.</p>
2460 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2461 always work. It makes no sense to apply a transformation to a mimetype the
2462 transform-function doesn't know to handle.</p>
2464 <p> One can, however, use empty mime-types and global transformations which should work
2465 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2466 for, but pay attention to option usage as well as what the transformation does to your
2467 column.</p>
2469 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2470 any other transform function and provides some basic functions.</p>
2472 <p> There are 5 possible file names:</p>
2474 <ol><li>A mimetype+subtype transform:<br /><br />
2476 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2478 Please not that mimetype and subtype are separated via '_', which shall
2479 not be contained in their names. The transform function/filename may
2480 contain only characters which cause no problems in the file system as
2481 well as the PHP function naming convention.<br /><br />
2483 The transform function will the be called
2484 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2486 <b>Example:</b><br /><br />
2488 <tt>text_html__formatted.inc.php</tt><br />
2489 <tt>PMA_transform_text_html__formatted()</tt></li>
2491 <li>A mimetype (w/o subtype) transform:<br /><br />
2493 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2495 Please note that there are no single '_' characters.
2496 The transform function/filename may contain only characters which cause
2497 no problems in the file system as well as the PHP function naming
2498 convention.<br /><br />
2500 The transform function will the be called
2501 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2503 <b>Example:</b><br /><br />
2505 <tt>text__formatted.inc.php</tt><br />
2506 <tt>PMA_transform_text__formatted()</tt></li>
2508 <li>A mimetype+subtype without specific transform function<br /><br />
2510 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2512 Please note that there are no '__' characters in the filename. Do not
2513 use special characters in the filename causing problems with the file
2514 system.<br /><br />
2516 No transformation function is defined in the file itself.<br /><br />
2518 <b>Example:</b><br /><br />
2520 <tt>text_plain.inc.php</tt><br />
2521 (No function)</li>
2523 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2525 <tt>[mimetype].inc.php</tt><br /><br />
2527 Please note that there are no '_' characters in the filename. Do not use
2528 special characters in the filename causing problems with the file system.
2529 <br /><br />
2531 No transformation function is defined in the file itself.<br /><br />
2533 <b>Example:</b><br /><br />
2535 <tt>text.inc.php</tt><br />
2536 (No function)</li>
2538 <li>A global transform function with no specific mimetype<br /><br />
2540 <tt>global__[transform].inc.php</tt><br /><br />
2542 The transform function will the be called
2543 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2545 <b>Example:</b><br /><br />
2547 <tt>global__formatted</tt><br />
2548 <tt>PMA_transform_global__formatted()</tt></li>
2549 </ol>
2551 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2552 transform function.</p>
2554 <p> All filenames containing no '__' in themselves are not shown as valid transform
2555 functions in the dropdown.</p>
2557 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2558 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2559 without a transform function.</p>
2561 <p> To create a new transform function please see
2562 <tt>libraries/transformations/template_generator.sh</tt>.
2563 To create a new, empty mimetype please see
2564 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2566 <p> A transform function always gets passed three variables:</p>
2568 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2569 you want to transform.</li>
2570 <li><b>$options</b> - Contains any user-passed options to a transform function
2571 as an array.</li>
2572 <li><b>$meta</b> - Contains an object with information about your column.
2573 The data is drawn from the output of the
2575 function. This means, all object properties described on the
2577 available in this variable and can be used to transform a column accordingly
2578 to unsigned/zerofill/not_null/... properties.<br />
2579 The $meta->mimetype variable contains the original MIME-type of the
2580 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2581 </ol>
2583 <p> Additionally you should also provide additional function to provide
2584 information about the transformation to the user. This function should
2585 have same name as transformation function just with appended
2586 <code>_info</code> suffix. This function accepts no parameters and returns
2587 array with information about the transformation. Currently following keys
2588 can be used:
2589 </p>
2590 <dl>
2591 <dt><code>info</code></dt>
2592 <dd>Long description of the transformation.</dd>
2593 </dl>
2595 <!-- FAQ -->
2602 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2607 </ol>
2609 <p> Please have a look at our
2611 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2612 features and or interface.</p>
2618 action is required or phpMyAdmin sends a blank page or a page full of
2619 cryptic characters to my browser, what can I do?</a></h4>
2622 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2623 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2624 configuration file.<br /></p>
2629 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2630 See also the
2632 entry about PHP bugs with output buffering.<br />
2633 If your server keeps crashing, please ask for help in the various Apache
2634 support groups.</p>
2643 application misbehaved by not returning a complete set of
2645 </h4>
2647 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2648 Have a look at the last message in this
2650 official PHP bug database.</p>
2655 and/or many error messages with the
2657 mode.</a></h4>
2659 <p> This is a known problem with the PHP
2661 filter: it's not so stable. Please use instead the cookie authentication mode.
2662 </p>
2667 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2668 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2669 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2670 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2671 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2676 work.</a></h4>
2678 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2679 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2680 or not, and so on). So, you must have Zlib/Bzip2
2681 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2685 an error about safe mode being in effect.</a></h4>
2687 <p> Your uploaded file is saved by PHP in the "upload dir", as
2688 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2689 the system default is <i>/tmp</i>).<br />
2690 We recommend the following setup for Apache servers running in safe mode,
2691 to enable uploads of files while being reasonably secure:</p>
2693 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2694 <li>give ownership to the Apache server's user.group:
2695 <tt>chown apache.apache /tmp/php</tt></li>
2696 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2697 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2698 <li>restart Apache</li>
2699 </ul>
2703 general file uploads don't work on my system and uploaded files have a
2704 <tt>Content-Type:</tt> header in the first line.</a></h4>
2706 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2707 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2708 So the problem is that this package has a serious bug that was corrected
2709 ages ago in PHP (2001-01-28: see
2711 for more details). The problem is that the bugged package is still
2712 available though it was corrected (see
2714 for more details).<br />
2715 So please download
2716 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2717 and the problem should go away.<br />
2718 And that fixes the \r\n problem with file uploads!</p>
2722 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2723 I'm using the Apache server.</a></h4>
2725 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2726 your <i>httpd.conf</i>:</p>
2730 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2734 uploading a file from the query box.</a></h4>
2736 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2737 restrictions. However you need to create temporary directory and
2739 The uploaded files will be moved there, and after execution of your
2745 <p> The MySQL manual explains how to
2747 reset the permissions</a>.</p>
2752 execute a bookmark.</a></h4>
2754 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2755 cannot access the uploaded query.</p>
2760 submit a query from the convenient text area.</a></h4>
2762 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2763 and try to increase it.</p>
2767 </h4>
2769 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2770 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2771 names to align with current standards.</p>
2776 </h4>
2778 <p> Starting with version 2.7.0, the import engine has been re–written and these
2779 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2780 to take advantage of the new import features.</p>
2782 <p> The first things to check (or ask your host provider to check) are the
2783 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2784 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2785 All of these three settings limit the maximum size of data that can be
2786 submitted and handled by PHP. One user also said that post_max_size
2787 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2789 There exist several workarounds if your upload is too big or your
2790 hosting provider is unwilling to change the settings:</p>
2793 feature. This allows one to
2794 upload a file to the server via scp, ftp, or your favorite file transfer
2795 method. PhpMyAdmin is then able to import the files from the temporary
2797 section</a> of this document.</li>
2799 BigDump</a>) to split the files before uploading. We cannot support this
2800 or any third party applications, but are aware of users having success
2801 with it.</li>
2802 <li>If you have shell (command line) access, use MySQL to import the files
2803 directly. You can do this by issuing the "source" command from
2804 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2805 </ul>
2809 support?</a></h4>
2811 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2812 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2813 connect to your MySQL server using PHP's classic
2816 is available in php 5.0. The latter one should be used unless you have
2817 good reason not to do so.<br />
2818 When compiling php, we strongly recommend that you manually link the MySQL
2819 extension of your choice to a MySQL client library of at least the same
2820 minor version since the one that is bundled with some PHP distributions is
2823 If your webserver is running on a windows system, you might want to try
2824 MySQL's
2826 instead of the MySQL / MySQLi extensions that are bundled with the official
2827 php Win32 builds.</p>
2831 message, "Client does not support authentication protocol requested
2832 by server; consider upgrading MySQL client"</a></h5>
2834 <p> You tried to access MySQL with an old MySQL client library. The version of
2835 your MySQL client library can be checked in your phpinfo() output.
2836 In general, it should have at least the same minor version as your server
2840 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2841 changed the authentication hash and your PHP is trying to use the old method.
2843 with the proper client library to match your MySQL installation. Your
2844 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2845 More information (and several workarounds) are located in the
2847 </p>
2854 script seems not to know the font face I'm using!</a></h4>
2856 <p> The "FPDF" library we're using for this feature requires some
2857 special files to use font faces.<br />
2859 these files.</p>
2863 check PHP Configuration".</a></h4>
2865 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2866 "MySQL extension". This extension may be part of the PHP
2867 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2868 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2869 to load the extension but failed.<br /><br />
2871 Usually, the problem is solved by installing a software package called
2872 "PHP-MySQL" or something similar.</p>
2877 and I cannot log in using cookie auth.</a></h4>
2879 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2883 so I cannot upload.</a></h4>
2885 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2886 parameter is not set to "on".</p>
2890 a new table the table and column names are changed to lowercase!</a></h4>
2892 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2893 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2894 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2895 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2896 directory and add the following line to the group [mysqld]:</p>
2898 <pre>set-variable = lower_case_table_names=0</pre>
2900 <p> Next, save the file and restart the MySQL service. You can always check the
2901 value of this directive using the query</p>
2903 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2910 and I get problems, such as undefined variables when I run a
2913 <p> A tip from Jose Fandos: put a comment on the following two lines
2914 in httpd.conf, like this:</p>
2916 <pre>
2917 # mod_gzip_item_include file \.php$
2919 </pre>
2921 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2922 PHP scripts. Of course you have to restart Apache.</p>
2927 I get the error "No input file specified" when trying to
2928 run phpMyAdmin.</a></h4>
2930 <p> This is a permission problem. Right-click on the phpmyadmin folder
2931 and choose properties. Under the tab Security, click on "Add"
2932 and select the user "IUSR_machine" from the list. Now set his
2933 permissions and it should work.</p>
2937 db_structure.php with plenty of tables).</a></h4>
2940 GZIP output buffering is enabled. If you turn off it (by
2942 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2943 PHP 5.0.0.</p>
2947 message 'Errorcode: 13'. What does this mean?</a></h4>
2949 <p> This can happen due to a MySQL bug when having database / table names with
2950 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2951 To fix this, turn off this directive, convert all database and table names
2952 to lower case and turn it on again. Alternatively, there's a bug-fix
2953 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2957 and the columns are duplicated.</a></h4>
2959 <p> It is possible to configure Apache in such a way that PHP has problems
2960 interpreting .php files.</p>
2962 <p> The problems occur when two different (and conflicting) set of directives
2963 are used:</p>
2965 <pre>
2966 SetOutputFilter PHP
2967 SetInputFilter PHP
2968 </pre>
2970 <p> and</p>
2972 <pre>AddType application/x-httpd-php .php</pre>
2974 <p> In the case we saw, one set of directives was in
2975 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2976 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2977 The recommended way is with <tt>AddType</tt>, so just comment out
2978 the first set of lines and restart Apache:</p>
2980 <pre>
2981 #SetOutputFilter PHP
2982 #SetInputFilter PHP
2983 </pre>
2988 <p> This problem is known to happen when the server is running Turck MMCache
2989 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2994 <p>Yes.</p>
2995 <p>
2996 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
2997 is still maintained.
2998 </p>
3001 <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>
3003 <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>
3006 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3007 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3008 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3009 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3010 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3011 enabled.) Click <tt>OK</tt>.</li>
3012 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3013 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3014 </ol>
3018 PHP 5.0.4 on 64-bit systems?</a></h4>
3020 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
3021 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3027 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
3028 the order of the server paragraph in <tt>config.inc.php</tt>.
3029 Table and script parts are optional. If you want
3030 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3031 some configuration. Following lines apply only for <a
3033 that you have enabled some features within global configuration. You need
3034 <code>Options FollowSymLinks</code> and <code>AllowOverride
3035 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3036 you need mod_rewrite to be enabled. Then you just need to create following
3037 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3038 (don't forget to change directory name inside of it):</p>
3040 <pre>
3041 RewriteEngine On
3042 RewriteBase /path_to_phpMyAdmin
3043 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3044 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3045 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3046 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3047 </pre>
3050 <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>
3052 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3053 following rewrite rule:</p>
3055 <pre>
3056 RewriteEngine On
3057 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3058 </pre>
3062 </h4>
3063 <p>
3064 There can be many explanations to this and a look at your server's
3065 error log file might give a clue.
3066 </p>
3070 password encryption in cookie auth doesn't work.</a></h4>
3072 <p> If your cluster consist of different architectures, PHP code used for
3073 encryption/decryption won't work correct. This is caused by use of
3074 pack/unpack functions in code. Only solution is to use mcrypt extension
3075 which works fine in this case.</p>
3080 <p> Yes but the default configuration values of Suhosin are known to cause
3081 problems with some operations, for example editing a table with many
3082 columns and no primary key or with textual primary key.
3083 </p>
3084 <p>
3085 Suhosin configuration might lead to malfunction in some cases and it can
3086 not be fully avoided as phpMyAdmin is kind of application which needs to
3087 transfer big amounts of columns in single HTTP request, what is something
3088 what Suhosin tries to prevent. Generally all
3089 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3090 <code>suhosin.get.*</code> directives can have negative effect on
3091 phpMyAdmin usability. You can always find in your error logs which limit
3092 did cause dropping of variable, so you can diagnose the problem and adjust
3093 matching configuration variable.
3094 </p>
3095 <p>
3096 The default values for most Suhosin configuration options will work in most
3097 scenarios, however you might want to adjust at least following parameters:
3098 </p>
3100 <ul>
3101 <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>
3102 <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>
3103 <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>
3104 <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>
3105 <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>
3106 <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>
3107 <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>
3108 <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>
3109 </ul>
3111 <p>
3113 <tt>SuhosinDisableWarning</tt> directive</a>.
3114 </p>
3118 but then my connection is redirected back to http. What can cause this
3119 behavior?</a></h4>
3121 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3122 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>
3125 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3127 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3128 Example from the Apache 2.2 documentation:</p>
3129 <pre>
3130 ProxyPass /mirror/foo/ http://backend.example.com/
3131 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3132 ProxyPassReverseCookieDomain backend.example.com public.example.com
3133 ProxyPassReverseCookiePath / /mirror/foo/
3134 </pre>
3136 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3137 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3138 This is not specific to phpmyadmin, it's just the behavior of Apache.
3139 </p>
3141 <pre>
3142 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3143 ProxyPassReverse /mirror/foo/
3144 http://backend.example.com/%7Euser/phpmyadmin
3145 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3146 </pre>
3148 <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>
3149 for more details.</p>
3153 privileges, I get an error about an unknown column.</a></h4>
3155 <p> The MySQL server's privilege tables are not up to date, you need to run
3156 the <tt>mysql_upgrade</tt> command on the server.</p>
3163 headers already sent by ..." is displayed, what's the problem?</a></h4>
3165 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3166 (I.E. no blank lines, no spaces, no characters...) neither before the
3167 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3168 tag at the end. We also got a report from a user under IIS, that used
3169 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3170 contained an end-of-line character (hex 0A) at the end; removing this character
3171 cleared his errors.</p>
3176 <p> Either there is an error with your PHP setup or your username/password is
3177 wrong. Try to make a small script which uses mysql_connect and see if it
3178 works. If it doesn't, it may be you haven't even compiled MySQL support
3179 into PHP.</p>
3183 connect to local MySQL server through socket '/tmp/mysql.sock'
3184 (111) ..." is displayed. What can I do?</a></h4>
3186 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3188 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3189 In your <i>php.ini</i> you will find a line</p>
3191 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3193 <p> change it to</p>
3195 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3197 <p> Then restart apache and it will work.</p>
3199 <p> Here is a fix suggested by Brad Ummer:</p>
3201 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3202 To do this, telnet to your server and go to the MySQL bin directory. In
3203 this directory there should be a file named <i>mysqladmin</i>. Type
3204 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3205 info about your MySQL server, including the socket
3206 (<i>/tmp/mysql.sock</i>, for example).</li>
3207 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3208 phpMyAdmin, you need to complete the socket information in the
3209 <i>config.inc.php</i>.<br />
3210 For example:
3212 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3213 <br /><br />
3215 Please also make sure that the permissions of this file allow to be readable
3216 by your webserver (i.e. '0755').</li>
3217 </ul>
3219 <p> Have also a look at the
3221 corresponding section of the MySQL documentation</a>.</p>
3225 what can I do?</a></h4>
3228 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3229 sometime.<br />
3230 Also have a look at your PHP version number: if it contains "4.0b..."
3231 it means you're running a beta version of PHP. That's not a so good idea,
3232 please upgrade to a plain revision.</p>
3236 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3237 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3239 <p> Check the value you set for the
3241 directive in the phpMyAdmin configuration file.</p>
3245 password: YES)"-error when trying to access a MySQL-Server on a
3246 host which is port-forwarded for my localhost.</a></h4>
3248 <p> When you are using a port on your localhost, which you redirect via
3249 port-forwarding to another host, MySQL is not resolving the localhost
3250 as expected.<br />
3251 Erik Wasser explains: The solution is: if your host is "localhost"
3252 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3253 connection for speeding up things. And that doesn't work in this configuration
3254 with port forwarding.<br />
3260 <p> Themes are configured with
3264 <br />
3266 should not delete the directory "original" or its underlying
3267 structure, because this is the system theme used by phpMyAdmin.
3268 "original" contains all images and styles, for backwards
3269 compatibility and for all themes that would not include images or css-files.
3270 <br /><br />
3273 is enabled, you can select your favorite theme on the main page. Your
3274 selected theme will be stored in a cookie.<br /><br /></p>
3276 <p> To create a theme:</p>
3278 <ul><li>make a new subdirectory (for example "your_theme_name") under
3280 (by default <tt>themes</tt>)</li>
3281 <li>copy the files and directories from "original" to
3282 "your_theme_name"</li>
3283 <li>edit the css-files in "your_theme_name/css"</li>
3284 <li>put your new images in "your_theme_name/img"</li>
3285 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3286 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3287 contain your chosen theme name, that will be visible in user interface</li>
3288 <li>make a new screenshot of your theme and save it under
3289 "your_theme_name/screen.png"</li>
3290 </ul>
3292 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3293 theme verbose name, theme generation and theme version. These versions and
3294 generations are enumerated from 1 and do not have any direct dependence on
3295 phpMyAdmin version. Themes within same generation should be backwards
3296 compatible - theme with version 2 should work in phpMyAdmin requiring
3297 version 1. Themes with different generation are incompatible.</p>
3299 <p> If you do not want to use your own symbols and buttons, remove the
3300 directory "img" in "your_theme_name". phpMyAdmin will
3301 use the default icons and buttons (from the system-theme "original").
3302 </p>
3306 what can I do?</a></h4>
3308 <p> Here are a few points to check:</p>
3310 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3312 directive empty. See also
3314 </li>
3315 <li>Maybe you have a broken PHP installation or you need to upgrade
3316 your Zend Optimizer. See
3318 http://bugs.php.net/bug.php?id=31134</a>.
3319 </li>
3320 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3321 set to the default (200) or another low value, you could get this
3322 error if your table has a high number of columns. Adjust this setting
3323 accordingly. (Thanks to Klaus Dorninger for the hint).
3324 </li>
3325 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3326 of ";" will cause this error. Replace it with "&;".
3327 </li>
3329 you might want to increase
3331 </li>
3332 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3333 </li>
3334 </ul>
3339 <p> To be able to see a progress bar during your uploads, your server must
3342 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3343 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3350 who logged out can not log in again in with the same nick.</a></h4>
3352 <p> This is related to the authentication mechanism (protocol) used by
3353 phpMyAdmin. To bypass this problem: just close all the opened
3354 browser windows and then go back to phpMyAdmin. You should be able to
3355 log in again.</p>
3359 limit error or a time limit error.</a></h4>
3361 <p> Compressed dumps are built in memory and because of this are limited to
3362 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3363 using
3365 (enabled by default). Zip exports can not be handled this way, so if you need
3366 Zip files for larger dump, you have to use another way.</p>
3370 when I rename a table or a column.</a></h4>
3372 <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>
3376 bundled with the MySQL server distribution.</a></h4>
3378 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3380 <pre>
3381 -- MySQL dump 8.22
3382 --
3383 -- Host: localhost Database: database
3384 ---------------------------------------------------------
3385 -- Server version 3.23.54
3386 </pre>
3388 <p> The invalid part of the code is the horizontal line made of dashes that
3389 appears once in every dump created with mysqldump. If you want to run your
3390 dump you have to turn it into valid MySQL. This means, you have to add a
3391 whitespace after the first two dashes of the line or add a # before it:
3392 <br />
3393 <code>
3394 -- -------------------------------------------------------<br />
3395 </code>
3396 or<br />
3397 <code>
3398 #---------------------------------------------------------
3399 </code>
3400 </p>
3407 <p> Please note that you should not use the separating string multiple times
3408 without any characters between them, or at the beginning/end of your table
3409 name. If you have to, think about using another TableSeparator or disabling
3410 that feature</p>
3415 <p> In Relation view, being able to choose a table in another database,
3416 or having more than one index column in the foreign key.<br /><br/>
3417 In Query-by-example (Query), automatic generation of the query
3418 LEFT JOIN from the foreign table.<br /><br/>
3419 </p>
3423 I get series of errors like "Warning: unable to parse url". How
3424 can this be fixed?</a></h4>
3425 <p>
3426 Your table neither have a primary key nor an unique one, so we must use a
3427 long expression to identify this row. This causes problems to parse_url
3428 function. The workaround is to create a primary or unique key.
3429 <br />
3430 </p>
3434 a MIME-Transformation onto!</a></h4>
3436 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3437 nested forms can be put inside the table where phpMyAdmin displays the results.
3438 You can, however, use any form inside of a table if keep the parent
3439 form-container with the target to tbl_row_delete.php and just put your own
3440 input-elements inside. If you use a custom submit input field, the form will
3441 submit itself to the displaying page again, where you can validate the
3442 $HTTP_POST_VARS in a transformation.
3444 For a tutorial on how to effectively use transformations, see our
3446 on the official phpMyAdmin-homepage.</p>
3450 MySQL server</a></h4>
3452 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3455 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3456 the quote-character (") is interpreted as an identifier quote character and
3457 not as a string quote character, which makes many internal phpMyAdmin
3459 statements. There is no workaround to this behaviour. News to this item will
3460 be posted in Bug report
3461 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3462 </p>
3466 more that one column with the same value
3467 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3468 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3470 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3471 can use it for the Edit and Delete links.</p>
3476 <p> phpMyAdmin uses a quick method to get the row count, and this method
3477 only returns an approximate count in the case of InnoDB tables. See
3479 a way to modify those results, but
3480 this could have a serious impact on performance.</p>
3485 <p> The number of records in queries containing COUNT and GROUP BY is
3486 not correctly calculated. Also, sorting results of a query like
3491 containing an hyphen.
3492 </a></h4>
3493 <p>
3494 The tests I have made with current MySQL 4.1.11 API shows that the
3495 API does not accept this syntax for the USE command. Enclosing the
3496 db name with backquotes works. For further confusion, no backquotes
3497 are needed with command-line mysql.
3498 </p>
3501 <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>
3502 <p>
3503 This has been a known limitation of phpMyAdmin since the beginning and
3504 it's not likely to be solved in the future.
3505 </p>
3507 <!-- Begin: Excel import limitations -->
3510 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3511 <p>
3512 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3513 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3514 <br /><br />
3515 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3516 </p>
3519 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3520 <p>
3521 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3522 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3523 </p>
3526 <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>
3527 <p>
3528 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3529 consider using a built-in type. These are almost always guarenteed to import correctly.
3530 </p>
3532 <!-- End: Excel import limitations -->
3533 <!-- Begin: CSV import limitations -->
3536 <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>
3537 <p>
3538 There is no reliable way to differetiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3539 </p>
3541 <!-- End: CSV import limitations -->
3542 <!-- Begin: Import type-detection limitations -->
3545 <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>
3546 <p>
3547 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
3548 you will have to edit the structure to your liking post-import.
3549 <br /><br />
3550 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
3551 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.
3552 </p>
3554 <!-- End: Import type-detection limitations -->
3556 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3559 <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
3560 need to install it for each customer.
3561 </a></h4>
3562 <p>
3563 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3564 your users. The development of this feature was kindly sponsored by
3565 NetCologne GmbH.
3566 This requires a properly setup MySQL user management and phpMyAdmin
3567 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3569 </p>
3573 access.
3574 </a></h4>
3575 <p>
3576 This depends on your system.<br />
3577 If you're running a server which cannot be accessed by other people, it's
3578 sufficient to use the directory protection bundled with your webserver
3580 If other people have telnet access to your server, you should use
3581 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3582 <br /><br />
3583 Suggestions:
3584 </p>
3585 <ul>
3586 <li>
3588 </li>
3589 <li>
3590 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3591 is a user whose password is only known to you, and apache is the
3592 group under which Apache runs.
3593 </li>
3594 <li>
3595 You should use PHP safe mode, to protect from other users that try
3597 </li>
3598 </ul>
3603 </a></h4>
3604 <p>
3609 </p>
3612 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3613 authentication.
3614 </a></h4>
3618 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3619 and/or
3621 are wrong.</li>
3623 <li>You have already setup a security mechanism for the
3624 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3625 phpMyAdmin's authentication, so remove it.</li>
3626 </ul>
3633 and put the privileges you want. For example,
3635 would let a user create/manage his/her database(s).</p>
3640 <p> If you have existing rules from an old .htaccess file, you can take them
3643 be a major benefit here if your installation is suited to using it. Then
3644 you can just add those updated lines into the
3648 <p> If you want a pre-made sample, you can try this fragment. It stops the
3649 'root' user from logging in from any networks other than the private
3652 <pre>
3653 //block root from logging in except from the private networks
3654 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3655 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3656 'deny root from all',
3657 'allow root from localhost',
3661 );
3662 </pre>
3667 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3668 different than the one set in your
3670 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3671 while a domain name is defined in the config file.</p>
3676 <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>
3682 when trying to create a table with more than 14 columns.
3683 </a></h4>
3684 <p>
3685 We could reproduce this problem only under Win98/98SE. Testing under
3686 WinNT4 or Win2K, we could easily create more than 60 columns.
3687 <br />
3688 A workaround is to create a smaller number of columns, then come back to
3689 your table properties and add the other columns.
3690 </p>
3694 <p>
3695 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3696 with each script/website that use forms.<br />
3697 Upgrade or downgrade your Xitami server.
3698 </p>
3701 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3702 <p>
3703 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3704 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3705 don't seem to work.<br />
3707 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3708 the user's temporary directory, so they must be moved before closing
3709 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3712 </p>
3716 Explorer never stores the cookies.
3717 </a></h4>
3718 <p>
3719 MS Internet Explorer seems to be really buggy about cookies, at least till
3720 version 6.
3721 </p>
3725 rows.
3726 </a></h4>
3727 <p>
3729 </p>
3732 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3733 when trying to modify a row in a table with many columns, or with a text
3734 column
3735 </a></h4>
3736 <p>
3737 Your table neither have a primary key nor an unique one, so we must use a
3738 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
3739 those browsers, and this not happen in Netscape, for example. The
3740 workaround is to create a primary or unique key, or use another browser.
3741 <br />
3742 </p>
3746 page.
3747 </a></h4>
3748 <p>
3749 Some browsers support right-clicking into the frame you want to refresh,
3750 just do this in the right frame.<br />
3751 </p>
3755 query box.
3756 </a></h4>
3757 <p>
3758 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3759 Mozilla versions.<br />
3760 </p>
3764 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3765 </a></h4>
3766 <p>
3767 This is a Mozilla bug (see bug #26882 at
3769 </p>
3774 </a></h4>
3775 <p>
3776 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3777 data in octet-stream mode. Since we can't detect the specific Netscape
3778 version, we cannot workaround this bug.
3779 </p>
3783 wrong.</a></h4>
3785 <p> Please ensure that you have set your browser's character set to the one of the
3786 language file you have selected on phpMyAdmin's start page.
3787 Alternatively, you can try the auto detection mode that is supported by the
3788 recent versions of the most browsers.</p>
3791 <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
3794 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3795 Netscape and Mozilla do not have this problem.</p>
3798 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3799 I cannot manage two servers: I log in to the first one, then the other one,
3800 but if I switch back to the first, I have to log in on each operation.</a></h4>
3806 but nothing happens after that, only a blank screen.</a></h4>
3817 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3822 address and you are starting
3824 containing a domain name, or the reverse situation.</li>
3825 <li>Security settings in IE and/or Microsoft Security Center are
3826 too high, thus blocking scripts execution.</li>
3827 <li>The Windows Firewall is blocking Apache and MySQL. You must
3831 </ul>
3834 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3835 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3836 installed in their Firefox is causing the problem.</p>
3840 clause is generated when I browse a table.</a></h4>
3841 <p> This happens only when both of these conditions are met: using the
3851 </a></h4>
3852 <p>
3853 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3854 specifying a wrong column-type.<br />
3855 Common errors include:
3856 </p>
3857 <ul>
3860 </ul>
3861 <p>
3862 Also, look at the syntax chapter in the MySQL manual to confirm that your
3863 syntax is correct.
3864 </p>
3868 columns and
3869 phpMyAdmin generates only one index with those two columns.
3870 </a></h4>
3871 <p>
3872 This is the way to create a multi-columns
3873 index. If you want two indexes, create the first one when creating the
3874 table, save, then display the table properties and click the Index link to
3875 create the other index.
3876 </p>
3880 <p>
3881 Since version 2.2.3, you have a checkbox for each column that can be null.
3883 column's value. Since version 2.5.5, you have to use the checkbox to get
3885 a literal NULL in the column, and not a NULL value (this works in PHP4).
3886 </p>
3891 <p> Click on a database or table name in the left frame, the properties will be
3893 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3894 statements that can be used to recreate your database/table.
3895 <br /><br />
3897 transmit the resulting dump to your station. Depending on your PHP
3898 configuration, you will see options to compress the dump. See also the
3900 configuration variable.<br /><br />
3903 this document.</p>
3908 </a></h4>
3910 <p> Click on a database name in the left frame, the properties will be
3912 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3914 the path to your dump filename, or use the Browse button. Then click Go.
3915 <br /><br />
3917 that you upgrade to take advantage of the new features.
3918 <br /><br />
3920 in this document.
3921 </p>
3926 <p> Here is an example with the tables persons, towns and countries, all
3928 table, create it as explained in the configuration section. Then create the
3929 example tables:</p>
3931 <pre>
3932 CREATE TABLE REL_countries (
3933 country_code char(1) NOT NULL default '',
3934 description varchar(10) NOT NULL default '',
3935 PRIMARY KEY (country_code)
3936 ) TYPE=MyISAM;
3938 INSERT INTO REL_countries VALUES ('C', 'Canada');
3940 CREATE TABLE REL_persons (
3941 id tinyint(4) NOT NULL auto_increment,
3942 person_name varchar(32) NOT NULL default '',
3944 country_code char(1) NOT NULL default '',
3945 PRIMARY KEY (id)
3946 ) TYPE=MyISAM;
3948 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3949 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3951 CREATE TABLE REL_towns (
3953 description varchar(30) NOT NULL default '',
3954 PRIMARY KEY (town_code)
3955 ) TYPE=MyISAM;
3957 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3958 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3959 </pre>
3965 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3969 </ul>
3977 <li>In the columns row, choose persons.person_name and click the
3979 <li>Do the same for towns.description and countries.descriptions in the
3982 the correct joins have been generated</li>
3984 </ul>
3988 <p>
3989 Starting from the previous example, create the pma_table_info as explained
3990 in the configuration section, then browse your persons table,
3991 and move the mouse over a town code or country code.
3992 <br /><br />
3993 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3994 enables: drop-down list of possible values.
3995 </p>
3998 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3999 <p>
4002 <br /><br />
4003 Then you need to think about your schema layout. Which tables will go on
4004 which pages?
4005 </p>
4006 <ul>
4012 page and click Go. If you like, you
4014 linked tables onto the new page.</li>
4015 <li>Select the name of the new page (making sure the Edit radio button
4016 is selected) and click Go.</li>
4018 Coordinates are relative; your diagram will
4019 be automatically scaled to fit the page. When initially placing tables
4020 on the page, just pick any coordinates -- say, 50x50. After clicking
4022 position the element correctly.</li>
4024 first be sure to click the Save
4025 button beneath the list of tables and coordinates, to save any changes
4026 you made there. Then scroll all the way down, select the
4028 you want, and click Go.</li>
4029 <li>Internet Explorer for Windows may suggest an incorrect filename when
4034 browsers on Windows, do not have this problem.</li>
4035 </ul>
4039 columns!</a></h4>
4041 <p> No, it's MySQL that is doing
4047 underscores in the database name?</a></h4>
4049 <p> If you do not put a backslash before the underscore, this is a wildcard
4052 john2db ...<br /><br />
4054 If you put a backslash before the underscore, it means that the database
4055 name will have a real underscore.</p>
4059 statistics pages?</a></h4>
4070 if it already exists during the import. It does NOT drop the table after
4071 your export, it only affects the import file.</li>
4073 Otherwise, you may get an error if the table name exists but has a
4074 different structure.</li>
4076 (if any) will be included in backup.</li>
4078 column and table names formed with special characters are protected.</li>
4080 types set in the pmadb in the dump as
4082 </li>
4083 </ul>
4088 command, for better documentation (but resulting file is bigger).</li>
4090 once the INSERT verb and the table name.</li>
4093 </li>
4095 more info is provided in the
4097 but basically with this selected, invalid values are adjusted and
4098 inserted rather than causing the entire statement to fail.</li>
4099 </ul>
4103 in its name.</a></h4>
4106 is the normal way to reference a database and table name. Worse, MySQL
4107 will usually let you create a database with a dot, but then you cannot
4108 work with it, nor delete it.</p>
4114 <p>
4115 To use SQL Validator, you need PHP with
4121 module.
4122 </p>
4124 <p>
4130 usage.
4131 </p>
4133 <p>
4134 If you use the Validator, you should be aware that any
4136 submit will be stored anonymously (database/table/column names,
4137 strings, numbers replaced with generic values). The Mimer
4140 We utilize it as free SOAP service.
4141 </p>
4145 it, but MySQL says "BLOB column '...' used in key specification without
4148 <p> The right way to do this, is to create the column without any indexes,
4150 dialog. On this page, you will be able to choose your BLOB column, and
4151 set a size to the index, which is the condition to create an index on
4152 a BLOB column.</p>
4156 editing fields?</a></h4>
4158 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4159 with many editing fields (table structure changes, row editing, etc.)
4160 (must be enabled in configuration - see.
4162 You can also have a look at the directive
4164 ('vertical') and see if this eases up editing for you.</p>
4168 WTF is this feature then useful for?</a></h4>
4170 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4171 on them. Otherwise you could just put a comment on the column. Because entering
4172 your own mimetype will cause serious syntax checking issues and validation,
4173 this introduces a high-risk false-user-input situation. Instead you have to
4174 initialize mimetypes using functions or empty mimetype definitions.<br />
4175 Plus, you have a whole overview of available mimetypes. Who knows all those
4176 mimetypes by heart so he/she can enter it at will?</p>
4180 can't I see any bookmarks below the query box? What is this variable for?
4181 </a></h4>
4183 <p> Any query you have executed can be stored as a bookmark on the page where the
4184 results are displayed. You will find a button labeled 'Bookmark this query'
4185 just at the end of the page.<br />
4186 As soon as you have stored a bookmark, it is related to the database you run
4187 the query on. You can now access a bookmark dropdown on each page, the query
4188 box appears on for that database.<br /><br />
4190 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4194 aware of that you HAVE to create a valid query, otherwise your query won't be
4195 even able to be stored in the database.<br />
4197 for your query will remain the way it is, but will be stripped of the /**/
4198 chars. So you can use:<br /><br />
4202 which will be expanded to<br /><br />
4206 in your query, where VARIABLE is the string you entered in the input box. If
4207 an empty string is provided, no replacements are made.<br /><br />
4209 A more complex example. Say you have stored this query:<br /><br />
4211 <br /><br />
4214 the full query will be:<br /><br />
4217 <br /><br />
4221 spaces inserted there
4222 will be later also inserted as spaces in your query and may lead to unexpected
4223 results especially when
4225 Your initial query which is going to be stored as a bookmark has to yield at
4226 least one result row so
4227 you can store the bookmark. You may have that to work around using well
4231 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4232 include exported table?</a></h4>
4234 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4235 document should look like following one (assuming you have table
4238 <pre>
4239 \documentclass{article} % or any class you want
4240 \usepackage{longtable} % for displaying table
4241 \begin{document} % start of document
4242 \include{table} % including exported table
4243 \end{document} % end of document
4244 </pre>
4248 access them.
4249 </a></h4>
4251 <p> You have one of these global privileges: CREATE
4252 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4253 enable users to see all the database names.
4256 So if your users do not need those privileges, you can remove them and their
4257 databases list will shorten.</p>
4261 possible values for a column, based on some foreign table?</a></h4>
4263 <p> You have to setup appropriate links between the tables, and also
4267 foreign table, a drop-down list of values will be available.
4268 You will see two lists of values, the first list containing the key
4269 and the display column, the second list containing the display column
4270 and the key. The reason for this is to be able to type the first
4271 letter of either the key or the display column.<br /><br />
4273 For 100 values or more, a distinct window will appear, to browse foreign
4274 key values and choose one. To change the default limit of 100, see
4275 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4279 automatically when entering Browse mode for a table?</a></h4>
4281 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4282 </p>
4286 Excel files, how can I enable that?</a></h4>
4288 <p> You can use
4290 which works out of the box, but phpMyAdmin supports direct export
4291 to Microsoft Excel version 97 and newer. For this to work, you need to set
4296 <pre>
4297 cd phpMyAdmin
4298 mkdir tmp
4299 chmod o+rwx tmp
4300 </pre>
4304 what happens to my column comments stored in pmadb?</a></h4>
4306 <p> Automatic migration of a table's pmadb-style column comments to the native
4307 ones is done whenever you enter Structure page for this table.</p>
4312 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4313 <ul>
4316 later)</li>
4319 </ul>
4323 <ol>
4324 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4325 <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>
4326 <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>
4327 <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>
4328 </ol>
4333 <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>
4339 <p>
4340 In all places where phpMyAdmin accepts format strings, you can use
4343 expanded variables depend on a context (for example, if you haven't chosen a
4344 table, you can not get the table name), but the following variables can be used:
4345 </p>
4346 <dl>
4352 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4363 </dl>
4370 <p> Our Bug Tracker is located at
4372 under the Bugs section.<br /><br />
4374 But please first discuss your bug with other users:<br />
4376 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4377 </p>
4381 existing language, where do I start?</a></h4>
4383 <p> Always use latest Git version of the po file to translate. You can optionally
4385 server</a> where you can also get the latest po files and merge them
4386 with your translations. For creating a new translation simply use
4390 to do this) or ask on the mailing list to add the translation to the web
4391 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Gettext_for_translators">our wiki</a>.
4392 </p>
4393 <p>
4394 Please note that we try not to use HTML entities like &eacute; in
4395 the translations, since we define the right character set in the file.
4396 With HTML entities, the text on JavaScript messages would not
4397 display correctly.
4398 However there are some entities that need to be there: quotes,
4399 non-breakable spaces, ampersands, less than, greater than.
4400 </p>
4401 <p>
4402 You can then put your translations, as a zip file to avoid losing special
4403 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4404 </p>
4405 <p>
4406 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4407 list, because this is where we ask for translations of new messages.
4408 </p>
4410 <p>
4411 Documentation is being translated using po4a and gettext (see
4413 for existing translations). To start, checkout
4414 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4415 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4416 and translate it online. If your language is missing, just contact
4418 you prefer to directly translate the po files, please put updated ones into our
4419 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4420 </p>
4424 phpMyAdmin. How should I proceed?</a></h4>
4429 <tt>git clone
4430 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4431 </li>
4433 <li>generate patch with your changes:
4435 </li>
4438 tracker of the phpMyAdmin project</a>.
4439 </li>
4440 </ol>
4442 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4444 <p> Write access to the repository is granted only to experienced developers who
4445 have already contributed something useful to phpMyAdmin.<br />
4451 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4453 <p> Please refer to
4454 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4455 </p>
4460 <p> If you use Apache web server, phpMyAdmin exports information about
4461 authentication to the Apache environment and it can be used in Apache logs.
4462 Currently there are two variables available:
4463 </p>
4464 <dl>
4466 <dd>User name of currently active user (he does not have to be logged
4467 in).</dd>
4474 </dl>
4475 <p>
4477 </p>
4478 <pre>
4481 </pre>
4482 <p>
4483 You can then use any log analyzing tools to detect possible break-in
4484 attempts.
4485 </p>
4491 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4492 It allows you to connect to local as well as remote servers. This requires you to enter
4493 server host name, username, password, port and the name of the database. Therefore you can
4494 now synchronize your databases placed on the same server or some remote server.
4495 </p>
4497 <p>
4498 This feature is helpful for developers who need to replicate their
4499 database’s structure as well as data. Moreover, this feature not only
4500 helps replication but also facilitates the user to keep his/her database
4501 in sync with another database. Other than the full database, certain
4502 tables of the databases can also be synchronized.
4503 </p>
4505 <p>
4506 You need to fill in the host name of the server, the username and
4507 password of an user account already there in MySQL. Port is by default
4508 populated with 3306 (MySQL default port). Then the name of the database
4509 should be mentioned at the end. All the information other than the port
4510 needs to be filled explicitly for the source as well as target servers.
4511 </p>
4513 <p>
4514 After successfully passing through the authentication phase, the source and
4515 target database table names will be displayed. It will be a tabular
4516 representation.
4517 </p>
4519 <p>
4520 On the left, are listed the source database table names. Some of the
4522 are only present in source database and they need to be added to the
4523 target database in order to synchronize the target database. The tables
4525 target database.
4526 </p>
4528 <p>
4529 On the right, are listed the target database table names. There are few
4531 means that these tables are to be created in target database in order to
4532 synchronize target database with source database. Some table names
4534 only present in target database and they will remain unchanged in the
4535 target database. The column in the middle shows the difference between
4536 the source and target corresponding tables.
4537 </p>
4539 <p>
4541 letters, indicating that either Structure or Data are not up to date. By
4542 clicking on them, they will turn grey, what means that they will be synchronized.
4543 </p>
4545 <!-- DEVELOPERS -->
4548 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4549 great features have been written by other people and you too can help to
4550 make phpMyAdmin a useful tool.</p>
4552 <p> If you're planning to contribute source, please read the following
4553 information:</p>
4559 it free from other code.<br />
4560 Commonly used functions should be added to
4563 <li>Obviously, you're free to use whatever coding style you want. But
4564 please try to keep your code as simple as possible: beginners are
4565 using phpMyAdmin as an example application.<br />
4566 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4567 compliant on one hand, they fit the
4570 coding standards</a>
4571 on the other hand. Please pay attention to this.</li>
4572 <li>Please enable showing PHP errors and warnings by the
4574 configuration directive.</li>
4575 <li>Please try to keep up the file-naming conventions. Table-related stuff
4578 <li>Please use gettext wrappers around all messages
4581 script. To use translated messages, call
4583 Gettext.</li>
4587 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4588 better debug and profile their code.<br />
4589 Please see the
4591 options for more information.<br />
4592 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4593 lost during its re-entry into Earth's atmosphere and in memory of the
4594 brave men and women who gave their lives for the people of Earth.</li>
4595 </ul>
4599 <pre>
4610 </pre>
4612 <p>
4613 This program is free software; you can redistribute it and/or modify
4614 it under the terms of the GNU General Public License version 2,
4615 as published by the Free Software Foundation.
4616 </p>
4618 <p>
4619 This program is distributed in the hope that it will be useful,
4620 but WITHOUT ANY WARRANTY; without even the implied warranty of
4621 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4622 GNU General Public License for more details.
4623 </p>
4625 <p>
4626 You should have received a copy of the GNU General Public License
4627 along with this program; if not, write to the Free Software
4629 </p>
4631 <!-- CREDITS -->
4636 <ul>
4639 <ul>
4642 </ul></li>
4645 <ul>
4650 </ul></li>
4653 <ul>
4659 </ul></li>
4662 <ul>
4664 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4665 generate XHTML1.0 and CSS2 compliant codes</li>
4668 </ul></li>
4671 <ul>
4679 </ul></li>
4682 <ul>
4687 </ul></li>
4690 <ul>
4693 </ul></li>
4696 <ul>
4698 </ul></li>
4701 <ul>
4704 </ul></li>
4707 <ul>
4711 </ul></li>
4714 <ul>
4717 </ul></li>
4720 <ul>
4727 </ul></li>
4730 <ul>
4734 </ul></li>
4737 <ul>
4743 </ul></li>
4746 (http://sf.net/projects/phpmysqlformgen/)
4747 <ul>
4749 </ul></li>
4752 <ul>
4754 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4759 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4763 </ul></li>
4766 <ul>
4768 </ul></li>
4771 <ul>
4773 </ul></li>
4776 <ul>
4778 </ul></li>
4781 <ul>
4782 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4783 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4784 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4785 </ul></li>
4788 <ul>
4790 </ul></li>
4793 <ul>
4795 </ul></li>
4798 <ul>
4800 </ul></li>
4803 <ul>
4806 </ul></li>
4809 <ul>
4812 </ul></li>
4815 <ul>
4817 </ul></li>
4820 <ul>
4823 </ul></li>
4825 <li>Ivan A Kirillov
4826 <ul>
4828 </ul></li>
4831 <ul>
4833 </ul></li>
4836 <ul>
4839 </ul></li>
4842 <ul>
4844 </ul></li>
4847 <ul>
4849 </ul></li>
4852 <ul>
4854 </ul></li>
4857 <ul>
4859 </ul></li>
4861 <li>Barrie Leslie
4862 <ul>
4864 </ul></li>
4866 </ul>
4868 <p>
4869 And also to the following people who have contributed minor changes,
4870 enhancements, bugfixes or support for a new language since version 2.1.0:
4871 </p>
4873 <p>
4874 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4875 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4876 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4877 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4879 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4880 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4881 Luís V., Martijn W. van der Lee,
4882 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4884 </p>
4889 <p>
4890 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4891 to create a web-based interface to MySQL using PHP3. Although I have not
4892 used any of his source-code, there are some concepts I've borrowed from
4893 him. phpMyAdmin was created because Peter told me he wasn't going to
4894 further develop his (great) tool.
4895 </p>
4896 <p>
4897 Thanks go to
4898 </p>
4899 <ul>
4901 code for the check when dropping a table or database. He also suggested
4902 that you should be able to specify the primary key on tbl_create.php3. To
4903 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4904 well as a bug-report. Plus many smaller improvements.
4905 </li>
4907 were introduced in 1.3.0 (including quite significant ones like the
4908 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4909 bug-fixes and help.
4910 </li>
4912 language-independent by outsourcing the strings to a separate file. He
4913 also contributed the French translation.
4914 </li>
4916 tbl_select.php3, a feature to display only some columns from a table.
4917 </li>
4919 functions in tbl_change.php3. He also added the
4921 </li>
4923 servers and is a regular contributor for bug-fixes.
4924 </li>
4926 features for 2.0.6.
4927 </li>
4928 </ul>
4929 <p>
4930 The following people have contributed minor changes, enhancements, bugfixes
4931 or support for a new language:
4932 </p>
4933 <p>
4934 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4935 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4936 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4937 G. Wieggers.
4938 </p>
4939 <p>
4940 And thanks to everyone else who sent me email with suggestions, bug-reports
4941 and or just some feedback.
4942 </p>
4948 <ul>
4950 - the default name of Apache's directory-level configuration file.</li>
4954 - a software application that enables a user to display and interact with
4955 text, images, and other information typically located on a web page at a
4956 website on the World Wide Web.</li>
4958 - a free software/open source data compression algorithm and program
4959 developed by Julian Seward.</li>
4961 - an important World Wide Web technology that enables a client web browser
4962 to request data from a program executed on the Web server.</li>
4964 - a log or record of changes made to a project.</li>
4966 - a computer system that accesses a (remote) service on another computer
4967 by some kind of network.</li>
4969 - a set of data values of a particular simple type, one for each row of
4970 the table.</li>
4972 - a packet of information sent by a server to a World Wide Web browser
4973 and then sent back by the browser each time it accesses that server.</li>
4975 - Comma-separated values</li>
4978 - an organized collection of data.</li>
4981 - a PHP module that extends PHP with additional functionality.</li>
4983 - a list of commonly asked question and there answers.</li>
4985 - one part of divided data/columns.</li>
4987 - a field or group of fields in a database record that point to a key
4988 field or group of fields forming a key of another database record in some
4989 (usually different) table.</li>
4991 - the free PDF library</li>
4993 GD Graphics Library</a> - a library by Thomas Boutell and others for
4994 dynamically manipulating images.</li>
4997 - gzip is short for GNU zip, a GNU free software file compression
4998 program.</li>
5000 - any machine connected to a computer network, a node that has a hostname.</li>
5002 - the unique name by which a network attached device is known on a network.</li>
5004 (HyperText Transfer Protocol)</a>
5005 - the primary method used to transfer or convey information on the World
5006 Wide Web.</li>
5009 additional security measures.</li>
5010 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5011 - a set of Internet-based services for servers using Microsoft Windows.</li>
5013 - a feature that allows quick access to the rows in a table.</li>
5015 - a data-oriented protocol used by source and destination hosts for
5016 communicating data across a packet-switched internetwork.</li>
5018 - a unique number that devices use in order to identify and communicate
5019 with each other on a network utilizing the Internet Protocol standard.</li>
5021 (Internet Server Application Programming Interface)</a>
5022 - the API of Internet Information Services (IIS).</li>
5024 - a business or organization that offers users access to the Internet and related services.</li>
5026 - a most commonly used standard method of lossy compression for
5027 photographic images.</li>
5033 - line of personal computers is designed, developed, manufactured, and
5034 marketed by Apple Computer.</li>
5035 <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>
5036 - the operating system which is included with all currently shipping Apple
5037 Macintosh computers in the consumer and professional markets.</li>
5039 - a cryptographic library.</li>
5041 - the MCrypt PHP extension.</li>
5042 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5043 - an Internet Standard for the format of e-mail.</li>
5045 - some sort of extension for the Apache Webserver.</li>
5047 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5048 Management System (DBMS).</li>
5050 - the improved MySQL client PHP extension.</li>
5052 - the MySQL client PHP extension.</li>
5054 - open standard for office documents.</li>
5055 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5056 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5058 (Portable Document Format)</a>
5059 - a file format developed by Adobe Systems for representing two
5060 dimensional documents in a device independent and resolution independent
5061 format.</li>
5063 - the PHP Extension and Application Repository.</li>
5065 - the perl-compatible regular expression functions for PHP</li>
5067 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5068 programming language used mainly for developing server-side applications
5069 and dynamic web content, and more recently, a broader range of software
5070 applications.</li>
5072 - a connection through which data is sent and received.</li>
5074 - Request for Comments (RFC) documents are a series of memoranda
5075 encompassing new research, innovations, and methodologies applicable to
5076 Internet technologies.</li>
5080 - represents a single, implicitly structured data item in a table.</li>
5082 - a computer system that provides services to other computing
5083 systems over a network.</li>
5084 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
5085 - handlers for different table types</li>
5087 - a form of inter-process communication.</li>
5089 Sockets Layer)</a>
5090 - a cryptographic protocol which provides secure communication on the Internet.</li>
5092 - Structured Query Language</li>
5094 - a set of data elements (cells) that is organized, defined and stored as
5095 horizontal rows and vertical columns where each item can be uniquely
5096 identified by a label or key or by it?s position in relation to other items.</li>
5099 - a type of archive file format: the Tape ARchive format.</li>
5101 - one of the core protocols of the Internet protocol suite.</li>
5105 - a sequence of characters, conforming to a standardized format, that is
5106 used for referring to resources, such as documents and images on the
5107 Internet, by their location.</li>
5109 - A computer (program) that is responsible for accepting HTTP requests
5110 from clients and serving them Web pages.</li>
5112 - a W3C-recommended general-purpose markup language for creating
5113 special-purpose markup languages, capable of describing many different
5114 kinds of data.</li>
5116 - a popular data compression and archival format.</li>
5118 - an open-source, cross-platform data compression library by Jean-loup
5119 Gailly and Mark Adler.</li>
5120 </ul>
5121 </div>
5124 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5127 <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>
5128 </ul>
5130 </body>
5131 </html>