| blob | 63eecda0f6158709f2a45e76f07e660abaeac527 |
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 use something else in your file:</b>
241 <pre>
243 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
244 GRANT SELECT (Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv,
245 Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv,
246 Grant_priv, References_priv, Index_priv, Alter_priv)
247 ON mysql.user TO 'pma'@'localhost';
248 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
249 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
250 ON mysql.tables_priv TO 'pma'@'localhost';
252 </pre>
253 ... and if you want to use the many new relation and bookmark
254 features:
255 <pre>
258 </pre>
259 (this of course requires you to have a special DB for
260 phpMyAdmin, the contents will be explained later)
261 </li>
262 <li>
264 privileges on a set of particular databases. Normally you shouldn't
265 give global privileges to an ordinary user, unless you understand
266 the impact of those privileges (for example, you are creating
267 a superuser).<br />
270 <tt>GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';</tt>
271 <br />
272 What the user may now do is controlled entirely by the MySQL user
273 management system.<br />
274 With HTTP or cookie authentication mode, you don't need to fill the user/password
276 </li>
277 </ul>
280 <ul>
283 allows you to login as any valid MySQL user.</li>
284 <li>Is only supported with PHP running as an Apache module, not with
285 CGI.</li>
286 </ul>
289 <ul>
290 <li>You can use this method as a replacement for the HTTP
291 authentication (for example, if you're running IIS).
292 </li>
294 <li>With this mode, the use can truly logout of phpMyAdmin and login back
295 with the same username.</li>
296 </ul>
299 <ul>
300 <li>This mode is the less secure one because it requires you to fill the
305 <li>In the ISP FAQ section, there is an entry explaining how to protect
306 your configuration file.<br /></li>
307 <li>For additional security in this mode, you may wish to consider the
310 directives.</li>
311 </ul>
314 <!-- CONFIGURATION -->
318 <p>
321 the option that allows to use the *nix end of line character
323 you have modified.
324 </p>
327 <dl>
329 <dd>
330 Sets here the complete URL (with full path) to your phpMyAdmin version.
332 <br /><br />
333 phpMyAdmin needs this setting, because of requirements of the HTTP
334 protocol, explained in RFC2616, section 14.30.
335 <br /><br />
336 Don't forget the slash at the end of your URL. The URL must contain
337 characters that are valid for a URL, and on some servers, the path
338 is case-sensitive.
339 <br /><br />
340 Starting with version 2.3.0, you can try to leave this parameter
341 empty, because the program tries to auto-detect its proper value.
342 Additional details are in the configuration file.
343 <br /><br />
344 Alternatively, this setting can be dynamically completed. For example,
345 you can try to use such a kind of code:
346 <pre>
347 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
348 . $_SERVER['HTTP_HOST']
349 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
352 or
354 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
355 . $_SERVER['SERVER_NAME']
356 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
358 </pre>
362 <br /><br />
363 </dd>
365 <dd>
366 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the system
367 detects your absolute URI automatically, we display a warning to remind
368 you. If you have tested the automatic detection, and it works perfectly
369 for your setup, then you can set this variable to squelch the warning.
370 <br /><br />
371 </dd>
374 <dd>
375 Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
376 with master / foreign - tables (see
378 <br />
379 If you tried to set this up and it does not work for you, have a look on
381 use it. You will find a link that will analyze why those features have
382 been disabled.<br />
383 If you do not want to use those features set this variable to
385 <br /><br />
386 </dd>
389 <dd>
390 Since version 1.4.2, phpMyAdmin supports the administration of multiple
391 MySQL servers.
392 Therefore, a $cfg['Servers']-array has been added which contains
393 the login information for the different servers. The first
396 the second server, etc.
397 If you have only one server to administer, simply leave free the
398 hostname of the other $cfg['Server']-entries.
399 <br /><br />
400 </dd>
403 <dd>
404 The hostname of your $i-th MySQL-server. E.g. localhost.
405 <br /><br />
406 </dd>
409 <dd>
410 The port-number of your $i-th MySQL-server. Default is 3306 (leave
411 blank).
412 <br /><br />
413 </dd>
416 <dd>
417 The path to the socket to use. Leave blank for default.<br />
418 To use the socket feature you must run PHP 3.0.10 or more.
419 <br /><br />
420 </dd>
423 <dd>
424 What type connection to use with the MySQL server. Your options are
426 is nearly guaranteed to be available on all MySQL servers, while
427 sockets are not supported on some platforms.
428 <br /><br />
429 To use the socket mode, your MySQL server must be on the same machine
430 as the Web server.
431 <br /><br />
432 </dd>
435 <dd>
436 Whether to use a compressed protocol for the MySQL server connection
437 or not (experimental).<br />
439 </dd>
441 <dt>
444 </dt>
445 <dd>
446 When using HTTP or cookie authentication modes (or 'config'
447 authentication mode since phpMyAdmin 2.2.1), you need to supply the
452 This account is used to check what databases the user will see at
453 login.<br />
456 <br /><br />
457 Note that if you try login to phpMyAdmin with this
461 <br /><br />
462 In versions before 2.2.5, those were called
464 <br /><br />
465 </dd>
468 <dd>
469 Whether config or cookie or http authentication should be used for this
470 server.
472 <ul>
473 <li>
474 'config' authentication
476 way: username and password are stored in
478 </li>
479 <li>
480 'cookie' authentication mode
482 2.2.3 allows you to log in as any valid MySQL user with the
483 help of... cookies. Log name and password are stored in
484 cookies during the session and password is deleted when it
485 ends.
486 </li>
487 <li>
488 'http' authentication (was called 'advanced' in older versions)
490 allows you to log in as any valid MySQL user via HTTP-Auth.
491 </li>
492 </ul><br />
495 for more information.
496 <br /><br />
497 </dd>
499 <dt>
502 </dt>
503 <dd>
504 The user/password-pair which phpMyAdmin will use to connect to this
505 MySQL-server. This user/password pair is not needed when HTTP or cookie
506 authentication is used, and should be empty.<br /><br />
507 </dd>
510 <dd>
511 If set to a(an array of) database name(s), only this(these) database(s)
512 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
513 database(s) name(s) may contain MySQL wildcards characters
517 This setting is an efficient way to lower the server charge since the
518 latter does not need to send MySQL requests to build the available
520 privileges rules of the MySQL database server</span>. If set, it just
521 means only these databases will be displayed but
523 <br /><br />
524 </dd>
527 <dd>
528 Only useful when using phpMyAdmin with multiple server entries. If set,
529 this string will be displayed instead of the hostname in the pull-down
530 menu on the main page. This can be useful if you want to show only
531 certain databases on your system, for example.
532 <br /><br />
533 </dd>
535 <dt>
538 </dt>
539 <dd>
540 Starting with version 2.3.0 phpMyAdmin offers a lot of features
541 to work with master / foreign - tables. To use those as well as
542 the bookmark feature you need special tables with a
543 predefined structure, which we explain below.<br />
544 If you are the only user of this phpMyAdmin installation, you can
545 use your current database to store those special tables; in this
546 case, just put your current database name in
548 <br /><br />
549 If you are setting up a multi-user phpMyAdmin installation,
550 you will need to create a new database and setup special privileges,
551 so, as superuser:
552 <br /><br />
553 <ul>
554 <li>
555 create a new database for phpMyAdmin:<br />
559 privileges on this database. Here is a query to set up
562 controluser):<br />
563 <tt>
564 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to 'pma'@'localhost';
565 </tt><br />
567 </li>
568 <li>
570 </li>
571 </ul><br />
572 </dd>
574 <dt>
577 </dt>
578 <dd>
579 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can be
580 useful for queries you often run.<br /><br />
582 To allow the usage of this functionality you have to:
583 <ul>
585 <li>within this database create a table following this scheme:
586 <br />
587 <tt>
596 </tt>
597 </li>
598 <li>enter the table name in
600 </ul><br />
601 </dd>
603 <dt>
606 </dt>
607 <dd>
608 Since release 2.2.4 you can describe, in a special 'relation' table,
609 which field is a key in another table (a foreign key). phpMyAdmin
610 currently uses this to
611 <ul>
612 <li>
613 make clickable, when you browse the master table, the data values
614 that point to the foreign table;
615 </li>
616 <li>
618 when browsing the master table, if you move the mouse to a column
619 containing a foreign key (use also the 'table_info' table);
620 </li>
621 <li>
622 display links on the table properties page, to check referential
623 integrity (display missing foreign keys) for each described key;
624 </li>
625 <li>
626 in query-by-example, create automatic joins (see an example in
628 </li>
629 <li>
630 enable you to get a PDF schema of your database (also uses the
631 table_coords table).
632 </li>
633 </ul>
634 <br />
636 The keys can be numeric or character.
637 <br /><br />
639 To allow the usage of this functionality the superuser has to:
640 <ul>
642 <li>
643 within this database create a table following this scheme:
644 <br />
645 <tt>
651 `foreign_table` varchar(64) NOT NULL default '',<br />
652 `foreign_field` varchar(64) NOT NULL default '',<br />
653 PRIMARY KEY (`master_db`, `master_table`, `master_field`),<br />
656 </tt>
657 </li>
658 <li>
659 put the relation table name in
661 </li>
662 <li>
663 now as normal user open phpMyAdmin and for each one of your
664 tables where you want to use this feature, click
666 </li>
667 </ul><br />
670 future development of the cross-db relations.<br /><br />
671 </dd>
673 <dt>
676 </dt>
677 <dd>
678 Since release 2.3.0 you can describe, in a special 'table_info'
679 table, which field is to be displayed as a tool-tip when moving the
680 cursor over the corresponding key.
681 <br />
682 This configuration variable will hold the name of this special
683 table.
684 To allow the usage of this functionality the superuser has to:
685 <ul>
687 <li>within this database create a table following this scheme:
688 <br />
689 <tt>
693 `display_field` varchar(64) NOT NULL default '',<br />
696 </tt>
697 </li>
698 <li>
699 put the table name in
701 </li>
702 <li>
703 then for each table where you want to use this feature,
705 to choose the field.
706 </li>
707 </ul><br />
709 <br /><br />
710 </dd>
712 <dt>
716 </dt>
717 <dd>
718 Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
719 the relations between your tables. To do this it needs two tables
722 table will be placed on a PDF schema output).
723 <br /><br />
726 output.
727 <br /><br />
728 To allow the usage of this functionality the superuser has to:
729 <ul>
731 <li>
732 within this database create a table following this scheme:
733 <br />
734 <tt>
741 PRIMARY KEY (`db_name`, `table_name`, `pdf_page_number`)<br />
742 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin PDF output';<br />
743 </tt>
744 </li>
745 <li>
746 also within this database create:<br />
747 <tt>
750 `page_nr` int(10) unsigned NOT NULL auto_increment,<br />
755 </tt>
756 </li>
757 <li>
758 put the first table name in
760 and the second table name in
762 </li>
763 </ul><br />
765 <br /><br />
766 </dd>
768 <dt>
771 </dt>
772 <dd>
773 <!-- This part requires a content update! -->
774 Since release 2.3.0 you can store comments to describe each column
776 <br /><br />
777 Starting with release 2.5.0, comments are consequently used on the table property
778 pages and table browse view, showing up as tool-tips above the column name (properties page)
779 or embedded within the header of table in browse view. They can also be shown
780 in a table dump. Please see the relevant configuration directives later on.
781 <br /><br />
782 Also new in release 2.5.0 is a mime-transformation system which is also based on
784 for further information. To use the mime-transformation system, your column_info
785 table has to have the three new fields 'mimetype', 'transformation', 'transformation_options'.
786 <br /><br />
787 To allow the usage of this functionality the superuser has to:
788 <ul>
790 <li>
791 within this database create a table following this scheme:
792 <br />
793 <tt>
801 transformation varchar(255) NOT NULL default '',<br />
802 transformation_options varchar(255) NOT NULL default '',<br />
804 UNIQUE KEY db_name (db_name, table_name, column_name)<br />
806 </tt>
807 </li>
808 <li>
809 put the table name in
811 </li>
812 <li>
814 <tt>
818 ADD `transformation_options` VARCHAR( 255 ) NOT NULL ;<br />
819 </tt>
820 and remember that the Variable in config.inc.php has been renamed
821 from <br />$cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i]['column_info']
822 </li>
823 </ul><br />
824 </dd>
826 <dt>
829 </dt>
830 <dd>
831 Since release 2.5.0 you can store your SQL history, which means all queries you
832 entered manually into the phpMyAdmin interface. If you don't want to use a table-
833 based history, you can use the JavaScript-based history. Using that, all your
834 history items are deleted when closing the window.<br /><br />
837 you want to have on hold. On every login, this list gets cut to the maximum amount.
838 <br /><br />
840 The query history is only available if you use the JavaScript-based query window,
842 <br /><br />
844 To allow the usage of this functionality the superuser has to:
845 <ul>
847 <li>
848 within this database create a table following this scheme:
849 <br />
850 <tt>
859 INDEX ( `username` , `db` , `table` , `timevalue` )<br />
861 </tt>
862 </li>
863 <li>
864 put the table name in
866 </li>
867 </ul><br />
868 </dd>
870 <dt>
873 </dt>
874 <dd>
875 Because release 2.5.0 introduced the new MIME-transformation support, the
876 column_info table got enhanced with three new fields. If the above variable is
877 set to TRUE (default) phpMyAdmin will check if you have the latest table structure
878 available. If not, it will emit a warning to the superuser.<br /><br />
880 You can disable this checking behavior by setting the variable to false, which
881 should offer a performance increase.<br /><br />
883 Recommended to set to FALSE, when you are sure, your table structure is up to date.
884 <br /><br />
885 </dd>
887 <dt>
889 </dt>
890 <dd>
891 If your rule order is empty, then IP authentication is disabled.
892 <br /><br />
894 applies all deny rules followed by allow rules.
895 Access is allowed by default. Any client which does not match a Deny
896 command or does match an Allow command will be allowed access to the
897 server.
898 <br /><br />
900 applies all allow rules followed by deny rules. Access is denied by
901 default. Any client which does not match an Allow directive or does
902 match a Deny directive will be denied access to the server.
903 <br /><br />
904 If your rule order is set to 'explicit', the authentication is
905 performed in a similar fashion to rule order 'deny,allow', with the
909 and was available in Apache by specifying allow and deny rules without
910 setting any order.
911 <br /><br />
912 </dd>
914 <dt>
916 </dt>
917 <dd>
918 The general format for the rules is as such:<br />
919 <tt>
920
922 </tt>
923 <br /><br />
928 well:<br />
929 <tt>
932 </tt>
933 <br /><br />
935 Having an empty rule list is equivalent to either using
939 <br /><br />
941 For the IP matching system, the following work:<br />
945 But the following does not work:<br />
947 <br /><br />
948 </dd>
951 <dd>
952 If you have more than one server configured, you can set
954 that server when phpMyAdmin is started, or set it to 0 to be given a
955 list of servers without logging in.<br />
957 MUST be set to that server.
958 <br /><br />
959 </dd>
962 <dd>
963 Defines whether to use GZip output buffering for increased
964 speed in HTTP transfers.
965 <br /><br />
966 </dd>
969 <dd>
970 Whether persistent connections should be used or not (mysql_connect or
971 mysql_pconnect).
972 <br /><br />
973 </dd>
976 <dd>
977 Set the number of seconds a script is allowed to run. If seconds is set
978 to zero, no time limit is imposed.<br />
979 This setting is used while importing/exporting dump files but has no
980 effect when PHP is running in safe mode.
981 <br /><br />
982 </dd>
985 <dd>
986 Mark used tables and make it possible to show databases with locked
987 tables (since 3.23.30).
988 <br /><br />
989 </dd>
992 <dd>
993 Defines whether SQL-queries generated by phpMyAdmin should be displayed
994 or not.
995 <br /><br />
996 </dd>
999 <dd>
1000 Defines whether normal users (non-administrator) are allowed to
1001 delete their own database or not. If set as FALSE, the link "Drop
1003 mydatabase" will be rejected. Quite practical for ISP's with many
1004 customers.
1005 <br /><br />
1006 </dd>
1009 <dd>
1011 displayed when you're about to loose data.
1012 <br /><br />
1013 </dd>
1016 <dd>
1017 Define whether the previous login should be recalled or not in cookie
1018 authentication mode.
1019 <br /><br />
1020 </dd>
1023 <dd>
1024 Define whether the "search string inside database" is enabled or not.
1025 <br /><br />
1026 </dd>
1029 <dd>
1030 Defines whether to use select-based menu and display only the current
1031 tables in the left frame (smaller page).
1032 <br /><br />
1033 </dd>
1036 <dd>
1037 Defines whether to display table comment as tool-tip in left frame or
1038 not.
1039 <br /><br />
1040 </dd>
1043 <dd>
1044 If tool-tips are enabled and a DB comment is set, this will flip the comment
1045 and the real name. That means, if you have a table called 'user0001' and add
1046 the comment 'MyName' on it, you will see the name 'MyName' used consequently
1047 in the left frame and the tool-tip shows the real name of the DB.
1048 <br /><br />
1049 </dd>
1052 <dd>
1053 Same as $cfg['ShowTooltipAliasDB'], except this works for table names.
1054 <br /><br />
1055 </dd>
1058 <dd>
1059 Defines whether to display space usage and statistics about databases
1060 and tables or not.<br />
1061 Note that statistics requires at least MySQL 3.23.3 and that, at this
1062 date, MySQL doesn't return such information for Berkeley DB tables.
1063 <br /><br />
1064 </dd>
1066 <dt>
1071 </dt>
1072 <dd>
1076 starting main (right) frame. This setting does not check MySQL commands
1077 entered directly.
1078 <br /><br />
1080 Please note that to block the usage of phpinfo() in scripts, you
1081 have to put this in your php.ini:<br />
1083 <br /><br />
1087 coded password value in the configuration file, end users can't be
1088 allowed to change their passwords.
1089 <br /><br />
1090 </dd>
1093 <dd>
1094 Defines whether to suggest a database name on the
1096 <br /><br />
1097 </dd>
1100 <dd>
1102 content or not.
1103 <br /><br />
1104 </dd>
1107 <dd>
1108 Defines whether navigation bar buttons contain text or symbols only.
1109 <br /><br />
1110 </dd>
1113 <dd>
1114 Defines whether an user should be displayed a
1116 <br /><br />
1117 </dd>
1120 <dd>
1121 Number of rows displayed when browsing a result set. If the result set
1122 contains more rows, Previous/Next links will be shown.
1123 <br /><br />
1124 </dd>
1127 <dd>
1131 DATE, DATETIME & TIMESTAMP, ascending order else- by default.
1132 <br /><br />
1133 </dd>
1136 <dd>
1138 from edition when browsing a table's content or not.
1139 Valid values are:<br />
1142 <br />
1145 <br /><br />
1146 </dd>
1149 <dd>
1150 Defines whether MySQL functions fields should be displayed or not in
1151 edit/insert mode.
1152 <br /><br />
1153 </dd>
1156 <dd>
1157 Defines which type of editing controls should be used for CHAR and
1158 VARCHAR fields. Possible values are:
1159 <ul>
1160 <li>
1161 input - this allows to limit size of text to size of field in
1162 MySQL, but has problems with newlines in fields
1163 </li>
1164 <li>
1165 textarea - no problems with newlines in fields, but also no
1166 length limitations
1167 </li>
1168 </ul>
1169 Default is old behavior so input.
1170 <br /><br />
1171 </dd>
1173 <dt>
1177 </dt>
1178 <dd>
1179 Defines whether to allow the use of zip/GZip/BZip2 compression when
1180 creating a dump file or not.
1181 <br /><br />
1182 </dd>
1185 <dd>
1186 If set to True, do use less graphically intense tabs on the top of the mainframe.
1187 <br /><br />
1188 </dd>
1191 <dd>
1192 Defines the tab displayed by default on server view. Possible
1197 <br /><br />
1198 </dd>
1201 <dd>
1202 Defines the tab displayed by default on database view. Possible
1205 <br /><br />
1206 </dd>
1209 <dd>
1210 Defines the tab displayed by default on table view. Possible
1214 <br /><br />
1215 </dd>
1218 <dd>
1219 If set to an URL which points to the MySQL documentation (type depends
1221 generated.
1222 <br />
1224 Documentation page</a> for more information about MySQL manuals and
1225 their types.
1226 <br /><br />
1227 </dd>
1230 <dd>
1231 Type of MySQL documentation:
1232 <ul>
1238 </ul>
1239 <br /><br />
1240 </dd>
1243 <dd>
1244 Defines the default language to use, if not browser-defined or
1245 user-defined.<br />
1247 this setting.
1248 <br /><br />
1249 </dd>
1252 <dd>
1253 Force: always use this language (must be defined in the
1255 <br /><br />
1256 </dd>
1259 <dd>
1260 Default character set to use for recoding of MySQL queries. This must be
1262 option.<br />
1263 You can give here any character set which is in
1265 choice, user can select any of them.
1266 <br /><br />
1267 </dd>
1270 <dd>
1271 Allow character set recoding of MySQL queries. You need recode or iconv
1272 support (compiled in or module) in PHP to allow MySQL queries recoding
1273 and used language file must have it enabled (by default only these
1274 which are in Unicode, just to avoid losing some characters).
1275 <br /><br />
1276 </dd>
1279 <dd>
1280 You can select here which functions will be used for character set
1281 conversion.
1282 Possible values are:<br />
1283 <ul>
1284 <li>auto - automatically use available one (first is tested
1285 iconv, then recode)</li>
1288 </ul>
1289 Default is auto.
1290 <br /><br />
1291 </dd>
1294 <dd>
1295 Available character sets for MySQL conversion. You can add your own (any of
1296 supported by recode/iconv) or remove these which you don't use.
1297 Character sets will be shown in same order as here listed, so if you
1298 frequently use some of these move them to the top.
1299 <br /><br />
1300 </dd>
1303 <dd>
1304 Left frame width in pixel.
1305 <br /><br />
1306 </dd>
1308 <dt>
1311 </dt>
1312 <dd>
1313 The background colors (HTML) used for both the frames.
1314 <br /><br />
1315 </dd>
1317 <dt>
1319 </dt>
1320 <dd>
1321 The URI of the background image used for the right frame. It can be
1322 absolute as well as relative from your phpMyAdmin directory.
1323 </dd>
1326 <dd>
1327 The color (HTML) used for the pointer in the left frame (does not work
1328 with Netscape 4).
1329 <br /><br />
1330 </dd>
1333 <dd>
1334 The size of a table's border.
1335 <br /><br />
1336 </dd>
1339 <dd>
1340 The color (HTML) used for table headers.
1341 <br /><br />
1342 </dd>
1345 <dd>
1346 The color (HTML) #1 for table rows.
1347 <br /><br />
1348 </dd>
1351 <dd>
1352 The color (HTML) #2 for table rows.
1353 <br /><br />
1354 </dd>
1356 <dt>
1359 </dt>
1360 <dd>
1361 The colors (HTML) uses for the pointer and the marker in browse mode
1363 The former feature highlights the row over which your mouse is passing
1364 and the latter lets you visually mark/unmark rows by clicking on
1365 them.<br />
1366 You can disable both of these features by emptying the respective
1367 directive.
1368 <br /><br />
1369 </dd>
1371 <dt>
1376 </dt>
1377 <dd>
1378 Number of columns and rows for the textareas.<br />
1380 SQL textareas inside the query window.<br />
1381 The Char* values are used for CHAR and VARCHAR editing (if configured
1382 via $cfg['CharEditing']).
1383 <br /><br />
1384 </dd>
1386 <dt>
1388 </dt>
1389 <dd>
1390 Defines if the whole textarea of the query box will be selected on
1391 click.
1392 <br /><br />
1393 </dd>
1396 <dd>
1398 field on browse view. Can be turned off by a toggle button on the
1399 browse page.
1400 <br /><br />
1401 </dd>
1403 <dt>
1406 </dt>
1407 <dd>
1408 Defines the place where modify and delete links would be put when
1409 tables contents are displayed (you may have them displayed both at the
1410 left and at the right).
1413 <br /><br />
1414 </dd>
1418 </dt>
1419 <dd>
1420 There are 3 display modes: horizontal, horizontalflipped and vertical. Define
1421 which one is displayed by default. The first mode displays each row on a
1422 horizontal line, the second rotates the headers by 90 degrees, so you can use
1423 descriptive headers even though fields only contain small values and still
1424 print them out. The vertical mode sorts each row on a vertical lineup.<br /><br />
1425 The HeaderFlipType can be set to 'css' or 'faked'. When using 'css' the rotation
1426 of the header for horizontalflipped is done via CSS. If set to 'faked' PGP
1427 does the transformation for you, but of course this does not look as good as CSS.
1428 <br /><br />
1429 </dd>
1432 <dd>
1433 When editing/creating new columns in a table all fields normally get lined up
1434 one field a line. (default: 'horizontal'). If you set this to 'vertical' you
1435 can have each field lined up vertically beneath each other. You can save up
1436 a lot of place on the horizontal direction and no longer have to scroll.
1437 <br /><br />
1438 </dd>
1442 </dt>
1443 <dd>
1444 By setting the corresponding variable to TRUE you can enable the display of
1445 column comments in Browse or Property display. In browse mode, the comments
1446 are show inside the header. In property mode, comments are displayed using
1447 a CSS-formatted dashed-line below the name of the field. The comment is shown
1448 as a tool-tip for that field.
1449 <br /><br />
1450 </dd>
1453 <dd>
1454 The name of the directory, ending with a slash, where SQL files have
1455 been uploaded by other means than phpMyAdmin (for example, ftp).
1456 Those files are available under a drop-down box when you click the
1457 database name, then the SQL tab.
1458 <br /><br />
1460 <br /><br />
1461 This feature is useful when your file is too big to be uploaded via
1462 HTTP, or when file uploads are disabled in PHP.
1463 <br /><br />
1464 Please note that if PHP is running in safe mode, this directory must
1465 be owned by the same user as the owner of the phpMyAdmin scripts.
1466 <br /><br />
1467 </dd>
1470 <dd>
1471 Repeat the headers every X cells, or 0 to deactivate.
1472 <br /><br />
1473 </dd>
1483 </dt>
1484 <dd>
1485 All those variables affect the new query frame/window. When $cfg['QueryFrame']
1486 is set to true a new frame is embedded on the left with a small area. Clicking
1487 on that results in opening a direct interface to enter SQL queries.<br /><br />
1488 When $cfg['QueryFrameJS'] is set to true, clicking on that link opens a new
1489 custom sized browser window ($cfg['QueryWindowWidth'], $cfg['QueryWindowWidth'] -
1490 both integers for the size in pixels). If set to false, clicking on the link
1491 only opens the SQL input in the mainframe.<br /><br />
1492 The usage of the JavaScript query window is recommended if you have a JavaScript
1493 enabled browser. Basic functions are used to exchange quite a few variables, so
1494 most 4th generation browsers should be capable to use that feature. It currently
1496 If $cfg['QueryHistoryDB'] is set to TRUE, all your Queries are logged to a table,
1498 If set to FALSE, all your queries will be appended to the form, but only as long
1499 as your window is opened they remain saved.<br /><br />
1500 When using the JavaScript based query window, it will always get updated when you
1501 click on a new table/db to browse and will focus if you click on "Edit SQL" after
1502 using a query.<br /><br />
1503 If $cfg['QueryHistoryDB'] is set to TRUE you can specify the amount of saved
1504 history items using $cfg['QueryHistoryMax'].<br /><br />
1505 The query window also has a custom tabbed look to group the features. Using the
1506 variable $cfg['QueryWindowDefTab'] you can specify the default tab to be used
1507 when opening the query window. It can be set to either 'sql', 'files', 'history'
1508 or 'full'.<br /><br />
1509 The variable $cfg['QueryFrameDebug'] can be used by developers for easier future
1510 feature integration.
1511 <br /><br />
1512 </dd>
1515 <dd>
1517 <br /><br />
1518 </dd>
1521 <dd>
1522 As of phpMyAdmin 2.3.0, we now have a fully functional SQL Parser system.
1523 It is enabled by default, as it is used to format the SQL queries.
1524 <br />
1525 As of 2.3.1, it will become an integral part of phpMyAdmin, as it will
1526 analyze certain queries to improve the behavior of phpMyAdmin. But as
1527 it is very new, and not yet heavily used, we offer you an option to
1528 turn it off.
1529 <br /><br />
1530 </dd>
1533 <dd>
1534 The main use of the new SQL Parser is to pretty-print SQL queries. By
1535 default we use HTML to format the query, but you can disable this by
1537 <br /><br />
1538 </dd>
1542 <dd>
1543 For the pretty-printing of SQL queries, under some cases the part of a
1544 query inside a bracket is indented. By changing
1547 specifies the units of the indent amount that you specified. This is
1548 used via stylesheets.
1549 <br /><br />
1550 </dd>
1553 <dd>
1554 This array is used to define the colours for each type of element of
1555 the pretty-printed SQL queries. The tuple format is<br />
1557 If you specify an empty string for the color of a class, it is ignored
1558 in creating the stylesheet.
1559 You should not alter the class names, only the colour strings.<br />
1561 <ul>
1585 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1586 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1587 </ul><br />
1588 </dd>
1590 <dt><b>$cfg['SQLValidator']['use']</b> boolean</dt>
1591 <dd>
1592 phpMyAdmin now supports use of the <a href="http://developer.mimer.com/validator/index.htm">Mimer SQL Validator</a> service,
1593 as originally published on
1595 <br />
1596 For help in setting up your system to use the service, see the
1598 <br /><br />
1599 </dd>
1601 <dt><b>$cfg['SQLValidator']['username']</b> string<br />
1602 <b>$cfg['SQLValidator']['password']</b> string</dt>
1603 <dd>
1604 The SOAP service allows you to login with <tt>anonymous</tt>
1605 and any password, so we use those by default.. Instead, if
1606 you have an account with them, you can put your login details
1607 here, and it will be used in place of the anonymous login.
1608 <br /><br />
1609 </dd>
1611 <dt><b>$cfg['DBG']['enable']</b> boolean</dt>
1612 <dd>
1613 <b>DEVELOPERS ONLY!</b><br />
1614 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1615 the code.
1616 <br />
1617 For help in setting up your system to this, see the
1619 </dd>
1621 <dt><b>$cfg['DBG']['profile']['enable']</b> boolean</dt>
1622 <dd>
1623 <b>DEVELOPERS ONLY!</b><br />
1624 Enable profiling support for phpMyAdmin. This will append a chunk of data
1625 to the end of every page displayed in the main window with profiling
1626 statistics for that page.<br />
1627 You may need need to increase the maximum execution time for this to
1628 complete successfully.
1629 </dd>
1631 <dt><b>$cfg['DBG']['profile']['threshold']</b> float (units in milliseconds)</dt>
1632 <dd>
1633 <b>DEVELOPERS ONLY!</b><br />
1634 When profiling data is displayed, this variable controls the threshold of
1635 display for any profiling data, based on the average time each time has
1636 taken. If it is over the threshold it is displayed, otherwise it is not
1637 displayed. This takes a value in milliseconds. In most cases you don't need
1638 to edit this.
1639 </dd>
1641 <dt><b>$cfg['ColumnTypes'] </b>array</dt>
1642 <dd>
1643 All possible types of a MySQL column. In most cases you don't need to
1644 edit this.
1645 <br /><br />
1646 </dd>
1648 <dt><b>$cfg['AttributeTypes'] </b>array</dt>
1649 <dd>
1650 Possible attributes for fields. In most cases you don't need to edit
1651 this.
1652 <br /><br />
1653 </dd>
1655 <dt><b>$cfg['Functions'] </b>array</dt>
1656 <dd>
1657 A list of functions MySQL supports. In most cases you don't need to
1658 edit this.
1659 <br /><br />
1660 </dd>
1662 </dl>
1664 <!-- TRANSFORMATIONS -->
1666 <h2>Transformations</h2>
1668 <p>
1672 </p>
1675 <h3>[1. Introduction]</h3>
1677 <p>To enable transformations, you have to setup the column_info table and the proper
1679 <br />
1681 <p>You can apply different transformations to the contents of each field. The
1682 transformation will take the content of each field and transform it with
1683 certain rules defined in the selected transformation.</p><br />
1685 <p>Say you have a field 'filename' which contains a filename. Normally you would see
1686 in phpMyAdmin only this filename. Using transformations you can transform that filename
1687 into a HTML link, so you can click inside of the phpMyAdmin structure on the field's
1688 link and will see the file displayed in a new browser window. Using transformation
1689 options you can also specify strings to append/prepend to a string or the format you
1690 want the output stored in.</p><br />
1692 <p>For a general overview of all available transformations and their options, you can
1693 consult your <i><www.your-host.com>/<your-install-dir>/libraries/transformations/overview.php3</i>
1694 installation.</p><br />
1695 <br />
1698 <h3>[2. Usage]</h3>
1700 <p>Go to your tbl_properties.inc.php3 page (i.e. reached through clicking on the
1701 'properties' link for a table). There you will see three new fields at the end of the
1702 line. They are called 'MIME-type', 'Browser transformation' and 'Transformation options'.</p>
1703 <br />
1705 <ul>
1706 <li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
1707 empty or to use 'auto' [this feature is not yet available]. Please note that
1708 transformations are inactive as long as no mime-type is selected.</li><br /><br />
1710 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
1711 hopefully growing amount of pre-defined transformations. See below for information on
1712 how to build your own transformation.<br /><br />
1714 There are global transformations and mimetype-bound transformations. Global transformations
1715 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
1716 Mimetype-bound transformations usually only operate on a certain mimetype. There are
1717 transformations which operate on the main mimetype (like 'image'), which will most likely
1718 take the subtype into regard, and those who only operate on a
1719 specific subtype (like 'image/jpeg').<br /><br />
1721 You can use transformations on mimetypes for which the function was not defined for. There
1722 is no security check for you selected the right transformation, so take care of what the
1723 output will be like.</li><br /><br />
1725 <li>The field 'Transformation options' is a free-type textfield. You have to enter
1726 transform-function specific options here. Usually the transforms can operate with default
1727 options, but it is generally a good idea to look up the overview to see which options are
1728 necessary.<br /><br />
1730 Much like the ENUM/SET-Fields, you have to split up several options using the format
1731 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
1732 parsed as an array, leaving the first value the first element in the array, and so
1733 forth.<br /><br />
1735 If you want to specify a MIME character set you can define it in the transformation_options.
1736 You have to put that outside of the pre-defined options of the specific mime-transform,
1738 for which you can specify 2 options and you want to append a character set, enter "'first
1739 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
1741 </ul>
1744 <h3>[3. File structure]</h3>
1746 <p>All mimetypes and their transformations are defined through single files in
1747 the directory 'libraries/transformations/'.</p><br />
1749 <p>They are stored in files to ease up customization and easy adding of new
1750 transformations.</p><br />
1752 <p>Because the user cannot enter own mimetypes, it is kept sure that transformations
1753 always work. It makes no sense to apply a transformation to a mimetype, the
1754 transform-function doesn't know to handle.</p><br />
1756 <p>One can, however, use empty mime-types and global transformations which should work
1757 for many mimetypes. You can also use transforms on a different mimetype they where built
1758 for, but pay attention to option usage as well as what the transformation does to your
1759 field.</p><br />
1761 <p>There is a basic file called 'global.inc.php3'. This function can be included by
1762 any other transform function and provides some basic functions.</p><br />
1764 <p>There are 5 possible file names:</p>
1766 <ol>
1767 <li>A mimetype+subtype transform:<br /><br />
1769 [mimetype]_[subtype]__[transform].inc.php3<br /><br />
1771 Please not that mimetype and subtype are separated via '_', which shall not be
1772 contained in their names. The transform function/filename may contain only
1773 characters which cause no problems in the file system as well as the PHP function
1774 naming convention.<br /><br />
1776 The transform function will the be called 'PMA_transform_[mimetype]_[subtype]__[transform]()'.<br /><br />
1778 <b>Example:</b><br /><br />
1780 text_html__formatted.inc.php3<br />
1781 PMA_transform_text_html__formatted()</li><br /><br />
1783 <li>A mimetype (w/o subtype) transform:<br /><br />
1785 [mimetype]__[transform].inc.php3<br /><br />
1787 Please note that there are no single '_' characters.
1788 The transform function/filename may contain only characters which cause no problems
1789 in the file system as well as the PHP function naming convention.<br /><br />
1791 The transform function will the be called 'PMA_transform_[mimetype]__[transform]()'.<br /><br />
1793 <b>Example:</b><br /><br />
1795 text__formatted.inc.php3<br />
1796 PMA_transform_text__formatted()</li><br /><br />
1798 <li>A mimetype+subtype without specific transform function<br /><br />
1800 [mimetype]_[subtype].inc.php3<br /><br />
1802 Please note that there are no '__' characters in the filename. Do not use special
1803 characters in the filename causing problems with the file system.<br /><br />
1805 No transformation function is defined in the file itself.<br /><br />
1807 <b>Example:</b><br /><br />
1809 text_plain.inc.php3<br />
1810 (No function)</li><br /><br />
1812 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
1814 [mimetype].inc.php3<br /><br />
1816 Please note that there are no '_' characters in the filename. Do not use special
1817 characters in the filename causing problems with the file system.<br /><br />
1819 No transformation function is defined in the file itself.<br /><br />
1821 <b>Example:</b><br /><br />
1823 text.inc.php3<br />
1824 (No function)</li><br /><br />
1826 <li>A global transform function with no specific mimetype<br /><br />
1828 global__[transform].inc.php3<br /><br />
1830 The transform function will the be called 'PMA_transform_global__[transform]()'.<br /><br />
1832 <b>Example:</b><br /><br />
1834 global__formatted<br />
1835 PMA_transform_global__formatted()</li>
1836 </ol>
1838 <br />
1839 <p>So generally use '_' to split up mimetype and subtype, and '__' to provide a
1840 transform function.</p><br />
1842 <p>All filenames containing no '__' in themselves are not shown as valid transform
1843 functions in the dropdown.</p><br />
1845 <p>Please see the libraries/transformations/TEMPLATE file for adding your own transform
1846 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
1847 without a transform function. Also note the introduction of a function description in
1848 the language files. For each function a $strTransformation_[filename without .inc.php3]
1849 has to exist.</p><br />
1851 <p>You can use the template generator to generate new functions and entries in the
1852 language file.</p><br />
1854 <p>To create a new transform function please see libraries/transformations/template_generator.sh.
1855 To create a new, empty mimetype please see libraries/transformations/template_generator_mimetype.sh.</p><br />
1857 <!-- FAQ -->
1859 <h2>FAQ - Frequently Asked Questions</h2>
1861 <p>
1869 </p>
1872 <h3>[1. Server]</h3>
1874 <h4>
1875 [1.1] I'm running PHP 4+ and my server is crashing each time a specific
1876 action is required or phpMyAdmin sends a blank page or a page full of
1877 cryptic characters to my browser, what can I do?
1878 </h4>
1879 <p>
1880 There are some known PHP bugs with output buffering and compression.<br />
1881 Try to set the <tt>$cfg['OBGzip']</tt> directive to <tt>FALSE</tt> in your
1882 <i>config.inc.php or .php3</i> file and the
1883 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
1884 configuration file.<br />
1885 Furthermore, we know about such problems connected to the release
1886 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
1887 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.
1888 </p>
1890 <h4>
1891 [1.2] My Apache server crashes when using phpMyAdmin.
1892 </h4>
1893 <p>
1894 You should first try the latest versions of Apache (and possibly MySQL).
1895 <br />
1896 See also the other FAQ entry about PHP bugs with output buffering.
1897 <br />
1898 If your server keeps crashing, please ask for help in the various
1899 Apache support groups.
1900 </p>
1902 <h4>
1904 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
1905 script: I'm always displayed the login screen.
1906 </h4>
1907 <p>
1908 This is a known PHP bug (see this
1910 official PHP bug database. It means there is and won't be any phpMyAdmin
1911 fix against it because there is no way to code a fix.
1912 </p>
1914 <h4>
1915 [1.4] Using phpMyAdmin on IIS, I'm displayed the error message:
1916 "The specified CGI application misbehaved by not returning a
1917 complete set of HTTP headers...".
1918 </h4>
1919 <p>
1920 You just forgot to read the <i>install.txt</i> file from the php
1921 distribution. Have a look at the last message in this
1923 official PHP bug database.
1924 </p>
1926 <h4>
1927 [1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
1928 messages with the HTTP or advanced authentication mode.
1929 </h4>
1930 <p>
1931 This is a known problem with the PHP ISAPI filter: it's not so stable. For
1932 some more information and complete testings see the messages posted by
1933 André B. aka "djdeluxe76" in
1934 <a href="http://www.phpwizard.net/phorum/read.php?f=1&i=6624&t=6300">this thread</a>
1935 from the phpWizard forum.<br />
1936 Please use instead the cookie authentication mode.
1937 </p>
1939 <h4>
1940 [1.6] I can't use phpMyAdmin on PWS: nothing is displayed!</h4>
1941 <p>
1942 This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
1943 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
1944 declarations (2 lines) from the scripts <i>header.inc.php3</i>,
1945 <i>header_printview.inc.php3</i>, <i>index.php3</i>, <i>left.php3</i> and
1946 <i>libraries/common.lib.php3</i>.
1947 </p>
1949 <h4>
1950 [1.7] How can I GZip or Bzip a dump or a CSV export. It does not seem to
1951 work.
1952 </h4>
1953 <p>
1954 These features are based on the <tt>gzencode()</tt> and
1955 <tt>bzcompress()</tt> PHP functions to be more independent of the platform
1956 (Unix/Windows, Safe Mode or not, and so on).
1957 So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
1958 (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
1959 We faced PHP crashes when trying to download a dump with MS Internet
1960 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
1961 this case you should switch to the release version of PHP 4.2.0.
1962 </p>
1964 <h4>
1965 [1.8] I cannot insert a text file in a table, and I get an error about
1966 safe mode being in effect.
1967 </h4>
1968 <p>
1969 Your uploaded file is saved by PHP in the "upload dir", as
1970 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
1971 the system default is <i>/tmp</i>).
1972 <br />
1973 We recommend the following setup for Apache servers running in safe mode,
1974 to enable uploads of files while being reasonably secure:
1975 </p>
1976 <ul>
1977 <li>create a separate directory for uploads:
1978 <tt>mkdir /tmp/php</tt></li>
1979 <li>give ownership to the Apache server's user.group:
1980 <tt>chown apache.apache /tmp/php</tt></li>
1981 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
1982 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in php.ini</li>
1983 <li>restart Apache</li>
1984 </ul>
1986 <h4>
1987 [1.9] I'm having troubles when uploading files. In general file uploads
1988 don't work on my system and uploaded files have a <tt>Content-Type:</tt>
1989 header in the first line.
1990 </h4>
1991 <p>
1992 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
1993 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?
1994 <br />
1995 So the problem is that this package has a serious bug that was corrected
1996 ages ago in PHP (2001-01-28: see
1998 for more details). The problem is that the bugged package is still
1999 available though it was corrected (see
2001 for more details).
2002 <br />
2003 So please download
2004 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2005 and the problem should go away.
2006 <br />
2007 And that fixes the \r\n problem with file uploads!
2008 </p>
2010 <h4>
2011 [1.10] I'm having troubles when uploading files with phpMyAdmin running
2012 on a secure server. My browser is Internet Explorer and I'm using the
2013 Apache server.
2014 </h4>
2015 <p>
2016 As suggested by "Rob M" in the phpWizard forum, add this line to
2017 your <i>httpd.conf</i>:<br />
2018 <tt>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</tt><br />
2019 It seems to clear up many problems between Internet Explorer and SSL.
2020 </p>
2022 <h4>
2023 [1.11] I get an 'open_basedir restriction' while uploading a file from
2024 the query box.
2025 </h4>
2026 <p>
2027 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2028 restrictions. Assuming that the restriction allows you to open files in the
2029 current directory ('.'), all you have to do is create a 'tmp' directory
2030 under the phpMyAdmin install directory, with permissions 777 and the same
2031 owner as the owner of your phpMyAdmin directory. The uploaded files will
2032 be moved there, and after execution of your SQL commands, removed.
2033 </p>
2035 <h4>
2036 [1.12] I have lost my MySQL root password, what can I do?
2037 </h4>
2038 <p>
2039 The MySQL manual explains how to
2041 reset the permissions</a>.
2042 </p>
2044 <h4>
2045 [1.13] I get an error 'No SQL query' when trying to execute a bookmark.
2046 </h4>
2047 <p>
2048 If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2049 cannot access the uploaded query.
2050 </p>
2052 <h4>
2053 [1.14] I get an error 'No SQL query' when trying to submit a query from
2054 the convenient text area.
2055 </h4>
2056 <p>
2057 Check the <tt>post_max_size</tt> directive from your PHP configuration file
2058 and try to increase it.
2059 </p>
2061 <h4>
2062 [1.15] I have problems with <i>mysql.user</i> field names.
2063 </h4>
2064 <p>
2065 In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2066 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2067 names to align with current standards.
2068 </p>
2069 <h4>
2070 [1.16] I cannot upload big dump files.
2071 </h4>
2072 <p>
2073 The first things to check (or ask your host provider to check) are the
2074 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2075 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2076 <br />
2077 All of these three settings limit the maximum size of data that can be
2078 submitted and handled by PHP. One user also said that post_max_size
2079 and memory_limit need to be larger than upload_max_filesize.
2080 </p>
2082 <h4>
2083 [1.17] Does phpMyAdmin support MySQL 4.1?
2084 </h4>
2085 <p>
2086 Because of a major change in the definition syntax of string field types,
2087 this version of phpMyAdmin probably won't work correctly with
2088 MySQL >= 4.1.0! We will work on the support as soon as
2089 MySQL 4.1.0 is released.
2090 </p>
2092 <h4>
2093 [1.18] I'm running MySQL <= 4.0.1 having
2094 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2095 capital letter in its name it is changed to lowercase as it should. But
2096 if I try to DROP this table MySQL is unable to find the corresponding
2097 file.
2098 </h4>
2099 <p>
2100 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2101 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2102 directive.
2103 </p>
2105 <h4>
2106 [1.19] I can't run the "display relations" feature because the
2107 script seems not to know the font face I'm using!
2108 </h4>
2109 <p>
2110 The "FPDF" library we're using for this feature requires some
2111 special files to use font faces.<br />
2112 Please refers to the
2114 these files.
2115 </p>
2118 <h4>
2119 [1.20] I receive the error "cannot load MySQL extension, please
2120 check PHP Configuration".
2121 </h4>
2122 <p>
2123 To connect to a MySQL server, PHP needs a set of MySQL functions called
2124 "MySQL extension".
2125 This extension may be part of the PHP server (compiled-in), otherwise it
2126 needs to be loaded dynamically. Its name is probably <i>mysql.so</i> or
2127 <i>mysql.dll</i>. phpMyAdmin tried to load the extension but failed.
2128 <br /><br />
2129 Usually, the problem is solved by installing a software package called
2130 "PHP-MySQL" or something similar.
2131 </p>
2133 <h4>
2134 [1.21] I am running the CGI version of PHP under Unix, and I cannot
2135 login using cookie auth.
2136 </h4>
2137 <p>
2138 In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.
2139 </p>
2141 <h4>
2142 [1.22] I don't see the "Location of text file" field, so
2143 I cannot upload.
2144 </h4>
2145 <p>
2146 This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2147 parameter is not set to "on".
2148 </p>
2150 <h4>
2151 [1.23] I'm running MySQL on a Win32 machine. Each time I create a new
2152 table the table and field names are changed to lowercase!
2153 </h4>
2154 <p>
2155 This happens because the MySQL directive <tt>lower_case_table_names</tt>
2156 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2157 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2158 Just edit you <tt>my.ini</tt> file that should be located in your Windows
2159 directory and add the following line:<br />
2160 <tt>set-variable = lower-case-table-names=0</tt><br />
2161 Next, save the file and restart the MySQL service. You can always check the
2162 value of this directive using the query<br />
2163 <tt>SHOW VARIABLES LIKE 'lower_case_table_names';</tt>
2164 </p>
2166 <h4>
2167 [1.24] Some characters are being truncated in my queries, or I get
2168 characters randomly added. I am running PHP 4.2.3.
2169 </h4>
2170 <p>
2171 This is a
2173 </p>
2175 <h4>
2176 [1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
2177 and I get problems, such as undefined variables when I run a SQL query.
2178 </h4>
2179 <p>
2180 A tip from Jose Fandos: put a comment on the following two lines
2181 in httpd.conf, like this:<br />
2182 <tt># mod_gzip_item_include file \.php$</tt><br />
2184 as this version of mod_gzip on Apache (Windows) has problems handling
2185 PHP scripts. Of course you have to restart Apache.
2186 </p>
2188 <h4>
2189 [1.26] I just installed phpMyAdmin in my document root of IIS but
2190 I get the error "No input file specified" when trying to
2191 run phpMyAdmin.
2192 </h4>
2193 <p>
2194 This is a permission problem. Right-click on the phpmyadmin folder
2195 and choose properties. Under the tab Security, click on "Add"
2196 and select the user "IUSER_machine" from the list. Now set his
2197 permissions and it should work.
2198 </p>
2200 <h4>
2201 [1.27] I get empty page when I want to view huge page (eg.
2202 db_details_structure.php3 with plenty of dabases).
2203 </h4>
2204 <p>
2206 GZIP output buffering enabled. If you turn off it (by <code>$cfg['OBGzip']
2207 = FALSE</code> in config.inc.php3), it should work. This bug will be fixed
2208 in PHP 5.0.0.
2209 </p>
2211 <h4>
2212 [1.28] My MySQL server sometimes refuses queries and returns the message
2213 'Errorcode: 13'. What does this mean?
2214 </h4>
2215 <p>
2216 This can happen due to a MySQL bug when having database / table names with
2217 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2218 To fix this, turn off this directive, convert all database and table names
2219 to lower case and turn it on again. Alternatively, there's a bug-fix
2220 available starting with MySQL 3.23.56 / 4.0.11-gamma.
2221 </p>
2224 <h4>
2225 [1.29] When I create a table or modify a field, I get an error
2226 and the fields are duplicated.
2227 </h4>
2228 <p>
2229 It is possible to configure Apache in such a way that PHP has problems
2230 interpreting .php files.
2231 <br /><br />
2232 The problems occur when two different (and conflicting) set of directives
2233 are used:
2234 <br /><br />
2235 <tt>
2236 SetOutputFilter PHP<br />
2237 SetInputFilter PHP<br />
2238 </tt>
2239 &
2240 <br />
2241 <tt>
2242 AddType application/x-httpd-php .php
2243 </tt>
2244 <br /><br />
2245 In the case we saw, one set of directives was in <tt>httpd.conf</tt>, while
2246 the other set was in <tt>php.conf</tt>.<br />
2247 The recommended way is with <tt>AddType</tt>, so just comment out
2248 the first set of lines and restart Apache:
2249 <br /><br />
2250 <tt><b>
2251 #SetOutputFilter PHP<br />
2252 #SetInputFilter PHP<br /></b>
2253 </tt>
2254 </p>
2257 <h3>[2. Configuration]</h3>
2259 <h4>
2260 [2.1] The error message "Warning: Cannot add header information -
2261 headers already sent by ..." is displayed, what's the problem?
2262 </h4>
2263 <p>
2264 Edit your <i>config.inc.php or .php3</i> file and ensure there is nothing
2265 (I.E. no blank lines, no spaces, no characters...) neither before the
2266 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2267 tag at the end.
2268 </p>
2270 <h4>
2271 [2.2] phpMyAdmin can't connect to MySQL. What's wrong?
2272 </h4>
2273 <p>
2274 Either there is an error with your PHP setup or your username/password is
2275 wrong. Try to make a small script which uses mysql_connect and see if it
2276 works. If it doesn't, it may be you haven't even compiled MySQL support
2277 into PHP.
2278 </p>
2280 <h4>
2281 [2.3] The error message "Warning: MySQL Connection Failed: Can't
2282 connect to local MySQL server through socket '/tmp/mysql.sock'
2283 (111)..." is displayed. What can I do?
2284 </h4>
2285 <p><br />
2286 For RedHat users, Harald Legner suggests this on the mailing list:
2287 <br /><br />
2288 On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2289 In your php.ini you will find a line
2290 <br />
2291 <tt>mysql.default_socket = /tmp/mysql.sock</tt>
2292 <br />
2293 change it to
2294 <br />
2295 <tt>mysql.default_socket = /var/lib/mysql/mysql.sock</tt>
2296 <br />
2297 Then restart apache and it will work.
2298 <br /><br />
2299 Here is a fix suggested by Brad Ummer in the phpwizard forum:
2300 </p>
2301 <ul>
2302 <li>
2303 First, you need to determine what socket is being used by MySQL.
2304 <br />
2305 To do this, telnet to your server and go to the MySQL bin directory. In
2306 this directory there should be a file named <i>mysqladmin</i>. Type
2307 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2308 info about your MySQL server, including the socket
2309 (<i>/tmp/mysql.sock</i>, for example).
2310 </li>
2311 <li>
2312 Then, you need to tell PHP to use this socket.<br />Assuming you are
2313 using PHP 3.0.10 or better, you can specify the socket to use when you
2314 open the connection. To do this in phpMyAdmin, you need to complete the
2315 socket information in the config.inc.php3.<br />
2316 For example:
2317 <tt>$cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</tt>
2318 </li>
2319 </ul>
2320 <p>
2321 Have also a look at the
2323 corresponding section of the MySQL documentation</a>.
2324 </p>
2326 <h4>
2327 [2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
2328 what can I do?
2329 </h4>
2330 <p>
2331 Try to set the <tt>$cfg['OBGZip']</tt> directive to <tt>FALSE</tt> in the
2332 phpMyAdmin configuration file. It helps sometime.<br />
2333 Also have a look at your PHP version number: if it contains
2334 "4.0b..." it means you're running a beta version of PHP. That's
2335 not a so good idea, please upgrade to a plain revision.
2336 </p>
2338 <h4>
2339 [2.5] Each time I want to insert or change a record or drop a database
2340 or a table, an error 404 (page not found) is displayed or, with HTTP or
2341 cookie authentication, I'm asked to login again. What's wrong?
2342 </h4>
2343 <p>
2344 Check the value you set for the <tt>$cfg['PmaAbsoluteUri']</tt> directive
2345 in the phpMyAdmin configuration file.
2346 </p>
2348 <h4>
2349 [2.6] I get an "Access denied for user: 'root@localhost' (Using
2350 password: YES)"-error when trying to access a MySQL-Server on a
2351 host which is port-forwarded for my localhost
2352 </h4>
2353 <p>
2354 When you are using a port on your localhost, which you redirect via
2355 port-forwarding to another host, MySQL is not resolving the localhost
2356 as expected.<br />
2357 Erik Wasser explains: The solution is: if your host is "localhost"
2358 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2359 connection for speeding up things. And that doesn't work in this configuration
2360 with port forwarding.<br />
2362 TCP connection.
2363 </p>
2367 <h3>[3. Known limitations]</h3>
2369 <h4>
2370 [3.1] When using HTTP authentication, an user who logged out can not
2371 relogin in with the same nick.
2372 </h4>
2373 <p>
2374 This is related to the authentication mechanism (protocol) used by
2375 phpMyAdmin. We plan to change it as soon as we may find enough free time
2376 to do it, but you can bypass this problem: just close all the opened
2377 browser windows and then go back to phpMyAdmin. You should be able to
2378 log in again.
2379 </p>
2381 <h4>
2382 [3.2] When dumping a large table in compressed mode, I get a memory
2383 limit error or a time limit error.
2384 </h4>
2385 <p>
2386 As of version 2.2.4, we build the compressed dump in memory, so large
2387 tables dumps may hang. The only alternative we can think about (using
2388 system calls to mysqldump then gzip or bzip2) would not be applicable in
2389 environments where PHP is in safe mode: access to system programs is
2390 is limited by the system administrator, and time limit is enforced.
2391 </p>
2393 <h4>
2394 [3.3] With InnoDB tables, I lose foreign key relationships when I rename
2395 or alter a table.
2396 </h4>
2397 <p>
2398 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in
2399 mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
2400 </p>
2402 <h4>
2403 [3.4] I am unable to import dumps I created with the mysqldump tool
2404 bundled with the MySQL server distribution.
2405 </h4>
2406 <p>
2407 The problem is that mysqldump creates invalid comments like this:
2408 </p>
2409 <pre>
2410 -- MySQL dump 8.22
2411 --
2412 -- Host: localhost Database: database
2413 ---------------------------------------------------------
2414 -- Server version 3.23.54
2415 </pre>
2416 <p>
2417 The invalid part of the code is the horizontal line made of dashes that
2418 appears once in every dump created with mysqldump. If you want to run your
2419 dump you have to turn it into valid MySQL. This means, you have to add a
2420 whitespace after the first to dashes of the line or add a # before it:
2421 <br />
2422 <code>
2423 -- -------------------------------------------------------<br />
2424 </code>
2425 or<br />
2426 <code>
2427 #---------------------------------------------------------
2428 </code>
2429 </p>
2433 <h3>[4. ISPs, multi-user installations ]</h3>
2435 <h4>
2436 [4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
2437 need to install it for each customer.
2438 </h4>
2439 <p>
2440 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
2441 your users. The development of this feature was kindly sponsored by
2442 NetCologne GmbH.
2443 This requires a properly setup MySQL user management and phpMyAdmin
2444 HTTP or cookie authentication. See the install section on
2445 "Using HTTP authentication".
2446 </p>
2448 <h4>
2449 [4.2] What's the preferred way of making phpMyAdmin secure against evil
2450 access.
2451 </h4>
2452 <p>
2453 This depends on your system.<br />
2454 If you're running a server which cannot be accessed by other people, it's
2455 sufficient to use the directory protection bundled with your webserver
2456 (with Apache you can use <i>.htaccess</i> files, for example).<br />
2457 If other people have telnet access to your server, you should use
2458 phpMyAdmin's HTTP authentication feature.
2459 <br /><br />
2460 Suggestions:
2461 </p>
2462 <ul>
2463 <li>
2464 Your <i>config.inc.php3</i> file should be <tt>chmod 660</tt>.
2465 </li>
2466 <li>
2467 All your phpMyAdmin files should be chown phpmy.apache, where phpmy
2468 is a user whose password is only known to you, and apache is the
2469 group under which Apache runs.
2470 </li>
2471 <li>
2472 You should use PHP safe mode, to protect from other users that try
2473 to include your <i>config.inc.php3</i> in their scripts.
2474 </li>
2475 </ul>
2477 <h4>
2478 [4.3] I get errors about not being able to include a file in
2479 <i>/lang</i> or in <i>/libraries</i>.
2480 </h4>
2481 <p>
2482 Check <i>php.ini</i>, or ask your sysadmin to check it. The
2483 <tt>include_path</tt> must contain "." somewhere in it, and
2484 <tt>open_basedir</tt>, if used, must contain "." and
2485 "./lang" to allow normal operation of phpMyAdmin.
2486 </p>
2487 <h4>
2488 [4.4] phpMyAdmin always gives "Access denied" when using HTTP
2489 authentication.
2490 </h4>
2491 <p>
2492 This could happen for several reasons:
2493 </p>
2494 <ul>
2495 <li>
2496 <tt>$cfg['Servers'][$i]['controluser']</tt> and/or
2497 <tt>$cfg['Servers'][$i]['controlpass']</tt> are wrong.
2498 </li>
2499 <li>
2500 The username/password you specify in the login-dialog are invalid.
2501 </li>
2502 <li>
2503 You have already setup a security mechanism for the
2504 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
2505 phpMyAdmin's authentication, so remove it.
2506 </li>
2507 </ul>
2509 <h4>
2510 [4.5] Is it possible to let users create their own databases?
2511 </h4>
2512 <p>
2513 Starting with 2.2.5, in the user management page, you can enter a wildcard
2514 database name for a user, and put the privileges you want. For example,
2515 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
2516 would let a user create/manage his/her database(s).
2517 </p>
2519 <h4>
2520 [4.6] How can I use the Host-based authentication additions?
2521 </h4>
2522 <p>
2523 If you have existing rules from an old .htaccess file, you can take them
2524 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
2525 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
2526 be a major benefit here if your installation is suited to using it. Then
2527 you can just add those updated lines into the
2528 <tt>$cfg['Servers'][$i]['AllowDeny']['rules']</tt> array.
2529 <br /><br />
2530 If you want a pre-made sample, you can try this fragment. It stops the
2531 'root' user from logging in from any networks other than the private
2532 network IP blocks.
2533 <br />
2534 <tt>
2535 //block root from logging in except from the private networks<br />
2536 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';<br />
2537 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(<br />
2538 'deny root from all',<br />
2539 'allow root from localhost',<br />
2540 'allow root from 10.0.0.0/8',<br />
2541 'allow root from 192.168.0.0/16',<br />
2542 'allow root from 172.16.0.0/12',<br />
2543 );
2544 </tt>
2545 </p>
2548 <h3>[5. Browsers or client OS]</h3>
2550 <h4>
2551 [5.1] I get an out of memory error, and my controls are non-functional,
2552 when trying to create a table with more than 14 fields.
2553 </h4>
2554 <p>
2555 We could reproduce this problem only under Win98/98SE. Testing under
2556 WinNT4 or Win2K, we could easily create more than 60 fields.
2557 <br />
2558 A workaround is to create a smaller number of fields, then come back to
2559 your table properties and add the other fields.
2560 </p>
2562 <h4>
2563 [5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.
2564 </h4>
2565 <p>
2566 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
2567 with each script/website that use forms.<br />
2568 Upgrade or downgrade your Xitami server.
2569 </p>
2571 <h4>
2572 [5.3] I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).
2573 </h4>
2574 <p>
2575 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
2576 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
2577 don't seem to work.<br />
2579 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
2580 the user's temporary directory, so they must be moved before closing
2581 Konqueror, or else they disappear. GZip dumps give an error message.<br />
2583 Testing needs to be done for Konqueror 2.2.2.<br />
2584 </p>
2586 <h4>
2587 [5.4] I can't use the cookie authentication mode because Internet
2588 Explorer never stores the cookies.
2589 </h4>
2590 <p>
2591 MS Internet Explorer seems to be really buggy about cookies, at least till
2592 version 6. And thanks to Andrew Zivolup we've traced also a PHP 4.1.1 bug
2593 in this area!
2594 <br />
2595 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
2596 work!
2597 </p>
2599 <h4>
2600 [5.5] In Internet Explorer 5.0, I get JavaScript errors when browsing my
2601 rows.
2602 </h4>
2603 <p>
2604 Upgrade to at least Internet Explorer 5.5 SP2.<br />
2605 </p>
2607 <h4>
2608 [5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying
2609 to modify a row in a table with many fields, or with a text field
2610 </h4>
2611 <p>
2612 Your table neither have a primary key nor an unique one, so we must use a
2613 long URL to identify this row. There is a limit on the length of the URL in
2614 those browsers, and this not happen in Netscape, for example. The
2615 workaround is to create a primary or unique key, or use another browser.
2616 <br />
2617 </p>
2619 <h4>
2620 [5.7] I refresh (reload) my browser, and come back to the welcome
2621 page.
2622 </h4>
2623 <p>
2624 Some browsers support right-clicking into the frame you want to refresh,
2625 just do this in the right frame.<br />
2626 </p>
2628 <h4>
2629 [5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
2630 query box.
2631 </h4>
2632 <p>
2633 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
2634 Mozilla versions.<br />
2635 </p>
2637 <h4>
2638 [5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
2639 whitespace in the SQL-Query edit area: the page scrolls down.
2640 </h4>
2641 <p>
2642 This is a Mozilla bug (see bug #26882 at
2644 </p>
2646 <h4>
2647 [5.10] With Netscape 4.75 I get empty rows between each row of data in a
2648 CSV exported file.
2649 </h4>
2650 <p>
2651 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
2652 data in octet-stream mode. Since we can't detect the specific Netscape
2653 version, we cannot workaround this bug.
2654 </p>
2656 <h4>
2657 [5.11] Extended-ASCII characters like German umlauts are displayed
2658 wrong.
2659 </h4>
2660 <p>
2661 Please ensure that you have set your browser's character set to the one of the
2662 language file you have selected on phpMyAdmin's start page.
2663 Alternatively, you can try the auto detection mode that is supported by the
2664 recent versions of the most browsers.
2665 </p>
2667 <h4>
2668 [5.12] Apple OS X: Safari browser changes special characters to
2669 "?".
2670 </h4>
2671 <p>
2672 This issue has been reported by a OS X user, who adds that Chimera,
2673 Netscape and Mozilla do not have this problem.
2674 </p>
2676 <h4>
2677 [5.13] With Internet Explorer 5.5 or 6, and HTTP authentication type,
2678 I cannot manage two servers: I login to the first one, then the other one,
2679 but if I switch back to the first, I have to login on each operation.
2680 </h4>
2681 <p>
2682 This is a bug in Internet Explorer, other browsers do not behave this way.
2683 </p>
2686 <h3>[6. Using phpMyAdmin]</h3>
2688 <h4>
2689 [6.1] I can't insert new rows into a table / I can't create a table
2690 - MySQL brings up a SQL-error.
2691 </h4>
2692 <p>
2693 Examine the SQL error with care. Often the problem is caused by
2694 specifying a wrong field-type.<br />
2695 Common errors include:
2696 </p>
2697 <ul>
2698 <li>Using <tt>VARCHAR</tt> without a size argument</li>
2699 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
2700 </ul>
2701 <p>
2702 Also, look at the syntax chapter in the MySQL manual to confirm that your
2703 syntax is correct.
2704 </p>
2706 <h4>
2707 [6.2] When I create a table, I click the Index checkbox for 2 fields and
2708 phpMyAdmin generates only one index with those 2 fields.
2709 </h4>
2710 <p>
2711 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
2712 index. If you want two indexes, create the first one when creating the
2713 table, save, then display the table properties and click the Index link to
2714 create the other index.
2715 </p>
2717 <h4>
2718 [6.3] How can I insert a null value into my table?
2719 </h4>
2720 <p>
2721 Since version 2.2.3, you have a checkbox for each field that can be null.
2722 Before 2.2.3, you had to enter "null", without the quotes, as the
2723 field's value.
2724 </p>
2726 <h4>
2727 [6.4] How can I backup my database or table?
2728 </h4>
2729 <p>
2730 Click on a database or table name in the left frame, the properties will be
2731 displayed. Then on the menu, click "Export", you can dump
2732 the structure, the data, or both. This will generate standard SQL
2733 statements that can be used to recreate your database/table.
2734 <br /><br />
2735 You will need to choose "Save as file", so that phpMyAdmin can
2736 transmit the resulting dump to your station. Depending on your PHP
2737 configuration, you will see options to compress the dump. See also the
2738 <tt>$cfg['ExecTimeLimit']</tt> configuration variable.
2739 <br /><br />
2740 For additional help on this subject, look for the word "dump" in
2741 this document.
2742 </p>
2744 <h4>
2745 [6.5] How can I restore (upload) my database or table using a dump?
2746 How can I run a ".sql" file.
2747 </h4>
2748 <p>
2749 Click on a database name in the left frame, the properties will be
2750 local displayed. Then in the "Run SQL query" section, type in
2751 your dump filename, or use the Browse button. Then click Go.
2752 <br /><br />
2753 For additional help on this subject, look for the word "upload"
2754 in this document.
2755 </p>
2757 <h4>
2758 [6.6] How can I use the relation table in Query-by-example?
2759 </h4>
2760 <p>
2761 Here is an example with the tables persons, towns and countries, all
2762 located in the database mydb. If you don't have a <tt>PMA_relation</tt>
2763 table, create it as explained in the configuration section. Then create the
2764 example tables:
2765 <br /><br />
2766 <tt>
2767 CREATE TABLE REL_countries (<br />
2768 country_code char(1) NOT NULL default '',<br />
2769 description varchar(10) NOT NULL default '',<br />
2770 PRIMARY KEY (country_code)<br />
2771 ) TYPE=MyISAM;<br />
2772 <br />
2773 INSERT INTO REL_countries VALUES ('C', 'Canada');<br />
2774 <br />
2775 CREATE TABLE REL_persons (<br />
2776 id tinyint(4) NOT NULL auto_increment,<br />
2777 person_name varchar(32) NOT NULL default '',<br />
2778 town_code varchar(5) default '0',<br />
2779 country_code char(1) NOT NULL default '',<br />
2780 PRIMARY KEY (id)<br />
2781 ) TYPE=MyISAM;<br />
2782 <br />
2783 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');<br />
2784 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');<br />
2785 <br />
2786 CREATE TABLE REL_towns (<br />
2787 town_code varchar(5) NOT NULL default '0',<br />
2788 description varchar(30) NOT NULL default '',<br />
2789 PRIMARY KEY (town_code)<br />
2790 ) TYPE=MyISAM;<br />
2791 <br />
2792 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');<br />
2793 INSERT INTO REL_towns VALUES ('M', 'Montréal');<br />
2794 <br />
2795 </tt>
2796 To setup appropriate links and display information:
2797 </p>
2798 <ul>
2799 <li>on table "REL_persons" click Structure, then Relation view</li>
2800 <li>in Links, for "town_code" choose "REL_towns->code"</li>
2801 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
2802 <li>on table "REL_towns" click Structure, then Relation view</li>
2803 <li>in "Choose field to display", choose "description"</li>
2804 <li>repeat the two previous steps for table "REL_countries"</li>
2805 </ul>
2807 <p>
2808 Then test like this:
2809 </p>
2810 <ul>
2811 <li>Click on your db name in the left frame</li>
2812 <li>Choose "Query"</li>
2813 <li>Use tables: persons, towns, countries</li>
2814 <li>Click "Update query"</li>
2815 <li>In the fields row, choose persons.person_name and click the
2816 "Show" tickbox </li>
2817 <li>Do the same for towns.description and countries.descriptions in the
2818 other 2 columns</li>
2819 <li>Click "Update query" and you will see in the query box that
2820 the correct joins have been generated</li>
2821 <li>Click "Submit query"</li>
2822 </ul>
2823 <br />
2826 <h4>
2827 [6.7] How can I use the "display field" feature?
2828 </h4>
2829 <p>
2830 Starting from the previous example, create the PMA_table_info as explained
2831 in the configuration section, then browse your persons table,
2832 and move the mouse over a town code or country code.
2833 </p>
2836 <h4>
2837 [6.8] How can I produce a PDF schema of my database?
2838 </h4>
2839 <p>
2840 First you have to fill the "relation", "table_coords"
2841 and "pdf_pages" configuration variables.
2842 <br /><br />
2843 Then, think about your schema layout: which tables will go on which pages.
2844 </p>
2845 <ul>
2846 <li>Click on your db name in the left frame</li>
2847 <li>Choose "Structure" in the navigation on top</li>
2848 <li>Choose "Edit PDF Pages" which should be somewhere at the
2849 bottom of the page</li>
2850 <li>Enter the name for a first pdf page and submit</li>
2851 <li>Choose this page to edit</li>
2852 <li>Now add a table you want to show on this page and it's coordinates and
2853 submit<br />
2854 First you will have to guess this coordinates of course, so just expect
2855 to have an area of about 297 * 210 and put the tables coordinates
2856 somewhere in there, you will be able to have a look at what happened
2857 and change them later.<br />
2858 For example, x=100 and y=200 means that the table will be at 200 mm
2859 down and 100 mm right from the upper left corner.<br />
2860 Actually if you have a width of more than 300 or a height of more than
2861 200 than it will automatically be scaled but 300*100 is a good start to
2862 have an idea of what coordinates to use.</li>
2863 <li>After every table you submitted you will have the possibility to submit
2864 more tables</li>
2865 <li>When you have entered enough tables Click on your db name in the left
2866 frame again</li>
2867 <li>Now, again at the bottom of the page you should be able to choose
2868 "Display PDF schema"<br />
2869 For testing it might be useful to show the grid as well, so you can see
2870 the coordinates used.<br />
2871 Maybe also choose color and submit.</li>
2872 <li>Save the file he will offer you to something like <i>Schema.pdf</i>
2873 (Internet Explorer has some bug there which might make it offer it
2874 without an extension. Under Windows it is important to have the
2875 extension ".pdf", under other OSes you should be fine just
2876 saving the file under the name it offers).</li>
2877 </ul>
2879 <h4>
2880 [6.9] phpMyAdmin is changing the type of one of my columns!
2881 </h4>
2882 <p>
2883 No, it's MySQL that is doing
2884 <a href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent column type changing</a>.
2885 </p>
2888 <h4>
2889 [6.10] My database has an underscore in it's name, and when I grant
2890 privileges to a user for this database, a backslash is added before the
2891 underscore.
2892 </h4>
2893 <p>
2894 This is normal and means that the grant is done only for this database. If
2895 there was no backslash, this would be a wildcard grant, and the
2896 underscore would mean "any character". So, if the database name
2897 is "john_db", the user would get rights to john1db, john2db...
2898 instead of just john_db.<br /><br />
2899 If you really want to grant using a wildcard, there is a dialog box "
2900 Database (wildcards allowed)" for this.
2901 </p>
2903 <h4>
2904 [6.11] What is the curious symbol ø in the statistics pages?
2905 </h4>
2906 <p>
2907 It means "average".
2908 </p>
2911 <h4>
2912 [6.12] I want to understand some Export options.
2913 </h4>
2914 <p>
2915 "Complete inserts" adds the column names on every INSERT command,
2916 for better documentation (but resulting file is bigger).<br />
2917 "Extended inserts" provides a shorter dump file by using only
2918 once the INSERT verb and the table name.<br />
2919 "Enclose table and field names with backquotes" ensures that
2920 field and table names formed with special characters are protected.<br />
2921 "Include column comments as inline SQL-comments" includes any
2922 column comments set in the PMA-DB in the dump as SQL comments (<i>/* xxx */</i>).<br /></p>
2924 <h4>
2925 [6.13] I would like to create a database with a dot in its name.
2926 </h4>
2927 <p>
2928 This is a bad idea, because in MySQL the syntax "database.table"
2929 is the normal way to reference a database and table name. Worse, MySQL
2930 will usually let you create a database with a dot, but then you cannot
2931 work with it, nor delete it.<br />
2932 </p>
2935 <h4>
2936 [6.14] How do I set up the SQL Validator?
2937 </h4>
2938 <p>
2939 To use it, you need a very recent version of PHP, 4.3.0 recommended, with
2940 XML, PCRE and PEAR support. On your system command line, run
2941 <tt>"pear install Net_Socket Net_URL HTTP_Request Mail_Mime Net_DIME
2942 SOAP"</tt> to get the necessary PEAR modules for usage.
2943 <br />
2944 If you use it, you should be aware that any SQL statement you
2945 submit will be stored anonymously (database/table/column names,
2946 strings, numbers replaced with generic values). The Mimer SQL
2947 Validator itself, is © 2001 Upright Database Technology.
2948 We utilize it as free SOAP service.
2949 </p>
2951 <h4>
2952 [6.15] I want to add a BLOB field and put an index on it, but MySQL
2953 says "BLOB column '...' used in key specification without a key
2954 length".
2955 </h4>
2956 <p>
2957 The right way to do this, is to create the field without any indexes,
2958 then display the table structure and use the "Create an index"
2959 dialog. On this page, you will be able to choose your BLOB field, and
2960 set a size to the index, which is the condition to create an index on
2961 a BLOB field.
2962 <br />
2963 </p>
2965 <h4>
2966 [6.16] How can I simply move in page with plenty editing fields?
2967 </h4>
2968 <p>
2969 You can use Ctrl+arrows for moving on most pages with plenty editing
2970 fields (table structure changes, row editing, etc.). You can also have
2971 a look at the directive $cfg['DefaultPropDisplay'] ('vertical') and see
2972 if this eases up editing for you.
2973 <br />
2974 </p>
2976 <h4>
2977 [6.17] Transformations: I can't enter my own mimetype! WTF is this feature
2978 then useful for?
2979 </h4>
2980 <p>
2981 Slow down :). Defining mimetypes is of no use, if you can't put transformations on them.
2982 Otherwise you could just put a comment on the field. Because entering your own mimetype will
2983 cause serious syntax checking issues and validation, this introduces a high-risk false-user-input
2984 situation. Instead you have to initialize mimetypes using functions or empty mimetype definitions.
2985 <br />
2986 Plus, you have a whole overview of available mimetypes. Who knows all those mimetypes by heart so
2987 he/she can enter it at will?
2988 <br />
2989 </p>
2992 <h4>
2993 [6.17] Bookmarks: Where can I store bookmarks? Why can't I see any bookmarks below the query box?
2994 What is this variable for?
2995 </h4>
2996 <p>
2997 Any query you have executed can be stored as a bookmark on the page where the results are displayed.
2998 You will find a button labeled 'Bookmark this query' just at the end of the page.<br />
2999 As soon as you have stored a bookmark, it is related to the database you run the query on. You can
3000 now access a bookmark dropdown on each page, the query box appears on for that database.<br />
3001 <br />
3002 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks. Just use the string
3003 <b>/*[VARIABLE]*/</b> anywhere in your query. Everything which is put into the <i>value</i> input
3004 box on the query box page will replace the string "/*[VARIABLE]*/" in your stored query.
3005 Just be aware of that you HAVE to create a valid query, otherwise your query won't be even able to be
3006 stored in the database.<br />
3007 Also remember, that everything else inside the <b>/*[VARIABLE]*/</b> string for your query will remain
3008 the way it is, but will be stripped of the /**/ chars. So you can use:<br /><br />
3009 <code>/*, [VARIABLE] AS myname */</code><br /><br />
3010 which will be expanded to<br /><br />
3011 <code>, VARIABLE as myname</code><br /><br />
3012 in your query, where VARIABLE is the string you entered in the input box. If an empty string is
3013 provided, no replacements are made.<br />
3014 <br />
3015 A more complex example. Say you have stored this query:<br /><br />
3016 <code>SELECT Name, Address FROM addresses WHERE 1 /* AND Name LIKE '%[VARIABLE]%' */</code><br /><br />
3017 Say, you now enter "phpMyAdmin" as the variable for the stored query, the full query will
3018 be:<br /><br />
3019 <code>SELECT Name, Address FROM addresses WHERE 1 AND Name LIKE '%phpMyAdmin%'</code>
3020 <br />
3021 <br />
3022 You can use multiple occurences of <b>/*[VARIABLE]*/</b> in a single query.<br />
3023 <b>NOTE THE ABSENCE OF SPACES</b> inside the "/**/" construct. Any spaces inserted there
3024 will be later also inserted as spaces in your query and may lead to unexpected results especially when
3025 using the variable expansion inside of a "LIKE ''" expression.<br />
3026 Your initial query which is going to be stored as a bookmark has to yield at least one result row so
3027 you can store the bookmark. You may have that to work around using well positioned "/**/"
3028 comments.
3029 </p>
3032 <h3>[7. phpMyAdmin project]</h3>
3034 <h4>
3035 [7.1] I have found a bug. How do I inform developers?
3036 </h4>
3037 <p>
3038 Our Bug Tracker is located at
3039 <a href="http://sourceforge.net/projects/phpmyadmin/">http://sourceforge.net/projects/phpmyadmin/</a>
3040 under the Bugs section.
3041 <br /><br />
3042 But please first discuss your bug with other users:
3043 <br />
3045 http://sourceforge.net/projects/phpmyadmin/</a> (and choose Forums)
3046 </p>
3048 <h4>
3049 [7.2] I want to translate the messages to a new language or upgrade an
3050 existing language, where do I start?
3051 </h4>
3052 <p>
3053 Always use the current CVS version of your language file.
3054 For a new language, start from <i>english-iso-8859-1.inc.php3</i>. If you
3055 don't know how to get the CVS version, please ask one of the developers.
3056 <br />
3057 Please note that we try not to use HTML entities like &eacute; in
3058 the translations, since we define the right character set in the file.
3059 With HTML entities, the text on JavaScript messages would not
3060 display correctly.
3061 However there are some entities that need to be there, for quotes
3062 ,non-breakable spaces, ampersands, less than, greater than.
3063 <br />
3064 You can then put your translations, as a zip file to avoid losing special
3065 characters, on the sourceforge.net translation tracker.
3066 <br />
3067 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3068 list, because this is where we ask for translations of new messages.
3069 <br />
3070 </p>
3072 <h4>
3073 [7.3] I would like to help out with the development of phpMyAdmin. How
3074 should I proceed?
3075 </h4>
3076 <p>
3077 The following method is preferred for new developers:
3078 </p>
3079 <ol>
3080 <li>
3081 fetch the current CVS tree over anonymous CVS:<br />
3082 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
3083 [Password: simply press the Enter key]<br />
3084 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
3085 [This will create a new sub-directory named phpMyAdmin]
3086 </li>
3087 <li>
3088 add your stuff
3089 </li>
3090 <li>
3091 put the modified files (tar'ed and gzip'ed) inside the patch tracker of
3092 the
3093 <a href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">phpMyAdmin SourceForge account</a>.
3094 </li>
3095 </ol>
3096 <p>
3097 Write access to the CVS tree is granted only to experienced developers who
3098 have already contributed something useful to phpMyAdmin.<br />
3099 Also, have a look at the
3101 </p>
3103 <!-- DEVELOPERS -->
3105 <h2>Developers Information</h2>
3107 <p>
3108 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3109 great features have been written by other people and you too can help to
3110 make phpMyAdmin a useful tool.
3111 </p>
3113 <p>
3114 If you're planning to contribute source, please read the following
3115 information:
3116 </p>
3117 <ul>
3118 <li>
3119 All files include <i>header.inc.php3</i> (layout),
3120 <i>libraries/common.lib.php3</i> (common functions) and
3121 <i>config.inc.php3</i>.
3122 <br />
3123 All configuration data belongs in <i>config.inc.php3</i>. Please keep
3124 it free from other code.
3125 <br />
3126 Commonly used functions should be added to
3127 <i>libraries/common.lib.php3</i> and more specific ones may be added
3128 within a library stored into the <i>libraries</i> sub-directory.
3129 </li>
3130 <li>
3131 Obviously, you're free to use whatever coding style you want. But
3132 please try to keep your code as simple as possible: beginners are
3133 using phpMyAdmin as an example application.<br />
3134 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3135 compliant on one hand, they fit the
3137 on the other hand. Please pay attention to this.
3138 </li>
3139 <li>
3140 Please try to keep up the file-naming conventions. Table-related stuff
3141 goes to <i>tbl_*.php3</i>, db-related code to <i>db_*.php3</i>,
3142 server-related tools to <i>server_*.php3</i> and so on.
3143 </li>
3144 <li>
3145 Please don't use verbose strings in your code, instead add the string
3146 (at least) to <i>english-iso-8859-1.inc.php3</i> and print() it out.
3147 </li>
3148 <li>
3149 If you want to be really helpful, write an entry for the ChangeLog.
3150 </li>
3153 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3154 better debug and profile their code.<br />
3155 Please see the <tt>$cfg['DBG']*</tt> configuration options for more
3156 information.<br />
3157 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3158 lost during its re-entry into Earth's atmosphere and in memory of the
3159 brave men and women who gave their lives for the people of Earth.
3160 </li>
3162 </ul>
3164 <!-- CREDITS -->
3166 <h2>Credits</h2>
3168 <pre>
3170 phpMyAdmin - Credits
3171 ====================
3173 CREDITS, in chronological order
3174 -------------------------------
3176 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
3177 * creator of the phpmyadmin project
3178 * maintainer from 1998 to summer 2000
3180 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
3181 * multi-language version
3182 * various fixes and improvements
3183 * project co-administrator
3185 - Olivier Müller <om_at_omnis.ch>
3186 * started SourceForge phpMyAdmin project in March 2001
3187 * sync'ed different existing CVS trees with new features and bugfixes
3188 * multi-language improvements, dynamic language selection
3189 * current project maintainer
3190 * many bugfixes and improvements
3192 - Loïc Chapeaux <lolo_at_phpheaven.net>
3193 * rewrote and optimized javascript, DHTML and DOM stuff
3194 * rewrote the scripts so they fit the PEAR coding standards and
3195 generate XHTML1.0 and CSS2 compliant codes
3196 * improved the language detection system
3197 * many bugfixes and improvements
3199 - Robin Johnson <robbat2_at_users.sourceforge.net>
3200 * database maintence controls
3201 * table type code
3202 * Host authentication IP Allow/Deny
3203 * DB-based configuration (Not completed)
3204 * SQL parser
3205 * SQL validator
3206 * many bugfixes and improvements
3208 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
3209 * bookmarks feature
3210 * multiple dump feature
3211 * gzip dump feature
3212 * zip dump feature
3214 - Geert Lund <glund_at_silversoft.dk>
3215 * various fixes
3216 * moderator of the phpMyAdmin users forum at phpwizard.net
3218 - Korakot Chaovavanich <korakot_at_iname.com>
3219 * "insert as new row" feature
3221 - Pete Kelly <webmaster_at_trafficg.com>
3222 * rewrote and fix dump code
3223 * bugfixes
3225 - Steve Alberty <alberty_at_neptunlabs.de>
3226 * rewrote dump code for PHP4
3227 * mySQL table statistics
3228 * bugfixes
3230 - Benjamin Gandon <gandon_at_isia.cma.fr>
3231 * main author of the version 2.1.0.1
3232 * bugfixes
3234 - Alexander M. Turek <rabus_at_bugfixes.info>
3235 * XML exports
3236 * MySQL 4 related features
3237 * various small features and fixes
3238 * German language file updates
3240 - Mike Beck <mike.beck_at_ibmiller.de>
3241 * automatic joins in QBE
3242 * links column in printview
3243 * Relation view
3245 - Michal Cihar <nijel_at_users.sourceforge.net>
3246 * enhanced index creation/display feature
3247 * feature to use a different charset for HTML than for MySQL
3248 * Czech language file updates
3250 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
3251 (http://sourceforge.net/projects/phpmysqlformgen/)
3252 * suggested the patch for multiple table printviews
3254 - Garvin Hicking <hicking_at_faktor-e.de>
3255 * built the patch for vertical display of table rows
3256 * built the Javascript based Query window + SQL history
3257 * Improvement of column/db comments
3258 * (MIME)-Transformations for columns
3259 * Use custom alias names for Databases in left frame
3260 * vertical display of column properties page
3261 * some bugfixes, smaller features
3263 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
3264 * japanese kanji encoding conversion feature
3266 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
3267 * the Cookie authentication mode
3269 - Axel Sander <n8falke_at_users.sourceforge.net>
3270 * table relation-links feature
3272 - Maxime Delorme <delorme.maxime_at_free.fr>
3273 * PDF schema output, thanks also to Olivier Plathey for the
3274 "FPDF" library (see http://www.fpdf.org/).
3276 - Olof Edlund <olof.edlund_at_upright.se>
3277 * SQL validator server
3279 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
3280 * phpMyAdmin logo
3282 And also to the following people who have contributed minor changes,
3283 enhancements, bugfixes or support for a new language since version 2.1.0:
3285 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
3286 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
3287 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
3288 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
3289 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
3290 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
3291 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
3292 Luís V., Martijn W. van der Lee,
3293 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
3294 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas, "Manuzhai".
3297 Original Credits of Version 2.1.0
3298 ---------------------------------
3300 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
3301 to create a web-based interface to MySQL using PHP3. Although I have not
3302 used any of his source-code, there are some concepts I've borrowed from
3303 him. phpMyAdmin was created because Peter told me he wasn't going to
3304 further develop his (great) tool.
3305 Thanks go to
3306 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
3307 code for the check when dropping a table or database. He also suggested
3308 that you should be able to specify the primary key on tbl_create.php3. To
3309 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
3310 well as a bug-report. Plus many smaller improvements.
3311 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
3312 were introduced in 1.3.0 (including quite significant ones like the
3313 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
3314 bug-fixes and help.
3315 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
3316 language-independent by outsourcing the strings to a separate file. He
3317 also contributed the French translation.
3318 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
3319 tbl_select.php3, a feature to display only some fields from a table.
3320 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
3321 functions in tbl_change.php3. He also added the
3322 "Query by Example" feature in 2.0.
3323 - Dave Walton <walton_at_nordicdms.com> added support for multiple
3324 servers and is a regular contributor for bug-fixes.
3325 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
3326 features for 2.0.6.
3327 The following people have contributed minor changes, enhancements, bugfixes
3328 or support for a new language:
3329 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
3330 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
3331 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
3332 G. Wieggers.
3334 And thanks to everyone else who sent me email with suggestions, bug-reports
3335 and or just some feedback.
3336 </pre>
3343 <img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" border="0" height="31" width="88" /></a>
3344
3346 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" border="0" width="88" height="31" /></a>
3347 </p>
3349 </body>
3350 </html>