| blob | 992b6d8048787b9f970142dc27515f4e6c0de58f |
4 <!-- $Id$ -->
5 <!--
6 vim: expandtab ts=4 sw=4 sts=4 tw=78
7 -->
9 <head>
13 </head>
15 <body>
25 <br />
32 </div>
37 <!-- TOP MENU -->
38 <ul>
39 <li>
41 SourceForge phpMyAdmin project page [ http://www.phpmyadmin.net/ ]
42 </a>
43 </li>
44 <li>
45 Local documents:
46 <ul>
50 </ul>
51 </li>
52 <li>
53 Documentation version:
55 </li>
56 </ul>
59 <!-- REQUIREMENTS -->
63 <ul>
64 <li>
65 PHP3 or PHP4: phpMyAdmin widely uses the 'str_replace()' PHP function
72 If you want to display inline thumbnails of JPEGs, you also need
73 GD2 support in PHP.
74 </li>
75 <li>
78 syntax of string field types, this version of phpMyAdmin probably won't
80 </li>
81 <li>
82 a web-browser (doh!).
83 </li>
84 </ul>
87 <!-- INTRODUCTION -->
91 <p>
92 phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
93 a single database. To accomplish the latter you'll need a properly set up
94 MySQL user who can read/write only the desired database. It's up to you to
95 look up the appropriate part in the MySQL manual.<br />
96 Currently phpMyAdmin can:
97 </p>
99 <ul>
112 <li>using Query-by-example (QBE), create complex queries automatically connecting required tables</li>
115 <li>transform stored data into any format using a set of predefined functions,
116 like displaying BLOB-data as image or download-link or ...</li>
117 <li>
118 communicate in
120 </li>
121 </ul>
124 (*)
125 phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dumps
128 </p>
131 <!-- INSTALLATION -->
135 <p>
137 methods to the MySQL database server. It is still the system administrator's job to
138 grant permissions on the MySQL databases properly. </span>phpMyAdmin's
140 </p>
142 <p>
144 version before OS X, StuffIt unstuffs with Mac formats.<br />
145 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
146 before uploading them to your server, as PHP seems not to like Mac-style
148 </p>
150 <p>
153 if you are using a kit with files having this extension.
154 </p>
157 <ol>
158 <li> Choose and download a distribution kit with the files having the
160 web/PHP server interprets those extensions.</li>
161 <li> Untar or unzip the distribution (be sure to unzip the subdirectories):
163 document root. If you don't have direct access to your document root,
164 put the files in a directory on your local machine, and, after step 3,
165 transfer the directory on your web server using, for example, ftp.</li>
166 <li> Open the file config.inc.php3 in your favorite editor and change
167 the values for host, user, password and authentication mode to fit
170 Have a look at
172 explanation of all values.</li>
173 <li> It is recommended that you protect the directory in which you
174 installed phpMyAdmin (unless it's on a closed intranet, or you wish to
175 use HTTP or cookie authentication), for example with HTTP-AUTH (in a
178 information.</li>
179 <li> Open the file
181 in your browser. phpMyAdmin should now display a welcome screen
182 and your databases, or a login dialog if using HTTP or cookie
183 authentication mode.</li>
184 <li> For a whole set of new features (bookmarks, comments, SQL-history, PDP-generation)
185 you need to create a set of tables in your database. Please look at your scripts/
187 You can already use your phpMyAdmin to create the tables for you. Please be
188 aware that you may have to have special (administrator) privileges to create
190 you should specify the table names in your config.inc.php3 file. The directives
193 </ol>
196 <ul>
197 <li>Please do not copy your older config.inc.php3 over the new one: it may
198 offer new configuration variables, and the new version may depend on
199 these for normal behavior. It is suggested instead to insert your site
200 values in the new one.</li>
201 </ul>
204 <ul>
206 environment</b> where you want to give users access to their own
207 database and don't want them to play around with others.
208 <br />
209 Nevertheless be aware that MS Internet Explorer seems to be really
211 bit buggy in this area!<br />
213 HTTP or cookie mode so that your user/password pair are not in clear
214 in the configuration file.<br /><br /></li>
216 <li>HTTP and cookie authentication modes are more secure: the MySQL
217 password does not need to be set in the phpMyAdmin configuration file
220 <br />
221 However, keep in mind that the password travels in plain text, unless
222 you are using the HTTPS protocol.
223 <br />
224 In cookie mode, we send the password in a temporary cookie, so most
225 browsers should not store the password in their cookie file.
226 <br /><br /></li>
228 <li>
229 For 'HTTP' and 'cookie' modes, phpMyAdmin needs a controluser that has
234 You must specify the details for the controluser in the
240 only an example: use something else in your file!</b><br />
242 if it's not the same as the MySQL server's one.
243 <pre>
245 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
246 GRANT SELECT (
247 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
248 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
249 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
250 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
251 Execute_priv, Repl_slave_priv, Repl_client_priv
252 ) ON mysql.user TO 'pma'@'localhost';
253 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
254 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
255 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
256 ON mysql.tables_priv TO 'pma'@'localhost';
257 </pre>
258 If you are using an old MySQL version (below 4.0.2), please use this
259 query instead of the second one:
260 <pre>
262 GRANT SELECT (
263 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
264 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
265 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
266 ) ON mysql.user TO 'pma'@'localhost';
267 </pre>
268 ... and if you want to use the many new relation and bookmark
269 features:
270 <pre>
273 </pre>
274 (this of course requires you to have a special DB for phpMyAdmin, the
275 contents will be explained later)<br />
276 Of course, the above queries only work if your MySQL version supports
277 the GRANT command. This is the case since 3.22.11.
278 </li>
279 <li>
281 privileges on a set of particular databases. Normally you shouldn't
282 give global privileges to an ordinary user, unless you understand
283 the impact of those privileges (for example, you are creating
284 a superuser).<br />
287 <tt>GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';</tt>
288 <br />
289 What the user may now do is controlled entirely by the MySQL user
290 management system.<br />
291 With HTTP or cookie authentication mode, you don't need to fill the user/password
293 </li>
294 </ul>
297 <ul>
300 allows you to login as any valid MySQL user.</li>
301 <li>Is only supported with PHP running as an Apache module, not with
302 CGI.</li>
303 </ul>
306 <ul>
307 <li>You can use this method as a replacement for the HTTP
308 authentication (for example, if you're running IIS).
309 </li>
311 <li>With this mode, the use can truly logout of phpMyAdmin and login back
312 with the same username.</li>
313 </ul>
316 <ul>
317 <li>This mode is the less secure one because it requires you to fill the
322 <li>In the ISP FAQ section, there is an entry explaining how to protect
323 your configuration file.<br /></li>
324 <li>For additional security in this mode, you may wish to consider the
327 directives.</li>
328 </ul>
331 <!-- CONFIGURATION -->
335 <p>
338 the option that allows to use the *nix end of line character
340 you have modified.
341 </p>
344 <dl>
346 <dd>
347 Sets here the complete URL (with full path) to your phpMyAdmin version.
349 <br /><br />
350 phpMyAdmin needs this setting, because of requirements of the HTTP
351 protocol, explained in RFC2616, section 14.30.
352 <br /><br />
353 Don't forget the slash at the end of your URL. The URL must contain
354 characters that are valid for a URL, and on some servers, the path
355 is case-sensitive.
356 <br /><br />
357 Starting with version 2.3.0, you can try to leave this parameter
358 empty, because the program tries to auto-detect its proper value.
359 Additional details are in the configuration file.
360 <br /><br />
361 Alternatively, this setting can be dynamically completed. For example,
362 you can try to use such a kind of code:
363 <pre>
364 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
365 . $_SERVER['HTTP_HOST']
366 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
369 or
371 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
372 . $_SERVER['SERVER_NAME']
373 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
375 </pre>
379 <br /><br />
380 </dd>
382 <dd>
383 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the system
384 detects your absolute URI automatically, we display a warning to remind
385 you. If you have tested the automatic detection, and it works perfectly
386 for your setup, then you can set this variable to squelch the warning.
387 <br /><br />
388 </dd>
391 <dd>
392 Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
393 with master / foreign - tables (see
395 <br />
396 If you tried to set this up and it does not work for you, have a look on
398 use it. You will find a link that will analyze why those features have
399 been disabled.<br />
400 If you do not want to use those features set this variable to
402 <br /><br />
403 </dd>
406 <dd>
407 Since version 1.4.2, phpMyAdmin supports the administration of multiple
408 MySQL servers.
409 Therefore, a $cfg['Servers']-array has been added which contains
410 the login information for the different servers. The first
413 the second server, etc.
414 If you have only one server to administer, simply leave free the
415 hostname of the other $cfg['Server']-entries.
416 <br /><br />
417 </dd>
420 <dd>
421 The hostname of your $i-th MySQL-server. E.g. localhost.
422 <br /><br />
423 </dd>
426 <dd>
427 The port-number of your $i-th MySQL-server. Default is 3306 (leave
429 ignores this port number and connects with the socket, so if you want
430 to connect to a port different from the default port, use
432 $cfg['Servers'][$i]['host'].
433 <br /><br />
434 </dd>
437 <dd>
438 The path to the socket to use. Leave blank for default.<br />
439 To use the socket feature you must run PHP 3.0.10 or more.
440 <br /><br />
441 </dd>
444 <dd>
445 What type connection to use with the MySQL server. Your options are
447 is nearly guaranteed to be available on all MySQL servers, while
448 sockets are not supported on some platforms.
449 <br /><br />
450 To use the socket mode, your MySQL server must be on the same machine
451 as the Web server.
452 <br /><br />
453 </dd>
456 <dd>
457 Whether to use a compressed protocol for the MySQL server connection
458 or not (experimental).<br />
460 </dd>
462 <dt>
465 </dt>
466 <dd>
467 When using HTTP or cookie authentication modes (or 'config'
468 authentication mode since phpMyAdmin 2.2.1), you need to supply the
473 This account is used to check what databases the user will see at
474 login.<br />
477 <br /><br />
478 Note that if you try login to phpMyAdmin with this
482 <br /><br />
483 In versions before 2.2.5, those were called
485 <br /><br />
486 </dd>
489 <dd>
490 Whether config or cookie or http authentication should be used for this
491 server.
493 <ul>
494 <li>
495 'config' authentication
497 way: username and password are stored in
499 </li>
500 <li>
501 'cookie' authentication mode
503 2.2.3 allows you to log in as any valid MySQL user with the
504 help of... cookies. Log name and password are stored in
505 cookies during the session and password is deleted when it
506 ends.
507 </li>
508 <li>
509 'http' authentication (was called 'advanced' in older versions)
511 allows you to log in as any valid MySQL user via HTTP-Auth.
512 </li>
513 </ul><br />
516 for more information.
517 <br /><br />
518 </dd>
520 <dt>
523 </dt>
524 <dd>
525 The user/password-pair which phpMyAdmin will use to connect to this
526 MySQL-server. This user/password pair is not needed when HTTP or cookie
527 authentication is used, and should be empty.<br /><br />
528 </dd>
531 <dd>
532 If set to a(an array of) database name(s), only this(these) database(s)
533 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
534 database(s) name(s) may contain MySQL wildcards characters
538 This setting is an efficient way to lower the server charge since the
539 latter does not need to send MySQL requests to build the available
541 privileges rules of the MySQL database server</span>. If set, it just
542 means only these databases will be displayed but
544 <br /><br />
545 An example of using more that one database:
547 </dd>
550 <dd>
551 Only useful when using phpMyAdmin with multiple server entries. If set,
552 this string will be displayed instead of the hostname in the pull-down
553 menu on the main page. This can be useful if you want to show only
554 certain databases on your system, for example.
555 <br /><br />
556 </dd>
558 <dt>
561 </dt>
562 <dd>
563 Starting with version 2.3.0 phpMyAdmin offers a lot of features
564 to work with master / foreign - tables. To use those as well as
565 the bookmark feature you need special tables with a
566 predefined structure, which we explain below.<br />
567 If you are the only user of this phpMyAdmin installation, you can
568 use your current database to store those special tables; in this
569 case, just put your current database name in
571 <br /><br />
572 If you are setting up a multi-user phpMyAdmin installation,
573 you will need to create a new database and setup special privileges,
574 so, as superuser:
575 <br /><br />
576 <ul>
577 <li>
578 create a new database for phpMyAdmin:<br />
582 privileges on this database. Here is a query to set up
585 controluser):<br />
586 <tt>
587 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to 'pma'@'localhost';
588 </tt><br />
590 </li>
591 <li>
593 </li>
594 </ul><br />
595 </dd>
597 <dt>
600 </dt>
601 <dd>
602 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can be
603 useful for queries you often run.<br /><br />
605 To allow the usage of this functionality you have to:
606 <ul>
608 <li>within this database create a table following this scheme:
609 <br />
610 <tt>
619 </tt>
620 </li>
621 <li>enter the table name in
623 </ul><br />
624 </dd>
626 <dt>
629 </dt>
630 <dd>
631 Since release 2.2.4 you can describe, in a special 'relation' table,
632 which field is a key in another table (a foreign key). phpMyAdmin
633 currently uses this to
634 <ul>
635 <li>
636 make clickable, when you browse the master table, the data values
637 that point to the foreign table;
638 </li>
639 <li>
641 when browsing the master table, if you move the mouse to a column
642 containing a foreign key (use also the 'table_info' table);
643 </li>
644 <li>
645 display links on the table properties page, to check referential
646 integrity (display missing foreign keys) for each described key;
647 </li>
648 <li>
649 in query-by-example, create automatic joins (see an example in
651 </li>
652 <li>
653 enable you to get a PDF schema of your database (also uses the
654 table_coords table).
655 </li>
656 </ul>
657 <br />
659 The keys can be numeric or character.
660 <br /><br />
662 To allow the usage of this functionality the superuser has to:
663 <ul>
665 <li>
666 within this database create a table following this scheme:
667 <br />
668 <tt>
674 `foreign_table` varchar(64) NOT NULL default '',<br />
675 `foreign_field` varchar(64) NOT NULL default '',<br />
676 PRIMARY KEY (`master_db`, `master_table`, `master_field`),<br />
679 </tt>
680 </li>
681 <li>
682 put the relation table name in
684 </li>
685 <li>
686 now as normal user open phpMyAdmin and for each one of your
687 tables where you want to use this feature, click
689 </li>
690 </ul><br />
693 future development of the cross-db relations.<br /><br />
694 </dd>
696 <dt>
699 </dt>
700 <dd>
701 Since release 2.3.0 you can describe, in a special 'table_info'
702 table, which field is to be displayed as a tool-tip when moving the
703 cursor over the corresponding key.
704 <br />
705 This configuration variable will hold the name of this special
706 table.
707 To allow the usage of this functionality the superuser has to:
708 <ul>
710 <li>within this database create a table following this scheme:
711 <br />
712 <tt>
716 `display_field` varchar(64) NOT NULL default '',<br />
719 </tt>
720 </li>
721 <li>
722 put the table name in
724 </li>
725 <li>
726 then for each table where you want to use this feature,
728 to choose the field.
729 </li>
730 </ul><br />
732 <br /><br />
733 </dd>
735 <dt>
739 </dt>
740 <dd>
741 Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
742 the relations between your tables. To do this it needs two tables
745 table will be placed on a PDF schema output).
746 <br /><br />
749 output.
750 <br /><br />
751 To allow the usage of this functionality the superuser has to:
752 <ul>
754 <li>
755 within this database create a table following this scheme:
756 <br />
757 <tt>
764 PRIMARY KEY (`db_name`, `table_name`, `pdf_page_number`)<br />
765 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin PDF output';<br />
766 </tt>
767 </li>
768 <li>
769 also within this database create:<br />
770 <tt>
773 `page_nr` int(10) unsigned NOT NULL auto_increment,<br />
778 </tt>
779 </li>
780 <li>
781 put the first table name in
783 and the second table name in
785 </li>
786 </ul><br />
788 <br /><br />
789 </dd>
791 <dt>
794 </dt>
795 <dd>
796 <!-- This part requires a content update! -->
797 Since release 2.3.0 you can store comments to describe each column
799 <br /><br />
800 Starting with release 2.5.0, comments are consequently used on the table property
801 pages and table browse view, showing up as tool-tips above the column name (properties page)
802 or embedded within the header of table in browse view. They can also be shown
803 in a table dump. Please see the relevant configuration directives later on.
804 <br /><br />
805 Also new in release 2.5.0 is a mime-transformation system which is also based on
807 for further information. To use the mime-transformation system, your column_info
808 table has to have the three new fields 'mimetype', 'transformation', 'transformation_options'.
809 <br /><br />
810 To allow the usage of this functionality the superuser has to:
811 <ul>
813 <li>
814 within this database create a table following this scheme:
815 <br />
816 <tt>
824 transformation varchar(255) NOT NULL default '',<br />
825 transformation_options varchar(255) NOT NULL default '',<br />
827 UNIQUE KEY db_name (db_name, table_name, column_name)<br />
829 </tt>
830 </li>
831 <li>
832 put the table name in
834 </li>
835 <li>
837 <tt>
841 ADD `transformation_options` VARCHAR( 255 ) NOT NULL ;<br />
842 </tt>
843 and remember that the Variable in config.inc.php has been renamed
844 from <br />$cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i]['column_info']
845 </li>
846 </ul><br />
847 </dd>
849 <dt>
852 </dt>
853 <dd>
854 Since release 2.5.0 you can store your SQL history, which means all queries you
855 entered manually into the phpMyAdmin interface. If you don't want to use a table-
856 based history, you can use the JavaScript-based history. Using that, all your
857 history items are deleted when closing the window.<br /><br />
860 you want to have on hold. On every login, this list gets cut to the maximum amount.
861 <br /><br />
863 The query history is only available if you use the JavaScript-based query window,
865 <br /><br />
867 To allow the usage of this functionality the superuser has to:
868 <ul>
870 <li>
871 within this database create a table following this scheme:
872 <br />
873 <tt>
882 INDEX ( `username` , `db` , `table` , `timevalue` )<br />
884 </tt>
885 </li>
886 <li>
887 put the table name in
889 </li>
890 </ul><br />
891 </dd>
893 <dt>
896 </dt>
897 <dd>
898 Because release 2.5.0 introduced the new MIME-transformation support, the
899 column_info table got enhanced with three new fields. If the above variable is
900 set to TRUE (default) phpMyAdmin will check if you have the latest table structure
901 available. If not, it will emit a warning to the superuser.<br /><br />
903 You can disable this checking behavior by setting the variable to false, which
904 should offer a performance increase.<br /><br />
906 Recommended to set to FALSE, when you are sure, your table structure is up to date.
907 <br /><br />
908 </dd>
910 <dt>
912 </dt>
913 <dd>
914 If your rule order is empty, then IP authentication is disabled.
915 <br /><br />
917 applies all deny rules followed by allow rules.
918 Access is allowed by default. Any client which does not match a Deny
919 command or does match an Allow command will be allowed access to the
920 server.
921 <br /><br />
923 applies all allow rules followed by deny rules. Access is denied by
924 default. Any client which does not match an Allow directive or does
925 match a Deny directive will be denied access to the server.
926 <br /><br />
927 If your rule order is set to 'explicit', the authentication is
928 performed in a similar fashion to rule order 'deny,allow', with the
932 and was available in Apache by specifying allow and deny rules without
933 setting any order.
934 <br /><br />
935 </dd>
937 <dt>
939 </dt>
940 <dd>
941 The general format for the rules is as such:<br />
942 <tt>
943
945 </tt>
946 <br /><br />
951 well:<br />
952 <tt>
955 </tt>
956 <br /><br />
958 Having an empty rule list is equivalent to either using
962 <br /><br />
964 For the IP matching system, the following work:<br />
968 But the following does not work:<br />
970 <br /><br />
971 </dd>
974 <dd>
975 If you have more than one server configured, you can set
977 that server when phpMyAdmin is started, or set it to 0 to be given a
978 list of servers without logging in.<br />
980 MUST be set to that server.
981 <br /><br />
982 </dd>
985 <dd>
986 Defines whether to use GZip output buffering for increased
987 speed in HTTP transfers.
988 <br /><br />
989 </dd>
992 <dd>
993 Whether persistent connections should be used or not (mysql_connect or
994 mysql_pconnect).
995 <br /><br />
996 </dd>
999 <dd>
1000 Set the number of seconds a script is allowed to run. If seconds is set
1001 to zero, no time limit is imposed.<br />
1002 This setting is used while importing/exporting dump files but has no
1003 effect when PHP is running in safe mode.
1004 <br /><br />
1005 </dd>
1008 <dd>
1009 Mark used tables and make it possible to show databases with locked
1010 tables (since 3.23.30).
1011 <br /><br />
1012 </dd>
1015 <dd>
1016 Defines whether SQL-queries generated by phpMyAdmin should be displayed
1017 or not.
1018 <br /><br />
1019 </dd>
1022 <dd>
1023 Defines whether normal users (non-administrator) are allowed to
1024 delete their own database or not. If set as FALSE, the link "Drop
1026 mydatabase" will be rejected. Quite practical for ISP's with many
1027 customers.
1028 <br /><br />
1029 </dd>
1032 <dd>
1034 displayed when you're about to loose data.
1035 <br /><br />
1036 </dd>
1039 <dd>
1040 Define whether the previous login should be recalled or not in cookie
1041 authentication mode.
1042 <br /><br />
1043 </dd>
1046 <dd>
1047 Define whether the "search string inside database" is enabled or not.
1048 <br /><br />
1049 </dd>
1052 <dd>
1053 Defines whether to use select-based menu and display only the current
1054 tables in the left frame (smaller page).
1055 Only in Non-Lightmode you can use the feature to display nested folders
1056 using $cfg['LeftFrameTableSeparator']
1057 <br /><br />
1058 </dd>
1061 <dd>
1062 Defines a string to be used to nest table spaces. Defaults to '__'. This
1063 means if you have tables like 'first__second__third' this will be
1065 If set to FALSE or empty, the feature is disabled.
1066 NOTE: You shall not use this Separator in a table name at the beginning or
1067 end of a table name, or multiple times after another without any other
1068 characters in between.
1069 <br /><br />
1070 </dd>
1073 <dd>
1074 Defines how many sublevels should be displayed when splitting
1075 up tables by the above Separator.
1076 <br /><br />
1077 </dd>
1080 <dd>
1081 Defines whether to display table comment as tool-tip in left frame or
1082 not.
1083 <br /><br />
1084 </dd>
1087 <dd>
1088 If tool-tips are enabled and a DB comment is set, this will flip the comment
1089 and the real name. That means, if you have a table called 'user0001' and add
1090 the comment 'MyName' on it, you will see the name 'MyName' used consequently
1091 in the left frame and the tool-tip shows the real name of the DB.
1092 <br /><br />
1093 </dd>
1096 <dd>
1097 Same as $cfg['ShowTooltipAliasDB'], except this works for table names.
1098 <br /><br />
1099 </dd>
1102 <dd>
1103 Defines whether to display space usage and statistics about databases
1104 and tables or not.<br />
1105 Note that statistics requires at least MySQL 3.23.3 and that, at this
1106 date, MySQL doesn't return such information for Berkeley DB tables.
1107 <br /><br />
1108 </dd>
1110 <dt>
1115 </dt>
1116 <dd>
1120 starting main (right) frame. This setting does not check MySQL commands
1121 entered directly.
1122 <br /><br />
1124 Please note that to block the usage of phpinfo() in scripts, you
1125 have to put this in your php.ini:<br />
1127 <br /><br />
1131 coded password value in the configuration file, end users can't be
1132 allowed to change their passwords.
1133 <br /><br />
1134 </dd>
1137 <dd>
1138 Defines whether to suggest a database name on the
1140 <br /><br />
1141 </dd>
1144 <dd>
1146 content or not.
1147 <br /><br />
1148 </dd>
1151 <dd>
1152 Defines whether navigation bar buttons contain text or symbols only.
1153 <br /><br />
1154 </dd>
1157 <dd>
1158 Defines whether an user should be displayed a
1160 <br /><br />
1161 </dd>
1164 <dd>
1165 Number of rows displayed when browsing a result set. If the result set
1166 contains more rows, Previous/Next links will be shown.
1167 <br /><br />
1168 </dd>
1171 <dd>
1175 DATE, DATETIME & TIMESTAMP, ascending order else- by default.
1176 <br /><br />
1177 </dd>
1180 <dd>
1182 from edition when browsing a table's content or not.
1183 Valid values are:<br />
1186 <br />
1189 <br /><br />
1190 </dd>
1193 <dd>
1194 Defines whether MySQL functions fields should be displayed or not in
1195 edit/insert mode.
1196 <br /><br />
1197 </dd>
1200 <dd>
1201 Defines which type of editing controls should be used for CHAR and
1202 VARCHAR fields. Possible values are:
1203 <ul>
1204 <li>
1205 input - this allows to limit size of text to size of field in
1206 MySQL, but has problems with newlines in fields
1207 </li>
1208 <li>
1209 textarea - no problems with newlines in fields, but also no
1210 length limitations
1211 </li>
1212 </ul>
1213 Default is old behavior so input.
1214 <br /><br />
1215 </dd>
1217 <dt>
1221 </dt>
1222 <dd>
1223 Defines whether to allow the use of zip/GZip/BZip2 compression when
1224 creating a dump file or not.
1225 <br /><br />
1226 </dd>
1229 <dd>
1230 If set to True, do use less graphically intense tabs on the top of the mainframe.
1231 <br /><br />
1232 </dd>
1235 <dd>
1236 Defines the tab displayed by default on server view. Possible
1241 <br /><br />
1242 </dd>
1245 <dd>
1246 Defines the tab displayed by default on database view. Possible
1249 <br /><br />
1250 </dd>
1253 <dd>
1254 Defines the tab displayed by default on table view. Possible
1258 <br /><br />
1259 </dd>
1262 <dd>
1263 If set to an URL which points to the MySQL documentation (type depends
1265 generated.
1266 <br />
1268 Documentation page</a> for more information about MySQL manuals and
1269 their types.
1270 <br /><br />
1271 </dd>
1274 <dd>
1275 Type of MySQL documentation:
1276 <ul>
1282 </ul>
1283 <br /><br />
1284 </dd>
1287 <dd>
1288 Defines the default language to use, if not browser-defined or
1289 user-defined.<br />
1291 this setting.
1292 <br /><br />
1293 </dd>
1296 <dd>
1297 Force: always use this language (must be defined in the
1299 <br /><br />
1300 </dd>
1303 <dd>
1304 Default character set to use for recoding of MySQL queries. This must be
1306 option.<br />
1307 You can give here any character set which is in
1309 choice, user can select any of them.
1310 <br /><br />
1311 </dd>
1314 <dd>
1315 Allow character set recoding of MySQL queries. You need recode or iconv
1316 support (compiled in or module) in PHP to allow MySQL queries recoding
1317 and used language file must have it enabled (by default only these
1318 which are in Unicode, just to avoid losing some characters).
1319 <br /><br />
1320 </dd>
1323 <dd>
1324 You can select here which functions will be used for character set
1325 conversion.
1326 Possible values are:<br />
1327 <ul>
1328 <li>auto - automatically use available one (first is tested
1329 iconv, then recode)</li>
1332 </ul>
1333 Default is auto.
1334 <br /><br />
1335 </dd>
1338 <dd>
1339 Specify some parameters for iconv used in charset conversion. See
1340 <a
1342 documentation</a> for details.
1343 <br /><br />
1344 </dd>
1347 <dd>
1348 Available character sets for MySQL conversion. You can add your own (any of
1349 supported by recode/iconv) or remove these which you don't use.
1350 Character sets will be shown in same order as here listed, so if you
1351 frequently use some of these move them to the top.
1352 <br /><br />
1353 </dd>
1356 <dd>
1358 MIME transformations.<br />
1359 Possible values are:<br />
1360 <ul>
1361 <li>
1362 auto - automatically detect, this is a bit expensive
1364 according to your server real possibilities
1365 </li>
1368 </ul>
1369 Default is auto.
1370 <br /><br />
1371 </dd>
1374 <dd>
1375 Left frame width in pixel.
1376 <br /><br />
1377 </dd>
1379 <dt>
1382 </dt>
1383 <dd>
1384 The background colors (HTML) used for both the frames.
1385 <br /><br />
1386 </dd>
1388 <dt>
1390 </dt>
1391 <dd>
1392 The URI of the background image used for the right frame. It can be
1393 absolute as well as relative from your phpMyAdmin directory.
1394 </dd>
1397 <dd>
1398 The color (HTML) used for the pointer in the left frame (does not work
1399 with Netscape 4).
1400 <br /><br />
1401 </dd>
1404 <dd>
1405 The size of a table's border.
1406 <br /><br />
1407 </dd>
1410 <dd>
1411 The color (HTML) used for table headers.
1412 <br /><br />
1413 </dd>
1416 <dd>
1417 The color (HTML) #1 for table rows.
1418 <br /><br />
1419 </dd>
1422 <dd>
1423 The color (HTML) #2 for table rows.
1424 <br /><br />
1425 </dd>
1427 <dt>
1430 </dt>
1431 <dd>
1432 The colors (HTML) uses for the pointer and the marker in browse mode
1434 The former feature highlights the row over which your mouse is passing
1435 and the latter lets you visually mark/unmark rows by clicking on
1436 them.<br />
1437 You can disable both of these features by emptying the respective
1438 directive.
1439 <br /><br />
1440 </dd>
1442 <dt>
1447 </dt>
1448 <dd>
1449 Number of columns and rows for the textareas.<br />
1451 SQL textareas inside the query window.<br />
1452 The Char* values are used for CHAR and VARCHAR editing (if configured
1453 via $cfg['CharEditing']).
1454 <br /><br />
1455 </dd>
1457 <dt>
1459 </dt>
1460 <dd>
1461 Defines whether textarea for LONGTEXT fields should have double size.
1462 <br /><br />
1463 </dd>
1465 <dt>
1467 </dt>
1468 <dd>
1469 Defines if the whole textarea of the query box will be selected on
1470 click.
1471 <br /><br />
1472 </dd>
1474 <dt>
1476 </dt>
1477 <dd>
1478 Enable Ctrl+Arrows moving between fields when editing?
1479 <br /><br />
1480 </dd>
1483 <dd>
1485 field on browse view. Can be turned off by a toggle button on the
1486 browse page.
1487 <br /><br />
1488 </dd>
1490 <dt>
1493 </dt>
1494 <dd>
1495 Defines the place where modify and delete links would be put when
1496 tables contents are displayed (you may have them displayed both at the
1497 left and at the right).
1500 <br /><br />
1501 </dd>
1505 </dt>
1506 <dd>
1507 There are 3 display modes: horizontal, horizontalflipped and vertical. Define
1508 which one is displayed by default. The first mode displays each row on a
1509 horizontal line, the second rotates the headers by 90 degrees, so you can use
1510 descriptive headers even though fields only contain small values and still
1511 print them out. The vertical mode sorts each row on a vertical lineup.<br /><br />
1512 The HeaderFlipType can be set to 'css' or 'faked'. When using 'css' the rotation
1513 of the header for horizontalflipped is done via CSS. If set to 'faked' PGP
1514 does the transformation for you, but of course this does not look as good as CSS.
1515 <br /><br />
1516 </dd>
1519 <dd>
1520 When editing/creating new columns in a table all fields normally get lined up
1521 one field a line. (default: 'horizontal'). If you set this to 'vertical' you
1522 can have each field lined up vertically beneath each other. You can save up
1523 a lot of place on the horizontal direction and no longer have to scroll.
1524 <br /><br />
1525 </dd>
1529 </dt>
1530 <dd>
1531 By setting the corresponding variable to TRUE you can enable the display of
1532 column comments in Browse or Property display. In browse mode, the comments
1533 are show inside the header. In property mode, comments are displayed using
1534 a CSS-formatted dashed-line below the name of the field. The comment is shown
1535 as a tool-tip for that field.
1536 <br /><br />
1537 </dd>
1540 <dd>
1541 The name of the directory, ending with a slash, where SQL files have
1542 been uploaded by other means than phpMyAdmin (for example, ftp).
1543 Those files are available under a drop-down box when you click the
1544 database name, then the SQL tab.
1545 <br /><br />
1547 <br /><br />
1548 This feature is useful when your file is too big to be uploaded via
1549 HTTP, or when file uploads are disabled in PHP.
1550 <br /><br />
1551 Please note that if PHP is running in safe mode, this directory must
1552 be owned by the same user as the owner of the phpMyAdmin scripts.
1553 <br /><br />
1554 </dd>
1557 <dd>
1558 The name of the directory, ending with a slash, where dumps can
1559 be saved.
1560 <br /><br />
1561 Please note that the directory has to be writable for user running
1562 webserver.
1563 <br /><br />
1564 Please note that if PHP is running in safe mode, this directory must
1565 be owned by the same user as the owner of the phpMyAdmin scripts.
1566 <br /><br />
1567 </dd>
1570 <dd>
1571 Repeat the headers every X cells, or 0 to deactivate.
1572 <br /><br />
1573 </dd>
1583 </dt>
1584 <dd>
1585 All those variables affect the new query frame/window. When $cfg['QueryFrame']
1586 is set to true a new frame is embedded on the left with a small area. Clicking
1587 on that results in opening a direct interface to enter SQL queries.<br /><br />
1588 When $cfg['QueryFrameJS'] is set to true, clicking on that link opens a new
1589 custom sized browser window ($cfg['QueryWindowWidth'], $cfg['QueryWindowWidth'] -
1590 both integers for the size in pixels). If set to false, clicking on the link
1591 only opens the SQL input in the mainframe.<br /><br />
1592 The usage of the JavaScript query window is recommended if you have a JavaScript
1593 enabled browser. Basic functions are used to exchange quite a few variables, so
1594 most 4th generation browsers should be capable to use that feature. It currently
1596 If $cfg['QueryHistoryDB'] is set to TRUE, all your Queries are logged to a table,
1598 If set to FALSE, all your queries will be appended to the form, but only as long
1599 as your window is opened they remain saved.<br /><br />
1600 When using the JavaScript based query window, it will always get updated when you
1601 click on a new table/db to browse and will focus if you click on "Edit SQL" after
1602 using a query.<br /><br />
1603 If $cfg['QueryHistoryDB'] is set to TRUE you can specify the amount of saved
1604 history items using $cfg['QueryHistoryMax'].<br /><br />
1605 The query window also has a custom tabbed look to group the features. Using the
1606 variable $cfg['QueryWindowDefTab'] you can specify the default tab to be used
1607 when opening the query window. It can be set to either 'sql', 'files', 'history'
1608 or 'full'.<br /><br />
1609 The variable $cfg['QueryFrameDebug'] can be used by developers for easier future
1610 feature integration.
1611 <br /><br />
1612 </dd>
1615 <dd>
1617 <br /><br />
1618 </dd>
1621 <dd>
1622 Determines for how large tables phpMyAdmin should get exact row count by
1626 <br /><br />
1627 </dd>
1630 <dd>
1631 The main use of the new SQL Parser is to pretty-print SQL queries. By
1632 default we use HTML to format the query, but you can disable this by
1634 <br /><br />
1635 </dd>
1639 <dd>
1640 For the pretty-printing of SQL queries, under some cases the part of a
1641 query inside a bracket is indented. By changing
1644 specifies the units of the indent amount that you specified. This is
1645 used via stylesheets.
1646 <br /><br />
1647 </dd>
1650 <dd>
1651 This array is used to define the colours for each type of element of
1652 the pretty-printed SQL queries. The tuple format is<br />
1654 If you specify an empty string for the color of a class, it is ignored
1655 in creating the stylesheet.
1656 You should not alter the class names, only the colour strings.<br />
1658 <ul>
1682 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1683 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1684 </ul><br />
1685 </dd>
1687 <dt><b>$cfg['SQLValidator']['use']</b> boolean</dt>
1688 <dd>
1689 phpMyAdmin now supports use of the <a href="http://developer.mimer.com/validator/index.htm">Mimer SQL Validator</a> service,
1690 as originally published on
1692 <br />
1693 For help in setting up your system to use the service, see the
1695 <br /><br />
1696 </dd>
1698 <dt><b>$cfg['SQLValidator']['username']</b> string<br />
1699 <b>$cfg['SQLValidator']['password']</b> string</dt>
1700 <dd>
1701 The SOAP service allows you to login with <tt>anonymous</tt>
1702 and any password, so we use those by default.. Instead, if
1703 you have an account with them, you can put your login details
1704 here, and it will be used in place of the anonymous login.
1705 <br /><br />
1706 </dd>
1708 <dt><b>$cfg['DBG']['enable']</b> boolean</dt>
1709 <dd>
1710 <b>DEVELOPERS ONLY!</b><br />
1711 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1712 the code.
1713 <br />
1714 For help in setting up your system to this, see the
1716 </dd>
1718 <dt><b>$cfg['DBG']['profile']['enable']</b> boolean</dt>
1719 <dd>
1720 <b>DEVELOPERS ONLY!</b><br />
1721 Enable profiling support for phpMyAdmin. This will append a chunk of data
1722 to the end of every page displayed in the main window with profiling
1723 statistics for that page.<br />
1724 You may need need to increase the maximum execution time for this to
1725 complete successfully.
1726 </dd>
1728 <dt><b>$cfg['DBG']['profile']['threshold']</b> float (units in milliseconds)</dt>
1729 <dd>
1730 <b>DEVELOPERS ONLY!</b><br />
1731 When profiling data is displayed, this variable controls the threshold of
1732 display for any profiling data, based on the average time each time has
1733 taken. If it is over the threshold it is displayed, otherwise it is not
1734 displayed. This takes a value in milliseconds. In most cases you don't need
1735 to edit this.
1736 </dd>
1738 <dt><b>$cfg['ColumnTypes'] </b>array</dt>
1739 <dd>
1740 All possible types of a MySQL column. In most cases you don't need to
1741 edit this.
1742 <br /><br />
1743 </dd>
1745 <dt><b>$cfg['AttributeTypes'] </b>array</dt>
1746 <dd>
1747 Possible attributes for fields. In most cases you don't need to edit
1748 this.
1749 <br /><br />
1750 </dd>
1752 <dt><b>$cfg['Functions'] </b>array</dt>
1753 <dd>
1754 A list of functions MySQL supports. In most cases you don't need to
1755 edit this.
1756 <br /><br />
1757 </dd>
1759 </dl>
1761 <!-- TRANSFORMATIONS -->
1763 <h2>Transformations</h2>
1765 <p>
1769 </p>
1772 <h3>[1. Introduction]</h3>
1774 <p>To enable transformations, you have to setup the column_info table and the proper
1776 <br />
1778 <p>You can apply different transformations to the contents of each field. The
1779 transformation will take the content of each field and transform it with
1780 certain rules defined in the selected transformation.</p><br />
1782 <p>Say you have a field 'filename' which contains a filename. Normally you would see
1783 in phpMyAdmin only this filename. Using transformations you can transform that filename
1784 into a HTML link, so you can click inside of the phpMyAdmin structure on the field's
1785 link and will see the file displayed in a new browser window. Using transformation
1786 options you can also specify strings to append/prepend to a string or the format you
1787 want the output stored in.</p><br />
1789 <p>For a general overview of all available transformations and their options, you can
1790 consult your <i><www.your-host.com>/<your-install-dir>/libraries/transformations/overview.php3</i>
1791 installation.</p>
1794 <h3>[2. Usage]</h3>
1796 <p>Go to your tbl_properties.inc.php3 page (i.e. reached through clicking on the
1797 'properties' link for a table). There you will see three new fields at the end of the
1798 line. They are called 'MIME-type', 'Browser transformation' and 'Transformation options'.</p>
1799 <br />
1801 <ul>
1802 <li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
1803 empty or to use 'auto' [this feature is not yet available]. Please note that
1804 transformations are inactive as long as no mime-type is selected.</li>
1806 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
1807 hopefully growing amount of pre-defined transformations. See below for information on
1808 how to build your own transformation.<br />
1810 There are global transformations and mimetype-bound transformations. Global transformations
1811 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
1812 Mimetype-bound transformations usually only operate on a certain mimetype. There are
1813 transformations which operate on the main mimetype (like 'image'), which will most likely
1814 take the subtype into regard, and those who only operate on a
1815 specific subtype (like 'image/jpeg').<br />
1817 You can use transformations on mimetypes for which the function was not defined for. There
1818 is no security check for you selected the right transformation, so take care of what the
1819 output will be like.</li>
1821 <li>The field 'Transformation options' is a free-type textfield. You have to enter
1822 transform-function specific options here. Usually the transforms can operate with default
1823 options, but it is generally a good idea to look up the overview to see which options are
1824 necessary.<br />
1826 Much like the ENUM/SET-Fields, you have to split up several options using the format
1827 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
1828 parsed as an array, leaving the first value the first element in the array, and so
1829 forth.<br />
1831 If you want to specify a MIME character set you can define it in the transformation_options.
1832 You have to put that outside of the pre-defined options of the specific mime-transform,
1834 for which you can specify 2 options and you want to append a character set, enter "'first
1835 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
1837 </ul>
1840 <h3>[3. File structure]</h3>
1842 <p>All mimetypes and their transformations are defined through single files in
1843 the directory 'libraries/transformations/'.</p><br />
1845 <p>They are stored in files to ease up customization and easy adding of new
1846 transformations.</p><br />
1848 <p>Because the user cannot enter own mimetypes, it is kept sure that transformations
1849 always work. It makes no sense to apply a transformation to a mimetype, the
1850 transform-function doesn't know to handle.</p><br />
1852 <p>One can, however, use empty mime-types and global transformations which should work
1853 for many mimetypes. You can also use transforms on a different mimetype they where built
1854 for, but pay attention to option usage as well as what the transformation does to your
1855 field.</p><br />
1857 <p>There is a basic file called 'global.inc.php3'. This function can be included by
1858 any other transform function and provides some basic functions.</p><br />
1860 <p>There are 5 possible file names:</p>
1862 <ol>
1863 <li>A mimetype+subtype transform:<br /><br />
1865 [mimetype]_[subtype]__[transform].inc.php3<br /><br />
1867 Please not that mimetype and subtype are separated via '_', which shall not be
1868 contained in their names. The transform function/filename may contain only
1869 characters which cause no problems in the file system as well as the PHP function
1870 naming convention.<br /><br />
1872 The transform function will the be called 'PMA_transform_[mimetype]_[subtype]__[transform]()'.<br /><br />
1874 <b>Example:</b><br /><br />
1876 text_html__formatted.inc.php3<br />
1877 PMA_transform_text_html__formatted()</li>
1879 <li>A mimetype (w/o subtype) transform:<br /><br />
1881 [mimetype]__[transform].inc.php3<br /><br />
1883 Please note that there are no single '_' characters.
1884 The transform function/filename may contain only characters which cause no problems
1885 in the file system as well as the PHP function naming convention.<br /><br />
1887 The transform function will the be called 'PMA_transform_[mimetype]__[transform]()'.<br /><br />
1889 <b>Example:</b><br /><br />
1891 text__formatted.inc.php3<br />
1892 PMA_transform_text__formatted()</li>
1894 <li>A mimetype+subtype without specific transform function<br /><br />
1896 [mimetype]_[subtype].inc.php3<br /><br />
1898 Please note that there are no '__' characters in the filename. Do not use special
1899 characters in the filename causing problems with the file system.<br /><br />
1901 No transformation function is defined in the file itself.<br /><br />
1903 <b>Example:</b><br /><br />
1905 text_plain.inc.php3<br />
1906 (No function)</li>
1908 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
1910 [mimetype].inc.php3<br /><br />
1912 Please note that there are no '_' characters in the filename. Do not use special
1913 characters in the filename causing problems with the file system.<br /><br />
1915 No transformation function is defined in the file itself.<br /><br />
1917 <b>Example:</b><br /><br />
1919 text.inc.php3<br />
1920 (No function)</li>
1922 <li>A global transform function with no specific mimetype<br /><br />
1924 global__[transform].inc.php3<br /><br />
1926 The transform function will the be called 'PMA_transform_global__[transform]()'.<br /><br />
1928 <b>Example:</b><br /><br />
1930 global__formatted<br />
1931 PMA_transform_global__formatted()</li>
1932 </ol>
1934 <br />
1935 <p>So generally use '_' to split up mimetype and subtype, and '__' to provide a
1936 transform function.</p><br />
1938 <p>All filenames containing no '__' in themselves are not shown as valid transform
1939 functions in the dropdown.</p><br />
1941 <p>Please see the libraries/transformations/TEMPLATE file for adding your own transform
1942 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
1943 without a transform function. Also note the introduction of a function description in
1944 the language files. For each function a $strTransformation_[filename without .inc.php3]
1945 has to exist.</p><br />
1947 <p>You can use the template generator to generate new functions and entries in the
1948 language file.</p><br />
1950 <p>To create a new transform function please see libraries/transformations/template_generator.sh.
1951 To create a new, empty mimetype please see libraries/transformations/template_generator_mimetype.sh.</p><br />
1953 <!-- FAQ -->
1955 <h2>FAQ - Frequently Asked Questions</h2>
1957 <p>
1965 </p>
1968 <h3>[1. Server]</h3>
1970 <h4>
1971 [1.1] I'm running PHP 4+ and my server is crashing each time a specific
1972 action is required or phpMyAdmin sends a blank page or a page full of
1973 cryptic characters to my browser, what can I do?
1974 </h4>
1975 <p>
1976 There are some known PHP bugs with output buffering and compression.<br />
1977 Try to set the <tt>$cfg['OBGzip']</tt> directive to <tt>FALSE</tt> in your
1978 <i>config.inc.php or .php3</i> file and the
1979 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
1980 configuration file.<br />
1981 Furthermore, we know about such problems connected to the release
1982 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
1983 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.
1984 </p>
1986 <h4>
1987 [1.2] My Apache server crashes when using phpMyAdmin.
1988 </h4>
1989 <p>
1990 You should first try the latest versions of Apache (and possibly MySQL).
1991 <br />
1992 See also the other FAQ entry about PHP bugs with output buffering.
1993 <br />
1994 If your server keeps crashing, please ask for help in the various
1995 Apache support groups.
1996 </p>
1998 <h4>
2000 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
2001 script: I'm always displayed the login screen.
2002 </h4>
2003 <p>
2004 This is a known PHP bug (see this
2006 official PHP bug database. It means there is and won't be any phpMyAdmin
2007 fix against it because there is no way to code a fix.
2008 </p>
2010 <h4>
2011 [1.4] Using phpMyAdmin on IIS, I'm displayed the error message:
2012 "The specified CGI application misbehaved by not returning a
2013 complete set of HTTP headers...".
2014 </h4>
2015 <p>
2016 You just forgot to read the <i>install.txt</i> file from the php
2017 distribution. Have a look at the last message in this
2019 official PHP bug database.
2020 </p>
2022 <h4>
2023 [1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
2024 messages with the HTTP or advanced authentication mode.
2025 </h4>
2026 <p>
2027 This is a known problem with the PHP ISAPI filter: it's not so stable. For
2028 some more information and complete testings see the messages posted by
2029 André B. aka "djdeluxe76" in
2030 <a href="http://www.phpwizard.net/phorum/read.php?f=1&i=6624&t=6300">this thread</a>
2031 from the phpWizard forum.<br />
2032 Please use instead the cookie authentication mode.
2033 </p>
2035 <h4>
2036 [1.6] I can't use phpMyAdmin on PWS: nothing is displayed!</h4>
2037 <p>
2038 This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2039 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2040 declarations (2 lines) from the scripts <i>header.inc.php3</i>,
2041 <i>header_printview.inc.php3</i>, <i>index.php3</i>, <i>left.php3</i> and
2042 <i>libraries/common.lib.php3</i>.
2043 </p>
2045 <h4>
2046 [1.7] How can I GZip or Bzip a dump or a CSV export. It does not seem to
2047 work.
2048 </h4>
2049 <p>
2050 These features are based on the <tt>gzencode()</tt> and
2051 <tt>bzcompress()</tt> PHP functions to be more independent of the platform
2052 (Unix/Windows, Safe Mode or not, and so on).
2053 So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
2054 (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2055 We faced PHP crashes when trying to download a dump with MS Internet
2056 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2057 this case you should switch to the release version of PHP 4.2.0.
2058 </p>
2060 <h4>
2061 [1.8] I cannot insert a text file in a table, and I get an error about
2062 safe mode being in effect.
2063 </h4>
2064 <p>
2065 Your uploaded file is saved by PHP in the "upload dir", as
2066 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2067 the system default is <i>/tmp</i>).
2068 <br />
2069 We recommend the following setup for Apache servers running in safe mode,
2070 to enable uploads of files while being reasonably secure:
2071 </p>
2072 <ul>
2073 <li>create a separate directory for uploads:
2074 <tt>mkdir /tmp/php</tt></li>
2075 <li>give ownership to the Apache server's user.group:
2076 <tt>chown apache.apache /tmp/php</tt></li>
2077 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2078 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in php.ini</li>
2079 <li>restart Apache</li>
2080 </ul>
2082 <h4>
2083 [1.9] I'm having troubles when uploading files. In general file uploads
2084 don't work on my system and uploaded files have a <tt>Content-Type:</tt>
2085 header in the first line.
2086 </h4>
2087 <p>
2088 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2089 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?
2090 <br />
2091 So the problem is that this package has a serious bug that was corrected
2092 ages ago in PHP (2001-01-28: see
2094 for more details). The problem is that the bugged package is still
2095 available though it was corrected (see
2097 for more details).
2098 <br />
2099 So please download
2100 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2101 and the problem should go away.
2102 <br />
2103 And that fixes the \r\n problem with file uploads!
2104 </p>
2106 <h4>
2107 [1.10] I'm having troubles when uploading files with phpMyAdmin running
2108 on a secure server. My browser is Internet Explorer and I'm using the
2109 Apache server.
2110 </h4>
2111 <p>
2112 As suggested by "Rob M" in the phpWizard forum, add this line to
2113 your <i>httpd.conf</i>:<br />
2114 <tt>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</tt><br />
2115 It seems to clear up many problems between Internet Explorer and SSL.
2116 </p>
2118 <h4>
2119 [1.11] I get an 'open_basedir restriction' while uploading a file from
2120 the query box.
2121 </h4>
2122 <p>
2123 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2124 restrictions. Assuming that the restriction allows you to open files in the
2125 current directory ('.'), all you have to do is create a 'tmp' directory
2126 under the phpMyAdmin install directory, with permissions 777 and the same
2127 owner as the owner of your phpMyAdmin directory. The uploaded files will
2128 be moved there, and after execution of your SQL commands, removed.
2129 </p>
2131 <h4>
2132 [1.12] I have lost my MySQL root password, what can I do?
2133 </h4>
2134 <p>
2135 The MySQL manual explains how to
2137 reset the permissions</a>.
2138 </p>
2140 <h4>
2141 [1.13] I get an error 'No SQL query' when trying to execute a bookmark.
2142 </h4>
2143 <p>
2144 If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2145 cannot access the uploaded query.
2146 </p>
2148 <h4>
2149 [1.14] I get an error 'No SQL query' when trying to submit a query from
2150 the convenient text area.
2151 </h4>
2152 <p>
2153 Check the <tt>post_max_size</tt> directive from your PHP configuration file
2154 and try to increase it.
2155 </p>
2157 <h4>
2158 [1.15] I have problems with <i>mysql.user</i> field names.
2159 </h4>
2160 <p>
2161 In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2162 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2163 names to align with current standards.
2164 </p>
2165 <h4>
2166 [1.16] I cannot upload big dump files.
2167 </h4>
2168 <p>
2169 The first things to check (or ask your host provider to check) are the
2170 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2171 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2172 <br />
2173 All of these three settings limit the maximum size of data that can be
2174 submitted and handled by PHP. One user also said that post_max_size
2175 and memory_limit need to be larger than upload_max_filesize.
2176 </p>
2178 <h4>
2179 [1.17] Does phpMyAdmin support MySQL 4.1?
2180 </h4>
2181 <p>
2182 Because of a major change in the definition syntax of string field types,
2183 this version of phpMyAdmin probably won't work correctly with
2184 MySQL >= 4.1.0! We will work on the support as soon as
2185 MySQL 4.1.0 is released.
2186 </p>
2188 <h4>
2189 [1.18] I'm running MySQL <= 4.0.1 having
2190 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2191 capital letter in its name it is changed to lowercase as it should. But
2192 if I try to DROP this table MySQL is unable to find the corresponding
2193 file.
2194 </h4>
2195 <p>
2196 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2197 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2198 directive.
2199 </p>
2201 <h4>
2202 [1.19] I can't run the "display relations" feature because the
2203 script seems not to know the font face I'm using!
2204 </h4>
2205 <p>
2206 The "FPDF" library we're using for this feature requires some
2207 special files to use font faces.<br />
2208 Please refers to the
2210 these files.
2211 </p>
2214 <h4>
2215 [1.20] I receive the error "cannot load MySQL extension, please
2216 check PHP Configuration".
2217 </h4>
2218 <p>
2219 To connect to a MySQL server, PHP needs a set of MySQL functions called
2220 "MySQL extension".
2221 This extension may be part of the PHP server (compiled-in), otherwise it
2222 needs to be loaded dynamically. Its name is probably <i>mysql.so</i> or
2223 <i>mysql.dll</i>. phpMyAdmin tried to load the extension but failed.
2224 <br /><br />
2225 Usually, the problem is solved by installing a software package called
2226 "PHP-MySQL" or something similar.
2227 </p>
2229 <h4>
2230 [1.21] I am running the CGI version of PHP under Unix, and I cannot
2231 login using cookie auth.
2232 </h4>
2233 <p>
2234 In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.
2235 </p>
2237 <h4>
2238 [1.22] I don't see the "Location of text file" field, so
2239 I cannot upload.
2240 </h4>
2241 <p>
2242 This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2243 parameter is not set to "on".
2244 </p>
2246 <h4>
2247 [1.23] I'm running MySQL on a Win32 machine. Each time I create a new
2248 table the table and field names are changed to lowercase!
2249 </h4>
2250 <p>
2251 This happens because the MySQL directive <tt>lower_case_table_names</tt>
2252 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2253 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2254 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2255 directory and add the following line to the group [mysqld]:<br />
2256 <tt>set-variable = lower_case_table_names=0</tt><br />
2257 Next, save the file and restart the MySQL service. You can always check the
2258 value of this directive using the query<br />
2259 <tt>SHOW VARIABLES LIKE 'lower_case_table_names';</tt>
2260 </p>
2262 <h4>
2263 [1.24] Some characters are being truncated in my queries, or I get
2264 characters randomly added. I am running PHP 4.2.3.
2265 </h4>
2266 <p>
2267 This is a
2269 </p>
2271 <h4>
2272 [1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
2273 and I get problems, such as undefined variables when I run a SQL query.
2274 </h4>
2275 <p>
2276 A tip from Jose Fandos: put a comment on the following two lines
2277 in httpd.conf, like this:<br />
2278 <tt># mod_gzip_item_include file \.php$</tt><br />
2280 as this version of mod_gzip on Apache (Windows) has problems handling
2281 PHP scripts. Of course you have to restart Apache.
2282 </p>
2284 <h4>
2285 [1.26] I just installed phpMyAdmin in my document root of IIS but
2286 I get the error "No input file specified" when trying to
2287 run phpMyAdmin.
2288 </h4>
2289 <p>
2290 This is a permission problem. Right-click on the phpmyadmin folder
2291 and choose properties. Under the tab Security, click on "Add"
2292 and select the user "IUSER_machine" from the list. Now set his
2293 permissions and it should work.
2294 </p>
2296 <h4>
2297 [1.27] I get empty page when I want to view huge page (eg.
2298 db_details_structure.php3 with plenty of dabases).
2299 </h4>
2300 <p>
2302 GZIP output buffering enabled. If you turn off it (by <code>$cfg['OBGzip']
2303 = FALSE</code> in config.inc.php3), it should work. This bug will be fixed
2304 in PHP 5.0.0.
2305 </p>
2307 <h4>
2308 [1.28] My MySQL server sometimes refuses queries and returns the message
2309 'Errorcode: 13'. What does this mean?
2310 </h4>
2311 <p>
2312 This can happen due to a MySQL bug when having database / table names with
2313 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2314 To fix this, turn off this directive, convert all database and table names
2315 to lower case and turn it on again. Alternatively, there's a bug-fix
2316 available starting with MySQL 3.23.56 / 4.0.11-gamma.
2317 </p>
2320 <h4>
2321 [1.29] When I create a table or modify a field, I get an error
2322 and the fields are duplicated.
2323 </h4>
2324 <p>
2325 It is possible to configure Apache in such a way that PHP has problems
2326 interpreting .php files.
2327 <br /><br />
2328 The problems occur when two different (and conflicting) set of directives
2329 are used:
2330 <br /><br />
2331 <tt>
2332 SetOutputFilter PHP<br />
2333 SetInputFilter PHP<br />
2334 </tt>
2335 &
2336 <br />
2337 <tt>
2338 AddType application/x-httpd-php .php
2339 </tt>
2340 <br /><br />
2341 In the case we saw, one set of directives was in <tt>httpd.conf</tt>, while
2342 the other set was in <tt>php.conf</tt>.<br />
2343 The recommended way is with <tt>AddType</tt>, so just comment out
2344 the first set of lines and restart Apache:
2345 <br /><br />
2346 <tt><b>
2347 #SetOutputFilter PHP<br />
2348 #SetInputFilter PHP<br /></b>
2349 </tt>
2350 </p>
2353 <h3>[2. Configuration]</h3>
2355 <h4>
2356 [2.1] The error message "Warning: Cannot add header information -
2357 headers already sent by ..." is displayed, what's the problem?
2358 </h4>
2359 <p>
2360 Edit your <i>config.inc.php or .php3</i> file and ensure there is nothing
2361 (I.E. no blank lines, no spaces, no characters...) neither before the
2362 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2363 tag at the end.
2364 </p>
2366 <h4>
2367 [2.2] phpMyAdmin can't connect to MySQL. What's wrong?
2368 </h4>
2369 <p>
2370 Either there is an error with your PHP setup or your username/password is
2371 wrong. Try to make a small script which uses mysql_connect and see if it
2372 works. If it doesn't, it may be you haven't even compiled MySQL support
2373 into PHP.
2374 </p>
2376 <h4>
2377 [2.3] The error message "Warning: MySQL Connection Failed: Can't
2378 connect to local MySQL server through socket '/tmp/mysql.sock'
2379 (111)..." is displayed. What can I do?
2380 </h4>
2381 <p><br />
2382 For RedHat users, Harald Legner suggests this on the mailing list:
2383 <br /><br />
2384 On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2385 In your php.ini you will find a line
2386 <br />
2387 <tt>mysql.default_socket = /tmp/mysql.sock</tt>
2388 <br />
2389 change it to
2390 <br />
2391 <tt>mysql.default_socket = /var/lib/mysql/mysql.sock</tt>
2392 <br />
2393 Then restart apache and it will work.
2394 <br /><br />
2395 Here is a fix suggested by Brad Ummer in the phpwizard forum:
2396 </p>
2397 <ul>
2398 <li>
2399 First, you need to determine what socket is being used by MySQL.
2400 <br />
2401 To do this, telnet to your server and go to the MySQL bin directory. In
2402 this directory there should be a file named <i>mysqladmin</i>. Type
2403 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2404 info about your MySQL server, including the socket
2405 (<i>/tmp/mysql.sock</i>, for example).
2406 </li>
2407 <li>
2408 Then, you need to tell PHP to use this socket.<br />Assuming you are
2409 using PHP 3.0.10 or better, you can specify the socket to use when you
2410 open the connection. To do this in phpMyAdmin, you need to complete the
2411 socket information in the config.inc.php3.<br />
2412 For example:
2413 <tt>$cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</tt><br /><br />
2414 Please also make sure that the permissions of this file allow to be readable
2415 by your webserver (i.e. '0755').
2416 </li>
2417 </ul>
2418 <p>
2419 Have also a look at the
2421 corresponding section of the MySQL documentation</a>.
2422 </p>
2424 <h4>
2425 [2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
2426 what can I do?
2427 </h4>
2428 <p>
2429 Try to set the <tt>$cfg['OBGZip']</tt> directive to <tt>FALSE</tt> in the
2430 phpMyAdmin configuration file. It helps sometime.<br />
2431 Also have a look at your PHP version number: if it contains
2432 "4.0b..." it means you're running a beta version of PHP. That's
2433 not a so good idea, please upgrade to a plain revision.
2434 </p>
2436 <h4>
2437 [2.5] Each time I want to insert or change a record or drop a database
2438 or a table, an error 404 (page not found) is displayed or, with HTTP or
2439 cookie authentication, I'm asked to login again. What's wrong?
2440 </h4>
2441 <p>
2442 Check the value you set for the <tt>$cfg['PmaAbsoluteUri']</tt> directive
2443 in the phpMyAdmin configuration file.
2444 </p>
2446 <h4>
2447 [2.6] I get an "Access denied for user: 'root@localhost' (Using
2448 password: YES)"-error when trying to access a MySQL-Server on a
2449 host which is port-forwarded for my localhost
2450 </h4>
2451 <p>
2452 When you are using a port on your localhost, which you redirect via
2453 port-forwarding to another host, MySQL is not resolving the localhost
2454 as expected.<br />
2455 Erik Wasser explains: The solution is: if your host is "localhost"
2456 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2457 connection for speeding up things. And that doesn't work in this configuration
2458 with port forwarding.<br />
2460 TCP connection.
2461 </p>
2465 <h3>[3. Known limitations]</h3>
2467 <h4>
2468 [3.1] When using HTTP authentication, an user who logged out can not
2469 relogin in with the same nick.
2470 </h4>
2471 <p>
2472 This is related to the authentication mechanism (protocol) used by
2473 phpMyAdmin. We plan to change it as soon as we may find enough free time
2474 to do it, but you can bypass this problem: just close all the opened
2475 browser windows and then go back to phpMyAdmin. You should be able to
2476 log in again.
2477 </p>
2479 <h4>
2480 [3.2] When dumping a large table in compressed mode, I get a memory
2481 limit error or a time limit error.
2482 </h4>
2483 <p>
2484 As of version 2.2.4, we build the compressed dump in memory, so large
2485 tables dumps may hang. The only alternative we can think about (using
2486 system calls to mysqldump then gzip or bzip2) would not be applicable in
2487 environments where PHP is in safe mode: access to system programs is
2488 is limited by the system administrator, and time limit is enforced.
2489 </p>
2491 <h4>
2492 [3.3] With InnoDB tables, I lose foreign key relationships when I rename
2493 or alter a table.
2494 </h4>
2495 <p>
2496 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in
2497 mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
2498 </p>
2500 <h4>
2501 [3.4] I am unable to import dumps I created with the mysqldump tool
2502 bundled with the MySQL server distribution.
2503 </h4>
2504 <p>
2505 The problem is that mysqldump creates invalid comments like this:
2506 </p>
2507 <pre>
2508 -- MySQL dump 8.22
2509 --
2510 -- Host: localhost Database: database
2511 ---------------------------------------------------------
2512 -- Server version 3.23.54
2513 </pre>
2514 <p>
2515 The invalid part of the code is the horizontal line made of dashes that
2516 appears once in every dump created with mysqldump. If you want to run your
2517 dump you have to turn it into valid MySQL. This means, you have to add a
2518 whitespace after the first to dashes of the line or add a # before it:
2519 <br />
2520 <code>
2521 -- -------------------------------------------------------<br />
2522 </code>
2523 or<br />
2524 <code>
2525 #---------------------------------------------------------
2526 </code>
2527 </p>
2529 <h4>
2530 [3.3] When using nested folders ($cfg['LeftFrameTableSeparator']) there
2531 are some multiple hierarchies displayed in a wrong manner?!
2532 </h4>
2533 <p>
2534 Please note that you should not use the seperating string multiple times
2535 without any characters between them, or at the beginning/end of your table
2536 name. If you have to, think about using another TableSeparator or disabling
2537 that feature
2538 </p>
2541 <h3>[4. ISPs, multi-user installations ]</h3>
2543 <h4>
2544 [4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
2545 need to install it for each customer.
2546 </h4>
2547 <p>
2548 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
2549 your users. The development of this feature was kindly sponsored by
2550 NetCologne GmbH.
2551 This requires a properly setup MySQL user management and phpMyAdmin
2552 HTTP or cookie authentication. See the install section on
2553 "Using HTTP authentication".
2554 </p>
2556 <h4>
2557 [4.2] What's the preferred way of making phpMyAdmin secure against evil
2558 access.
2559 </h4>
2560 <p>
2561 This depends on your system.<br />
2562 If you're running a server which cannot be accessed by other people, it's
2563 sufficient to use the directory protection bundled with your webserver
2564 (with Apache you can use <i>.htaccess</i> files, for example).<br />
2565 If other people have telnet access to your server, you should use
2566 phpMyAdmin's HTTP authentication feature.
2567 <br /><br />
2568 Suggestions:
2569 </p>
2570 <ul>
2571 <li>
2572 Your <i>config.inc.php3</i> file should be <tt>chmod 660</tt>.
2573 </li>
2574 <li>
2575 All your phpMyAdmin files should be chown phpmy.apache, where phpmy
2576 is a user whose password is only known to you, and apache is the
2577 group under which Apache runs.
2578 </li>
2579 <li>
2580 You should use PHP safe mode, to protect from other users that try
2581 to include your <i>config.inc.php3</i> in their scripts.
2582 </li>
2583 </ul>
2585 <h4>
2586 [4.3] I get errors about not being able to include a file in
2587 <i>/lang</i> or in <i>/libraries</i>.
2588 </h4>
2589 <p>
2590 Check <i>php.ini</i>, or ask your sysadmin to check it. The
2591 <tt>include_path</tt> must contain "." somewhere in it, and
2592 <tt>open_basedir</tt>, if used, must contain "." and
2593 "./lang" to allow normal operation of phpMyAdmin.
2594 </p>
2595 <h4>
2596 [4.4] phpMyAdmin always gives "Access denied" when using HTTP
2597 authentication.
2598 </h4>
2599 <p>
2600 This could happen for several reasons:
2601 </p>
2602 <ul>
2603 <li>
2604 <tt>$cfg['Servers'][$i]['controluser']</tt> and/or
2605 <tt>$cfg['Servers'][$i]['controlpass']</tt> are wrong.
2606 </li>
2607 <li>
2608 The username/password you specify in the login-dialog are invalid.
2609 </li>
2610 <li>
2611 You have already setup a security mechanism for the
2612 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
2613 phpMyAdmin's authentication, so remove it.
2614 </li>
2615 </ul>
2617 <h4>
2618 [4.5] Is it possible to let users create their own databases?
2619 </h4>
2620 <p>
2621 Starting with 2.2.5, in the user management page, you can enter a wildcard
2622 database name for a user (for example "joe%"),
2623 and put the privileges you want. For example,
2624 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
2625 would let a user create/manage his/her database(s).
2626 </p>
2628 <h4>
2629 [4.6] How can I use the Host-based authentication additions?
2630 </h4>
2631 <p>
2632 If you have existing rules from an old .htaccess file, you can take them
2633 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
2634 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
2635 be a major benefit here if your installation is suited to using it. Then
2636 you can just add those updated lines into the
2637 <tt>$cfg['Servers'][$i]['AllowDeny']['rules']</tt> array.
2638 <br /><br />
2639 If you want a pre-made sample, you can try this fragment. It stops the
2640 'root' user from logging in from any networks other than the private
2641 network IP blocks.
2642 <br />
2643 <tt>
2644 //block root from logging in except from the private networks<br />
2645 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';<br />
2646 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(<br />
2647 'deny root from all',<br />
2648 'allow root from localhost',<br />
2649 'allow root from 10.0.0.0/8',<br />
2650 'allow root from 192.168.0.0/16',<br />
2651 'allow root from 172.16.0.0/12',<br />
2652 );
2653 </tt>
2654 </p>
2655 <h4>
2656 [4.7] Authentication window is displayed more than once, why?
2657 </h4>
2658 <p>
2659 This happens if you are using a URL to start phpMyAdmin which is
2660 different than the one set in your <tt>$cfg['PmaAbsoluteUri']</tt>.
2661 For example, a missing "www", or entering with an IP address
2662 while a domain name is defined in the config file.
2663 </p>
2666 <h3>[5. Browsers or client OS]</h3>
2668 <h4>
2669 [5.1] I get an out of memory error, and my controls are non-functional,
2670 when trying to create a table with more than 14 fields.
2671 </h4>
2672 <p>
2673 We could reproduce this problem only under Win98/98SE. Testing under
2674 WinNT4 or Win2K, we could easily create more than 60 fields.
2675 <br />
2676 A workaround is to create a smaller number of fields, then come back to
2677 your table properties and add the other fields.
2678 </p>
2680 <h4>
2681 [5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.
2682 </h4>
2683 <p>
2684 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
2685 with each script/website that use forms.<br />
2686 Upgrade or downgrade your Xitami server.
2687 </p>
2689 <h4>
2690 [5.3] I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).
2691 </h4>
2692 <p>
2693 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
2694 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
2695 don't seem to work.<br />
2697 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
2698 the user's temporary directory, so they must be moved before closing
2699 Konqueror, or else they disappear. GZip dumps give an error message.<br />
2701 Testing needs to be done for Konqueror 2.2.2.<br />
2702 </p>
2704 <h4>
2705 [5.4] I can't use the cookie authentication mode because Internet
2706 Explorer never stores the cookies.
2707 </h4>
2708 <p>
2709 MS Internet Explorer seems to be really buggy about cookies, at least till
2710 version 6. And thanks to Andrew Zivolup we've traced also a PHP 4.1.1 bug
2711 in this area!
2712 <br />
2713 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
2714 work!
2715 </p>
2717 <h4>
2718 [5.5] In Internet Explorer 5.0, I get JavaScript errors when browsing my
2719 rows.
2720 </h4>
2721 <p>
2722 Upgrade to at least Internet Explorer 5.5 SP2.<br />
2723 </p>
2725 <h4>
2727 when trying to modify a row in a table with many fields, or with a text field
2728 </h4>
2729 <p>
2730 Your table neither have a primary key nor an unique one, so we must use a
2731 long URL to identify this row. There is a limit on the length of the URL in
2732 those browsers, and this not happen in Netscape, for example. The
2733 workaround is to create a primary or unique key, or use another browser.
2734 <br />
2735 </p>
2737 <h4>
2738 [5.7] I refresh (reload) my browser, and come back to the welcome
2739 page.
2740 </h4>
2741 <p>
2742 Some browsers support right-clicking into the frame you want to refresh,
2743 just do this in the right frame.<br />
2744 </p>
2746 <h4>
2747 [5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
2748 query box.
2749 </h4>
2750 <p>
2751 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
2752 Mozilla versions.<br />
2753 </p>
2755 <h4>
2756 [5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
2757 whitespace in the SQL-Query edit area: the page scrolls down.
2758 </h4>
2759 <p>
2760 This is a Mozilla bug (see bug #26882 at
2762 </p>
2764 <h4>
2765 [5.10] With Netscape 4.75 I get empty rows between each row of data in a
2766 CSV exported file.
2767 </h4>
2768 <p>
2769 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
2770 data in octet-stream mode. Since we can't detect the specific Netscape
2771 version, we cannot workaround this bug.
2772 </p>
2774 <h4>
2775 [5.11] Extended-ASCII characters like German umlauts are displayed
2776 wrong.
2777 </h4>
2778 <p>
2779 Please ensure that you have set your browser's character set to the one of the
2780 language file you have selected on phpMyAdmin's start page.
2781 Alternatively, you can try the auto detection mode that is supported by the
2782 recent versions of the most browsers.
2783 </p>
2785 <h4>
2786 [5.12] Apple OS X: Safari browser changes special characters to
2787 "?".
2788 </h4>
2789 <p>
2790 This issue has been reported by a OS X user, who adds that Chimera,
2791 Netscape and Mozilla do not have this problem.
2792 </p>
2794 <h4>
2795 [5.13] With Internet Explorer 5.5 or 6, and HTTP authentication type,
2796 I cannot manage two servers: I login to the first one, then the other one,
2797 but if I switch back to the first, I have to login on each operation.
2798 </h4>
2799 <p>
2800 This is a bug in Internet Explorer, other browsers do not behave this way.
2801 </p>
2803 <h4>
2804 [5.14] Using Opera6, I can manage to get to the authentification, but nothing
2805 happens after that, only a blank screen.
2806 </h4>
2807 <p>
2808 Having $cfg['QueryFrameJS'] set to TRUE, this leads to a bug in Opera6, because it
2809 is not able to interpret frameset definitiions written by JavaScript. Please upgrade
2810 to Opera7 at least.
2811 </p>
2814 <h3>[6. Using phpMyAdmin]</h3>
2816 <h4>
2817 [6.1] I can't insert new rows into a table / I can't create a table
2818 - MySQL brings up a SQL-error.
2819 </h4>
2820 <p>
2821 Examine the SQL error with care. Often the problem is caused by
2822 specifying a wrong field-type.<br />
2823 Common errors include:
2824 </p>
2825 <ul>
2826 <li>Using <tt>VARCHAR</tt> without a size argument</li>
2827 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
2828 </ul>
2829 <p>
2830 Also, look at the syntax chapter in the MySQL manual to confirm that your
2831 syntax is correct.
2832 </p>
2834 <h4>
2835 [6.2] When I create a table, I click the Index checkbox for 2 fields and
2836 phpMyAdmin generates only one index with those 2 fields.
2837 </h4>
2838 <p>
2839 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
2840 index. If you want two indexes, create the first one when creating the
2841 table, save, then display the table properties and click the Index link to
2842 create the other index.
2843 </p>
2845 <h4>
2846 [6.3] How can I insert a null value into my table?
2847 </h4>
2848 <p>
2849 Since version 2.2.3, you have a checkbox for each field that can be null.
2850 Before 2.2.3, you had to enter "null", without the quotes, as the
2851 field's value.
2852 </p>
2854 <h4>
2855 [6.4] How can I backup my database or table?
2856 </h4>
2857 <p>
2858 Click on a database or table name in the left frame, the properties will be
2859 displayed. Then on the menu, click "Export", you can dump
2860 the structure, the data, or both. This will generate standard SQL
2861 statements that can be used to recreate your database/table.
2862 <br /><br />
2863 You will need to choose "Save as file", so that phpMyAdmin can
2864 transmit the resulting dump to your station. Depending on your PHP
2865 configuration, you will see options to compress the dump. See also the
2866 <tt>$cfg['ExecTimeLimit']</tt> configuration variable.
2867 <br /><br />
2868 For additional help on this subject, look for the word "dump" in
2869 this document.
2870 </p>
2872 <h4>
2873 [6.5] How can I restore (upload) my database or table using a dump?
2874 How can I run a ".sql" file.
2875 </h4>
2876 <p>
2877 Click on a database name in the left frame, the properties will be
2878 local displayed. Then in the "Run SQL query" section, type in
2879 your dump filename, or use the Browse button. Then click Go.
2880 <br /><br />
2881 For additional help on this subject, look for the word "upload"
2882 in this document.
2883 </p>
2885 <h4>
2886 [6.6] How can I use the relation table in Query-by-example?
2887 </h4>
2888 <p>
2889 Here is an example with the tables persons, towns and countries, all
2890 located in the database mydb. If you don't have a <tt>PMA_relation</tt>
2891 table, create it as explained in the configuration section. Then create the
2892 example tables:
2893 <br /><br />
2894 <tt>
2895 CREATE TABLE REL_countries (<br />
2896 country_code char(1) NOT NULL default '',<br />
2897 description varchar(10) NOT NULL default '',<br />
2898 PRIMARY KEY (country_code)<br />
2899 ) TYPE=MyISAM;<br />
2900 <br />
2901 INSERT INTO REL_countries VALUES ('C', 'Canada');<br />
2902 <br />
2903 CREATE TABLE REL_persons (<br />
2904 id tinyint(4) NOT NULL auto_increment,<br />
2905 person_name varchar(32) NOT NULL default '',<br />
2906 town_code varchar(5) default '0',<br />
2907 country_code char(1) NOT NULL default '',<br />
2908 PRIMARY KEY (id)<br />
2909 ) TYPE=MyISAM;<br />
2910 <br />
2911 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');<br />
2912 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');<br />
2913 <br />
2914 CREATE TABLE REL_towns (<br />
2915 town_code varchar(5) NOT NULL default '0',<br />
2916 description varchar(30) NOT NULL default '',<br />
2917 PRIMARY KEY (town_code)<br />
2918 ) TYPE=MyISAM;<br />
2919 <br />
2920 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');<br />
2921 INSERT INTO REL_towns VALUES ('M', 'Montréal');<br />
2922 <br />
2923 </tt>
2924 To setup appropriate links and display information:
2925 </p>
2926 <ul>
2927 <li>on table "REL_persons" click Structure, then Relation view</li>
2928 <li>in Links, for "town_code" choose "REL_towns->code"</li>
2929 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
2930 <li>on table "REL_towns" click Structure, then Relation view</li>
2931 <li>in "Choose field to display", choose "description"</li>
2932 <li>repeat the two previous steps for table "REL_countries"</li>
2933 </ul>
2935 <p>
2936 Then test like this:
2937 </p>
2938 <ul>
2939 <li>Click on your db name in the left frame</li>
2940 <li>Choose "Query"</li>
2941 <li>Use tables: persons, towns, countries</li>
2942 <li>Click "Update query"</li>
2943 <li>In the fields row, choose persons.person_name and click the
2944 "Show" tickbox </li>
2945 <li>Do the same for towns.description and countries.descriptions in the
2946 other 2 columns</li>
2947 <li>Click "Update query" and you will see in the query box that
2948 the correct joins have been generated</li>
2949 <li>Click "Submit query"</li>
2950 </ul>
2951 <br />
2954 <h4>
2955 [6.7] How can I use the "display field" feature?
2956 </h4>
2957 <p>
2958 Starting from the previous example, create the PMA_table_info as explained
2959 in the configuration section, then browse your persons table,
2960 and move the mouse over a town code or country code.
2961 </p>
2964 <h4>
2965 [6.8] How can I produce a PDF schema of my database?
2966 </h4>
2967 <p>
2968 First you have to fill the "relation", "table_coords"
2969 and "pdf_pages" configuration variables.
2970 <br /><br />
2971 Then, think about your schema layout: which tables will go on which pages.
2972 </p>
2973 <ul>
2974 <li>Click on your db name in the left frame</li>
2975 <li>Choose "Structure" in the navigation on top</li>
2976 <li>Choose "Edit PDF Pages" which should be somewhere at the
2977 bottom of the page</li>
2978 <li>Enter the name for a first pdf page and submit</li>
2979 <li>Choose this page to edit</li>
2980 <li>Now add a table you want to show on this page and it's coordinates and
2981 submit<br />
2982 First you will have to guess this coordinates of course, so just expect
2983 to have an area of about 297 * 210 and put the tables coordinates
2984 somewhere in there, you will be able to have a look at what happened
2985 and change them later.<br />
2986 For example, x=100 and y=200 means that the table will be at 200 mm
2987 down and 100 mm right from the upper left corner.<br />
2988 Actually if you have a width of more than 300 or a height of more than
2989 200 than it will automatically be scaled but 300*100 is a good start to
2990 have an idea of what coordinates to use.</li>
2991 <li>After every table you submitted you will have the possibility to submit
2992 more tables</li>
2993 <li>When you have entered enough tables Click on your db name in the left
2994 frame again</li>
2995 <li>Now, again at the bottom of the page you should be able to choose
2996 "Display PDF schema"<br />
2997 For testing it might be useful to show the grid as well, so you can see
2998 the coordinates used.<br />
2999 Maybe also choose color and submit.</li>
3000 <li>Save the file he will offer you to something like <i>Schema.pdf</i>
3001 (Internet Explorer has some bug there which might make it offer it
3002 without an extension. Under Windows it is important to have the
3003 extension ".pdf", under other OSes you should be fine just
3004 saving the file under the name it offers).</li>
3005 </ul>
3007 <h4>
3008 [6.9] phpMyAdmin is changing the type of one of my columns!
3009 </h4>
3010 <p>
3011 No, it's MySQL that is doing
3012 <a href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent column type changing</a>.
3013 </p>
3016 <h4>
3017 [6.10] When creating a privilege, what happens with underscores in
3018 the database name?
3019 </h4>
3020 <p>
3021 If you do not put a backslash before the underscore, this is a wildcard
3022 grant, and the underscore means "any character". So, if the
3023 database name is "john_db", the user would get rights to john1db,
3024 john2db...<br /><br />
3025 If you put a backslash before the underscore, it means that the database
3026 name will have a real underscore.
3027 </p>
3029 <h4>
3030 [6.11] What is the curious symbol ø in the statistics pages?
3031 </h4>
3032 <p>
3033 It means "average".
3034 </p>
3037 <h4>
3038 [6.12] I want to understand some Export options.
3039 </h4>
3040 <p>
3041 "Complete inserts" adds the column names on every INSERT command,
3042 for better documentation (but resulting file is bigger).<br />
3043 "Extended inserts" provides a shorter dump file by using only
3044 once the INSERT verb and the table name.<br />
3045 "Enclose table and field names with backquotes" ensures that
3046 field and table names formed with special characters are protected.<br />
3047 "Include column comments as inline SQL-comments" includes any
3048 column comments set in the PMA-DB in the dump as SQL comments (<i>/* xxx */</i>).<br /></p>
3050 <h4>
3051 [6.13] I would like to create a database with a dot in its name.
3052 </h4>
3053 <p>
3054 This is a bad idea, because in MySQL the syntax "database.table"
3055 is the normal way to reference a database and table name. Worse, MySQL
3056 will usually let you create a database with a dot, but then you cannot
3057 work with it, nor delete it.<br />
3058 </p>
3061 <h4>
3062 [6.14] How do I set up the SQL Validator?
3063 </h4>
3064 <p>
3065 To use it, you need a very recent version of PHP, 4.3.0 recommended, with
3066 XML, PCRE and PEAR support. On your system command line, run
3067 <tt>"pear install Net_Socket Net_URL HTTP_Request Mail_Mime Net_DIME
3068 SOAP"</tt> to get the necessary PEAR modules for usage.
3069 <br />
3070 If you use it, you should be aware that any SQL statement you
3071 submit will be stored anonymously (database/table/column names,
3072 strings, numbers replaced with generic values). The Mimer SQL
3073 Validator itself, is © 2001 Upright Database Technology.
3074 We utilize it as free SOAP service.
3075 </p>
3077 <h4>
3078 [6.15] I want to add a BLOB field and put an index on it, but MySQL
3079 says "BLOB column '...' used in key specification without a key
3080 length".
3081 </h4>
3082 <p>
3083 The right way to do this, is to create the field without any indexes,
3084 then display the table structure and use the "Create an index"
3085 dialog. On this page, you will be able to choose your BLOB field, and
3086 set a size to the index, which is the condition to create an index on
3087 a BLOB field.
3088 <br />
3089 </p>
3091 <h4>
3092 [6.16] How can I simply move in page with plenty editing fields?
3093 </h4>
3094 <p>
3095 You can use Ctrl+arrows for moving on most pages with plenty editing
3096 fields (table structure changes, row editing, etc.) (must be anabled in
3097 configuration - see. $cfg['CtrlArrowsMoving']). You can also have a look
3098 at the directive $cfg['DefaultPropDisplay'] ('vertical') and see if this
3099 eases up editing for you.
3100 <br />
3101 </p>
3103 <h4>
3104 [6.17] Transformations: I can't enter my own mimetype! WTF is this feature
3105 then useful for?
3106 </h4>
3107 <p>
3108 Slow down :). Defining mimetypes is of no use, if you can't put transformations on them.
3109 Otherwise you could just put a comment on the field. Because entering your own mimetype will
3110 cause serious syntax checking issues and validation, this introduces a high-risk false-user-input
3111 situation. Instead you have to initialize mimetypes using functions or empty mimetype definitions.
3112 <br />
3113 Plus, you have a whole overview of available mimetypes. Who knows all those mimetypes by heart so
3114 he/she can enter it at will?
3115 <br />
3116 </p>
3119 <h4>
3120 [6.17] Bookmarks: Where can I store bookmarks? Why can't I see any bookmarks below the query box?
3121 What is this variable for?
3122 </h4>
3123 <p>
3124 Any query you have executed can be stored as a bookmark on the page where the results are displayed.
3125 You will find a button labeled 'Bookmark this query' just at the end of the page.<br />
3126 As soon as you have stored a bookmark, it is related to the database you run the query on. You can
3127 now access a bookmark dropdown on each page, the query box appears on for that database.<br />
3128 <br />
3129 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks. Just use the string
3130 <b>/*[VARIABLE]*/</b> anywhere in your query. Everything which is put into the <i>value</i> input
3131 box on the query box page will replace the string "/*[VARIABLE]*/" in your stored query.
3132 Just be aware of that you HAVE to create a valid query, otherwise your query won't be even able to be
3133 stored in the database.<br />
3134 Also remember, that everything else inside the <b>/*[VARIABLE]*/</b> string for your query will remain
3135 the way it is, but will be stripped of the /**/ chars. So you can use:<br /><br />
3136 <code>/*, [VARIABLE] AS myname */</code><br /><br />
3137 which will be expanded to<br /><br />
3138 <code>, VARIABLE as myname</code><br /><br />
3139 in your query, where VARIABLE is the string you entered in the input box. If an empty string is
3140 provided, no replacements are made.<br />
3141 <br />
3142 A more complex example. Say you have stored this query:<br /><br />
3143 <code>SELECT Name, Address FROM addresses WHERE 1 /* AND Name LIKE '%[VARIABLE]%' */</code><br /><br />
3144 Say, you now enter "phpMyAdmin" as the variable for the stored query, the full query will
3145 be:<br /><br />
3146 <code>SELECT Name, Address FROM addresses WHERE 1 AND Name LIKE '%phpMyAdmin%'</code>
3147 <br />
3148 <br />
3149 You can use multiple occurences of <b>/*[VARIABLE]*/</b> in a single query.<br />
3150 <b>NOTE THE ABSENCE OF SPACES</b> inside the "/**/" construct. Any spaces inserted there
3151 will be later also inserted as spaces in your query and may lead to unexpected results especially when
3152 using the variable expansion inside of a "LIKE ''" expression.<br />
3153 Your initial query which is going to be stored as a bookmark has to yield at least one result row so
3154 you can store the bookmark. You may have that to work around using well positioned "/**/"
3155 comments.
3156 </p>
3159 <h3>[7. phpMyAdmin project]</h3>
3161 <h4>
3162 [7.1] I have found a bug. How do I inform developers?
3163 </h4>
3164 <p>
3165 Our Bug Tracker is located at
3166 <a href="http://sourceforge.net/projects/phpmyadmin/">http://sourceforge.net/projects/phpmyadmin/</a>
3167 under the Bugs section.
3168 <br /><br />
3169 But please first discuss your bug with other users:
3170 <br />
3172 http://sourceforge.net/projects/phpmyadmin/</a> (and choose Forums)
3173 </p>
3175 <h4>
3176 [7.2] I want to translate the messages to a new language or upgrade an
3177 existing language, where do I start?
3178 </h4>
3179 <p>
3180 Always use the current CVS version of your language file.
3181 For a new language, start from <i>english-iso-8859-1.inc.php3</i>. If you
3182 don't know how to get the CVS version, please ask one of the developers.
3183 <br />
3184 Please note that we try not to use HTML entities like &eacute; in
3185 the translations, since we define the right character set in the file.
3186 With HTML entities, the text on JavaScript messages would not
3187 display correctly.
3188 However there are some entities that need to be there, for quotes
3189 ,non-breakable spaces, ampersands, less than, greater than.
3190 <br />
3191 You can then put your translations, as a zip file to avoid losing special
3192 characters, on the sourceforge.net translation tracker.
3193 <br />
3194 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3195 list, because this is where we ask for translations of new messages.
3196 <br />
3197 </p>
3199 <h4>
3200 [7.3] I would like to help out with the development of phpMyAdmin. How
3201 should I proceed?
3202 </h4>
3203 <p>
3204 The following method is preferred for new developers:
3205 </p>
3206 <ol>
3207 <li>
3208 fetch the current CVS tree over anonymous CVS:<br />
3209 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
3210 [Password: simply press the Enter key]<br />
3211 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
3212 [This will create a new sub-directory named phpMyAdmin]
3213 </li>
3214 <li>
3215 add your stuff
3216 </li>
3217 <li>
3218 put the modified files (tar'ed and gzip'ed) inside the patch tracker of
3219 the
3220 <a href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">phpMyAdmin SourceForge account</a>.
3221 </li>
3222 </ol>
3223 <p>
3224 Write access to the CVS tree is granted only to experienced developers who
3225 have already contributed something useful to phpMyAdmin.<br />
3226 Also, have a look at the
3228 </p>
3230 <!-- DEVELOPERS -->
3232 <h2>Developers Information</h2>
3234 <p>
3235 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3236 great features have been written by other people and you too can help to
3237 make phpMyAdmin a useful tool.
3238 </p>
3240 <p>
3241 If you're planning to contribute source, please read the following
3242 information:
3243 </p>
3244 <ul>
3245 <li>
3246 All files include <i>header.inc.php3</i> (layout),
3247 <i>libraries/common.lib.php3</i> (common functions) and
3248 <i>config.inc.php3</i>.
3249 <br />
3250 All configuration data belongs in <i>config.inc.php3</i>. Please keep
3251 it free from other code.
3252 <br />
3253 Commonly used functions should be added to
3254 <i>libraries/common.lib.php3</i> and more specific ones may be added
3255 within a library stored into the <i>libraries</i> sub-directory.
3256 </li>
3257 <li>
3258 Obviously, you're free to use whatever coding style you want. But
3259 please try to keep your code as simple as possible: beginners are
3260 using phpMyAdmin as an example application.<br />
3261 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3262 compliant on one hand, they fit the
3264 on the other hand. Please pay attention to this.
3265 </li>
3266 <li>
3267 Please try to keep up the file-naming conventions. Table-related stuff
3268 goes to <i>tbl_*.php3</i>, db-related code to <i>db_*.php3</i>,
3269 server-related tools to <i>server_*.php3</i> and so on.
3270 </li>
3271 <li>
3272 Please don't use verbose strings in your code, instead add the string
3273 (at least) to <i>english-iso-8859-1.inc.php3</i> and print() it out.
3274 </li>
3275 <li>
3276 If you want to be really helpful, write an entry for the ChangeLog.
3277 </li>
3280 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3281 better debug and profile their code.<br />
3282 Please see the <tt>$cfg['DBG']*</tt> configuration options for more
3283 information.<br />
3284 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3285 lost during its re-entry into Earth's atmosphere and in memory of the
3286 brave men and women who gave their lives for the people of Earth.
3287 </li>
3289 </ul>
3291 <!-- CREDITS -->
3293 <h2>Credits</h2>
3295 <pre>
3297 phpMyAdmin - Credits
3298 ====================
3300 CREDITS, in chronological order
3301 -------------------------------
3303 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
3304 * creator of the phpmyadmin project
3305 * maintainer from 1998 to summer 2000
3307 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
3308 * multi-language version
3309 * various fixes and improvements
3310 * project co-administrator
3312 - Olivier Müller <om_at_omnis.ch>
3313 * started SourceForge phpMyAdmin project in March 2001
3314 * sync'ed different existing CVS trees with new features and bugfixes
3315 * multi-language improvements, dynamic language selection
3316 * current project maintainer
3317 * many bugfixes and improvements
3319 - Loïc Chapeaux <lolo_at_phpheaven.net>
3320 * rewrote and optimized javascript, DHTML and DOM stuff
3321 * rewrote the scripts so they fit the PEAR coding standards and
3322 generate XHTML1.0 and CSS2 compliant codes
3323 * improved the language detection system
3324 * many bugfixes and improvements
3326 - Robin Johnson <robbat2_at_users.sourceforge.net>
3327 * database maintence controls
3328 * table type code
3329 * Host authentication IP Allow/Deny
3330 * DB-based configuration (Not completed)
3331 * SQL parser
3332 * SQL validator
3333 * many bugfixes and improvements
3335 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
3336 * bookmarks feature
3337 * multiple dump feature
3338 * gzip dump feature
3339 * zip dump feature
3341 - Geert Lund <glund_at_silversoft.dk>
3342 * various fixes
3343 * moderator of the phpMyAdmin users forum at phpwizard.net
3345 - Korakot Chaovavanich <korakot_at_iname.com>
3346 * "insert as new row" feature
3348 - Pete Kelly <webmaster_at_trafficg.com>
3349 * rewrote and fix dump code
3350 * bugfixes
3352 - Steve Alberty <alberty_at_neptunlabs.de>
3353 * rewrote dump code for PHP4
3354 * mySQL table statistics
3355 * bugfixes
3357 - Benjamin Gandon <gandon_at_isia.cma.fr>
3358 * main author of the version 2.1.0.1
3359 * bugfixes
3361 - Alexander M. Turek <rabus_at_bugfixes.info>
3362 * XML exports
3363 * MySQL 4 related features
3364 * various small features and fixes
3365 * German language file updates
3367 - Mike Beck <mike.beck_at_ibmiller.de>
3368 * automatic joins in QBE
3369 * links column in printview
3370 * Relation view
3372 - Michal Cihar <nijel_at_users.sourceforge.net>
3373 * enhanced index creation/display feature
3374 * feature to use a different charset for HTML than for MySQL
3375 * Czech language file updates
3377 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
3378 (http://sourceforge.net/projects/phpmysqlformgen/)
3379 * suggested the patch for multiple table printviews
3381 - Garvin Hicking <hicking_at_faktor-e.de>
3382 * built the patch for vertical display of table rows
3383 * built the Javascript based Query window + SQL history
3384 * Improvement of column/db comments
3385 * (MIME)-Transformations for columns
3386 * Use custom alias names for Databases in left frame
3387 * vertical display of column properties page
3388 * some bugfixes, smaller features
3390 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
3391 * japanese kanji encoding conversion feature
3393 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
3394 * the Cookie authentication mode
3396 - Axel Sander <n8falke_at_users.sourceforge.net>
3397 * table relation-links feature
3399 - Maxime Delorme <delorme.maxime_at_free.fr>
3400 * PDF schema output, thanks also to Olivier Plathey for the
3401 "FPDF" library (see http://www.fpdf.org/).
3403 - Olof Edlund <olof.edlund_at_upright.se>
3404 * SQL validator server
3406 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
3407 * phpMyAdmin logo
3409 And also to the following people who have contributed minor changes,
3410 enhancements, bugfixes or support for a new language since version 2.1.0:
3412 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
3413 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
3414 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
3415 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
3416 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
3417 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
3418 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
3419 Luís V., Martijn W. van der Lee,
3420 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
3421 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas, "Manuzhai".
3424 Original Credits of Version 2.1.0
3425 ---------------------------------
3427 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
3428 to create a web-based interface to MySQL using PHP3. Although I have not
3429 used any of his source-code, there are some concepts I've borrowed from
3430 him. phpMyAdmin was created because Peter told me he wasn't going to
3431 further develop his (great) tool.
3432 Thanks go to
3433 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
3434 code for the check when dropping a table or database. He also suggested
3435 that you should be able to specify the primary key on tbl_create.php3. To
3436 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
3437 well as a bug-report. Plus many smaller improvements.
3438 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
3439 were introduced in 1.3.0 (including quite significant ones like the
3440 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
3441 bug-fixes and help.
3442 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
3443 language-independent by outsourcing the strings to a separate file. He
3444 also contributed the French translation.
3445 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
3446 tbl_select.php3, a feature to display only some fields from a table.
3447 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
3448 functions in tbl_change.php3. He also added the
3449 "Query by Example" feature in 2.0.
3450 - Dave Walton <walton_at_nordicdms.com> added support for multiple
3451 servers and is a regular contributor for bug-fixes.
3452 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
3453 features for 2.0.6.
3454 The following people have contributed minor changes, enhancements, bugfixes
3455 or support for a new language:
3456 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
3457 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
3458 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
3459 G. Wieggers.
3461 And thanks to everyone else who sent me email with suggestions, bug-reports
3462 and or just some feedback.
3463 </pre>
3470 <img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" border="0" height="31" width="88" /></a>
3471
3473 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" border="0" width="88" height="31" /></a>
3474 </p>
3476 </body>
3477 </html>