| blob | 1e11f8d6e3c307519d67273db9e674dd37c16c33 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <head>
14 </head>
18 <h1>
20 3.4.5-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,
122 </li>
123 <li>import data and MySQL structures from OpenDocument spreadsheets, as well as <abbr title="Extensible Markup Language">XML</abbr>, <abbr title="Comma Separated Values">CSV</abbr>, and <abbr title="Server Query Language">SQL</abbr> files</li>
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.
1283 </dd>
1285 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1286 </dd>
1288 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1289 </dd>
1292 <dd>If you have more than one server configured, you can set
1294 that server when phpMyAdmin is started, or set it to 0 to be given a
1295 list of servers without logging in.<br />
1297 MUST be set to that server.</dd>
1300 <dd>Defines whether to refresh only parts of certain pages using Ajax
1301 techniques. Applies only where a non-Ajax behavior is possible;
1302 for example, the Designer feature is Ajax-only so this directive
1303 does not apply to it.</dd>
1306 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1307 page.</dd>
1310 <dd>The maximum number of database names to be displayed in the
1311 navigation frame and the database list.</dd>
1314 <dd>The maximum number of table names to be displayed in the
1315 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1316 when in Light mode.</dd>
1319 <dd>The maximum number of characters when a SQL query is displayed. The
1320 default limit of 1000 should be correct to avoid the display of tons
1321 of hexadecimal codes that represent BLOBs, but some users have real
1322 SQL queries that are longer than 1000 characters. Also, if a query's
1323 length exceeds this limit, this query is not saved in the history.</dd>
1326 <dd>Defines whether to use GZip output buffering for increased
1328 Set to true/false for enabling/disabling. When set to 'auto' (string),
1329 phpMyAdmin tries to enable output buffering and will automatically disable
1330 it if your browser has some problems with buffering. IE6 with a certain patch
1331 is known to cause data corruption when having enabled buffering.</dd>
1334 <dd>Whether persistent connections should be used or not (mysql_connect or
1335 mysql_pconnect).</dd>
1341 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1342 to zero, no time limit is imposed.<br />
1343 This setting is used while importing/exporting dump files and in the
1344 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1351 <dd>Set the number of bytes a script is allowed to allocate. If set
1352 to zero, no limit is imposed.<br />
1353 This setting is used while importing/exporting dump files and at some
1354 other places in phpMyAdmin so you definitely don't want to put here
1355 a too low value. It has no effect when PHP is running in safe mode.<br />
1356 You can also use any string as in php.ini, eg. '16M'. Ensure
1360 <dd>Mark used tables and make it possible to show databases with locked
1365 generated by phpMyAdmin should be displayed or not.</dd>
1368 <dd>Defines whether normal users (non-administrator) are allowed to
1369 delete their own database or not. If set as FALSE, the link "Drop
1371 mydatabase" will be rejected. Quite practical for
1373 customers.<br />
1374 Please note that this limitation of SQL queries is not as strict as
1375 when using MySQL privileges. This is due to nature of SQL queries
1376 which might be quite complicated. So this choice should be viewed as
1377 help to avoid accidental dropping rather than strict privilege
1378 limitation.</dd>
1382 displayed when you're about to lose data.</dd>
1385 <dd>Define whether the previous login should be recalled or not in cookie
1386 authentication mode.<br /><br />
1388 This is automatically disabled if you do not have configured
1390 </dd>
1393 <dd>Define how long is login cookie valid. Please note that php
1394 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1395 might limit session validity and if session is lost, login cookie is
1397 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1401 means that it will be kept for existing session. This is recommended
1402 for not trusted environments.</dd>
1405 <dd>If enabled (default), logout deletes cookies for all servers,
1406 otherwise only for current one. Setting this to false makes it easy to
1407 forget to log out from other server, when you are using more of
1408 them.</dd>
1414 <dd>Define whether phpMyAdmin will continue executing a multi-query
1415 statement if one of the queries fails. Default is to abort execution.</dd>
1418 <dd>Define whether phpMyAdmin will output the results of each query of a
1419 multi-query statement embedded into the
1424 <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.
1425 <br /><br />
1428 MySQL servers behind the firewall where your
1430 </dd>
1439 <dd>Defines whether to use a select-based menu and display only the current
1440 tables in the left frame (smaller page). Only in Non-Lightmode you can
1441 use the feature to display nested folders using
1443 </dd>
1446 <dd>In light mode, defines whether to display the names of databases (in the
1447 selector) using a tree, see also
1449 </dd>
1452 string or array</dt>
1453 <dd>The string used to separate the parts of the database name when showing
1454 them in a tree. Alternatively you can specify more strings in an array
1455 and all of them will be used as a separator.</dd>
1458 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1459 This means if you have tables like 'first__second__third' this will be
1461 If set to FALSE or empty, the feature is disabled. NOTE: You should
1462 not use this separator at the beginning or end of a
1463 table name or multiple times after another without any other
1464 characters in between.</dd>
1467 <dd>Defines how many sublevels should be displayed when splitting
1468 up tables by the above separator.</dd>
1471 <dd>Defines whether to display table comment as tool-tip in left frame or
1472 not.</dd>
1475 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1476 comment and the real name. That means that if you have a table called
1477 'user0001' and add the comment 'MyName' on it, you will see the name
1478 'MyName' used consequently in the left frame and the tool-tip shows
1479 the real name of the DB.</dd>
1482 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1484 When setting this to 'nested', the Alias of the Tablename is only used
1485 to split/nest the tables according to the
1487 directive. So only the folder is called like the Alias, the tablename itself
1488 stays the real tablename.</dd>
1491 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1494 <dd>Enter URL where logo in the navigation frame will point to.
1495 For use especially with self made theme which changes this.
1504 integer</dt>
1505 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1506 list of tables in the left frame.
1511 <dd>Defines whether or not to display a server choice at the top of the left frame.
1512 Defaults to FALSE.</dd>
1514 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1515 Defaults to FALSE (drop-down).</dd>
1517 <dd>Defines whether to display database choice in light navigation frame as links
1518 instead of in a drop-down. Defaults to 'auto' - on main page list is
1519 shown, when database is selected, only drop down is displayed.</dd>
1522 <dd>Defines the tab displayed by default when clicking the small
1523 icon next to each table name in the navigation panel. Possible
1529 <dd>Defines whether or not to display space usage and statistics about databases
1530 and tables.<br />
1531 Note that statistics requires at least MySQL 3.23.3 and that, at this
1532 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1535 <dd>Defines whether to display detailed server information on main page.
1536 You can additionally hide more information by using
1538 </dd>
1543 </dt>
1546 not at the starting main (right) frame. This setting
1547 does not check MySQL commands entered directly.<br /><br />
1549 Please note that to block the usage of phpinfo() in scripts, you
1556 hard coded password value in the configuration file, end users can't
1557 be allowed to change their passwords.</dd>
1560 <dd>Defines whether to suggest a database name on the
1564 <dd>Defines whether navigation bar buttons and the right panel top menu
1565 contain text or symbols only. A value of TRUE displays icons, FALSE
1566 displays text and 'both' displays both icons and text.</dd>
1569 <dd>Defines whether a user should be displayed a
1573 <dd>Number of rows displayed when browsing a result set. If the result set
1580 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1584 option is ticked by default.</dd>
1588 from editing when browsing a table's content. Valid values are:
1593 </ul>
1594 </dd>
1597 <dd>Defines whether or not MySQL functions fields should be initially
1598 displayed in edit/insert mode. Since version 2.10, the user can
1599 toggle this setting from the interface.
1600 </dd>
1603 <dd>Defines whether or not type fields should be initially
1604 displayed in edit/insert mode. The user can
1605 toggle this setting from the interface.
1606 </dd>
1609 <dd>Defines which type of editing controls should be used for CHAR and
1610 VARCHAR columns. Possible values are:
1611 <ul><li>input - this allows to limit size of text to size of columns in
1612 MySQL, but has problems with newlines in columns</li>
1613 <li>textarea - no problems with newlines in columns, but also no
1614 length limitations</li>
1615 </ul>
1616 Default is old behavior so input.</dd>
1622 <dd>If there are fewer items than this in the set of foreign keys, then a
1623 drop-down box of foreign keys is presented, in the style described by the
1625 setting.</dd>
1628 <dd>For the foreign key drop-down fields, there are several methods of
1629 display, offering both the key and value data. The contents of the
1630 array should be one or both of the following strings:
1636 </dt>
1637 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1638 creating a dump file</dd>
1641 </dt>
1642 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1643 compressed exports. This doesn't affect smaller dumps and allows users to
1644 create larger dumps that won't otherwise fit in memory due to php
1645 memory limit. Produced files contain more GZip/BZip2 headers, but all
1646 normal programs handle this correctly.</dd>
1650 mainframe.</dd>
1654 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1659 <dd>How many columns will be utilized to display the tables on the
1660 database property view? Default is 1 column. When setting this to a
1661 value larger than 1, the type of the database will be omitted for more
1662 display space.</dd>
1666 <dd>Defines the tab displayed by default on server view. Possible
1673 <dd>Defines the tab displayed by default on database view. Possible
1678 <dd>Defines the tab displayed by default on table view. Possible
1685 points to the MySQL documentation (type depends
1686 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1687 generated.<br />
1689 for more information about MySQL manuals and their types.</dd>
1692 <dd>Type of MySQL documentation:
1698 </ul>
1699 </dd>
1702 <dd>Defines the default language to use, if not browser-defined or
1703 user-defined.<br />
1704 The corresponding language file needs to be in
1706 </dd>
1709 <dd>Defines the default connection collation to use, if not
1710 user-defined.<br />
1716 The corresponding language file needs to be in
1718 </dd>
1721 <dd>Limit list of available languages to those matching the given regular
1722 expression. For example if you want only Czech and English, you should
1726 <dd>You can select here which functions will be used for character set
1727 conversion. Possible values are:
1728 <ul><li>auto - automatically use available one (first is tested
1729 iconv, then recode)</li>
1733 </ul>
1734 Default is auto.</dd>
1735 <dd>
1736 Enabled charset conversion activates a pull-down menu
1737 in the Export and Import pages, to choose the character set when
1738 exporting a file. The default value in this menu comes from
1740 </dd>
1743 <dd>Specify some parameters for iconv used in charset conversion. See
1746 used, so that invalid characters will be transliterated.</dd>
1749 <dd>Available character sets for MySQL conversion. You can add your own (any of
1750 supported by recode/iconv) or remove these which you don't use.
1751 Character sets will be shown in same order as here listed, so if you
1752 frequently use some of these move them to the top.</dd>
1757 default empty, you need to fill in some trusted proxy servers if you
1758 want to use rules for IP addresses behind proxy.<br /><br />
1760 The following example specifies that phpMyAdmin should trust a
1762 <pre>
1763 $cfg['TrustedProxies'] =
1765 </pre>
1766 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1767 client's IP address as usual.
1768 </dd>
1772 MIME transformations.<br />
1773 Possible values are:
1774 <ul><li>auto - automatically detect, this is a bit expensive
1776 according to your server real possibilities</li>
1779 </ul>
1780 Default is auto.
1781 </dd>
1784 <dd>
1785 We normally check the permissions on the configuration file to ensure
1786 it's not world writable. However, phpMyAdmin could be installed on
1787 a NTFS filesystem mounted on a non-Windows server, in which case the
1788 permissions seems wrong but in fact cannot be detected. In this case
1790 </dd>
1793 <dd>
1794 Limit for length of URL in links. When length would be above this limit, it
1795 is replaced by form with button.
1796 This is required as some web servers (IIS) have problems with long URLs.
1798 </dd>
1802 </dd>
1804 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1806 </dt>
1807 <dd>The background styles used for both the frames.
1810 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1812 <dd>The style used for the pointer in the navi frame.
1821 </dd>
1825 <dd>The style used for table headers. See
1830 </dd>
1834 </dd>
1836 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1838 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1840 </dt>
1842 The former feature highlights the row over which your mouse is passing
1843 and the latter lets you visually mark/unmark rows by clicking on
1844 them. Highlighting / marking a column is done by hovering over /
1845 clicking the column's header (outside of the text).<br />
1850 <dd>You put here a valid CSS font family value, for example
1855 <dd>You put here a valid CSS font family value, for example
1869 </dt>
1871 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1873 The Char* values are used for CHAR and VARCHAR editing (if configured
1877 </dt>
1881 </dt>
1882 <dd>Defines if the whole textarea of the query box will be selected on
1883 click.</dd>
1886 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1887 Can be turned off by a toggle button on the browse page.</dd>
1891 </dt>
1892 <dd>Defines the place where table row links (Edit, Inline edit, Copy,
1893 Delete) would be put when
1894 tables contents are displayed (you may have them displayed both at the
1895 left and at the right).
1901 Define which one is displayed by default. The first mode displays each
1902 row on a horizontal line, the second rotates the headers by 90
1903 degrees, so you can use descriptive headers even though columns only
1904 contain small values and still print them out. The vertical mode sorts
1905 each row on a vertical lineup.
1906 </dd>
1909 <dd>
1910 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1911 'css' the rotation of the header for horizontalflipped is done via
1912 CSS. The CSS transformation currently works only in Internet
1913 Explorer.If set to 'fake' PHP does the transformation for you, but of
1914 course this does not look as good as CSS. The 'auto' option enables
1915 CSS transformation when browser supports it and use PHP based one
1916 otherwise.
1917 </dd>
1921 string or integer</dt>
1922 <dd>When editing/creating new columns in a table all fields normally get
1923 lined up one field a line. (default: 'horizontal'). If you set this to
1924 'vertical' you can have each field lined up vertically beneath each
1925 other. You can save up a lot of place on the horizontal direction and
1926 no longer have to scroll. If you set this to integer, editing of fewer
1927 columns will appear in 'vertical' mode, while editing of more columns
1928 still in 'horizontal' mode. This way you can still effectively edit
1929 large number of columns, while having full view on few of them.</dd>
1933 </dt>
1935 display of column comments in Browse or Property display. In browse
1936 mode, the comments are shown inside the header. In property mode,
1937 comments are displayed using a CSS-formatted dashed-line below the
1938 name of the column. The comment is shown as a tool-tip for that column.
1939 </dd>
1951 <dd>Whether to display a link to validate a query in any SQL Query box.
1958 <dd>
1959 The name of the directory where
1961 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1962 are available under a drop-down box when you click the database or
1963 table name, then the Import tab.
1964 <br /><br />
1966 If you want different directory for each user, %u will be replaced
1967 with username.<br /><br />
1971 compressed formats is enabled).<br /><br />
1973 This feature is useful when your file is too big to be uploaded via
1975 uploads are disabled in PHP.<br /><br />
1977 Please note that if PHP is running in safe mode, this directory must
1978 be owned by the same user as the owner of the phpMyAdmin scripts.
1979 <br /><br />
1983 alternatives.
1984 </dd>
1987 <dd>
1988 The name of the directory where dumps can be saved.<br /><br />
1990 If you want different directory for each user, %u will be replaced
1991 with username.<br /><br />
1993 Please note that the directory must exist and has to be writable for
1994 the user running webserver.<br /><br />
1996 Please note that if PHP is running in safe mode, this directory must
1997 be owned by the same user as the owner of the phpMyAdmin scripts.
1998 </dd>
2001 <dd>
2002 The name of the directory where temporary files can be stored.
2003 <br /><br />
2006 for uploaded files, see
2009 <br /><br />
2011 If the directory where phpMyAdmin is installed is subject to an
2013 temporary directory in some directory accessible by the web
2014 server. However for security reasons, this directory should be outside
2015 the tree published by webserver. If you cannot avoid having this
2016 directory published by webserver, place at least an empty
2018 possible.
2019 <br /><br />
2021 This directory should have as strict permissions as possible as the only
2022 user required to access this directory is the one who runs the
2023 webserver. If you have root privileges, simply make this user owner of
2024 this directory and make it accessible only by it:
2025 <br /><br />
2027 <pre>
2028 chown www-data:www-data tmp
2029 chmod 700 tmp
2030 </pre>
2032 If you cannot change owner of the directory, you can achieve a similar
2035 <pre>
2036 chmod 700 tmp
2037 setfacl -m "g:www-data:rwx" tmp
2038 setfacl -d -m "g:www-data:rwx" tmp
2039 </pre>
2041 If neither of above works for you, you can still make the directory
2043 system reading and writing data in this directory.
2044 </dd>
2047 <dd>
2048 In this array are defined default parameters for export, names of
2049 items are similar to texts seen on export page, so you can easily
2050 identify what they mean.
2051 </dd>
2054 <dd>
2055 Defines how the export form is displayed when it loads. Valid values are:
2056 <ul>
2059 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2060 </ul>
2061 </dd>
2064 <dd>
2065 In this array are defined default parameters for import, names of
2066 items are similar to texts seen on import page, so you can easily
2067 identify what they mean.
2068 </dd>
2071 <dd>
2072 Repeat the headers every X cells, or 0 to deactivate.
2073 </dd>
2081 </dt>
2082 <dd>
2083 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2084 or icon is always displayed on the left panel. If JavaScript is enabled in
2085 your browser, a click on this opens a distinct query window, which is
2086 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2087 changes to display a query box.<br /><br />
2089 The size of this query window can be customized with
2091 - both integers for the size in pixels. Note that normally, those
2093 theme you are using.<br /><br />
2097 opens the query window and puts the current query
2098 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2099 query in the right panel's query box.
2100 <br /><br />
2101 The usage of the JavaScript query window is recommended if you have a
2102 JavaScript enabled browser. Basic functions are used to exchange quite
2103 a few variables, so most 4th generation browsers should be capable to
2104 use that feature. It currently is only tested with Internet Explorer 6
2105 and Mozilla 1.x.
2106 <br /><br />
2108 to a table, which has to be created by you (see <a
2110 all your queries will be appended to the form, but only as long as
2111 your window is opened they remain saved.
2112 <br /><br />
2113 When using the JavaScript based query window, it will always get
2114 updated when you click on a new table/db to browse and will focus if
2115 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2116 the query window by checking the box "Do not overwrite this query from
2117 outside the window" below the query textarea. Then you can browse
2118 tables/databases in the background without losing the contents of the
2119 textarea, so this is especially useful when composing a query with
2120 tables you first have to look in. The checkbox will get automatically
2121 checked whenever you change the contents of the textarea. Please
2122 uncheck the button whenever you definitely want the query window to
2123 get updated even though you have made alterations.
2124 <br /><br />
2127 <br /><br />
2128 The query window also has a custom tabbed look to group the features.
2130 default tab to be used when opening the query window. It can be set to
2131 either 'sql', 'files', 'history' or 'full'.</dd>
2137 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2139 If the approximate row count as returned by
2142 count will be used.
2143 </dd>
2145 <dd>For VIEWs, since obtaining the exact count could have an
2146 impact on performance, this value is the maximum to be displayed, using
2148 any row counting.
2149 </dd>
2152 <dd>Sorts database and table names according to natural order (for example,
2153 t1, t2, t10). Currently implemented in the left panel (Light mode)
2154 and in Database view, for the table list.</dd>
2163 that users can't set through user preferences. For possible values, refer
2170 <dd>Allows you to specify window's title bar. You can use
2172 </dd>
2182 </dd>
2185 <dd>If theme manager is active, use this as the path of the subdirectory
2186 containing all the themes.</dd>
2200 </dt>
2201 <dd>Default queries that will be displayed in query boxes when user didn't
2202 specify any. You can use standard
2204 </dd>
2207 <dd>
2208 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
2209 default we use HTML to format the query, but you can disable this by
2211 </dd>
2214 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2215 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2216 query inside a bracket is indented. By changing
2219 specifies the units of the indent amount that you specified. This is
2220 used via stylesheets.</dd>
2223 <dd>This array is used to define the colours for each type of element of
2224 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2226 If you specify an empty string for the color of a class, it is ignored
2227 in creating the stylesheet.
2228 You should not alter the class names, only the colour strings.<br />
2249 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2253 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2254 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2255 </ul>
2256 </dd>
2260 <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,
2261 as originally published on
2263 <br />
2264 For help in setting up your system to use the service, see the
2266 </dd>
2270 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2271 and any password, so we use those by default. Instead, if
2272 you have an account with them, you can put your login details
2273 here, and it will be used in place of the anonymous login.</dd>
2274 </dl>
2275 </dd>
2278 <dd><b>DEVELOPERS ONLY!</b></dd>
2281 <dd><b>DEVELOPERS ONLY!</b><br />
2282 Enable logging queries and execution times to be displayed in the bottom
2283 of main page (right frame).</dd>
2286 <dd>All possible types of a MySQL column. In most cases you don't need to
2287 edit this.</dd>
2290 <dd>Possible attributes for columns. In most cases you don't need to edit
2291 this.</dd>
2294 <dd>A list of functions MySQL supports. In most cases you don't need to
2295 edit this.</dd>
2298 <dd>Mapping of column types to meta types used for preferring displayed
2299 functions. In most cases you don't need to edit this.</dd>
2302 <dd>Functions preferred for column meta types as defined in
2303 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2304 to edit this.</dd>
2307 <dd>Functions selected by default when inserting/changing row, Functions
2308 are defined for meta types from
2310 <code>first_timestamp</code>, which is used for first timestamp column
2311 in table.</dd>
2314 <dd>Operators available for search operations on numeric and date columns.
2315 </dd>
2318 <dd>Operators available for search operations on character columns.
2319 Note that we put <code>LIKE</code> by default instead of
2320 <code>LIKE %...%</code>, to avoid unintended performance problems
2321 in case of huge tables.</dd>
2324 <dd>Operators available for search operations on ENUM columns.</dd>
2327 <dd>Additional operators available for search operations when the
2328 column can be null.</dd>
2330 </dl>
2332 <!-- TRANSFORMATIONS -->
2338 </ol>
2342 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2344 section</a> on how to do so.</p>
2346 <p> You can apply different transformations to the contents of each column. The
2347 transformation will take the content of each column and transform it with
2348 certain rules defined in the selected transformation.</p>
2350 <p> Say you have a column 'filename' which contains a filename. Normally you would
2351 see in phpMyAdmin only this filename. Using transformations you can transform
2352 that filename into a HTML link, so you can click inside of the phpMyAdmin
2353 structure on the column's link and will see the file displayed in a new browser
2354 window. Using transformation options you can also specify strings to
2355 append/prepend to a string or the format you want the output stored in.</p>
2357 <p> For a general overview of all available transformations and their options,
2358 you can consult your
2359 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2360 installation.</p>
2362 <p> For a tutorial on how to effectively use transformations, see our
2364 the official phpMyAdmin homepage.</p>
2368 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2369 clicking on the 'Structure' link for a table). There click on
2370 "Change" (or change icon) and there you will see three new
2371 fields at
2372 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2373 'Transformation options'.</p>
2375 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2376 that corresponds to the column's contents. Please note that
2377 transformations are inactive as long as no MIME-type is selected.</li>
2379 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2380 hopefully growing amount of pre-defined transformations. See below for information on
2381 how to build your own transformation.<br />
2383 There are global transformations and mimetype-bound transformations. Global transformations
2384 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2385 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2386 transformations which operate on the main mimetype (like 'image'), which will most likely
2387 take the subtype into regard, and those who only operate on a
2388 specific subtype (like 'image/jpeg').<br />
2390 You can use transformations on mimetypes for which the function was not defined for. There
2391 is no security check for you selected the right transformation, so take care of what the
2392 output will be like.</li>
2394 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2395 transform-function specific options here. Usually the transforms can operate with default
2396 options, but it is generally a good idea to look up the overview to see which options are
2397 necessary.<br />
2399 Much like the ENUM/SET-Fields, you have to split up several options using the format
2400 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2401 parsed as an array, leaving the first value the first element in the array, and so
2402 forth.<br />
2404 If you want to specify a MIME character set you can define it in the transformation_options.
2405 You have to put that outside of the pre-defined options of the specific mime-transform,
2407 for which you can specify 2 options and you want to append a character set, enter "'first
2408 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2410 </ul>
2414 <p> All mimetypes and their transformations are defined through single files in
2415 the directory 'libraries/transformations/'.</p>
2417 <p> They are stored in files to ease up customization and easy adding of new
2418 transformations.</p>
2420 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2421 always work. It makes no sense to apply a transformation to a mimetype the
2422 transform-function doesn't know to handle.</p>
2424 <p> One can, however, use empty mime-types and global transformations which should work
2425 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2426 for, but pay attention to option usage as well as what the transformation does to your
2427 column.</p>
2429 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2430 any other transform function and provides some basic functions.</p>
2432 <p> There are 5 possible file names:</p>
2434 <ol><li>A mimetype+subtype transform:<br /><br />
2436 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2438 Please not that mimetype and subtype are separated via '_', which shall
2439 not be contained in their names. The transform function/filename may
2440 contain only characters which cause no problems in the file system as
2441 well as the PHP function naming convention.<br /><br />
2443 The transform function will the be called
2444 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2446 <b>Example:</b><br /><br />
2448 <tt>text_html__formatted.inc.php</tt><br />
2449 <tt>PMA_transform_text_html__formatted()</tt></li>
2451 <li>A mimetype (w/o subtype) transform:<br /><br />
2453 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2455 Please note that there are no single '_' characters.
2456 The transform function/filename may contain only characters which cause
2457 no problems in the file system as well as the PHP function naming
2458 convention.<br /><br />
2460 The transform function will the be called
2461 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2463 <b>Example:</b><br /><br />
2465 <tt>text__formatted.inc.php</tt><br />
2466 <tt>PMA_transform_text__formatted()</tt></li>
2468 <li>A mimetype+subtype without specific transform function<br /><br />
2470 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2472 Please note that there are no '__' characters in the filename. Do not
2473 use special characters in the filename causing problems with the file
2474 system.<br /><br />
2476 No transformation function is defined in the file itself.<br /><br />
2478 <b>Example:</b><br /><br />
2480 <tt>text_plain.inc.php</tt><br />
2481 (No function)</li>
2483 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2485 <tt>[mimetype].inc.php</tt><br /><br />
2487 Please note that there are no '_' characters in the filename. Do not use
2488 special characters in the filename causing problems with the file system.
2489 <br /><br />
2491 No transformation function is defined in the file itself.<br /><br />
2493 <b>Example:</b><br /><br />
2495 <tt>text.inc.php</tt><br />
2496 (No function)</li>
2498 <li>A global transform function with no specific mimetype<br /><br />
2500 <tt>global__[transform].inc.php</tt><br /><br />
2502 The transform function will the be called
2503 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2505 <b>Example:</b><br /><br />
2507 <tt>global__formatted</tt><br />
2508 <tt>PMA_transform_global__formatted()</tt></li>
2509 </ol>
2511 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2512 transform function.</p>
2514 <p> All filenames containing no '__' in themselves are not shown as valid transform
2515 functions in the dropdown.</p>
2517 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2518 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2519 without a transform function.</p>
2521 <p> To create a new transform function please see
2522 <tt>libraries/transformations/template_generator.sh</tt>.
2523 To create a new, empty mimetype please see
2524 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2526 <p> A transform function always gets passed three variables:</p>
2528 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2529 you want to transform.</li>
2530 <li><b>$options</b> - Contains any user-passed options to a transform function
2531 as an array.</li>
2532 <li><b>$meta</b> - Contains an object with information about your column.
2533 The data is drawn from the output of the
2535 function. This means, all object properties described on the
2537 available in this variable and can be used to transform a column accordingly
2538 to unsigned/zerofill/not_null/... properties.<br />
2539 The $meta->mimetype variable contains the original MIME-type of the
2540 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2541 </ol>
2543 <p> Additionally you should also provide additional function to provide
2544 information about the transformation to the user. This function should
2545 have same name as transformation function just with appended
2546 <code>_info</code> suffix. This function accepts no parameters and returns
2547 array with information about the transformation. Currently following keys
2548 can be used:
2549 </p>
2550 <dl>
2551 <dt><code>info</code></dt>
2552 <dd>Long description of the transformation.</dd>
2553 </dl>
2555 <!-- FAQ -->
2562 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2567 </ol>
2569 <p> Please have a look at our
2571 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2572 features and or interface.</p>
2578 action is required or phpMyAdmin sends a blank page or a page full of
2579 cryptic characters to my browser, what can I do?</a></h4>
2582 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2583 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2584 configuration file.<br /></p>
2589 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2590 See also the
2592 entry about PHP bugs with output buffering.<br />
2593 If your server keeps crashing, please ask for help in the various Apache
2594 support groups.</p>
2603 application misbehaved by not returning a complete set of
2605 </h4>
2607 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2608 Have a look at the last message in this
2610 official PHP bug database.</p>
2615 and/or many error messages with the
2618 <p> This is a known problem with the PHP
2620 filter: it's not so stable. Please use instead the cookie authentication mode.
2621 </p>
2626 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2627 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2628 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2629 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2630 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2635 work.</a></h4>
2637 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2638 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2639 or not, and so on). So, you must have Zlib/Bzip2
2640 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2644 an error about safe mode being in effect.</a></h4>
2646 <p> Your uploaded file is saved by PHP in the "upload dir", as
2647 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2648 the system default is <i>/tmp</i>).<br />
2649 We recommend the following setup for Apache servers running in safe mode,
2650 to enable uploads of files while being reasonably secure:</p>
2652 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2653 <li>give ownership to the Apache server's user.group:
2654 <tt>chown apache.apache /tmp/php</tt></li>
2655 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2656 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2657 <li>restart Apache</li>
2658 </ul>
2665 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2666 I'm using the Apache server.</a></h4>
2668 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2669 your <i>httpd.conf</i>:</p>
2673 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2677 uploading a file from the query box.</a></h4>
2679 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2680 restrictions. However you need to create temporary directory and
2682 The uploaded files will be moved there, and after execution of your
2688 <p> The MySQL manual explains how to
2690 reset the permissions</a>.</p>
2700 </h4>
2702 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2703 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2704 names to align with current standards.</p>
2709 </h4>
2711 <p> Starting with version 2.7.0, the import engine has been re–written and these
2712 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2713 to take advantage of the new import features.</p>
2715 <p> The first things to check (or ask your host provider to check) are the
2716 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2717 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2718 All of these three settings limit the maximum size of data that can be
2719 submitted and handled by PHP. One user also said that post_max_size
2720 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2722 There exist several workarounds if your upload is too big or your
2723 hosting provider is unwilling to change the settings:</p>
2726 feature. This allows one to
2727 upload a file to the server via scp, ftp, or your favorite file transfer
2728 method. PhpMyAdmin is then able to import the files from the temporary
2730 section</a> of this document.</li>
2732 BigDump</a>) to split the files before uploading. We cannot support this
2733 or any third party applications, but are aware of users having success
2734 with it.</li>
2735 <li>If you have shell (command line) access, use MySQL to import the files
2736 directly. You can do this by issuing the "source" command from
2737 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2738 </ul>
2742 support?</a></h4>
2744 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2745 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2746 connect to your MySQL server using PHP's classic
2749 is available in php 5.0. The latter one should be used unless you have a
2750 good reason not to do so.<br />
2751 When compiling PHP, we strongly recommend that you manually link the MySQL
2752 extension of your choice to a MySQL client library of at least the same
2753 minor version since the one that is bundled with some PHP distributions is
2756 MariaDB is also supported (versions 5.1 and 5.2 were tested).
2757 </p>
2761 message, "Client does not support authentication protocol requested
2762 by server; consider upgrading MySQL client"</a></h5>
2764 <p> You tried to access MySQL with an old MySQL client library. The version of
2765 your MySQL client library can be checked in your phpinfo() output.
2766 In general, it should have at least the same minor version as your server
2770 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2771 changed the authentication hash and your PHP is trying to use the old method.
2773 with the proper client library to match your MySQL installation. Your
2774 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2775 More information (and several workarounds) are located in the
2777 </p>
2784 script seems not to know the font face I'm using!</a></h4>
2786 <p> The "FPDF" library we're using for this feature requires some
2787 special files to use font faces.<br />
2789 these files.</p>
2793 check PHP Configuration".</a></h4>
2795 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2796 "MySQL extension". This extension may be part of the PHP
2797 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2798 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2799 to load the extension but failed.<br /><br />
2801 Usually, the problem is solved by installing a software package called
2802 "PHP-MySQL" or something similar.</p>
2807 and I cannot log in using cookie auth.</a></h4>
2809 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2813 so I cannot upload.</a></h4>
2815 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2816 parameter is not set to "on".</p>
2820 a new table the table and column names are changed to lowercase!</a></h4>
2822 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2823 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2824 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2825 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2826 directory and add the following line to the group [mysqld]:</p>
2828 <pre>set-variable = lower_case_table_names=0</pre>
2830 <p> Next, save the file and restart the MySQL service. You can always check the
2831 value of this directive using the query</p>
2833 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2840 and I get problems, such as undefined variables when I run a
2843 <p> A tip from Jose Fandos: put a comment on the following two lines
2844 in httpd.conf, like this:</p>
2846 <pre>
2847 # mod_gzip_item_include file \.php$
2849 </pre>
2851 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2852 PHP scripts. Of course you have to restart Apache.</p>
2857 I get the error "No input file specified" when trying to
2858 run phpMyAdmin.</a></h4>
2860 <p> This is a permission problem. Right-click on the phpmyadmin folder
2861 and choose properties. Under the tab Security, click on "Add"
2862 and select the user "IUSR_machine" from the list. Now set his
2863 permissions and it should work.</p>
2867 db_structure.php with plenty of tables).</a></h4>
2870 GZIP output buffering is enabled. If you turn off it (by
2872 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2873 PHP 5.0.0.</p>
2877 message 'Errorcode: 13'. What does this mean?</a></h4>
2879 <p> This can happen due to a MySQL bug when having database / table names with
2880 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2881 To fix this, turn off this directive, convert all database and table names
2882 to lower case and turn it on again. Alternatively, there's a bug-fix
2883 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2887 and the columns are duplicated.</a></h4>
2889 <p> It is possible to configure Apache in such a way that PHP has problems
2890 interpreting .php files.</p>
2892 <p> The problems occur when two different (and conflicting) set of directives
2893 are used:</p>
2895 <pre>
2896 SetOutputFilter PHP
2897 SetInputFilter PHP
2898 </pre>
2900 <p> and</p>
2902 <pre>AddType application/x-httpd-php .php</pre>
2904 <p> In the case we saw, one set of directives was in
2905 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2906 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2907 The recommended way is with <tt>AddType</tt>, so just comment out
2908 the first set of lines and restart Apache:</p>
2910 <pre>
2911 #SetOutputFilter PHP
2912 #SetInputFilter PHP
2913 </pre>
2918 <p> This problem is known to happen when the server is running Turck MMCache
2919 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2924 <p>Yes.</p>
2925 <p>
2926 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
2927 is still maintained.
2928 </p>
2931 <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>
2933 <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>
2936 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2937 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2938 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2939 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2940 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2941 enabled.) Click <tt>OK</tt>.</li>
2942 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2943 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2944 </ol>
2948 PHP 5.0.4 on 64-bit systems?</a></h4>
2950 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2951 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2957 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
2958 the order of the server paragraph in <tt>config.inc.php</tt>.
2959 Table and script parts are optional. If you want
2960 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2961 some configuration. Following lines apply only for <a
2963 that you have enabled some features within global configuration. You need
2964 <code>Options FollowSymLinks</code> and <code>AllowOverride
2965 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2966 you need mod_rewrite to be enabled. Then you just need to create following
2967 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2968 (don't forget to change directory name inside of it):</p>
2970 <pre>
2971 RewriteEngine On
2972 RewriteBase /path_to_phpMyAdmin
2973 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2974 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2975 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2976 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2977 </pre>
2980 <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>
2982 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2983 following rewrite rule:</p>
2985 <pre>
2986 RewriteEngine On
2987 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2988 </pre>
2992 </h4>
2993 <p>
2994 There can be many explanations to this and a look at your server's
2995 error log file might give a clue.
2996 </p>
3000 password encryption in cookie auth doesn't work.</a></h4>
3002 <p> If your cluster consist of different architectures, PHP code used for
3003 encryption/decryption won't work correct. This is caused by use of
3004 pack/unpack functions in code. Only solution is to use mcrypt extension
3005 which works fine in this case.</p>
3010 <p> Yes but the default configuration values of Suhosin are known to cause
3011 problems with some operations, for example editing a table with many
3012 columns and no primary key or with textual primary key.
3013 </p>
3014 <p>
3015 Suhosin configuration might lead to malfunction in some cases and it can
3016 not be fully avoided as phpMyAdmin is kind of application which needs to
3017 transfer big amounts of columns in single HTTP request, what is something
3018 what Suhosin tries to prevent. Generally all
3019 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3020 <code>suhosin.get.*</code> directives can have negative effect on
3021 phpMyAdmin usability. You can always find in your error logs which limit
3022 did cause dropping of variable, so you can diagnose the problem and adjust
3023 matching configuration variable.
3024 </p>
3025 <p>
3026 The default values for most Suhosin configuration options will work in most
3027 scenarios, however you might want to adjust at least following parameters:
3028 </p>
3030 <ul>
3031 <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>
3032 <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>
3033 <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>
3034 <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>
3035 <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>
3036 <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>
3037 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.get.max_value_length">suhosin.get.max_value_length</a> should be increased (eg. 1024)</li>
3038 <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>
3039 <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>
3040 </ul>
3042 <p>
3044 <tt>SuhosinDisableWarning</tt> directive</a>.
3045 </p>
3049 but then my connection is redirected back to http. What can cause this
3050 behavior?</a></h4>
3052 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3053 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>
3056 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3058 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3059 Example from the Apache 2.2 documentation:</p>
3060 <pre>
3061 ProxyPass /mirror/foo/ http://backend.example.com/
3062 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3063 ProxyPassReverseCookieDomain backend.example.com public.example.com
3064 ProxyPassReverseCookiePath / /mirror/foo/
3065 </pre>
3067 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3068 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3069 This is not specific to phpmyadmin, it's just the behavior of Apache.
3070 </p>
3072 <pre>
3073 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3074 ProxyPassReverse /mirror/foo/
3075 http://backend.example.com/%7Euser/phpmyadmin
3076 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3077 </pre>
3079 <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>
3080 for more details.</p>
3084 privileges, I get an error about an unknown column.</a></h4>
3086 <p> The MySQL server's privilege tables are not up to date, you need to run
3087 the <tt>mysql_upgrade</tt> command on the server.</p>
3094 headers already sent by ..." is displayed, what's the problem?</a></h4>
3096 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3097 (I.E. no blank lines, no spaces, no characters...) neither before the
3098 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3099 tag at the end. We also got a report from a user under IIS, that used
3100 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3101 contained an end-of-line character (hex 0A) at the end; removing this character
3102 cleared his errors.</p>
3107 <p> Either there is an error with your PHP setup or your username/password is
3108 wrong. Try to make a small script which uses mysql_connect and see if it
3109 works. If it doesn't, it may be you haven't even compiled MySQL support
3110 into PHP.</p>
3114 connect to local MySQL server through socket '/tmp/mysql.sock'
3115 (111) ..." is displayed. What can I do?</a></h4>
3117 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3119 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3120 In your <i>php.ini</i> you will find a line</p>
3122 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3124 <p> change it to</p>
3126 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3128 <p> Then restart apache and it will work.</p>
3130 <p> Here is a fix suggested by Brad Ummer:</p>
3132 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3133 To do this, telnet to your server and go to the MySQL bin directory. In
3134 this directory there should be a file named <i>mysqladmin</i>. Type
3135 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3136 info about your MySQL server, including the socket
3137 (<i>/tmp/mysql.sock</i>, for example).</li>
3138 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3139 phpMyAdmin, you need to complete the socket information in the
3140 <i>config.inc.php</i>.<br />
3141 For example:
3143 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3144 <br /><br />
3146 Please also make sure that the permissions of this file allow to be readable
3147 by your webserver (i.e. '0755').</li>
3148 </ul>
3150 <p> Have also a look at the
3152 corresponding section of the MySQL documentation</a>.</p>
3156 what can I do?</a></h4>
3159 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3160 sometime.<br />
3161 Also have a look at your PHP version number: if it contains "4.0b..."
3162 it means you're running a beta version of PHP. That's not a so good idea,
3163 please upgrade to a plain revision.</p>
3167 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3168 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3170 <p> Check the value you set for the
3172 directive in the phpMyAdmin configuration file.</p>
3176 password: YES)"-error when trying to access a MySQL-Server on a
3177 host which is port-forwarded for my localhost.</a></h4>
3179 <p> When you are using a port on your localhost, which you redirect via
3180 port-forwarding to another host, MySQL is not resolving the localhost
3181 as expected.<br />
3182 Erik Wasser explains: The solution is: if your host is "localhost"
3183 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3184 connection for speeding up things. And that doesn't work in this configuration
3185 with port forwarding.<br />
3191 <p> Themes are configured with
3195 <br />
3197 should not delete the directory "original" or its underlying
3198 structure, because this is the system theme used by phpMyAdmin.
3199 "original" contains all images and styles, for backwards
3200 compatibility and for all themes that would not include images or css-files.
3201 <br /><br />
3204 is enabled, you can select your favorite theme on the main page. Your
3205 selected theme will be stored in a cookie.<br /><br /></p>
3207 <p> To create a theme:</p>
3209 <ul><li>make a new subdirectory (for example "your_theme_name") under
3211 (by default <tt>themes</tt>)</li>
3212 <li>copy the files and directories from "original" to
3213 "your_theme_name"</li>
3214 <li>edit the css-files in "your_theme_name/css"</li>
3215 <li>put your new images in "your_theme_name/img"</li>
3216 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3217 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3218 contain your chosen theme name, that will be visible in user interface</li>
3219 <li>make a new screenshot of your theme and save it under
3220 "your_theme_name/screen.png"</li>
3221 </ul>
3223 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3224 theme verbose name, theme generation and theme version. These versions and
3225 generations are enumerated from 1 and do not have any direct dependence on
3226 phpMyAdmin version. Themes within same generation should be backwards
3227 compatible - theme with version 2 should work in phpMyAdmin requiring
3228 version 1. Themes with different generation are incompatible.</p>
3230 <p> If you do not want to use your own symbols and buttons, remove the
3231 directory "img" in "your_theme_name". phpMyAdmin will
3232 use the default icons and buttons (from the system-theme "original").
3233 </p>
3237 what can I do?</a></h4>
3239 <p> Here are a few points to check:</p>
3241 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3243 directive empty. See also
3245 </li>
3246 <li>Maybe you have a broken PHP installation or you need to upgrade
3247 your Zend Optimizer. See
3249 http://bugs.php.net/bug.php?id=31134</a>.
3250 </li>
3251 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3252 set to the default (200) or another low value, you could get this
3253 error if your table has a high number of columns. Adjust this setting
3254 accordingly. (Thanks to Klaus Dorninger for the hint).
3255 </li>
3256 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3257 of ";" will cause this error. Replace it with "&;".
3258 </li>
3260 you might want to increase
3262 </li>
3263 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3264 </li>
3265 </ul>
3270 <p> To be able to see a progress bar during your uploads, your server must
3273 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3274 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3281 who logged out can not log in again in with the same nick.</a></h4>
3283 <p> This is related to the authentication mechanism (protocol) used by
3284 phpMyAdmin. To bypass this problem: just close all the opened
3285 browser windows and then go back to phpMyAdmin. You should be able to
3286 log in again.</p>
3290 limit error or a time limit error.</a></h4>
3292 <p> Compressed dumps are built in memory and because of this are limited to
3293 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3294 using
3296 (enabled by default). Zip exports can not be handled this way, so if you need
3297 Zip files for larger dump, you have to use another way.</p>
3301 when I rename a table or a column.</a></h4>
3303 <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>
3307 bundled with the MySQL server distribution.</a></h4>
3309 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3311 <pre>
3312 -- MySQL dump 8.22
3313 --
3314 -- Host: localhost Database: database
3315 ---------------------------------------------------------
3316 -- Server version 3.23.54
3317 </pre>
3319 <p> The invalid part of the code is the horizontal line made of dashes that
3320 appears once in every dump created with mysqldump. If you want to run your
3321 dump you have to turn it into valid MySQL. This means, you have to add a
3322 whitespace after the first two dashes of the line or add a # before it:
3323 <br />
3324 <code>
3325 -- -------------------------------------------------------<br />
3326 </code>
3327 or<br />
3328 <code>
3329 #---------------------------------------------------------
3330 </code>
3331 </p>
3338 <p> Please note that you should not use the separating string multiple times
3339 without any characters between them, or at the beginning/end of your table
3340 name. If you have to, think about using another TableSeparator or disabling
3341 that feature</p>
3346 <p> In Relation view, being able to choose a table in another database,
3347 or having more than one index column in the foreign key.<br /><br/>
3348 In Query-by-example (Query), automatic generation of the query
3349 LEFT JOIN from the foreign table.<br /><br/>
3350 </p>
3354 I get series of errors like "Warning: unable to parse url". How
3355 can this be fixed?</a></h4>
3356 <p>
3357 Your table neither have a primary key nor an unique one, so we must use a
3358 long expression to identify this row. This causes problems to parse_url
3359 function. The workaround is to create a primary or unique key.
3360 <br />
3361 </p>
3365 a MIME-Transformation onto!</a></h4>
3367 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3368 nested forms can be put inside the table where phpMyAdmin displays the results.
3369 You can, however, use any form inside of a table if keep the parent
3370 form-container with the target to tbl_row_delete.php and just put your own
3371 input-elements inside. If you use a custom submit input field, the form will
3372 submit itself to the displaying page again, where you can validate the
3373 $HTTP_POST_VARS in a transformation.
3375 For a tutorial on how to effectively use transformations, see our
3377 on the official phpMyAdmin-homepage.</p>
3381 MySQL server</a></h4>
3383 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3386 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3387 the quote-character (") is interpreted as an identifier quote character and
3388 not as a string quote character, which makes many internal phpMyAdmin
3390 statements. There is no workaround to this behaviour. News to this item will
3391 be posted in Bug report
3392 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3393 </p>
3397 more that one column with the same value
3398 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3399 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3401 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3402 can use it for the Edit and Delete links.</p>
3407 <p> phpMyAdmin uses a quick method to get the row count, and this method
3408 only returns an approximate count in the case of InnoDB tables. See
3410 a way to modify those results, but
3411 this could have a serious impact on performance.</p>
3418 containing an hyphen.
3419 </a></h4>
3420 <p>
3421 The tests I have made with MySQL 5.1.49 shows that the
3422 API does not accept this syntax for the USE command.
3423 </p>
3426 <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>
3427 <p>
3428 This has been a known limitation of phpMyAdmin since the beginning and
3429 it's not likely to be solved in the future.
3430 </p>
3432 <!-- Begin: Excel import limitations -->
3443 <!-- End: Excel import limitations -->
3444 <!-- Begin: CSV import limitations -->
3447 <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>
3448 <p>
3449 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.
3450 </p>
3452 <!-- End: CSV import limitations -->
3453 <!-- Begin: Import type-detection limitations -->
3456 <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>
3457 <p>
3458 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
3459 you will have to edit the structure to your liking post-import.
3460 <br /><br />
3461 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
3462 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.
3463 </p>
3465 <!-- End: Import type-detection limitations -->
3467 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3470 <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
3471 need to install it for each customer.
3472 </a></h4>
3473 <p>
3474 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3475 your users. The development of this feature was kindly sponsored by
3476 NetCologne GmbH.
3477 This requires a properly setup MySQL user management and phpMyAdmin
3478 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3480 </p>
3484 access.
3485 </a></h4>
3486 <p>
3487 This depends on your system.<br />
3488 If you're running a server which cannot be accessed by other people, it's
3489 sufficient to use the directory protection bundled with your webserver
3491 If other people have telnet access to your server, you should use
3492 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3493 <br /><br />
3494 Suggestions:
3495 </p>
3496 <ul>
3497 <li>
3499 </li>
3500 <li>
3501 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3502 is a user whose password is only known to you, and apache is the
3503 group under which Apache runs.
3504 </li>
3505 <li>
3506 You should use PHP safe mode, to protect from other users that try
3508 </li>
3509 </ul>
3514 </a></h4>
3515 <p>
3520 </p>
3523 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3524 authentication.
3525 </a></h4>
3529 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3530 and/or
3532 are wrong.</li>
3534 <li>You have already setup a security mechanism for the
3535 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3536 phpMyAdmin's authentication, so remove it.</li>
3537 </ul>
3544 and put the privileges you want. For example,
3546 would let a user create/manage his/her database(s).</p>
3551 <p> If you have existing rules from an old .htaccess file, you can take them
3554 be a major benefit here if your installation is suited to using it. Then
3555 you can just add those updated lines into the
3559 <p> If you want a pre-made sample, you can try this fragment. It stops the
3560 'root' user from logging in from any networks other than the private
3563 <pre>
3564 //block root from logging in except from the private networks
3565 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3566 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3567 'deny root from all',
3568 'allow root from localhost',
3572 );
3573 </pre>
3578 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3579 different than the one set in your
3581 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3582 while a domain name is defined in the config file.</p>
3587 <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>
3593 when trying to create a table with more than 14 columns.
3594 </a></h4>
3595 <p>
3596 We could reproduce this problem only under Win98/98SE. Testing under
3597 WinNT4 or Win2K, we could easily create more than 60 columns.
3598 <br />
3599 A workaround is to create a smaller number of columns, then come back to
3600 your table properties and add the other columns.
3601 </p>
3605 <p>
3606 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3607 with each script/website that use forms.<br />
3608 Upgrade or downgrade your Xitami server.
3609 </p>
3612 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3613 <p>
3614 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3615 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3616 don't seem to work.<br />
3618 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3619 the user's temporary directory, so they must be moved before closing
3620 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3623 </p>
3627 Explorer never stores the cookies.
3628 </a></h4>
3629 <p>
3630 MS Internet Explorer seems to be really buggy about cookies, at least till
3631 version 6.
3632 </p>
3636 rows.
3637 </a></h4>
3638 <p>
3640 </p>
3643 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3644 when trying to modify a row in a table with many columns, or with a text
3645 column
3646 </a></h4>
3647 <p>
3648 Your table neither have a primary key nor an unique one, so we must use a
3649 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
3650 those browsers, and this not happen in Netscape, for example. The
3651 workaround is to create a primary or unique key, or use another browser.
3652 <br />
3653 </p>
3657 page.
3658 </a></h4>
3659 <p>
3660 Some browsers support right-clicking into the frame you want to refresh,
3661 just do this in the right frame.<br />
3662 </p>
3666 query box.
3667 </a></h4>
3668 <p>
3669 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3670 Mozilla versions.<br />
3671 </p>
3675 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3676 </a></h4>
3677 <p>
3678 This is a Mozilla bug (see bug #26882 at
3680 </p>
3685 </a></h4>
3686 <p>
3687 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3688 data in octet-stream mode. Since we can't detect the specific Netscape
3689 version, we cannot workaround this bug.
3690 </p>
3694 wrong.</a></h4>
3696 <p> Please ensure that you have set your browser's character set to the one of the
3697 language file you have selected on phpMyAdmin's start page.
3698 Alternatively, you can try the auto detection mode that is supported by the
3699 recent versions of the most browsers.</p>
3702 <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
3705 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3706 Netscape and Mozilla do not have this problem.</p>
3709 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3710 I cannot manage two servers: I log in to the first one, then the other one,
3711 but if I switch back to the first, I have to log in on each operation.</a></h4>
3717 but nothing happens after that, only a blank screen.</a></h4>
3728 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3733 address and you are starting
3735 containing a domain name, or the reverse situation.</li>
3736 <li>Security settings in IE and/or Microsoft Security Center are
3737 too high, thus blocking scripts execution.</li>
3738 <li>The Windows Firewall is blocking Apache and MySQL. You must
3742 </ul>
3745 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3746 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3747 installed in their Firefox is causing the problem.</p>
3751 clause is generated when I browse a table.</a></h4>
3752 <p> This happens only when both of these conditions are met: using the
3762 </a></h4>
3763 <p>
3764 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3765 specifying a wrong column-type.<br />
3766 Common errors include:
3767 </p>
3768 <ul>
3771 </ul>
3772 <p>
3773 Also, look at the syntax chapter in the MySQL manual to confirm that your
3774 syntax is correct.
3775 </p>
3779 columns and
3780 phpMyAdmin generates only one index with those two columns.
3781 </a></h4>
3782 <p>
3783 This is the way to create a multi-columns
3784 index. If you want two indexes, create the first one when creating the
3785 table, save, then display the table properties and click the Index link to
3786 create the other index.
3787 </p>
3791 <p>
3792 Since version 2.2.3, you have a checkbox for each column that can be null.
3794 column's value. Since version 2.5.5, you have to use the checkbox to get
3796 a literal NULL in the column, and not a NULL value (this works in PHP4).
3797 </p>
3802 <p> Click on a database or table name in the left frame, the properties will be
3804 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3805 statements that can be used to recreate your database/table.
3806 <br /><br />
3808 transmit the resulting dump to your station. Depending on your PHP
3809 configuration, you will see options to compress the dump. See also the
3811 configuration variable.<br /><br />
3814 this document.</p>
3819 </a></h4>
3821 <p> Click on a database name in the left frame, the properties will be
3823 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3825 the path to your dump filename, or use the Browse button. Then click Go.
3826 <br /><br />
3828 that you upgrade to take advantage of the new features.
3829 <br /><br />
3831 in this document.
3832 </p>
3837 <p> Here is an example with the tables persons, towns and countries, all
3839 table, create it as explained in the configuration section. Then create the
3840 example tables:</p>
3842 <pre>
3843 CREATE TABLE REL_countries (
3844 country_code char(1) NOT NULL default '',
3845 description varchar(10) NOT NULL default '',
3846 PRIMARY KEY (country_code)
3847 ) TYPE=MyISAM;
3849 INSERT INTO REL_countries VALUES ('C', 'Canada');
3851 CREATE TABLE REL_persons (
3852 id tinyint(4) NOT NULL auto_increment,
3853 person_name varchar(32) NOT NULL default '',
3855 country_code char(1) NOT NULL default '',
3856 PRIMARY KEY (id)
3857 ) TYPE=MyISAM;
3859 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3860 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3862 CREATE TABLE REL_towns (
3864 description varchar(30) NOT NULL default '',
3865 PRIMARY KEY (town_code)
3866 ) TYPE=MyISAM;
3868 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3869 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3870 </pre>
3876 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3880 </ul>
3888 <li>In the columns row, choose persons.person_name and click the
3890 <li>Do the same for towns.description and countries.descriptions in the
3893 the correct joins have been generated</li>
3895 </ul>
3899 <p>
3900 Starting from the previous example, create the pma_table_info as explained
3901 in the configuration section, then browse your persons table,
3902 and move the mouse over a town code or country code.
3903 <br /><br />
3904 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3905 enables: drop-down list of possible values.
3906 </p>
3909 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3910 <p>
3913 <br /><br />
3914 Then you need to think about your schema layout. Which tables will go on
3915 which pages?
3916 </p>
3917 <ul>
3923 page and click Go. If you like, you
3925 linked tables onto the new page.</li>
3926 <li>Select the name of the new page (making sure the Edit radio button
3927 is selected) and click Go.</li>
3929 Coordinates are relative; your diagram will
3930 be automatically scaled to fit the page. When initially placing tables
3931 on the page, just pick any coordinates -- say, 50x50. After clicking
3933 position the element correctly.</li>
3935 first be sure to click the Save
3936 button beneath the list of tables and coordinates, to save any changes
3937 you made there. Then scroll all the way down, select the
3939 you want, and click Go.</li>
3940 <li>Internet Explorer for Windows may suggest an incorrect filename when
3945 browsers on Windows, do not have this problem.</li>
3946 </ul>
3950 columns!</a></h4>
3952 <p> No, it's MySQL that is doing
3958 underscores in the database name?</a></h4>
3960 <p> If you do not put a backslash before the underscore, this is a wildcard
3963 john2db ...<br /><br />
3965 If you put a backslash before the underscore, it means that the database
3966 name will have a real underscore.</p>
3970 statistics pages?</a></h4>
3981 if it already exists during the import. It does NOT drop the table after
3982 your export, it only affects the import file.</li>
3984 Otherwise, you may get an error if the table name exists but has a
3985 different structure.</li>
3987 (if any) will be included in backup.</li>
3989 column and table names formed with special characters are protected.</li>
3991 types set in the pmadb in the dump as
3993 </li>
3994 </ul>
3999 command, for better documentation (but resulting file is bigger).</li>
4001 once the INSERT verb and the table name.</li>
4004 </li>
4006 more info is provided in the
4008 but basically with this selected, invalid values are adjusted and
4009 inserted rather than causing the entire statement to fail.</li>
4010 </ul>
4014 in its name.</a></h4>
4017 is the normal way to reference a database and table name. Worse, MySQL
4018 will usually let you create a database with a dot, but then you cannot
4019 work with it, nor delete it.</p>
4025 <p>
4026 To use SQL Validator, you need PHP with
4032 module.
4033 </p>
4035 <p>
4041 usage.
4042 </p>
4044 <p>
4045 If you use the Validator, you should be aware that any
4047 submit will be stored anonymously (database/table/column names,
4048 strings, numbers replaced with generic values). The Mimer
4051 We utilize it as free SOAP service.
4052 </p>
4056 it, but MySQL says "BLOB column '...' used in key specification without
4059 <p> The right way to do this, is to create the column without any indexes,
4061 dialog. On this page, you will be able to choose your BLOB column, and
4062 set a size to the index, which is the condition to create an index on
4063 a BLOB column.</p>
4067 editing fields?</a></h4>
4069 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4070 with many editing fields (table structure changes, row editing, etc.).
4071 You can also have a look at the directive
4073 ('vertical') and see if this eases up editing for you.</p>
4077 WTF is this feature then useful for?</a></h4>
4079 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4080 on them. Otherwise you could just put a comment on the column. Because entering
4081 your own mimetype will cause serious syntax checking issues and validation,
4082 this introduces a high-risk false-user-input situation. Instead you have to
4083 initialize mimetypes using functions or empty mimetype definitions.<br />
4084 Plus, you have a whole overview of available mimetypes. Who knows all those
4085 mimetypes by heart so he/she can enter it at will?</p>
4089 can't I see any bookmarks below the query box? What is this variable for?
4090 </a></h4>
4092 <p> Any query you have executed can be stored as a bookmark on the page where the
4093 results are displayed. You will find a button labeled 'Bookmark this query'
4094 just at the end of the page.<br />
4095 As soon as you have stored a bookmark, it is related to the database you run
4096 the query on. You can now access a bookmark dropdown on each page, the query
4097 box appears on for that database.<br /><br />
4099 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4103 aware of that you HAVE to create a valid query, otherwise your query won't be
4104 even able to be stored in the database.<br />
4106 for your query will remain the way it is, but will be stripped of the /**/
4107 chars. So you can use:<br /><br />
4111 which will be expanded to<br /><br />
4115 in your query, where VARIABLE is the string you entered in the input box. If
4116 an empty string is provided, no replacements are made.<br /><br />
4118 A more complex example. Say you have stored this query:<br /><br />
4120 <br /><br />
4123 the full query will be:<br /><br />
4126 <br /><br />
4128 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4130 spaces inserted there
4131 will be later also inserted as spaces in your query and may lead to unexpected
4132 results especially when
4134 Your initial query which is going to be stored as a bookmark has to yield at
4135 least one result row so
4136 you can store the bookmark. You may have that to work around using well
4140 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4141 include exported table?</a></h4>
4143 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4144 document should look like following one (assuming you have table
4147 <pre>
4148 \documentclass{article} % or any class you want
4149 \usepackage{longtable} % for displaying table
4150 \begin{document} % start of document
4151 \include{table} % including exported table
4152 \end{document} % end of document
4153 </pre>
4157 access them.
4158 </a></h4>
4160 <p> You have one of these global privileges: CREATE
4161 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4162 enable users to see all the database names.
4165 So if your users do not need those privileges, you can remove them and their
4166 databases list will shorten.</p>
4170 possible values for a column, based on some foreign table?</a></h4>
4172 <p> You have to setup appropriate links between the tables, and also
4176 foreign table, a drop-down list of values will be available.
4177 You will see two lists of values, the first list containing the key
4178 and the display column, the second list containing the display column
4179 and the key. The reason for this is to be able to type the first
4180 letter of either the key or the display column.<br /><br />
4182 For 100 values or more, a distinct window will appear, to browse foreign
4183 key values and choose one. To change the default limit of 100, see
4184 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4188 automatically when entering Browse mode for a table?</a></h4>
4190 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4191 </p>
4196 <p> You can use
4198 which works out of the box.<br />
4199 Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel
4200 version 97 and newer was dropped.
4201 </p>
4205 what happens to my column comments stored in pmadb?</a></h4>
4207 <p> Automatic migration of a table's pmadb-style column comments to the native
4208 ones is done whenever you enter Structure page for this table.</p>
4213 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4214 <ul>
4217 later)</li>
4220 </ul>
4224 <ol>
4225 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4226 <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>
4227 <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>
4228 <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>
4229 </ol>
4234 <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>
4240 <p>
4241 In all places where phpMyAdmin accepts format strings, you can use
4244 expanded variables depend on a context (for example, if you haven't chosen a
4245 table, you can not get the table name), but the following variables can be used:
4246 </p>
4247 <dl>
4253 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4264 </dl>
4269 <p>
4270 By clicking on the button 'toggle scratchboard' on the page
4271 where you edit x/y coordinates of those elements you can activate a
4272 scratchboard where all your elements are placed. By clicking on an
4273 element, you can move them around in the pre-defined area and the x/y
4274 coordinates will get updated dynamically. Likewise, when entering a
4275 new position directly into the input field, the new position in the
4276 scratchboard changes after your cursor leaves the input field.
4277 </p>
4278 <p>
4279 You have to click on the 'OK'-button below the tables to save the new
4280 positions. If you want to place a new element, first add it to the
4281 table of elements and then you can drag the new element around.
4282 </p>
4283 <p>
4284 By changing the paper size and the orientation you can change the size
4285 of the scratchboard as well. You can do so by just changing the
4286 dropdown field below, and the scratchboard will resize automatically,
4287 without interfering with the current placement of the elements.
4288 </p>
4289 <p>
4290 If ever an element gets out of range you can either enlarge the paper
4291 size or click on the 'reset' button to place all elements below each
4292 other.
4293 </p>
4298 <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>
4305 <p> Our Bug Tracker is located at
4307 under the Bugs section.<br /><br />
4309 But please first discuss your bug with other users:<br />
4311 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4312 </p>
4316 existing language, where do I start?</a></h4>
4318 <p> Always use latest Git version of the po file to translate. You can optionally
4320 server</a> where you can also get the latest po files and merge them
4321 with your translations. For creating a new translation simply use
4325 to do this) or ask on the mailing list to add the translation to the web
4326 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4327 </p>
4328 <p>
4329 Please note that we try not to use HTML entities like &eacute; in
4330 the translations, since we define the right character set in the file.
4331 With HTML entities, the text on JavaScript messages would not
4332 display correctly.
4333 However there are some entities that need to be there: quotes,
4334 non-breakable spaces, ampersands, less than, greater than.
4335 </p>
4336 <p>
4337 You can then put your translations, as a zip file to avoid losing special
4338 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4339 </p>
4340 <p>
4341 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4342 list, because this is where we ask for translations of new messages.
4343 </p>
4345 <p>
4346 Documentation is being translated using po4a and gettext (see
4348 for existing translations). To start, checkout
4349 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4350 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4351 and translate it online. If your language is missing, just contact
4353 you prefer to directly translate the po files, please put updated ones into our
4354 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4355 </p>
4359 phpMyAdmin. How should I proceed?</a></h4>
4364 <tt>git clone
4365 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4366 </li>
4368 <li>generate patch with your changes:
4370 </li>
4373 tracker of the phpMyAdmin project</a>.
4374 </li>
4375 </ol>
4377 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Git">our wiki</a>.</p>
4379 <p> Write access to the repository is granted only to experienced developers who
4380 have already contributed something useful to phpMyAdmin.<br />
4386 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4388 <p> Please refer to
4389 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4390 </p>
4395 <p> If you use Apache web server, phpMyAdmin exports information about
4396 authentication to the Apache environment and it can be used in Apache logs.
4397 Currently there are two variables available:
4398 </p>
4399 <dl>
4401 <dd>User name of currently active user (he does not have to be logged
4402 in).</dd>
4409 </dl>
4410 <p>
4412 </p>
4413 <pre>
4416 </pre>
4417 <p>
4418 You can then use any log analyzing tools to detect possible break-in
4419 attempts.
4420 </p>
4426 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4427 It allows you to connect to local as well as remote servers. This requires you to enter
4428 server host name, username, password, port and the name of the database. Therefore you can
4429 now synchronize your databases placed on the same server or some remote server.
4430 </p>
4432 <p>
4433 This feature is helpful for developers who need to replicate their
4434 database’s structure as well as data. Moreover, this feature not only
4435 helps replication but also facilitates the user to keep his/her database
4436 in sync with another database. Other than the full database, certain
4437 tables of the databases can also be synchronized.
4438 </p>
4440 <p>
4441 You need to fill in the host name of the server, the username and
4442 password of an user account already there in MySQL. Port is by default
4443 populated with 3306 (MySQL default port). Then the name of the database
4444 should be mentioned at the end. All the information other than the port
4445 needs to be filled explicitly for the source as well as target servers.
4446 </p>
4448 <p>
4449 After successfully passing through the authentication phase, the source and
4450 target database table names will be displayed. It will be a tabular
4451 representation.
4452 </p>
4454 <p>
4455 On the left, are listed the source database table names. Some of the
4457 are only present in source database and they need to be added to the
4458 target database in order to synchronize the target database. The tables
4460 target database.
4461 </p>
4463 <p>
4464 On the right, are listed the target database table names. There are few
4466 means that these tables are to be created in target database in order to
4467 synchronize target database with source database. Some table names
4469 only present in target database and they will remain unchanged in the
4470 target database. The column in the middle shows the difference between
4471 the source and target corresponding tables.
4472 </p>
4474 <p>
4476 letters, indicating that either Structure or Data are not up to date. By
4477 clicking on them, they will turn grey, what means that they will be synchronized.
4478 </p>
4480 <!-- DEVELOPERS -->
4483 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4484 great features have been written by other people and you too can help to
4485 make phpMyAdmin a useful tool.</p>
4487 <p> If you're planning to contribute source, please read the following
4488 information:</p>
4494 it free from other code.<br />
4495 Commonly used functions should be added to
4498 <li>Obviously, you're free to use whatever coding style you want. But
4499 please try to keep your code as simple as possible: beginners are
4500 using phpMyAdmin as an example application.<br />
4501 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4502 compliant on one hand, they fit the
4505 coding standards</a>
4506 on the other hand. Please pay attention to this.</li>
4507 <li>Please enable showing PHP errors and warnings by the
4509 configuration directive.</li>
4510 <li>Please try to keep up the file-naming conventions. Table-related stuff
4513 <li>Please use gettext wrappers around all messages
4516 script. To use translated messages, call
4518 Gettext.</li>
4522 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4523 better debug and profile their code.<br />
4524 Please see the
4526 options for more information.<br />
4527 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4528 lost during its re-entry into Earth's atmosphere and in memory of the
4529 brave men and women who gave their lives for the people of Earth.</li>
4530 </ul>
4534 <pre>
4545 </pre>
4547 <p>
4548 This program is free software; you can redistribute it and/or modify
4549 it under the terms of the GNU General Public License version 2,
4550 as published by the Free Software Foundation.
4551 </p>
4553 <p>
4554 This program is distributed in the hope that it will be useful,
4555 but WITHOUT ANY WARRANTY; without even the implied warranty of
4556 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4557 GNU General Public License for more details.
4558 </p>
4560 <p>
4561 You should have received a copy of the GNU General Public License
4562 along with this program; if not, write to the Free Software
4564 </p>
4566 <!-- CREDITS -->
4571 <ul>
4574 <ul>
4577 </ul></li>
4580 <ul>
4585 </ul></li>
4588 <ul>
4594 </ul></li>
4597 <ul>
4599 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4600 generate XHTML1.0 and CSS2 compliant codes</li>
4603 </ul></li>
4606 <ul>
4614 </ul></li>
4617 <ul>
4622 </ul></li>
4625 <ul>
4628 </ul></li>
4631 <ul>
4633 </ul></li>
4636 <ul>
4639 </ul></li>
4642 <ul>
4646 </ul></li>
4649 <ul>
4652 </ul></li>
4655 <ul>
4662 </ul></li>
4665 <ul>
4669 </ul></li>
4672 <ul>
4678 </ul></li>
4681 (http://sf.net/projects/phpmysqlformgen/)
4682 <ul>
4684 </ul></li>
4687 <ul>
4689 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4694 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4698 </ul></li>
4701 <ul>
4703 </ul></li>
4706 <ul>
4708 </ul></li>
4711 <ul>
4713 </ul></li>
4716 <ul>
4717 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4718 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4719 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4720 </ul></li>
4723 <ul>
4725 </ul></li>
4728 <ul>
4730 </ul></li>
4733 <ul>
4735 </ul></li>
4738 <ul>
4741 </ul></li>
4743 <li>Nicola Asuni (Tecnick.com)
4744 <ul>
4747 </ul></li>
4750 <ul>
4753 </ul></li>
4756 <ul>
4758 </ul></li>
4761 <ul>
4764 </ul></li>
4766 <li>Ivan A Kirillov
4767 <ul>
4769 </ul></li>
4772 <ul>
4774 </ul></li>
4777 <ul>
4780 </ul></li>
4783 <ul>
4785 </ul></li>
4788 <ul>
4790 </ul></li>
4793 <ul>
4795 </ul></li>
4798 <ul>
4800 </ul></li>
4803 <ul>
4805 </ul></li>
4808 <ul>
4812 </ul></li>
4815 <ul>
4817 </ul></li>
4820 <ul>
4822 </ul></li>
4824 <li>Barrie Leslie
4825 <ul>
4827 </ul></li>
4830 <ul>
4832 </ul></li>
4835 </ul>
4837 <p>
4838 And also to the following people who have contributed minor changes,
4839 enhancements, bugfixes or support for a new language since version 2.1.0:
4840 </p>
4842 <p>
4843 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4844 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4845 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4846 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4848 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4849 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4850 Luís V., Martijn W. van der Lee,
4851 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4853 </p>
4858 <p>
4859 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4860 to create a web-based interface to MySQL using PHP3. Although I have not
4861 used any of his source-code, there are some concepts I've borrowed from
4862 him. phpMyAdmin was created because Peter told me he wasn't going to
4863 further develop his (great) tool.
4864 </p>
4865 <p>
4866 Thanks go to
4867 </p>
4868 <ul>
4870 code for the check when dropping a table or database. He also suggested
4871 that you should be able to specify the primary key on tbl_create.php3. To
4872 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4873 well as a bug-report. Plus many smaller improvements.
4874 </li>
4876 were introduced in 1.3.0 (including quite significant ones like the
4877 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4878 bug-fixes and help.
4879 </li>
4881 language-independent by outsourcing the strings to a separate file. He
4882 also contributed the French translation.
4883 </li>
4885 tbl_select.php3, a feature to display only some columns from a table.
4886 </li>
4888 functions in tbl_change.php3. He also added the
4890 </li>
4892 servers and is a regular contributor for bug-fixes.
4893 </li>
4895 features for 2.0.6.
4896 </li>
4897 </ul>
4898 <p>
4899 The following people have contributed minor changes, enhancements, bugfixes
4900 or support for a new language:
4901 </p>
4902 <p>
4903 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4904 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4905 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4906 G. Wieggers.
4907 </p>
4908 <p>
4909 And thanks to everyone else who sent me email with suggestions, bug-reports
4910 and or just some feedback.
4911 </p>
4917 <ul>
4919 - the default name of Apache's directory-level configuration file.</li>
4923 - a software application that enables a user to display and interact with
4924 text, images, and other information typically located on a web page at a
4925 website on the World Wide Web.</li>
4927 - a free software/open source data compression algorithm and program
4928 developed by Julian Seward.</li>
4930 - an important World Wide Web technology that enables a client web browser
4931 to request data from a program executed on the Web server.</li>
4933 - a log or record of changes made to a project.</li>
4935 - a computer system that accesses a (remote) service on another computer
4936 by some kind of network.</li>
4938 - a set of data values of a particular simple type, one for each row of
4939 the table.</li>
4941 - a packet of information sent by a server to a World Wide Web browser
4942 and then sent back by the browser each time it accesses that server.</li>
4944 - Comma-separated values</li>
4947 - an organized collection of data.</li>
4950 - a PHP module that extends PHP with additional functionality.</li>
4952 - a list of commonly asked question and there answers.</li>
4954 - one part of divided data/columns.</li>
4956 - a field or group of fields in a database record that point to a key
4957 field or group of fields forming a key of another database record in some
4958 (usually different) table.</li>
4960 - the free PDF library</li>
4962 GD Graphics Library</a> - a library by Thomas Boutell and others for
4963 dynamically manipulating images.</li>
4966 - gzip is short for GNU zip, a GNU free software file compression
4967 program.</li>
4969 - any machine connected to a computer network, a node that has a hostname.</li>
4971 - the unique name by which a network attached device is known on a network.</li>
4973 (HyperText Transfer Protocol)</a>
4974 - the primary method used to transfer or convey information on the World
4975 Wide Web.</li>
4978 additional security measures.</li>
4979 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4980 - a set of Internet-based services for servers using Microsoft Windows.</li>
4982 - a feature that allows quick access to the rows in a table.</li>
4984 - a data-oriented protocol used by source and destination hosts for
4985 communicating data across a packet-switched internetwork.</li>
4987 - a unique number that devices use in order to identify and communicate
4988 with each other on a network utilizing the Internet Protocol standard.</li>
4990 (Internet Server Application Programming Interface)</a>
4991 - the API of Internet Information Services (IIS).</li>
4993 - a business or organization that offers users access to the Internet and related services.</li>
4995 - a most commonly used standard method of lossy compression for
4996 photographic images.</li>
5002 - line of personal computers is designed, developed, manufactured, and
5003 marketed by Apple Computer.</li>
5004 <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>
5005 - the operating system which is included with all currently shipping Apple
5006 Macintosh computers in the consumer and professional markets.</li>
5008 - a cryptographic library.</li>
5010 - the MCrypt PHP extension.</li>
5011 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5012 - an Internet Standard for the format of e-mail.</li>
5014 - some sort of extension for the Apache Webserver.</li>
5016 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5017 Management System (DBMS).</li>
5019 - the improved MySQL client PHP extension.</li>
5021 - the MySQL client PHP extension.</li>
5023 - open standard for office documents.</li>
5024 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5025 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5027 (Portable Document Format)</a>
5028 - a file format developed by Adobe Systems for representing two
5029 dimensional documents in a device independent and resolution independent
5030 format.</li>
5032 - the PHP Extension and Application Repository.</li>
5034 - the perl-compatible regular expression functions for PHP</li>
5036 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5037 programming language used mainly for developing server-side applications
5038 and dynamic web content, and more recently, a broader range of software
5039 applications.</li>
5041 - a connection through which data is sent and received.</li>
5043 - Request for Comments (RFC) documents are a series of memoranda
5044 encompassing new research, innovations, and methodologies applicable to
5045 Internet technologies.</li>
5049 - represents a single, implicitly structured data item in a table.</li>
5051 - a computer system that provides services to other computing
5052 systems over a network.</li>
5053 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5054 - handlers for different table types</li>
5056 - a form of inter-process communication.</li>
5058 Sockets Layer)</a>
5059 - a cryptographic protocol which provides secure communication on the Internet.</li>
5061 - Structured Query Language</li>
5063 - a set of data elements (cells) that is organized, defined and stored as
5064 horizontal rows and vertical columns where each item can be uniquely
5065 identified by a label or key or by it?s position in relation to other items.</li>
5068 - a type of archive file format: the Tape ARchive format.</li>
5070 - one of the core protocols of the Internet protocol suite.</li>
5074 - a sequence of characters, conforming to a standardized format, that is
5075 used for referring to resources, such as documents and images on the
5076 Internet, by their location.</li>
5078 - A computer (program) that is responsible for accepting HTTP requests
5079 from clients and serving them Web pages.</li>
5081 - a W3C-recommended general-purpose markup language for creating
5082 special-purpose markup languages, capable of describing many different
5083 kinds of data.</li>
5085 - a popular data compression and archival format.</li>
5087 - an open-source, cross-platform data compression library by Jean-loup
5088 Gailly and Mark Adler.</li>
5089 </ul>
5090 </div>
5093 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5096 <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>
5097 </ul>
5099 </body>
5100 </html>