| blob | 59788c103e579a3ed523280a1b7fb0870d2745a2 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <head>
14 </head>
18 <h1>
20 3.5.0-dev
21 Documentation
22 </h1>
23 </div>
25 <!-- TOP MENU -->
34 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
39 </ul>
44 phpMyAdmin homepage</a></li>
46 SourceForge phpMyAdmin project page</a></li>
48 Official phpMyAdmin wiki</a></li>
49 <li>Local documents:
52 </ul>
53 </li>
54 </ul>
56 <!-- REQUIREMENTS -->
63 , the Standard PHP Library (SPL) extension and JSON support.
64 </li>
67 currently the default), you should install the mbstring and ctype
68 extensions.
69 </li>
70 <li>You need GD2 support in PHP to display inline
72 original aspect ratio</li>
78 load pages significantly slower.
79 </li>
82 <li>To support BLOB streaming, see PHP and MySQL requirements
85 <li>To support XML and Open Document Spreadsheet importing,
86 you need PHP 5.2.17 or newer and the
88 </ul>
89 </li>
92 </ul>
94 <!-- INTRODUCTION -->
97 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
98 a single database. To accomplish the latter you'll need a properly set up
99 MySQL user who can read/write only the desired database. It's up to you to
100 look up the appropriate part in the MySQL manual.
101 </p>
106 <li>create, copy, drop, rename and alter databases, tables, columns and
107 indexes</li>
108 <li>maintenance server, databases and tables, with proposals on server
109 configuration</li>
110 <li>execute, edit and bookmark any
112 batch-queries</li>
115 </li>
122 OpenDocument Text and Spreadsheet,
125 </li>
126 <li>import data and MySQL structures from 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>
130 <li>using Query-by-example (QBE), create complex queries automatically
131 connecting required tables</li>
133 your Database layout</li>
135 <li>transform stored data into any format using a set of predefined
136 functions, like displaying BLOB-data as image or download-link
137 </li>
145 <li>communicate in <a href="http://www.phpmyadmin.net/home_page/translations.php">62 different languages</a>
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>
637 domain to call phpMyAdmin inside a frame, and is a potential security
638 hole allowing cross-frame scripting attacks.</dd>
642 algorithm to encrypt the password.<br />
644 passphrase of your choice. It will be used internally by the blowfish
645 algorithm: you won’t be prompted for this passphrase. There is
646 no maximum length for this secret.<br /><br />
648 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
649 makes a bit weaker security as this generated secret is stored in
650 session and furthermore it makes impossible to recall user name from
651 cookie.</dd>
655 MySQL servers. Therefore, a
657 been added which contains the login information for the different servers.
658 The first
660 contains the hostname of the first server, the second
662 the hostname of the second server, etc. In
664 server definition, however you can put as many as you need in
666 have to define all settings, just those you need to change).</dd>
670 $i-th MySQL-server. E.g. localhost.</dd>
675 ignores this port number and connects with the socket, so if you want
676 to connect to a port different from the default port, use
679 </dd>
683 To determine the correct socket, check your MySQL configuration or, using the
685 Among the resulting information displayed will be the socket used.</dd>
688 <dd>Whether to enable SSL for connection to MySQL server.
689 </dd>
692 <dd>What type connection to use with the MySQL server. Your options are
694 is nearly guaranteed to be available on all MySQL servers, while
695 sockets are not supported on some platforms.<br /><br />
697 To use the socket mode, your MySQL server must be on the same machine
698 as the Web server.</dd>
701 <dd>What php MySQL extension to use for the connection. Valid options are:
702 <br /><br />
705 The classic MySQL extension.<br /><br />
708 The improved MySQL extension. This extension became available
709 with PHP 5.0.0 and is the recommended way to connect to a server
713 <dd>Whether to use a compressed protocol for the MySQL server connection
714 or not (experimental).</dd>
718 </dt>
719 <dd>Permits to use an alternate host to hold the configuration storage
720 data.</dd>
725 </dt>
727 all relational features (see
729 and, for a MySQL server running with
732 authentication mode).<br /><br />
735 cookie authentication modes (or 'config'
736 authentication mode since phpMyAdmin 2.2.1), you need to supply the
741 This account is used to check what databases the user will see at
742 login.<br />
746 In phpMyAdmin versions before 2.2.5, those were called
750 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
751 <dd>Whether config or cookie or
753 should be used for this server.
755 is the plain old way: username and password are stored in
757 <li>'cookie' authentication mode
759 2.2.3 allows you to log in as any valid MySQL user with the
760 help of cookies. Username and password are stored in
761 cookies during the session and password is deleted when it
762 ends. This can also allow you to log in in arbitrary server if
763 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
764 </li>
765 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
766 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
767 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
768 <li>'signon' authentication mode
770 as introduced in 2.10.0 allows you to log in from prepared PHP
771 session data or using supplied PHP script. This is useful for implementing single signon
772 from another application.
778 You need to
784 </ul>
787 for more information.
788 </dd>
790 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
791 </dt>
792 <dd>
793 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
794 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
795 specified in your configuration, a string combined of "phpMyAdmin " and either
798 </dd>
800 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
801 </dt>
802 <dd>
804 names for hardware authentication. Leave empty to deactivate this feature.
805 </dd>
809 </dt>
810 <dd>
811 When using auth_type = 'config', this is the user/password-pair
812 which phpMyAdmin will use to connect to the
813 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
814 cookie authentication is used and should be empty.</dd>
816 <span
818 </dt>
819 <dd>
820 Allow attempt to log in without password when a login with password
821 fails. This can be used together with http authentication, when
822 authentication is done some other way and phpMyAdmin gets user name
823 from auth and uses empty password for connecting to MySQL. Password
824 login is still tried first, but as fallback, no password method is
825 tried.</dd>
828 </dt>
829 <dd>
830 If set to a (an array of) database name(s), only this (these) database(s)
831 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
832 database(s) name(s) may contain MySQL wildcards characters
836 This setting is an efficient way to lower the server load since the
837 latter does not need to send MySQL requests to build the available
839 privileges rules of the MySQL database server</span>. If set, it just
840 means only these databases will be displayed but
842 <br /><br />
844 An example of using more that one database:
846 <br /><br />
848 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
849 databases in the left frame, so that you can individually arrange your databases.<br />
850 If you want to have certain databases at the top, but don't care about the others, you do not
851 need to specify all other databases. Use:
853 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
854 order.</dd>
857 </dt>
858 <dd>Regular expression for hiding some databases from unprivileged users.
859 This only hides them
860 from listing, but a user is still able to access them (using, for example,
861 the SQL query area). To limit access, use the MySQL privilege system.
862 <br /><br />
867 More information on regular expressions can be found in the
869 PCRE pattern syntax</a> portion of the PHP reference manual.
870 </dd>
873 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
874 this string will be displayed instead of the hostname in the pull-down
875 menu on the main page. This can be useful if you want to show only
876 certain databases on your system, for example. For HTTP auth, all
877 non-US-ASCII characters will be stripped.</dd>
881 </dt>
882 <dd>The name of the database containing the phpMyAdmin configuration storage.
883 <br /><br />
886 section in this document to see the benefits of this feature,
887 and for a quick way of creating this database and the needed tables.
888 <br /><br />
890 If you are the only user of this phpMyAdmin installation, you can
891 use your current database to store those special tables; in this
892 case, just put your current database name in
894 set this parameter to the name of your central database containing
895 the phpMyAdmin configuration storage.</dd>
899 </dt>
901 useful for queries you often run.<br /><br />
903 To allow the usage of this functionality:
905 <li>enter the table name in
907 </ul>
908 </dd>
912 </dt>
914 which column is a key in another table (a foreign key). phpMyAdmin
915 currently uses this to
916 <ul><li>make clickable, when you browse the master table, the data values
917 that point to the foreign table;</li>
919 when browsing the master table, if you move the mouse to a column
920 containing a foreign key (use also the 'table_info' table);<br />
923 <li>in edit/insert mode, display a drop-down list of possible foreign
927 <li>display links on the table properties page, to check referential
928 integrity (display missing foreign keys) for each described key;
929 </li>
933 schema of your database (also uses the table_coords table).</li>
934 </ul>
936 The keys can be numeric or character.<br /><br />
938 To allow the usage of this functionality:
941 configuration storage</li>
942 <li>put the relation table name in
944 <li>now as normal user open phpMyAdmin and for each one of your
945 tables where you want to use this feature, click
947 columns.
948 </li>
949 </ul>
953 future development of the cross-db relations.
954 </dd>
958 </dt>
959 <dd>
960 Since release 2.3.0 you can describe, in a special 'table_info'
961 table, which column is to be displayed as a tool-tip when moving the
962 cursor over the corresponding key.<br />
963 This configuration variable will hold the name of this special
964 table. To allow the usage of this functionality:
966 <li>put the table name in
968 'pma_table_info')</li>
969 <li>then for each table where you want to use this feature,
971 to choose the column.</li>
972 </ul>
974 </dd>
978 </dt>
981 the relations between your tables. To do this it needs two tables
986 schema output).<br /><br />
990 To allow the usage of this functionality:
993 <li>put the correct table names in
996 </ul>
999 </dd>
1003 </dt>
1005 Since release 2.3.0 you can store comments to describe each column for
1007 <br /><br />
1009 Starting with release 2.5.0, comments are consequently used on the table
1010 property pages and table browse view, showing up as tool-tips above the
1011 column name (properties page) or embedded within the header of table in
1012 browse view. They can also be shown in a table dump. Please see the
1013 relevant configuration directives later on.<br /><br />
1015 Also new in release 2.5.0 is a MIME-transformation system which is also
1017 Transformations</a> for further information. To use the
1018 MIME-transformation system, your column_info table has to have the three
1019 new columns 'mimetype', 'transformation', 'transformation_options'.
1020 <br /><br />
1022 To allow the usage of this functionality:
1024 <li>put the table name in
1026 'pma_column_info')</li>
1029 <pre>
1030 ALTER TABLE `pma_column_comments`
1031 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1032 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1033 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1034 </pre>
1037 renamed from<br />
1040 </ul>
1041 </dd>
1045 </dt>
1048 all queries you entered manually into the phpMyAdmin interface. If you
1049 don't want to use a table-based history, you can use the JavaScript-based
1050 history. Using that, all your history items are deleted when closing the
1051 window.<br /><br />
1053 Using
1055 you can specify an amount of history items you want to have on hold. On
1056 every login, this list gets cut to the maximum amount.<br /><br />
1058 The query history is only available if JavaScript is enabled in your
1059 browser.<br /><br />
1061 To allow the usage of this functionality:
1065 (e.g. 'pma_history')
1066 </li>
1067 </ul>
1068 </dd>
1072 </dt>
1073 <dd>
1074 Since release 3.5.0 you can show recently used tables in the left navigation frame.
1075 It helps you to jump across table directly, without the need to select the database,
1076 and then select the table. Using
1078 you can configure the maximum number of recent tables shown. When you select a table
1079 from the list, it will jump to the page specified in
1080 <a href="#cfg_LeftDefaultTabTable" class="configrule">$cfg['LeftDefaultTabTable']</a>.<br/><br/>
1082 Without configuring the storage, you can still access the recently used tables,
1083 but it will disappear after you logout.<br/><br/>
1085 To allow the usage of this functionality persistently:
1087 <ul>
1090 </ul>
1091 </dd>
1095 </dt>
1096 <dd>
1097 Since release 3.5.0 phpMyAdmin can be configured to remember several things
1098 (sorted column
1100 , column order, and column visibility from a database table) for browsing tables.
1101 Without configuring the storage, these features still can be used,
1102 but the values will disappear after you logout.<br/><br/>
1104 To allow the usage of these functionality persistently:
1106 <ul>
1108 <li>put the table name in <tt>$cfg['Servers'][$i]['table_uiprefs']</tt> (e.g. 'pma_table_uiprefs')</li>
1109 </ul>
1110 </dd>
1114 </dt>
1115 <dd>
1116 Since release 3.3.x a tracking mechanism is available.
1118 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1119 and data definition statements. After enabling it you can create versions of tables.
1120 <br/><br/>
1121 The creation of a version has two effects:
1123 <ul>
1125 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1126 </ul>
1128 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1129 For the report you can use filters, for example you can get a list of statements within a date range.
1130 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1131 In addition you can export the (filtered) report to a file or to a temporary database.
1132 <br/><br/>
1134 To allow the usage of this functionality:
1136 <ul>
1139 </ul>
1140 </dd>
1143 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1144 </dt>
1145 <dd>
1146 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1147 <br/><br/>
1148 If this is set to true and you create a table or view with
1150 <ul>
1153 </ul>
1155 and no version exists for it, the mechanism will
1156 create a version for you automatically.
1157 </dd>
1160 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1161 </dt>
1162 <dd>
1163 Defines the list of statements the auto-creation uses for new versions. Default value is
1164 <br/>
1166 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1167 CREATE INDEX,DROP INDEX,
1168 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1169 CREATE VIEW,ALTER VIEW,DROP VIEW,
1170 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1171 </dd>
1174 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1175 </dt>
1176 <dd>
1177 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1178 <br/><br/>
1179 </dd>
1183 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1184 </dt>
1185 <dd>
1186 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1187 <br/><br/>
1188 </dd>
1191 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1192 </dt>
1193 <dd>
1194 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1195 <br/><br/>
1196 </dd>
1200 </dt>
1201 <dd>
1202 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1203 and store them in the database.
1204 <br /><br />
1207 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1208 or, it is is unavailable, until the end of session.
1209 <br /><br />
1211 To allow the usage of this functionality:
1213 <ul>
1215 configuration storage</li>
1217 </ul>
1218 </dd>
1222 </dt>
1224 to visually manage the relations.
1225 <br /><br />
1227 To allow the usage of this functionality:
1230 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1231 </li>
1232 </ul>
1233 </dd>
1235 <dt><span id="cfg_Servers_MaxTableUiprefs">$cfg['Servers'][$i]['MaxTableUiprefs']</span> integer
1236 </dt>
1240 When tables are dropped or renamed, table_uiprefs may contain invalid
1241 data (referring to tables which no longer exist).<br />
1242 We only keep this number of newest rows in table_uiprefs and automatically delete older rows.</dd>
1245 </dt>
1247 column_info table got enhanced with three new columns. If the above variable
1249 latest table structure available. If not, it will emit a warning to the
1250 superuser.<br /><br />
1252 You can disable this checking behavior by setting the variable to false,
1253 which should offer a performance increase.<br /><br />
1255 Recommended to set to FALSE, when you are sure, your table structure is
1256 up to date.</dd>
1258 boolean</dt>
1259 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1260 </dd>
1262 boolean</dt>
1263 <dd>Whether to allow logins without a password. The default
1265 to a MySQL server with was left with an empty password for root or
1266 on which an anonymous (blank) user is defined.
1267 </dd>
1270 </dt>
1272 authorization is disabled.<br /><br />
1275 all deny rules followed by allow rules. Access is allowed by default. Any
1276 client which does not match a Deny command or does match an Allow command
1277 will be allowed access to the server. <br /><br />
1280 applies all allow rules followed by deny rules. Access is denied by
1281 default. Any client which does not match an Allow directive or does
1282 match a Deny directive will be denied access to the server.<br /><br />
1284 If your rule order is set to 'explicit', authorization is
1285 performed in a similar fashion to rule order 'deny,allow', with the
1289 and was available in Apache by specifying allow and deny rules without
1290 setting any order.<br /><br />
1292 Please also see <a
1294 address behind proxies.
1295 </dd>
1297 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1298 </dt>
1299 <dd>The general format for the rules is as such:
1301 <pre>
1303 </pre>
1308 well (please note that those containing SERVER_ADDRESS might not be
1309 available on all webservers):
1310 <pre>
1316 </pre>
1318 Having an empty rule list is equivalent to either using
1324 following work:<br />
1326 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1327 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1328 But the following does not work:<br />
1331 Also IPv6 addresses are not supported.
1332 </dd>
1334 <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.
1335 </dd>
1336 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1338 DATABASES</tt> command used to fetch the name of available databases will
1339 probably be too slow, so it can be replaced by faster commands (see
1341 </dd>
1343 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1344 </dd>
1346 <dd>Name of PHP script to be sourced and executed to obtain
1347 login credentials. This is alternative approach to session based single
1348 signon. The script needs to provide function
1350 password, accepting single parameter of existing username (can be empty).
1352 </dd>
1353 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1354 <dd>Name of session which will be used for signon authentication method.
1356 this is session which phpMyAdmin uses internally. Takes effect only if
1358 is not configured.
1359 </dd>
1361 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1362 </dd>
1364 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1365 </dd>
1368 <dd>If you have more than one server configured, you can set
1370 that server when phpMyAdmin is started, or set it to 0 to be given a
1371 list of servers without logging in.<br />
1373 MUST be set to that server.</dd>
1376 <dd>Defines whether to refresh only parts of certain pages using Ajax
1377 techniques. Applies only where a non-Ajax behavior is possible;
1378 for example, the Designer feature is Ajax-only so this directive
1379 does not apply to it.</dd>
1382 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1383 page.</dd>
1386 <dd>The maximum number of database names to be displayed in the
1387 navigation frame and the database list.</dd>
1390 <dd>The maximum number of table names to be displayed in the
1391 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1392 when in Light mode.</dd>
1398 <dd>The maximum number of characters when a SQL query is displayed. The
1399 default limit of 1000 should be correct to avoid the display of tons
1400 of hexadecimal codes that represent BLOBs, but some users have real
1401 SQL queries that are longer than 1000 characters. Also, if a query's
1402 length exceeds this limit, this query is not saved in the history.</dd>
1405 <dd>Defines whether to use GZip output buffering for increased
1407 Set to true/false for enabling/disabling. When set to 'auto' (string),
1408 phpMyAdmin tries to enable output buffering and will automatically disable
1409 it if your browser has some problems with buffering. IE6 with a certain patch
1410 is known to cause data corruption when having enabled buffering.</dd>
1413 <dd>Whether <a href="http://php.net/manual/en/features.persistent-connections.php">persistent connections</a>
1414 should be used or not. Works with following extensions:
1415 <ul>
1416 <li>mysql (<a href="http://php.net/manual/en/function.mysql-pconnect.php">mysql_pconnect</a>),</li>
1417 <li>mysqli (requires PHP 5.3.0 or newer, <a href="http://php.net/manual/en/mysqli.persistconns.php">more information</a>).</li>
1418 </ul></dd>
1424 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1425 to zero, no time limit is imposed.<br />
1426 This setting is used while importing/exporting dump files and in the
1427 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1434 <dd>Set the number of bytes a script is allowed to allocate. If set
1435 to zero, no limit is imposed.<br />
1436 This setting is used while importing/exporting dump files and at some
1437 other places in phpMyAdmin so you definitely don't want to put here
1438 a too low value. It has no effect when PHP is running in safe mode.<br />
1439 You can also use any string as in php.ini, eg. '16M'. Ensure
1443 <dd>Mark used tables and make it possible to show databases with locked
1448 generated by phpMyAdmin should be displayed or not.</dd>
1451 <dd>Defines whether normal users (non-administrator) are allowed to
1452 delete their own database or not. If set as FALSE, the link "Drop
1454 mydatabase" will be rejected. Quite practical for
1456 customers.<br />
1457 Please note that this limitation of SQL queries is not as strict as
1458 when using MySQL privileges. This is due to nature of SQL queries
1459 which might be quite complicated. So this choice should be viewed as
1460 help to avoid accidental dropping rather than strict privilege
1461 limitation.</dd>
1465 displayed when you're about to lose data.</dd>
1468 <dd>Define whether the previous login should be recalled or not in cookie
1469 authentication mode.<br /><br />
1471 This is automatically disabled if you do not have configured
1473 </dd>
1476 <dd>Define how long is login cookie valid. Please note that php
1477 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1478 might limit session validity and if session is lost, login cookie is
1480 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1484 means that it will be kept for existing session. This is recommended
1485 for not trusted environments.</dd>
1488 <dd>If enabled (default), logout deletes cookies for all servers,
1489 otherwise only for current one. Setting this to false makes it easy to
1490 forget to log out from other server, when you are using more of
1491 them.</dd>
1497 <dd>Define whether phpMyAdmin will continue executing a multi-query
1498 statement if one of the queries fails. Default is to abort execution.</dd>
1501 <dd>Define whether phpMyAdmin will output the results of each query of a
1502 multi-query statement embedded into the
1507 <dd>If enabled, allows you to log in to arbitrary servers using cookie auth and permits to specify servers of your choice in the Synchronize dialog.
1508 <br /><br />
1511 MySQL servers behind the firewall where your
1513 </dd>
1522 <dd>Defines whether to use a select-based menu and display only the current
1523 tables in the left frame (smaller page). Only in Non-Lightmode you can
1524 use the feature to display nested folders using
1526 </dd>
1529 <dd>Defines whether to display the names of databases (in the
1530 selector) using a tree, see also
1532 </dd>
1535 string or array</dt>
1536 <dd>The string used to separate the parts of the database name when showing
1537 them in a tree. Alternatively you can specify more strings in an array
1538 and all of them will be used as a separator.</dd>
1541 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1542 This means if you have tables like 'first__second__third' this will be
1544 If set to FALSE or empty, the feature is disabled. NOTE: You should
1545 not use this separator at the beginning or end of a
1546 table name or multiple times after another without any other
1547 characters in between.</dd>
1550 <dd>Defines how many sublevels should be displayed when splitting
1551 up tables by the above separator.</dd>
1554 <dd>The maximum number of recently used tables shown in the left navigation
1558 <dd>Defines whether to display table comment as tool-tip in left frame or
1559 not.</dd>
1562 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1563 comment and the real name. That means that if you have a table called
1564 'user0001' and add the comment 'MyName' on it, you will see the name
1565 'MyName' used consequently in the left frame and the tool-tip shows
1566 the real name of the DB.</dd>
1569 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1571 When setting this to 'nested', the Alias of the Tablename is only used
1572 to split/nest the tables according to the
1574 directive. So only the folder is called like the Alias, the tablename itself
1575 stays the real tablename.</dd>
1578 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1581 <dd>Enter URL where logo in the navigation frame will point to.
1582 For use especially with self made theme which changes this.
1591 integer</dt>
1592 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1593 list of tables in the left frame.
1598 <dd>Defines whether or not to display a server choice at the top of the left frame.
1599 Defaults to FALSE.</dd>
1601 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1602 Defaults to FALSE (drop-down).</dd>
1604 <dd>Defines whether to display database choice in light navigation frame as links
1605 instead of in a drop-down. Defaults to 'auto' - on main page list is
1606 shown, when database is selected, only drop down is displayed.</dd>
1609 <dd>Defines the tab displayed by default when clicking the small
1610 icon next to each table name in the navigation panel. Possible
1616 <dd>Defines whether or not to display space usage and statistics about databases
1617 and tables.<br />
1618 Note that statistics requires at least MySQL 3.23.3 and that, at this
1619 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1622 <dd>Defines whether to display detailed server information on main page.
1623 You can additionally hide more information by using
1625 </dd>
1630 </dt>
1633 not at the starting main (right) frame. This setting
1634 does not check MySQL commands entered directly.<br /><br />
1636 Please note that to block the usage of phpinfo() in scripts, you
1643 hard coded password value in the configuration file, end users can't
1644 be allowed to change their passwords.</dd>
1647 <dd>Defines whether to suggest a database name on the
1651 <dd>Defines whether navigation bar buttons and the right panel top menu
1652 contain text or symbols only. A value of TRUE displays icons, FALSE
1653 displays text and 'both' displays both icons and text.</dd>
1656 <dd>Defines whether a user should be displayed a
1660 <dd>Number of rows displayed when browsing a result set. If the result set
1667 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1671 option is ticked by default.</dd>
1675 from editing when browsing a table's content. Valid values are:
1680 </ul>
1681 </dd>
1684 <dd>Defines whether or not MySQL functions fields should be initially
1685 displayed in edit/insert mode. Since version 2.10, the user can
1686 toggle this setting from the interface.
1687 </dd>
1690 <dd>Defines whether or not type fields should be initially
1691 displayed in edit/insert mode. The user can
1692 toggle this setting from the interface.
1693 </dd>
1696 <dd>Defines which type of editing controls should be used for CHAR and
1697 VARCHAR columns. Possible values are:
1698 <ul><li>input - this allows to limit size of text to size of columns in
1699 MySQL, but has problems with newlines in columns</li>
1700 <li>textarea - no problems with newlines in columns, but also no
1701 length limitations</li>
1702 </ul>
1703 Default is old behavior so input.</dd>
1706 <dd>Defines the minimum size for input fields generated for CHAR and
1707 VARCHAR columns.</dd>
1710 <dd>Defines the maximum size for input fields generated for CHAR and
1711 VARCHAR columns.</dd>
1717 <dd>If there are fewer items than this in the set of foreign keys, then a
1718 drop-down box of foreign keys is presented, in the style described by the
1720 setting.</dd>
1723 <dd>For the foreign key drop-down fields, there are several methods of
1724 display, offering both the key and value data. The contents of the
1725 array should be one or both of the following strings:
1731 </dt>
1732 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1733 creating a dump file</dd>
1736 </dt>
1737 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1738 compressed exports. This doesn't affect smaller dumps and allows users to
1739 create larger dumps that won't otherwise fit in memory due to php
1740 memory limit. Produced files contain more GZip/BZip2 headers, but all
1741 normal programs handle this correctly.</dd>
1745 mainframe.</dd>
1749 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1754 <dd>How many columns will be utilized to display the tables on the
1755 database property view? Default is 1 column. When setting this to a
1756 value larger than 1, the type of the database will be omitted for more
1757 display space.</dd>
1761 <dd>Defines the tab displayed by default on server view. Possible
1768 <dd>Defines the tab displayed by default on database view. Possible
1773 <dd>Defines the tab displayed by default on table view. Possible
1780 points to the MySQL documentation (type depends
1781 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1782 generated.<br />
1784 for more information about MySQL manuals and their types.</dd>
1787 <dd>Type of MySQL documentation:
1793 </ul>
1794 </dd>
1797 <dd>Defines the default language to use, if not browser-defined or
1798 user-defined.<br />
1799 The corresponding language file needs to be in
1801 </dd>
1804 <dd>Defines the default connection collation to use, if not
1805 user-defined.<br />
1807 documentation</a> for list of possible values. This setting is ignored when
1808 connected to Drizzle server.</dd>
1812 The corresponding language file needs to be in
1814 </dd>
1817 <dd>Limit list of available languages to those matching the given regular
1818 expression. For example if you want only Czech and English, you should
1822 <dd>You can select here which functions will be used for character set
1823 conversion. Possible values are:
1824 <ul><li>auto - automatically use available one (first is tested
1825 iconv, then recode)</li>
1829 </ul>
1830 Default is auto.</dd>
1831 <dd>
1832 Enabled charset conversion activates a pull-down menu
1833 in the Export and Import pages, to choose the character set when
1834 exporting a file. The default value in this menu comes from
1836 </dd>
1839 <dd>Specify some parameters for iconv used in charset conversion. See
1842 used, so that invalid characters will be transliterated.</dd>
1845 <dd>Available character sets for MySQL conversion. You can add your own (any of
1846 supported by recode/iconv) or remove these which you don't use.
1847 Character sets will be shown in same order as here listed, so if you
1848 frequently use some of these move them to the top.</dd>
1853 default empty, you need to fill in some trusted proxy servers if you
1854 want to use rules for IP addresses behind proxy.<br /><br />
1856 The following example specifies that phpMyAdmin should trust a
1858 <pre>
1859 $cfg['TrustedProxies'] =
1861 </pre>
1862 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1863 client's IP address as usual.
1864 </dd>
1868 MIME transformations.<br />
1869 Possible values are:
1873 </ul>
1874 Default is auto.
1875 </dd>
1878 <dd>
1879 We normally check the permissions on the configuration file to ensure
1880 it's not world writable. However, phpMyAdmin could be installed on
1881 a NTFS filesystem mounted on a non-Windows server, in which case the
1882 permissions seems wrong but in fact cannot be detected. In this case
1884 </dd>
1887 <dd>
1888 Limit for length of URL in links. When length would be above this limit, it
1889 is replaced by form with button.
1890 This is required as some web servers (IIS) have problems with long URLs.
1892 </dd>
1894 <dt
1896 <dd>
1897 In the database Structure page, it's possible to mark some tables then
1898 choose an operation like optimizing for many tables. This can slow down
1901 </dd>
1905 </dd>
1907 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1909 </dt>
1910 <dd>The background styles used for both the frames.
1913 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1915 <dd>The style used for the pointer in the navi frame.
1924 </dd>
1928 <dd>The style used for table headers. See
1933 </dd>
1937 </dd>
1939 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1941 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1943 </dt>
1945 The former feature highlights the row over which your mouse is passing
1946 and the latter lets you visually mark/unmark rows by clicking on
1947 them. Highlighting / marking a column is done by hovering over /
1948 clicking the column's header (outside of the text).<br />
1953 <dd>You put here a valid CSS font family value, for example
1958 <dd>You put here a valid CSS font family value, for example
1972 </dt>
1974 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1976 The Char* values are used for CHAR and VARCHAR editing (if configured
1980 </dt>
1984 </dt>
1985 <dd>Defines if the whole textarea of the query box will be selected on
1986 click.</dd>
1989 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1990 Can be turned off by a toggle button on the browse page.</dd>
1993 </dt>
1994 <dd>Defines the place where table row links (Edit, Copy,
1995 Delete) would be put when tables contents are displayed (you may
1996 have them displayed at the left side, right side, both sides or nowhere).
2002 Define which one is displayed by default. The first mode displays each
2003 row on a horizontal line, the second rotates the headers by 90
2004 degrees, so you can use descriptive headers even though columns only
2005 contain small values and still print them out. The vertical mode sorts
2006 each row on a vertical lineup.
2007 </dd>
2013 <dd>
2014 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
2015 'css' the rotation of the header for horizontalflipped is done via
2016 CSS. The CSS transformation currently works only in Internet
2017 Explorer.If set to 'fake' PHP does the transformation for you, but of
2018 course this does not look as good as CSS. The 'auto' option enables
2019 CSS transformation when browser supports it and use PHP based one
2020 otherwise.
2021 </dd>
2025 </dt>
2027 display of column comments in Browse or Property display. In browse
2028 mode, the comments are shown inside the header. In property mode,
2029 comments are displayed using a CSS-formatted dashed-line below the
2030 name of the column. The comment is shown as a tool-tip for that column.
2031 </dd>
2043 <dd>Whether to display a link to validate a query in any SQL Query box.
2050 <dd>
2051 The name of the directory where
2053 uploaded by other means than phpMyAdmin (for example, ftp). Those files
2054 are available under a drop-down box when you click the database or
2055 table name, then the Import tab.
2056 <br /><br />
2058 If you want different directory for each user, %u will be replaced
2059 with username.<br /><br />
2063 compressed formats is enabled).<br /><br />
2065 This feature is useful when your file is too big to be uploaded via
2067 uploads are disabled in PHP.<br /><br />
2069 Please note that if PHP is running in safe mode, this directory must
2070 be owned by the same user as the owner of the phpMyAdmin scripts.
2071 <br /><br />
2075 alternatives.
2076 </dd>
2079 <dd>
2080 The name of the directory where dumps can be saved.<br /><br />
2082 If you want different directory for each user, %u will be replaced
2083 with username.<br /><br />
2085 Please note that the directory must exist and has to be writable for
2086 the user running webserver.<br /><br />
2088 Please note that if PHP is running in safe mode, this directory must
2089 be owned by the same user as the owner of the phpMyAdmin scripts.
2090 </dd>
2093 <dd>
2094 The name of the directory where temporary files can be stored.
2095 <br /><br />
2097 This is needed for importing ESRI Shapefiles, see
2102 <br /><br />
2104 If the directory where phpMyAdmin is installed is subject to an
2106 temporary directory in some directory accessible by the web
2107 server. However for security reasons, this directory should be outside
2108 the tree published by webserver. If you cannot avoid having this
2109 directory published by webserver, place at least an empty
2111 possible.
2112 <br /><br />
2114 This directory should have as strict permissions as possible as the only
2115 user required to access this directory is the one who runs the
2116 webserver. If you have root privileges, simply make this user owner of
2117 this directory and make it accessible only by it:
2118 <br /><br />
2120 <pre>
2121 chown www-data:www-data tmp
2122 chmod 700 tmp
2123 </pre>
2125 If you cannot change owner of the directory, you can achieve a similar
2128 <pre>
2129 chmod 700 tmp
2130 setfacl -m "g:www-data:rwx" tmp
2131 setfacl -d -m "g:www-data:rwx" tmp
2132 </pre>
2134 If neither of above works for you, you can still make the directory
2136 system reading and writing data in this directory.
2137 </dd>
2140 <dd>
2141 In this array are defined default parameters for export, names of
2142 items are similar to texts seen on export page, so you can easily
2143 identify what they mean.
2144 </dd>
2147 <dd>
2148 Defines how the export form is displayed when it loads. Valid values are:
2149 <ul>
2152 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2153 </ul>
2154 </dd>
2157 <dd>
2158 In this array are defined default parameters for import, names of
2159 items are similar to texts seen on import page, so you can easily
2160 identify what they mean.
2161 </dd>
2164 <dd>
2165 Defines whether or not to save all edited cells at once in browse-mode.
2166 </dd>
2169 <dd>
2170 Defines whether or not type display direction option is shown
2171 when browsing a table.
2172 </dd>
2175 <dd>
2176 Repeat the headers every X cells, or 0 to deactivate.
2177 </dd>
2185 </dt>
2186 <dd>
2187 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2188 or icon is always displayed on the left panel. If JavaScript is enabled in
2189 your browser, a click on this opens a distinct query window, which is
2190 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2191 changes to display a query box.<br /><br />
2193 The size of this query window can be customized with
2195 - both integers for the size in pixels. Note that normally, those
2197 theme you are using.<br /><br />
2201 opens the query window and puts the current query
2202 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2203 query in the right panel's query box.
2204 <br /><br />
2205 The usage of the JavaScript query window is recommended if you have a
2206 JavaScript enabled browser. Basic functions are used to exchange quite
2207 a few variables, so most 4th generation browsers should be capable to
2208 use that feature. It currently is only tested with Internet Explorer 6
2209 and Mozilla 1.x.
2210 <br /><br />
2212 to a table, which has to be created by you (see <a
2214 all your queries will be appended to the form, but only as long as
2215 your window is opened they remain saved.
2216 <br /><br />
2217 When using the JavaScript based query window, it will always get
2218 updated when you click on a new table/db to browse and will focus if
2219 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2220 the query window by checking the box "Do not overwrite this query from
2221 outside the window" below the query textarea. Then you can browse
2222 tables/databases in the background without losing the contents of the
2223 textarea, so this is especially useful when composing a query with
2224 tables you first have to look in. The checkbox will get automatically
2225 checked whenever you change the contents of the textarea. Please
2226 uncheck the button whenever you definitely want the query window to
2227 get updated even though you have made alterations.
2228 <br /><br />
2231 <br /><br />
2232 The query window also has a custom tabbed look to group the features.
2234 default tab to be used when opening the query window. It can be set to
2235 either 'sql', 'files', 'history' or 'full'.</dd>
2241 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2243 If the approximate row count as returned by
2246 count will be used.
2247 </dd>
2249 <dd>For VIEWs, since obtaining the exact count could have an
2250 impact on performance, this value is the maximum to be displayed, using
2252 any row counting.
2253 </dd>
2256 <dd>Sorts database and table names according to natural order (for example,
2257 t1, t2, t10). Currently implemented in the left panel (Light mode)
2258 and in Database view, for the table list.</dd>
2267 that users can't set through user preferences. For possible values, refer
2271 <dd>Activates in the user preferences a tab containing options for
2272 developers of phpMyAdmin.</dd>
2278 <dd>Allows you to specify window's title bar. You can use
2280 </dd>
2290 </dd>
2293 <dd>If theme manager is active, use this as the path of the subdirectory
2294 containing all the themes.</dd>
2308 </dt>
2309 <dd>Default queries that will be displayed in query boxes when user didn't
2310 specify any. You can use standard
2312 </dd>
2315 <dd>
2316 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
2317 default we use HTML to format the query, but you can disable this by
2319 </dd>
2322 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2323 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2324 query inside a bracket is indented. By changing
2327 specifies the units of the indent amount that you specified. This is
2328 used via stylesheets.</dd>
2331 <dd>This array is used to define the colours for each type of element of
2332 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2334 If you specify an empty string for the color of a class, it is ignored
2335 in creating the stylesheet.
2336 You should not alter the class names, only the colour strings.<br />
2357 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2361 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2362 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2363 </ul>
2364 </dd>
2368 <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,
2369 as originally published on
2371 <br />
2372 For help in setting up your system to use the service, see the
2374 </dd>
2378 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2379 and any password, so we use those by default. Instead, if
2380 you have an account with them, you can put your login details
2381 here, and it will be used in place of the anonymous login.</dd>
2382 </dl>
2383 </dd>
2386 <dd><b>DEVELOPERS ONLY!</b></dd>
2389 <dd><b>DEVELOPERS ONLY!</b><br />
2390 Enable logging queries and execution times to be displayed in the bottom
2391 of main page (right frame).</dd>
2394 <dd>All possible types of a MySQL column. In most cases you don't need to
2395 edit this.</dd>
2398 <dd>Possible attributes for columns. In most cases you don't need to edit
2399 this.</dd>
2402 <dd>A list of functions MySQL supports. In most cases you don't need to
2403 edit this.</dd>
2406 <dd>Mapping of column types to meta types used for preferring displayed
2407 functions. In most cases you don't need to edit this.</dd>
2410 <dd>Functions preferred for column meta types as defined in
2411 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2412 to edit this.</dd>
2415 <dd>Functions selected by default when inserting/changing row, Functions
2416 are defined for meta types from
2418 <code>first_timestamp</code>, which is used for first timestamp column
2419 in table.</dd>
2421 </dl>
2423 <!-- TRANSFORMATIONS -->
2429 </ol>
2433 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2435 section</a> on how to do so.</p>
2437 <p> You can apply different transformations to the contents of each column. The
2438 transformation will take the content of each column and transform it with
2439 certain rules defined in the selected transformation.</p>
2441 <p> Say you have a column 'filename' which contains a filename. Normally you would
2442 see in phpMyAdmin only this filename. Using transformations you can transform
2443 that filename into a HTML link, so you can click inside of the phpMyAdmin
2444 structure on the column's link and will see the file displayed in a new browser
2445 window. Using transformation options you can also specify strings to
2446 append/prepend to a string or the format you want the output stored in.</p>
2448 <p> For a general overview of all available transformations and their options,
2449 you can consult your
2450 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2451 installation.</p>
2453 <p> For a tutorial on how to effectively use transformations, see our
2455 the official phpMyAdmin homepage.</p>
2459 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2460 clicking on the 'Structure' link for a table). There click on
2461 "Change" (or change icon) and there you will see three new
2462 fields at
2463 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2464 'Transformation options'.</p>
2466 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2467 that corresponds to the column's contents. Please note that
2468 transformations are inactive as long as no MIME-type is selected.</li>
2470 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2471 hopefully growing amount of pre-defined transformations. See below for information on
2472 how to build your own transformation.<br />
2474 There are global transformations and mimetype-bound transformations. Global transformations
2475 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2476 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2477 transformations which operate on the main mimetype (like 'image'), which will most likely
2478 take the subtype into regard, and those who only operate on a
2479 specific subtype (like 'image/jpeg').<br />
2481 You can use transformations on mimetypes for which the function was not defined for. There
2482 is no security check for you selected the right transformation, so take care of what the
2483 output will be like.</li>
2485 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2486 transform-function specific options here. Usually the transforms can operate with default
2487 options, but it is generally a good idea to look up the overview to see which options are
2488 necessary.<br />
2490 Much like the ENUM/SET-Fields, you have to split up several options using the format
2491 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2492 parsed as an array, leaving the first value the first element in the array, and so
2493 forth.<br />
2495 If you want to specify a MIME character set you can define it in the transformation_options.
2496 You have to put that outside of the pre-defined options of the specific mime-transform,
2498 for which you can specify 2 options and you want to append a character set, enter "'first
2499 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2501 </ul>
2505 <p> All mimetypes and their transformations are defined through single files in
2506 the directory 'libraries/transformations/'.</p>
2508 <p> They are stored in files to ease up customization and easy adding of new
2509 transformations.</p>
2511 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2512 always work. It makes no sense to apply a transformation to a mimetype the
2513 transform-function doesn't know to handle.</p>
2515 <p> One can, however, use empty mime-types and global transformations which should work
2516 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2517 for, but pay attention to option usage as well as what the transformation does to your
2518 column.</p>
2520 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2521 any other transform function and provides some basic functions.</p>
2523 <p> There are 5 possible file names:</p>
2525 <ol><li>A mimetype+subtype transform:<br /><br />
2527 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2529 Please not that mimetype and subtype are separated via '_', which shall
2530 not be contained in their names. The transform function/filename may
2531 contain only characters which cause no problems in the file system as
2532 well as the PHP function naming convention.<br /><br />
2534 The transform function will the be called
2535 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2537 <b>Example:</b><br /><br />
2539 <tt>text_html__formatted.inc.php</tt><br />
2540 <tt>PMA_transform_text_html__formatted()</tt></li>
2542 <li>A mimetype (w/o subtype) transform:<br /><br />
2544 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2546 Please note that there are no single '_' characters.
2547 The transform function/filename may contain only characters which cause
2548 no problems in the file system as well as the PHP function naming
2549 convention.<br /><br />
2551 The transform function will the be called
2552 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2554 <b>Example:</b><br /><br />
2556 <tt>text__formatted.inc.php</tt><br />
2557 <tt>PMA_transform_text__formatted()</tt></li>
2559 <li>A mimetype+subtype without specific transform function<br /><br />
2561 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2563 Please note that there are no '__' characters in the filename. Do not
2564 use special characters in the filename causing problems with the file
2565 system.<br /><br />
2567 No transformation function is defined in the file itself.<br /><br />
2569 <b>Example:</b><br /><br />
2571 <tt>text_plain.inc.php</tt><br />
2572 (No function)</li>
2574 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2576 <tt>[mimetype].inc.php</tt><br /><br />
2578 Please note that there are no '_' characters in the filename. Do not use
2579 special characters in the filename causing problems with the file system.
2580 <br /><br />
2582 No transformation function is defined in the file itself.<br /><br />
2584 <b>Example:</b><br /><br />
2586 <tt>text.inc.php</tt><br />
2587 (No function)</li>
2589 <li>A global transform function with no specific mimetype<br /><br />
2591 <tt>global__[transform].inc.php</tt><br /><br />
2593 The transform function will the be called
2594 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2596 <b>Example:</b><br /><br />
2598 <tt>global__formatted</tt><br />
2599 <tt>PMA_transform_global__formatted()</tt></li>
2600 </ol>
2602 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2603 transform function.</p>
2605 <p> All filenames containing no '__' in themselves are not shown as valid transform
2606 functions in the dropdown.</p>
2608 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2609 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2610 without a transform function.</p>
2612 <p> To create a new transform function please see
2613 <tt>libraries/transformations/template_generator.sh</tt>.
2614 To create a new, empty mimetype please see
2615 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2617 <p> A transform function always gets passed three variables:</p>
2619 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2620 you want to transform.</li>
2621 <li><b>$options</b> - Contains any user-passed options to a transform function
2622 as an array.</li>
2623 <li><b>$meta</b> - Contains an object with information about your column.
2624 The data is drawn from the output of the
2626 function. This means, all object properties described on the
2628 available in this variable and can be used to transform a column accordingly
2629 to unsigned/zerofill/not_null/... properties.<br />
2630 The $meta->mimetype variable contains the original MIME-type of the
2631 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2632 </ol>
2634 <p> Additionally you should also provide additional function to provide
2635 information about the transformation to the user. This function should
2636 have same name as transformation function just with appended
2637 <code>_info</code> suffix. This function accepts no parameters and returns
2638 array with information about the transformation. Currently following keys
2639 can be used:
2640 </p>
2641 <dl>
2642 <dt><code>info</code></dt>
2643 <dd>Long description of the transformation.</dd>
2644 </dl>
2646 <!-- FAQ -->
2653 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2658 </ol>
2660 <p> Please have a look at our
2662 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2663 features and or interface.</p>
2669 action is required or phpMyAdmin sends a blank page or a page full of
2670 cryptic characters to my browser, what can I do?</a></h4>
2673 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2674 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2675 configuration file.<br /></p>
2680 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2681 See also the
2683 entry about PHP bugs with output buffering.<br />
2684 If your server keeps crashing, please ask for help in the various Apache
2685 support groups.</p>
2694 application misbehaved by not returning a complete set of
2696 </h4>
2698 <p> You just forgot to read the <i>install.txt</i> file from the PHP distribution.
2699 Have a look at the last message in this
2701 official PHP bug database.</p>
2706 and/or many error messages with the
2709 <p> This is a known problem with the PHP
2711 filter: it's not so stable. Please use instead the cookie authentication mode.
2712 </p>
2717 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2718 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2719 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2720 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2721 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2726 work.</a></h4>
2728 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2729 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2730 or not, and so on). So, you must have Zlib/Bzip2
2731 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2735 an error about safe mode being in effect.</a></h4>
2737 <p> Your uploaded file is saved by PHP in the "upload dir", as
2738 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2739 the system default is <i>/tmp</i>).<br />
2740 We recommend the following setup for Apache servers running in safe mode,
2741 to enable uploads of files while being reasonably secure:</p>
2743 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2744 <li>give ownership to the Apache server's user.group:
2745 <tt>chown apache.apache /tmp/php</tt></li>
2746 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2747 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2748 <li>restart Apache</li>
2749 </ul>
2756 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2757 I'm using the Apache server.</a></h4>
2759 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2760 your <i>httpd.conf</i>:</p>
2764 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2768 uploading a file from the query box.</a></h4>
2770 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2771 restrictions. However you need to create temporary directory and
2773 The uploaded files will be moved there, and after execution of your
2779 <p> The MySQL manual explains how to
2781 reset the permissions</a>.</p>
2791 </h4>
2793 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2794 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2795 names to align with current standards.</p>
2800 </h4>
2802 <p> Starting with version 2.7.0, the import engine has been re–written and these
2803 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2804 to take advantage of the new import features.</p>
2806 <p> The first things to check (or ask your host provider to check) are the
2807 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2808 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2809 All of these three settings limit the maximum size of data that can be
2810 submitted and handled by PHP. One user also said that post_max_size
2811 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2813 There exist several workarounds if your upload is too big or your
2814 hosting provider is unwilling to change the settings:</p>
2817 feature. This allows one to
2818 upload a file to the server via scp, ftp, or your favorite file transfer
2819 method. PhpMyAdmin is then able to import the files from the temporary
2821 section</a> of this document.</li>
2823 BigDump</a>) to split the files before uploading. We cannot support this
2824 or any third party applications, but are aware of users having success
2825 with it.</li>
2826 <li>If you have shell (command line) access, use MySQL to import the files
2827 directly. You can do this by issuing the "source" command from
2828 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2829 </ul>
2833 support?</a></h4>
2835 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2836 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2837 connect to your MySQL server using PHP's classic
2840 is available in PHP 5.0. The latter one should be used unless you have a
2841 good reason not to do so.<br />
2842 When compiling PHP, we strongly recommend that you manually link the MySQL
2843 extension of your choice to a MySQL client library of at least the same
2844 minor version since the one that is bundled with some PHP distributions is
2848 (versions 5.1 and 5.2 were tested).<br /><br />
2850 </p>
2854 message, "Client does not support authentication protocol requested
2855 by server; consider upgrading MySQL client"</a></h5>
2857 <p> You tried to access MySQL with an old MySQL client library. The version of
2858 your MySQL client library can be checked in your phpinfo() output.
2859 In general, it should have at least the same minor version as your server
2863 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2864 changed the authentication hash and your PHP is trying to use the old method.
2866 with the proper client library to match your MySQL installation. Your
2867 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2868 More information (and several workarounds) are located in the
2870 </p>
2877 script seems not to know the font face I'm using!</a></h4>
2879 <p> The "FPDF" library we're using for this feature requires some
2880 special files to use font faces.<br />
2882 these files.</p>
2886 check PHP Configuration".</a></h4>
2888 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2889 "MySQL extension". This extension may be part of the PHP
2890 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2891 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2892 to load the extension but failed.<br /><br />
2894 Usually, the problem is solved by installing a software package called
2895 "PHP-MySQL" or something similar.</p>
2900 and I cannot log in using cookie auth.</a></h4>
2902 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2906 so I cannot upload.</a></h4>
2908 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2909 parameter is not set to "on".</p>
2913 a new table the table and column names are changed to lowercase!</a></h4>
2915 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2916 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2917 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2918 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2919 directory and add the following line to the group [mysqld]:</p>
2921 <pre>set-variable = lower_case_table_names=0</pre>
2923 <p> Next, save the file and restart the MySQL service. You can always check the
2924 value of this directive using the query</p>
2926 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2933 and I get problems, such as undefined variables when I run a
2936 <p> A tip from Jose Fandos: put a comment on the following two lines
2937 in httpd.conf, like this:</p>
2939 <pre>
2940 # mod_gzip_item_include file \.php$
2942 </pre>
2944 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2945 PHP scripts. Of course you have to restart Apache.</p>
2950 I get the error "No input file specified" when trying to
2951 run phpMyAdmin.</a></h4>
2953 <p> This is a permission problem. Right-click on the phpmyadmin folder
2954 and choose properties. Under the tab Security, click on "Add"
2955 and select the user "IUSR_machine" from the list. Now set his
2956 permissions and it should work.</p>
2960 db_structure.php with plenty of tables).</a></h4>
2963 GZIP output buffering is enabled. If you turn off it (by
2965 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2966 PHP 5.0.0.</p>
2970 message 'Errorcode: 13'. What does this mean?</a></h4>
2972 <p> This can happen due to a MySQL bug when having database / table names with
2973 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2974 To fix this, turn off this directive, convert all database and table names
2975 to lower case and turn it on again. Alternatively, there's a bug-fix
2976 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2980 and the columns are duplicated.</a></h4>
2982 <p> It is possible to configure Apache in such a way that PHP has problems
2983 interpreting .php files.</p>
2985 <p> The problems occur when two different (and conflicting) set of directives
2986 are used:</p>
2988 <pre>
2989 SetOutputFilter PHP
2990 SetInputFilter PHP
2991 </pre>
2993 <p> and</p>
2995 <pre>AddType application/x-httpd-php .php</pre>
2997 <p> In the case we saw, one set of directives was in
2998 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2999 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
3000 The recommended way is with <tt>AddType</tt>, so just comment out
3001 the first set of lines and restart Apache:</p>
3003 <pre>
3004 #SetOutputFilter PHP
3005 #SetInputFilter PHP
3006 </pre>
3011 <p> This problem is known to happen when the server is running Turck MMCache
3012 but upgrading MMCache to version 2.3.21 solves the problem.</p>
3017 <p>Yes.</p>
3018 <p>
3019 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
3020 is still maintained.
3021 </p>
3024 <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>
3026 <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>
3029 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3030 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3031 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3032 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3033 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3034 enabled.) Click <tt>OK</tt>.</li>
3035 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3036 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3037 </ol>
3046 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
3047 the order of the server paragraph in <tt>config.inc.php</tt>.
3048 Table and script parts are optional. If you want
3049 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3050 some configuration. Following lines apply only for <a
3052 that you have enabled some features within global configuration. You need
3053 <code>Options FollowSymLinks</code> and <code>AllowOverride
3054 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3055 you need mod_rewrite to be enabled. Then you just need to create following
3056 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3057 (don't forget to change directory name inside of it):</p>
3059 <pre>
3060 RewriteEngine On
3061 RewriteBase /path_to_phpMyAdmin
3062 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3063 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3064 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3065 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3066 </pre>
3069 <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>
3071 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3072 following rewrite rule:</p>
3074 <pre>
3075 RewriteEngine On
3076 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3077 </pre>
3081 </h4>
3082 <p>
3083 There can be many explanations to this and a look at your server's
3084 error log file might give a clue.
3085 </p>
3089 password encryption in cookie auth doesn't work.</a></h4>
3091 <p> If your cluster consist of different architectures, PHP code used for
3092 encryption/decryption won't work correct. This is caused by use of
3093 pack/unpack functions in code. Only solution is to use mcrypt extension
3094 which works fine in this case.</p>
3099 <p> Yes but the default configuration values of Suhosin are known to cause
3100 problems with some operations, for example editing a table with many
3101 columns and no primary key or with textual primary key.
3102 </p>
3103 <p>
3104 Suhosin configuration might lead to malfunction in some cases and it can
3105 not be fully avoided as phpMyAdmin is kind of application which needs to
3106 transfer big amounts of columns in single HTTP request, what is something
3107 what Suhosin tries to prevent. Generally all
3108 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3109 <code>suhosin.get.*</code> directives can have negative effect on
3110 phpMyAdmin usability. You can always find in your error logs which limit
3111 did cause dropping of variable, so you can diagnose the problem and adjust
3112 matching configuration variable.
3113 </p>
3114 <p>
3115 The default values for most Suhosin configuration options will work in most
3116 scenarios, however you might want to adjust at least following parameters:
3117 </p>
3119 <ul>
3120 <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>
3121 <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>
3122 <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>
3123 <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>
3124 <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>
3125 <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>
3126 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.get.max_value_length">suhosin.get.max_value_length</a> should be increased (eg. 1024)</li>
3127 <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>
3128 <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>
3129 </ul>
3131 <p>
3133 <tt>SuhosinDisableWarning</tt> directive</a>.
3134 </p>
3138 but then my connection is redirected back to http. What can cause this
3139 behavior?</a></h4>
3141 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3142 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>
3145 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3147 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3148 Example from the Apache 2.2 documentation:</p>
3149 <pre>
3150 ProxyPass /mirror/foo/ http://backend.example.com/
3151 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3152 ProxyPassReverseCookieDomain backend.example.com public.example.com
3153 ProxyPassReverseCookiePath / /mirror/foo/
3154 </pre>
3156 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3157 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3158 This is not specific to phpmyadmin, it's just the behavior of Apache.
3159 </p>
3161 <pre>
3162 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3163 ProxyPassReverse /mirror/foo/
3164 http://backend.example.com/%7Euser/phpmyadmin
3165 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3166 </pre>
3168 <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>
3169 for more details.</p>
3173 privileges, I get an error about an unknown column.</a></h4>
3175 <p> The MySQL server's privilege tables are not up to date, you need to run
3176 the <tt>mysql_upgrade</tt> command on the server.</p>
3183 headers already sent by ..." is displayed, what's the problem?</a></h4>
3185 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3186 (I.E. no blank lines, no spaces, no characters...) neither before the
3187 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3188 tag at the end. We also got a report from a user under IIS, that used
3189 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3190 contained an end-of-line character (hex 0A) at the end; removing this character
3191 cleared his errors.</p>
3196 <p> Either there is an error with your PHP setup or your username/password is
3197 wrong. Try to make a small script which uses mysql_connect and see if it
3198 works. If it doesn't, it may be you haven't even compiled MySQL support
3199 into PHP.</p>
3203 connect to local MySQL server through socket '/tmp/mysql.sock'
3204 (111) ..." is displayed. What can I do?</a></h4>
3206 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3208 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3209 In your <i>php.ini</i> you will find a line</p>
3211 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3213 <p> change it to</p>
3215 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3217 <p> Then restart apache and it will work.</p>
3219 <p> Here is a fix suggested by Brad Ummer:</p>
3221 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3222 To do this, telnet to your server and go to the MySQL bin directory. In
3223 this directory there should be a file named <i>mysqladmin</i>. Type
3224 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3225 info about your MySQL server, including the socket
3226 (<i>/tmp/mysql.sock</i>, for example).</li>
3227 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3228 phpMyAdmin, you need to complete the socket information in the
3229 <i>config.inc.php</i>.<br />
3230 For example:
3232 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3233 <br /><br />
3235 Please also make sure that the permissions of this file allow to be readable
3236 by your webserver (i.e. '0755').</li>
3237 </ul>
3239 <p> Have also a look at the
3241 corresponding section of the MySQL documentation</a>.</p>
3245 what can I do?</a></h4>
3248 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3249 sometime.<br />
3250 Also have a look at your PHP version number: if it contains "b" or "alpha"
3251 it means you're running a testing version of PHP. That's not a so good idea,
3252 please upgrade to a plain revision.</p>
3256 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3257 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3259 <p> Check the value you set for the
3261 directive in the phpMyAdmin configuration file.</p>
3265 password: YES)"-error when trying to access a MySQL-Server on a
3266 host which is port-forwarded for my localhost.</a></h4>
3268 <p> When you are using a port on your localhost, which you redirect via
3269 port-forwarding to another host, MySQL is not resolving the localhost
3270 as expected.<br />
3271 Erik Wasser explains: The solution is: if your host is "localhost"
3272 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3273 connection for speeding up things. And that doesn't work in this configuration
3274 with port forwarding.<br />
3280 <p> Themes are configured with
3284 <br />
3286 should not delete the directory "original" or its underlying
3287 structure, because this is the system theme used by phpMyAdmin.
3288 "original" contains all images and styles, for backwards
3289 compatibility and for all themes that would not include images or css-files.
3290 <br /><br />
3293 is enabled, you can select your favorite theme on the main page. Your
3294 selected theme will be stored in a cookie.<br /><br /></p>
3296 <p> To create a theme:</p>
3298 <ul><li>make a new subdirectory (for example "your_theme_name") under
3300 (by default <tt>themes</tt>)</li>
3301 <li>copy the files and directories from "original" to
3302 "your_theme_name"</li>
3303 <li>edit the css-files in "your_theme_name/css"</li>
3304 <li>put your new images in "your_theme_name/img"</li>
3305 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3306 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3307 contain your chosen theme name, that will be visible in user interface</li>
3308 <li>make a new screenshot of your theme and save it under
3309 "your_theme_name/screen.png"</li>
3310 </ul>
3312 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3313 theme verbose name, theme generation and theme version. These versions and
3314 generations are enumerated from 1 and do not have any direct dependence on
3315 phpMyAdmin version. Themes within same generation should be backwards
3316 compatible - theme with version 2 should work in phpMyAdmin requiring
3317 version 1. Themes with different generation are incompatible.</p>
3319 <p> If you do not want to use your own symbols and buttons, remove the
3320 directory "img" in "your_theme_name". phpMyAdmin will
3321 use the default icons and buttons (from the system-theme "original").
3322 </p>
3326 what can I do?</a></h4>
3328 <p> Here are a few points to check:</p>
3330 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3332 directive empty. See also
3334 </li>
3335 <li>Maybe you have a broken PHP installation or you need to upgrade
3336 your Zend Optimizer. See
3338 http://bugs.php.net/bug.php?id=31134</a>.
3339 </li>
3340 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3341 set to the default (200) or another low value, you could get this
3342 error if your table has a high number of columns. Adjust this setting
3343 accordingly. (Thanks to Klaus Dorninger for the hint).
3344 </li>
3345 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3346 of ";" will cause this error. Replace it with "&;".
3347 </li>
3349 you might want to increase
3351 </li>
3352 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3353 </li>
3354 </ul>
3359 <p> To be able to see a progress bar during your uploads, your server must
3362 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3363 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3370 who logged out can not log in again in with the same nick.</a></h4>
3372 <p> This is related to the authentication mechanism (protocol) used by
3373 phpMyAdmin. To bypass this problem: just close all the opened
3374 browser windows and then go back to phpMyAdmin. You should be able to
3375 log in again.</p>
3379 limit error or a time limit error.</a></h4>
3381 <p> Compressed dumps are built in memory and because of this are limited to
3382 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3383 using
3385 (enabled by default). Zip exports can not be handled this way, so if you need
3386 Zip files for larger dump, you have to use another way.</p>
3390 when I rename a table or a column.</a></h4>
3392 <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>
3396 bundled with the MySQL server distribution.</a></h4>
3398 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3400 <pre>
3401 -- MySQL dump 8.22
3402 --
3403 -- Host: localhost Database: database
3404 ---------------------------------------------------------
3405 -- Server version 3.23.54
3406 </pre>
3408 <p> The invalid part of the code is the horizontal line made of dashes that
3409 appears once in every dump created with mysqldump. If you want to run your
3410 dump you have to turn it into valid MySQL. This means, you have to add a
3411 whitespace after the first two dashes of the line or add a # before it:
3412 <br />
3413 <code>
3414 -- -------------------------------------------------------<br />
3415 </code>
3416 or<br />
3417 <code>
3418 #---------------------------------------------------------
3419 </code>
3420 </p>
3427 <p> Please note that you should not use the separating string multiple times
3428 without any characters between them, or at the beginning/end of your table
3429 name. If you have to, think about using another TableSeparator or disabling
3430 that feature</p>
3435 <p> In Relation view, being able to choose a table in another database,
3436 or having more than one index column in the foreign key.<br /><br/>
3437 In Query-by-example (Query), automatic generation of the query
3438 LEFT JOIN from the foreign table.<br /><br/>
3439 </p>
3443 I get series of errors like "Warning: unable to parse url". How
3444 can this be fixed?</a></h4>
3445 <p>
3446 Your table neither have a primary key nor an unique one, so we must use a
3447 long expression to identify this row. This causes problems to parse_url
3448 function. The workaround is to create a primary or unique key.
3449 <br />
3450 </p>
3454 a MIME-Transformation onto!</a></h4>
3456 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3457 nested forms can be put inside the table where phpMyAdmin displays the results.
3458 You can, however, use any form inside of a table if keep the parent
3459 form-container with the target to tbl_row_delete.php and just put your own
3460 input-elements inside. If you use a custom submit input field, the form will
3461 submit itself to the displaying page again, where you can validate the
3462 $HTTP_POST_VARS in a transformation.
3464 For a tutorial on how to effectively use transformations, see our
3466 on the official phpMyAdmin-homepage.</p>
3470 MySQL server</a></h4>
3472 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3475 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3476 the quote-character (") is interpreted as an identifier quote character and
3477 not as a string quote character, which makes many internal phpMyAdmin
3479 statements. There is no workaround to this behaviour. News to this item will
3480 be posted in Bug report
3481 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3482 </p>
3486 more that one column with the same value
3487 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3488 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3490 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3491 can use it for the Edit and Delete links.</p>
3496 <p> phpMyAdmin uses a quick method to get the row count, and this method
3497 only returns an approximate count in the case of InnoDB tables. See
3499 a way to modify those results, but
3500 this could have a serious impact on performance.</p>
3507 containing an hyphen.
3508 </a></h4>
3509 <p>
3510 The tests I have made with MySQL 5.1.49 shows that the
3511 API does not accept this syntax for the USE command.
3512 </p>
3515 <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>
3516 <p>
3517 This has been a known limitation of phpMyAdmin since the beginning and
3518 it's not likely to be solved in the future.
3519 </p>
3521 <!-- Begin: Excel import limitations -->
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 differentiate 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 Follow security recommendations for PHP and your webserver.
3596 </li>
3597 </ul>
3602 </a></h4>
3603 <p>
3608 </p>
3611 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3612 authentication.
3613 </a></h4>
3617 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3618 and/or
3620 are wrong.</li>
3622 <li>You have already setup a security mechanism for the
3623 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3624 phpMyAdmin's authentication, so remove it.</li>
3625 </ul>
3632 and put the privileges you want. For example,
3634 would let a user create/manage his/her database(s).</p>
3639 <p> If you have existing rules from an old .htaccess file, you can take them
3642 be a major benefit here if your installation is suited to using it. Then
3643 you can just add those updated lines into the
3647 <p> If you want a pre-made sample, you can try this fragment. It stops the
3648 'root' user from logging in from any networks other than the private
3651 <pre>
3652 //block root from logging in except from the private networks
3653 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3654 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3655 'deny root from all',
3656 'allow root from localhost',
3660 );
3661 </pre>
3666 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3667 different than the one set in your
3669 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3670 while a domain name is defined in the config file.</p>
3675 <p>When starting phpMyAdmin, you can use the <tt>db</tt>, <tt>pma_username</tt>, <tt>pma_password</tt> and <tt>server</tt> parameters. This last one can contain either the numeric host index (from <tt>$i</tt> of the configuration file) or one of the host names present in the configuration file. Using <tt>pma_username</tt> and <tt>pma_password</tt> has been tested along with the usage of 'cookie' <tt>auth_type</tt>.</p>
3681 when trying to create a table with more than 14 columns.
3682 </a></h4>
3683 <p>
3684 We could reproduce this problem only under Win98/98SE. Testing under
3685 WinNT4 or Win2K, we could easily create more than 60 columns.
3686 <br />
3687 A workaround is to create a smaller number of columns, then come back to
3688 your table properties and add the other columns.
3689 </p>
3693 <p>
3694 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3695 with each script/website that use forms.<br />
3696 Upgrade or downgrade your Xitami server.
3697 </p>
3700 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3701 <p>
3702 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3703 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3704 don't seem to work.<br />
3706 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3707 the user's temporary directory, so they must be moved before closing
3708 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3711 </p>
3715 Explorer never stores the cookies.
3716 </a></h4>
3717 <p>
3718 MS Internet Explorer seems to be really buggy about cookies, at least till
3719 version 6.
3720 </p>
3724 rows.
3725 </a></h4>
3726 <p>
3728 </p>
3731 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3732 when trying to modify a row in a table with many columns, or with a text
3733 column
3734 </a></h4>
3735 <p>
3736 Your table neither have a primary key nor an unique one, so we must use a
3737 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
3738 those browsers, and this not happen in Netscape, for example. The
3739 workaround is to create a primary or unique key, or use another browser.
3740 <br />
3741 </p>
3745 page.
3746 </a></h4>
3747 <p>
3748 Some browsers support right-clicking into the frame you want to refresh,
3749 just do this in the right frame.<br />
3750 </p>
3754 query box.
3755 </a></h4>
3756 <p>
3757 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3758 Mozilla versions.<br />
3759 </p>
3763 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3764 </a></h4>
3765 <p>
3766 This is a Mozilla bug (see bug #26882 at
3768 </p>
3773 </a></h4>
3774 <p>
3775 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3776 data in octet-stream mode. Since we can't detect the specific Netscape
3777 version, we cannot workaround this bug.
3778 </p>
3782 wrong.</a></h4>
3784 <p> Please ensure that you have set your browser's character set to the one of the
3785 language file you have selected on phpMyAdmin's start page.
3786 Alternatively, you can try the auto detection mode that is supported by the
3787 recent versions of the most browsers.</p>
3790 <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
3793 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3794 Netscape and Mozilla do not have this problem.</p>
3797 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3798 I cannot manage two servers: I log in to the first one, then the other one,
3799 but if I switch back to the first, I have to log in on each operation.</a></h4>
3805 but nothing happens after that, only a blank screen.</a></h4>
3816 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3821 address and you are starting
3823 containing a domain name, or the reverse situation.</li>
3824 <li>Security settings in IE and/or Microsoft Security Center are
3825 too high, thus blocking scripts execution.</li>
3826 <li>The Windows Firewall is blocking Apache and MySQL. You must
3830 </ul>
3833 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3834 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3835 installed in their Firefox is causing the problem.</p>
3839 clause is generated when I browse a table.</a></h4>
3840 <p> This happens only when both of these conditions are met: using the
3850 </a></h4>
3851 <p>
3852 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3853 specifying a wrong column-type.<br />
3854 Common errors include:
3855 </p>
3856 <ul>
3859 </ul>
3860 <p>
3861 Also, look at the syntax chapter in the MySQL manual to confirm that your
3862 syntax is correct.
3863 </p>
3867 columns and
3868 phpMyAdmin generates only one index with those two columns.
3869 </a></h4>
3870 <p>
3871 This is the way to create a multi-columns
3872 index. If you want two indexes, create the first one when creating the
3873 table, save, then display the table properties and click the Index link to
3874 create the other index.
3875 </p>
3879 <p>
3880 Since version 2.2.3, you have a checkbox for each column that can be null.
3882 column's value. Since version 2.5.5, you have to use the checkbox to get
3884 a literal NULL in the column, and not a NULL value (this works in PHP4).
3885 </p>
3890 <p> Click on a database or table name in the left frame, the properties will be
3892 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3893 statements that can be used to recreate your database/table.
3894 <br /><br />
3896 transmit the resulting dump to your station. Depending on your PHP
3897 configuration, you will see options to compress the dump. See also the
3899 configuration variable.<br /><br />
3902 this document.</p>
3907 </a></h4>
3909 <p> Click on a database name in the left frame, the properties will be
3911 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3913 the path to your dump filename, or use the Browse button. Then click Go.
3914 <br /><br />
3916 that you upgrade to take advantage of the new features.
3917 <br /><br />
3919 in this document.
3920 </p>
3925 <p> Here is an example with the tables persons, towns and countries, all
3927 table, create it as explained in the configuration section. Then create the
3928 example tables:</p>
3930 <pre>
3931 CREATE TABLE REL_countries (
3932 country_code char(1) NOT NULL default '',
3933 description varchar(10) NOT NULL default '',
3934 PRIMARY KEY (country_code)
3935 ) TYPE=MyISAM;
3937 INSERT INTO REL_countries VALUES ('C', 'Canada');
3939 CREATE TABLE REL_persons (
3940 id tinyint(4) NOT NULL auto_increment,
3941 person_name varchar(32) NOT NULL default '',
3943 country_code char(1) NOT NULL default '',
3944 PRIMARY KEY (id)
3945 ) TYPE=MyISAM;
3947 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3948 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3950 CREATE TABLE REL_towns (
3952 description varchar(30) NOT NULL default '',
3953 PRIMARY KEY (town_code)
3954 ) TYPE=MyISAM;
3956 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3957 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3958 </pre>
3964 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3968 </ul>
3976 <li>In the columns row, choose persons.person_name and click the
3978 <li>Do the same for towns.description and countries.descriptions in the
3981 the correct joins have been generated</li>
3983 </ul>
3987 <p>
3988 Starting from the previous example, create the pma_table_info as explained
3989 in the configuration section, then browse your persons table,
3990 and move the mouse over a town code or country code.
3991 <br /><br />
3992 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3993 enables: drop-down list of possible values.
3994 </p>
3997 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3998 <p>
4001 <br /><br />
4002 Then you need to think about your schema layout. Which tables will go on
4003 which pages?
4004 </p>
4005 <ul>
4011 page and click Go. If you like, you
4013 linked tables onto the new page.</li>
4014 <li>Select the name of the new page (making sure the Edit radio button
4015 is selected) and click Go.</li>
4017 Coordinates are relative; your diagram will
4018 be automatically scaled to fit the page. When initially placing tables
4019 on the page, just pick any coordinates -- say, 50x50. After clicking
4021 position the element correctly.</li>
4023 first be sure to click the Save
4024 button beneath the list of tables and coordinates, to save any changes
4025 you made there. Then scroll all the way down, select the
4027 you want, and click Go.</li>
4028 <li>Internet Explorer for Windows may suggest an incorrect filename when
4033 browsers on Windows, do not have this problem.</li>
4034 </ul>
4038 columns!</a></h4>
4040 <p> No, it's MySQL that is doing
4046 underscores in the database name?</a></h4>
4048 <p> If you do not put a backslash before the underscore, this is a wildcard
4051 john2db ...<br /><br />
4053 If you put a backslash before the underscore, it means that the database
4054 name will have a real underscore.</p>
4058 statistics pages?</a></h4>
4069 if it already exists during the import. It does NOT drop the table after
4070 your export, it only affects the import file.</li>
4072 Otherwise, you may get an error if the table name exists but has a
4073 different structure.</li>
4075 (if any) will be included in backup.</li>
4077 column and table names formed with special characters are protected.</li>
4079 types set in the pmadb in the dump as
4081 </li>
4082 </ul>
4087 command, for better documentation (but resulting file is bigger).</li>
4089 once the INSERT verb and the table name.</li>
4092 </li>
4094 more info is provided in the
4096 but basically with this selected, invalid values are adjusted and
4097 inserted rather than causing the entire statement to fail.</li>
4098 </ul>
4102 in its name.</a></h4>
4105 is the normal way to reference a database and table name. Worse, MySQL
4106 will usually let you create a database with a dot, but then you cannot
4107 work with it, nor delete it.</p>
4113 <p>
4114 To use SQL Validator, you need PHP with
4120 module.
4121 </p>
4123 <p>
4129 usage.
4130 </p>
4132 <p>
4133 If you use the Validator, you should be aware that any
4135 submit will be stored anonymously (database/table/column names,
4136 strings, numbers replaced with generic values). The Mimer
4139 We utilize it as free SOAP service.
4140 </p>
4144 it, but MySQL says "BLOB column '...' used in key specification without
4147 <p> The right way to do this, is to create the column without any indexes,
4149 dialog. On this page, you will be able to choose your BLOB column, and
4150 set a size to the index, which is the condition to create an index on
4151 a BLOB column.</p>
4155 editing fields?</a></h4>
4157 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4158 with many editing fields (table structure changes, row editing, etc.).
4159 You can also have a look at the directive
4161 ('vertical') and see if this eases up editing for you.</p>
4165 WTF is this feature then useful for?</a></h4>
4167 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4168 on them. Otherwise you could just put a comment on the column. Because entering
4169 your own mimetype will cause serious syntax checking issues and validation,
4170 this introduces a high-risk false-user-input situation. Instead you have to
4171 initialize mimetypes using functions or empty mimetype definitions.<br />
4172 Plus, you have a whole overview of available mimetypes. Who knows all those
4173 mimetypes by heart so he/she can enter it at will?</p>
4177 can't I see any bookmarks below the query box? What is this variable for?
4178 </a></h4>
4180 <p> Any query you have executed can be stored as a bookmark on the page where the
4181 results are displayed. You will find a button labeled 'Bookmark this query'
4182 just at the end of the page.<br />
4183 As soon as you have stored a bookmark, it is related to the database you run
4184 the query on. You can now access a bookmark dropdown on each page, the query
4185 box appears on for that database.<br /><br />
4187 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4191 aware of that you HAVE to create a valid query, otherwise your query won't be
4192 even able to be stored in the database.<br />
4194 for your query will remain the way it is, but will be stripped of the /**/
4195 chars. So you can use:<br /><br />
4199 which will be expanded to<br /><br />
4203 in your query, where VARIABLE is the string you entered in the input box. If
4204 an empty string is provided, no replacements are made.<br /><br />
4206 A more complex example. Say you have stored this query:<br /><br />
4208 <br /><br />
4211 the full query will be:<br /><br />
4214 <br /><br />
4216 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4218 spaces inserted there
4219 will be later also inserted as spaces in your query and may lead to unexpected
4220 results especially when
4222 Your initial query which is going to be stored as a bookmark has to yield at
4223 least one result row so
4224 you can store the bookmark. You may have that to work around using well
4228 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4229 include exported table?</a></h4>
4231 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4232 document should look like following one (assuming you have table
4235 <pre>
4236 \documentclass{article} % or any class you want
4237 \usepackage{longtable} % for displaying table
4238 \begin{document} % start of document
4239 \include{table} % including exported table
4240 \end{document} % end of document
4241 </pre>
4245 access them.
4246 </a></h4>
4248 <p> You have one of these global privileges: CREATE
4249 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4250 enable users to see all the database names.
4253 So if your users do not need those privileges, you can remove them and their
4254 databases list will shorten.</p>
4258 possible values for a column, based on some foreign table?</a></h4>
4260 <p> You have to setup appropriate links between the tables, and also
4264 foreign table, a drop-down list of values will be available.
4265 You will see two lists of values, the first list containing the key
4266 and the display column, the second list containing the display column
4267 and the key. The reason for this is to be able to type the first
4268 letter of either the key or the display column.<br /><br />
4270 For 100 values or more, a distinct window will appear, to browse foreign
4271 key values and choose one. To change the default limit of 100, see
4272 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4276 automatically when entering Browse mode for a table?</a></h4>
4278 <p> Yes. If a bookmark has the same label as a table name and it's not a public bookmark, it will be executed.
4279 </p>
4284 <p> You can use
4286 which works out of the box.<br />
4287 Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel
4288 version 97 and newer was dropped.
4289 </p>
4293 what happens to my column comments stored in pmadb?</a></h4>
4295 <p> Automatic migration of a table's pmadb-style column comments to the native
4296 ones is done whenever you enter Structure page for this table.</p>
4301 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4302 <ul>
4305 later)</li>
4308 </ul>
4312 <ol>
4313 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4314 <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>
4315 <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>
4316 <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>
4317 </ol>
4322 <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>
4328 <p>
4329 In all places where phpMyAdmin accepts format strings, you can use
4332 expanded variables depend on a context (for example, if you haven't chosen a
4333 table, you can not get the table name), but the following variables can be used:
4334 </p>
4335 <dl>
4341 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4352 </dl>
4357 <p>
4358 By clicking on the button 'toggle scratchboard' on the page
4359 where you edit x/y coordinates of those elements you can activate a
4360 scratchboard where all your elements are placed. By clicking on an
4361 element, you can move them around in the pre-defined area and the x/y
4362 coordinates will get updated dynamically. Likewise, when entering a
4363 new position directly into the input field, the new position in the
4364 scratchboard changes after your cursor leaves the input field.
4365 </p>
4366 <p>
4367 You have to click on the 'OK'-button below the tables to save the new
4368 positions. If you want to place a new element, first add it to the
4369 table of elements and then you can drag the new element around.
4370 </p>
4371 <p>
4372 By changing the paper size and the orientation you can change the size
4373 of the scratchboard as well. You can do so by just changing the
4374 dropdown field below, and the scratchboard will resize automatically,
4375 without interfering with the current placement of the elements.
4376 </p>
4377 <p>
4378 If ever an element gets out of range you can either enlarge the paper
4379 size or click on the 'reset' button to place all elements below each
4380 other.
4381 </p>
4386 <p> Not every table can be put to the chart. Only tables with one, two or three columns can be visualised as a chart. Moreover the table must be in a special format for chart script to understand it. Currently supported formats can be found in the <a href="http://wiki.phpmyadmin.net/pma/Charts#Data_formats_for_query_results_chart">wiki</a>.</p>
4391 <p>
4392 An ESRI Shapefile is actually a set of several files, where .shp file contains
4393 geometry data and .dbf file contains data related to those geometry data.
4394 To read data from .dbf file you need to have PHP compiled with the dBase extension
4395 (--enable-dbase). Otherwise only geometry data will be imported.
4396 </p>
4399 <ul>
4400 <li>
4401 <p>
4402 Configure upload directory with
4404 .shp and .dbf files with the same filename and chose the .shp file from the import page.
4405 </p>
4406 </li>
4407 <li>
4408 <p>
4409 Create a Zip archive with .shp and .dbf files and import it. For this to work,
4412 </p>
4415 <pre>
4416 cd phpMyAdmin
4417 mkdir tmp
4418 chmod o+rwx tmp
4419 </pre>
4420 </li>
4421 </ul>
4429 <p>The display column is shown in pink. To set/unset a column as the display column, click the "Choose column to display" icon, then click on the appropriate column name.</p>
4434 <p> The Zoom search feature is an alternative to table search feature. It allows you to explore
4435 a table by representing its data in a scatter plot. You can locate this feature by selecting
4436 a table and clicking the 'Search' tab. One of the sub-tabs in the 'Table Search' page is
4437 'Zoom Search'. <br/><br/>
4441 for example, id and town_code. The id values will be represented on one axis and town_code
4442 values on the other axis. Each row will be represented as a point in a scatter plot based
4443 on its id and town_code. You can include two additional search criteria apart from the two
4444 fields to display.<br/><br/>
4446 You can choose which field should be displayed as label for each point. If a display
4449 You can also select the maximum number of rows you want to be displayed in the plot by
4450 specifing it in the 'Max rows to plot' field. Once you have decided over your criteria,
4451 click 'Go' to display the plot.<br/><br/>
4453 After the plot is generated, you can use the mousewheel to zoom in and out of the plot.
4454 In addition, panning feature is enabled to navigate through the plot. You can zoom-in to
4455 a certail level of detail and use panning to locate your area of interest. Clicking on a
4456 point opens a dialogue box, displaying field values of the data row represented by the point.
4457 You can edit the values if required and click on submit to issue an update query. Basic
4458 instructions on how to use can be viewed by clicking the 'How to use?' link located just above
4459 the plot.</p>
4466 <p> Our Bug Tracker is located at
4468 under the Bugs section.<br /><br />
4470 But please first discuss your bug with other users:<br />
4472 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4473 </p>
4477 existing language, where do I start?</a></h4>
4479 <p> Always use latest Git version of the po file to translate. You can optionally
4481 server</a> where you can also get the latest po files and merge them
4482 with your translations. For creating a new translation simply use
4486 to do this) or ask on the mailing list to add the translation to the web
4487 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4488 </p>
4489 <p>
4490 Please note that we try not to use HTML entities like &eacute; in
4491 the translations, since we define the right character set in the file.
4492 With HTML entities, the text on JavaScript messages would not
4493 display correctly.
4494 However there are some entities that need to be there: quotes,
4495 non-breakable spaces, ampersands, less than, greater than.
4496 </p>
4497 <p>
4498 You can then put your translations, as a zip file to avoid losing special
4499 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4500 </p>
4501 <p>
4502 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4503 list, because this is where we ask for translations of new messages.
4504 </p>
4506 <p>
4507 Documentation is being translated using po4a and gettext (see
4509 for existing translations). To start, checkout
4510 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4511 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4512 and translate it online. If your language is missing, just contact
4514 you prefer to directly translate the po files, please put updated ones into our
4515 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4516 </p>
4520 phpMyAdmin. How should I proceed?</a></h4>
4525 <tt>git clone
4526 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4527 </li>
4529 <li>generate patch with your changes:
4531 </li>
4534 tracker of the phpMyAdmin project</a>.
4535 </li>
4536 </ol>
4538 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Git">our wiki</a>.</p>
4540 <p> Write access to the repository is granted only to experienced developers who
4541 have already contributed something useful to phpMyAdmin.<br />
4547 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4549 <p> Please refer to
4550 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4551 </p>
4556 <p> If you use Apache web server, phpMyAdmin exports information about
4557 authentication to the Apache environment and it can be used in Apache logs.
4558 Currently there are two variables available:
4559 </p>
4560 <dl>
4562 <dd>User name of currently active user (he does not have to be logged
4563 in).</dd>
4570 </dl>
4571 <p>
4573 </p>
4574 <pre>
4577 </pre>
4578 <p>
4579 You can then use any log analyzing tools to detect possible break-in
4580 attempts.
4581 </p>
4587 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4588 It allows you to connect to local as well as remote servers. This requires you to enter
4589 server host name, username, password, port and the name of the database. Therefore you can
4590 now synchronize your databases placed on the same server or some remote server.
4591 </p>
4593 <p>
4594 This feature is helpful for developers who need to replicate their
4595 database’s structure as well as data. Moreover, this feature not only
4596 helps replication but also facilitates the user to keep his/her database
4597 in sync with another database. Other than the full database, certain
4598 tables of the databases can also be synchronized.
4599 </p>
4601 <p>
4602 You need to fill in the host name of the server, the username and
4603 password of an user account already there in MySQL. Port is by default
4604 populated with 3306 (MySQL default port). Then the name of the database
4605 should be mentioned at the end. All the information other than the port
4606 needs to be filled explicitly for the source as well as target servers.
4607 </p>
4609 <p>
4610 After successfully passing through the authentication phase, the source and
4611 target database table names will be displayed. It will be a tabular
4612 representation.
4613 </p>
4615 <p>
4616 On the left, are listed the source database table names. Some of the
4618 are only present in source database and they need to be added to the
4619 target database in order to synchronize the target database. The tables
4621 target database.
4622 </p>
4624 <p>
4625 On the right, are listed the target database table names. There are few
4627 means that these tables are to be created in target database in order to
4628 synchronize target database with source database. Some table names
4630 only present in target database and they will remain unchanged in the
4631 target database. The column in the middle shows the difference between
4632 the source and target corresponding tables.
4633 </p>
4635 <p>
4637 letters, indicating that either Structure or Data are not up to date. By
4638 clicking on them, they will turn grey, what means that they will be synchronized.
4639 </p>
4641 <!-- DEVELOPERS -->
4644 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4645 great features have been written by other people and you too can help to
4646 make phpMyAdmin a useful tool.</p>
4648 <p> If you're planning to contribute source, please read the following
4649 information:</p>
4655 it free from other code.<br />
4656 Commonly used functions should be added to
4659 <li>Obviously, you're free to use whatever coding style you want. But
4660 please try to keep your code as simple as possible: beginners are
4661 using phpMyAdmin as an example application.<br />
4662 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4663 compliant on one hand, they fit the
4666 coding standards</a>
4667 on the other hand. Please pay attention to this.</li>
4668 <li>Please enable showing PHP errors and warnings by the
4670 configuration directive.</li>
4671 <li>Please try to keep up the file-naming conventions. Table-related stuff
4674 <li>Please use gettext wrappers around all messages
4677 script. To use translated messages, call
4679 Gettext.</li>
4683 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4684 better debug and profile their code.<br />
4685 Please see the
4687 options for more information.<br />
4688 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4689 lost during its re-entry into Earth's atmosphere and in memory of the
4690 brave men and women who gave their lives for the people of Earth.</li>
4691 </ul>
4695 <pre>
4706 </pre>
4708 <p>
4709 This program is free software; you can redistribute it and/or modify
4710 it under the terms of the GNU General Public License version 2,
4711 as published by the Free Software Foundation.
4712 </p>
4714 <p>
4715 This program is distributed in the hope that it will be useful,
4716 but WITHOUT ANY WARRANTY; without even the implied warranty of
4717 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4718 GNU General Public License for more details.
4719 </p>
4721 <p>
4722 You should have received a copy of the GNU General Public License
4723 along with this program; if not, write to the Free Software
4725 </p>
4727 <!-- CREDITS -->
4732 <ul>
4735 <ul>
4738 </ul></li>
4741 <ul>
4746 </ul></li>
4749 <ul>
4754 </ul></li>
4757 <ul>
4759 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4760 generate XHTML1.0 and CSS2 compliant codes</li>
4763 </ul></li>
4766 <ul>
4774 </ul></li>
4777 <ul>
4782 </ul></li>
4785 <ul>
4788 </ul></li>
4791 <ul>
4793 </ul></li>
4796 <ul>
4799 </ul></li>
4802 <ul>
4806 </ul></li>
4809 <ul>
4812 </ul></li>
4815 <ul>
4822 </ul></li>
4825 <ul>
4829 </ul></li>
4832 <ul>
4838 </ul></li>
4841 (http://sf.net/projects/phpmysqlformgen/)
4842 <ul>
4844 </ul></li>
4847 <ul>
4849 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4854 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4858 </ul></li>
4861 <ul>
4863 </ul></li>
4866 <ul>
4868 </ul></li>
4871 <ul>
4873 </ul></li>
4876 <ul>
4877 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4878 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4879 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4880 </ul></li>
4883 <ul>
4885 </ul></li>
4888 <ul>
4890 </ul></li>
4893 <ul>
4895 </ul></li>
4898 <ul>
4901 </ul></li>
4903 <li>Nicola Asuni (Tecnick.com)
4904 <ul>
4907 </ul></li>
4910 <ul>
4913 </ul></li>
4916 <ul>
4918 </ul></li>
4921 <ul>
4924 </ul></li>
4926 <li>Ivan A Kirillov
4927 <ul>
4929 </ul></li>
4932 <ul>
4934 </ul></li>
4937 <ul>
4941 </ul></li>
4944 <ul>
4946 </ul></li>
4949 <ul>
4951 </ul></li>
4954 <ul>
4956 </ul></li>
4959 <ul>
4961 </ul></li>
4964 <ul>
4966 </ul></li>
4969 <ul>
4973 </ul></li>
4976 <ul>
4978 </ul></li>
4981 <ul>
4983 </ul></li>
4985 <li>Barrie Leslie
4986 <ul>
4988 </ul></li>
4991 <ul>
4993 </ul></li>
4996 <ul>
4999 </ul></li>
5001 </ul>
5003 <p>
5004 And also to the following people who have contributed minor changes,
5005 enhancements, bugfixes or support for a new language since version 2.1.0:
5006 </p>
5008 <p>
5009 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
5010 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
5011 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
5012 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
5014 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
5015 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
5016 Luís V., Martijn W. van der Lee,
5017 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
5019 </p>
5024 <p>
5025 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
5026 to create a web-based interface to MySQL using PHP3. Although I have not
5027 used any of his source-code, there are some concepts I've borrowed from
5028 him. phpMyAdmin was created because Peter told me he wasn't going to
5029 further develop his (great) tool.
5030 </p>
5031 <p>
5032 Thanks go to
5033 </p>
5034 <ul>
5036 code for the check when dropping a table or database. He also suggested
5037 that you should be able to specify the primary key on tbl_create.php3. To
5038 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
5039 well as a bug-report. Plus many smaller improvements.
5040 </li>
5042 were introduced in 1.3.0 (including quite significant ones like the
5043 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
5044 bug-fixes and help.
5045 </li>
5047 language-independent by outsourcing the strings to a separate file. He
5048 also contributed the French translation.
5049 </li>
5051 tbl_select.php3, a feature to display only some columns from a table.
5052 </li>
5054 functions in tbl_change.php3. He also added the
5056 </li>
5058 servers and is a regular contributor for bug-fixes.
5059 </li>
5061 features for 2.0.6.
5062 </li>
5063 </ul>
5064 <p>
5065 The following people have contributed minor changes, enhancements, bugfixes
5066 or support for a new language:
5067 </p>
5068 <p>
5069 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
5070 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
5071 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
5072 G. Wieggers.
5073 </p>
5074 <p>
5075 And thanks to everyone else who sent me email with suggestions, bug-reports
5076 and or just some feedback.
5077 </p>
5083 <ul>
5085 - the default name of Apache's directory-level configuration file.</li>
5089 - a software application that enables a user to display and interact with
5090 text, images, and other information typically located on a web page at a
5091 website on the World Wide Web.</li>
5093 - a free software/open source data compression algorithm and program
5094 developed by Julian Seward.</li>
5096 - an important World Wide Web technology that enables a client web browser
5097 to request data from a program executed on the Web server.</li>
5099 - a log or record of changes made to a project.</li>
5101 - a computer system that accesses a (remote) service on another computer
5102 by some kind of network.</li>
5104 - a set of data values of a particular simple type, one for each row of
5105 the table.</li>
5107 - a packet of information sent by a server to a World Wide Web browser
5108 and then sent back by the browser each time it accesses that server.</li>
5110 - Comma-separated values</li>
5113 - an organized collection of data.</li>
5116 - a PHP module that extends PHP with additional functionality.</li>
5118 - a list of commonly asked question and there answers.</li>
5120 - one part of divided data/columns.</li>
5122 - a column or group of columns in a database row that point to a key
5123 column or group of columns forming a key of another database row in some
5124 (usually different) table.</li>
5126 - the free PDF library</li>
5128 GD Graphics Library</a> - a library by Thomas Boutell and others for
5129 dynamically manipulating images.</li>
5132 - gzip is short for GNU zip, a GNU free software file compression
5133 program.</li>
5135 - any machine connected to a computer network, a node that has a hostname.</li>
5137 - the unique name by which a network attached device is known on a network.</li>
5139 (HyperText Transfer Protocol)</a>
5140 - the primary method used to transfer or convey information on the World
5141 Wide Web.</li>
5144 additional security measures.</li>
5145 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5146 - a set of Internet-based services for servers using Microsoft Windows.</li>
5148 - a feature that allows quick access to the rows in a table.</li>
5150 - a data-oriented protocol used by source and destination hosts for
5151 communicating data across a packet-switched internetwork.</li>
5153 - a unique number that devices use in order to identify and communicate
5154 with each other on a network utilizing the Internet Protocol standard.</li>
5156 (Internet Server Application Programming Interface)</a>
5157 - the API of Internet Information Services (IIS).</li>
5159 - a business or organization that offers users access to the Internet and related services.</li>
5161 - a most commonly used standard method of lossy compression for
5162 photographic images.</li>
5168 - line of personal computers is designed, developed, manufactured, and
5169 marketed by Apple Computer.</li>
5170 <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>
5171 - the operating system which is included with all currently shipping Apple
5172 Macintosh computers in the consumer and professional markets.</li>
5174 - a cryptographic library.</li>
5176 - the MCrypt PHP extension.</li>
5177 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5178 - an Internet Standard for the format of e-mail.</li>
5180 - some sort of extension for the Apache Webserver.</li>
5182 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5183 Management System (DBMS).</li>
5185 - the improved MySQL client PHP extension.</li>
5187 - the MySQL client PHP extension.</li>
5189 - open standard for office documents.</li>
5190 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5191 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5193 (Portable Document Format)</a>
5194 - a file format developed by Adobe Systems for representing two
5195 dimensional documents in a device independent and resolution independent
5196 format.</li>
5198 - the PHP Extension and Application Repository.</li>
5200 - the perl-compatible regular expression functions for PHP</li>
5202 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5203 programming language used mainly for developing server-side applications
5204 and dynamic web content, and more recently, a broader range of software
5205 applications.</li>
5207 - a connection through which data is sent and received.</li>
5209 - Request for Comments (RFC) documents are a series of memoranda
5210 encompassing new research, innovations, and methodologies applicable to
5211 Internet technologies.</li>
5215 - represents a single, implicitly structured data item in a table.</li>
5217 - a computer system that provides services to other computing
5218 systems over a network.</li>
5219 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5220 - handlers for different table types</li>
5222 - a form of inter-process communication.</li>
5224 Sockets Layer)</a>
5225 - a cryptographic protocol which provides secure communication on the Internet.</li>
5227 - a subroutine available to applications accessing a relational database system</li>
5229 - Structured Query Language</li>
5231 - a set of data elements (cells) that is organized, defined and stored as
5232 horizontal rows and vertical columns where each item can be uniquely
5233 identified by a label or key or by it?s position in relation to other items.</li>
5236 - a type of archive file format: the Tape ARchive format.</li>
5238 - one of the core protocols of the Internet protocol suite.</li>
5240 - a procedural code that is automatically executed in response to
5241 certain events on a particular table or view in a database</li>
5245 - a sequence of characters, conforming to a standardized format, that is
5246 used for referring to resources, such as documents and images on the
5247 Internet, by their location.</li>
5249 - A computer (program) that is responsible for accepting HTTP requests
5250 from clients and serving them Web pages.</li>
5252 - a W3C-recommended general-purpose markup language for creating
5253 special-purpose markup languages, capable of describing many different
5254 kinds of data.</li>
5256 - a popular data compression and archival format.</li>
5258 - an open-source, cross-platform data compression library by Jean-loup
5259 Gailly and Mark Adler.</li>
5260 </ul>
5261 </div>
5264 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5267 <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>
5268 </ul>
5270 </body>
5271 </html>