| blob | 12de63fd04c612c12cdc56d7966b7823bd649d96 |
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 logs 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>
1232 <dd>Disable using <tt>INFORMATION_SCHEMA</tt> to retrieve information (use <tt>SHOW</tt> commands instead), because of speed issues when many databases are present. Currently used in some parts of the code, more to come.
1233 </dd>
1234 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1236 DATABASES</tt> command used to fetch the name of available databases will
1237 probably be too slow, so it can be replaced by faster commands (see
1239 </dd>
1241 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1242 </dd>
1243 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1244 <dd>Name of session which will be used for signon authentication method.
1245 </dd>
1247 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1248 </dd>
1250 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1251 </dd>
1254 <dd>If you have more than one server configured, you can set
1256 that server when phpMyAdmin is started, or set it to 0 to be given a
1257 list of servers without logging in.<br />
1259 MUST be set to that server.</dd>
1262 <dd>The maximum number of database names to be displayed in the
1263 navigation frame and the database list.</dd>
1266 <dd>The maximum number of table names to be displayed in the
1267 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1268 when in Light mode.</dd>
1271 <dd>The maximum number of characters when a SQL query is displayed. The
1272 default limit of 1000 should be correct to avoid the display of tons
1273 of hexadecimal codes that represent BLOBs, but some users have real
1274 SQL queries that are longer than 1000 characters. Also, if a query's
1275 length exceeds this limit, this query is not saved in the history.</dd>
1278 <dd>Defines whether to use GZip output buffering for increased
1280 Set to true/false for enabling/disabling. When set to 'auto' (string),
1281 phpMyAdmin tries to enable output buffering and will automatically disable
1282 it if your browser has some problems with buffering. IE6 with a certain patch
1283 is known to cause data corruption when having enabled buffering.</dd>
1286 <dd>Whether persistent connections should be used or not (mysql_connect or
1287 mysql_pconnect).</dd>
1293 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1294 to zero, no time limit is imposed.<br />
1295 This setting is used while importing/exporting dump files and in the
1296 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1299 <dd>Set the number of bytes a script is allowed to allocate. If set
1300 to zero, no limit is imposed.<br />
1301 This setting is used while importing/exporting dump files and at some
1302 other places in phpMyAdmin so you definitely don't want to put here
1303 a too low value. It has no effect when PHP is running in safe mode.<br />
1304 You can also use any string as in php.ini, eg. '16M'. Ensure
1308 <dd>Mark used tables and make it possible to show databases with locked
1313 generated by phpMyAdmin should be displayed or not.</dd>
1316 <dd>Defines whether normal users (non-administrator) are allowed to
1317 delete their own database or not. If set as FALSE, the link "Drop
1319 mydatabase" will be rejected. Quite practical for
1321 customers.<br />
1322 Please note that this limitation of SQL queries is not as strict as
1323 when using MySQL privileges. This is due to nature of SQL queries
1324 which might be quite complicated. So this choice should be viewed as
1325 help to avoid accidental dropping rather than strict privilege
1326 limitation.</dd>
1330 displayed when you're about to lose data.</dd>
1333 <dd>Define whether the previous login should be recalled or not in cookie
1334 authentication mode.<br /><br />
1336 This is automatically disabled if you do not have configured
1338 </dd>
1341 <dd>Define how long is login cookie valid. Please note that php
1342 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1343 might limit session validity and if session is lost, login cookie is
1345 at least as high is $cfg['LoginCookieValidity'] is set.</dd>
1349 means that it will be kept for existing session. This is recommended
1350 for not trusted environments.</dd>
1353 <dd>If enabled (default), logout deletes cookies for all servers,
1354 otherwise only for current one. Setting this to false makes it easy to
1355 forget to log out from other server, when you are using more of
1356 them.</dd>
1362 <dd>Define whether phpMyAdmin will continue executing a multi-query
1363 statement if one of the queries fails. Default is to abort execution.</dd>
1366 <dd>Define whether phpMyAdmin will output the results of each query of a
1367 multi-query statement embedded into the
1372 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1373 <br /><br />
1376 MySQL servers behind the firewall where your
1378 </dd>
1381 <dd>Defines whether to use a select-based menu and display only the current
1382 tables in the left frame (smaller page). Only in Non-Lightmode you can
1383 use the feature to display nested folders using
1385 </dd>
1388 <dd>In light mode, defines whether to display the names of databases (in the
1389 selector) using a tree, see also
1391 </dd>
1394 string or array</dt>
1395 <dd>The string used to separate the parts of the database name when showing
1396 them in a tree. Alternatively you can specify more strings in an array
1397 and all of them will be used as a separator.</dd>
1400 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1401 This means if you have tables like 'first__second__third' this will be
1403 If set to FALSE or empty, the feature is disabled. NOTE: You should
1404 not use this separator at the beginning or end of a
1405 table name or multiple times after another without any other
1406 characters in between.</dd>
1409 <dd>Defines how many sublevels should be displayed when splitting
1410 up tables by the above separator.</dd>
1413 <dd>Defines whether to display table comment as tool-tip in left frame or
1414 not.</dd>
1417 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1418 comment and the real name. That means that if you have a table called
1419 'user0001' and add the comment 'MyName' on it, you will see the name
1420 'MyName' used consequently in the left frame and the tool-tip shows
1421 the real name of the DB.</dd>
1424 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1426 When setting this to 'nested', the Alias of the Tablename is only used
1427 to split/nest the tables according to the
1429 directive. So only the folder is called like the Alias, the tablename itself
1430 stays the real tablename.</dd>
1433 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1436 <dd>Enter URL where logo in the navigation frame will point to.
1437 For use especially with self made theme which changes this.
1446 <dd>Defines whether or not to display a server choice at the top of the left frame.
1447 Defaults to FALSE.</dd>
1449 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1450 Defaults to FALSE (drop-down).</dd>
1452 <dd>Defines whether to display database choice in light navigation frame as links
1453 instead of in a drop-down. Defaults to 'auto' - on main page list is
1454 shown, when database is selected, only drop down is displayed.</dd>
1457 <dd>Defines the tab displayed by default when clicking the small
1458 icon next to each table name in the navigation panel. Possible
1464 <dd>Defines whether or not to display space usage and statistics about databases
1465 and tables.<br />
1466 Note that statistics requires at least MySQL 3.23.3 and that, at this
1467 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1470 <dd>Defines whether to display detailed server information on main page.
1471 You can additionally hide more information by using
1473 </dd>
1478 </dt>
1481 not at the starting main (right) frame. This setting
1482 does not check MySQL commands entered directly.<br /><br />
1484 Please note that to block the usage of phpinfo() in scripts, you
1491 hard coded password value in the configuration file, end users can't
1492 be allowed to change their passwords.</dd>
1495 <dd>Defines whether to suggest a database name on the
1499 <dd>Defines whether navigation bar buttons and the right panel top menu
1500 contain text or symbols only. A value of TRUE displays icons, FALSE
1501 displays text and 'both' displays both icons and text.</dd>
1504 <dd>Defines whether a user should be displayed a
1508 <dd>Number of rows displayed when browsing a result set. If the result set
1515 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1519 from editing when browsing a table's content. Valid values are:
1524 </ul>
1525 </dd>
1528 <dd>Defines whether or not MySQL functions fields should be initially
1529 displayed in edit/insert mode. Since version 2.10, the user can
1530 toggle this setting from the interface.
1531 </dd>
1534 <dd>Defines which type of editing controls should be used for CHAR and
1535 VARCHAR fields. Possible values are:
1536 <ul><li>input - this allows to limit size of text to size of field in
1537 MySQL, but has problems with newlines in fields</li>
1538 <li>textarea - no problems with newlines in fields, but also no
1539 length limitations</li>
1540 </ul>
1541 Default is old behavior so input.</dd>
1547 <dd>If there are fewer items than this in the set of foreign keys, then a
1548 drop-down box of foreign keys is presented, in the style described by the
1550 setting.</dd>
1553 <dd>For the foreign key drop-down fields, there are several methods of
1554 display, offering both the key and value data. The contents of the
1555 array should be one or both of the following strings:
1561 </dt>
1562 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1563 creating a dump file</dd>
1566 </dt>
1567 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1568 compressed exports. This doesn't affect smaller dumps and allows users to
1569 create larger dumps that won't otherwise fit in memory due to php
1570 memory limit. Produced files contain more GZip/BZip2 headers, but all
1571 normal programs handle this correctly.</dd>
1575 mainframe.</dd>
1579 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1584 <dd>How many columns will be utilized to display the tables on the
1585 database property view? Default is 1 column. When setting this to a
1586 value larger than 1, the type of the database will be omitted for more
1587 display space.</dd>
1591 <dd>Defines the tab displayed by default on server view. Possible
1598 <dd>Defines the tab displayed by default on database view. Possible
1603 <dd>Defines the tab displayed by default on table view. Possible
1610 points to the MySQL documentation (type depends
1611 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1612 generated.<br />
1614 for more information about MySQL manuals and their types.</dd>
1617 <dd>Type of MySQL documentation:
1623 </ul>
1624 </dd>
1627 <dd>Defines the default language to use, if not browser-defined or
1628 user-defined.<br />
1630 this setting.</dd>
1633 <dd>Defines the default connection collation to use, if not
1634 user-defined.<br />
1639 <dd>Force: always use this language (must be defined in the
1643 <dd>Limit list of available languages to those matching the given regular
1644 expression. For example if you want only Czech and English, you should
1648 <dd>Default character set to use for recoding of MySQL queries. This must be
1649 enabled and it's described by
1651 option.<br />
1652 You can give here any character set which is in
1654 array and this is just default choice, user can select any of them.</dd>
1657 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1658 support (compiled in or module) in PHP to allow MySQL queries recoding
1659 and used language file must have it enabled (by default only these
1660 which are in Unicode, just to avoid losing some characters).<br /><br />
1663 in the Export and Import pages, to choose the character set when
1664 exporting a file. The default value in this menu comes from
1666 </dd>
1669 <dd>You can select here which functions will be used for character set
1670 conversion. Possible values are:
1671 <ul><li>auto - automatically use available one (first is tested
1672 iconv, then recode)</li>
1675 </ul>
1676 Default is auto.</dd>
1679 <dd>Specify some parameters for iconv used in charset conversion. See
1682 used, so that invalid characters will be transliterated.</dd>
1685 <dd>Available character sets for MySQL conversion. You can add your own (any of
1686 supported by recode/iconv) or remove these which you don't use.
1687 Character sets will be shown in same order as here listed, so if you
1688 frequently use some of these move them to the top.</dd>
1693 default empty, you need to fill in some trusted proxy servers if you
1694 want to use rules for IP addresses behind proxy.<br /><br />
1696 The following example specifies that phpMyAdmin should trust a
1698 <pre>
1699 $cfg['TrustedProxies'] =
1701 </pre>
1702 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1703 client's IP address as usual.
1704 </dd>
1708 MIME transformations.<br />
1709 Possible values are:
1710 <ul><li>auto - automatically detect, this is a bit expensive
1712 according to your server real possibilities</li>
1715 </ul>
1716 Default is auto.
1717 </dd>
1720 <dd>
1721 We normally check the permissions on the configuration file to ensure
1722 it's not world writable. However, phpMyAdmin could be installed on
1723 a NTFS filesystem mounted on a non-Windows server, in which case the
1724 permissions seems wrong but in fact cannot be detected. In this case
1726 </dd>
1729 <dd>
1730 Limit for length of URL in links. When length would be above this limit, it
1731 is replaced by form with button.
1732 This is required as some web servers (IIS) have problems with long URLs.
1734 </dd>
1738 </dd>
1740 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1741 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1742 </dt>
1743 <dd>The background styles used for both the frames.
1746 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1748 <dd>The style used for the pointer in the navi frame.
1752 </dt>
1753 <dd>The color used for the database name in the navi frame.
1762 </dd>
1766 <dd>The style used for table headers. See
1771 </dd>
1775 </dd>
1777 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1779 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1781 </dt>
1783 The former feature highlights the row over which your mouse is passing
1784 and the latter lets you visually mark/unmark rows by clicking on
1785 them.<br />
1790 <dd>You put here a valid CSS font family value, for example
1795 <dd>You put here a valid CSS font family value, for example
1809 </dt>
1811 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1813 The Char* values are used for CHAR and VARCHAR editing (if configured
1817 </dt>
1821 </dt>
1822 <dd>Defines if the whole textarea of the query box will be selected on
1823 click.</dd>
1826 </dt>
1827 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1828 editing.</dd>
1831 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1832 Can be turned off by a toggle button on the browse page.</dd>
1836 </dt>
1837 <dd>Defines the place where modify and delete links would be put when
1838 tables contents are displayed (you may have them displayed both at the
1839 left and at the right).
1845 </dt>
1847 Define which one is displayed by default. The first mode displays each
1848 row on a horizontal line, the second rotates the headers by 90
1849 degrees, so you can use descriptive headers even though fields only
1850 contain small values and still print them out. The vertical mode sorts
1851 each row on a vertical lineup.<br /><br />
1853 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1854 the rotation of the header for horizontalflipped is done via CSS. If
1855 set to 'fake' PHP does the transformation for you, but of course this
1856 does not look as good as CSS.</dd>
1860 string or integer</dt>
1861 <dd>When editing/creating new columns in a table all fields normally get
1862 lined up one field a line. (default: 'horizontal'). If you set this to
1863 'vertical' you can have each field lined up vertically beneath each
1864 other. You can save up a lot of place on the horizontal direction and
1865 no longer have to scroll. If you set this to integer, editing of fewer
1866 columns will appear in 'vertical' mode, while editing of more fields
1867 still in 'horizontal' mode. This way you can still effectively edit
1868 large number of fields, while having full view on few of them.</dd>
1872 </dt>
1874 display of column comments in Browse or Property display. In browse
1875 mode, the comments are shown inside the header. In property mode,
1876 comments are displayed using a CSS-formatted dashed-line below the
1877 name of the field. The comment is shown as a tool-tip for that field.
1878 </dd>
1890 <dd>Whether to display a link to validate a query in any SQL Query box.
1897 <dd>
1898 The name of the directory where
1900 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1901 are available under a drop-down box when you click the database or
1902 table name, then the Import tab.
1903 <br /><br />
1905 If you want different directory for each user, %u will be replaced
1906 with username.<br /><br />
1910 compressed formats is enabled).<br /><br />
1912 This feature is useful when your file is too big to be uploaded via
1914 uploads are disabled in PHP.<br /><br />
1916 Please note that if PHP is running in safe mode, this directory must
1917 be owned by the same user as the owner of the phpMyAdmin scripts.
1918 <br /><br />
1922 alternatives.
1923 </dd>
1926 <dd>
1927 The name of the directory where dumps can be saved.<br /><br />
1929 If you want different directory for each user, %u will be replaced
1930 with username.<br /><br />
1932 Please note that the directory must exist and has to be writable for
1933 the user running webserver.<br /><br />
1935 Please note that if PHP is running in safe mode, this directory must
1936 be owned by the same user as the owner of the phpMyAdmin scripts.
1937 </dd>
1940 <dd>
1941 The name of the directory where temporary files can be stored.
1942 <br /><br />
1944 This is needed for native MS Excel export, see
1950 <br /><br />
1952 If the directory where phpMyAdmin is installed is subject to an
1954 temporary directory in some directory accessible by the web
1955 server. However for security reasons, this directory should be outside
1956 the tree published by webserver. If you cannot avoid having this
1957 directory published by webserver, place at least an empty
1959 possible.
1960 <br /><br />
1962 This directory should have as strict permissions as possible as the only
1963 user required to access this directory is the one who runs the
1964 webserver. If you have root privileges, simply make this user owner of
1965 this directory and make it accessible only by it:
1966 <br /><br />
1968 <pre>
1969 chown www-data:www-data tmp
1970 chmod 700 tmp
1971 </pre>
1973 If you cannot change owner of the directory, you can achieve a similar
1976 <pre>
1977 chmod 700 tmp
1978 setfacl -m "g:www-data:rwx" tmp
1979 setfacl -d -m "g:www-data:rwx" tmp
1980 </pre>
1982 If neither of above works for you, you can still make the directory
1984 system reading and writing data in this directory.
1985 </dd>
1988 <dd>
1989 In this array are defined default parameters for export, names of
1990 items are similar to texts seen on export page, so you can easily
1991 identify what they mean.
1992 </dd>
1995 <dd>
1996 In this array are defined default parameters for import, names of
1997 items are similar to texts seen on import page, so you can easily
1998 identify what they mean.
1999 </dd>
2002 <dd>
2003 Repeat the headers every X cells, or 0 to deactivate.
2004 </dd>
2012 </dt>
2013 <dd>
2014 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2015 or icon is always displayed on the left panel. If JavaScript is enabled in
2016 your browser, a click on this opens a distinct query window, which is
2017 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2018 changes to display a query box.<br /><br />
2020 The size of this query window can be customized with
2022 - both integers for the size in pixels. Note that normally, those
2024 theme you are using.<br /><br />
2028 opens the query window and puts the current query
2029 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2030 query in the right panel's query box.
2031 <br /><br />
2032 The usage of the JavaScript query window is recommended if you have a
2033 JavaScript enabled browser. Basic functions are used to exchange quite
2034 a few variables, so most 4th generation browsers should be capable to
2035 use that feature. It currently is only tested with Internet Explorer 6
2036 and Mozilla 1.x.
2037 <br /><br />
2039 to a table, which has to be created by you (see <a
2041 all your queries will be appended to the form, but only as long as
2042 your window is opened they remain saved.
2043 <br /><br />
2044 When using the JavaScript based query window, it will always get
2045 updated when you click on a new table/db to browse and will focus if
2046 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2047 the query window by checking the box "Do not overwrite this query from
2048 outside the window" below the query textarea. Then you can browse
2049 tables/databases in the background without losing the contents of the
2050 textarea, so this is especially useful when composing a query with
2051 tables you first have to look in. The checkbox will get automatically
2052 checked whenever you change the contents of the textarea. Please
2053 uncheck the button whenever you definitely want the query window to
2054 get updated even though you have made alterations.
2055 <br /><br />
2058 <br /><br />
2059 The query window also has a custom tabbed look to group the features.
2061 default tab to be used when opening the query window. It can be set to
2062 either 'sql', 'files', 'history' or 'full'.</dd>
2068 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2070 If the approximate row count as returned by
2073 count will be used.
2074 </dd>
2076 <dd>For VIEWs, since obtaining the exact count could have an
2077 impact on performance, this value is the maximum to be displayed, using
2079 any row counting.
2080 </dd>
2084 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2086 page. By clicking on the button 'toggle scratchboard' on the page
2087 where you edit x/y coordinates of those elements you can activate a
2088 scratchboard where all your elements are placed. By clicking on an
2089 element, you can move them around in the pre-defined area and the x/y
2090 coordinates will get updated dynamically. Likewise, when entering a
2091 new position directly into the input field, the new position in the
2092 scratchboard changes after your cursor leaves the input field.<br />
2093 You have to click on the 'OK'-button below the tables to save the new
2094 positions. If you want to place a new element, first add it to the
2095 table of elements and then you can drag the new element around.<br />
2096 By changing the paper size and the orientation you can change the size
2097 of the scratchboard as well. You can do so by just changing the
2098 dropdown field below, and the scratchboard will resize automatically,
2099 without interfering with the current placement of the elements.<br />
2100 If ever an element gets out of range you can either enlarge the paper
2101 size or click on the 'reset' button to place all elements below each
2102 other.<br />
2104 get this control to work. The basic Drag&Drop script functionality
2105 was kindly borrowed from www.youngpup.net and is underlying so
2106 specific license.</dd>
2109 <dd>Sorts database and table names according to natural order (for example,
2110 t1, t2, t10). Currently implemented in the left panel (Light mode)
2111 and in Database view, for the table list.</dd>
2122 <dd>Allows you to specify window's title bar. Following magic string can
2123 be used to get special values:
2124 <dl>
2130 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2139 </dl>
2140 </dd>
2150 </dd>
2153 <dd>If theme manager is active, use this as the path of the subdirectory
2154 containing all the themes.</dd>
2168 </dt>
2169 <dd>Default queries that will be displayed in query boxes when user didn't
2170 specify any. Use %d for database name, %t for table name and %f for a
2171 comma separated list of field names. Note that %t and %f are only
2175 <dd>
2176 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
2177 default we use HTML to format the query, but you can disable this by
2179 </dd>
2182 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2183 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2184 query inside a bracket is indented. By changing
2187 specifies the units of the indent amount that you specified. This is
2188 used via stylesheets.</dd>
2191 <dd>This array is used to define the colours for each type of element of
2192 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2194 If you specify an empty string for the color of a class, it is ignored
2195 in creating the stylesheet.
2196 You should not alter the class names, only the colour strings.<br />
2217 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2221 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2222 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2223 </ul>
2224 </dd>
2228 <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,
2229 as originally published on
2231 <br />
2232 For help in setting up your system to use the service, see the
2234 </dd>
2238 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2239 and any password, so we use those by default. Instead, if
2240 you have an account with them, you can put your login details
2241 here, and it will be used in place of the anonymous login.</dd>
2242 </dl>
2243 </dd>
2246 <dd><b>DEVELOPERS ONLY!</b></dd>
2249 <dd><b>DEVELOPERS ONLY!</b><br />
2250 Enable logging queries and execution times to be displayed in the bottom
2251 of main page (right frame).</dd>
2254 <dd><b>DEVELOPERS ONLY!</b><br />
2255 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2256 the code.<br />
2257 For help in setting up your system to this, see the
2261 <dd><b>DEVELOPERS ONLY!</b><br />
2262 Enable profiling support for phpMyAdmin. This will append a chunk of data
2263 to the end of every page displayed in the main window with profiling
2264 statistics for that page.<br />
2265 You may need to increase the maximum execution time for this to
2266 complete successfully.<i>Profiling was removed from the code for
2267 version 2.9.0 due to licensing issues.</i></dd>
2269 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2270 <dd><b>DEVELOPERS ONLY!</b><br />
2271 When profiling data is displayed, this variable controls the threshold of
2272 display for any profiling data, based on the average time each time has
2273 taken. If it is over the threshold it is displayed, otherwise it is not
2274 displayed. This takes a value in milliseconds. In most cases you don't need
2275 to edit this.</dd>
2278 <dd>All possible types of a MySQL column. In most cases you don't need to
2279 edit this.</dd>
2282 <dd>Possible attributes for fields. In most cases you don't need to edit
2283 this.</dd>
2286 <dd>A list of functions MySQL supports. In most cases you don't need to
2287 edit this.</dd>
2290 <dd>Mapping of column types to meta types used for preferring displayed
2291 functions. In most cases you don't need to edit this.</dd>
2294 <dd>Functions preferred for column meta types as defined in
2295 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2296 to edit this.</dd>
2299 <dd>Functions selected by default when inserting/changing row, Functions
2300 are defined for meta types from
2302 <code>first_timestamp</code>, which is used for first timestamp column
2303 in table.</dd>
2306 <dd>Operators available for search operations on numeric and date fields.
2307 </dd>
2310 <dd>Operators available for search operations on character fields.
2311 Note that we put <code>LIKE</code> by default instead of
2312 <code>LIKE %...%</code>, to avoid unintended performance problems
2313 in case of huge tables.</dd>
2316 <dd>Operators available for search operations on enum fields.</dd>
2319 <dd>Additional operators available for search operations when the
2320 field can be null.</dd>
2322 </dl>
2324 <!-- TRANSFORMATIONS -->
2330 </ol>
2334 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2336 section</a> on how to do so.</p>
2338 <p> You can apply different transformations to the contents of each field. The
2339 transformation will take the content of each field and transform it with
2340 certain rules defined in the selected transformation.</p>
2342 <p> Say you have a field 'filename' which contains a filename. Normally you would
2343 see in phpMyAdmin only this filename. Using transformations you can transform
2344 that filename into a HTML link, so you can click inside of the phpMyAdmin
2345 structure on the field's link and will see the file displayed in a new browser
2346 window. Using transformation options you can also specify strings to
2347 append/prepend to a string or the format you want the output stored in.</p>
2349 <p> For a general overview of all available transformations and their options,
2350 you can consult your
2351 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2352 installation.</p>
2354 <p> For a tutorial on how to effectively use transformations, see our
2356 the official phpMyAdmin homepage.</p>
2360 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2361 clicking on the 'Structure' link for a table). There click on
2362 "Change" (or change icon) and there you will see three new fields at
2363 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2364 'Transformation options'.</p>
2366 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2367 that corresponds to the column's contents. Please note that
2368 transformations are inactive as long as no MIME-type is selected.</li>
2370 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2371 hopefully growing amount of pre-defined transformations. See below for information on
2372 how to build your own transformation.<br />
2374 There are global transformations and mimetype-bound transformations. Global transformations
2375 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2376 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2377 transformations which operate on the main mimetype (like 'image'), which will most likely
2378 take the subtype into regard, and those who only operate on a
2379 specific subtype (like 'image/jpeg').<br />
2381 You can use transformations on mimetypes for which the function was not defined for. There
2382 is no security check for you selected the right transformation, so take care of what the
2383 output will be like.</li>
2385 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2386 transform-function specific options here. Usually the transforms can operate with default
2387 options, but it is generally a good idea to look up the overview to see which options are
2388 necessary.<br />
2390 Much like the ENUM/SET-Fields, you have to split up several options using the format
2391 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2392 parsed as an array, leaving the first value the first element in the array, and so
2393 forth.<br />
2395 If you want to specify a MIME character set you can define it in the transformation_options.
2396 You have to put that outside of the pre-defined options of the specific mime-transform,
2398 for which you can specify 2 options and you want to append a character set, enter "'first
2399 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2401 </ul>
2405 <p> All mimetypes and their transformations are defined through single files in
2406 the directory 'libraries/transformations/'.</p>
2408 <p> They are stored in files to ease up customization and easy adding of new
2409 transformations.</p>
2411 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2412 always work. It makes no sense to apply a transformation to a mimetype, the
2413 transform-function doesn't know to handle.</p>
2415 <p> One can, however, use empty mime-types and global transformations which should work
2416 for many mimetypes. You can also use transforms on a different mimetype they where built
2417 for, but pay attention to option usage as well as what the transformation does to your
2418 field.</p>
2420 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2421 any other transform function and provides some basic functions.</p>
2423 <p> There are 5 possible file names:</p>
2425 <ol><li>A mimetype+subtype transform:<br /><br />
2427 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2429 Please not that mimetype and subtype are separated via '_', which shall
2430 not be contained in their names. The transform function/filename may
2431 contain only characters which cause no problems in the file system as
2432 well as the PHP function naming convention.<br /><br />
2434 The transform function will the be called
2435 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2437 <b>Example:</b><br /><br />
2439 <tt>text_html__formatted.inc.php</tt><br />
2440 <tt>PMA_transform_text_html__formatted()</tt></li>
2442 <li>A mimetype (w/o subtype) transform:<br /><br />
2444 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2446 Please note that there are no single '_' characters.
2447 The transform function/filename may contain only characters which cause
2448 no problems in the file system as well as the PHP function naming
2449 convention.<br /><br />
2451 The transform function will the be called
2452 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2454 <b>Example:</b><br /><br />
2456 <tt>text__formatted.inc.php</tt><br />
2457 <tt>PMA_transform_text__formatted()</tt></li>
2459 <li>A mimetype+subtype without specific transform function<br /><br />
2461 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2463 Please note that there are no '__' characters in the filename. Do not
2464 use special characters in the filename causing problems with the file
2465 system.<br /><br />
2467 No transformation function is defined in the file itself.<br /><br />
2469 <b>Example:</b><br /><br />
2471 <tt>text_plain.inc.php</tt><br />
2472 (No function)</li>
2474 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2476 <tt>[mimetype].inc.php</tt><br /><br />
2478 Please note that there are no '_' characters in the filename. Do not use
2479 special characters in the filename causing problems with the file system.
2480 <br /><br />
2482 No transformation function is defined in the file itself.<br /><br />
2484 <b>Example:</b><br /><br />
2486 <tt>text.inc.php</tt><br />
2487 (No function)</li>
2489 <li>A global transform function with no specific mimetype<br /><br />
2491 <tt>global__[transform].inc.php</tt><br /><br />
2493 The transform function will the be called
2494 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2496 <b>Example:</b><br /><br />
2498 <tt>global__formatted</tt><br />
2499 <tt>PMA_transform_global__formatted()</tt></li>
2500 </ol>
2502 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2503 transform function.</p>
2505 <p> All filenames containing no '__' in themselves are not shown as valid transform
2506 functions in the dropdown.</p>
2508 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2509 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2510 without a transform function. Also note the introduction of a function description in
2511 the language files. For each function a $strTransformation_[filename without .inc.php]
2512 has to exist.</p>
2514 <p> You can use the template generator to generate new functions and entries in the
2515 language file.</p>
2517 <p> To create a new transform function please see
2518 <tt>libraries/transformations/template_generator.sh</tt>.
2519 To create a new, empty mimetype please see
2520 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2522 <p> A transform function always gets passed three variables:</p>
2524 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2525 you want to transform.</li>
2526 <li><b>$options</b> - Contains any user-passed options to a transform function
2527 as an array.</li>
2528 <li><b>$meta</b> - Contains an object with field information to your column.
2529 The data is drawn from the output of the
2531 function. This means, all object properties described on the
2533 available in this variable and can be used to transform a field accordingly
2534 to unsigned/zerofill/not_null/... properties.<br />
2535 The $meta->mimetype variable contains the original MIME-type of the
2536 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2537 </ol>
2539 <!-- FAQ -->
2546 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2551 </ol>
2553 <p> Please have a look at our
2555 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2556 features and or interface.</p>
2562 action is required or phpMyAdmin sends a blank page or a page full of
2563 cryptic characters to my browser, what can I do?</a></h4>
2565 <p> There are some known PHP bugs with output buffering and compression.<br />
2567 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2568 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2569 configuration file.<br />
2570 Furthermore, we know about such problems connected to the release
2571 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2572 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2577 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2578 See also the
2580 entry about PHP bugs with output buffering.<br />
2581 If your server keeps crashing, please ask for help in the various Apache
2582 support groups.</p>
2586 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2587 script: I'm always displayed the login screen.</a></h4>
2589 <p> This is a known PHP bug (see this
2591 official PHP bug database. It means there is and won't be any phpMyAdmin
2592 fix against it because there is no way to code a fix.</p>
2598 application misbehaved by not returning a complete set of
2600 </h4>
2602 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2603 Have a look at the last message in this
2605 official PHP bug database.</p>
2610 and/or many error messages with the
2612 mode.</a></h4>
2614 <p> This is a known problem with the PHP
2616 filter: it's not so stable. Please use instead the cookie authentication mode.
2617 </p>
2622 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2623 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2624 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2625 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2626 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2631 work.</a></h4>
2633 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2634 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2635 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2636 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2637 We faced PHP crashes when trying to download a dump with MS Internet
2638 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2639 this case you should switch to the release version of PHP 4.2.0.</p>
2643 an error about safe mode being in effect.</a></h4>
2645 <p> Your uploaded file is saved by PHP in the "upload dir", as
2646 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2647 the system default is <i>/tmp</i>).<br />
2648 We recommend the following setup for Apache servers running in safe mode,
2649 to enable uploads of files while being reasonably secure:</p>
2651 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2652 <li>give ownership to the Apache server's user.group:
2653 <tt>chown apache.apache /tmp/php</tt></li>
2654 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2655 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2656 <li>restart Apache</li>
2657 </ul>
2661 general file uploads don't work on my system and uploaded files have a
2662 <tt>Content-Type:</tt> header in the first line.</a></h4>
2664 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2665 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2666 So the problem is that this package has a serious bug that was corrected
2667 ages ago in PHP (2001-01-28: see
2669 for more details). The problem is that the bugged package is still
2670 available though it was corrected (see
2672 for more details).<br />
2673 So please download
2674 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2675 and the problem should go away.<br />
2676 And that fixes the \r\n problem with file uploads!</p>
2680 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2681 I'm using the Apache server.</a></h4>
2683 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2684 your <i>httpd.conf</i>:</p>
2688 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2692 uploading a file from the query box.</a></h4>
2694 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2695 restrictions. However you need to create temporary directory and
2697 The uploaded files will be moved there, and after execution of your
2703 <p> The MySQL manual explains how to
2705 reset the permissions</a>.</p>
2710 execute a bookmark.</a></h4>
2712 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2713 cannot access the uploaded query.</p>
2718 submit a query from the convenient text area.</a></h4>
2720 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2721 and try to increase it.</p>
2725 </h4>
2727 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2728 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2729 names to align with current standards.</p>
2734 </h4>
2736 <p> Starting with version 2.7.0, the import engine has been re–written and these
2737 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2738 to take advantage of the new import features.</p>
2740 <p> The first things to check (or ask your host provider to check) are the
2741 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2742 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2743 All of these three settings limit the maximum size of data that can be
2744 submitted and handled by PHP. One user also said that post_max_size
2745 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2747 There exist several workarounds if your upload is too big or your
2748 hosting provider is unwilling to change the settings:</p>
2751 feature. This allows one to
2752 upload a file to the server via scp, ftp, or your favorite file transfer
2753 method. PhpMyAdmin is then able to import the files from the temporary
2755 section</a> of this document.</li>
2757 BigDump</a>) to split the files before uploading. We cannot support this
2758 or any third party applications, but are aware of users having success
2759 with it.</li>
2760 <li>If you have shell (command line) access, use MySQL to import the files
2761 directly. You can do this by issuing the "source" command from
2762 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2763 </ul>
2767 support?</a></h4>
2769 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2770 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2771 connect to your MySQL server using PHP's classic
2774 is available in php 5.0. The latter one should be used unless you have
2775 good reason not to do so.<br />
2776 When compiling php, we strongly recommend that you manually link the MySQL
2777 extension of your choice to a MySQL client library of at least the same
2778 minor version since the one that is bundled with some PHP distributions is
2781 If your webserver is running on a windows system, you might want to try
2782 MySQL's
2784 instead of the MySQL / MySQLi extensions that are bundled with the official
2785 php Win32 builds.</p>
2789 message, "Client does not support authentication protocol requested
2790 by server; consider upgrading MySQL client"</a></h5>
2792 <p> You tried to access MySQL with an old MySQL client library. The version of
2793 your MySQL client library can be checked in your phpinfo() output.
2794 In general, it should have at least the same minor version as your server
2798 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2799 changed the authentication hash and your PHP is trying to use the old method.
2801 with the proper client library to match your MySQL installation. Your
2802 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2803 More information (and several workarounds) are located in the
2805 </p>
2809 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2810 capital letter in its name it is changed to lowercase as it should. But
2811 if I try to DROP this table MySQL is unable to find the corresponding
2812 file.</a></h4>
2814 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2815 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2816 directive.</p>
2820 script seems not to know the font face I'm using!</a></h4>
2822 <p> The "FPDF" library we're using for this feature requires some
2823 special files to use font faces.<br />
2825 these files.</p>
2829 check PHP Configuration".</a></h4>
2831 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2832 "MySQL extension". This extension may be part of the PHP
2833 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2834 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2835 to load the extension but failed.<br /><br />
2837 Usually, the problem is solved by installing a software package called
2838 "PHP-MySQL" or something similar.</p>
2843 and I cannot log in using cookie auth.</a></h4>
2845 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2849 so I cannot upload.</a></h4>
2851 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2852 parameter is not set to "on".</p>
2856 a new table the table and field names are changed to lowercase!</a></h4>
2858 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2859 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2860 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2861 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2862 directory and add the following line to the group [mysqld]:</p>
2864 <pre>set-variable = lower_case_table_names=0</pre>
2866 <p> Next, save the file and restart the MySQL service. You can always check the
2867 value of this directive using the query</p>
2869 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2873 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2876 </p>
2880 and I get problems, such as undefined variables when I run a
2883 <p> A tip from Jose Fandos: put a comment on the following two lines
2884 in httpd.conf, like this:</p>
2886 <pre>
2887 # mod_gzip_item_include file \.php$
2889 </pre>
2891 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2892 PHP scripts. Of course you have to restart Apache.</p>
2897 I get the error "No input file specified" when trying to
2898 run phpMyAdmin.</a></h4>
2900 <p> This is a permission problem. Right-click on the phpmyadmin folder
2901 and choose properties. Under the tab Security, click on "Add"
2902 and select the user "IUSR_machine" from the list. Now set his
2903 permissions and it should work.</p>
2907 db_structure.php with plenty of tables).</a></h4>
2910 GZIP output buffering is enabled. If you turn off it (by
2912 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2913 PHP 5.0.0.</p>
2917 message 'Errorcode: 13'. What does this mean?</a></h4>
2919 <p> This can happen due to a MySQL bug when having database / table names with
2920 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2921 To fix this, turn off this directive, convert all database and table names
2922 to lower case and turn it on again. Alternatively, there's a bug-fix
2923 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2927 and the fields are duplicated.</a></h4>
2929 <p> It is possible to configure Apache in such a way that PHP has problems
2930 interpreting .php files.</p>
2932 <p> The problems occur when two different (and conflicting) set of directives
2933 are used:</p>
2935 <pre>
2936 SetOutputFilter PHP
2937 SetInputFilter PHP
2938 </pre>
2940 <p> and</p>
2942 <pre>AddType application/x-httpd-php .php</pre>
2944 <p> In the case we saw, one set of directives was in
2945 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2946 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2947 The recommended way is with <tt>AddType</tt>, so just comment out
2948 the first set of lines and restart Apache:</p>
2950 <pre>
2951 #SetOutputFilter PHP
2952 #SetInputFilter PHP
2953 </pre>
2958 <p> This problem is known to happen when the server is running Turck MMCache
2959 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2964 <p> Yes.<br />
2965 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2966 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2967 <tt>error_reporting</tt> settings.
2968 </p>
2971 <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>
2973 <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>
2976 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2977 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2978 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2979 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2980 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2981 enabled.) Click <tt>OK</tt>.</li>
2982 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2983 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2984 </ol>
2988 PHP 5.0.4 on 64-bit systems?</a></h4>
2990 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2991 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2997 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
2998 the order of the server paragraph in <tt>config.inc.php</tt>.
2999 Table and script parts are optional. If you want
3000 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3001 some configuration. Following lines apply only for <a
3003 that you have enabled some features within global configuration. You need
3004 <code>Options FollowSymLinks</code> and <code>AllowOverride
3005 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3006 you need mod_rewrite to be enabled. Then you just need to create following
3007 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3008 (don't forget to change directory name inside of it):</p>
3010 <pre>
3011 RewriteEngine On
3012 RewriteBase /path_to_phpMyAdmin
3013 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3014 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3015 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3016 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3017 </pre>
3020 <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>
3022 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3023 following rewrite rule:</p>
3025 <pre>
3026 RewriteEngine On
3027 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3028 </pre>
3032 </h4>
3033 <p>
3034 There can be many explanations to this and a look at your server's
3035 error log file might give a clue.
3036 </p>
3040 password encryption in cookie auth doesn't work.</a></h4>
3042 <p> If your cluster consist of different architectures, PHP code used for
3043 encryption/decryption won't work correct. This is caused by use of
3044 pack/unpack functions in code. Only solution is to use mcrypt extension
3045 which works fine in this case.</p>
3050 <p> Yes but the default configuration values of Suhosin are known to cause
3051 problems with some operations, for example editing a table with many
3052 columns and no primary key. Tuning information is available at
3054 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
3055 although the parameter names have changed (<tt>suhosin</tt> instead
3057 <tt>SuhosinDisableWarning</tt> directive</a>.
3058 </p>
3062 but then my connection is redirected back to http. What can cause this
3063 behavior?</a></h4>
3065 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3066 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>
3069 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
3071 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3072 Example from the Apache 2.2 documentation:</p>
3073 <pre>
3074 ProxyPass /mirror/foo/ http://backend.example.com/
3075 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3076 ProxyPassReverseCookieDomain backend.example.com public.example.com
3077 ProxyPassReverseCookiePath / /mirror/foo/
3078 </pre>
3080 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3081 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3082 This is not specific to phpmyadmin, it's just the behavior of Apache.
3083 </p>
3085 <pre>
3086 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3087 ProxyPassReverse /mirror/foo/
3088 http://backend.example.com/%7Euser/phpmyadmin
3089 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3090 </pre>
3092 <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>
3093 for more details.</p>
3097 privileges, I get an error about an unknown column.</a></h4>
3099 <p> The MySQL server's privilege tables are not up to date, you need to run
3100 the <tt>mysql_upgrade</tt> command on the server.</p>
3107 headers already sent by ..." is displayed, what's the problem?</a></h4>
3109 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3110 (I.E. no blank lines, no spaces, no characters...) neither before the
3111 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3112 tag at the end. We also got a report from a user under IIS, that used
3113 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3114 contained an end-of-line character (hex 0A) at the end; removing this character
3115 cleared his errors.</p>
3120 <p> Either there is an error with your PHP setup or your username/password is
3121 wrong. Try to make a small script which uses mysql_connect and see if it
3122 works. If it doesn't, it may be you haven't even compiled MySQL support
3123 into PHP.</p>
3127 connect to local MySQL server through socket '/tmp/mysql.sock'
3128 (111) ..." is displayed. What can I do?</a></h4>
3130 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3132 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3133 In your <i>php.ini</i> you will find a line</p>
3135 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3137 <p> change it to</p>
3139 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3141 <p> Then restart apache and it will work.</p>
3143 <p> Here is a fix suggested by Brad Ummer:</p>
3145 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3146 To do this, telnet to your server and go to the MySQL bin directory. In
3147 this directory there should be a file named <i>mysqladmin</i>. Type
3148 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3149 info about your MySQL server, including the socket
3150 (<i>/tmp/mysql.sock</i>, for example).</li>
3151 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3152 phpMyAdmin, you need to complete the socket information in the
3153 <i>config.inc.php</i>.<br />
3154 For example:
3156 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3157 <br /><br />
3159 Please also make sure that the permissions of this file allow to be readable
3160 by your webserver (i.e. '0755').</li>
3161 </ul>
3163 <p> Have also a look at the
3165 corresponding section of the MySQL documentation</a>.</p>
3169 what can I do?</a></h4>
3172 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3173 sometime.<br />
3174 Also have a look at your PHP version number: if it contains "4.0b..."
3175 it means you're running a beta version of PHP. That's not a so good idea,
3176 please upgrade to a plain revision.</p>
3180 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3181 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3183 <p> Check the value you set for the
3185 directive in the phpMyAdmin configuration file.</p>
3189 password: YES)"-error when trying to access a MySQL-Server on a
3190 host which is port-forwarded for my localhost.</a></h4>
3192 <p> When you are using a port on your localhost, which you redirect via
3193 port-forwarding to another host, MySQL is not resolving the localhost
3194 as expected.<br />
3195 Erik Wasser explains: The solution is: if your host is "localhost"
3196 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3197 connection for speeding up things. And that doesn't work in this configuration
3198 with port forwarding.<br />
3204 <p> Themes are configured with
3208 <br />
3210 should not delete the directory "original" or its underlying
3211 structure, because this is the system theme used by phpMyAdmin.
3212 "original" contains all images and styles, for backwards
3213 compatibility and for all themes that would not include images or css-files.
3214 <br /><br />
3217 is enabled, you can select your favorite theme on the main page. Your
3218 selected theme will be stored in a cookie.<br /><br /></p>
3220 <p> To create a theme:</p>
3222 <ul><li>make a new subdirectory (for example "your_theme_name") under
3224 (by default <tt>themes</tt>)</li>
3225 <li>copy the files and directories from "original" to
3226 "your_theme_name"</li>
3227 <li>edit the css-files in "your_theme_name/css"</li>
3228 <li>put your new images in "your_theme_name/img"</li>
3229 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3230 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3231 contain your chosen theme name, that will be visible in user interface</li>
3232 <li>make a new screenshot of your theme and save it under
3233 "your_theme_name/screen.png"</li>
3234 </ul>
3236 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3237 theme verbose name, theme generation and theme version. These versions and
3238 generations are enumerated from 1 and do not have any direct dependence on
3239 phpMyAdmin version. Themes within same generation should be backwards
3240 compatible - theme with version 2 should work in phpMyAdmin requiring
3241 version 1. Themes with different generation are incompatible.</p>
3243 <p> If you do not want to use your own symbols and buttons, remove the
3244 directory "img" in "your_theme_name". phpMyAdmin will
3245 use the default icons and buttons (from the system-theme "original").
3246 </p>
3250 what can I do?</a></h4>
3252 <p> Here are a few points to check:</p>
3254 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3256 directive empty. See also
3258 </li>
3259 <li>Maybe you have a broken PHP installation or you need to upgrade
3260 your Zend Optimizer. See
3262 http://bugs.php.net/bug.php?id=31134</a>.
3263 </li>
3264 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3265 set to the default (200) or another low value, you could get this
3266 error if your table has a high number of columns. Adjust this setting
3267 accordingly. (Thanks to Klaus Dorninger for the hint).
3268 </li>
3269 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3270 of ";" will cause this error. Replace it with "&;".
3271 </li>
3273 you might want to increase
3275 </li>
3276 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3277 </li>
3278 </ul>
3285 who logged out can not log in again in with the same nick.</a></h4>
3287 <p> This is related to the authentication mechanism (protocol) used by
3288 phpMyAdmin. To bypass this problem: just close all the opened
3289 browser windows and then go back to phpMyAdmin. You should be able to
3290 log in again.</p>
3294 limit error or a time limit error.</a></h4>
3296 <p> Compressed dumps are built in memory and because of this are limited to
3297 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3298 using
3300 (enabled by default). Zip exports can not be handled this way, so if you need
3301 Zip files for larger dump, you have to use another way.</p>
3305 when I rename a table or a column.</a></h4>
3307 <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>
3311 bundled with the MySQL server distribution.</a></h4>
3313 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3315 <pre>
3316 -- MySQL dump 8.22
3317 --
3318 -- Host: localhost Database: database
3319 ---------------------------------------------------------
3320 -- Server version 3.23.54
3321 </pre>
3323 <p> The invalid part of the code is the horizontal line made of dashes that
3324 appears once in every dump created with mysqldump. If you want to run your
3325 dump you have to turn it into valid MySQL. This means, you have to add a
3326 whitespace after the first two dashes of the line or add a # before it:
3327 <br />
3328 <code>
3329 -- -------------------------------------------------------<br />
3330 </code>
3331 or<br />
3332 <code>
3333 #---------------------------------------------------------
3334 </code>
3335 </p>
3342 <p> Please note that you should not use the separating string multiple times
3343 without any characters between them, or at the beginning/end of your table
3344 name. If you have to, think about using another TableSeparator or disabling
3345 that feature</p>
3350 <p> In Relation view, being able to choose a table in another database,
3351 or having more than one index field in the foreign key.<br /><br/>
3352 In Query-by-example (Query), automatic generation of the query
3353 LEFT JOIN from the foreign table.<br /><br/>
3354 </p>
3358 I get series of errors like "Warning: unable to parse url". How
3359 can this be fixed?</a></h4>
3360 <p>
3361 Your table neither have a primary key nor an unique one, so we must use a
3362 long expression to identify this row. This causes problems to parse_url
3363 function. The workaround is to create a primary or unique key.
3364 <br />
3365 </p>
3369 a MIME-Transformation onto!</a></h4>
3371 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3372 nested forms can be put inside the table where phpMyAdmin displays the results.
3373 You can, however, use any form inside of a table if keep the parent
3374 form-container with the target to tbl_row_delete.php and just put your own
3375 input-elements inside. If you use a custom submit input field, the form will
3376 submit itself to the displaying page again, where you can validate the
3377 $HTTP_POST_VARS in a transformation.
3379 For a tutorial on how to effectively use transformations, see our
3381 on the official phpMyAdmin-homepage.</p>
3385 MySQL server</a></h4>
3387 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3390 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3391 the quote-character (") is interpreted as an identifier quote character and
3392 not as a string quote character, which makes many internal phpMyAdmin
3394 statements. There is no workaround to this behaviour. News to this item will
3395 be posted in Bug report
3396 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3397 </p>
3401 more that one column with the same value
3402 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3403 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3405 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3406 can use it for the Edit and Delete links.</p>
3411 <p> phpMyAdmin uses a quick method to get the row count, and this method
3412 only returns an approximate count in the case of InnoDB tables. See
3414 a way to modify those results, but
3415 this could have a serious impact on performance.</p>
3420 <p> The number of records in queries containing COUNT and GROUP BY is
3421 not correctly calculated. Also, sorting results of a query like
3426 containing an hyphen.
3427 </a></h4>
3428 <p>
3429 The tests I have made with current MySQL 4.1.11 API shows that the
3430 API does not accept this syntax for the USE command. Enclosing the
3431 db name with backquotes works. For further confusion, no backquotes
3432 are needed with command-line mysql.
3433 </p>
3436 <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>
3437 <p>
3438 This has been a known limitation of phpMyAdmin since the beginning and
3439 it's not likely to be solved in the future.
3440 </p>
3442 <!-- Begin: Excel import limitations -->
3445 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3446 <p>
3447 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target=_blank>PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3448 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3449 <br /><br />
3450 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3451 </p>
3454 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3455 <p>
3456 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3457 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3458 </p>
3461 <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>
3462 <p>
3463 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3464 consider using a built-in type. These are almost always guarenteed to import correctly.
3465 </p>
3467 <!-- End: Excel import limitations -->
3468 <!-- Begin: CSV import limitations -->
3471 <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>
3472 <p>
3473 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.
3474 </p>
3476 <!-- End: CSV import limitations -->
3477 <!-- Begin: Import type-detection limitations -->
3480 <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>
3481 <p>
3482 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
3483 you will have to edit the structure to your liking post-import.
3484 <br /><br />
3485 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
3486 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.
3487 </p>
3489 <!-- End: Import type-detection limitations -->
3491 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3494 <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
3495 need to install it for each customer.
3496 </a></h4>
3497 <p>
3498 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3499 your users. The development of this feature was kindly sponsored by
3500 NetCologne GmbH.
3501 This requires a properly setup MySQL user management and phpMyAdmin
3502 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3504 </p>
3508 access.
3509 </a></h4>
3510 <p>
3511 This depends on your system.<br />
3512 If you're running a server which cannot be accessed by other people, it's
3513 sufficient to use the directory protection bundled with your webserver
3515 If other people have telnet access to your server, you should use
3516 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3517 <br /><br />
3518 Suggestions:
3519 </p>
3520 <ul>
3521 <li>
3523 </li>
3524 <li>
3525 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3526 is a user whose password is only known to you, and apache is the
3527 group under which Apache runs.
3528 </li>
3529 <li>
3530 You should use PHP safe mode, to protect from other users that try
3532 </li>
3533 </ul>
3538 </a></h4>
3539 <p>
3544 </p>
3547 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3548 authentication.
3549 </a></h4>
3553 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3554 and/or
3556 are wrong.</li>
3558 <li>You have already setup a security mechanism for the
3559 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3560 phpMyAdmin's authentication, so remove it.</li>
3561 </ul>
3568 and put the privileges you want. For example,
3570 would let a user create/manage his/her database(s).</p>
3575 <p> If you have existing rules from an old .htaccess file, you can take them
3578 be a major benefit here if your installation is suited to using it. Then
3579 you can just add those updated lines into the
3583 <p> If you want a pre-made sample, you can try this fragment. It stops the
3584 'root' user from logging in from any networks other than the private
3587 <pre>
3588 //block root from logging in except from the private networks
3589 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3590 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3591 'deny root from all',
3592 'allow root from localhost',
3596 );
3597 </pre>
3602 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3603 different than the one set in your
3605 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3606 while a domain name is defined in the config file.</p>
3611 <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>
3617 when trying to create a table with more than 14 fields.
3618 </a></h4>
3619 <p>
3620 We could reproduce this problem only under Win98/98SE. Testing under
3621 WinNT4 or Win2K, we could easily create more than 60 fields.
3622 <br />
3623 A workaround is to create a smaller number of fields, then come back to
3624 your table properties and add the other fields.
3625 </p>
3629 <p>
3630 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3631 with each script/website that use forms.<br />
3632 Upgrade or downgrade your Xitami server.
3633 </p>
3636 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3637 <p>
3638 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3639 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3640 don't seem to work.<br />
3642 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3643 the user's temporary directory, so they must be moved before closing
3644 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3647 </p>
3651 Explorer never stores the cookies.
3652 </a></h4>
3653 <p>
3654 MS Internet Explorer seems to be really buggy about cookies, at least till
3656 in this area!
3657 <br />
3658 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3659 work!
3660 </p>
3664 rows.
3665 </a></h4>
3666 <p>
3668 </p>
3671 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3672 when trying to modify a row in a table with many fields, or with a text field
3673 </a></h4>
3674 <p>
3675 Your table neither have a primary key nor an unique one, so we must use a
3676 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
3677 those browsers, and this not happen in Netscape, for example. The
3678 workaround is to create a primary or unique key, or use another browser.
3679 <br />
3680 </p>
3684 page.
3685 </a></h4>
3686 <p>
3687 Some browsers support right-clicking into the frame you want to refresh,
3688 just do this in the right frame.<br />
3689 </p>
3693 query box.
3694 </a></h4>
3695 <p>
3696 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3697 Mozilla versions.<br />
3698 </p>
3702 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3703 </a></h4>
3704 <p>
3705 This is a Mozilla bug (see bug #26882 at
3707 </p>
3712 </a></h4>
3713 <p>
3714 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3715 data in octet-stream mode. Since we can't detect the specific Netscape
3716 version, we cannot workaround this bug.
3717 </p>
3721 wrong.</a></h4>
3723 <p> Please ensure that you have set your browser's character set to the one of the
3724 language file you have selected on phpMyAdmin's start page.
3725 Alternatively, you can try the auto detection mode that is supported by the
3726 recent versions of the most browsers.</p>
3729 <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
3732 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3733 Netscape and Mozilla do not have this problem.</p>
3736 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3737 I cannot manage two servers: I log in to the first one, then the other one,
3738 but if I switch back to the first, I have to log in on each operation.</a></h4>
3744 but nothing happens after that, only a blank screen.</a></h4>
3755 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3760 address and you are starting
3762 containing a domain name, or the reverse situation.</li>
3763 <li>Security settings in IE and/or Microsoft Security Center are
3764 too high, thus blocking scripts execution.</li>
3765 <li>The Windows Firewall is blocking Apache and MySQL. You must
3769 </ul>
3772 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3773 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3774 installed in their Firefox is causing the problem.</p>
3778 clause is generated when I browse a table.</a></h4>
3779 <p> This happens only when both of these conditions are met: using the
3789 </a></h4>
3790 <p>
3791 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3792 specifying a wrong field-type.<br />
3793 Common errors include:
3794 </p>
3795 <ul>
3798 </ul>
3799 <p>
3800 Also, look at the syntax chapter in the MySQL manual to confirm that your
3801 syntax is correct.
3802 </p>
3806 phpMyAdmin generates only one index with those two fields.
3807 </a></h4>
3808 <p>
3809 This is the way to create a multi-fields
3810 index. If you want two indexes, create the first one when creating the
3811 table, save, then display the table properties and click the Index link to
3812 create the other index.
3813 </p>
3817 <p>
3818 Since version 2.2.3, you have a checkbox for each field that can be null.
3820 field's value. Since version 2.5.5, you have to use the checkbox to get
3822 a literal NULL in the field, and not a NULL value (this works in PHP4).
3823 </p>
3828 <p> Click on a database or table name in the left frame, the properties will be
3830 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3831 statements that can be used to recreate your database/table.
3832 <br /><br />
3834 transmit the resulting dump to your station. Depending on your PHP
3835 configuration, you will see options to compress the dump. See also the
3837 configuration variable.<br /><br />
3840 this document.</p>
3845 </a></h4>
3847 <p> Click on a database name in the left frame, the properties will be
3849 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3851 the path to your dump filename, or use the Browse button. Then click Go.
3852 <br /><br />
3854 that you upgrade to take advantage of the new features.
3855 <br /><br />
3857 in this document.
3858 </p>
3863 <p> Here is an example with the tables persons, towns and countries, all
3865 table, create it as explained in the configuration section. Then create the
3866 example tables:</p>
3868 <pre>
3869 CREATE TABLE REL_countries (
3870 country_code char(1) NOT NULL default '',
3871 description varchar(10) NOT NULL default '',
3872 PRIMARY KEY (country_code)
3873 ) TYPE=MyISAM;
3875 INSERT INTO REL_countries VALUES ('C', 'Canada');
3877 CREATE TABLE REL_persons (
3878 id tinyint(4) NOT NULL auto_increment,
3879 person_name varchar(32) NOT NULL default '',
3881 country_code char(1) NOT NULL default '',
3882 PRIMARY KEY (id)
3883 ) TYPE=MyISAM;
3885 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3886 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3888 CREATE TABLE REL_towns (
3890 description varchar(30) NOT NULL default '',
3891 PRIMARY KEY (town_code)
3892 ) TYPE=MyISAM;
3894 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3895 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3896 </pre>
3902 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3906 </ul>
3914 <li>In the fields row, choose persons.person_name and click the
3916 <li>Do the same for towns.description and countries.descriptions in the
3919 the correct joins have been generated</li>
3921 </ul>
3925 <p>
3926 Starting from the previous example, create the pma_table_info as explained
3927 in the configuration section, then browse your persons table,
3928 and move the mouse over a town code or country code.
3929 <br /><br />
3930 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3931 enables: drop-down list of possible values.
3932 </p>
3935 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3936 <p>
3939 <br /><br />
3940 Then you need to think about your schema layout. Which tables will go on
3941 which pages?
3942 </p>
3943 <ul>
3949 page and click Go. If you like, you
3951 linked tables onto the new page.</li>
3952 <li>Select the name of the new page (making sure the Edit radio button
3953 is selected) and click Go.</li>
3955 Coordinates are relative; your diagram will
3956 be automatically scaled to fit the page. When initially placing tables
3957 on the page, just pick any coordinates -- say, 50x50. After clicking
3959 position the element correctly.</li>
3961 first be sure to click the Save
3962 button beneath the list of tables and coordinates, to save any changes
3963 you made there. Then scroll all the way down, select the
3965 you want, and click Go.</li>
3966 <li>Internet Explorer for Windows may suggest an incorrect filename when
3971 browsers on Windows, do not have this problem.</li>
3972 </ul>
3976 columns!</a></h4>
3978 <p> No, it's MySQL that is doing
3984 underscores in the database name?</a></h4>
3986 <p> If you do not put a backslash before the underscore, this is a wildcard
3989 john2db ...<br /><br />
3991 If you put a backslash before the underscore, it means that the database
3992 name will have a real underscore.</p>
3996 statistics pages?</a></h4>
4007 if it already exists during the import. It does NOT drop the table after
4008 your export, it only affects the import file.</li>
4010 Otherwise, you may get an error if the table name exists but has a
4011 different structure.</li>
4013 (if any) will be included in backup.</li>
4015 field and table names formed with special characters are protected.</li>
4017 types set in the pmadb in the dump as
4019 </li>
4020 </ul>
4025 command, for better documentation (but resulting file is bigger).</li>
4027 once the INSERT verb and the table name.</li>
4030 </li>
4032 more info is provided in the
4034 but basically with this selected, invalid values are adjusted and
4035 inserted rather than causing the entire statement to fail.</li>
4036 </ul>
4040 in its name.</a></h4>
4043 is the normal way to reference a database and table name. Worse, MySQL
4044 will usually let you create a database with a dot, but then you cannot
4045 work with it, nor delete it.</p>
4058 for usage.<br />
4059 On a more recent pear version, I had problems with the state of Net_DIME
4060 being beta, so this single command
4062 needed modules.<br />
4063 If you use the Validator, you should be aware that any
4065 submit will be stored anonymously (database/table/column names,
4066 strings, numbers replaced with generic values). The Mimer
4069 We utilize it as free SOAP service.</p>
4073 it, but MySQL says "BLOB column '...' used in key specification without
4076 <p> The right way to do this, is to create the field without any indexes,
4078 dialog. On this page, you will be able to choose your BLOB field, and
4079 set a size to the index, which is the condition to create an index on
4080 a BLOB field.</p>
4084 editing fields?</a></h4>
4086 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4087 with many editing fields (table structure changes, row editing, etc.)
4088 (must be enabled in configuration - see.
4090 You can also have a look at the directive
4092 ('vertical') and see if this eases up editing for you.</p>
4096 WTF is this feature then useful for?</a></h4>
4098 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4099 on them. Otherwise you could just put a comment on the field. Because entering
4100 your own mimetype will cause serious syntax checking issues and validation,
4101 this introduces a high-risk false-user-input situation. Instead you have to
4102 initialize mimetypes using functions or empty mimetype definitions.<br />
4103 Plus, you have a whole overview of available mimetypes. Who knows all those
4104 mimetypes by heart so he/she can enter it at will?</p>
4108 can't I see any bookmarks below the query box? What is this variable for?
4109 </a></h4>
4111 <p> Any query you have executed can be stored as a bookmark on the page where the
4112 results are displayed. You will find a button labeled 'Bookmark this query'
4113 just at the end of the page.<br />
4114 As soon as you have stored a bookmark, it is related to the database you run
4115 the query on. You can now access a bookmark dropdown on each page, the query
4116 box appears on for that database.<br /><br />
4118 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4122 aware of that you HAVE to create a valid query, otherwise your query won't be
4123 even able to be stored in the database.<br />
4125 for your query will remain the way it is, but will be stripped of the /**/
4126 chars. So you can use:<br /><br />
4130 which will be expanded to<br /><br />
4134 in your query, where VARIABLE is the string you entered in the input box. If
4135 an empty string is provided, no replacements are made.<br /><br />
4137 A more complex example. Say you have stored this query:<br /><br />
4139 <br /><br />
4142 the full query will be:<br /><br />
4145 <br /><br />
4149 spaces inserted there
4150 will be later also inserted as spaces in your query and may lead to unexpected
4151 results especially when
4153 Your initial query which is going to be stored as a bookmark has to yield at
4154 least one result row so
4155 you can store the bookmark. You may have that to work around using well
4159 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4160 include exported table?</a></h4>
4162 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4163 document should look like following one (assuming you have table
4166 <pre>
4167 \documentclass{article} % or any class you want
4168 \usepackage{longtable} % for displaying table
4169 \begin{document} % start of document
4170 \include{table} % including exported table
4171 \end{document} % end of document
4172 </pre>
4176 access them.
4177 </a></h4>
4180 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4181 enable users to see all the database names.
4184 So if your users do not need those privileges, you can remove them and their
4185 databases list will shorten.</p>
4189 possible values for a field, based on some foreign table?</a></h4>
4191 <p> You have to setup appropriate links between the tables, and also
4195 foreign table, a drop-down list of values will be available.
4196 You will see two lists of values, the first list containing the key
4197 and the display field, the second list containing the display field
4198 and the key. The reason for this is to be able to type the first
4199 letter of either the key or the display field.<br /><br />
4201 For 100 values or more, a distinct window will appear, to browse foreign
4202 key values and choose one. To change the default limit of 100, see
4203 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4207 automatically when entering Browse mode for a table?</a></h4>
4209 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4210 </p>
4214 Excel files, how can I enable that?</a></h4>
4216 <p> Current version does support direct export to Microsoft Excel and Word
4217 versions 2000 and newer. If you need export older versions, you can use
4219 which works out of the box or you can
4221 several problems, most important are limitation of cell content to 255
4222 chars and no support for charsets, so think carefully whether you want to
4223 enable this.</b>. For enabling this you need to set
4227 module Spreadsheet_Excel_Writer into php include path. The
4228 installation can be done by following command:</p>
4230 <pre>
4231 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
4232 </pre>
4234 <p> First part of switches set we want to install beta version of that module
4235 (no stable version available yet) and then we tell pear we want to satisfy
4236 dependencies.</p>
4238 <p> If you are running in PHP safe mode, you will have to set
4241 modules are located, for example:</p>
4243 <pre>
4244 safe_mode_include_dir = /usr/local/lib/php
4245 </pre>
4249 <pre>
4250 cd phpMyAdmin
4251 mkdir tmp
4252 chmod o+rwx tmp
4253 </pre>
4257 what happens to my column comments stored in pmadb?</a></h4>
4259 <p> Automatic migration of a table's pmadb-style column comments to the native
4260 ones is done whenever you enter Structure page for this table.</p>
4265 <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>
4267 <ol>
4268 <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>
4269 <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>
4270 <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>
4271 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4272 <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>
4273 <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>
4274 </ol>
4281 <p> Our Bug Tracker is located at
4283 under the Bugs section.<br /><br />
4285 But please first discuss your bug with other users:<br />
4291 existing language, where do I start?</a></h4>
4293 <p> Always use the current SVN version of your language file.
4295 don't know how to get the SVN version, please ask one of the developers.
4296 <br />
4297 Please note that we try not to use HTML entities like &eacute; in
4298 the translations, since we define the right character set in the file.
4299 With HTML entities, the text on JavaScript messages would not
4300 display correctly.
4301 However there are some entities that need to be there, for quotes
4302 ,non-breakable spaces, ampersands, less than, greater than.<br />
4303 You can then put your translations, as a zip file to avoid losing special
4304 characters, on the sourceforge.net translation tracker.<br />
4305 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4306 list, because this is where we ask for translations of new messages.</p>
4310 phpMyAdmin. How should I proceed?</a></h4>
4315 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4316 </li>
4318 <li>generate patch with your changes:
4320 </li>
4323 tracker of the phpMyAdmin project</a>.
4324 </li>
4325 </ol>
4327 <p> Write access to the SVN tree is granted only to experienced developers who
4328 have already contributed something useful to phpMyAdmin.<br />
4334 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4336 <p> Please refer to
4337 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4338 </p>
4343 <p> If you use Apache web server, phpMyAdmin exports information about
4344 authentication to Apache environment and it can be used in Apache logs.
4345 Currently there are two variables available:
4346 </p>
4347 <dl>
4349 <dd>User name of currently active user (he does not have to be logged
4350 in).</dd>
4357 </dl>
4358 <p>
4360 </p>
4361 <pre>
4364 </pre>
4365 <p>
4366 You can then use any log analyzing tools to detect possible break in
4367 attempts.
4368 </p>
4374 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4375 It allows you to connect to local as well as remote servers.This requires you to enter
4376 server host name, username, password, port and the name of the database. Therefore you can
4377 now synchronize your databases placed on the same server or some remote server.
4378 </p>
4380 <p>For more details see <a href="./documentation-gsoc/Synchronization_User Manual.htm">How to synchronize</a>
4381 </p>
4383 <!-- DEVELOPERS -->
4386 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4387 great features have been written by other people and you too can help to
4388 make phpMyAdmin a useful tool.</p>
4390 <p> If you're planning to contribute source, please read the following
4391 information:</p>
4397 it free from other code.<br />
4398 Commonly used functions should be added to
4401 <li>Obviously, you're free to use whatever coding style you want. But
4402 please try to keep your code as simple as possible: beginners are
4403 using phpMyAdmin as an example application.<br />
4404 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4405 compliant on one hand, they fit the
4408 coding standards</a>
4409 on the other hand. Please pay attention to this.</li>
4410 <li>Please try to keep up the file-naming conventions. Table-related stuff
4413 <li>Please don't put message strings in your code, instead add the string
4418 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4419 better debug and profile their code.<br />
4420 Please see the
4422 options for more information.<br />
4423 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4424 lost during its re-entry into Earth's atmosphere and in memory of the
4425 brave men and women who gave their lives for the people of Earth.</li>
4426 </ul>
4430 <pre>
4441 </pre>
4443 <p>
4444 This program is free software; you can redistribute it and/or modify
4445 it under the terms of the GNU General Public License version 2,
4446 as published by the Free Software Foundation.
4447 </p>
4449 <p>
4450 This program is distributed in the hope that it will be useful,
4451 but WITHOUT ANY WARRANTY; without even the implied warranty of
4452 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4453 GNU General Public License for more details.
4454 </p>
4456 <p>
4457 You should have received a copy of the GNU General Public License
4458 along with this program; if not, write to the Free Software
4460 </p>
4462 <!-- CREDITS -->
4467 <ul>
4470 <ul>
4473 </ul></li>
4476 <ul>
4481 </ul></li>
4484 <ul>
4490 </ul></li>
4493 <ul>
4495 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4496 generate XHTML1.0 and CSS2 compliant codes</li>
4499 </ul></li>
4502 <ul>
4510 </ul></li>
4513 <ul>
4518 </ul></li>
4521 <ul>
4524 </ul></li>
4527 <ul>
4529 </ul></li>
4532 <ul>
4535 </ul></li>
4538 <ul>
4542 </ul></li>
4545 <ul>
4548 </ul></li>
4551 <ul>
4558 </ul></li>
4561 <ul>
4565 </ul></li>
4568 <ul>
4574 </ul></li>
4577 (http://sf.net/projects/phpmysqlformgen/)
4578 <ul>
4580 </ul></li>
4583 <ul>
4585 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4590 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4594 </ul></li>
4597 <ul>
4599 </ul></li>
4602 <ul>
4604 </ul></li>
4607 <ul>
4609 </ul></li>
4612 <ul>
4613 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4614 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4615 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4616 </ul></li>
4619 <ul>
4621 </ul></li>
4624 <ul>
4626 </ul></li>
4629 <ul>
4631 </ul></li>
4634 <ul>
4637 </ul></li>
4640 <ul>
4643 </ul></li>
4646 <ul>
4648 </ul></li>
4651 <ul>
4654 </ul></li>
4656 <li>Ivan A Kirillov
4657 <ul>
4659 </ul></li>
4662 <ul>
4664 </ul></li>
4667 <ul>
4669 </ul></li>
4672 <ul>
4674 </ul></li>
4677 <ul>
4679 </ul></li>
4682 <ul>
4684 </ul></li>
4687 <ul>
4689 </ul></li>
4691 </ul>
4693 <p>
4694 And also to the following people who have contributed minor changes,
4695 enhancements, bugfixes or support for a new language since version 2.1.0:
4696 </p>
4698 <p>
4699 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4700 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4701 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4702 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4704 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4705 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4706 Luís V., Martijn W. van der Lee,
4707 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4709 </p>
4714 <p>
4715 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4716 to create a web-based interface to MySQL using PHP3. Although I have not
4717 used any of his source-code, there are some concepts I've borrowed from
4718 him. phpMyAdmin was created because Peter told me he wasn't going to
4719 further develop his (great) tool.
4720 </p>
4721 <p>
4722 Thanks go to
4723 </p>
4724 <ul>
4726 code for the check when dropping a table or database. He also suggested
4727 that you should be able to specify the primary key on tbl_create.php3. To
4728 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4729 well as a bug-report. Plus many smaller improvements.
4730 </li>
4732 were introduced in 1.3.0 (including quite significant ones like the
4733 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4734 bug-fixes and help.
4735 </li>
4737 language-independent by outsourcing the strings to a separate file. He
4738 also contributed the French translation.
4739 </li>
4741 tbl_select.php3, a feature to display only some fields from a table.
4742 </li>
4744 functions in tbl_change.php3. He also added the
4746 </li>
4748 servers and is a regular contributor for bug-fixes.
4749 </li>
4751 features for 2.0.6.
4752 </li>
4753 </ul>
4754 <p>
4755 The following people have contributed minor changes, enhancements, bugfixes
4756 or support for a new language:
4757 </p>
4758 <p>
4759 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4760 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4761 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4762 G. Wieggers.
4763 </p>
4764 <p>
4765 And thanks to everyone else who sent me email with suggestions, bug-reports
4766 and or just some feedback.
4767 </p>
4773 <ul>
4775 - the default name of Apache's directory-level configuration file.</li>
4779 - a software application that enables a user to display and interact with
4780 text, images, and other information typically located on a web page at a
4781 website on the World Wide Web.</li>
4783 - a free software/open source data compression algorithm and program
4784 developed by Julian Seward.</li>
4786 - an important World Wide Web technology that enables a client web browser
4787 to request data from a program executed on the Web server.</li>
4789 - a log or record of changes made to a project.</li>
4791 - a computer system that accesses a (remote) service on another computer
4792 by some kind of network.</li>
4794 - a set of data values of a particular simple type, one for each row of
4795 the table.</li>
4797 - a packet of information sent by a server to a World Wide Web browser
4798 and then sent back by the browser each time it accesses that server.</li>
4800 - Comma-separated values</li>
4803 - an organized collection of data.</li>
4806 - a PHP module that extends PHP with additional functionality.</li>
4808 - a list of commonly asked question and there answers.</li>
4810 - one part of divided data/columns.</li>
4812 - a field or group of fields in a database record that point to a key
4813 field or group of fields forming a key of another database record in some
4814 (usually different) table.</li>
4816 - the free PDF library</li>
4818 GD Graphics Library</a> - a library by Thomas Boutell and others for
4819 dynamically manipulating images.</li>
4822 - gzip is short for GNU zip, a GNU free software file compression
4823 program.</li>
4825 - any machine connected to a computer network, a node that has a hostname.</li>
4827 - the unique name by which a network attached device is known on a network.</li>
4829 (HyperText Transfer Protocol)</a>
4830 - the primary method used to transfer or convey information on the World
4831 Wide Web.</li>
4834 additional security measures.</li>
4835 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4836 - a set of Internet-based services for servers using Microsoft Windows.</li>
4838 - a feature that allows quick access to the rows in a table.</li>
4840 - a data-oriented protocol used by source and destination hosts for
4841 communicating data across a packet-switched internetwork.</li>
4843 - a unique number that devices use in order to identify and communicate
4844 with each other on a network utilizing the Internet Protocol standard.</li>
4846 (Internet Server Application Programming Interface)</a>
4847 - the API of Internet Information Services (IIS).</li>
4849 - a business or organization that offers users access to the Internet and related services.</li>
4851 - a most commonly used standard method of lossy compression for
4852 photographic images.</li>
4858 - line of personal computers is designed, developed, manufactured, and
4859 marketed by Apple Computer.</li>
4860 <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>
4861 - the operating system which is included with all currently shipping Apple
4862 Macintosh computers in the consumer and professional markets.</li>
4864 - a cryptographic library.</li>
4866 - the MCrypt PHP extension.</li>
4867 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4868 - an Internet Standard for the format of e-mail.</li>
4870 - some sort of extension for the Apache Webserver.</li>
4872 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4873 Management System (DBMS).</li>
4875 - the improved MySQL client PHP extension.</li>
4877 - the MySQL client PHP extension.</li>
4879 - open standard for office documents.</li>
4880 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4881 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4883 (Portable Document Format)</a>
4884 - a file format developed by Adobe Systems for representing two
4885 dimensional documents in a device independent and resolution independent
4886 format.</li>
4888 - the PHP Extension and Application Repository.</li>
4890 - the perl-compatible regular expression functions for PHP</li>
4892 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4893 programming language used mainly for developing server-side applications
4894 and dynamic web content, and more recently, a broader range of software
4895 applications.</li>
4897 - a connection through which data is sent and received.</li>
4899 - Request for Comments (RFC) documents are a series of memoranda
4900 encompassing new research, innovations, and methodologies applicable to
4901 Internet technologies.</li>
4905 - represents a single, implicitly structured data item in a table.</li>
4907 - a computer system that provides services to other computing
4908 systems over a network.</li>
4909 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4910 - handlers for different table types</li>
4912 - a form of inter-process communication.</li>
4914 Sockets Layer)</a>
4915 - a cryptographic protocol which provides secure communication on the Internet.</li>
4917 - Structured Query Language</li>
4919 - a set of data elements (cells) that is organized, defined and stored as
4920 horizontal rows and vertical columns where each item can be uniquely
4921 identified by a label or key or by it?s position in relation to other items.</li>
4924 - a type of archive file format: the Tape ARchive format.</li>
4926 - one of the core protocols of the Internet protocol suite.</li>
4930 - a sequence of characters, conforming to a standardized format, that is
4931 used for referring to resources, such as documents and images on the
4932 Internet, by their location.</li>
4934 - A computer (program) that is responsible for accepting HTTP requests
4935 from clients and serving them Web pages.</li>
4937 - a W3C-recommended general-purpose markup language for creating
4938 special-purpose markup languages, capable of describing many different
4939 kinds of data.</li>
4941 - a popular data compression and archival format.</li>
4943 - an open-source, cross-platform data compression library by Jean-loup
4944 Gailly and Mark Adler.</li>
4945 </ul>
4946 </div>
4949 <li>Copyright © 2003 - 2009 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
4952 <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>
4953 </ul>
4955 </body>
4956 </html>