| blob | 6933b03a43ec7f6f4be106a8578524bc5e7b562b |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.3.0-dev
22 Documentation
23 </h1>
24 </div>
26 <!-- TOP MENU -->
35 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
41 </ul>
46 phpMyAdmin homepage</a></li>
48 SourceForge phpMyAdmin project page</a></li>
50 Official phpMyAdmin wiki</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
58 </li>
59 </ul>
61 <!-- REQUIREMENTS -->
68 and the Standard PHP Library (SPL) extension.
69 </li>
72 currently default), you should install mbstring and ctype
73 extensions.
74 </li>
75 <li>You need GD2 support in PHP to display inline
77 original aspect ratio</li>
83 load pages significantly slower.
84 </li>
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, fields and
104 indexes</li>
105 <li>maintenance server, databases and tables, with proposals on server
106 configuration</li>
107 <li>execute, edit and bookmark any
109 batch-queries</li>
112 </li>
119 OpenDocument Text and Spreadsheet,
121 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
122 </li>
123 <li>import data and MySQL structures from <abbr title="Microsoft Excel 97-2003 and Excel 2007">Microsoft Excel</abbr> and OpenDocument spreadsheets, as well as <abbr title="Extensible Markup Language">XML</abbr>, <abbr title="Comma Separated Values">CSV</abbr>, and <abbr title="Server Query Language">SQL</abbr> files</li>
127 <li>using Query-by-example (QBE), create complex queries automatically
128 connecting required tables</li>
130 your Database layout</li>
132 <li>transform stored data into any format using a set of predefined
133 functions, like displaying BLOB-data as image or download-link
134 </li>
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>
343 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
344 that you may need special (administrator) privileges to create the database
345 and tables, and that the script may need some tuning, depending on the
346 database name.</p>
351 section</a>. You will also need to have a controluser with the proper rights
358 unpacked one. Configuration files from old versions may
359 require some tweaking as some options have been changed or removed; in
361 so you better remove it from your file and just use the default one.
363 statement that you might find near the end of your configuration file.</p>
367 is version-specific.</p>
370 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
371 you should run the SQL script found in
378 where you want to give users access to their own database and don't want
379 them to play around with others.<br />
380 Nevertheless be aware that MS Internet Explorer seems to be really buggy
382 in this area!<br />
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>
444 on a set of particular databases. Normally you shouldn't give global
445 privileges to an ordinary user, unless you understand the impact of those
446 privileges (for example, you are creating a superuser).<br />
450 <pre>
451 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
452 </pre>
454 What the user may now do is controlled entirely by the MySQL user
455 management system.<br />
457 authentication mode, you don't need to fill the user/password fields
459 array.</li>
460 </ul>
465 method and allows you to log in as any valid MySQL user.</li>
466 <li>Is supported with most PHP configurations. For
479 mode.</li>
480 </ul>
484 <ul><li>You can use this method as a replacement for the
486 (for example, if you're running
488 <li>Obviously, the user must enable cookies in the browser, but this is
489 now a requirement for all authentication modes.</li>
490 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
491 with the same username.</li>
492 <li>If you want to log in to arbitrary server see
497 not required.</li>
498 </ul>
502 <ul><li>This mode is a convenient way of using credentials from another
503 application to authenticate to phpMyAdmin.</li>
504 <li>The other application has to store login information into
505 session data.</li>
507 section.</li>
508 </ul>
511 <ul><li>This mode is the less secure one because it requires you to fill the
513 $cfg['Servers'][$i]['user']</a> and
515 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
516 can read your config.inc.php can discover your username and password).
517 <br />
524 is an entry explaining how to protect your configuration file.</li>
525 <li>For additional security in this mode, you may wish to consider the Host
526 authentication
528 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
530 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
531 directives.</li>
532 <li>Unlike cookie and http, does not require a user to log in when first
533 loading the phpMyAdmin site. This is by design but could allow any
534 user to access your installation. Use of some restriction method is
536 HTTP-AUTH directive or disallowing incoming HTTP requests at
537 one’s router or firewall will suffice (both of which
538 are beyond the scope of this manual but easily searchable with Google).</li>
539 </ul>
541 <p>
542 The Swekey is a low cost authentication USB key that can be used in
543 web applications.<br /><br />
544 When Swekey authentication is activated, phpMyAdmin requires the
545 users's Swekey to be plugged before entering the login page (currently
546 supported for cookie authentication mode only). Swekey Authentication is
547 disabled by default.<br /><br />
549 </p>
550 <pre>
551 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
552 </pre>
553 <p>
555 each user with their Swekey Id. It is important to place this file outside
556 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
558 users' information.<br /><br />
559 If you want to purchase a Swekey please visit
561 since this link provides funding for phpMyAdmin.
562 </p>
563 <!-- CONFIGURATION -->
567 users:</span> PHP does not seem to like
571 before saving a script you have modified.</p>
576 section to create one. This file only needs to contain the parameters you want to
577 change from their corresponding default value in
580 <p> The parameters which relate to design (like colors) are placed in
583 your site specific code to be included on start and end of each page.</p>
587 (with full path) to your phpMyAdmin installation's directory.
590 some web servers are case–sensitive.
593 Starting with version 2.3.0, it is advisable to try leaving this
594 blank. In most cases phpMyAdmin automatically detects the proper
595 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
596 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
597 A good test is to browse a table, edit a row and save it. There should
598 be an error message if phpMyAdmin is having trouble auto–detecting
599 the correct value. If you get an error that this must be set or if
600 the autodetect code fails to detect your path, please post a bug
601 report on our bug tracker so we can improve the code.</dd>
605 with master / foreign – tables (see
607 <br />
608 If you tried to set this up and it does not work for you, have a look on
610 use it. You will find a link that will analyze why those features have
611 been disabled.<br />
612 If you do not want to use those features set this variable to
616 <dd>A warning is displayed on the main page if Suhosin is detected.
618 from appearing.</dd>
621 <dd>Disable the default warning that is displayed if mcrypt is missing for
622 cookie authentication.
624 from appearing.</dd>
628 domain to call phpMyAdmin inside a frame, and is a potential security
629 hole allowing cross-frame scripting attacks.</dd>
633 algorithm to encrypt the password.<br />
635 passphrase of your choice. It will be used internally by the blowfish
636 algorithm: you won’t be prompted for this passphrase. The maximum
639 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
640 makes a bit weaker security as this generated secret is stored in
641 session and furthermore it makes impossible to recall user name from
642 cookie.</dd>
646 MySQL servers. Therefore, a
648 been added which contains the login information for the different servers.
649 The first
651 contains the hostname of the first server, the second
653 the hostname of the second server, etc. In
655 server definition, however you can put as many as you need in
657 have to define all settings, just those you need to change).</dd>
661 $i-th MySQL-server. E.g. localhost.</dd>
666 ignores this port number and connects with the socket, so if you want
667 to connect to a port different from the default port, use
670 </dd>
674 To determine the correct socket, check your MySQL configuration or, using the
676 Among the resulting information displayed will be the socket used.</dd>
679 <dd>Whether to enable SSL for connection to MySQL server.
680 </dd>
683 <dd>What type connection to use with the MySQL server. Your options are
685 is nearly guaranteed to be available on all MySQL servers, while
686 sockets are not supported on some platforms.<br /><br />
688 To use the socket mode, your MySQL server must be on the same machine
689 as the Web server.</dd>
692 <dd>What php MySQL extension to use for the connection. Valid options are:
693 <br /><br />
696 The classic MySQL extension. This is the recommended and default
697 method at this time.<br /><br />
700 The improved MySQL extension. This extension became available
701 with php 5.0.0 and is the recommended way to connect to a server
705 <dd>Whether to use a compressed protocol for the MySQL server connection
706 or not (experimental).<br />
712 </dt>
714 all relational features (see
716 and, for a MySQL server previous to 4.1.2 or running with
719 authentication mode).<br /><br />
722 cookie authentication modes (or 'config'
723 authentication mode since phpMyAdmin 2.2.1), you need to supply the
728 This account is used to check what databases the user will see at
729 login.<br />
733 In phpMyAdmin versions before 2.2.5, those were called
737 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
738 <dd>Whether config or cookie or
740 should be used for this server.
742 is the plain old way: username and password are stored in
744 <li>'cookie' authentication mode
746 2.2.3 allows you to log in as any valid MySQL user with the
747 help of cookies. Username and password are stored in
748 cookies during the session and password is deleted when it
749 ends. This can also allow you to log in in arbitrary server if
750 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
751 </li>
752 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
753 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
754 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
755 <li>'signon' authentication mode
757 as introduced in 2.10.0 allows you to log in from prepared PHP
758 session data. This is useful for implementing single signon
759 from another application. Sample way how to seed session is in
765 </ul>
768 for more information.
769 </dd>
771 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
772 </dt>
773 <dd>
775 names for hardware authentication. Leave empty to deactivate this feature.
776 </dd>
780 </dt>
781 <dd>
782 When using auth_type = 'config', this is the user/password-pair
783 which phpMyAdmin will use to connect to the
784 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
785 cookie authentication is used and should be empty.</dd>
787 <span
789 </dt>
790 <dd>
791 Allow attempt to log in without password when a login with password
792 fails. This can be used together with http authentication, when
793 authentication is done some other way and phpMyAdmin gets user name
794 from auth and uses empty password for connecting to MySQL. Password
795 login is still tried first, but as fallback, no password method is
796 tried.</dd>
799 </dt>
800 <dd>
801 If set to a (an array of) database name(s), only this (these) database(s)
802 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
803 database(s) name(s) may contain MySQL wildcards characters
807 This setting is an efficient way to lower the server load since the
808 latter does not need to send MySQL requests to build the available
810 privileges rules of the MySQL database server</span>. If set, it just
811 means only these databases will be displayed but
813 <br /><br />
815 An example of using more that one database:
817 <br /><br />
819 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
820 databases in the left frame, so that you can individually arrange your databases.<br />
821 If you want to have certain databases at the top, but don't care about the others, you do not
822 need to specify all other databases. Use:
824 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
825 order.</dd>
828 </dt>
829 <dd>Regular expression for hiding some databases. This only hides them
830 from listing, but a user is still able to access them (using, for example,
831 the SQL query area). To limit access, use the MySQL privilege system.
832 <br /><br />
837 More information on regular expressions can be found in the
839 PCRE pattern syntax</a> portion of the PHP reference manual.
840 </dd>
843 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
844 this string will be displayed instead of the hostname in the pull-down
845 menu on the main page. This can be useful if you want to show only
846 certain databases on your system, for example. For HTTP auth, all
847 non-US-ASCII characters will be stripped.</dd>
851 </dt>
852 <dd>The name of the database containing the linked-tables infrastructure.
853 <br /><br />
856 section in this document to see the benefits of this infrastructure,
857 and for a quick way of creating this database and the needed tables.
858 <br /><br />
860 If you are the only user of this phpMyAdmin installation, you can
861 use your current database to store those special tables; in this
862 case, just put your current database name in
864 set this parameter to the name of your central database containing
865 the linked-tables infrastructure.</dd>
869 </dt>
871 useful for queries you often run.<br /><br />
873 To allow the usage of this functionality:
875 <li>enter the table name in
877 </ul>
878 </dd>
882 </dt>
884 which field is a key in another table (a foreign key). phpMyAdmin
885 currently uses this to
886 <ul><li>make clickable, when you browse the master table, the data values
887 that point to the foreign table;</li>
889 when browsing the master table, if you move the mouse to a column
890 containing a foreign key (use also the 'table_info' table);<br />
893 <li>in edit/insert mode, display a drop-down list of possible foreign
897 <li>display links on the table properties page, to check referential
898 integrity (display missing foreign keys) for each described key;
899 </li>
903 schema of your database (also uses the table_coords table).</li>
904 </ul>
906 The keys can be numeric or character.<br /><br />
908 To allow the usage of this functionality:
911 infrastructure</li>
912 <li>put the relation table name in
914 <li>now as normal user open phpMyAdmin and for each one of your
915 tables where you want to use this feature, click
917 </li>
918 </ul>
922 future development of the cross-db relations.
923 </dd>
927 </dt>
928 <dd>
929 Since release 2.3.0 you can describe, in a special 'table_info'
930 table, which field is to be displayed as a tool-tip when moving the
931 cursor over the corresponding key.<br />
932 This configuration variable will hold the name of this special
933 table. To allow the usage of this functionality:
935 <li>put the table name in
937 <li>then for each table where you want to use this feature,
939 to choose the field.</li>
940 </ul>
942 </dd>
946 </dt>
949 the relations between your tables. To do this it needs two tables
954 schema output).<br /><br />
958 To allow the usage of this functionality:
961 infrastructure</li>
962 <li>put the correct table names in
965 </ul>
968 </dd>
972 </dt>
974 Since release 2.3.0 you can store comments to describe each column for
976 <br /><br />
978 Starting with release 2.5.0, comments are consequently used on the table
979 property pages and table browse view, showing up as tool-tips above the
980 column name (properties page) or embedded within the header of table in
981 browse view. They can also be shown in a table dump. Please see the
982 relevant configuration directives later on.<br /><br />
984 Also new in release 2.5.0 is a MIME-transformation system which is also
986 Transformations</a> for further information. To use the
987 MIME-transformation system, your column_info table has to have the three
988 new fields 'mimetype', 'transformation', 'transformation_options'.
989 <br /><br />
991 To allow the usage of this functionality:
993 infrastructure</li>
994 <li>put the table name in
998 <pre>
999 ALTER TABLE `pma_column_comments`
1000 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1001 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1002 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1003 </pre>
1006 renamed from<br />
1009 </ul>
1010 </dd>
1014 </dt>
1017 all queries you entered manually into the phpMyAdmin interface. If you
1018 don't want to use a table-based history, you can use the JavaScript-based
1019 history. Using that, all your history items are deleted when closing the
1020 window.<br /><br />
1022 Using
1024 you can specify an amount of history items you want to have on hold. On
1025 every login, this list gets cut to the maximum amount.<br /><br />
1027 The query history is only available if JavaScript is enabled in your
1028 browser.<br /><br />
1030 To allow the usage of this functionality:
1033 infrastructure</li>
1035 </li>
1036 </ul>
1037 </dd>
1041 </dt>
1042 <dd>
1043 Since release 3.3.x a tracking mechanism is available.
1045 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1046 and data definition statements. After enabling it you can create versions of tables.
1047 <br/><br/>
1048 The creation of a version has two effects:
1050 <ul>
1052 <li>phpMyAdmin loggs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1053 </ul>
1055 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1056 For the report you can use filters, for example you can get a list of statements within a date range.
1057 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1058 In addition you can export the (filtered) report to a file or to a temporary database.
1059 <br/><br/>
1061 To allow the usage of this functionality:
1063 <ul>
1066 </ul>
1067 </dd>
1070 <span id="cfg_Servers_tracking_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1071 </dt>
1072 <dd>
1073 Whether the tracking mechanism creates versions for tables and views automatically. Default value is true.
1074 <br/><br/>
1075 If this is set to true and you create a table or view with
1077 <ul>
1080 </ul>
1082 and no version exists for it, the mechanism will
1083 create a version for you automatically.
1084 </dd>
1087 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1088 </dt>
1089 <dd>
1090 Defines the list of statements the auto-creation uses for new versions. Default value is
1091 <br/>
1093 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1094 CREATE INDEX,DROP INDEX,
1095 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1096 CREATE VIEW,ALTER VIEW,DROP VIEW,
1097 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1098 </dd>
1101 <span id="cfg_Servers_tracking_drop_view">$cfg['Servers'][$i]['tracking_version_drop_view']</span> boolean
1102 </dt>
1103 <dd>
1104 Whether a DROP VIEW IF EXISTS statement will added as first line to the log when creating a view. Default value is true.
1105 <br/><br/>
1106 </dd>
1110 <span id="cfg_Servers_tracking_drop_table">$cfg['Servers'][$i]['tracking_version_drop_table']</span> boolean
1111 </dt>
1112 <dd>
1113 Whether a DROP TABLE IF EXISTS statement will added as first line to the log when creating a table. Default value is true.
1114 <br/><br/>
1115 </dd>
1118 <span id="cfg_Servers_tracking_drop_database">$cfg['Servers'][$i]['tracking_version_drop_database']</span> boolean
1119 </dt>
1120 <dd>
1121 Whether a DROP DATABASE IF EXISTS statement will added as first line to the log when creating a database. Default value is true.
1122 <br/><br/>
1123 </dd>
1128 </dt>
1130 to visually manage the relations.
1131 <br /><br />
1133 To allow the usage of this functionality:
1136 infrastructure</li>
1138 </li>
1139 </ul>
1140 </dd>
1143 </dt>
1145 column_info table got enhanced with three new fields. If the above variable
1147 latest table structure available. If not, it will emit a warning to the
1148 superuser.<br /><br />
1150 You can disable this checking behavior by setting the variable to false,
1151 which should offer a performance increase.<br /><br />
1153 Recommended to set to FALSE, when you are sure, your table structure is
1154 up to date.</dd>
1156 boolean</dt>
1157 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1158 </dd>
1160 boolean</dt>
1161 <dd>Whether to allow logins without a password. The default
1163 to a MySQL server with was left with an empty password for root or
1164 on which an anonymous (blank) user is defined.
1165 </dd>
1168 </dt>
1170 authentication is disabled.<br /><br />
1173 all deny rules followed by allow rules. Access is allowed by default. Any
1174 client which does not match a Deny command or does match an Allow command
1175 will be allowed access to the server. <br /><br />
1178 applies all allow rules followed by deny rules. Access is denied by
1179 default. Any client which does not match an Allow directive or does
1180 match a Deny directive will be denied access to the server.<br /><br />
1182 If your rule order is set to 'explicit', the authentication is
1183 performed in a similar fashion to rule order 'deny,allow', with the
1187 and was available in Apache by specifying allow and deny rules without
1188 setting any order.<br /><br />
1190 Please also see <a
1192 address behind proxies.
1193 </dd>
1195 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1196 </dt>
1197 <dd>The general format for the rules is as such:
1199 <pre>
1201 </pre>
1206 well (please note that those containing SERVER_ADDRESS might not be
1207 available on all webservers):
1208 <pre>
1214 </pre>
1216 Having an empty rule list is equivalent to either using
1222 following work:<br />
1224 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1225 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1226 But the following does not work:<br />
1229 Also IPv6 addresses are not supported.
1230 </dd>
1231 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1232 <dd>Name of session which will be used for signon authentication method.
1233 </dd>
1235 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1236 </dd>
1238 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1239 </dd>
1242 <dd>If you have more than one server configured, you can set
1244 that server when phpMyAdmin is started, or set it to 0 to be given a
1245 list of servers without logging in.<br />
1247 MUST be set to that server.</dd>
1250 <dd>The maximum number of database names to be displayed in the
1251 navigation frame and the database list.</dd>
1254 <dd>The maximum number of table names to be displayed in the
1255 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1256 when in Light mode.</dd>
1259 <dd>The maximum number of characters when a SQL query is displayed. The
1260 default limit of 1000 should be correct to avoid the display of tons
1261 of hexadecimal codes that represent BLOBs, but some users have real
1262 SQL queries that are longer than 1000 characters. Also, if a query's
1263 length exceeds this limit, this query is not saved in the history.</dd>
1266 <dd>Defines whether to use GZip output buffering for increased
1268 Set to true/false for enabling/disabling. When set to 'auto' (string),
1269 phpMyAdmin tries to enable output buffering and will automatically disable
1270 it if your browser has some problems with buffering. IE6 with a certain patch
1271 is known to cause data corruption when having enabled buffering.</dd>
1274 <dd>Whether persistent connections should be used or not (mysql_connect or
1275 mysql_pconnect).</dd>
1281 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1282 to zero, no time limit is imposed.<br />
1283 This setting is used while importing/exporting dump files but has no
1284 effect when PHP is running in safe mode.</dd>
1287 <dd>Set the number of bytes a script is allowed to allocate. If number set
1288 to zero, no limit is imposed.<br />
1289 This setting is used while importing/exporting dump files but has no
1290 effect when PHP is running in safe mode.<br />
1294 <dd>Mark used tables and make it possible to show databases with locked
1299 generated by phpMyAdmin should be displayed or not.</dd>
1302 <dd>Defines whether normal users (non-administrator) are allowed to
1303 delete their own database or not. If set as FALSE, the link "Drop
1305 mydatabase" will be rejected. Quite practical for
1307 customers.<br />
1308 Please note that this limitation of SQL queries is not as strict as
1309 when using MySQL privileges. This is due to nature of SQL queries
1310 which might be quite complicated. So this choice should be viewed as
1311 help to avoid accidental dropping rather than strict privilege
1312 limitation.</dd>
1316 displayed when you're about to lose data.</dd>
1319 <dd>Define whether the previous login should be recalled or not in cookie
1320 authentication mode.<br /><br />
1322 This is automatically disabled if you do not have configured
1324 </dd>
1327 <dd>Define how long is login cookie valid. Please note that php
1328 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1329 might limit session validity and if session is lost, login cookie is
1331 at least as high is $cfg['LoginCookieValidity'] is set.</dd>
1335 means that it will be kept for existing session. This is recommended
1336 for not trusted environments.</dd>
1339 <dd>If enabled (default), logout deletes cookies for all servers,
1340 otherwise only for current one. Setting this to false makes it easy to
1341 forget to log out from other server, when you are using more of
1342 them.</dd>
1348 <dd>Define whether phpMyAdmin will continue executing a multi-query
1349 statement if one of the queries fails. Default is to abort execution.</dd>
1352 <dd>Define whether phpMyAdmin will output the results of each query of a
1353 multi-query statement embedded into the
1358 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1359 <br /><br />
1362 MySQL servers behind the firewall where your
1364 </dd>
1367 <dd>Defines whether to use a select-based menu and display only the current
1368 tables in the left frame (smaller page). Only in Non-Lightmode you can
1369 use the feature to display nested folders using
1371 </dd>
1374 <dd>In light mode, defines whether to display the names of databases (in the
1375 selector) using a tree, see also
1377 </dd>
1380 string or array</dt>
1381 <dd>The string used to separate the parts of the database name when showing
1382 them in a tree. Alternatively you can specify more strings in an array
1383 and all of them will be used as a separator.</dd>
1386 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1387 This means if you have tables like 'first__second__third' this will be
1389 If set to FALSE or empty, the feature is disabled. NOTE: You should
1390 not use this separator at the beginning or end of a
1391 table name or multiple times after another without any other
1392 characters in between.</dd>
1395 <dd>Defines how many sublevels should be displayed when splitting
1396 up tables by the above separator.</dd>
1399 <dd>Defines whether to display table comment as tool-tip in left frame or
1400 not.</dd>
1403 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1404 comment and the real name. That means that if you have a table called
1405 'user0001' and add the comment 'MyName' on it, you will see the name
1406 'MyName' used consequently in the left frame and the tool-tip shows
1407 the real name of the DB.</dd>
1410 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1412 When setting this to 'nested', the Alias of the Tablename is only used
1413 to split/nest the tables according to the
1415 directive. So only the folder is called like the Alias, the tablename itself
1416 stays the real tablename.</dd>
1419 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1422 <dd>Enter URL where logo in the navigation frame will point to.
1423 For use especially with self made theme which changes this.
1432 <dd>Defines whether or not to display a server choice at the top of the left frame.
1433 Defaults to FALSE.</dd>
1435 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1436 Defaults to FALSE (drop-down).</dd>
1438 <dd>Defines whether to display database choice in light navigation frame as links
1439 instead of in a drop-down. Defaults to 'auto' - on main page list is
1440 shown, when database is selected, only drop down is displayed.</dd>
1443 <dd>Defines the tab displayed by default when clicking the small
1444 icon next to each table name in the navigation panel. Possible
1450 <dd>Defines whether or not to display space usage and statistics about databases
1451 and tables.<br />
1452 Note that statistics requires at least MySQL 3.23.3 and that, at this
1453 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1456 <dd>Defines whether to display detailed server information on main page.
1457 You can additionally hide more information by using
1459 </dd>
1464 </dt>
1467 not at the starting main (right) frame. This setting
1468 does not check MySQL commands entered directly.<br /><br />
1470 Please note that to block the usage of phpinfo() in scripts, you
1477 hard coded password value in the configuration file, end users can't
1478 be allowed to change their passwords.</dd>
1481 <dd>Defines whether to suggest a database name on the
1485 <dd>Defines whether navigation bar buttons and the right panel top menu
1486 contain text or symbols only. A value of TRUE displays icons, FALSE
1487 displays text and 'both' displays both icons and text.</dd>
1490 <dd>Defines whether a user should be displayed a
1494 <dd>Number of rows displayed when browsing a result set. If the result set
1501 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1505 from editing when browsing a table's content. Valid values are:
1510 </ul>
1511 </dd>
1514 <dd>Defines whether or not MySQL functions fields should be initially
1515 displayed in edit/insert mode. Since version 2.10, the user can
1516 toggle this setting from the interface.
1517 </dd>
1520 <dd>Defines which type of editing controls should be used for CHAR and
1521 VARCHAR fields. Possible values are:
1522 <ul><li>input - this allows to limit size of text to size of field in
1523 MySQL, but has problems with newlines in fields</li>
1524 <li>textarea - no problems with newlines in fields, but also no
1525 length limitations</li>
1526 </ul>
1527 Default is old behavior so input.</dd>
1533 <dd>If there are fewer items than this in the set of foreign keys, then a
1534 drop-down box of foreign keys is presented, in the style described by the
1536 setting.</dd>
1539 <dd>For the foreign key drop-down fields, there are several methods of
1540 display, offering both the key and value data. The contents of the
1541 array should be one or both of the following strings:
1547 </dt>
1548 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1549 creating a dump file</dd>
1552 </dt>
1553 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1554 compressed exports. This doesn't affect smaller dumps and allows users to
1555 create larger dumps that won't otherwise fit in memory due to php
1556 memory limit. Produced files contain more GZip/BZip2 headers, but all
1557 normal programs handle this correctly.</dd>
1561 mainframe.</dd>
1565 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1570 <dd>How many columns will be utilized to display the tables on the
1571 database property view? Default is 1 column. When setting this to a
1572 value larger than 1, the type of the database will be omitted for more
1573 display space.</dd>
1577 <dd>Defines the tab displayed by default on server view. Possible
1584 <dd>Defines the tab displayed by default on database view. Possible
1589 <dd>Defines the tab displayed by default on table view. Possible
1596 points to the MySQL documentation (type depends
1597 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1598 generated.<br />
1600 for more information about MySQL manuals and their types.</dd>
1603 <dd>Type of MySQL documentation:
1609 </ul>
1610 </dd>
1613 <dd>Defines the default language to use, if not browser-defined or
1614 user-defined.<br />
1616 this setting.</dd>
1619 <dd>Defines the default connection collation to use, if not
1620 user-defined.<br />
1625 <dd>Force: always use this language (must be defined in the
1629 <dd>Limit list of available languages to those matching the given regular
1630 expression. For example if you want only Czech and English, you should
1634 <dd>Default character set to use for recoding of MySQL queries. This must be
1635 enabled and it's described by
1637 option.<br />
1638 You can give here any character set which is in
1640 array and this is just default choice, user can select any of them.</dd>
1643 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1644 support (compiled in or module) in PHP to allow MySQL queries recoding
1645 and used language file must have it enabled (by default only these
1646 which are in Unicode, just to avoid losing some characters).<br /><br />
1649 in the Export and Import pages, to choose the character set when
1650 exporting a file. The default value in this menu comes from
1652 </dd>
1655 <dd>You can select here which functions will be used for character set
1656 conversion. Possible values are:
1657 <ul><li>auto - automatically use available one (first is tested
1658 iconv, then recode)</li>
1661 </ul>
1662 Default is auto.</dd>
1665 <dd>Specify some parameters for iconv used in charset conversion. See
1668 used, so that invalid characters will be transliterated.</dd>
1671 <dd>Available character sets for MySQL conversion. You can add your own (any of
1672 supported by recode/iconv) or remove these which you don't use.
1673 Character sets will be shown in same order as here listed, so if you
1674 frequently use some of these move them to the top.</dd>
1679 default empty, you need to fill in some trusted proxy servers if you
1680 want to use rules for IP addresses behind proxy.<br /><br />
1682 The following example specifies that phpMyAdmin should trust a
1684 <pre>
1685 $cfg['TrustedProxies'] =
1687 </pre>
1688 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1689 client's IP address as usual.
1690 </dd>
1694 MIME transformations.<br />
1695 Possible values are:
1696 <ul><li>auto - automatically detect, this is a bit expensive
1698 according to your server real possibilities</li>
1701 </ul>
1702 Default is auto.
1703 </dd>
1706 <dd>
1707 We normally check the permissions on the configuration file to ensure
1708 it's not world writable. However, phpMyAdmin could be installed on
1709 a NTFS filesystem mounted on a non-Windows server, in which case the
1710 permissions seems wrong but in fact cannot be detected. In this case
1712 </dd>
1715 <dd>
1716 Limit for length of URL in links. When length would be above this limit, it
1717 is replaced by form with button.
1718 This is required as some web servers (IIS) have problems with long URLs.
1720 </dd>
1724 </dd>
1726 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1727 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1728 </dt>
1729 <dd>The background styles used for both the frames.
1732 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1734 <dd>The style used for the pointer in the navi frame.
1738 </dt>
1739 <dd>The color used for the database name in the navi frame.
1748 </dd>
1752 <dd>The style used for table headers. See
1757 </dd>
1761 </dd>
1763 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1765 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1767 </dt>
1769 The former feature highlights the row over which your mouse is passing
1770 and the latter lets you visually mark/unmark rows by clicking on
1771 them.<br />
1776 <dd>You put here a valid CSS font family value, for example
1781 <dd>You put here a valid CSS font family value, for example
1795 </dt>
1797 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1799 The Char* values are used for CHAR and VARCHAR editing (if configured
1803 </dt>
1807 </dt>
1808 <dd>Defines if the whole textarea of the query box will be selected on
1809 click.</dd>
1812 </dt>
1813 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1814 editing.</dd>
1817 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1818 Can be turned off by a toggle button on the browse page.</dd>
1822 </dt>
1823 <dd>Defines the place where modify and delete links would be put when
1824 tables contents are displayed (you may have them displayed both at the
1825 left and at the right).
1831 </dt>
1833 Define which one is displayed by default. The first mode displays each
1834 row on a horizontal line, the second rotates the headers by 90
1835 degrees, so you can use descriptive headers even though fields only
1836 contain small values and still print them out. The vertical mode sorts
1837 each row on a vertical lineup.<br /><br />
1839 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1840 the rotation of the header for horizontalflipped is done via CSS. If
1841 set to 'fake' PHP does the transformation for you, but of course this
1842 does not look as good as CSS.</dd>
1846 string or integer</dt>
1847 <dd>When editing/creating new columns in a table all fields normally get
1848 lined up one field a line. (default: 'horizontal'). If you set this to
1849 'vertical' you can have each field lined up vertically beneath each
1850 other. You can save up a lot of place on the horizontal direction and
1851 no longer have to scroll. If you set this to integer, editing of fewer
1852 columns will appear in 'vertical' mode, while editing of more fields
1853 still in 'horizontal' mode. This way you can still effectively edit
1854 large number of fields, while having full view on few of them.</dd>
1858 </dt>
1860 display of column comments in Browse or Property display. In browse
1861 mode, the comments are shown inside the header. In property mode,
1862 comments are displayed using a CSS-formatted dashed-line below the
1863 name of the field. The comment is shown as a tool-tip for that field.
1864 </dd>
1876 <dd>Whether to display a link to validate a query in any SQL Query box.
1883 <dd>
1884 The name of the directory where
1886 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1887 are available under a drop-down box when you click the database or
1888 table name, then the Import tab.
1889 <br /><br />
1891 If you want different directory for each user, %u will be replaced
1892 with username.<br /><br />
1896 compressed formats is enabled).<br /><br />
1898 This feature is useful when your file is too big to be uploaded via
1900 uploads are disabled in PHP.<br /><br />
1902 Please note that if PHP is running in safe mode, this directory must
1903 be owned by the same user as the owner of the phpMyAdmin scripts.
1904 <br /><br />
1908 alternatives.
1909 </dd>
1912 <dd>
1913 The name of the directory where dumps can be saved.<br /><br />
1915 If you want different directory for each user, %u will be replaced
1916 with username.<br /><br />
1918 Please note that the directory must exist and has to be writable for
1919 the user running webserver.<br /><br />
1921 Please note that if PHP is running in safe mode, this directory must
1922 be owned by the same user as the owner of the phpMyAdmin scripts.
1923 </dd>
1926 <dd>
1927 The name of the directory where temporary files can be stored.
1928 <br /><br />
1930 This is needed for native MS Excel export, see
1936 <br /><br />
1938 If the directory where phpMyAdmin is installed is subject to an
1940 temporary directory in some directory accessible by the web
1941 server. However for security reasons, this directory should be outside
1942 the tree published by webserver. If you cannot avoid having this
1943 directory published by webserver, place at least an empty
1945 possible.
1946 <br /><br />
1948 This directory should have as strict permissions as possible as the only
1949 user required to access this directory is the one who runs the
1950 webserver. If you have root privileges, simply make this user owner of
1951 this directory and make it accessible only by it:
1952 <br /><br />
1954 <pre>
1955 chown www-data:www-data tmp
1956 chmod 700 tmp
1957 </pre>
1959 If you cannot change owner of the directory, you can achieve a similar
1962 <pre>
1963 chmod 700 tmp
1964 setfacl -m "g:www-data:rwx" tmp
1965 setfacl -d -m "g:www-data:rwx" tmp
1966 </pre>
1968 If neither of above works for you, you can still make the directory
1970 system reading and writing data in this directory.
1971 </dd>
1974 <dd>
1975 In this array are defined default parameters for export, names of
1976 items are similar to texts seen on export page, so you can easily
1977 identify what they mean.
1978 </dd>
1981 <dd>
1982 In this array are defined default parameters for import, names of
1983 items are similar to texts seen on import page, so you can easily
1984 identify what they mean.
1985 </dd>
1988 <dd>
1989 Repeat the headers every X cells, or 0 to deactivate.
1990 </dd>
1998 </dt>
1999 <dd>
2000 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2001 or icon is always displayed on the left panel. If JavaScript is enabled in
2002 your browser, a click on this opens a distinct query window, which is
2003 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2004 changes to display a query box.<br /><br />
2006 The size of this query window can be customized with
2008 - both integers for the size in pixels. Note that normally, those
2010 theme you are using.<br /><br />
2014 opens the query window and puts the current query
2015 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2016 query in the right panel's query box.
2017 <br /><br />
2018 The usage of the JavaScript query window is recommended if you have a
2019 JavaScript enabled browser. Basic functions are used to exchange quite
2020 a few variables, so most 4th generation browsers should be capable to
2021 use that feature. It currently is only tested with Internet Explorer 6
2022 and Mozilla 1.x.
2023 <br /><br />
2025 to a table, which has to be created by you (see <a
2027 all your queries will be appended to the form, but only as long as
2028 your window is opened they remain saved.
2029 <br /><br />
2030 When using the JavaScript based query window, it will always get
2031 updated when you click on a new table/db to browse and will focus if
2032 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2033 the query window by checking the box "Do not overwrite this query from
2034 outside the window" below the query textarea. Then you can browse
2035 tables/databases in the background without losing the contents of the
2036 textarea, so this is especially useful when composing a query with
2037 tables you first have to look in. The checkbox will get automatically
2038 checked whenever you change the contents of the textarea. Please
2039 uncheck the button whenever you definitely want the query window to
2040 get updated even though you have made alterations.
2041 <br /><br />
2044 <br /><br />
2045 The query window also has a custom tabbed look to group the features.
2047 default tab to be used when opening the query window. It can be set to
2048 either 'sql', 'files', 'history' or 'full'.</dd>
2054 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2056 If the approximate row count as returned by
2059 count will be used.
2060 </dd>
2062 <dd>For VIEWs, since obtaining the exact count could have an
2063 impact on performance, this value is the maximum to be displayed, using
2065 any row counting.
2066 </dd>
2070 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2072 page. By clicking on the button 'toggle scratchboard' on the page
2073 where you edit x/y coordinates of those elements you can activate a
2074 scratchboard where all your elements are placed. By clicking on an
2075 element, you can move them around in the pre-defined area and the x/y
2076 coordinates will get updated dynamically. Likewise, when entering a
2077 new position directly into the input field, the new position in the
2078 scratchboard changes after your cursor leaves the input field.<br />
2079 You have to click on the 'OK'-button below the tables to save the new
2080 positions. If you want to place a new element, first add it to the
2081 table of elements and then you can drag the new element around.<br />
2082 By changing the paper size and the orientation you can change the size
2083 of the scratchboard as well. You can do so by just changing the
2084 dropdown field below, and the scratchboard will resize automatically,
2085 without interfering with the current placement of the elements.<br />
2086 If ever an element gets out of range you can either enlarge the paper
2087 size or click on the 'reset' button to place all elements below each
2088 other.<br />
2090 get this control to work. The basic Drag&Drop script functionality
2091 was kindly borrowed from www.youngpup.net and is underlying so
2092 specific license.</dd>
2095 <dd>Sorts database and table names according to natural order (for example,
2096 t1, t2, t10). Currently implemented in the left panel (Light mode)
2097 and in Database view, for the table list.</dd>
2108 <dd>Allows you to specify window's title bar. Following magic string can
2109 be used to get special values:
2110 <dl>
2116 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2125 </dl>
2126 </dd>
2136 </dd>
2139 <dd>If theme manager is active, use this as the path of the subdirectory
2140 containing all the themes.</dd>
2154 </dt>
2155 <dd>Default queries that will be displayed in query boxes when user didn't
2156 specify any. Use %d for database name, %t for table name and %f for a
2157 comma separated list of field names. Note that %t and %f are only
2161 <dd>
2162 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
2163 default we use HTML to format the query, but you can disable this by
2165 </dd>
2168 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2169 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2170 query inside a bracket is indented. By changing
2173 specifies the units of the indent amount that you specified. This is
2174 used via stylesheets.</dd>
2177 <dd>This array is used to define the colours for each type of element of
2178 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2180 If you specify an empty string for the color of a class, it is ignored
2181 in creating the stylesheet.
2182 You should not alter the class names, only the colour strings.<br />
2203 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2207 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2208 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2209 </ul>
2210 </dd>
2214 <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,
2215 as originally published on
2217 <br />
2218 For help in setting up your system to use the service, see the
2220 </dd>
2224 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2225 and any password, so we use those by default. Instead, if
2226 you have an account with them, you can put your login details
2227 here, and it will be used in place of the anonymous login.</dd>
2228 </dl>
2229 </dd>
2232 <dd><b>DEVELOPERS ONLY!</b></dd>
2235 <dd><b>DEVELOPERS ONLY!</b><br />
2236 Enable logging queries and execution times to be displayed in the bottom
2237 of main page (right frame).</dd>
2240 <dd><b>DEVELOPERS ONLY!</b><br />
2241 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2242 the code.<br />
2243 For help in setting up your system to this, see the
2247 <dd><b>DEVELOPERS ONLY!</b><br />
2248 Enable profiling support for phpMyAdmin. This will append a chunk of data
2249 to the end of every page displayed in the main window with profiling
2250 statistics for that page.<br />
2251 You may need to increase the maximum execution time for this to
2252 complete successfully.<i>Profiling was removed from the code for
2253 version 2.9.0 due to licensing issues.</i></dd>
2255 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2256 <dd><b>DEVELOPERS ONLY!</b><br />
2257 When profiling data is displayed, this variable controls the threshold of
2258 display for any profiling data, based on the average time each time has
2259 taken. If it is over the threshold it is displayed, otherwise it is not
2260 displayed. This takes a value in milliseconds. In most cases you don't need
2261 to edit this.</dd>
2264 <dd>All possible types of a MySQL column. In most cases you don't need to
2265 edit this.</dd>
2268 <dd>Possible attributes for fields. In most cases you don't need to edit
2269 this.</dd>
2272 <dd>A list of functions MySQL supports. In most cases you don't need to
2273 edit this.</dd>
2276 <dd>Mapping of column types to meta types used for preferring displayed
2277 functions. In most cases you don't need to edit this.</dd>
2280 <dd>Functions preferred for column meta types as defined in
2281 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2282 to edit this.</dd>
2285 <dd>Functions selected by default when inserting/changing row, Functions
2286 are defined for meta types from
2288 <code>first_timestamp</code>, which is used for first timestamp column
2289 in table.</dd>
2292 <dd>Operators available for search operations on numeric and date fields.
2293 </dd>
2296 <dd>Operators available for search operations on character fields.
2297 Note that we put <code>LIKE</code> by default instead of
2298 <code>LIKE %...%</code>, to avoid unintended performance problems
2299 in case of huge tables.</dd>
2302 <dd>Operators available for search operations on enum fields.</dd>
2305 <dd>Additional operators available for search operations when the
2306 field can be null.</dd>
2308 </dl>
2310 <!-- TRANSFORMATIONS -->
2316 </ol>
2320 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2322 section</a> on how to do so.</p>
2324 <p> You can apply different transformations to the contents of each field. The
2325 transformation will take the content of each field and transform it with
2326 certain rules defined in the selected transformation.</p>
2328 <p> Say you have a field 'filename' which contains a filename. Normally you would
2329 see in phpMyAdmin only this filename. Using transformations you can transform
2330 that filename into a HTML link, so you can click inside of the phpMyAdmin
2331 structure on the field's link and will see the file displayed in a new browser
2332 window. Using transformation options you can also specify strings to
2333 append/prepend to a string or the format you want the output stored in.</p>
2335 <p> For a general overview of all available transformations and their options,
2336 you can consult your
2337 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2338 installation.</p>
2340 <p> For a tutorial on how to effectively use transformations, see our
2342 the official phpMyAdmin homepage.</p>
2346 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2347 clicking on the 'Structure' link for a table). There click on
2348 "Change" (or change icon) and there you will see three new fields at
2349 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2350 'Transformation options'.</p>
2352 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2353 that corresponds to the column's contents. Please note that
2354 transformations are inactive as long as no MIME-type is selected.</li>
2356 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2357 hopefully growing amount of pre-defined transformations. See below for information on
2358 how to build your own transformation.<br />
2360 There are global transformations and mimetype-bound transformations. Global transformations
2361 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2362 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2363 transformations which operate on the main mimetype (like 'image'), which will most likely
2364 take the subtype into regard, and those who only operate on a
2365 specific subtype (like 'image/jpeg').<br />
2367 You can use transformations on mimetypes for which the function was not defined for. There
2368 is no security check for you selected the right transformation, so take care of what the
2369 output will be like.</li>
2371 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2372 transform-function specific options here. Usually the transforms can operate with default
2373 options, but it is generally a good idea to look up the overview to see which options are
2374 necessary.<br />
2376 Much like the ENUM/SET-Fields, you have to split up several options using the format
2377 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2378 parsed as an array, leaving the first value the first element in the array, and so
2379 forth.<br />
2381 If you want to specify a MIME character set you can define it in the transformation_options.
2382 You have to put that outside of the pre-defined options of the specific mime-transform,
2384 for which you can specify 2 options and you want to append a character set, enter "'first
2385 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2387 </ul>
2391 <p> All mimetypes and their transformations are defined through single files in
2392 the directory 'libraries/transformations/'.</p>
2394 <p> They are stored in files to ease up customization and easy adding of new
2395 transformations.</p>
2397 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2398 always work. It makes no sense to apply a transformation to a mimetype, the
2399 transform-function doesn't know to handle.</p>
2401 <p> One can, however, use empty mime-types and global transformations which should work
2402 for many mimetypes. You can also use transforms on a different mimetype they where built
2403 for, but pay attention to option usage as well as what the transformation does to your
2404 field.</p>
2406 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2407 any other transform function and provides some basic functions.</p>
2409 <p> There are 5 possible file names:</p>
2411 <ol><li>A mimetype+subtype transform:<br /><br />
2413 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2415 Please not that mimetype and subtype are separated via '_', which shall
2416 not be contained in their names. The transform function/filename may
2417 contain only characters which cause no problems in the file system as
2418 well as the PHP function naming convention.<br /><br />
2420 The transform function will the be called
2421 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2423 <b>Example:</b><br /><br />
2425 <tt>text_html__formatted.inc.php</tt><br />
2426 <tt>PMA_transform_text_html__formatted()</tt></li>
2428 <li>A mimetype (w/o subtype) transform:<br /><br />
2430 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2432 Please note that there are no single '_' characters.
2433 The transform function/filename may contain only characters which cause
2434 no problems in the file system as well as the PHP function naming
2435 convention.<br /><br />
2437 The transform function will the be called
2438 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2440 <b>Example:</b><br /><br />
2442 <tt>text__formatted.inc.php</tt><br />
2443 <tt>PMA_transform_text__formatted()</tt></li>
2445 <li>A mimetype+subtype without specific transform function<br /><br />
2447 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2449 Please note that there are no '__' characters in the filename. Do not
2450 use special characters in the filename causing problems with the file
2451 system.<br /><br />
2453 No transformation function is defined in the file itself.<br /><br />
2455 <b>Example:</b><br /><br />
2457 <tt>text_plain.inc.php</tt><br />
2458 (No function)</li>
2460 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2462 <tt>[mimetype].inc.php</tt><br /><br />
2464 Please note that there are no '_' characters in the filename. Do not use
2465 special characters in the filename causing problems with the file system.
2466 <br /><br />
2468 No transformation function is defined in the file itself.<br /><br />
2470 <b>Example:</b><br /><br />
2472 <tt>text.inc.php</tt><br />
2473 (No function)</li>
2475 <li>A global transform function with no specific mimetype<br /><br />
2477 <tt>global__[transform].inc.php</tt><br /><br />
2479 The transform function will the be called
2480 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2482 <b>Example:</b><br /><br />
2484 <tt>global__formatted</tt><br />
2485 <tt>PMA_transform_global__formatted()</tt></li>
2486 </ol>
2488 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2489 transform function.</p>
2491 <p> All filenames containing no '__' in themselves are not shown as valid transform
2492 functions in the dropdown.</p>
2494 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2495 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2496 without a transform function. Also note the introduction of a function description in
2497 the language files. For each function a $strTransformation_[filename without .inc.php]
2498 has to exist.</p>
2500 <p> You can use the template generator to generate new functions and entries in the
2501 language file.</p>
2503 <p> To create a new transform function please see
2504 <tt>libraries/transformations/template_generator.sh</tt>.
2505 To create a new, empty mimetype please see
2506 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2508 <p> A transform function always gets passed three variables:</p>
2510 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2511 you want to transform.</li>
2512 <li><b>$options</b> - Contains any user-passed options to a transform function
2513 as an array.</li>
2514 <li><b>$meta</b> - Contains an object with field information to your column.
2515 The data is drawn from the output of the
2517 function. This means, all object properties described on the
2519 available in this variable and can be used to transform a field accordingly
2520 to unsigned/zerofill/not_null/... properties.<br />
2521 The $meta->mimetype variable contains the original MIME-type of the
2522 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2523 </ol>
2525 <!-- FAQ -->
2532 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2537 </ol>
2539 <p> Please have a look at our
2541 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2542 features and or interface.</p>
2548 action is required or phpMyAdmin sends a blank page or a page full of
2549 cryptic characters to my browser, what can I do?</a></h4>
2551 <p> There are some known PHP bugs with output buffering and compression.<br />
2553 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2554 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2555 configuration file.<br />
2556 Furthermore, we know about such problems connected to the release
2557 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2558 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2563 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2564 See also the
2566 entry about PHP bugs with output buffering.<br />
2567 If your server keeps crashing, please ask for help in the various Apache
2568 support groups.</p>
2572 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2573 script: I'm always displayed the login screen.</a></h4>
2575 <p> This is a known PHP bug (see this
2577 official PHP bug database. It means there is and won't be any phpMyAdmin
2578 fix against it because there is no way to code a fix.</p>
2584 application misbehaved by not returning a complete set of
2586 </h4>
2588 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2589 Have a look at the last message in this
2591 official PHP bug database.</p>
2596 and/or many error messages with the
2598 mode.</a></h4>
2600 <p> This is a known problem with the PHP
2602 filter: it's not so stable. Please use instead the cookie authentication mode.
2603 </p>
2608 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2609 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2610 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2611 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2612 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2617 work.</a></h4>
2619 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2620 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2621 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2622 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2623 We faced PHP crashes when trying to download a dump with MS Internet
2624 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2625 this case you should switch to the release version of PHP 4.2.0.</p>
2629 an error about safe mode being in effect.</a></h4>
2631 <p> Your uploaded file is saved by PHP in the "upload dir", as
2632 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2633 the system default is <i>/tmp</i>).<br />
2634 We recommend the following setup for Apache servers running in safe mode,
2635 to enable uploads of files while being reasonably secure:</p>
2637 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2638 <li>give ownership to the Apache server's user.group:
2639 <tt>chown apache.apache /tmp/php</tt></li>
2640 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2641 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2642 <li>restart Apache</li>
2643 </ul>
2647 general file uploads don't work on my system and uploaded files have a
2648 <tt>Content-Type:</tt> header in the first line.</a></h4>
2650 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2651 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2652 So the problem is that this package has a serious bug that was corrected
2653 ages ago in PHP (2001-01-28: see
2655 for more details). The problem is that the bugged package is still
2656 available though it was corrected (see
2658 for more details).<br />
2659 So please download
2660 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2661 and the problem should go away.<br />
2662 And that fixes the \r\n problem with file uploads!</p>
2666 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2667 I'm using the Apache server.</a></h4>
2669 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2670 your <i>httpd.conf</i>:</p>
2674 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2678 uploading a file from the query box.</a></h4>
2680 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2681 restrictions. However you need to create temporary directory and
2683 The uploaded files will be moved there, and after execution of your
2689 <p> The MySQL manual explains how to
2691 reset the permissions</a>.</p>
2696 execute a bookmark.</a></h4>
2698 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2699 cannot access the uploaded query.</p>
2704 submit a query from the convenient text area.</a></h4>
2706 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2707 and try to increase it.</p>
2711 </h4>
2713 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2714 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2715 names to align with current standards.</p>
2720 </h4>
2722 <p> Starting with version 2.7.0, the import engine has been re–written and these
2723 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2724 to take advantage of the new import features.</p>
2726 <p> The first things to check (or ask your host provider to check) are the
2727 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2728 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2729 All of these three settings limit the maximum size of data that can be
2730 submitted and handled by PHP. One user also said that post_max_size
2731 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2733 There exist several workarounds if your upload is too big or your
2734 hosting provider is unwilling to change the settings:</p>
2737 feature. This allows one to
2738 upload a file to the server via scp, ftp, or your favorite file transfer
2739 method. PhpMyAdmin is then able to import the files from the temporary
2741 section</a> of this document.</li>
2743 BigDump</a>) to split the files before uploading. We cannot support this
2744 or any third party applications, but are aware of users having success
2745 with it.</li>
2746 <li>If you have shell (command line) access, use MySQL to import the files
2747 directly. You can do this by issuing the "source" command from
2748 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2749 </ul>
2753 support?</a></h4>
2755 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2756 fully supported. phpMyAdmin may connect to your MySQL server
2757 using PHP's classic
2760 is available in php 5.0.<br />
2761 Either way, the developers of both extensions recommend to use the classic
2762 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2763 When compiling php, we strongly recommend that you manually link the MySQL
2764 extension of your choice to a MySQL client library of at least the same
2765 minor version since the one that is bundled with some PHP distributions is
2768 If your webserver is running on a windows system, you might want to try
2769 MySQL's
2771 instead of the MySQL / MySQLi extensions that are bundled with the official
2772 php Win32 builds.</p>
2776 message, "Client does not support authentication protocol requested
2777 by server; consider upgrading MySQL client"</a></h5>
2779 <p> You tried to access MySQL with an old MySQL client library. The version of
2780 your MySQL client library can be checked in your phpinfo() output.
2781 In general, it should have at least the same minor version as your server
2785 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2786 changed the authentication hash and your PHP is trying to use the old method.
2788 with the proper client library to match your MySQL installation. Your
2789 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2790 More information (and several workarounds) are located in the
2792 </p>
2796 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2797 capital letter in its name it is changed to lowercase as it should. But
2798 if I try to DROP this table MySQL is unable to find the corresponding
2799 file.</a></h4>
2801 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2802 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2803 directive.</p>
2807 script seems not to know the font face I'm using!</a></h4>
2809 <p> The "FPDF" library we're using for this feature requires some
2810 special files to use font faces.<br />
2812 these files.</p>
2816 check PHP Configuration".</a></h4>
2818 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2819 "MySQL extension". This extension may be part of the PHP
2820 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2821 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2822 to load the extension but failed.<br /><br />
2824 Usually, the problem is solved by installing a software package called
2825 "PHP-MySQL" or something similar.</p>
2830 and I cannot log in using cookie auth.</a></h4>
2832 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2836 so I cannot upload.</a></h4>
2838 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2839 parameter is not set to "on".</p>
2843 a new table the table and field names are changed to lowercase!</a></h4>
2845 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2846 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2847 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2848 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2849 directory and add the following line to the group [mysqld]:</p>
2851 <pre>set-variable = lower_case_table_names=0</pre>
2853 <p> Next, save the file and restart the MySQL service. You can always check the
2854 value of this directive using the query</p>
2856 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2860 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2863 </p>
2867 and I get problems, such as undefined variables when I run a
2870 <p> A tip from Jose Fandos: put a comment on the following two lines
2871 in httpd.conf, like this:</p>
2873 <pre>
2874 # mod_gzip_item_include file \.php$
2876 </pre>
2878 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2879 PHP scripts. Of course you have to restart Apache.</p>
2884 I get the error "No input file specified" when trying to
2885 run phpMyAdmin.</a></h4>
2887 <p> This is a permission problem. Right-click on the phpmyadmin folder
2888 and choose properties. Under the tab Security, click on "Add"
2889 and select the user "IUSR_machine" from the list. Now set his
2890 permissions and it should work.</p>
2894 db_structure.php with plenty of tables).</a></h4>
2897 GZIP output buffering is enabled. If you turn off it (by
2899 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2900 PHP 5.0.0.</p>
2904 message 'Errorcode: 13'. What does this mean?</a></h4>
2906 <p> This can happen due to a MySQL bug when having database / table names with
2907 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2908 To fix this, turn off this directive, convert all database and table names
2909 to lower case and turn it on again. Alternatively, there's a bug-fix
2910 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2914 and the fields are duplicated.</a></h4>
2916 <p> It is possible to configure Apache in such a way that PHP has problems
2917 interpreting .php files.</p>
2919 <p> The problems occur when two different (and conflicting) set of directives
2920 are used:</p>
2922 <pre>
2923 SetOutputFilter PHP
2924 SetInputFilter PHP
2925 </pre>
2927 <p> and</p>
2929 <pre>AddType application/x-httpd-php .php</pre>
2931 <p> In the case we saw, one set of directives was in
2932 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2933 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2934 The recommended way is with <tt>AddType</tt>, so just comment out
2935 the first set of lines and restart Apache:</p>
2937 <pre>
2938 #SetOutputFilter PHP
2939 #SetInputFilter PHP
2940 </pre>
2945 <p> This problem is known to happen when the server is running Turck MMCache
2946 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2951 <p> Yes.<br />
2952 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2953 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2954 <tt>error_reporting</tt> settings.
2955 </p>
2958 <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>
2960 <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>
2963 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2964 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2965 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2966 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2967 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2968 enabled.) Click <tt>OK</tt>.</li>
2969 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2970 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2971 </ol>
2975 PHP 5.0.4 on 64-bit systems?</a></h4>
2977 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2978 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2984 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
2985 the order of the server paragraph in <tt>config.inc.php</tt>.
2986 Table and script parts are optional. If you want
2987 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2988 some configuration. Following lines apply only for <a
2990 that you have enabled some features within global configuration. You need
2991 <code>Options FollowSymLinks</code> and <code>AllowOverride
2992 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2993 you need mod_rewrite to be enabled. Then you just need to create following
2994 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2995 (don't forget to change directory name inside of it):</p>
2997 <pre>
2998 RewriteEngine On
2999 RewriteBase /path_to_phpMyAdmin
3000 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3001 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3002 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3003 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3004 </pre>
3007 <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>
3009 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3010 following rewrite rule:</p>
3012 <pre>
3013 RewriteEngine On
3014 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3015 </pre>
3019 </h4>
3020 <p>
3021 There can be many explanations to this and a look at your server's
3022 error log file might give a clue.
3023 </p>
3027 password encryption in cookie auth doesn't work.</a></h4>
3029 <p> If your cluster consist of different architectures, PHP code used for
3030 encryption/decryption won't work correct. This is caused by use of
3031 pack/unpack functions in code. Only solution is to use mcrypt extension
3032 which works fine in this case.</p>
3037 <p> Yes but the default configuration values of Suhosin are known to cause
3038 problems with some operations, for example editing a table with many
3039 columns and no primary key. Tuning information is available at
3041 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
3042 although the parameter names have changed (<tt>suhosin</tt> instead
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 commandline tool 'mysql' 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>
3272 who logged out can not log in again in with the same nick.</a></h4>
3274 <p> This is related to the authentication mechanism (protocol) used by
3275 phpMyAdmin. To bypass this problem: just close all the opened
3276 browser windows and then go back to phpMyAdmin. You should be able to
3277 log in again.</p>
3281 limit error or a time limit error.</a></h4>
3283 <p> Compressed dumps are built in memory and because of this are limited to
3284 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3285 using
3287 (enabled by default). Zip exports can not be handled this way, so if you need
3288 Zip files for larger dump, you have to use another way.</p>
3292 when I rename a table or a column.</a></h4>
3294 <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>
3298 bundled with the MySQL server distribution.</a></h4>
3300 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3302 <pre>
3303 -- MySQL dump 8.22
3304 --
3305 -- Host: localhost Database: database
3306 ---------------------------------------------------------
3307 -- Server version 3.23.54
3308 </pre>
3310 <p> The invalid part of the code is the horizontal line made of dashes that
3311 appears once in every dump created with mysqldump. If you want to run your
3312 dump you have to turn it into valid MySQL. This means, you have to add a
3313 whitespace after the first two dashes of the line or add a # before it:
3314 <br />
3315 <code>
3316 -- -------------------------------------------------------<br />
3317 </code>
3318 or<br />
3319 <code>
3320 #---------------------------------------------------------
3321 </code>
3322 </p>
3329 <p> Please note that you should not use the separating string multiple times
3330 without any characters between them, or at the beginning/end of your table
3331 name. If you have to, think about using another TableSeparator or disabling
3332 that feature</p>
3337 <p> In Relation view, being able to choose a table in another database,
3338 or having more than one index field in the foreign key.<br /><br/>
3339 In Query-by-example (Query), automatic generation of the query
3340 LEFT JOIN from the foreign table.<br /><br/>
3341 </p>
3345 I get series of errors like "Warning: unable to parse url". How
3346 can this be fixed?</a></h4>
3347 <p>
3348 Your table neither have a primary key nor an unique one, so we must use a
3349 long expression to identify this row. This causes problems to parse_url
3350 function. The workaround is to create a primary or unique key.
3351 <br />
3352 </p>
3356 a MIME-Transformation onto!</a></h4>
3358 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3359 nested forms can be put inside the table where phpMyAdmin displays the results.
3360 You can, however, use any form inside of a table if keep the parent
3361 form-container with the target to tbl_row_delete.php and just put your own
3362 input-elements inside. If you use a custom submit input field, the form will
3363 submit itself to the displaying page again, where you can validate the
3364 $HTTP_POST_VARS in a transformation.
3366 For a tutorial on how to effectively use transformations, see our
3368 on the official phpMyAdmin-homepage.</p>
3372 MySQL server</a></h4>
3374 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3377 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3378 the quote-character (") is interpreted as an identifier quote character and
3379 not as a string quote character, which makes many internal phpMyAdmin
3381 statements. There is no workaround to this behaviour. News to this item will
3382 be posted in Bug report
3383 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3384 </p>
3388 more that one column with the same value
3389 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3390 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3392 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3393 can use it for the Edit and Delete links.</p>
3398 <p> phpMyAdmin uses a quick method to get the row count, and this method
3399 only returns an approximate count in the case of InnoDB tables. See
3401 a way to modify those results, but
3402 this could have a serious impact on performance.</p>
3407 <p> The number of records in queries containing COUNT and GROUP BY is
3408 not correctly calculated. Also, sorting results of a query like
3413 containing an hyphen.
3414 </a></h4>
3415 <p>
3416 The tests I have made with current MySQL 4.1.11 API shows that the
3417 API does not accept this syntax for the USE command. Enclosing the
3418 db name with backquotes works. For further confusion, no backquotes
3419 are needed with command-line mysql.
3420 </p>
3423 <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>
3424 <p>
3425 This has been a known limitation of phpMyAdmin since the beginning and
3426 it's not likely to be solved in the future.
3427 </p>
3429 <!-- Begin: Excel import limitations -->
3432 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3433 <p>
3434 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target=_blank>PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3435 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3436 <br /><br />
3437 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3438 </p>
3441 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3442 <p>
3443 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3444 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3445 </p>
3448 <a href="#faq3_17">3.17 When I import an Excel spreadsheet, my custom cell types are not represented as they are in Excel.</a></h4>
3449 <p>
3450 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3451 consider using a built-in type. These are almost always guarenteed to import correctly.
3452 </p>
3454 <!-- End: Excel import limitations -->
3455 <!-- Begin: CSV import limitations -->
3458 <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>
3459 <p>
3460 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.
3461 </p>
3463 <!-- End: CSV import limitations -->
3464 <!-- Begin: Import type-detection limitations -->
3467 <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>
3468 <p>
3469 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
3470 you will have to edit the structure to your liking post-import.
3471 <br /><br />
3472 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
3473 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.
3474 </p>
3476 <!-- End: Import type-detection limitations -->
3478 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3481 <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
3482 need to install it for each customer.
3483 </a></h4>
3484 <p>
3485 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3486 your users. The development of this feature was kindly sponsored by
3487 NetCologne GmbH.
3488 This requires a properly setup MySQL user management and phpMyAdmin
3489 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3491 </p>
3495 access.
3496 </a></h4>
3497 <p>
3498 This depends on your system.<br />
3499 If you're running a server which cannot be accessed by other people, it's
3500 sufficient to use the directory protection bundled with your webserver
3502 If other people have telnet access to your server, you should use
3503 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3504 <br /><br />
3505 Suggestions:
3506 </p>
3507 <ul>
3508 <li>
3510 </li>
3511 <li>
3512 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3513 is a user whose password is only known to you, and apache is the
3514 group under which Apache runs.
3515 </li>
3516 <li>
3517 You should use PHP safe mode, to protect from other users that try
3519 </li>
3520 </ul>
3525 </a></h4>
3526 <p>
3531 </p>
3534 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3535 authentication.
3536 </a></h4>
3540 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3541 and/or
3543 are wrong.</li>
3545 <li>You have already setup a security mechanism for the
3546 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3547 phpMyAdmin's authentication, so remove it.</li>
3548 </ul>
3555 and put the privileges you want. For example,
3557 would let a user create/manage his/her database(s).</p>
3562 <p> If you have existing rules from an old .htaccess file, you can take them
3565 be a major benefit here if your installation is suited to using it. Then
3566 you can just add those updated lines into the
3570 <p> If you want a pre-made sample, you can try this fragment. It stops the
3571 'root' user from logging in from any networks other than the private
3574 <pre>
3575 //block root from logging in except from the private networks
3576 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3577 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3578 'deny root from all',
3579 'allow root from localhost',
3583 );
3584 </pre>
3589 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3590 different than the one set in your
3592 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3593 while a domain name is defined in the config file.</p>
3598 <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>
3604 when trying to create a table with more than 14 fields.
3605 </a></h4>
3606 <p>
3607 We could reproduce this problem only under Win98/98SE. Testing under
3608 WinNT4 or Win2K, we could easily create more than 60 fields.
3609 <br />
3610 A workaround is to create a smaller number of fields, then come back to
3611 your table properties and add the other fields.
3612 </p>
3616 <p>
3617 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3618 with each script/website that use forms.<br />
3619 Upgrade or downgrade your Xitami server.
3620 </p>
3623 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3624 <p>
3625 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3626 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3627 don't seem to work.<br />
3629 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3630 the user's temporary directory, so they must be moved before closing
3631 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3634 </p>
3638 Explorer never stores the cookies.
3639 </a></h4>
3640 <p>
3641 MS Internet Explorer seems to be really buggy about cookies, at least till
3643 in this area!
3644 <br />
3645 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3646 work!
3647 </p>
3651 rows.
3652 </a></h4>
3653 <p>
3655 </p>
3658 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3659 when trying to modify a row in a table with many fields, or with a text field
3660 </a></h4>
3661 <p>
3662 Your table neither have a primary key nor an unique one, so we must use a
3663 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
3664 those browsers, and this not happen in Netscape, for example. The
3665 workaround is to create a primary or unique key, or use another browser.
3666 <br />
3667 </p>
3671 page.
3672 </a></h4>
3673 <p>
3674 Some browsers support right-clicking into the frame you want to refresh,
3675 just do this in the right frame.<br />
3676 </p>
3680 query box.
3681 </a></h4>
3682 <p>
3683 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3684 Mozilla versions.<br />
3685 </p>
3689 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3690 </a></h4>
3691 <p>
3692 This is a Mozilla bug (see bug #26882 at
3694 </p>
3699 </a></h4>
3700 <p>
3701 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3702 data in octet-stream mode. Since we can't detect the specific Netscape
3703 version, we cannot workaround this bug.
3704 </p>
3708 wrong.</a></h4>
3710 <p> Please ensure that you have set your browser's character set to the one of the
3711 language file you have selected on phpMyAdmin's start page.
3712 Alternatively, you can try the auto detection mode that is supported by the
3713 recent versions of the most browsers.</p>
3716 <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
3719 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3720 Netscape and Mozilla do not have this problem.</p>
3723 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3724 I cannot manage two servers: I log in to the first one, then the other one,
3725 but if I switch back to the first, I have to log in on each operation.</a></h4>
3731 but nothing happens after that, only a blank screen.</a></h4>
3742 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3747 address and you are starting
3749 containing a domain name, or the reverse situation.</li>
3750 <li>Security settings in IE and/or Microsoft Security Center are
3751 too high, thus blocking scripts execution.</li>
3752 <li>The Windows Firewall is blocking Apache and MySQL. You must
3756 </ul>
3759 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3760 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3761 installed in their Firefox is causing the problem.</p>
3765 clause is generated when I browse a table.</a></h4>
3766 <p> This happens only when both of these conditions are met: using the
3776 </a></h4>
3777 <p>
3778 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3779 specifying a wrong field-type.<br />
3780 Common errors include:
3781 </p>
3782 <ul>
3785 </ul>
3786 <p>
3787 Also, look at the syntax chapter in the MySQL manual to confirm that your
3788 syntax is correct.
3789 </p>
3793 phpMyAdmin generates only one index with those two fields.
3794 </a></h4>
3795 <p>
3796 This is the way to create a multi-fields
3797 index. If you want two indexes, create the first one when creating the
3798 table, save, then display the table properties and click the Index link to
3799 create the other index.
3800 </p>
3804 <p>
3805 Since version 2.2.3, you have a checkbox for each field that can be null.
3807 field's value. Since version 2.5.5, you have to use the checkbox to get
3809 a literal NULL in the field, and not a NULL value (this works in PHP4).
3810 </p>
3815 <p> Click on a database or table name in the left frame, the properties will be
3817 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3818 statements that can be used to recreate your database/table.
3819 <br /><br />
3821 transmit the resulting dump to your station. Depending on your PHP
3822 configuration, you will see options to compress the dump. See also the
3824 configuration variable.<br /><br />
3827 this document.</p>
3832 </a></h4>
3834 <p> Click on a database name in the left frame, the properties will be
3836 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3838 the path to your dump filename, or use the Browse button. Then click Go.
3839 <br /><br />
3841 that you upgrade to take advantage of the new features.
3842 <br /><br />
3844 in this document.
3845 </p>
3850 <p> Here is an example with the tables persons, towns and countries, all
3852 table, create it as explained in the configuration section. Then create the
3853 example tables:</p>
3855 <pre>
3856 CREATE TABLE REL_countries (
3857 country_code char(1) NOT NULL default '',
3858 description varchar(10) NOT NULL default '',
3859 PRIMARY KEY (country_code)
3860 ) TYPE=MyISAM;
3862 INSERT INTO REL_countries VALUES ('C', 'Canada');
3864 CREATE TABLE REL_persons (
3865 id tinyint(4) NOT NULL auto_increment,
3866 person_name varchar(32) NOT NULL default '',
3868 country_code char(1) NOT NULL default '',
3869 PRIMARY KEY (id)
3870 ) TYPE=MyISAM;
3872 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3873 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3875 CREATE TABLE REL_towns (
3877 description varchar(30) NOT NULL default '',
3878 PRIMARY KEY (town_code)
3879 ) TYPE=MyISAM;
3881 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3882 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3883 </pre>
3889 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3893 </ul>
3901 <li>In the fields row, choose persons.person_name and click the
3903 <li>Do the same for towns.description and countries.descriptions in the
3906 the correct joins have been generated</li>
3908 </ul>
3912 <p>
3913 Starting from the previous example, create the pma_table_info as explained
3914 in the configuration section, then browse your persons table,
3915 and move the mouse over a town code or country code.
3916 <br /><br />
3917 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3918 enables: drop-down list of possible values.
3919 </p>
3922 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3923 <p>
3926 <br /><br />
3927 Then you need to think about your schema layout. Which tables will go on
3928 which pages?
3929 </p>
3930 <ul>
3936 page and click Go. If you like, you
3938 linked tables onto the new page.</li>
3939 <li>Select the name of the new page (making sure the Edit radio button
3940 is selected) and click Go.</li>
3942 Coordinates are relative; your diagram will
3943 be automatically scaled to fit the page. When initially placing tables
3944 on the page, just pick any coordinates -- say, 50x50. After clicking
3946 position the element correctly.</li>
3948 first be sure to click the Save
3949 button beneath the list of tables and coordinates, to save any changes
3950 you made there. Then scroll all the way down, select the
3952 you want, and click Go.</li>
3953 <li>Internet Explorer for Windows may suggest an incorrect filename when
3958 browsers on Windows, do not have this problem.</li>
3959 </ul>
3963 columns!</a></h4>
3965 <p> No, it's MySQL that is doing
3971 underscores in the database name?</a></h4>
3973 <p> If you do not put a backslash before the underscore, this is a wildcard
3976 john2db ...<br /><br />
3978 If you put a backslash before the underscore, it means that the database
3979 name will have a real underscore.</p>
3983 statistics pages?</a></h4>
3994 if it already exists during the import. It does NOT drop the table after
3995 your export, it only affects the import file.</li>
3997 Otherwise, you may get an error if the table name exists but has a
3998 different structure.</li>
4000 (if any) will be included in backup.</li>
4002 field and table names formed with special characters are protected.</li>
4004 types set in the pmadb in the dump as
4006 </li>
4007 </ul>
4012 command, for better documentation (but resulting file is bigger).</li>
4014 once the INSERT verb and the table name.</li>
4017 </li>
4019 more info is provided in the
4021 but basically with this selected, invalid values are adjusted and
4022 inserted rather than causing the entire statement to fail.</li>
4023 </ul>
4027 in its name.</a></h4>
4030 is the normal way to reference a database and table name. Worse, MySQL
4031 will usually let you create a database with a dot, but then you cannot
4032 work with it, nor delete it.</p>
4045 for usage.<br />
4046 On a more recent pear version, I had problems with the state of Net_DIME
4047 being beta, so this single command
4049 needed modules.<br />
4050 If you use the Validator, you should be aware that any
4052 submit will be stored anonymously (database/table/column names,
4053 strings, numbers replaced with generic values). The Mimer
4056 We utilize it as free SOAP service.</p>
4060 it, but MySQL says "BLOB column '...' used in key specification without
4063 <p> The right way to do this, is to create the field without any indexes,
4065 dialog. On this page, you will be able to choose your BLOB field, and
4066 set a size to the index, which is the condition to create an index on
4067 a BLOB field.</p>
4071 editing fields?</a></h4>
4073 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4074 with many editing fields (table structure changes, row editing, etc.)
4075 (must be enabled in configuration - see.
4077 You can also have a look at the directive
4079 ('vertical') and see if this eases up editing for you.</p>
4083 WTF is this feature then useful for?</a></h4>
4085 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4086 on them. Otherwise you could just put a comment on the field. Because entering
4087 your own mimetype will cause serious syntax checking issues and validation,
4088 this introduces a high-risk false-user-input situation. Instead you have to
4089 initialize mimetypes using functions or empty mimetype definitions.<br />
4090 Plus, you have a whole overview of available mimetypes. Who knows all those
4091 mimetypes by heart so he/she can enter it at will?</p>
4095 can't I see any bookmarks below the query box? What is this variable for?
4096 </a></h4>
4098 <p> Any query you have executed can be stored as a bookmark on the page where the
4099 results are displayed. You will find a button labeled 'Bookmark this query'
4100 just at the end of the page.<br />
4101 As soon as you have stored a bookmark, it is related to the database you run
4102 the query on. You can now access a bookmark dropdown on each page, the query
4103 box appears on for that database.<br /><br />
4105 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4109 aware of that you HAVE to create a valid query, otherwise your query won't be
4110 even able to be stored in the database.<br />
4112 for your query will remain the way it is, but will be stripped of the /**/
4113 chars. So you can use:<br /><br />
4117 which will be expanded to<br /><br />
4121 in your query, where VARIABLE is the string you entered in the input box. If
4122 an empty string is provided, no replacements are made.<br /><br />
4124 A more complex example. Say you have stored this query:<br /><br />
4126 <br /><br />
4129 the full query will be:<br /><br />
4132 <br /><br />
4136 spaces inserted there
4137 will be later also inserted as spaces in your query and may lead to unexpected
4138 results especially when
4140 Your initial query which is going to be stored as a bookmark has to yield at
4141 least one result row so
4142 you can store the bookmark. You may have that to work around using well
4146 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4147 include exported table?</a></h4>
4149 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4150 document should look like following one (assuming you have table
4153 <pre>
4154 \documentclass{article} % or any class you want
4155 \usepackage{longtable} % for displaying table
4156 \begin{document} % start of document
4157 \include{table} % including exported table
4158 \end{document} % end of document
4159 </pre>
4163 access them.
4164 </a></h4>
4167 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4168 enable users to see all the database names.
4171 So if your users do not need those privileges, you can remove them and their
4172 databases list will shorten.</p>
4176 possible values for a field, based on some foreign table?</a></h4>
4178 <p> You have to setup appropriate links between the tables, and also
4182 foreign table, a drop-down list of values will be available.
4183 You will see two lists of values, the first list containing the key
4184 and the display field, the second list containing the display field
4185 and the key. The reason for this is to be able to type the first
4186 letter of either the key or the display field.<br /><br />
4188 For 100 values or more, a distinct window will appear, to browse foreign
4189 key values and choose one. To change the default limit of 100, see
4190 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4194 automatically when entering Browse mode for a table?</a></h4>
4196 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4197 </p>
4201 Excel files, how can I enable that?</a></h4>
4203 <p> Current version does support direct export to Microsoft Excel and Word
4204 versions 2000 and newer. If you need export older versions, you can use
4206 which works out of the box or you can
4208 several problems, most important are limitation of cell content to 255
4209 chars and no support for charsets, so think carefully whether you want to
4210 enable this.</b>. For enabling this you need to set
4214 module Spreadsheet_Excel_Writer into php include path. The
4215 installation can be done by following command:</p>
4217 <pre>
4218 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
4219 </pre>
4221 <p> First part of switches set we want to install beta version of that module
4222 (no stable version available yet) and then we tell pear we want to satisfy
4223 dependencies.</p>
4225 <p> If you are running in PHP safe mode, you will have to set
4228 modules are located, for example:</p>
4230 <pre>
4231 safe_mode_include_dir = /usr/local/lib/php
4232 </pre>
4236 <pre>
4237 cd phpMyAdmin
4238 mkdir tmp
4239 chmod o+rwx tmp
4240 </pre>
4244 what happens to my column comments stored in pmadb?</a></h4>
4246 <p> Automatic migration of a table's pmadb-style column comments to the native
4247 ones is done whenever you enter Structure page for this table.</p>
4252 <p> First, for general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. We currently support streaming if you are running MySQL 5.1 with the PBXT and PBMS storage engines.</p>
4254 <ol>
4255 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of something like "localhost".</li>
4256 <li>A current limitation is that your first login via phpMyAdmin to a freshly-started server must be done with an account that has the SUPER privilege.</li>
4257 <li>On your target database, go to Operations and in the "BLOB Repository" section, click "Enable". This creates the PBMS system tables inside your database.</li>
4258 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4259 <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 column instead of the repository.</li>
4260 <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 but in case it's incorrect, it's possible to edit it by clicking on the displayed MIME-type.</li>
4261 </ol>
4268 <p> Our Bug Tracker is located at
4270 under the Bugs section.<br /><br />
4272 But please first discuss your bug with other users:<br />
4278 existing language, where do I start?</a></h4>
4280 <p> Always use the current SVN version of your language file.
4282 don't know how to get the SVN version, please ask one of the developers.
4283 <br />
4284 Please note that we try not to use HTML entities like &eacute; in
4285 the translations, since we define the right character set in the file.
4286 With HTML entities, the text on JavaScript messages would not
4287 display correctly.
4288 However there are some entities that need to be there, for quotes
4289 ,non-breakable spaces, ampersands, less than, greater than.<br />
4290 You can then put your translations, as a zip file to avoid losing special
4291 characters, on the sourceforge.net translation tracker.<br />
4292 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4293 list, because this is where we ask for translations of new messages.</p>
4297 phpMyAdmin. How should I proceed?</a></h4>
4302 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4303 </li>
4305 <li>generate patch with your changes:
4307 </li>
4310 tracker of the phpMyAdmin project</a>.
4311 </li>
4312 </ol>
4314 <p> Write access to the SVN tree is granted only to experienced developers who
4315 have already contributed something useful to phpMyAdmin.<br />
4321 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4323 <p> Please refer to
4324 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4325 </p>
4330 <p> If you use Apache web server, phpMyAdmin exports information about
4331 authentication to Apache environment and it can be used in Apache logs.
4332 Currently there are two variables available:
4333 </p>
4334 <dl>
4336 <dd>User name of currently active user (he does not have to be logged
4337 in).</dd>
4344 </dl>
4345 <p>
4347 </p>
4348 <pre>
4351 </pre>
4352 <p>
4353 You can then use any log analyzing tools to detect possible break in
4354 attempts.
4355 </p>
4361 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4362 It allows you to connect to local as well as remote servers.This requires you to enter
4363 server host name, username, password, port and the name of the database. Therefore you can
4364 now synchronize your databases placed on the same server or some remote server.
4365 </p>
4367 <p>For more details see <a href="./documentation-gsoc/Synchronization_User Manual.htm">How to synchronize</a>
4368 </p>
4370 <!-- DEVELOPERS -->
4373 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4374 great features have been written by other people and you too can help to
4375 make phpMyAdmin a useful tool.</p>
4377 <p> If you're planning to contribute source, please read the following
4378 information:</p>
4384 it free from other code.<br />
4385 Commonly used functions should be added to
4388 <li>Obviously, you're free to use whatever coding style you want. But
4389 please try to keep your code as simple as possible: beginners are
4390 using phpMyAdmin as an example application.<br />
4391 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4392 compliant on one hand, they fit the
4395 coding standards</a>
4396 on the other hand. Please pay attention to this.</li>
4397 <li>Please try to keep up the file-naming conventions. Table-related stuff
4400 <li>Please don't put message strings in your code, instead add the string
4405 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4406 better debug and profile their code.<br />
4407 Please see the
4409 options for more information.<br />
4410 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4411 lost during its re-entry into Earth's atmosphere and in memory of the
4412 brave men and women who gave their lives for the people of Earth.</li>
4413 </ul>
4417 <pre>
4428 </pre>
4430 <p>
4431 This program is free software; you can redistribute it and/or modify
4432 it under the terms of the GNU General Public License version 2,
4433 as published by the Free Software Foundation.
4434 </p>
4436 <p>
4437 This program is distributed in the hope that it will be useful,
4438 but WITHOUT ANY WARRANTY; without even the implied warranty of
4439 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4440 GNU General Public License for more details.
4441 </p>
4443 <p>
4444 You should have received a copy of the GNU General Public License
4445 along with this program; if not, write to the Free Software
4447 </p>
4449 <!-- CREDITS -->
4454 <ul>
4457 <ul>
4460 </ul></li>
4463 <ul>
4468 </ul></li>
4471 <ul>
4477 </ul></li>
4480 <ul>
4482 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4483 generate XHTML1.0 and CSS2 compliant codes</li>
4486 </ul></li>
4489 <ul>
4497 </ul></li>
4500 <ul>
4505 </ul></li>
4508 <ul>
4511 </ul></li>
4514 <ul>
4516 </ul></li>
4519 <ul>
4522 </ul></li>
4525 <ul>
4529 </ul></li>
4532 <ul>
4535 </ul></li>
4538 <ul>
4545 </ul></li>
4548 <ul>
4552 </ul></li>
4555 <ul>
4561 </ul></li>
4564 (http://sf.net/projects/phpmysqlformgen/)
4565 <ul>
4567 </ul></li>
4570 <ul>
4572 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4577 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4581 </ul></li>
4584 <ul>
4586 </ul></li>
4589 <ul>
4591 </ul></li>
4594 <ul>
4596 </ul></li>
4599 <ul>
4600 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4601 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4602 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4603 </ul></li>
4606 <ul>
4608 </ul></li>
4611 <ul>
4613 </ul></li>
4616 <ul>
4618 </ul></li>
4621 <ul>
4624 </ul></li>
4627 <ul>
4630 </ul></li>
4633 <ul>
4635 </ul></li>
4638 <ul>
4641 </ul></li>
4643 <li>Ivan A Kirillov
4644 <ul>
4646 </ul></li>
4649 <ul>
4651 </ul></li>
4654 <ul>
4656 </ul></li>
4659 <ul>
4661 </ul></li>
4664 <ul>
4666 </ul></li>
4668 </ul>
4670 <p>
4671 And also to the following people who have contributed minor changes,
4672 enhancements, bugfixes or support for a new language since version 2.1.0:
4673 </p>
4675 <p>
4676 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4677 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4678 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4679 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4681 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4682 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4683 Luís V., Martijn W. van der Lee,
4684 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4686 </p>
4691 <p>
4692 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4693 to create a web-based interface to MySQL using PHP3. Although I have not
4694 used any of his source-code, there are some concepts I've borrowed from
4695 him. phpMyAdmin was created because Peter told me he wasn't going to
4696 further develop his (great) tool.
4697 </p>
4698 <p>
4699 Thanks go to
4700 </p>
4701 <ul>
4703 code for the check when dropping a table or database. He also suggested
4704 that you should be able to specify the primary key on tbl_create.php3. To
4705 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4706 well as a bug-report. Plus many smaller improvements.
4707 </li>
4709 were introduced in 1.3.0 (including quite significant ones like the
4710 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4711 bug-fixes and help.
4712 </li>
4714 language-independent by outsourcing the strings to a separate file. He
4715 also contributed the French translation.
4716 </li>
4718 tbl_select.php3, a feature to display only some fields from a table.
4719 </li>
4721 functions in tbl_change.php3. He also added the
4723 </li>
4725 servers and is a regular contributor for bug-fixes.
4726 </li>
4728 features for 2.0.6.
4729 </li>
4730 </ul>
4731 <p>
4732 The following people have contributed minor changes, enhancements, bugfixes
4733 or support for a new language:
4734 </p>
4735 <p>
4736 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4737 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4738 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4739 G. Wieggers.
4740 </p>
4741 <p>
4742 And thanks to everyone else who sent me email with suggestions, bug-reports
4743 and or just some feedback.
4744 </p>
4750 <ul>
4752 - the default name of Apache's directory-level configuration file.</li>
4756 - a software application that enables a user to display and interact with
4757 text, images, and other information typically located on a web page at a
4758 website on the World Wide Web.</li>
4760 - a free software/open source data compression algorithm and program
4761 developed by Julian Seward.</li>
4763 - an important World Wide Web technology that enables a client web browser
4764 to request data from a program executed on the Web server.</li>
4766 - a log or record of changes made to a project.</li>
4768 - a computer system that accesses a (remote) service on another computer
4769 by some kind of network.</li>
4771 - a set of data values of a particular simple type, one for each row of
4772 the table.</li>
4774 - a packet of information sent by a server to a World Wide Web browser
4775 and then sent back by the browser each time it accesses that server.</li>
4777 - Comma-separated values</li>
4780 - an organized collection of data.</li>
4783 - a PHP module that extends PHP with additional functionality.</li>
4785 - a list of commonly asked question and there answers.</li>
4787 - one part of divided data/columns.</li>
4789 - a field or group of fields in a database record that point to a key
4790 field or group of fields forming a key of another database record in some
4791 (usually different) table.</li>
4793 - the free PDF library</li>
4795 GD Graphics Library</a> - a library by Thomas Boutell and others for
4796 dynamically manipulating images.</li>
4799 - gzip is short for GNU zip, a GNU free software file compression
4800 program.</li>
4802 - any machine connected to a computer network, a node that has a hostname.</li>
4804 - the unique name by which a network attached device is known on a network.</li>
4806 (HyperText Transfer Protocol)</a>
4807 - the primary method used to transfer or convey information on the World
4808 Wide Web.</li>
4811 additional security measures.</li>
4812 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4813 - a set of Internet-based services for servers using Microsoft Windows.</li>
4815 - a feature that allows quick access to the rows in a table.</li>
4817 - a data-oriented protocol used by source and destination hosts for
4818 communicating data across a packet-switched internetwork.</li>
4820 - a unique number that devices use in order to identify and communicate
4821 with each other on a network utilizing the Internet Protocol standard.</li>
4823 (Internet Server Application Programming Interface)</a>
4824 - the API of Internet Information Services (IIS).</li>
4826 - a business or organization that offers users access to the Internet and related services.</li>
4828 - a most commonly used standard method of lossy compression for
4829 photographic images.</li>
4835 - line of personal computers is designed, developed, manufactured, and
4836 marketed by Apple Computer.</li>
4837 <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>
4838 - the operating system which is included with all currently shipping Apple
4839 Macintosh computers in the consumer and professional markets.</li>
4841 - a cryptographic library.</li>
4843 - the MCrypt PHP extension.</li>
4844 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4845 - an Internet Standard for the format of e-mail.</li>
4847 - some sort of extension for the Apache Webserver.</li>
4849 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4850 Management System (DBMS).</li>
4852 - the improved MySQL client PHP extension.</li>
4854 - the MySQL client PHP extension.</li>
4856 - open standard for office documents.</li>
4857 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4858 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4860 (Portable Document Format)</a>
4861 - a file format developed by Adobe Systems for representing two
4862 dimensional documents in a device independent and resolution independent
4863 format.</li>
4865 - the PHP Extension and Application Repository.</li>
4867 - the perl-compatible regular expression functions for PHP</li>
4869 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4870 programming language used mainly for developing server-side applications
4871 and dynamic web content, and more recently, a broader range of software
4872 applications.</li>
4874 - a connection through which data is sent and received.</li>
4876 - Request for Comments (RFC) documents are a series of memoranda
4877 encompassing new research, innovations, and methodologies applicable to
4878 Internet technologies.</li>
4882 - represents a single, implicitly structured data item in a table.</li>
4884 - a computer system that provides services to other computing
4885 systems over a network.</li>
4886 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4887 - handlers for different table types</li>
4889 - a form of inter-process communication.</li>
4891 Sockets Layer)</a>
4892 - a cryptographic protocol which provides secure communication on the Internet.</li>
4894 - Structured Query Language</li>
4896 - a set of data elements (cells) that is organized, defined and stored as
4897 horizontal rows and vertical columns where each item can be uniquely
4898 identified by a label or key or by it?s position in relation to other items.</li>
4901 - a type of archive file format: the Tape ARchive format.</li>
4903 - one of the core protocols of the Internet protocol suite.</li>
4907 - a sequence of characters, conforming to a standardized format, that is
4908 used for referring to resources, such as documents and images on the
4909 Internet, by their location.</li>
4911 - A computer (program) that is responsible for accepting HTTP requests
4912 from clients and serving them Web pages.</li>
4914 - a W3C-recommended general-purpose markup language for creating
4915 special-purpose markup languages, capable of describing many different
4916 kinds of data.</li>
4918 - a popular data compression and archival format.</li>
4920 - an open-source, cross-platform data compression library by Jean-loup
4921 Gailly and Mark Adler.</li>
4922 </ul>
4923 </div>
4926 <li>Copyright © 2003 - 2009 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
4929 <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>
4930 </ul>
4932 </body>
4933 </html>