| blob | 5b3da22006bae0eab7cebe1e9b6723fd4ef3ed5f |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <head>
14 </head>
18 <h1>
20 3.5.0-dev
21 Documentation
22 </h1>
23 </div>
25 <!-- TOP MENU -->
34 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
39 </ul>
44 phpMyAdmin homepage</a></li>
46 SourceForge phpMyAdmin project page</a></li>
48 Official phpMyAdmin wiki</a></li>
49 <li>Local documents:
52 </ul>
53 </li>
54 </ul>
56 <!-- REQUIREMENTS -->
63 , the Standard PHP Library (SPL) extension and JSON support.
64 </li>
67 currently the default), you should install the mbstring and ctype
68 extensions.
69 </li>
70 <li>You need GD2 support in PHP to display inline
72 original aspect ratio</li>
78 load pages significantly slower.
79 </li>
82 <li>To support BLOB streaming, see PHP and MySQL requirements
85 </ul>
86 </li>
89 </ul>
91 <!-- INTRODUCTION -->
94 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
95 a single database. To accomplish the latter you'll need a properly set up
96 MySQL user who can read/write only the desired database. It's up to you to
97 look up the appropriate part in the MySQL manual.
98 </p>
103 <li>create, copy, drop, rename and alter databases, tables, columns and
104 indexes</li>
105 <li>maintenance server, databases and tables, with proposals on server
106 configuration</li>
107 <li>execute, edit and bookmark any
109 batch-queries</li>
112 </li>
119 OpenDocument Text and Spreadsheet,
121 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
122 </li>
123 <li>import data and MySQL structures from <abbr title="Microsoft Excel 97-2003 and Excel 2007">Microsoft Excel</abbr> and OpenDocument spreadsheets, as well as <abbr title="Extensible Markup Language">XML</abbr>, <abbr title="Comma Separated Values">CSV</abbr>, and <abbr title="Server Query Language">SQL</abbr> files</li>
127 <li>using Query-by-example (QBE), create complex queries automatically
128 connecting required tables</li>
130 your Database layout</li>
132 <li>transform stored data into any format using a set of predefined
133 functions, like displaying BLOB-data as image or download-link
134 </li>
140 <li>communicate in <a href="http://www.phpmyadmin.net/home_page/translations.php">62 different languages</a>
141 </li>
142 <li>synchronize two databases residing on the same as well as remote servers
144 </li>
146 </ul>
149 <p> Many people have difficulty
150 understanding the concept of user management with regards to phpMyAdmin. When
151 a user logs in to phpMyAdmin, that username and password are passed directly
152 to MySQL. phpMyAdmin does no account management on its own (other than
153 allowing one to manipulate the MySQL user account information); all users
154 must be valid MySQL users.</p>
163 <!-- INSTALLATION -->
171 </ol>
174 phpMyAdmin does not apply any special security methods to the MySQL database
175 server. It is still the system administrator's job to grant permissions on
177 be used for this.
178 </p>
186 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
187 before uploading them to your server, as PHP seems not to like
192 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
193 Downloads page. Some kits contain only the English messages,
194 others contain all languages in UTF-8 format (this should be fine
195 in most situations), others contain all
196 languages and all character sets. We'll assume you chose a kit whose
198 </li>
199 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
201 document root. If you don't have direct access to your document root,
202 put the files in a directory on your local machine, and, after step 4,
203 transfer the directory on your web server using, for example, ftp.</li>
204 <li>Ensure that all the scripts have the appropriate owner (if PHP is
205 running in safe mode, having some scripts with an owner different
206 from the owner of other scripts will be a
211 <li>Now you must configure your installation. There are two methods that
212 can be used. Traditionally, users have hand-edited a copy of
214 provided for those who prefer a graphical installation. Creating a
215 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
216 <ul><li>To manually create the file, simply use your text editor to
219 file) in the main (top-level) phpMyAdmin directory (the one
223 default value is okay for a particular setting, there is no
225 few directives to get going, a simple configuration may look
226 like this:
227 <pre>
228 <?php
229 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
231 $i=0;
232 $i++;
233 $cfg['Servers'][$i]['auth_type'] = 'cookie';
234 ?>
235 </pre>
236 Or, if you prefer to not be prompted every time you log in:
237 <pre>
238 <?php
240 $i=0;
241 $i++;
242 $cfg['Servers'][$i]['user'] = 'root';
243 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
244 $cfg['Servers'][$i]['auth_type'] = 'config';
245 ?>
246 </pre>
247 For a full explanation of possible configuration values, see the
253 directory. This is a security measure. On a Linux/Unix system you
254 can use the following commands:
255 <pre>
256 cd phpMyAdmin
257 mkdir config # create directory for saving
258 chmod o+rw config # give it world writable permissions
259 </pre>
260 And to edit an existing configuration, copy it over first:
261 <pre>
262 cp config.inc.php config/ # copy current configuration for editing
263 chmod o+w config/config.inc.php # give it world writable permissions
264 </pre>
265 On other platforms, simply create the folder and ensure that your
274 the webserver does not have the proper permissions you may see the
276 config/</tt> directory exists and has the proper permissions -
278 and upload (via FTP or some similar means) to the proper location.<br /><br />
280 Once the file has been saved, it must be moved out of the <tt>
281 config/</tt> directory and the permissions must be reset, again
282 as a security measure:
283 <pre>
284 mv config/config.inc.php . # move file to current directory
285 chmod o-rw config.inc.php # remove world read and write permissions
286 rm -rf config # remove not needed directory
287 </pre>
288 Now the file is ready to be used. You can choose to review or edit
289 the file with your favorite editor, if you prefer to set some
290 advanced options which the setup script does not provide.</li></ul></li>
291 <li>If you are using the
293 protect the phpMyAdmin installation directory because using
294 config does not require a user to
295 enter a password to access the phpMyAdmin installation. Use of an alternate
296 authentication method is recommended, for example with
304 in your browser. phpMyAdmin should now display a welcome screen
305 and your databases, or a login dialog if using
307 authentication mode.</li>
310 Apache you can use supplied .htaccess file in that folder, for other
311 webservers, you should configure this yourself. Such configuration
312 prevents from possible path exposure and cross side scripting
313 vulnerabilities that might happen to be found in that code.</li>
314 <li>
315 It is generally good idea to protect public phpMyAdmin installation
316 against access by robots as they usually can not do anything good
318 your webserver or limit access by web server configuration. You can
321 </li>
322 </ol>
326 <p> For a whole set of new features (bookmarks, comments,
328 tracking mechanism,
330 transformation, etc.) you need to create a set of special tables. Those
331 tables can be located in your own database, or in a central database for a
332 multi-user installation (this database would then be accessed by the
333 controluser, so no other user should have rights to it).</p>
344 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
345 that you may need special (administrator) privileges to create the database
346 and tables, and that the script may need some tuning, depending on the
347 database name.</p>
352 section</a>. You will also need to have a controluser with the proper rights
359 unpacked one. Configuration files from old versions may
360 require some tweaking as some options have been changed or removed; in
362 so you better remove it from your file and just use the default one.
364 statement that you might find near the end of your configuration file.</p>
368 is version-specific.</p>
371 version 5.x or newer and if you use the phpMyAdmin configuration storage,
372 you should run the SQL script found in
379 where you want to give users access to their own database and don't want
380 them to play around with others.<br />
381 Nevertheless be aware that MS Internet Explorer seems to be really buggy
385 that your user/password pair are not in clear in the configuration file.
386 </li>
389 authentication modes are more secure: the MySQL login information does
390 not need to be set in the phpMyAdmin configuration file (except possibly
392 However, keep in mind that the password travels in plain text, unless
393 you are using the HTTPS protocol.<br />
394 In cookie mode, the password is stored, encrypted with the blowfish
395 algorithm, in a temporary cookie.</li>
407 file under the
409 $cfg['Servers'][$i]['controluser']</a></tt> and
414 only an example: use something else in your file!</b> Input these
415 statements from the phpMyAdmin SQL Query window or mysql command–line
416 client.<br />
418 if it's not the same as the MySQL server's one.
420 <pre>
421 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
422 GRANT SELECT (
423 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
424 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
425 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
426 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
427 Execute_priv, Repl_slave_priv, Repl_client_priv
428 ) ON mysql.user TO 'pma'@'localhost';
429 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
430 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
431 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
432 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
434 If you want to use the many new relation and bookmark features:
436 <pre>
438 </pre>
441 configuration storage</a> be set up).
442 <br /></li>
445 on a set of particular databases. Normally you shouldn't give global
446 privileges to an ordinary user, unless you understand the impact of those
447 privileges (for example, you are creating a superuser).<br />
451 <pre>
452 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
453 </pre>
455 What the user may now do is controlled entirely by the MySQL user
456 management system.<br />
458 authentication mode, you don't need to fill the user/password fields
460 array.</li>
461 </ul>
466 method and allows you to log in as any valid MySQL user.</li>
467 <li>Is supported with most PHP configurations. For
480 mode.</li>
481 </ul>
485 <ul><li>You can use this method as a replacement for the
487 (for example, if you're running
489 <li>Obviously, the user must enable cookies in the browser, but this is
490 now a requirement for all authentication modes.</li>
491 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
492 with the same username.</li>
493 <li>If you want to log in to arbitrary server see
498 not required.</li>
499 </ul>
503 <ul><li>This mode is a convenient way of using credentials from another
504 application to authenticate to phpMyAdmin.</li>
505 <li>The other application has to store login information into
506 session data.</li>
508 section.</li>
509 </ul>
512 <ul><li>This mode is the less secure one because it requires you to fill the
514 $cfg['Servers'][$i]['user']</a> and
516 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
517 can read your config.inc.php can discover your username and password).
518 <br />
525 is an entry explaining how to protect your configuration file.</li>
526 <li>For additional security in this mode, you may wish to consider the Host
527 authentication
529 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
531 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
532 directives.</li>
533 <li>Unlike cookie and http, does not require a user to log in when first
534 loading the phpMyAdmin site. This is by design but could allow any
535 user to access your installation. Use of some restriction method is
537 HTTP-AUTH directive or disallowing incoming HTTP requests at
538 one’s router or firewall will suffice (both of which
539 are beyond the scope of this manual but easily searchable with Google).</li>
540 </ul>
542 <p>
543 The Swekey is a low cost authentication USB key that can be used in
544 web applications.<br /><br />
545 When Swekey authentication is activated, phpMyAdmin requires the
546 users's Swekey to be plugged before entering the login page (currently
547 supported for cookie authentication mode only). Swekey Authentication is
548 disabled by default.<br /><br />
550 </p>
551 <pre>
552 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
553 </pre>
554 <p>
556 each user with their Swekey Id. It is important to place this file outside
557 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
559 users' information.<br /><br />
560 If you want to purchase a Swekey please visit
562 since this link provides funding for phpMyAdmin.
563 </p>
564 <!-- CONFIGURATION -->
568 users:</span> PHP does not seem to like
572 before saving a script you have modified.</p>
577 section to create one. This file only needs to contain the parameters you want to
578 change from their corresponding default value in
581 <p> The parameters which relate to design (like colors) are placed in
584 your site specific code to be included on start and end of each page.</p>
588 (with full path) to your phpMyAdmin installation's directory.
591 some web servers are case–sensitive.
594 Starting with version 2.3.0, it is advisable to try leaving this
595 blank. In most cases phpMyAdmin automatically detects the proper
596 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
597 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
598 A good test is to browse a table, edit a row and save it. There should
599 be an error message if phpMyAdmin is having trouble auto–detecting
600 the correct value. If you get an error that this must be set or if
601 the autodetect code fails to detect your path, please post a bug
602 report on our bug tracker so we can improve the code.</dd>
606 with master / foreign – tables (see
608 <br />
609 If you tried to set this up and it does not work for you, have a look on
611 use it. You will find a link that will analyze why those features have
612 been disabled.<br />
613 If you do not want to use those features set this variable to
617 <dd>A warning is displayed on the main page if Suhosin is detected.
619 from appearing.</dd>
622 <dd>Disable the default warning that is displayed if mcrypt is missing for
623 cookie authentication.
625 from appearing.</dd>
632 domain to call phpMyAdmin inside a frame, and is a potential security
633 hole allowing cross-frame scripting attacks.</dd>
637 algorithm to encrypt the password.<br />
639 passphrase of your choice. It will be used internally by the blowfish
640 algorithm: you won’t be prompted for this passphrase. There is
641 no maximum length for this secret.<br /><br />
643 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
644 makes a bit weaker security as this generated secret is stored in
645 session and furthermore it makes impossible to recall user name from
646 cookie.</dd>
650 MySQL servers. Therefore, a
652 been added which contains the login information for the different servers.
653 The first
655 contains the hostname of the first server, the second
657 the hostname of the second server, etc. In
659 server definition, however you can put as many as you need in
661 have to define all settings, just those you need to change).</dd>
665 $i-th MySQL-server. E.g. localhost.</dd>
670 ignores this port number and connects with the socket, so if you want
671 to connect to a port different from the default port, use
674 </dd>
678 To determine the correct socket, check your MySQL configuration or, using the
680 Among the resulting information displayed will be the socket used.</dd>
683 <dd>Whether to enable SSL for connection to MySQL server.
684 </dd>
687 <dd>What type connection to use with the MySQL server. Your options are
689 is nearly guaranteed to be available on all MySQL servers, while
690 sockets are not supported on some platforms.<br /><br />
692 To use the socket mode, your MySQL server must be on the same machine
693 as the Web server.</dd>
696 <dd>What php MySQL extension to use for the connection. Valid options are:
697 <br /><br />
700 The classic MySQL extension. This is the recommended and default
701 method at this time.<br /><br />
704 The improved MySQL extension. This extension became available
705 with php 5.0.0 and is the recommended way to connect to a server
709 <dd>Whether to use a compressed protocol for the MySQL server connection
710 or not (experimental).<br />
716 </dt>
718 all relational features (see
720 and, for a MySQL server running with
723 authentication mode).<br /><br />
726 cookie authentication modes (or 'config'
727 authentication mode since phpMyAdmin 2.2.1), you need to supply the
732 This account is used to check what databases the user will see at
733 login.<br />
737 In phpMyAdmin versions before 2.2.5, those were called
741 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
742 <dd>Whether config or cookie or
744 should be used for this server.
746 is the plain old way: username and password are stored in
748 <li>'cookie' authentication mode
750 2.2.3 allows you to log in as any valid MySQL user with the
751 help of cookies. Username and password are stored in
752 cookies during the session and password is deleted when it
753 ends. This can also allow you to log in in arbitrary server if
754 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
755 </li>
756 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
757 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
758 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
759 <li>'signon' authentication mode
761 as introduced in 2.10.0 allows you to log in from prepared PHP
762 session data. This is useful for implementing single signon
763 from another application. Sample way how to seed session is in
765 alternative example using OpenID -
771 </ul>
774 for more information.
775 </dd>
777 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
778 </dt>
779 <dd>
780 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
781 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
782 specified in your configuration, a string combined of "phpMyAdmin " and either
785 </dd>
787 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
788 </dt>
789 <dd>
791 names for hardware authentication. Leave empty to deactivate this feature.
792 </dd>
796 </dt>
797 <dd>
798 When using auth_type = 'config', this is the user/password-pair
799 which phpMyAdmin will use to connect to the
800 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
801 cookie authentication is used and should be empty.</dd>
803 <span
805 </dt>
806 <dd>
807 Allow attempt to log in without password when a login with password
808 fails. This can be used together with http authentication, when
809 authentication is done some other way and phpMyAdmin gets user name
810 from auth and uses empty password for connecting to MySQL. Password
811 login is still tried first, but as fallback, no password method is
812 tried.</dd>
815 </dt>
816 <dd>
817 If set to a (an array of) database name(s), only this (these) database(s)
818 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
819 database(s) name(s) may contain MySQL wildcards characters
823 This setting is an efficient way to lower the server load since the
824 latter does not need to send MySQL requests to build the available
826 privileges rules of the MySQL database server</span>. If set, it just
827 means only these databases will be displayed but
829 <br /><br />
831 An example of using more that one database:
833 <br /><br />
835 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
836 databases in the left frame, so that you can individually arrange your databases.<br />
837 If you want to have certain databases at the top, but don't care about the others, you do not
838 need to specify all other databases. Use:
840 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
841 order.</dd>
844 </dt>
845 <dd>Regular expression for hiding some databases from unprivileged users.
846 This only hides them
847 from listing, but a user is still able to access them (using, for example,
848 the SQL query area). To limit access, use the MySQL privilege system.
849 <br /><br />
854 More information on regular expressions can be found in the
856 PCRE pattern syntax</a> portion of the PHP reference manual.
857 </dd>
860 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
861 this string will be displayed instead of the hostname in the pull-down
862 menu on the main page. This can be useful if you want to show only
863 certain databases on your system, for example. For HTTP auth, all
864 non-US-ASCII characters will be stripped.</dd>
868 </dt>
869 <dd>The name of the database containing the phpMyAdmin configuration storage.
870 <br /><br />
873 section in this document to see the benefits of this feature,
874 and for a quick way of creating this database and the needed tables.
875 <br /><br />
877 If you are the only user of this phpMyAdmin installation, you can
878 use your current database to store those special tables; in this
879 case, just put your current database name in
881 set this parameter to the name of your central database containing
882 the phpMyAdmin configuration storage.</dd>
886 </dt>
888 useful for queries you often run.<br /><br />
890 To allow the usage of this functionality:
892 <li>enter the table name in
894 </ul>
895 </dd>
899 </dt>
901 which column is a key in another table (a foreign key). phpMyAdmin
902 currently uses this to
903 <ul><li>make clickable, when you browse the master table, the data values
904 that point to the foreign table;</li>
906 when browsing the master table, if you move the mouse to a column
907 containing a foreign key (use also the 'table_info' table);<br />
910 <li>in edit/insert mode, display a drop-down list of possible foreign
914 <li>display links on the table properties page, to check referential
915 integrity (display missing foreign keys) for each described key;
916 </li>
920 schema of your database (also uses the table_coords table).</li>
921 </ul>
923 The keys can be numeric or character.<br /><br />
925 To allow the usage of this functionality:
928 configuration storage</li>
929 <li>put the relation table name in
931 <li>now as normal user open phpMyAdmin and for each one of your
932 tables where you want to use this feature, click
934 columns.
935 </li>
936 </ul>
940 future development of the cross-db relations.
941 </dd>
945 </dt>
946 <dd>
947 Since release 2.3.0 you can describe, in a special 'table_info'
948 table, which column is to be displayed as a tool-tip when moving the
949 cursor over the corresponding key.<br />
950 This configuration variable will hold the name of this special
951 table. To allow the usage of this functionality:
953 <li>put the table name in
955 'pma_table_info')</li>
956 <li>then for each table where you want to use this feature,
958 to choose the column.</li>
959 </ul>
961 </dd>
965 </dt>
968 the relations between your tables. To do this it needs two tables
973 schema output).<br /><br />
977 To allow the usage of this functionality:
980 <li>put the correct table names in
983 </ul>
986 </dd>
990 </dt>
992 Since release 2.3.0 you can store comments to describe each column for
994 <br /><br />
996 Starting with release 2.5.0, comments are consequently used on the table
997 property pages and table browse view, showing up as tool-tips above the
998 column name (properties page) or embedded within the header of table in
999 browse view. They can also be shown in a table dump. Please see the
1000 relevant configuration directives later on.<br /><br />
1002 Also new in release 2.5.0 is a MIME-transformation system which is also
1004 Transformations</a> for further information. To use the
1005 MIME-transformation system, your column_info table has to have the three
1006 new columns 'mimetype', 'transformation', 'transformation_options'.
1007 <br /><br />
1009 To allow the usage of this functionality:
1011 <li>put the table name in
1013 'pma_column_info')</li>
1016 <pre>
1017 ALTER TABLE `pma_column_comments`
1018 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1019 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1020 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1021 </pre>
1024 renamed from<br />
1027 </ul>
1028 </dd>
1032 </dt>
1035 all queries you entered manually into the phpMyAdmin interface. If you
1036 don't want to use a table-based history, you can use the JavaScript-based
1037 history. Using that, all your history items are deleted when closing the
1038 window.<br /><br />
1040 Using
1042 you can specify an amount of history items you want to have on hold. On
1043 every login, this list gets cut to the maximum amount.<br /><br />
1045 The query history is only available if JavaScript is enabled in your
1046 browser.<br /><br />
1048 To allow the usage of this functionality:
1052 (e.g. 'pma_history')
1053 </li>
1054 </ul>
1055 </dd>
1059 </dt>
1060 <dd>
1061 Since release 3.3.x a tracking mechanism is available.
1063 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1064 and data definition statements. After enabling it you can create versions of tables.
1065 <br/><br/>
1066 The creation of a version has two effects:
1068 <ul>
1070 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1071 </ul>
1073 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1074 For the report you can use filters, for example you can get a list of statements within a date range.
1075 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1076 In addition you can export the (filtered) report to a file or to a temporary database.
1077 <br/><br/>
1079 To allow the usage of this functionality:
1081 <ul>
1084 </ul>
1085 </dd>
1088 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1089 </dt>
1090 <dd>
1091 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1092 <br/><br/>
1093 If this is set to true and you create a table or view with
1095 <ul>
1098 </ul>
1100 and no version exists for it, the mechanism will
1101 create a version for you automatically.
1102 </dd>
1105 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1106 </dt>
1107 <dd>
1108 Defines the list of statements the auto-creation uses for new versions. Default value is
1109 <br/>
1111 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1112 CREATE INDEX,DROP INDEX,
1113 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1114 CREATE VIEW,ALTER VIEW,DROP VIEW,
1115 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1116 </dd>
1119 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1120 </dt>
1121 <dd>
1122 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1123 <br/><br/>
1124 </dd>
1128 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1129 </dt>
1130 <dd>
1131 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1132 <br/><br/>
1133 </dd>
1136 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1137 </dt>
1138 <dd>
1139 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1140 <br/><br/>
1141 </dd>
1145 </dt>
1146 <dd>
1147 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1148 and store them in the database.
1149 <br /><br />
1152 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1153 or, it is is unavailable, until the end of session.
1154 <br /><br />
1156 To allow the usage of this functionality:
1158 <ul>
1160 configuration storage</li>
1162 </ul>
1163 </dd>
1167 </dt>
1169 to visually manage the relations.
1170 <br /><br />
1172 To allow the usage of this functionality:
1175 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1176 </li>
1177 </ul>
1178 </dd>
1181 </dt>
1183 column_info table got enhanced with three new columns. If the above variable
1185 latest table structure available. If not, it will emit a warning to the
1186 superuser.<br /><br />
1188 You can disable this checking behavior by setting the variable to false,
1189 which should offer a performance increase.<br /><br />
1191 Recommended to set to FALSE, when you are sure, your table structure is
1192 up to date.</dd>
1194 boolean</dt>
1195 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1196 </dd>
1198 boolean</dt>
1199 <dd>Whether to allow logins without a password. The default
1201 to a MySQL server with was left with an empty password for root or
1202 on which an anonymous (blank) user is defined.
1203 </dd>
1206 </dt>
1208 authorization is disabled.<br /><br />
1211 all deny rules followed by allow rules. Access is allowed by default. Any
1212 client which does not match a Deny command or does match an Allow command
1213 will be allowed access to the server. <br /><br />
1216 applies all allow rules followed by deny rules. Access is denied by
1217 default. Any client which does not match an Allow directive or does
1218 match a Deny directive will be denied access to the server.<br /><br />
1220 If your rule order is set to 'explicit', authorization is
1221 performed in a similar fashion to rule order 'deny,allow', with the
1225 and was available in Apache by specifying allow and deny rules without
1226 setting any order.<br /><br />
1228 Please also see <a
1230 address behind proxies.
1231 </dd>
1233 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1234 </dt>
1235 <dd>The general format for the rules is as such:
1237 <pre>
1239 </pre>
1244 well (please note that those containing SERVER_ADDRESS might not be
1245 available on all webservers):
1246 <pre>
1252 </pre>
1254 Having an empty rule list is equivalent to either using
1260 following work:<br />
1262 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1263 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1264 But the following does not work:<br />
1267 Also IPv6 addresses are not supported.
1268 </dd>
1270 <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.
1271 </dd>
1272 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1274 DATABASES</tt> command used to fetch the name of available databases will
1275 probably be too slow, so it can be replaced by faster commands (see
1277 </dd>
1279 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1280 </dd>
1281 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1282 <dd>Name of session which will be used for signon authentication method.
1284 this is session which phpMyAdmin uses internally.
1285 </dd>
1287 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1288 </dd>
1290 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1291 </dd>
1294 <dd>If you have more than one server configured, you can set
1296 that server when phpMyAdmin is started, or set it to 0 to be given a
1297 list of servers without logging in.<br />
1299 MUST be set to that server.</dd>
1302 <dd>Defines whether to refresh only parts of certain pages using Ajax
1303 techniques. Applies only where a non-Ajax behavior is possible;
1304 for example, the Designer feature is Ajax-only so this directive
1305 does not apply to it.</dd>
1308 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1309 page.</dd>
1312 <dd>The maximum number of database names to be displayed in the
1313 navigation frame and the database list.</dd>
1316 <dd>The maximum number of table names to be displayed in the
1317 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1318 when in Light mode.</dd>
1321 <dd>The maximum number of characters when a SQL query is displayed. The
1322 default limit of 1000 should be correct to avoid the display of tons
1323 of hexadecimal codes that represent BLOBs, but some users have real
1324 SQL queries that are longer than 1000 characters. Also, if a query's
1325 length exceeds this limit, this query is not saved in the history.</dd>
1328 <dd>Defines whether to use GZip output buffering for increased
1330 Set to true/false for enabling/disabling. When set to 'auto' (string),
1331 phpMyAdmin tries to enable output buffering and will automatically disable
1332 it if your browser has some problems with buffering. IE6 with a certain patch
1333 is known to cause data corruption when having enabled buffering.</dd>
1336 <dd>Whether persistent connections should be used or not (mysql_connect or
1337 mysql_pconnect).</dd>
1343 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1344 to zero, no time limit is imposed.<br />
1345 This setting is used while importing/exporting dump files and in the
1346 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1353 <dd>Set the number of bytes a script is allowed to allocate. If set
1354 to zero, no limit is imposed.<br />
1355 This setting is used while importing/exporting dump files and at some
1356 other places in phpMyAdmin so you definitely don't want to put here
1357 a too low value. It has no effect when PHP is running in safe mode.<br />
1358 You can also use any string as in php.ini, eg. '16M'. Ensure
1362 <dd>Mark used tables and make it possible to show databases with locked
1367 generated by phpMyAdmin should be displayed or not.</dd>
1370 <dd>Defines whether normal users (non-administrator) are allowed to
1371 delete their own database or not. If set as FALSE, the link "Drop
1373 mydatabase" will be rejected. Quite practical for
1375 customers.<br />
1376 Please note that this limitation of SQL queries is not as strict as
1377 when using MySQL privileges. This is due to nature of SQL queries
1378 which might be quite complicated. So this choice should be viewed as
1379 help to avoid accidental dropping rather than strict privilege
1380 limitation.</dd>
1384 displayed when you're about to lose data.</dd>
1387 <dd>Define whether the previous login should be recalled or not in cookie
1388 authentication mode.<br /><br />
1390 This is automatically disabled if you do not have configured
1392 </dd>
1395 <dd>Define how long is login cookie valid. Please note that php
1396 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1397 might limit session validity and if session is lost, login cookie is
1399 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1403 means that it will be kept for existing session. This is recommended
1404 for not trusted environments.</dd>
1407 <dd>If enabled (default), logout deletes cookies for all servers,
1408 otherwise only for current one. Setting this to false makes it easy to
1409 forget to log out from other server, when you are using more of
1410 them.</dd>
1416 <dd>Define whether phpMyAdmin will continue executing a multi-query
1417 statement if one of the queries fails. Default is to abort execution.</dd>
1420 <dd>Define whether phpMyAdmin will output the results of each query of a
1421 multi-query statement embedded into the
1426 <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.
1427 <br /><br />
1430 MySQL servers behind the firewall where your
1432 </dd>
1441 <dd>Defines whether to use a select-based menu and display only the current
1442 tables in the left frame (smaller page). Only in Non-Lightmode you can
1443 use the feature to display nested folders using
1445 </dd>
1448 <dd>In light mode, defines whether to display the names of databases (in the
1449 selector) using a tree, see also
1451 </dd>
1454 string or array</dt>
1455 <dd>The string used to separate the parts of the database name when showing
1456 them in a tree. Alternatively you can specify more strings in an array
1457 and all of them will be used as a separator.</dd>
1460 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1461 This means if you have tables like 'first__second__third' this will be
1463 If set to FALSE or empty, the feature is disabled. NOTE: You should
1464 not use this separator at the beginning or end of a
1465 table name or multiple times after another without any other
1466 characters in between.</dd>
1469 <dd>Defines how many sublevels should be displayed when splitting
1470 up tables by the above separator.</dd>
1473 <dd>Defines whether to display table comment as tool-tip in left frame or
1474 not.</dd>
1477 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1478 comment and the real name. That means that if you have a table called
1479 'user0001' and add the comment 'MyName' on it, you will see the name
1480 'MyName' used consequently in the left frame and the tool-tip shows
1481 the real name of the DB.</dd>
1484 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1486 When setting this to 'nested', the Alias of the Tablename is only used
1487 to split/nest the tables according to the
1489 directive. So only the folder is called like the Alias, the tablename itself
1490 stays the real tablename.</dd>
1493 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1496 <dd>Enter URL where logo in the navigation frame will point to.
1497 For use especially with self made theme which changes this.
1506 integer</dt>
1507 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1508 list of tables in the left frame.
1513 <dd>Defines whether or not to display a server choice at the top of the left frame.
1514 Defaults to FALSE.</dd>
1516 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1517 Defaults to FALSE (drop-down).</dd>
1519 <dd>Defines whether to display database choice in light navigation frame as links
1520 instead of in a drop-down. Defaults to 'auto' - on main page list is
1521 shown, when database is selected, only drop down is displayed.</dd>
1524 <dd>Defines the tab displayed by default when clicking the small
1525 icon next to each table name in the navigation panel. Possible
1531 <dd>Defines whether or not to display space usage and statistics about databases
1532 and tables.<br />
1533 Note that statistics requires at least MySQL 3.23.3 and that, at this
1534 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1537 <dd>Defines whether to display detailed server information on main page.
1538 You can additionally hide more information by using
1540 </dd>
1545 </dt>
1548 not at the starting main (right) frame. This setting
1549 does not check MySQL commands entered directly.<br /><br />
1551 Please note that to block the usage of phpinfo() in scripts, you
1558 hard coded password value in the configuration file, end users can't
1559 be allowed to change their passwords.</dd>
1562 <dd>Defines whether to suggest a database name on the
1566 <dd>Defines whether navigation bar buttons and the right panel top menu
1567 contain text or symbols only. A value of TRUE displays icons, FALSE
1568 displays text and 'both' displays both icons and text.</dd>
1571 <dd>Defines whether a user should be displayed a
1575 <dd>Number of rows displayed when browsing a result set. If the result set
1582 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1586 option is ticked by default.</dd>
1590 from editing when browsing a table's content. Valid values are:
1595 </ul>
1596 </dd>
1599 <dd>Defines whether or not MySQL functions fields should be initially
1600 displayed in edit/insert mode. Since version 2.10, the user can
1601 toggle this setting from the interface.
1602 </dd>
1605 <dd>Defines whether or not type fields should be initially
1606 displayed in edit/insert mode. The user can
1607 toggle this setting from the interface.
1608 </dd>
1611 <dd>Defines which type of editing controls should be used for CHAR and
1612 VARCHAR columns. Possible values are:
1613 <ul><li>input - this allows to limit size of text to size of columns in
1614 MySQL, but has problems with newlines in columns</li>
1615 <li>textarea - no problems with newlines in columns, but also no
1616 length limitations</li>
1617 </ul>
1618 Default is old behavior so input.</dd>
1624 <dd>If there are fewer items than this in the set of foreign keys, then a
1625 drop-down box of foreign keys is presented, in the style described by the
1627 setting.</dd>
1630 <dd>For the foreign key drop-down fields, there are several methods of
1631 display, offering both the key and value data. The contents of the
1632 array should be one or both of the following strings:
1638 </dt>
1639 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1640 creating a dump file</dd>
1643 </dt>
1644 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1645 compressed exports. This doesn't affect smaller dumps and allows users to
1646 create larger dumps that won't otherwise fit in memory due to php
1647 memory limit. Produced files contain more GZip/BZip2 headers, but all
1648 normal programs handle this correctly.</dd>
1652 mainframe.</dd>
1656 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1661 <dd>How many columns will be utilized to display the tables on the
1662 database property view? Default is 1 column. When setting this to a
1663 value larger than 1, the type of the database will be omitted for more
1664 display space.</dd>
1668 <dd>Defines the tab displayed by default on server view. Possible
1675 <dd>Defines the tab displayed by default on database view. Possible
1680 <dd>Defines the tab displayed by default on table view. Possible
1687 points to the MySQL documentation (type depends
1688 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1689 generated.<br />
1691 for more information about MySQL manuals and their types.</dd>
1694 <dd>Type of MySQL documentation:
1700 </ul>
1701 </dd>
1704 <dd>Defines the default language to use, if not browser-defined or
1705 user-defined.<br />
1706 The corresponding language file needs to be in
1708 </dd>
1711 <dd>Defines the default connection collation to use, if not
1712 user-defined.<br />
1718 The corresponding language file needs to be in
1720 </dd>
1723 <dd>Limit list of available languages to those matching the given regular
1724 expression. For example if you want only Czech and English, you should
1728 <dd>You can select here which functions will be used for character set
1729 conversion. Possible values are:
1730 <ul><li>auto - automatically use available one (first is tested
1731 iconv, then recode)</li>
1735 </ul>
1736 Default is auto.</dd>
1737 <dd>
1738 Enabled charset conversion activates a pull-down menu
1739 in the Export and Import pages, to choose the character set when
1740 exporting a file. The default value in this menu comes from
1742 </dd>
1745 <dd>Specify some parameters for iconv used in charset conversion. See
1748 used, so that invalid characters will be transliterated.</dd>
1751 <dd>Available character sets for MySQL conversion. You can add your own (any of
1752 supported by recode/iconv) or remove these which you don't use.
1753 Character sets will be shown in same order as here listed, so if you
1754 frequently use some of these move them to the top.</dd>
1759 default empty, you need to fill in some trusted proxy servers if you
1760 want to use rules for IP addresses behind proxy.<br /><br />
1762 The following example specifies that phpMyAdmin should trust a
1764 <pre>
1765 $cfg['TrustedProxies'] =
1767 </pre>
1768 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1769 client's IP address as usual.
1770 </dd>
1774 MIME transformations.<br />
1775 Possible values are:
1776 <ul><li>auto - automatically detect, this is a bit expensive
1778 according to your server real possibilities</li>
1781 </ul>
1782 Default is auto.
1783 </dd>
1786 <dd>
1787 We normally check the permissions on the configuration file to ensure
1788 it's not world writable. However, phpMyAdmin could be installed on
1789 a NTFS filesystem mounted on a non-Windows server, in which case the
1790 permissions seems wrong but in fact cannot be detected. In this case
1792 </dd>
1795 <dd>
1796 Limit for length of URL in links. When length would be above this limit, it
1797 is replaced by form with button.
1798 This is required as some web servers (IIS) have problems with long URLs.
1800 </dd>
1804 </dd>
1806 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1808 </dt>
1809 <dd>The background styles used for both the frames.
1812 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1814 <dd>The style used for the pointer in the navi frame.
1823 </dd>
1827 <dd>The style used for table headers. See
1832 </dd>
1836 </dd>
1838 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1840 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1842 </dt>
1844 The former feature highlights the row over which your mouse is passing
1845 and the latter lets you visually mark/unmark rows by clicking on
1846 them. Highlighting / marking a column is done by hovering over /
1847 clicking the column's header (outside of the text).<br />
1852 <dd>You put here a valid CSS font family value, for example
1857 <dd>You put here a valid CSS font family value, for example
1871 </dt>
1873 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1875 The Char* values are used for CHAR and VARCHAR editing (if configured
1879 </dt>
1883 </dt>
1884 <dd>Defines if the whole textarea of the query box will be selected on
1885 click.</dd>
1888 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1889 Can be turned off by a toggle button on the browse page.</dd>
1893 </dt>
1894 <dd>Defines the place where table row links (Edit, Inline edit, Copy,
1895 Delete) would be put when
1896 tables contents are displayed (you may have them displayed both at the
1897 left and at the right).
1903 Define which one is displayed by default. The first mode displays each
1904 row on a horizontal line, the second rotates the headers by 90
1905 degrees, so you can use descriptive headers even though columns only
1906 contain small values and still print them out. The vertical mode sorts
1907 each row on a vertical lineup.
1908 </dd>
1911 <dd>
1912 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1913 'css' the rotation of the header for horizontalflipped is done via
1914 CSS. The CSS transformation currently works only in Internet
1915 Explorer.If set to 'fake' PHP does the transformation for you, but of
1916 course this does not look as good as CSS. The 'auto' option enables
1917 CSS transformation when browser supports it and use PHP based one
1918 otherwise.
1919 </dd>
1923 string or integer</dt>
1924 <dd>When editing/creating new columns in a table all fields normally get
1925 lined up one field a line. (default: 'horizontal'). If you set this to
1926 'vertical' you can have each field lined up vertically beneath each
1927 other. You can save up a lot of place on the horizontal direction and
1928 no longer have to scroll. If you set this to integer, editing of fewer
1929 columns will appear in 'vertical' mode, while editing of more columns
1930 still in 'horizontal' mode. This way you can still effectively edit
1931 large number of columns, while having full view on few of them.</dd>
1935 </dt>
1937 display of column comments in Browse or Property display. In browse
1938 mode, the comments are shown inside the header. In property mode,
1939 comments are displayed using a CSS-formatted dashed-line below the
1940 name of the column. The comment is shown as a tool-tip for that column.
1941 </dd>
1953 <dd>Whether to display a link to validate a query in any SQL Query box.
1960 <dd>
1961 The name of the directory where
1963 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1964 are available under a drop-down box when you click the database or
1965 table name, then the Import tab.
1966 <br /><br />
1968 If you want different directory for each user, %u will be replaced
1969 with username.<br /><br />
1973 compressed formats is enabled).<br /><br />
1975 This feature is useful when your file is too big to be uploaded via
1977 uploads are disabled in PHP.<br /><br />
1979 Please note that if PHP is running in safe mode, this directory must
1980 be owned by the same user as the owner of the phpMyAdmin scripts.
1981 <br /><br />
1985 alternatives.
1986 </dd>
1989 <dd>
1990 The name of the directory where dumps can be saved.<br /><br />
1992 If you want different directory for each user, %u will be replaced
1993 with username.<br /><br />
1995 Please note that the directory must exist and has to be writable for
1996 the user running webserver.<br /><br />
1998 Please note that if PHP is running in safe mode, this directory must
1999 be owned by the same user as the owner of the phpMyAdmin scripts.
2000 </dd>
2003 <dd>
2004 The name of the directory where temporary files can be stored.
2005 <br /><br />
2007 This is needed for native MS Excel export, see
2013 <br /><br />
2015 If the directory where phpMyAdmin is installed is subject to an
2017 temporary directory in some directory accessible by the web
2018 server. However for security reasons, this directory should be outside
2019 the tree published by webserver. If you cannot avoid having this
2020 directory published by webserver, place at least an empty
2022 possible.
2023 <br /><br />
2025 This directory should have as strict permissions as possible as the only
2026 user required to access this directory is the one who runs the
2027 webserver. If you have root privileges, simply make this user owner of
2028 this directory and make it accessible only by it:
2029 <br /><br />
2031 <pre>
2032 chown www-data:www-data tmp
2033 chmod 700 tmp
2034 </pre>
2036 If you cannot change owner of the directory, you can achieve a similar
2039 <pre>
2040 chmod 700 tmp
2041 setfacl -m "g:www-data:rwx" tmp
2042 setfacl -d -m "g:www-data:rwx" tmp
2043 </pre>
2045 If neither of above works for you, you can still make the directory
2047 system reading and writing data in this directory.
2048 </dd>
2051 <dd>
2052 In this array are defined default parameters for export, names of
2053 items are similar to texts seen on export page, so you can easily
2054 identify what they mean.
2055 </dd>
2058 <dd>
2059 Defines how the export form is displayed when it loads. Valid values are:
2060 <ul>
2063 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2064 </ul>
2065 </dd>
2068 <dd>
2069 In this array are defined default parameters for import, names of
2070 items are similar to texts seen on import page, so you can easily
2071 identify what they mean.
2072 </dd>
2075 <dd>
2076 Repeat the headers every X cells, or 0 to deactivate.
2077 </dd>
2085 </dt>
2086 <dd>
2087 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2088 or icon is always displayed on the left panel. If JavaScript is enabled in
2089 your browser, a click on this opens a distinct query window, which is
2090 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2091 changes to display a query box.<br /><br />
2093 The size of this query window can be customized with
2095 - both integers for the size in pixels. Note that normally, those
2097 theme you are using.<br /><br />
2101 opens the query window and puts the current query
2102 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2103 query in the right panel's query box.
2104 <br /><br />
2105 The usage of the JavaScript query window is recommended if you have a
2106 JavaScript enabled browser. Basic functions are used to exchange quite
2107 a few variables, so most 4th generation browsers should be capable to
2108 use that feature. It currently is only tested with Internet Explorer 6
2109 and Mozilla 1.x.
2110 <br /><br />
2112 to a table, which has to be created by you (see <a
2114 all your queries will be appended to the form, but only as long as
2115 your window is opened they remain saved.
2116 <br /><br />
2117 When using the JavaScript based query window, it will always get
2118 updated when you click on a new table/db to browse and will focus if
2119 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2120 the query window by checking the box "Do not overwrite this query from
2121 outside the window" below the query textarea. Then you can browse
2122 tables/databases in the background without losing the contents of the
2123 textarea, so this is especially useful when composing a query with
2124 tables you first have to look in. The checkbox will get automatically
2125 checked whenever you change the contents of the textarea. Please
2126 uncheck the button whenever you definitely want the query window to
2127 get updated even though you have made alterations.
2128 <br /><br />
2131 <br /><br />
2132 The query window also has a custom tabbed look to group the features.
2134 default tab to be used when opening the query window. It can be set to
2135 either 'sql', 'files', 'history' or 'full'.</dd>
2141 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2143 If the approximate row count as returned by
2146 count will be used.
2147 </dd>
2149 <dd>For VIEWs, since obtaining the exact count could have an
2150 impact on performance, this value is the maximum to be displayed, using
2152 any row counting.
2153 </dd>
2156 <dd>Sorts database and table names according to natural order (for example,
2157 t1, t2, t10). Currently implemented in the left panel (Light mode)
2158 and in Database view, for the table list.</dd>
2167 that users can't set through user preferences. For possible values, refer
2174 <dd>Allows you to specify window's title bar. You can use
2176 </dd>
2186 </dd>
2189 <dd>If theme manager is active, use this as the path of the subdirectory
2190 containing all the themes.</dd>
2204 </dt>
2205 <dd>Default queries that will be displayed in query boxes when user didn't
2206 specify any. You can use standard
2208 </dd>
2211 <dd>
2212 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
2213 default we use HTML to format the query, but you can disable this by
2215 </dd>
2218 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2219 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2220 query inside a bracket is indented. By changing
2223 specifies the units of the indent amount that you specified. This is
2224 used via stylesheets.</dd>
2227 <dd>This array is used to define the colours for each type of element of
2228 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2230 If you specify an empty string for the color of a class, it is ignored
2231 in creating the stylesheet.
2232 You should not alter the class names, only the colour strings.<br />
2253 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2257 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2258 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2259 </ul>
2260 </dd>
2264 <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,
2265 as originally published on
2267 <br />
2268 For help in setting up your system to use the service, see the
2270 </dd>
2274 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2275 and any password, so we use those by default. Instead, if
2276 you have an account with them, you can put your login details
2277 here, and it will be used in place of the anonymous login.</dd>
2278 </dl>
2279 </dd>
2282 <dd><b>DEVELOPERS ONLY!</b></dd>
2285 <dd><b>DEVELOPERS ONLY!</b><br />
2286 Enable logging queries and execution times to be displayed in the bottom
2287 of main page (right frame).</dd>
2290 <dd>All possible types of a MySQL column. In most cases you don't need to
2291 edit this.</dd>
2294 <dd>Possible attributes for columns. In most cases you don't need to edit
2295 this.</dd>
2298 <dd>A list of functions MySQL supports. In most cases you don't need to
2299 edit this.</dd>
2302 <dd>Mapping of column types to meta types used for preferring displayed
2303 functions. In most cases you don't need to edit this.</dd>
2306 <dd>Functions preferred for column meta types as defined in
2307 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2308 to edit this.</dd>
2311 <dd>Functions selected by default when inserting/changing row, Functions
2312 are defined for meta types from
2314 <code>first_timestamp</code>, which is used for first timestamp column
2315 in table.</dd>
2318 <dd>Operators available for search operations on numeric and date columns.
2319 </dd>
2322 <dd>Operators available for search operations on character columns.
2323 Note that we put <code>LIKE</code> by default instead of
2324 <code>LIKE %...%</code>, to avoid unintended performance problems
2325 in case of huge tables.</dd>
2328 <dd>Operators available for search operations on ENUM columns.</dd>
2331 <dd>Additional operators available for search operations when the
2332 column can be null.</dd>
2334 </dl>
2336 <!-- TRANSFORMATIONS -->
2342 </ol>
2346 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2348 section</a> on how to do so.</p>
2350 <p> You can apply different transformations to the contents of each column. The
2351 transformation will take the content of each column and transform it with
2352 certain rules defined in the selected transformation.</p>
2354 <p> Say you have a column 'filename' which contains a filename. Normally you would
2355 see in phpMyAdmin only this filename. Using transformations you can transform
2356 that filename into a HTML link, so you can click inside of the phpMyAdmin
2357 structure on the column's link and will see the file displayed in a new browser
2358 window. Using transformation options you can also specify strings to
2359 append/prepend to a string or the format you want the output stored in.</p>
2361 <p> For a general overview of all available transformations and their options,
2362 you can consult your
2363 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2364 installation.</p>
2366 <p> For a tutorial on how to effectively use transformations, see our
2368 the official phpMyAdmin homepage.</p>
2372 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2373 clicking on the 'Structure' link for a table). There click on
2374 "Change" (or change icon) and there you will see three new
2375 fields at
2376 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2377 'Transformation options'.</p>
2379 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2380 that corresponds to the column's contents. Please note that
2381 transformations are inactive as long as no MIME-type is selected.</li>
2383 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2384 hopefully growing amount of pre-defined transformations. See below for information on
2385 how to build your own transformation.<br />
2387 There are global transformations and mimetype-bound transformations. Global transformations
2388 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2389 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2390 transformations which operate on the main mimetype (like 'image'), which will most likely
2391 take the subtype into regard, and those who only operate on a
2392 specific subtype (like 'image/jpeg').<br />
2394 You can use transformations on mimetypes for which the function was not defined for. There
2395 is no security check for you selected the right transformation, so take care of what the
2396 output will be like.</li>
2398 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2399 transform-function specific options here. Usually the transforms can operate with default
2400 options, but it is generally a good idea to look up the overview to see which options are
2401 necessary.<br />
2403 Much like the ENUM/SET-Fields, you have to split up several options using the format
2404 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2405 parsed as an array, leaving the first value the first element in the array, and so
2406 forth.<br />
2408 If you want to specify a MIME character set you can define it in the transformation_options.
2409 You have to put that outside of the pre-defined options of the specific mime-transform,
2411 for which you can specify 2 options and you want to append a character set, enter "'first
2412 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2414 </ul>
2418 <p> All mimetypes and their transformations are defined through single files in
2419 the directory 'libraries/transformations/'.</p>
2421 <p> They are stored in files to ease up customization and easy adding of new
2422 transformations.</p>
2424 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2425 always work. It makes no sense to apply a transformation to a mimetype the
2426 transform-function doesn't know to handle.</p>
2428 <p> One can, however, use empty mime-types and global transformations which should work
2429 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2430 for, but pay attention to option usage as well as what the transformation does to your
2431 column.</p>
2433 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2434 any other transform function and provides some basic functions.</p>
2436 <p> There are 5 possible file names:</p>
2438 <ol><li>A mimetype+subtype transform:<br /><br />
2440 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2442 Please not that mimetype and subtype are separated via '_', which shall
2443 not be contained in their names. The transform function/filename may
2444 contain only characters which cause no problems in the file system as
2445 well as the PHP function naming convention.<br /><br />
2447 The transform function will the be called
2448 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2450 <b>Example:</b><br /><br />
2452 <tt>text_html__formatted.inc.php</tt><br />
2453 <tt>PMA_transform_text_html__formatted()</tt></li>
2455 <li>A mimetype (w/o subtype) transform:<br /><br />
2457 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2459 Please note that there are no single '_' characters.
2460 The transform function/filename may contain only characters which cause
2461 no problems in the file system as well as the PHP function naming
2462 convention.<br /><br />
2464 The transform function will the be called
2465 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2467 <b>Example:</b><br /><br />
2469 <tt>text__formatted.inc.php</tt><br />
2470 <tt>PMA_transform_text__formatted()</tt></li>
2472 <li>A mimetype+subtype without specific transform function<br /><br />
2474 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2476 Please note that there are no '__' characters in the filename. Do not
2477 use special characters in the filename causing problems with the file
2478 system.<br /><br />
2480 No transformation function is defined in the file itself.<br /><br />
2482 <b>Example:</b><br /><br />
2484 <tt>text_plain.inc.php</tt><br />
2485 (No function)</li>
2487 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2489 <tt>[mimetype].inc.php</tt><br /><br />
2491 Please note that there are no '_' characters in the filename. Do not use
2492 special characters in the filename causing problems with the file system.
2493 <br /><br />
2495 No transformation function is defined in the file itself.<br /><br />
2497 <b>Example:</b><br /><br />
2499 <tt>text.inc.php</tt><br />
2500 (No function)</li>
2502 <li>A global transform function with no specific mimetype<br /><br />
2504 <tt>global__[transform].inc.php</tt><br /><br />
2506 The transform function will the be called
2507 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2509 <b>Example:</b><br /><br />
2511 <tt>global__formatted</tt><br />
2512 <tt>PMA_transform_global__formatted()</tt></li>
2513 </ol>
2515 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2516 transform function.</p>
2518 <p> All filenames containing no '__' in themselves are not shown as valid transform
2519 functions in the dropdown.</p>
2521 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2522 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2523 without a transform function.</p>
2525 <p> To create a new transform function please see
2526 <tt>libraries/transformations/template_generator.sh</tt>.
2527 To create a new, empty mimetype please see
2528 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2530 <p> A transform function always gets passed three variables:</p>
2532 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2533 you want to transform.</li>
2534 <li><b>$options</b> - Contains any user-passed options to a transform function
2535 as an array.</li>
2536 <li><b>$meta</b> - Contains an object with information about your column.
2537 The data is drawn from the output of the
2539 function. This means, all object properties described on the
2541 available in this variable and can be used to transform a column accordingly
2542 to unsigned/zerofill/not_null/... properties.<br />
2543 The $meta->mimetype variable contains the original MIME-type of the
2544 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2545 </ol>
2547 <p> Additionally you should also provide additional function to provide
2548 information about the transformation to the user. This function should
2549 have same name as transformation function just with appended
2550 <code>_info</code> suffix. This function accepts no parameters and returns
2551 array with information about the transformation. Currently following keys
2552 can be used:
2553 </p>
2554 <dl>
2555 <dt><code>info</code></dt>
2556 <dd>Long description of the transformation.</dd>
2557 </dl>
2559 <!-- FAQ -->
2566 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2571 </ol>
2573 <p> Please have a look at our
2575 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2576 features and or interface.</p>
2582 action is required or phpMyAdmin sends a blank page or a page full of
2583 cryptic characters to my browser, what can I do?</a></h4>
2586 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2587 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2588 configuration file.<br /></p>
2593 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2594 See also the
2596 entry about PHP bugs with output buffering.<br />
2597 If your server keeps crashing, please ask for help in the various Apache
2598 support groups.</p>
2607 application misbehaved by not returning a complete set of
2609 </h4>
2611 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2612 Have a look at the last message in this
2614 official PHP bug database.</p>
2619 and/or many error messages with the
2622 <p> This is a known problem with the PHP
2624 filter: it's not so stable. Please use instead the cookie authentication mode.
2625 </p>
2630 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2631 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2632 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2633 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2634 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2639 work.</a></h4>
2641 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2642 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2643 or not, and so on). So, you must have Zlib/Bzip2
2644 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2648 an error about safe mode being in effect.</a></h4>
2650 <p> Your uploaded file is saved by PHP in the "upload dir", as
2651 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2652 the system default is <i>/tmp</i>).<br />
2653 We recommend the following setup for Apache servers running in safe mode,
2654 to enable uploads of files while being reasonably secure:</p>
2656 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2657 <li>give ownership to the Apache server's user.group:
2658 <tt>chown apache.apache /tmp/php</tt></li>
2659 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2660 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2661 <li>restart Apache</li>
2662 </ul>
2669 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2670 I'm using the Apache server.</a></h4>
2672 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2673 your <i>httpd.conf</i>:</p>
2677 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2681 uploading a file from the query box.</a></h4>
2683 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2684 restrictions. However you need to create temporary directory and
2686 The uploaded files will be moved there, and after execution of your
2692 <p> The MySQL manual explains how to
2694 reset the permissions</a>.</p>
2704 </h4>
2706 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2707 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2708 names to align with current standards.</p>
2713 </h4>
2715 <p> Starting with version 2.7.0, the import engine has been re–written and these
2716 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2717 to take advantage of the new import features.</p>
2719 <p> The first things to check (or ask your host provider to check) are the
2720 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2721 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2722 All of these three settings limit the maximum size of data that can be
2723 submitted and handled by PHP. One user also said that post_max_size
2724 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2726 There exist several workarounds if your upload is too big or your
2727 hosting provider is unwilling to change the settings:</p>
2730 feature. This allows one to
2731 upload a file to the server via scp, ftp, or your favorite file transfer
2732 method. PhpMyAdmin is then able to import the files from the temporary
2734 section</a> of this document.</li>
2736 BigDump</a>) to split the files before uploading. We cannot support this
2737 or any third party applications, but are aware of users having success
2738 with it.</li>
2739 <li>If you have shell (command line) access, use MySQL to import the files
2740 directly. You can do this by issuing the "source" command from
2741 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2742 </ul>
2746 support?</a></h4>
2748 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2749 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2750 connect to your MySQL server using PHP's classic
2753 is available in php 5.0. The latter one should be used unless you have a
2754 good reason not to do so.<br />
2755 When compiling PHP, we strongly recommend that you manually link the MySQL
2756 extension of your choice to a MySQL client library of at least the same
2757 minor version since the one that is bundled with some PHP distributions is
2760 MariaDB is also supported (versions 5.1 and 5.2 were tested).
2761 </p>
2765 message, "Client does not support authentication protocol requested
2766 by server; consider upgrading MySQL client"</a></h5>
2768 <p> You tried to access MySQL with an old MySQL client library. The version of
2769 your MySQL client library can be checked in your phpinfo() output.
2770 In general, it should have at least the same minor version as your server
2774 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2775 changed the authentication hash and your PHP is trying to use the old method.
2777 with the proper client library to match your MySQL installation. Your
2778 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2779 More information (and several workarounds) are located in the
2781 </p>
2788 script seems not to know the font face I'm using!</a></h4>
2790 <p> The "FPDF" library we're using for this feature requires some
2791 special files to use font faces.<br />
2793 these files.</p>
2797 check PHP Configuration".</a></h4>
2799 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2800 "MySQL extension". This extension may be part of the PHP
2801 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2802 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2803 to load the extension but failed.<br /><br />
2805 Usually, the problem is solved by installing a software package called
2806 "PHP-MySQL" or something similar.</p>
2811 and I cannot log in using cookie auth.</a></h4>
2813 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2817 so I cannot upload.</a></h4>
2819 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2820 parameter is not set to "on".</p>
2824 a new table the table and column names are changed to lowercase!</a></h4>
2826 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2827 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2828 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2829 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2830 directory and add the following line to the group [mysqld]:</p>
2832 <pre>set-variable = lower_case_table_names=0</pre>
2834 <p> Next, save the file and restart the MySQL service. You can always check the
2835 value of this directive using the query</p>
2837 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2844 and I get problems, such as undefined variables when I run a
2847 <p> A tip from Jose Fandos: put a comment on the following two lines
2848 in httpd.conf, like this:</p>
2850 <pre>
2851 # mod_gzip_item_include file \.php$
2853 </pre>
2855 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2856 PHP scripts. Of course you have to restart Apache.</p>
2861 I get the error "No input file specified" when trying to
2862 run phpMyAdmin.</a></h4>
2864 <p> This is a permission problem. Right-click on the phpmyadmin folder
2865 and choose properties. Under the tab Security, click on "Add"
2866 and select the user "IUSR_machine" from the list. Now set his
2867 permissions and it should work.</p>
2871 db_structure.php with plenty of tables).</a></h4>
2874 GZIP output buffering is enabled. If you turn off it (by
2876 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2877 PHP 5.0.0.</p>
2881 message 'Errorcode: 13'. What does this mean?</a></h4>
2883 <p> This can happen due to a MySQL bug when having database / table names with
2884 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2885 To fix this, turn off this directive, convert all database and table names
2886 to lower case and turn it on again. Alternatively, there's a bug-fix
2887 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2891 and the columns are duplicated.</a></h4>
2893 <p> It is possible to configure Apache in such a way that PHP has problems
2894 interpreting .php files.</p>
2896 <p> The problems occur when two different (and conflicting) set of directives
2897 are used:</p>
2899 <pre>
2900 SetOutputFilter PHP
2901 SetInputFilter PHP
2902 </pre>
2904 <p> and</p>
2906 <pre>AddType application/x-httpd-php .php</pre>
2908 <p> In the case we saw, one set of directives was in
2909 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2910 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2911 The recommended way is with <tt>AddType</tt>, so just comment out
2912 the first set of lines and restart Apache:</p>
2914 <pre>
2915 #SetOutputFilter PHP
2916 #SetInputFilter PHP
2917 </pre>
2922 <p> This problem is known to happen when the server is running Turck MMCache
2923 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2928 <p>Yes.</p>
2929 <p>
2930 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
2931 is still maintained.
2932 </p>
2935 <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>
2937 <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>
2940 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2941 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2942 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2943 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2944 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2945 enabled.) Click <tt>OK</tt>.</li>
2946 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2947 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2948 </ol>
2952 PHP 5.0.4 on 64-bit systems?</a></h4>
2954 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2955 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2961 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
2962 the order of the server paragraph in <tt>config.inc.php</tt>.
2963 Table and script parts are optional. If you want
2964 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2965 some configuration. Following lines apply only for <a
2967 that you have enabled some features within global configuration. You need
2968 <code>Options FollowSymLinks</code> and <code>AllowOverride
2969 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2970 you need mod_rewrite to be enabled. Then you just need to create following
2971 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2972 (don't forget to change directory name inside of it):</p>
2974 <pre>
2975 RewriteEngine On
2976 RewriteBase /path_to_phpMyAdmin
2977 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2978 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2979 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2980 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2981 </pre>
2984 <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>
2986 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2987 following rewrite rule:</p>
2989 <pre>
2990 RewriteEngine On
2991 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2992 </pre>
2996 </h4>
2997 <p>
2998 There can be many explanations to this and a look at your server's
2999 error log file might give a clue.
3000 </p>
3004 password encryption in cookie auth doesn't work.</a></h4>
3006 <p> If your cluster consist of different architectures, PHP code used for
3007 encryption/decryption won't work correct. This is caused by use of
3008 pack/unpack functions in code. Only solution is to use mcrypt extension
3009 which works fine in this case.</p>
3014 <p> Yes but the default configuration values of Suhosin are known to cause
3015 problems with some operations, for example editing a table with many
3016 columns and no primary key or with textual primary key.
3017 </p>
3018 <p>
3019 Suhosin configuration might lead to malfunction in some cases and it can
3020 not be fully avoided as phpMyAdmin is kind of application which needs to
3021 transfer big amounts of columns in single HTTP request, what is something
3022 what Suhosin tries to prevent. Generally all
3023 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3024 <code>suhosin.get.*</code> directives can have negative effect on
3025 phpMyAdmin usability. You can always find in your error logs which limit
3026 did cause dropping of variable, so you can diagnose the problem and adjust
3027 matching configuration variable.
3028 </p>
3029 <p>
3030 The default values for most Suhosin configuration options will work in most
3031 scenarios, however you might want to adjust at least following parameters:
3032 </p>
3034 <ul>
3035 <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>
3036 <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>
3037 <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>
3038 <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>
3039 <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>
3040 <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>
3041 <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>
3042 <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>
3043 </ul>
3045 <p>
3047 <tt>SuhosinDisableWarning</tt> directive</a>.
3048 </p>
3052 but then my connection is redirected back to http. What can cause this
3053 behavior?</a></h4>
3055 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3056 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>
3059 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3061 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3062 Example from the Apache 2.2 documentation:</p>
3063 <pre>
3064 ProxyPass /mirror/foo/ http://backend.example.com/
3065 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3066 ProxyPassReverseCookieDomain backend.example.com public.example.com
3067 ProxyPassReverseCookiePath / /mirror/foo/
3068 </pre>
3070 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3071 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3072 This is not specific to phpmyadmin, it's just the behavior of Apache.
3073 </p>
3075 <pre>
3076 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3077 ProxyPassReverse /mirror/foo/
3078 http://backend.example.com/%7Euser/phpmyadmin
3079 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3080 </pre>
3082 <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>
3083 for more details.</p>
3087 privileges, I get an error about an unknown column.</a></h4>
3089 <p> The MySQL server's privilege tables are not up to date, you need to run
3090 the <tt>mysql_upgrade</tt> command on the server.</p>
3097 headers already sent by ..." is displayed, what's the problem?</a></h4>
3099 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3100 (I.E. no blank lines, no spaces, no characters...) neither before the
3101 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3102 tag at the end. We also got a report from a user under IIS, that used
3103 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3104 contained an end-of-line character (hex 0A) at the end; removing this character
3105 cleared his errors.</p>
3110 <p> Either there is an error with your PHP setup or your username/password is
3111 wrong. Try to make a small script which uses mysql_connect and see if it
3112 works. If it doesn't, it may be you haven't even compiled MySQL support
3113 into PHP.</p>
3117 connect to local MySQL server through socket '/tmp/mysql.sock'
3118 (111) ..." is displayed. What can I do?</a></h4>
3120 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3122 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3123 In your <i>php.ini</i> you will find a line</p>
3125 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3127 <p> change it to</p>
3129 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3131 <p> Then restart apache and it will work.</p>
3133 <p> Here is a fix suggested by Brad Ummer:</p>
3135 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3136 To do this, telnet to your server and go to the MySQL bin directory. In
3137 this directory there should be a file named <i>mysqladmin</i>. Type
3138 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3139 info about your MySQL server, including the socket
3140 (<i>/tmp/mysql.sock</i>, for example).</li>
3141 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3142 phpMyAdmin, you need to complete the socket information in the
3143 <i>config.inc.php</i>.<br />
3144 For example:
3146 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3147 <br /><br />
3149 Please also make sure that the permissions of this file allow to be readable
3150 by your webserver (i.e. '0755').</li>
3151 </ul>
3153 <p> Have also a look at the
3155 corresponding section of the MySQL documentation</a>.</p>
3159 what can I do?</a></h4>
3162 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3163 sometime.<br />
3164 Also have a look at your PHP version number: if it contains "4.0b..."
3165 it means you're running a beta version of PHP. That's not a so good idea,
3166 please upgrade to a plain revision.</p>
3170 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3171 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3173 <p> Check the value you set for the
3175 directive in the phpMyAdmin configuration file.</p>
3179 password: YES)"-error when trying to access a MySQL-Server on a
3180 host which is port-forwarded for my localhost.</a></h4>
3182 <p> When you are using a port on your localhost, which you redirect via
3183 port-forwarding to another host, MySQL is not resolving the localhost
3184 as expected.<br />
3185 Erik Wasser explains: The solution is: if your host is "localhost"
3186 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3187 connection for speeding up things. And that doesn't work in this configuration
3188 with port forwarding.<br />
3194 <p> Themes are configured with
3198 <br />
3200 should not delete the directory "original" or its underlying
3201 structure, because this is the system theme used by phpMyAdmin.
3202 "original" contains all images and styles, for backwards
3203 compatibility and for all themes that would not include images or css-files.
3204 <br /><br />
3207 is enabled, you can select your favorite theme on the main page. Your
3208 selected theme will be stored in a cookie.<br /><br /></p>
3210 <p> To create a theme:</p>
3212 <ul><li>make a new subdirectory (for example "your_theme_name") under
3214 (by default <tt>themes</tt>)</li>
3215 <li>copy the files and directories from "original" to
3216 "your_theme_name"</li>
3217 <li>edit the css-files in "your_theme_name/css"</li>
3218 <li>put your new images in "your_theme_name/img"</li>
3219 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3220 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3221 contain your chosen theme name, that will be visible in user interface</li>
3222 <li>make a new screenshot of your theme and save it under
3223 "your_theme_name/screen.png"</li>
3224 </ul>
3226 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3227 theme verbose name, theme generation and theme version. These versions and
3228 generations are enumerated from 1 and do not have any direct dependence on
3229 phpMyAdmin version. Themes within same generation should be backwards
3230 compatible - theme with version 2 should work in phpMyAdmin requiring
3231 version 1. Themes with different generation are incompatible.</p>
3233 <p> If you do not want to use your own symbols and buttons, remove the
3234 directory "img" in "your_theme_name". phpMyAdmin will
3235 use the default icons and buttons (from the system-theme "original").
3236 </p>
3240 what can I do?</a></h4>
3242 <p> Here are a few points to check:</p>
3244 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3246 directive empty. See also
3248 </li>
3249 <li>Maybe you have a broken PHP installation or you need to upgrade
3250 your Zend Optimizer. See
3252 http://bugs.php.net/bug.php?id=31134</a>.
3253 </li>
3254 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3255 set to the default (200) or another low value, you could get this
3256 error if your table has a high number of columns. Adjust this setting
3257 accordingly. (Thanks to Klaus Dorninger for the hint).
3258 </li>
3259 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3260 of ";" will cause this error. Replace it with "&;".
3261 </li>
3263 you might want to increase
3265 </li>
3266 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3267 </li>
3268 </ul>
3273 <p> To be able to see a progress bar during your uploads, your server must
3276 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3277 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3284 who logged out can not log in again in with the same nick.</a></h4>
3286 <p> This is related to the authentication mechanism (protocol) used by
3287 phpMyAdmin. To bypass this problem: just close all the opened
3288 browser windows and then go back to phpMyAdmin. You should be able to
3289 log in again.</p>
3293 limit error or a time limit error.</a></h4>
3295 <p> Compressed dumps are built in memory and because of this are limited to
3296 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3297 using
3299 (enabled by default). Zip exports can not be handled this way, so if you need
3300 Zip files for larger dump, you have to use another way.</p>
3304 when I rename a table or a column.</a></h4>
3306 <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>
3310 bundled with the MySQL server distribution.</a></h4>
3312 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3314 <pre>
3315 -- MySQL dump 8.22
3316 --
3317 -- Host: localhost Database: database
3318 ---------------------------------------------------------
3319 -- Server version 3.23.54
3320 </pre>
3322 <p> The invalid part of the code is the horizontal line made of dashes that
3323 appears once in every dump created with mysqldump. If you want to run your
3324 dump you have to turn it into valid MySQL. This means, you have to add a
3325 whitespace after the first two dashes of the line or add a # before it:
3326 <br />
3327 <code>
3328 -- -------------------------------------------------------<br />
3329 </code>
3330 or<br />
3331 <code>
3332 #---------------------------------------------------------
3333 </code>
3334 </p>
3341 <p> Please note that you should not use the separating string multiple times
3342 without any characters between them, or at the beginning/end of your table
3343 name. If you have to, think about using another TableSeparator or disabling
3344 that feature</p>
3349 <p> In Relation view, being able to choose a table in another database,
3350 or having more than one index column in the foreign key.<br /><br/>
3351 In Query-by-example (Query), automatic generation of the query
3352 LEFT JOIN from the foreign table.<br /><br/>
3353 </p>
3357 I get series of errors like "Warning: unable to parse url". How
3358 can this be fixed?</a></h4>
3359 <p>
3360 Your table neither have a primary key nor an unique one, so we must use a
3361 long expression to identify this row. This causes problems to parse_url
3362 function. The workaround is to create a primary or unique key.
3363 <br />
3364 </p>
3368 a MIME-Transformation onto!</a></h4>
3370 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3371 nested forms can be put inside the table where phpMyAdmin displays the results.
3372 You can, however, use any form inside of a table if keep the parent
3373 form-container with the target to tbl_row_delete.php and just put your own
3374 input-elements inside. If you use a custom submit input field, the form will
3375 submit itself to the displaying page again, where you can validate the
3376 $HTTP_POST_VARS in a transformation.
3378 For a tutorial on how to effectively use transformations, see our
3380 on the official phpMyAdmin-homepage.</p>
3384 MySQL server</a></h4>
3386 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3389 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3390 the quote-character (") is interpreted as an identifier quote character and
3391 not as a string quote character, which makes many internal phpMyAdmin
3393 statements. There is no workaround to this behaviour. News to this item will
3394 be posted in Bug report
3395 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3396 </p>
3400 more that one column with the same value
3401 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3402 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3404 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3405 can use it for the Edit and Delete links.</p>
3410 <p> phpMyAdmin uses a quick method to get the row count, and this method
3411 only returns an approximate count in the case of InnoDB tables. See
3413 a way to modify those results, but
3414 this could have a serious impact on performance.</p>
3421 containing an hyphen.
3422 </a></h4>
3423 <p>
3424 The tests I have made with MySQL 5.1.49 shows that the
3425 API does not accept this syntax for the USE command.
3426 </p>
3429 <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>
3430 <p>
3431 This has been a known limitation of phpMyAdmin since the beginning and
3432 it's not likely to be solved in the future.
3433 </p>
3435 <!-- Begin: Excel import limitations -->
3438 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3439 <p>
3440 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3441 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3442 <br /><br />
3443 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3444 </p>
3447 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3448 <p>
3449 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3450 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3451 </p>
3454 <a href="#faq3_17">3.17 When I import an Excel spreadsheet, my custom cell types are not represented as they are in Excel.</a></h4>
3455 <p>
3456 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3457 consider using a built-in type. These are almost always guarenteed to import correctly.
3458 </p>
3460 <!-- End: Excel import limitations -->
3461 <!-- Begin: CSV import limitations -->
3464 <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>
3465 <p>
3466 There is no reliable way to differetiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3467 </p>
3469 <!-- End: CSV import limitations -->
3470 <!-- Begin: Import type-detection limitations -->
3473 <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>
3474 <p>
3475 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
3476 you will have to edit the structure to your liking post-import.
3477 <br /><br />
3478 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
3479 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.
3480 </p>
3482 <!-- End: Import type-detection limitations -->
3484 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3487 <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
3488 need to install it for each customer.
3489 </a></h4>
3490 <p>
3491 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3492 your users. The development of this feature was kindly sponsored by
3493 NetCologne GmbH.
3494 This requires a properly setup MySQL user management and phpMyAdmin
3495 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3497 </p>
3501 access.
3502 </a></h4>
3503 <p>
3504 This depends on your system.<br />
3505 If you're running a server which cannot be accessed by other people, it's
3506 sufficient to use the directory protection bundled with your webserver
3508 If other people have telnet access to your server, you should use
3509 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3510 <br /><br />
3511 Suggestions:
3512 </p>
3513 <ul>
3514 <li>
3516 </li>
3517 <li>
3518 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3519 is a user whose password is only known to you, and apache is the
3520 group under which Apache runs.
3521 </li>
3522 <li>
3523 You should use PHP safe mode, to protect from other users that try
3525 </li>
3526 </ul>
3531 </a></h4>
3532 <p>
3537 </p>
3540 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3541 authentication.
3542 </a></h4>
3546 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3547 and/or
3549 are wrong.</li>
3551 <li>You have already setup a security mechanism for the
3552 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3553 phpMyAdmin's authentication, so remove it.</li>
3554 </ul>
3561 and put the privileges you want. For example,
3563 would let a user create/manage his/her database(s).</p>
3568 <p> If you have existing rules from an old .htaccess file, you can take them
3571 be a major benefit here if your installation is suited to using it. Then
3572 you can just add those updated lines into the
3576 <p> If you want a pre-made sample, you can try this fragment. It stops the
3577 'root' user from logging in from any networks other than the private
3580 <pre>
3581 //block root from logging in except from the private networks
3582 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3583 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3584 'deny root from all',
3585 'allow root from localhost',
3589 );
3590 </pre>
3595 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3596 different than the one set in your
3598 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3599 while a domain name is defined in the config file.</p>
3604 <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>
3610 when trying to create a table with more than 14 columns.
3611 </a></h4>
3612 <p>
3613 We could reproduce this problem only under Win98/98SE. Testing under
3614 WinNT4 or Win2K, we could easily create more than 60 columns.
3615 <br />
3616 A workaround is to create a smaller number of columns, then come back to
3617 your table properties and add the other columns.
3618 </p>
3622 <p>
3623 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3624 with each script/website that use forms.<br />
3625 Upgrade or downgrade your Xitami server.
3626 </p>
3629 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3630 <p>
3631 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3632 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3633 don't seem to work.<br />
3635 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3636 the user's temporary directory, so they must be moved before closing
3637 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3640 </p>
3644 Explorer never stores the cookies.
3645 </a></h4>
3646 <p>
3647 MS Internet Explorer seems to be really buggy about cookies, at least till
3648 version 6.
3649 </p>
3653 rows.
3654 </a></h4>
3655 <p>
3657 </p>
3660 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3661 when trying to modify a row in a table with many columns, or with a text
3662 column
3663 </a></h4>
3664 <p>
3665 Your table neither have a primary key nor an unique one, so we must use a
3666 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
3667 those browsers, and this not happen in Netscape, for example. The
3668 workaround is to create a primary or unique key, or use another browser.
3669 <br />
3670 </p>
3674 page.
3675 </a></h4>
3676 <p>
3677 Some browsers support right-clicking into the frame you want to refresh,
3678 just do this in the right frame.<br />
3679 </p>
3683 query box.
3684 </a></h4>
3685 <p>
3686 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3687 Mozilla versions.<br />
3688 </p>
3692 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3693 </a></h4>
3694 <p>
3695 This is a Mozilla bug (see bug #26882 at
3697 </p>
3702 </a></h4>
3703 <p>
3704 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3705 data in octet-stream mode. Since we can't detect the specific Netscape
3706 version, we cannot workaround this bug.
3707 </p>
3711 wrong.</a></h4>
3713 <p> Please ensure that you have set your browser's character set to the one of the
3714 language file you have selected on phpMyAdmin's start page.
3715 Alternatively, you can try the auto detection mode that is supported by the
3716 recent versions of the most browsers.</p>
3719 <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
3722 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3723 Netscape and Mozilla do not have this problem.</p>
3726 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3727 I cannot manage two servers: I log in to the first one, then the other one,
3728 but if I switch back to the first, I have to log in on each operation.</a></h4>
3734 but nothing happens after that, only a blank screen.</a></h4>
3745 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3750 address and you are starting
3752 containing a domain name, or the reverse situation.</li>
3753 <li>Security settings in IE and/or Microsoft Security Center are
3754 too high, thus blocking scripts execution.</li>
3755 <li>The Windows Firewall is blocking Apache and MySQL. You must
3759 </ul>
3762 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3763 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3764 installed in their Firefox is causing the problem.</p>
3768 clause is generated when I browse a table.</a></h4>
3769 <p> This happens only when both of these conditions are met: using the
3779 </a></h4>
3780 <p>
3781 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3782 specifying a wrong column-type.<br />
3783 Common errors include:
3784 </p>
3785 <ul>
3788 </ul>
3789 <p>
3790 Also, look at the syntax chapter in the MySQL manual to confirm that your
3791 syntax is correct.
3792 </p>
3796 columns and
3797 phpMyAdmin generates only one index with those two columns.
3798 </a></h4>
3799 <p>
3800 This is the way to create a multi-columns
3801 index. If you want two indexes, create the first one when creating the
3802 table, save, then display the table properties and click the Index link to
3803 create the other index.
3804 </p>
3808 <p>
3809 Since version 2.2.3, you have a checkbox for each column that can be null.
3811 column's value. Since version 2.5.5, you have to use the checkbox to get
3813 a literal NULL in the column, and not a NULL value (this works in PHP4).
3814 </p>
3819 <p> Click on a database or table name in the left frame, the properties will be
3821 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3822 statements that can be used to recreate your database/table.
3823 <br /><br />
3825 transmit the resulting dump to your station. Depending on your PHP
3826 configuration, you will see options to compress the dump. See also the
3828 configuration variable.<br /><br />
3831 this document.</p>
3836 </a></h4>
3838 <p> Click on a database name in the left frame, the properties will be
3840 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3842 the path to your dump filename, or use the Browse button. Then click Go.
3843 <br /><br />
3845 that you upgrade to take advantage of the new features.
3846 <br /><br />
3848 in this document.
3849 </p>
3854 <p> Here is an example with the tables persons, towns and countries, all
3856 table, create it as explained in the configuration section. Then create the
3857 example tables:</p>
3859 <pre>
3860 CREATE TABLE REL_countries (
3861 country_code char(1) NOT NULL default '',
3862 description varchar(10) NOT NULL default '',
3863 PRIMARY KEY (country_code)
3864 ) TYPE=MyISAM;
3866 INSERT INTO REL_countries VALUES ('C', 'Canada');
3868 CREATE TABLE REL_persons (
3869 id tinyint(4) NOT NULL auto_increment,
3870 person_name varchar(32) NOT NULL default '',
3872 country_code char(1) NOT NULL default '',
3873 PRIMARY KEY (id)
3874 ) TYPE=MyISAM;
3876 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3877 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3879 CREATE TABLE REL_towns (
3881 description varchar(30) NOT NULL default '',
3882 PRIMARY KEY (town_code)
3883 ) TYPE=MyISAM;
3885 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3886 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3887 </pre>
3893 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3897 </ul>
3905 <li>In the columns row, choose persons.person_name and click the
3907 <li>Do the same for towns.description and countries.descriptions in the
3910 the correct joins have been generated</li>
3912 </ul>
3916 <p>
3917 Starting from the previous example, create the pma_table_info as explained
3918 in the configuration section, then browse your persons table,
3919 and move the mouse over a town code or country code.
3920 <br /><br />
3921 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3922 enables: drop-down list of possible values.
3923 </p>
3926 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3927 <p>
3930 <br /><br />
3931 Then you need to think about your schema layout. Which tables will go on
3932 which pages?
3933 </p>
3934 <ul>
3940 page and click Go. If you like, you
3942 linked tables onto the new page.</li>
3943 <li>Select the name of the new page (making sure the Edit radio button
3944 is selected) and click Go.</li>
3946 Coordinates are relative; your diagram will
3947 be automatically scaled to fit the page. When initially placing tables
3948 on the page, just pick any coordinates -- say, 50x50. After clicking
3950 position the element correctly.</li>
3952 first be sure to click the Save
3953 button beneath the list of tables and coordinates, to save any changes
3954 you made there. Then scroll all the way down, select the
3956 you want, and click Go.</li>
3957 <li>Internet Explorer for Windows may suggest an incorrect filename when
3962 browsers on Windows, do not have this problem.</li>
3963 </ul>
3967 columns!</a></h4>
3969 <p> No, it's MySQL that is doing
3975 underscores in the database name?</a></h4>
3977 <p> If you do not put a backslash before the underscore, this is a wildcard
3980 john2db ...<br /><br />
3982 If you put a backslash before the underscore, it means that the database
3983 name will have a real underscore.</p>
3987 statistics pages?</a></h4>
3998 if it already exists during the import. It does NOT drop the table after
3999 your export, it only affects the import file.</li>
4001 Otherwise, you may get an error if the table name exists but has a
4002 different structure.</li>
4004 (if any) will be included in backup.</li>
4006 column and table names formed with special characters are protected.</li>
4008 types set in the pmadb in the dump as
4010 </li>
4011 </ul>
4016 command, for better documentation (but resulting file is bigger).</li>
4018 once the INSERT verb and the table name.</li>
4021 </li>
4023 more info is provided in the
4025 but basically with this selected, invalid values are adjusted and
4026 inserted rather than causing the entire statement to fail.</li>
4027 </ul>
4031 in its name.</a></h4>
4034 is the normal way to reference a database and table name. Worse, MySQL
4035 will usually let you create a database with a dot, but then you cannot
4036 work with it, nor delete it.</p>
4042 <p>
4043 To use SQL Validator, you need PHP with
4049 module.
4050 </p>
4052 <p>
4058 usage.
4059 </p>
4061 <p>
4062 If you use the Validator, you should be aware that any
4064 submit will be stored anonymously (database/table/column names,
4065 strings, numbers replaced with generic values). The Mimer
4068 We utilize it as free SOAP service.
4069 </p>
4073 it, but MySQL says "BLOB column '...' used in key specification without
4076 <p> The right way to do this, is to create the column without any indexes,
4078 dialog. On this page, you will be able to choose your BLOB column, and
4079 set a size to the index, which is the condition to create an index on
4080 a BLOB column.</p>
4084 editing fields?</a></h4>
4086 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4087 with many editing fields (table structure changes, row editing, etc.).
4088 You can also have a look at the directive
4090 ('vertical') and see if this eases up editing for you.</p>
4094 WTF is this feature then useful for?</a></h4>
4096 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4097 on them. Otherwise you could just put a comment on the column. Because entering
4098 your own mimetype will cause serious syntax checking issues and validation,
4099 this introduces a high-risk false-user-input situation. Instead you have to
4100 initialize mimetypes using functions or empty mimetype definitions.<br />
4101 Plus, you have a whole overview of available mimetypes. Who knows all those
4102 mimetypes by heart so he/she can enter it at will?</p>
4106 can't I see any bookmarks below the query box? What is this variable for?
4107 </a></h4>
4109 <p> Any query you have executed can be stored as a bookmark on the page where the
4110 results are displayed. You will find a button labeled 'Bookmark this query'
4111 just at the end of the page.<br />
4112 As soon as you have stored a bookmark, it is related to the database you run
4113 the query on. You can now access a bookmark dropdown on each page, the query
4114 box appears on for that database.<br /><br />
4116 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4120 aware of that you HAVE to create a valid query, otherwise your query won't be
4121 even able to be stored in the database.<br />
4123 for your query will remain the way it is, but will be stripped of the /**/
4124 chars. So you can use:<br /><br />
4128 which will be expanded to<br /><br />
4132 in your query, where VARIABLE is the string you entered in the input box. If
4133 an empty string is provided, no replacements are made.<br /><br />
4135 A more complex example. Say you have stored this query:<br /><br />
4137 <br /><br />
4140 the full query will be:<br /><br />
4143 <br /><br />
4145 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4147 spaces inserted there
4148 will be later also inserted as spaces in your query and may lead to unexpected
4149 results especially when
4151 Your initial query which is going to be stored as a bookmark has to yield at
4152 least one result row so
4153 you can store the bookmark. You may have that to work around using well
4157 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4158 include exported table?</a></h4>
4160 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4161 document should look like following one (assuming you have table
4164 <pre>
4165 \documentclass{article} % or any class you want
4166 \usepackage{longtable} % for displaying table
4167 \begin{document} % start of document
4168 \include{table} % including exported table
4169 \end{document} % end of document
4170 </pre>
4174 access them.
4175 </a></h4>
4177 <p> You have one of these global privileges: CREATE
4178 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4179 enable users to see all the database names.
4182 So if your users do not need those privileges, you can remove them and their
4183 databases list will shorten.</p>
4187 possible values for a column, based on some foreign table?</a></h4>
4189 <p> You have to setup appropriate links between the tables, and also
4193 foreign table, a drop-down list of values will be available.
4194 You will see two lists of values, the first list containing the key
4195 and the display column, the second list containing the display column
4196 and the key. The reason for this is to be able to type the first
4197 letter of either the key or the display column.<br /><br />
4199 For 100 values or more, a distinct window will appear, to browse foreign
4200 key values and choose one. To change the default limit of 100, see
4201 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4205 automatically when entering Browse mode for a table?</a></h4>
4207 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4208 </p>
4212 Excel files, how can I enable that?</a></h4>
4214 <p> You can use
4216 which works out of the box, but phpMyAdmin supports direct export
4217 to Microsoft Excel version 97 and newer. For this to work, you need to set
4222 <pre>
4223 cd phpMyAdmin
4224 mkdir tmp
4225 chmod o+rwx tmp
4226 </pre>
4230 what happens to my column comments stored in pmadb?</a></h4>
4232 <p> Automatic migration of a table's pmadb-style column comments to the native
4233 ones is done whenever you enter Structure page for this table.</p>
4238 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4239 <ul>
4242 later)</li>
4245 </ul>
4249 <ol>
4250 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4251 <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>
4252 <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>
4253 <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>
4254 </ol>
4259 <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>
4265 <p>
4266 In all places where phpMyAdmin accepts format strings, you can use
4269 expanded variables depend on a context (for example, if you haven't chosen a
4270 table, you can not get the table name), but the following variables can be used:
4271 </p>
4272 <dl>
4278 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4289 </dl>
4294 <p>
4295 By clicking on the button 'toggle scratchboard' on the page
4296 where you edit x/y coordinates of those elements you can activate a
4297 scratchboard where all your elements are placed. By clicking on an
4298 element, you can move them around in the pre-defined area and the x/y
4299 coordinates will get updated dynamically. Likewise, when entering a
4300 new position directly into the input field, the new position in the
4301 scratchboard changes after your cursor leaves the input field.
4302 </p>
4303 <p>
4304 You have to click on the 'OK'-button below the tables to save the new
4305 positions. If you want to place a new element, first add it to the
4306 table of elements and then you can drag the new element around.
4307 </p>
4308 <p>
4309 By changing the paper size and the orientation you can change the size
4310 of the scratchboard as well. You can do so by just changing the
4311 dropdown field below, and the scratchboard will resize automatically,
4312 without interfering with the current placement of the elements.
4313 </p>
4314 <p>
4315 If ever an element gets out of range you can either enlarge the paper
4316 size or click on the 'reset' button to place all elements below each
4317 other.
4318 </p>
4323 <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>
4330 <p> Our Bug Tracker is located at
4332 under the Bugs section.<br /><br />
4334 But please first discuss your bug with other users:<br />
4336 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4337 </p>
4341 existing language, where do I start?</a></h4>
4343 <p> Always use latest Git version of the po file to translate. You can optionally
4345 server</a> where you can also get the latest po files and merge them
4346 with your translations. For creating a new translation simply use
4350 to do this) or ask on the mailing list to add the translation to the web
4351 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4352 </p>
4353 <p>
4354 Please note that we try not to use HTML entities like &eacute; in
4355 the translations, since we define the right character set in the file.
4356 With HTML entities, the text on JavaScript messages would not
4357 display correctly.
4358 However there are some entities that need to be there: quotes,
4359 non-breakable spaces, ampersands, less than, greater than.
4360 </p>
4361 <p>
4362 You can then put your translations, as a zip file to avoid losing special
4363 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4364 </p>
4365 <p>
4366 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4367 list, because this is where we ask for translations of new messages.
4368 </p>
4370 <p>
4371 Documentation is being translated using po4a and gettext (see
4373 for existing translations). To start, checkout
4374 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4375 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4376 and translate it online. If your language is missing, just contact
4378 you prefer to directly translate the po files, please put updated ones into our
4379 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4380 </p>
4384 phpMyAdmin. How should I proceed?</a></h4>
4389 <tt>git clone
4390 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4391 </li>
4393 <li>generate patch with your changes:
4395 </li>
4398 tracker of the phpMyAdmin project</a>.
4399 </li>
4400 </ol>
4402 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Git">our wiki</a>.</p>
4404 <p> Write access to the repository is granted only to experienced developers who
4405 have already contributed something useful to phpMyAdmin.<br />
4411 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4413 <p> Please refer to
4414 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4415 </p>
4420 <p> If you use Apache web server, phpMyAdmin exports information about
4421 authentication to the Apache environment and it can be used in Apache logs.
4422 Currently there are two variables available:
4423 </p>
4424 <dl>
4426 <dd>User name of currently active user (he does not have to be logged
4427 in).</dd>
4434 </dl>
4435 <p>
4437 </p>
4438 <pre>
4441 </pre>
4442 <p>
4443 You can then use any log analyzing tools to detect possible break-in
4444 attempts.
4445 </p>
4451 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4452 It allows you to connect to local as well as remote servers. This requires you to enter
4453 server host name, username, password, port and the name of the database. Therefore you can
4454 now synchronize your databases placed on the same server or some remote server.
4455 </p>
4457 <p>
4458 This feature is helpful for developers who need to replicate their
4459 database’s structure as well as data. Moreover, this feature not only
4460 helps replication but also facilitates the user to keep his/her database
4461 in sync with another database. Other than the full database, certain
4462 tables of the databases can also be synchronized.
4463 </p>
4465 <p>
4466 You need to fill in the host name of the server, the username and
4467 password of an user account already there in MySQL. Port is by default
4468 populated with 3306 (MySQL default port). Then the name of the database
4469 should be mentioned at the end. All the information other than the port
4470 needs to be filled explicitly for the source as well as target servers.
4471 </p>
4473 <p>
4474 After successfully passing through the authentication phase, the source and
4475 target database table names will be displayed. It will be a tabular
4476 representation.
4477 </p>
4479 <p>
4480 On the left, are listed the source database table names. Some of the
4482 are only present in source database and they need to be added to the
4483 target database in order to synchronize the target database. The tables
4485 target database.
4486 </p>
4488 <p>
4489 On the right, are listed the target database table names. There are few
4491 means that these tables are to be created in target database in order to
4492 synchronize target database with source database. Some table names
4494 only present in target database and they will remain unchanged in the
4495 target database. The column in the middle shows the difference between
4496 the source and target corresponding tables.
4497 </p>
4499 <p>
4501 letters, indicating that either Structure or Data are not up to date. By
4502 clicking on them, they will turn grey, what means that they will be synchronized.
4503 </p>
4505 <!-- DEVELOPERS -->
4508 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4509 great features have been written by other people and you too can help to
4510 make phpMyAdmin a useful tool.</p>
4512 <p> If you're planning to contribute source, please read the following
4513 information:</p>
4519 it free from other code.<br />
4520 Commonly used functions should be added to
4523 <li>Obviously, you're free to use whatever coding style you want. But
4524 please try to keep your code as simple as possible: beginners are
4525 using phpMyAdmin as an example application.<br />
4526 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4527 compliant on one hand, they fit the
4530 coding standards</a>
4531 on the other hand. Please pay attention to this.</li>
4532 <li>Please enable showing PHP errors and warnings by the
4534 configuration directive.</li>
4535 <li>Please try to keep up the file-naming conventions. Table-related stuff
4538 <li>Please use gettext wrappers around all messages
4541 script. To use translated messages, call
4543 Gettext.</li>
4547 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4548 better debug and profile their code.<br />
4549 Please see the
4551 options for more information.<br />
4552 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4553 lost during its re-entry into Earth's atmosphere and in memory of the
4554 brave men and women who gave their lives for the people of Earth.</li>
4555 </ul>
4559 <pre>
4570 </pre>
4572 <p>
4573 This program is free software; you can redistribute it and/or modify
4574 it under the terms of the GNU General Public License version 2,
4575 as published by the Free Software Foundation.
4576 </p>
4578 <p>
4579 This program is distributed in the hope that it will be useful,
4580 but WITHOUT ANY WARRANTY; without even the implied warranty of
4581 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4582 GNU General Public License for more details.
4583 </p>
4585 <p>
4586 You should have received a copy of the GNU General Public License
4587 along with this program; if not, write to the Free Software
4589 </p>
4591 <!-- CREDITS -->
4596 <ul>
4599 <ul>
4602 </ul></li>
4605 <ul>
4610 </ul></li>
4613 <ul>
4619 </ul></li>
4622 <ul>
4624 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4625 generate XHTML1.0 and CSS2 compliant codes</li>
4628 </ul></li>
4631 <ul>
4639 </ul></li>
4642 <ul>
4647 </ul></li>
4650 <ul>
4653 </ul></li>
4656 <ul>
4658 </ul></li>
4661 <ul>
4664 </ul></li>
4667 <ul>
4671 </ul></li>
4674 <ul>
4677 </ul></li>
4680 <ul>
4687 </ul></li>
4690 <ul>
4694 </ul></li>
4697 <ul>
4703 </ul></li>
4706 (http://sf.net/projects/phpmysqlformgen/)
4707 <ul>
4709 </ul></li>
4712 <ul>
4714 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4719 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4723 </ul></li>
4726 <ul>
4728 </ul></li>
4731 <ul>
4733 </ul></li>
4736 <ul>
4738 </ul></li>
4741 <ul>
4742 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4743 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4744 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4745 </ul></li>
4748 <ul>
4750 </ul></li>
4753 <ul>
4755 </ul></li>
4758 <ul>
4760 </ul></li>
4763 <ul>
4766 </ul></li>
4768 <li>Nicola Asuni (Tecnick.com)
4769 <ul>
4772 </ul></li>
4775 <ul>
4778 </ul></li>
4781 <ul>
4783 </ul></li>
4786 <ul>
4789 </ul></li>
4791 <li>Ivan A Kirillov
4792 <ul>
4794 </ul></li>
4797 <ul>
4799 </ul></li>
4802 <ul>
4805 </ul></li>
4808 <ul>
4810 </ul></li>
4813 <ul>
4815 </ul></li>
4818 <ul>
4820 </ul></li>
4823 <ul>
4825 </ul></li>
4828 <ul>
4830 </ul></li>
4833 <ul>
4837 </ul></li>
4840 <ul>
4842 </ul></li>
4845 <ul>
4847 </ul></li>
4849 <li>Barrie Leslie
4850 <ul>
4852 </ul></li>
4855 <ul>
4857 </ul></li>
4860 </ul>
4862 <p>
4863 And also to the following people who have contributed minor changes,
4864 enhancements, bugfixes or support for a new language since version 2.1.0:
4865 </p>
4867 <p>
4868 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4869 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4870 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4871 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4873 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4874 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4875 Luís V., Martijn W. van der Lee,
4876 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4878 </p>
4883 <p>
4884 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4885 to create a web-based interface to MySQL using PHP3. Although I have not
4886 used any of his source-code, there are some concepts I've borrowed from
4887 him. phpMyAdmin was created because Peter told me he wasn't going to
4888 further develop his (great) tool.
4889 </p>
4890 <p>
4891 Thanks go to
4892 </p>
4893 <ul>
4895 code for the check when dropping a table or database. He also suggested
4896 that you should be able to specify the primary key on tbl_create.php3. To
4897 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4898 well as a bug-report. Plus many smaller improvements.
4899 </li>
4901 were introduced in 1.3.0 (including quite significant ones like the
4902 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4903 bug-fixes and help.
4904 </li>
4906 language-independent by outsourcing the strings to a separate file. He
4907 also contributed the French translation.
4908 </li>
4910 tbl_select.php3, a feature to display only some columns from a table.
4911 </li>
4913 functions in tbl_change.php3. He also added the
4915 </li>
4917 servers and is a regular contributor for bug-fixes.
4918 </li>
4920 features for 2.0.6.
4921 </li>
4922 </ul>
4923 <p>
4924 The following people have contributed minor changes, enhancements, bugfixes
4925 or support for a new language:
4926 </p>
4927 <p>
4928 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4929 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4930 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4931 G. Wieggers.
4932 </p>
4933 <p>
4934 And thanks to everyone else who sent me email with suggestions, bug-reports
4935 and or just some feedback.
4936 </p>
4942 <ul>
4944 - the default name of Apache's directory-level configuration file.</li>
4948 - a software application that enables a user to display and interact with
4949 text, images, and other information typically located on a web page at a
4950 website on the World Wide Web.</li>
4952 - a free software/open source data compression algorithm and program
4953 developed by Julian Seward.</li>
4955 - an important World Wide Web technology that enables a client web browser
4956 to request data from a program executed on the Web server.</li>
4958 - a log or record of changes made to a project.</li>
4960 - a computer system that accesses a (remote) service on another computer
4961 by some kind of network.</li>
4963 - a set of data values of a particular simple type, one for each row of
4964 the table.</li>
4966 - a packet of information sent by a server to a World Wide Web browser
4967 and then sent back by the browser each time it accesses that server.</li>
4969 - Comma-separated values</li>
4972 - an organized collection of data.</li>
4975 - a PHP module that extends PHP with additional functionality.</li>
4977 - a list of commonly asked question and there answers.</li>
4979 - one part of divided data/columns.</li>
4981 - a field or group of fields in a database record that point to a key
4982 field or group of fields forming a key of another database record in some
4983 (usually different) table.</li>
4985 - the free PDF library</li>
4987 GD Graphics Library</a> - a library by Thomas Boutell and others for
4988 dynamically manipulating images.</li>
4991 - gzip is short for GNU zip, a GNU free software file compression
4992 program.</li>
4994 - any machine connected to a computer network, a node that has a hostname.</li>
4996 - the unique name by which a network attached device is known on a network.</li>
4998 (HyperText Transfer Protocol)</a>
4999 - the primary method used to transfer or convey information on the World
5000 Wide Web.</li>
5003 additional security measures.</li>
5004 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5005 - a set of Internet-based services for servers using Microsoft Windows.</li>
5007 - a feature that allows quick access to the rows in a table.</li>
5009 - a data-oriented protocol used by source and destination hosts for
5010 communicating data across a packet-switched internetwork.</li>
5012 - a unique number that devices use in order to identify and communicate
5013 with each other on a network utilizing the Internet Protocol standard.</li>
5015 (Internet Server Application Programming Interface)</a>
5016 - the API of Internet Information Services (IIS).</li>
5018 - a business or organization that offers users access to the Internet and related services.</li>
5020 - a most commonly used standard method of lossy compression for
5021 photographic images.</li>
5027 - line of personal computers is designed, developed, manufactured, and
5028 marketed by Apple Computer.</li>
5029 <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>
5030 - the operating system which is included with all currently shipping Apple
5031 Macintosh computers in the consumer and professional markets.</li>
5033 - a cryptographic library.</li>
5035 - the MCrypt PHP extension.</li>
5036 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5037 - an Internet Standard for the format of e-mail.</li>
5039 - some sort of extension for the Apache Webserver.</li>
5041 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5042 Management System (DBMS).</li>
5044 - the improved MySQL client PHP extension.</li>
5046 - the MySQL client PHP extension.</li>
5048 - open standard for office documents.</li>
5049 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5050 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5052 (Portable Document Format)</a>
5053 - a file format developed by Adobe Systems for representing two
5054 dimensional documents in a device independent and resolution independent
5055 format.</li>
5057 - the PHP Extension and Application Repository.</li>
5059 - the perl-compatible regular expression functions for PHP</li>
5061 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5062 programming language used mainly for developing server-side applications
5063 and dynamic web content, and more recently, a broader range of software
5064 applications.</li>
5066 - a connection through which data is sent and received.</li>
5068 - Request for Comments (RFC) documents are a series of memoranda
5069 encompassing new research, innovations, and methodologies applicable to
5070 Internet technologies.</li>
5074 - represents a single, implicitly structured data item in a table.</li>
5076 - a computer system that provides services to other computing
5077 systems over a network.</li>
5078 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5079 - handlers for different table types</li>
5081 - a form of inter-process communication.</li>
5083 Sockets Layer)</a>
5084 - a cryptographic protocol which provides secure communication on the Internet.</li>
5086 - Structured Query Language</li>
5088 - a set of data elements (cells) that is organized, defined and stored as
5089 horizontal rows and vertical columns where each item can be uniquely
5090 identified by a label or key or by it?s position in relation to other items.</li>
5093 - a type of archive file format: the Tape ARchive format.</li>
5095 - one of the core protocols of the Internet protocol suite.</li>
5099 - a sequence of characters, conforming to a standardized format, that is
5100 used for referring to resources, such as documents and images on the
5101 Internet, by their location.</li>
5103 - A computer (program) that is responsible for accepting HTTP requests
5104 from clients and serving them Web pages.</li>
5106 - a W3C-recommended general-purpose markup language for creating
5107 special-purpose markup languages, capable of describing many different
5108 kinds of data.</li>
5110 - a popular data compression and archival format.</li>
5112 - an open-source, cross-platform data compression library by Jean-loup
5113 Gailly and Mark Adler.</li>
5114 </ul>
5115 </div>
5118 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5121 <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>
5122 </ul>
5124 </body>
5125 </html>