| blob | b05867bf77a37198c62327b6921d2fd9ac680bf2 |
4 <!-- $Id$ -->
6 <head>
10 <!--
17 }
21 }
28 }
32 }
33 h1 {
38 }
43 }
44 body {
47 }
48 td {
51 }
52 ul {
55 }
56 ol {
59 }
60 p {
63 }
64 h2 {
70 }
71 //-->
72 </style>
73 </head>
80 <!-- TOP MENU -->
81 <ul>
82 <li>
85 </li>
86 <li>
87 Local documents:
88 <ul>
92 </ul>
93 </li>
94 <li>
95 Documentation version:
97 </li>
98 </ul>
101 <!-- REQUIREMENTS -->
113 </font>
118 <ul>
119 <li>
120 PHP3 or PHP4: phpMyAdmin widely uses the 'str_replace()' php function
126 support</font>;
127 </li>
128 <li>
131 syntax of string field types, this version of phpMyAdmin probably won't
133 </li>
134 <li>
135 a web-browser (doh!).
136 </li>
137 </ul>
140 <!-- INTRODUCTION -->
152 </font>
157 <p>
158 phpMyAdmin can manage a whole MySQL-server (needs a super-user)
159 but also a single database. To accomplish the latter you'll need
160 a properly set up MySQL-user who can read/write only the desired
161 database. It's up to you to look up the appropriate part in the
162 MySQL manual. Currently phpMyAdmin can:
163 </p>
165 <ul>
178 <li>
179 communicate in more than
181 </li>
182 </ul>
185 <tr>
187 <td>
188 phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dumps
191 </td>
192 </tr>
193 </table>
196 <!-- INSTALLATION -->
208 </font>
213 <p>
215 methods to the MySQL database server. It is still the sysadmin's job to
216 grant permissions on the MySQL databases properly. </font>phpMyAdmin's
218 </p>
220 <p>
222 version before OS X, Stuffit unstuffs with Mac formats.<br />
223 So you'll have to resave as in Bbedit to unix style ALL phpMyAdmin scripts
224 before uploading them to your server, as PHP seems not to like Mac-style
226 </p>
228 <p>
231 if you are using a kit with files having this extension.
232 </p>
235 <ol>
236 <li> Choose and download a distribution kit with the files having the
238 web/PHP server interprets those extensions.</li>
239 <li> Untar or unzip the distribution (be sure to unzip the subdirectories):
241 document root. If you don't have direct access to your document root,
242 put the files in a directory on your local machine, and, after step 3,
243 transfer the directory on your web server using, for example, ftp.</li>
244 <li> Open the file config.inc.php3 in your favourite editor and change
245 the values for host, user, password and authentication mode to fit
246 your environment.
248 Have a look at
250 explanation of all values.</li>
251 <li> It is recommended that you protect the directory in which you
252 installed phpMyAdmin (unless it's on a closed intranet, or you wish to
253 use http or cookie authentication), for example with HTTP-AUTH (in a
256 information.</li>
257 <li> Open the file
259 in your browser. phpMyAdmin should now display a welcome screen
260 and your databases, or a login dialog if using http or cookie
261 authentication mode.</li>
262 </ol>
265 <ul>
266 <li>Please do not copy your older config.inc.php3 over the new one: it may
267 offer new configuration variables, and the new version may depend on
268 these for normal behavior. It is suggested instead to insert your site
269 values in the new one.</li>
270 </ul>
273 <ul>
274 <li>Http and cookie authentication modes are recommended in a multi-user
275 environment where you want to give users access to their own database
276 and don't want them to play around with others.
277 <br />
278 Nevertheless be aware that MS Internet Explorer seems to be really
280 bit buggy in this area!<br /><br /></li>
282 <li>Http and cookie authentication modes are more secure: the MySQL
283 password does not need to be set in the phpMyAdmin configuration file
286 <br />
287 However, keep in mind that the password travels in plain text, unless
288 you are using the https protocol.
289 <br />
290 In cookie mode, we send the password in a temporary cookie, so most
291 browsers should not store the password in their cookie file.
292 <br /><br /></li>
294 <li>
295 For 'http' and 'cookie' modes, phpMyAdmin needs a controluser that has
300 You must specify the details for the controluser in the
306 use something else in your file:</b><br />
308 <tr>
310 <td>
312 <tt>GRANT SELECT (Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv) ON mysql.user TO 'pma'@'localhost';</tt><br />
314 <tt>GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv) ON mysql.tables_priv TO 'pma'@'localhost';</tt>
315 </td>
316 </tr>
317 <tr>
319 ... and if you want to use the many new relation and bookmark
320 features:
321 </td>
322 </tr>
323 <tr>
325 <td>
327 (this of course requires you to have a special DB for
328 phpMyAdmin, the contents will be explained later)
329 </td>
330 </tr>
331 </table>
332 <br />
333 </li>
334 <li>
336 privileges on a set of particular databases. Normally you shouldn't
337 give global privileges to an ordinary user, unless you understand
338 the impact of those privileges (for example, you are creating
339 a superuser).<br />
342 <tt>GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';</tt>
343 <br />
344 What the user may now do is controlled entirely by the MySQL user
345 management system.<br />
346 With http or cookie auth mode, you don't need to fill the user/password
348 </li>
349 </ul>
352 <ul>
355 allows you to login as any valid MySQL user.</li>
356 <li>Is only supported with PHP running as an Apache module, not with
357 cgi.</li>
358 </ul>
361 <ul>
362 <li>You can use this method as a replacement for the http
363 authentication (for example, if you're running IIS).
364 </li>
366 <li>With this mode, the use can truly logout of phpMyAdmin and login back
367 with the same username.</li>
368 </ul>
371 <ul>
372 <li>This mode is the less secure one because it requires you to fill the
377 <li>In the ISP FAQ section, there is an entry explaining how to protect
378 your configuration file.<br /></li>
379 <li>For additional security in this mode, you may wish to consider the
382 directives.</li>
383 </ul>
386 <!-- CONFIGURATION -->
398 </font>
403 <p>
406 the option that allows to use the *nix end of line character
408 you have modified.
409 </p>
412 <dl>
414 <dd>
415 Sets here the complete url (with full path) to your phpMyAdmin version.
417 <br /><br />
418 phpMyAdmin needs this setting, because of requirements of the HTTP
419 protocol, explained in RFC2616, section 14.30.
420 <br /><br />
421 Don't forget the slash at the end of your url. The url must contain
422 characters that are valid for a url, and on some servers, the path
423 is case-sensitive.
424 <br /><br />
425 Starting with version 2.3.0, you can try to leave this parameter
426 empty, because the program tries to auto-detect its proper value.
427 Additional details are in the configuration file.
428 <br /><br />
429 Alternatively, this setting can be dynamically completed. For example,
430 you can try to use such a kind of code:
431 <pre>
432 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
433 . $_SERVER['HTTP_HOST']
434 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
437 or
439 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
440 . $_SERVER['SERVER_NAME']
441 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
443 </pre>
447 <br /><br />
448 </dd>
450 <dd>
451 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the system
452 detects your absolute URI automatically, we display a warning to remind
453 you. If you have tested the automatic detection, and it works perfectly
454 for your setup, then you can set this variable to squelch the warning.
455 <br /><br />
456 </dd>
459 <dd>
460 Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
461 with master / foreign - tables (see
463 <br />
464 If you tried to set this up and it does not work for you, have a look on
466 use it. You will find a link that will analyze why those features have
467 been disabled.<br />
468 If you do not want to use those features set this variable to
470 <br /><br />
471 </dd>
474 <dd>
475 Since version 1.4.2, phpMyAdmin supports the administration of multiple
476 MySQL servers.
477 Therefore, a $cfg['Servers']-array has been added which contains
478 the login information for the different servers. The first
481 the second server, etc.
482 If you have only one server to administer, simply leave free the
483 hostname of the other $cfg['Server']-entries.
484 <br /><br />
485 </dd>
488 <dd>
489 The hostname of your $i-th MySQL-server. E.g. localhost.
490 <br /><br />
491 </dd>
494 <dd>
495 The port-number of your $i-th MySQL-server. Default is 3306 (leave
496 blank).
497 <br /><br />
498 </dd>
501 <dd>
502 The path to the socket to use. Leave blank for default.<br />
503 To use the socket feature you must run php 3.0.10 or more.
504 <br /><br />
505 </dd>
508 <dd>
509 What type connection to use with the MySQL server. Your options are
511 is nearly guarenteed to be available on all MySQL servers, while
512 sockets are not supported on some platforms.
513 <br /><br />
514 </dd>
516 <dt>
519 </dt>
520 <dd>
521 When using http or cookie authentication modes (or 'config'
522 authentication mode since phpMyAdmin 2.2.1), you need to supply the
527 This account is used to check what databases the user will see at
528 login.<br />
531 <br /><br />
532 Note that if you try login to phpMyAdmin with this
536 <br /><br />
537 In versions before 2.2.5, those were called
539 <br /><br />
540 </dd>
543 <dd>
544 Whether config or cookie or http authentication should be used for this
545 server.
547 <ul>
548 <li>
549 'config' authentication
551 way: username and password are stored in
553 </li>
554 <li>
555 'cookie' authentication mode
557 2.2.3 allows you to log in as any valid MySQL user with the
558 help of... cookies. Log name and password are stored in
559 cookies during the session and password is deleted when it
560 ends.
561 </li>
562 <li>
563 'http' authentication (was called 'advanced' in older versions)
565 allows you to log in as any valid MySQL user via HTTP-Auth.
566 </li>
567 </ul><br />
570 for more information.
571 <br /><br />
572 </dd>
574 <dt>
577 </dt>
578 <dd>
579 The user/password-pair which phpMyAdmin will use to connect to this
580 MySQL-server. This user/password pair is not needed when http or cookie
581 authentication is used, and should be empty.<br /><br />
582 </dd>
585 <dd>
586 If set to a(an array of) database name(s), only this(these) database(s)
587 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
588 database(s) name(s) may contain MySQL wilcards characters
592 This setting is an efficient way to lower the server charge since the
593 latter does not need to send MySQL requests to build the available
595 privileges rules of the MySQL database server</font>. If set, it just
596 means only these databases will be displayed but
598 <br /><br />
599 </dd>
602 <dd>
603 Only useful when using phpMyAdmin with multiple server entries. If set,
604 this string will be displayed instead of the hostname in the pulldown
605 menu on the main page. This can be useful if you want to show only
606 certain databases on your system, for example.
607 <br /><br />
608 </dd>
610 <dt>
613 </dt>
614 <dd>
615 Starting with version 2.3.0 phpMyAdmin offers a lot of features
616 to work with master / foreign - tables. To use those as well as
617 the bookmark feature you need special tables with a
618 predefined structure, which we explain below.<br />
619 If you are the only user of this phpMyAdmin installation, you can
620 use your current database to store those special tables; in this
621 case, just put your current database name in
623 <br /><br />
624 If you are setting up a multi-user phpMyAdmin installation,
625 you will need to create a new db and setup special privileges,
626 so, as superuser:
627 <br /><br />
628 <ul>
629 <li>
630 create a new database for phpmyadmin:<br />
634 privileges on this database. Here is a query to set up
637 controluser):<br />
638 <tt>
639 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to 'pma'@'localhost';
640 </tt><br />
642 </li>
643 <li>
645 </li>
646 </ul><br />
647 </dd>
649 <dt>
652 </dt>
653 <dd>
654 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can be
655 useful for queries you often run.<br /><br />
657 To allow the usage of this functionality you have to:
658 <ul>
660 <li>within this database create a table following this scheme:
661 <br />
662 <tt>
671 </tt>
672 </li>
673 <li>enter the tablename in
675 </ul><br />
676 </dd>
678 <dt>
681 </dt>
682 <dd>
683 Since release 2.2.4 you can describe, in a special 'relation' table,
684 which field is a key in another table (a foreign key). phpMyAdmin
685 currently uses this to
686 <ul>
687 <li>
688 make clickable, when you browse the master table, the data values
689 that point to the foreign table;
690 </li>
691 <li>
693 when browsing the master table, if you move the mouse to a column
694 containing a foreign key (use also the 'table_info' table);
695 </li>
696 <li>
697 display links on the table properties page, to check referential
698 integrity (display missing foreign keys) for each described key;
699 </li>
700 <li>
701 in query-by-example, create automatic joins (see an example in
703 </li>
704 <li>
705 enable you to get a PDF schema of your database (also uses the
706 table_coords table).
707 </li>
708 </ul>
709 <br />
711 The keys can be numeric or character.
712 <br /><br />
714 To allow the usage of this functionality the superuser has to:
715 <ul>
717 <li>
718 within this database create a table following this scheme:
719 <br />
720 <tt>
726 `foreign_table` varchar(64) NOT NULL default '',<br />
727 `foreign_field` varchar(64) NOT NULL default '',<br />
728 PRIMARY KEY (`master_db`, `master_table`, `master_field`),<br />
731 </tt>
732 </li>
733 <li>
734 put the relation table name in
736 </li>
737 <li>
738 now as normal user open phpMyAdmin and for each one of your
739 tables where you want to use this feature, click
741 </li>
742 </ul><br />
745 future development of the cross-db relations.<br /><br />
746 </dd>
748 <dt>
751 </dt>
752 <dd>
753 Since release 2.3.0 you can describe, in a special 'table_info'
754 table, which field is to be displayed as a tooltip when moving the
755 cursor over the corresponding key.
756 <br />
757 This configuration variable will hold the name of this special
758 table.
759 To allow the usage of this functionality the superuser has to:
760 <ul>
762 <li>within this database create a table following this scheme:
763 <br />
764 <tt>
768 `display_field` varchar(64) NOT NULL default '',<br />
771 </tt>
772 </li>
773 <li>
774 put the table name in
776 </li>
777 <li>
778 then for each table where you want to use this feature,
780 to choose the field.
781 </li>
782 </ul><br />
784 <br /><br />
785 </dd>
787 <dt>
791 </dt>
792 <dd>
793 Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
794 the relations between your tables. To do this it needs two tables
797 table will be placed on a PDF schema output).
798 <br /><br />
801 output.
802 <br /><br />
803 To allow the usage of this functionality the superuser has to:
804 <ul>
806 <li>
807 within this database create a table following this scheme:
808 <br />
809 <tt>
816 PRIMARY KEY (`db_name`, `table_name`, `pdf_page_number`)<br />
817 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin PDF output';<br />
818 </tt>
819 </li>
820 <li>
821 also within this database create:<br />
822 <tt>
825 `page_nr` int(10) unsigned NOT NULL auto_increment,<br />
830 </tt>
831 </li>
832 <li>
833 put the first table name in
835 and the second table name in
837 </li>
838 </ul><br />
840 <br /><br />
841 </dd>
843 <dt>
846 </dt>
847 <dd>
848 Since release 2.3.0 you can store comments to describe each column
850 <br />
851 To allow the usage of this functionality the superuser has to:
852 <ul>
854 <li>
855 within this database create a table following this scheme:
856 <br />
857 <tt>
865 UNIQUE KEY db_name (db_name, table_name, column_name)<br />
867 </tt>
868 </li>
869 <li>
870 put the table name in
872 </li>
873 </ul><br />
874 </dd>
876 <dt>
878 </dt>
879 <dd>
880 If your rule order is empty, then IP authentication is disabled.
881 <br /><br />
883 applies all deny rules followed by allow rules.
884 Access is allowed by default. Any client which does not match a Deny
885 command or does match an Allow command will be allowed access to the
886 server.
887 <br /><br />
889 applies all allow rules followed by deny rules. Access is denied by
890 default. Any client which does not match an Allow directive or does
891 match a Deny directive will be denied access to the server.
892 <br /><br />
893 If your rule order is set to 'explicit', the authentication is
894 performed in a similar fashion to rule order 'deny,allow', with the
898 and was available in Apache by specifying allow and deny rules without
899 setting any order.
900 <br /><br />
901 </dd>
903 <dt>
905 </dt>
906 <dd>
907 The general format for the rules is as such:<br />
908 <tt>
909
911 </tt>
912 <br /><br />
917 well:<br />
918 <tt>
921 </tt>
922 <br /><br />
924 Having an empty rule list is equivalent to either using
928 <br /><br />
930 For the IP matching system, the following work:<br />
934 But the following does not work:<br />
936 <br /><br />
937 </dd>
940 <dd>
941 If you have more than one server configured, you can set
943 that server when phpMyAdmin is started, or set it to 0 to be given a
944 list of servers without logging in.<br />
946 MUST be set to that server.
947 <br /><br />
948 </dd>
951 <dd>
952 Defines whether to use gzip output buffering for increased
953 speed in HTTP transfers.
954 <br /><br />
955 </dd>
958 <dd>
959 Whether persistent connections should be used or not (mysql_connect or
960 mysql_pconnect).
961 <br /><br />
962 </dd>
965 <dd>
966 Set the number of seconds a script is allowed to run. If seconds is set
967 to zero, no time limit is imposed.<br />
968 This setting is used while importing/exporting dump files but has no
969 effect when PHP is running in safe mode.
970 <br /><br />
971 </dd>
974 <dd>
975 Mark used tables and make it possible to show databases with locked
976 tables (since 3.23.30).
977 <br /><br />
978 </dd>
981 <dd>
982 Defines whether sql-queries generated by phpMyAdmin should be displayed
983 or not.
984 <br /><br />
985 </dd>
988 <dd>
989 Defines whether normal users (non-administrator) are allowed to
990 delete their own database or not. If set as FALSE, the link "Drop
992 mydatabase" will be rejected. Quite practical for ISP's with many
993 customers.
994 <br /><br />
995 </dd>
998 <dd>
1000 displayed when you're about to loose data.
1001 <br /><br />
1002 </dd>
1005 <dd>
1006 Define whether the previous login should be recalled or not in cookie
1007 authentication mode.
1008 <br /><br />
1009 </dd>
1012 <dd>
1013 Define whether the "search string inside database" is enabled or not.
1014 <br /><br />
1015 </dd>
1018 <dd>
1019 Defines whether to use select-based menu and display only the current
1020 tables in the left frame (smaller page).
1021 <br /><br />
1022 </dd>
1025 <dd>
1026 Defines whether to display table comment as tooltip in left frame or
1027 not.
1028 <br /><br />
1029 </dd>
1032 <dd>
1033 Defines whether to display space usage and statistics about databases
1034 and tables or not.<br />
1035 Note that statistics requires at least MySQL 3.23.3 and that, at this
1036 date, MySQL doesn't return such information for Berkeley DB tables.
1037 <br /><br />
1038 </dd>
1040 <dt>
1045 </dt>
1046 <dd>
1050 starting main (right) frame. This setting does not check MySQL commands
1051 entered directly.
1052 <br /><br />
1054 Please note that to block the usage of phpinfo() in scripts, you
1055 have to put this in your php.ini:<br />
1057 <br /><br />
1061 coded password value in the configuration file, end users can't be
1062 allowed to change their passwords.
1063 <br /><br />
1064 </dd>
1067 <dd>
1068 Defines whether to suggest a database name on the
1070 <br /><br />
1071 </dd>
1074 <dd>
1076 content or not.
1077 <br /><br />
1078 </dd>
1081 <dd>
1082 Defines whether navigation bar buttons contain text or symbols only.
1083 <br /><br />
1084 </dd>
1087 <dd>
1088 Defines whether an user should be displayed a
1090 <br /><br />
1091 </dd>
1094 <dd>
1095 Number of rows displayed when browsing a resultset. If the resultset
1096 contains more rows, Previous/Next links will be shown.
1097 <br /><br />
1098 </dd>
1101 <dd>
1105 DATE, DATETIME & TIMESTAMP, ascending order else- by default.
1106 <br /><br />
1107 </dd>
1110 <dd>
1112 from edition when browsing a table's content or not.
1113 Valid values are:<br />
1116 <br />
1119 <br /><br />
1120 </dd>
1123 <dd>
1124 Defines whether MySQL functions fields should be displayed or not in
1125 edit/insert mode.
1126 <br /><br />
1127 </dd>
1130 <dd>
1131 Defines which type of editing controls should be used for CHAR and
1132 VARCHAR fields. Possible values are:
1133 <ul>
1134 <li>
1135 input - this allows to limit size of text to size of field in
1136 MySQL, but has problems with newlines in fields
1137 </li>
1138 <li>
1139 textarea - no problems with newlines in fields, but also no
1140 length limitations
1141 </li>
1142 </ul>
1143 Default is old behavior so input.
1144 <br /><br />
1145 </dd>
1147 <dt>
1151 </dt>
1152 <dd>
1153 Defines whether to allow the use of zip/gzip/bzip compression when
1154 creating a dump file or not.
1155 <br /><br />
1156 </dd>
1159 <dd>
1160 Defines the tab displayed by default on database view. Possible
1163 <br /><br />
1164 </dd>
1167 <dd>
1168 Defines the tab displayed by default on table view. Possible
1172 <br /><br />
1173 </dd>
1176 <dd>
1177 If set to an URL which points to the MySQL documentation (type depends
1179 generated.
1180 <br />
1182 Documentation page</a> for more information about MySQL manuals and
1183 their types.
1184 <br /><br />
1185 </dd>
1188 <dd>
1189 Type of MySQL documentation:
1190 <ul>
1196 </ul>
1197 <br /><br />
1198 </dd>
1201 <dd>
1202 Defines the default language to use, if not browser-defined or
1203 user-defined.<br />
1205 this setting.
1206 <br /><br />
1207 </dd>
1210 <dd>
1211 Force: always use this language (must be defined in the
1213 <br /><br />
1214 </dd>
1217 <dd>
1218 Default charset to use for recoding of MySQL queries. This must be
1220 option.<br />
1221 You can give here any charset which is in
1223 choice, user can select any of them.
1224 <br /><br />
1225 </dd>
1228 <dd>
1229 Allow charset recoding of MySQL queries. You need recode or iconv
1230 support (compiled in or module) in php to allow MySQL queries recoding
1231 and used language file must have it enabled (by default only these
1232 which are in unicode, just to avoid losing some characters).
1233 <br /><br />
1234 </dd>
1237 <dd>
1238 You can select here which functions will be used for charset
1239 conversion.
1240 Possible values are:<br />
1241 <ul>
1242 <li>auto - automatically use available one (first is tested
1243 iconv, then recode)</li>
1246 </ul>
1247 Default is auto.
1248 <br /><br />
1249 </dd>
1252 <dd>
1253 Available charsets for MySQL conversion. You can add your own (any of
1254 supported by recode/iconv) or remove these which you don't use.
1255 Charsets will be shown in same order as here listed, so if you
1256 frequently use some of these move them to the top.
1257 <br /><br />
1258 </dd>
1261 <dd>
1262 Left frame width in pixel.
1263 <br /><br />
1264 </dd>
1266 <dt>
1269 </dt>
1270 <dd>
1271 The background colors (HTML) used for both the frames.
1272 <br /><br />
1273 </dd>
1275 <dt>
1277 </dt>
1278 <dd>
1279 The URI of the background image used for the right frame. It can be
1280 absolute as well as relative from your phpMyAdmin directory.
1281 </dd>
1284 <dd>
1285 The color (HTML) used for the pointer in the left frame (does not work
1286 with NS4).
1287 <br /><br />
1288 </dd>
1291 <dd>
1292 The size of a table's border.
1293 <br /><br />
1294 </dd>
1297 <dd>
1298 The color (HTML) used for table headers.
1299 <br /><br />
1300 </dd>
1303 <dd>
1304 The color (HTML) #1 for table rows.
1305 <br /><br />
1306 </dd>
1309 <dd>
1310 The color (HTML) #2 for table rows.
1311 <br /><br />
1312 </dd>
1314 <dt>
1317 </dt>
1318 <dd>
1319 The colors (HTML) uses for the pointer and the marker in browse mode
1320 (does not work with NS4).<br />
1321 The former feature highlights the row over which your mouse is passing
1322 and the latter lets you visually mark/unmark rows by clicking on
1323 them.<br />
1324 You can disable both of these features by emptying the respective
1325 directive.
1326 <br /><br />
1327 </dd>
1329 <dt>
1334 </dt>
1335 <dd>
1336 Number of columns and rows for the textareas.<br />
1338 The Char* values are used for CHAR and VARCHAR editing (if configured
1339 via $cfg['CharEditing']).
1340 <br /><br />
1341 </dd>
1343 <dt>
1345 </dt>
1346 <dd>
1347 Defines if the whole textarea of the query box will be selected on
1348 click.
1349 <br /><br />
1350 </dd>
1353 <dd>
1355 field on browse view. Can be turned off by a toggle button on the
1356 browse page.
1357 <br /><br />
1358 </dd>
1360 <dt>
1363 </dt>
1364 <dd>
1365 Defines the place where modify and delete links would be put when
1366 tables contents are displayed (you may have them displayed both at the
1367 left and at the right).
1370 <br /><br />
1371 </dd>
1374 <dd>
1375 There are 2 display modes: horizontal and vertical. Define which one is
1376 displayed by default.
1377 <br /><br />
1378 </dd>
1381 <dd>
1382 The name of the directory, ending with a slash, where SQL files have
1383 been uploaded by other means than phpMyAdmin (for example, ftp).
1384 Those files are available under a drop-down box when you click the
1385 database name, then the SQL tab.
1386 <br /><br />
1388 <br /><br />
1389 This feature is useful when your file is too big to be uploaded via
1390 HTTP, or when file uploads are disabled in PHP.
1391 <br /><br />
1392 Please note that if PHP is running in safe mode, this directory must
1393 be owned by the same user as the owner of the phpMyAdmin scripts.
1394 <br /><br />
1395 </dd>
1398 <dd>
1399 Repeat the headers every X cells, or 0 to deactivate.
1400 <br /><br />
1401 </dd>
1404 <dd>
1405 As of phpMyAdmin 2.3.0, we now have a fully functional SQL Parser system.
1406 It is enabled by default, as it is used to format the SQL queries.
1407 <br />
1408 As of 2.3.1, it will become an integral part of phpMyAdmin, as it will
1409 analyze certain queries to improve the behavior of phpMyAdmin. But as
1410 it is very new, and not yet heavily used, we offer you an option to
1411 turn it off.
1412 <br /><br />
1413 </dd>
1416 <dd>
1417 The main use of the new SQL Parser is to pretty-print SQL queries. By
1418 default we use HTML to format the query, but you can disable this by
1420 <br /><br />
1421 </dd>
1425 <dd>
1426 For the pretty-printing of SQL queries, under some cases the part of a
1427 query inside a bracket is indented. By changing
1430 specifies the units of the indent amount that you specified. This is
1431 used via stylesheets.
1432 <br /><br />
1433 </dd>
1436 <dd>
1437 This array is used to define the colours for each type of element of
1438 the pretty-printed SQL queries. The tuple format is<br />
1440 If you specify an empty string for the color of a class, it is ignored
1441 in creating the stylesheet.
1442 You should not alter the class names, only the colour strings.<br />
1444 <ul>
1468 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1469 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1470 </ul><br />
1471 </dd>
1473 <dt><b>$cfg['SQLValidator']['use']</b> boolean</dt>
1474 <dd>
1475 phpMyAdmin now supports use of the <a class="navigation" href="http://developer.mimer.com/validator/index.htm">Mimer SQL Validator</a> service,
1476 as originally published on
1477 <a class="navigation" href="http://developers.slashdot.org/article.pl?sid=02/02/19/1720246">Slashdot</a>.
1478 <br />
1479 For help in setting up your system to use the service, see the
1481 <br /><br />
1482 </dd>
1484 <dt><b>$cfg['SQLValidator']['username']</b> string<br />
1485 <b>$cfg['SQLValidator']['password']</b> string</dt>
1486 <dd>
1487 The SOAP service allows you to login with <tt>anonymous</tt>
1488 and any password, so we use those by default.. Instead, if
1489 you have an account with them, you can put your login details
1490 here, and it will be used in place of the anonymous login.
1491 <br /><br />
1492 </dd>
1494 <dt><b>$cfg['ColumnTypes'] </b>array</dt>
1495 <dd>
1496 All possible types of a MySQL column. In most cases you don't need to
1497 edit this.
1498 <br /><br />
1499 </dd>
1501 <dt><b>$cfg['AttributeTypes'] </b>array</dt>
1502 <dd>
1503 Possible attributes for fields. In most cases you don't need to edit
1504 this.
1505 <br /><br />
1506 </dd>
1508 <dt><b>$cfg['Functions'] </b>array</dt>
1509 <dd>
1510 A list of functions MySQL supports. In most cases you don't need to
1511 edit this.
1512 <br /><br />
1513 </dd>
1515 </dl>
1518 <!-- FAQ -->
1530 </font>
1533 <h2>FAQ - Frequently Asked Questions</h2>
1543 <h3>[1. Server]</h3>
1544 <p>
1545 <b>[1.1] I'm running php 4+ and my server is crashing each time a specific
1546 action is required or phpMyAdmin sends a blank page or a page full of
1547 cryptic characters to my browser, what can I do?</b>
1548 <br />
1549 There are some known php bugs with output buffering and compression.<br />
1550 Try to set the <tt>$cfg['OBGzip']</tt> directive to <tt>FALSE</tt> in your
1551 <i>config.inc.php or .php3</i> file and the
1552 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
1553 configuration file.<br />
1554 Furthermore, we know about such problems connected to the release
1555 candidates of php 4.2.0 (tested with php 4.2.0 RC1 to RC4) together with
1556 MS Internet Explorer. Please upgrade to the release version php 4.2.0.
1557 </p>
1559 <p>
1560 <b>[1.2] My Apache server crashes when using phpMyAdmin.</b>
1561 <br />
1562 You should first try the latest versions of Apache (and possibly MySQL).
1563 <br />
1564 See also the other FAQ entry about php bugs with output buffering.
1565 <br />
1566 If your server keeps crashing, please ask for help in the various
1567 Apache support groups.
1568 </p>
1570 <p>
1572 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
1573 script: I'm always displayed the login screen.</b>
1574 <br />
1575 This is a known PHP bug (see this
1577 official php bug database. It means there is and won't be any phpMyAdmin
1578 fix against it because there is no way to code a fix.
1579 </p>
1581 <p>
1582 <b>[1.4] Using phpMyAdmin on IIS, I'm displayed the error message:
1583 "The specified CGI application misbehaved by not returning a
1584 complete set of HTTP headers...."</b>
1585 <br />
1586 You just forgot to read the <i>install.txt</i> file from the php
1587 distribution. Have a look at the last message in this
1589 official php bug database.
1590 </p>
1592 <p>
1593 <b>[1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
1594 messages with the http or advanced authentication mode.</b>
1595 <br />
1596 This is a known problem with the php ISAPI filter: it's not so stable. For
1597 some more information and complete testings see the messages posted by
1598 André B. aka "djdeluxe76" in
1599 <a href="http://www.phpwizard.net/phorum/read.php?f=1&i=6624&t=6300">this thread</a>
1600 from the phpWizard forum.<br />
1601 Please use instead the cookie authentication mode.
1602 </p>
1604 <p>
1605 <b>[1.6] I can't use phpMyAdmin on PWS: nothing is displayed!</b>
1606 <br />
1607 This seems to be a PWS bug. Filippo Simoncini found a workaroud (at this
1608 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
1609 declarations (2 lines) from the scripts <i>header.inc.php3</i>,
1610 <i>header_printview.inc.php3</i>, <i>index.php3</i>, <i>left.php3</i> and
1611 <i>libraries/common.lib.php3</i>.
1612 </p>
1614 <p>
1615 <b>[1.7] How can I GZip or Bzip a dump or a CSV export. It seems to not
1616 work?</b>
1617 <br />
1618 These features are based on the <tt>gzencode()</tt> and
1619 <tt>bzcompress()</tt> php functions to be more independent of the platform
1620 (Unix/Windows, Safe Mode or not, and so on).
1621 So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
1622 (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
1623 We faced php crashes when trying to download a dump with MS Internet
1624 Explorer when phpMyAdmin is run with a release candidate of php 4.2.0. In
1625 this case you should switch to the release version of php 4.2.0.
1626 </p>
1628 <p>
1629 <b>[1.8] I cannot insert a text file in a table, and I get an error about
1630 safe mode being in effect.</b>
1631 <br />
1632 Your uploaded file is saved by PHP in the "upload dir", as
1633 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
1634 the system default is <i>/tmp</i>).
1635 <br />
1636 We recommend the following setup for Apache servers running in safe mode,
1637 to enable uploads of files while being reasonably secure:
1638 </p>
1639 <ul>
1640 <li>create a separate directory for uploads:
1641 <tt>mkdir /tmp/php</tt></li>
1642 <li>give ownership to the Apache server's user.group:
1643 <tt>chown apache.apache /tmp/php</tt></li>
1644 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
1645 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in php.ini</li>
1646 <li>restart Apache</li>
1647 </ul>
1649 <p>
1650 <b>[1.9] I'm having troubles when uploading files. In general file uploads
1651 don't work on my system and uploaded files have a <tt>Content-Type:</tt>
1652 header in the first line.</b>
1653 <br />
1654 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
1655 and you updated your php rpm to php-4.0.4pl1-3.i386.rpm, didn't you?
1656 <br />
1657 So the problem is that this package has a serious bug that was corrected
1658 ages ago in php (2001-01-28: see
1660 for more details). The problem is that the bugged package is still
1661 available though it was corrected (see
1663 for more details).
1664 <br />
1665 So please download
1666 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
1667 and the problem should go away.
1668 <br />
1669 And that fixes the \r\n problem with file uploads!
1670 </p>
1672 <p>
1673 <b>[1.10] I'm having troubles when uploading files with phpMyAdmin running
1674 on a secure server. My browser is Internet Explorer and I'm using the
1675 Apache server.</b>
1676 <br />
1677 As suggested by "Rob M" in the phpWizard forum, add this line to
1678 your <i>httpd.conf</i>:<br />
1679 <tt>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</tt><br />
1680 It seems to clear up many problems between IE and SSL.
1681 </p>
1683 <p>
1684 <b>[1.11] I get an 'open_basedir restriction' while uploading a file from
1685 the query box.</b>
1686 <br />
1687 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
1688 restrictions. Assuming that the restriction allows you to open files in the
1689 current directory ('.'), all you have to do is create a 'tmp' directory
1690 under the phpMyAdmin install directory, with permissions 777 and the same
1691 owner as the owner of your phpMyAdmin directory. The uploaded files will
1692 be moved there, and after execution of your SQL commands, removed.
1693 </p>
1695 <p>
1696 <b>[1.12] I have lost my MySQL root password, what can I do?</b>
1697 <br />
1698 The MySql manual explains how to
1700 reset the permissions</a>.
1701 </p>
1703 <p>
1704 <b>[1.13] I get an error 'No SQL query' when trying to execute a
1705 bookmark.</b>
1706 <br />
1707 If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
1708 cannot access the uploaded query.
1709 </p>
1711 <p>
1712 <b>[1.14] I get an error 'No SQL query' when trying to submit a query from
1713 the convenient text area.</b>
1714 <br />
1715 Check the <tt>post_max_size</tt> directive from your php configuration file
1716 and try to increase it.
1717 </p>
1719 <p>
1720 <b>[1.15] I have problems with <i>mysql.user</i> field names.</b>
1721 <br />
1722 In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
1723 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
1724 names to align with current standards.
1725 </p>
1726 <p>
1727 <b>[1.16] I cannot upload big dump files.</b>
1728 <br />
1729 The first things to check (or ask your host provider to check) are the
1730 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
1731 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
1732 <br />
1733 All of these three settings limit the maximum size of data that can be
1734 submitted and handled by php. One user also said that post_max_size
1735 and memory_limit need to be larger than upload_max_filesize.
1736 </p>
1738 <p>
1739 <b>[1.17] Does phpMyAdmin support MySQL 4?</b>
1740 <br />
1741 MySQL 4 is not yet fully supported by phpMyAdmin.<br />
1742 Because of MySQL 4's backwards compatibility you can use phpMyAdmin
1743 for administering MySQL 4 servers, but phpMyAdmin does not yet
1744 support its new features. Please notice that in this case it is recommended
1745 to use php >= 4.1 since older versions of php are not
1746 compatible to MySQL 4.<br />
1747 Furthermore, several users reported problems with phpMyAdmin related to
1749 release and should be used for test purposes only!</font>
1750 Because of a major change in the definition syntax of string field types,
1751 this version of phpMyAdmin probably won't work correctly with
1752 MySQL >= 4.1.0! We will work on the support as soon as
1753 MySQL 4.1.0 is released.
1754 </p>
1756 <p>
1757 <b>[1.18] I'm running MySQL <= 4.0.1 having
1758 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
1759 capital letter in its name it is changed to lowercase as it should. But
1760 if I try to DROP this table MySQL is unable to find the corresponding
1761 file.</b>
1762 <br />
1763 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
1764 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
1765 directive.
1766 </p>
1768 <p>
1769 <b>[1.19] I can't run the "display relations" feature because the
1770 script seems not to know the font face I'm using!</b>
1771 <br />
1772 The "FPDF" library we're using for this feature requires some
1773 special files to use font faces.<br />
1774 Please refers to the
1776 these files.
1777 </p>
1780 <p>
1781 <b>[1.20] I receive the error "cannot load MySQL extension, please
1782 check PHP Configuration".</b>
1783 <br />
1784 To connect to a MySQL server, PHP needs a set of MySQL functions called
1785 "MySQL extension".
1786 This extension may be part of the PHP server (compiled-in), otherwise it
1787 needs to be loaded dynamically. Its name is probably <i>mysql.so</i> or
1788 <i>mysql.dll</i>. phpMyAdmin tried to load the extension but failed.
1789 <br /><br />
1790 Usually, the problem is solved by installing a software package called
1791 "PHP-MySQL" or something similar.
1792 </p>
1794 <p>
1795 <b>[1.21] I am running the CGI version of PHP under Unix, and I cannot
1796 login using cookie auth.</b>
1797 <br />
1798 In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.
1799 </p>
1801 <p>
1802 <b>[1.22] I don't see the "Location of text file" field, so
1803 I cannot upload.</b>
1804 <br />
1805 This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
1806 parameter is not set to "on".
1807 </p>
1809 <p>
1810 <b>[1.23] I'm running MySQL on a Win32 machine. Each time I create a new
1811 table the table and field names are changed to lowercase!</b>
1812 <br />
1813 This happens because the MySQL directive <tt>lower_case_table_names</tt>
1814 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
1815 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
1816 Just edit you <tt>my.ini</tt> file that should be located in your Windows
1817 directory and add the following line:<br />
1818 <tt>lower-case-table-names=0</tt><br />
1819 Next, save the file and restart the MySQL service. You can always check the
1820 value of this directive using the query<br />
1821 <tt>SHOW VARIABLES LIKE 'lower_case_table_names';</tt>
1822 </p>
1824 <p>
1825 <b>[1.24] Some characters are being truncated in my queries, or I get
1826 characters randomly added. I am running PHP 4.2.3.</b>
1827 <br />
1828 This is a
1830 </p>
1832 <p>
1833 <b>[1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
1834 and I get problems, such as undefined variables when I run a SQL query.</b>
1835 <br />
1836 A tip from Jose Fandos: put a comment on the following two lines
1837 in httpd.conf, like this:<br />
1838 <tt># mod_gzip_item_include file \.php$</tt><br />
1840 as this version of mod_gzip on Apache (Windows) has problems handling
1841 php scripts. Of course you have to restart Apache.
1842 </p>
1845 <h3>[2. Configuration]</h3>
1847 <p>
1848 <b>[2.1] The error message "Warning: Cannot add header information -
1849 headers already sent by ..." is displayed, what's the problem?</b>
1850 <br />
1851 Edit your <i>config.inc.php or .php3</i> file and ensure there is nothing
1852 (ie no blank lines, no spaces, no characters...) neither before the
1853 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
1854 tag at the end.
1855 </p>
1857 <p>
1858 <b>[2.2] phpMyAdmin can't connect to MySQL. What's wrong?</b>
1859 <br />
1860 Either there is an error with your PHP setup or your username/password is
1861 wrong. Try to make a small script which uses mysql_connect and see if it
1862 works. If it doesn't, it may be you haven't even compiled MySQL support
1863 into PHP.
1864 </p>
1866 <p>
1867 <b>[2.3] The error message "Warning: MySQL Connection Failed: Can't
1868 connect to local MySQL server through socket '/tmp/mysql.sock'
1869 (111)..." is displayed. What can I do?</b>
1870 <br /><br />
1871 For RedHat users, Harald Legner suggests this on the mailing list:
1872 <br /><br />
1873 On my RedHat-Box the socket of mysql is <i>/var/lib/mysql/mysql.sock</i>.
1874 In your php.ini you will find a line
1875 <br />
1876 <tt>mysql.default_socket = /tmp/mysql.sock</tt>
1877 <br />
1878 change it to
1879 <br />
1880 <tt>mysql.default_socket = /var/lib/mysql/mysql.sock</tt>
1881 <br />
1882 Then restart apache and it will work.
1883 <br /><br />
1884 Here is a fix suggested by Brad Ummer in the phpwizard forum:
1885 </p>
1886 <ul>
1887 <li>
1888 First, you need to determine what socket is being used by MySQL.
1889 <br />
1890 To do this, telnet to your server and go to the MySQL bin directory. In
1891 this directory there should be a file named <i>mysqladmin</i>. Type
1892 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
1893 info about your MySQL server, including the socket
1894 (<i>/tmp/mysql.sock</i>, for example).
1895 </li>
1896 <li>
1897 Then, you need to tell PHP to use this socket.<br />Assuming you are
1898 using PHP 3.0.10 or better, you can specify the socket to use when you
1899 open the connection. To do this in phpMyAdmin, you need to complete the
1900 socket information in the config.inc.php3.<br />
1901 For example:
1902 <tt>$cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</tt>
1903 </li>
1904 </ul>
1905 <p>
1906 Have also a look at the
1907 <a class="navigation" href="http://www.mysql.com/doc/C/a/Can_not_connect_to_server.html" target="_blank">
1908 corresponding section of the MySQL documentation</a>.
1909 </p>
1911 <p>
1912 <b>[2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
1913 what can I do?</b>
1914 <br />
1915 Try to set the <tt>$cfg['OBGZip']</tt> directive to <tt>FALSE</tt> in the
1916 phpMyAdmin configuration file. It helps sometime.<br />
1917 Also have a look at your php version number: if it contains
1918 "4.0b..." it means you're running a beta version of PHP. That's
1919 not a so good idea, please upgrade to a plain revision.
1920 </p>
1922 <p>
1923 <b>[2.5] Each time I want to insert or change a record or drop a database
1924 or a table, an error 404 (page not found) is displayed or, with http or
1925 cookie authentication, I'm asked to login again. What's wrong?</b>
1926 <br />
1927 Check the value you set for the <tt>$cfg['PmaAbsoluteUri']</tt> directive
1928 in the phpMyAdmin configuration file.
1929 </p>
1933 <h3>[3. Known limitations]</h3>
1935 <p>
1936 <b>[3.1] When using http authentication, an user who logged out can not
1937 relog in with the same nick.</b>
1938 <br />
1939 This is related to the authentication mechanism (protocol) used by
1940 phpMyAdmin. We plan to change it as soon as we may find enough free time
1941 to do it, but you can bypass this problem: just close all the opened
1942 browser windows and then go back to phpMyAdmin. You should be able to
1943 logs in again.
1944 </p>
1946 <p>
1947 <b>[3.2] When dumping a large table in compressed mode, I get a memory
1948 limit error or a time limit error.</b>
1949 <br />
1950 As of version 2.2.4, we build the compressed dump in memory, so large
1951 tables dumps may hang. The only alternative we can think about (using
1952 system calls to mysqldump then gzip or bzip2) would not be applicable in
1953 environments where PHP is in safe mode: access to system programs is
1954 is limited by the system administrator, and time limit is enforced.
1955 </p>
1957 <p>
1958 <b>[3.3] With InnoDB tables, I lose foreign key relationships when I rename
1959 or alter a table.</b>
1960 <br />
1961 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in
1962 mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
1963 </p>
1967 <h3>[4. ISPs, multi-user installations ]</h3>
1968 <p>
1969 <b>[4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
1970 need to install it for each customer?</b>
1971 <br />
1972 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
1973 your users. The development of this feature was kindly sponsored by
1974 NetCologne GmbH.
1975 This requires a properly setup MySQL user management and phpMyAdmin
1976 http or cookie authentication. See the install section on
1977 "Using http authentication".
1978 </p>
1980 <p>
1981 <b>[4.2] What's the preferred way of making phpMyAdmin secure against evil
1982 access?</b>
1983 <br />
1984 This depends on your system.<br />
1985 If you're running a server which cannot be accessed by other people, it's
1986 sufficient to use the directory protection bundled with your webserver
1987 (with Apache you can use <i>.htaccess</i> files, for example).<br />
1988 If other people have telnet access to your server, you should use
1989 phpMyAdmin's http authentication feature.
1990 <br /><br />
1991 Suggestions:
1992 </p>
1993 <ul>
1994 <li>
1995 Your <i>config.inc.php3</i> file should be <tt>chmod 660</tt>.
1996 </li>
1997 <li>
1998 All your phpMyAdmin files should be chown phpmy.apache, where phpmy
1999 is a user whose password is only known to you, and apache is the
2000 group under which Apache runs.
2001 </li>
2002 <li>
2003 You should use PHP safe mode, to protect from other users that try
2004 to include your <i>config.inc.php3</i> in their scripts.
2005 </li>
2006 </ul>
2008 <p>
2009 <b>[4.3] I get errors about not being able to include a file in
2010 <i>/lang</i> or in <i>/libraries</i>.</b>
2011 <br />
2012 Check <i>php.ini</i>, or ask your sysadmin to check it. The
2013 <tt>include_path</tt> must contain "." somewhere in it, and
2014 <tt>open_basedir</tt>, if used, must contain "." and
2015 "./lang" to allow normal operation of phpMyAdmin.
2016 </p>
2017 <p>
2018 <b>[4.4] phpMyAdmin always gives "Access denied" when using http
2019 authentication.</b><br />
2020 This could happen for several reasons:
2021 </p>
2022 <ul>
2023 <li>
2024 <tt>$cfg['Servers'][$i]['controluser']</tt> and/or
2025 <tt>$cfg['Servers'][$i]['controlpass']</tt> are wrong.
2026 </li>
2027 <li>
2028 The username/password you specify in the login-dialog are invalid.
2029 </li>
2030 <li>
2031 You have already setup a security mechanism for the
2032 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
2033 phpMyAdmin's authentication, so remove it.
2034 </li>
2035 </ul>
2037 <p>
2038 <b>[4.5] Is it possible to let users create their own databases?</b>
2039 <br />
2040 Starting with 2.2.5, in the user management page, you can enter a wildcard
2041 database name for a user, and put the privileges you want. For example,
2042 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
2043 would let a user create/manage his/her database(s).
2044 </p>
2046 <p>
2047 <b>[4.6] How can I use the Host-based authentication additions?</b>
2048 <br />
2049 If you have existing rules from an old .htaccess file, you can take them
2050 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
2051 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
2052 be a major benefit here if your installation is suited to using it. Then
2053 you can just add those updated lines into the
2054 <tt>$cfg['Servers'][$i]['AllowDeny']['rules']</tt> array.
2055 <br /><br />
2056 If you want a pre-made sample, you can try this fragment. It stops the
2057 'root' user from logging in from any networks other than the private
2058 network IP blocks.
2059 <br />
2060 <tt>
2061 //block root from logging in except from the private networks<br />
2062 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';<br />
2063 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(<br />
2064 'deny root from all',<br />
2065 'allow root from localhost',<br />
2066 'allow root from 10.0.0.0/8',<br />
2067 'allow root from 192.168.0.0/16',<br />
2068 'allow root from 172.16.0.0/12',<br />
2069 );
2070 </tt>
2071 </p>
2074 <h3>[5. Browsers or client OS]</h3>
2075 <p>
2076 <b>[5.1] I get an out of memory error, and my controls are non-functional,
2077 when trying to create a table with more than 14 fields.</b>
2078 <br />
2079 We could reproduce this problem only under Win98/98SE. Testing under
2080 WinNT4 or Win2K, we could easily create more than 60 fields.
2081 <br />
2082 A workaround is to create a smaller number of fields, then come back to
2083 your table properties and add the other fields.
2084 </p>
2086 <p>
2087 <b>[5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.</b>
2088 <br />
2089 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
2090 with each script/website that use forms.<br />
2091 Upgrade or downgrade your Xitami server.
2092 </p>
2094 <p>
2095 <b>[5.3] I have problems dumping tables with Konqueror
2096 (phpMyAdmin 2.2.2)</b>
2097 <br />
2098 With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except that
2099 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
2100 don't seem to work.<br />
2102 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
2103 the user's temporary directory, so they must be moved before closing
2104 Konqueror, or else they disappear. Gzip dumps give an error message.<br />
2106 Testing needs to be done for Konqueror 2.2.2.<br />
2107 </p>
2109 <p>
2110 <b>[5.4] I can't use the cookie authentication mode because Internet
2111 Explorer never stores the cookies.</b>
2112 <br />
2113 MS Internet Explorer seems to be really buggy about cookies, at least till
2114 version 6. And thanks to Andrew Zivolup we've traced also a php 4.1.1 bug
2115 in this area!
2116 <br />
2117 Then, if you're running php 4.1.1, try to upgrade or downgrade... it may
2118 work!
2119 </p>
2121 <p>
2122 <b>[5.5] In Internet Explorer 5.0, I get Javascript errors when browsing my
2123 rows.</b>
2124 <br />
2125 Upgrade to at least Internet Explorer 5.5SP2.<br />
2126 </p>
2128 <p>
2129 <b>[5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying
2130 to modify a row in a table with many fields, or with a text field.</b>
2131 <br />
2132 Your table neither have a primary key nor an unique one, so we must use a
2133 long URL to identify this row. There is a limit on the lenght of the URL in
2134 those browsers, and this not happen in Netscape, for example. The
2135 workaround is to create a primary or unique key, or use another browser.
2136 <br />
2137 </p>
2139 <p>
2140 <b>[5.7] I refresh (reload) my browser, and come back to the welcome
2141 page.</b>
2142 <br />
2143 Some browsers support right-clicking into the frame you want to refresh,
2144 just do this in the right frame.<br />
2145 </p>
2147 <p>
2148 <b>[5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
2149 query box.</b>
2150 <br />
2151 Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future
2152 Mozilla versions.<br />
2153 </p>
2155 <p>
2156 <b>[5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
2157 whitespace in the SQL-Query edit area: the page scrolls down.</b>
2158 <br />
2159 This is a Mozilla bug (see bug #26882 at
2161 </p>
2163 <p>
2164 <b>[5.10] With Netscape 4.75 I get empty rows between each row of data in a
2165 CSV exported file.</b>
2166 <br />
2167 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
2168 data in octet-stream mode. Since we can't detect the specific Netscape
2169 version, we cannot workaround this bug.
2170 </p>
2172 <p>
2173 <b>[5.11] Extended-ASCII characters like German umlauts are displayed
2174 wrong.</b>
2175 <br />
2176 Please ensure that you have set your browser's charset to the one of the
2177 language file you have selected on phpMyAdmin's start page.
2178 Alternatively, you can try the auto detection mode that is supported by the
2179 recent versions of the most browsers.
2180 </p>
2183 <h3>[6. Using phpMyAdmin]</h3>
2184 <p>
2185 <b>[6.1] I can't insert new rows into a table / I can't create a table
2186 - MySQL brings up a SQL-error.</b>
2187 <br />
2188 Examine the SQL error with care. Often the problem is caused by
2189 specifying a wrong field-type.<br />
2190 Common errors include:
2191 </p>
2192 <ul>
2193 <li>Using <tt>VARCHAR</tt> without a size argument</li>
2194 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
2195 </ul>
2196 <p>
2197 Also, look at the syntax chapter in the MySQL manual to confirm that your
2198 syntax is correct.
2199 </p>
2200 <p>
2201 <b>[6.2] When I create a table, I click the Index checkbox for 2 fields and
2202 phpMyAdmin generates only one index with those 2 fields.</b>
2203 <br />
2204 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
2205 index. If you want two indexes, create the first one when creating the
2206 table, save, then display the table properties and click the Index link to
2207 create the other index.
2208 </p>
2210 <p>
2211 <b>[6.3] How can I insert a null value into my table?</b>
2212 <br />
2213 Since version 2.2.3, you have a checkbox for each field that can be null.
2214 Before 2.2.3, you had to enter "null", without the quotes, as the
2215 field's value.
2216 </p>
2218 <p>
2219 <b>[6.4] How can I backup my database or table?</b>
2220 <br />
2221 Click on a database or table name in the left frame, the properties will be
2222 displayed. Then on the menu, click "Export", you can dump
2223 the structure, the data, or both. This will generate standard SQL
2224 statements that can be used to recreate your database/table.
2225 <br /><br />
2226 You will need to choose "Save as file", so that phpMyAdmin can
2227 transmit the resulting dump to your station. Depending on your PHP
2228 configuration, you will see options to compress the dump. See also the
2229 <tt>$cfg['ExecTimeLimit']</tt> configuration variable.
2230 <br /><br />
2231 For additional help on this subject, look for the word "dump" in
2232 this document.
2233 </p>
2235 <p>
2236 <b>[6.5] How can I restore (upload) my database or table using a dump?
2237 How can I run a ".sql" file?</b>
2238 <br />
2239 Click on a database name in the left frame, the properties will be
2240 local displayed. Then in the "Run SQL query" section, type in
2241 your dump filename, or use the Browse button. Then click Go.
2242 <br /><br />
2243 For additional help on this subject, look for the word "upload"
2244 in this document.
2245 </p>
2247 <p>
2248 <b>[6.6] How can I use the relation table in Query-by-example?</b>
2249 <br />
2250 Here is an example with the tables persons, towns and countries, all
2251 located in the database mydb. If you don't have a <tt>PMA_relation</tt>
2252 table, create it as explained in the configuration section. Then create the
2253 example tables:
2254 <br /><br />
2255 <tt>
2256 CREATE TABLE REL_countries (<br />
2257 country_code char(1) NOT NULL default '',<br />
2258 description varchar(10) NOT NULL default '',<br />
2259 PRIMARY KEY (country_code)<br />
2260 ) TYPE=MyISAM;<br />
2261 <br />
2262 INSERT INTO REL_countries VALUES ('C', 'Canada');<br />
2263 <br />
2264 CREATE TABLE REL_persons (<br />
2265 id tinyint(4) NOT NULL auto_increment,<br />
2266 person_name varchar(32) NOT NULL default '',<br />
2267 town_code varchar(5) default '0',<br />
2268 country_code char(1) NOT NULL default '',<br />
2269 PRIMARY KEY (id)<br />
2270 ) TYPE=MyISAM;<br />
2271 <br />
2272 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');<br />
2273 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');<br />
2274 <br />
2275 CREATE TABLE REL_towns (<br />
2276 town_code varchar(5) NOT NULL default '0',<br />
2277 description varchar(30) NOT NULL default '',<br />
2278 PRIMARY KEY (town_code)<br />
2279 ) TYPE=MyISAM;<br />
2280 <br />
2281 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');<br />
2282 INSERT INTO REL_towns VALUES ('M', 'Montréal');<br />
2283 <br />
2284 </tt>
2285 To setup appropriate links and display information:
2286 <ul>
2287 <li>on table "REL_persons" click Structure, then Relation view</li>
2288 <li>in Links, for "town_code" choose "REL_towns->code"</li>
2289 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
2290 <li>on table "REL_towns" click Structure, then Relation view</li>
2291 <li>in "Choose field to display", choose "description"</li>
2292 <li>repeat the two previous steps for table "REL_countries"</li>
2293 </ul>
2294 <br />
2295 Then test like this:
2296 </p>
2297 <ul>
2298 <li>Click on your db name in the left frame</li>
2299 <li>Choose "Query"</li>
2300 <li>Use tables: persons, towns, countries</li>
2301 <li>Click "Update query"</li>
2302 <li>In the fields row, choose persons.person_name and click the
2303 "Show" tickbox </li>
2304 <li>Do the same for towns.description and countries.descriptions in the
2305 other 2 columns</li>
2306 <li>Click "Update query" and you will see in the query box that
2307 the correct joins have been generated</li>
2308 <li>Click "Submit query"</li>
2309 </ul>
2310 <br />
2313 <p>
2314 <b>[6.7] How can I use the "display field" feature?</b>
2315 <br />
2316 Starting from the previous example, create the PMA_table_info as explained
2317 in the configuration section, then browse your persons table,
2318 and move the mouse over a town code or country code.
2319 </p>
2322 <p>
2323 <b>[6.8] How can I produce a PDF schema of my database?</b>
2324 <br />
2325 First you have to fill the "relation", "table_coords"
2326 and "pdf_pages" configuration variables.
2327 <br /><br />
2328 Then, think about your schema layout: which tables will go on which pages.
2329 </p>
2330 <ul>
2331 <li>Click on your db name in the left frame</li>
2332 <li>Choose "Structure" in the navigation on top</li>
2333 <li>Choose "Edit PDF Pages" which should be somewhere at the
2334 bottom of the page</li>
2335 <li>Enter the name for a first pdf page and submit</li>
2336 <li>Choose this page to edit</li>
2337 <li>Now add a table you want to show on this page and it's coordinates and
2338 submit<br />
2339 First you will have to guess this coordinates of course, so just expect
2340 to have an area of about 297 * 210 and put the tables coordinates
2341 somewhere in there, you will be able to have a look at what happened
2342 and change them later.<br />
2343 For example, x=100 and y=200 means that the table will be at 200 mm
2344 down and 100 mm right from the upper left corner.<br />
2345 Actually if you have a width of more than 300 or a height of more than
2346 200 than it will automatically be scaled but 300*100 is a good start to
2347 have an idea of what coordinates to use.</li>
2348 <li>After every table you submitted you will have the possibility to submit
2349 more tables</li>
2350 <li>When you have entered enough tables Click on your db name in the left
2351 frame again</li>
2352 <li>Now, again at the bottom of the page you should be able to choose
2353 "Display PDF schema"<br />
2354 For testing it might be useful to show the grid as well, so you can see
2355 the coordinates used.<br />
2356 Maybe also choose color and submit.</li>
2357 <li>Save the file he will offer you to something like <i>Schema.pdf</i>
2358 (Internet Explorer has some bug there which might make it offer it
2359 without an extension. Under Windows it is important to have the
2360 extension ".pdf", under other OSes you should be fine just
2361 saving the file under the name it offers).</li>
2362 </ul>
2364 <p>
2365 <b>[6.9] phpMyAdmin is changing the type of one of my columns!</b>
2366 <br />
2367 No, it's MySQL that is doing
2368 <a class="navigation" href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent column type changing</a>.
2369 </p>
2372 <p>
2373 <b>[6.10] My database has an underscore in it's name, and when I grant
2374 privileges to a user for this database, a backslash is added before the
2375 underscore.</b>
2376 <br />
2377 This is normal and means that the grant is done only for this database. If
2378 there was no backslash, this would be a wildcard grant, and the
2379 underscore would mean "any character". So, if the database name
2380 is "john_db", the user would get rights to john1db, john2db...
2381 instead of just john_db.<br /><br />
2382 If you really want to grant using a wildcard, there is a dialog box "
2383 Database (wildcards allowed)" for this.
2384 </p>
2385 <p>
2386 <b>[6.11] What is the curious symbol ø in the table statistics?</b>
2387 <br />
2388 It means "average".
2389 </p>
2392 <p>
2393 <b>[6.12] I want to understand some Export options.</b>
2394 <br />
2395 "Complete inserts" adds the column names on every INSERT command,
2396 for better documentation (but resulting file is bigger).<br />
2397 "Extended inserts" provides a shorter dump file by using only
2398 once the INSERT verb and the table name.<br />
2399 "Enclose table and field names with backquotes" ensures that
2400 field and table names formed with special characters are protected.<br />
2401 </p>
2403 <p>
2404 <b>[6.13] I would like to create a database with a dot in its name.</b>
2405 <br />
2406 This is a bad idea, because in MySQL the syntax "database.table"
2407 is the normal way to reference a database and table name. Worse, MySQL
2408 will usually let you create a database with a dot, but then you cannot
2409 work with it, nor delete it.<br />
2410 </p>
2413 <p>
2414 <b>[6.14] How do I set up the SQL validator?</b>
2415 <br />
2416 To use it, you need a very recent version of PHP, built with
2417 Overload, XML and PEAR support. On your system command line, run
2419 PEAR modules for usage.
2420 <br />
2421 If you use it, you should be aware that any SQL statement you
2422 submit will be stored anonymously (database/table/column names,
2423 strings, numbers replaced with generic values). The Mimer SQL
2424 Validator itself, is © 2001 Upright Database Technology.
2425 We utilize it as free XML-SOAP service.
2426 <br />
2427 The overload module is crucial to the functionality of the validator
2428 service.
2429 </p>
2431 <p>
2432 <b>[6.15] I want to add a BLOB field and put an index on it, but MySQL
2433 says "BLOB column '...' used in key specification without a key
2434 length".</b>
2435 <br />
2436 The right way to do this, is to create the field without any indexes,
2437 then display the table structure and use the "Create an index"
2438 dialog. On this page, you will be able to choose your BLOB field, and
2439 set a size to the index, which is the condition to create an index on
2440 a BLOB field.
2441 <br />
2442 </p>
2445 <h3>[7. phpMyAdmin project]</h3>
2446 <p>
2447 <b>[7.1] I have found a bug. How do I inform developers?</b>
2448 <br />
2449 Our Bug Tracker is located at
2450 <a href="http://sourceforge.net/projects/phpmyadmin/">http://sourceforge.net/projects/phpmyadmin/</a>
2451 under the Bugs section.
2452 <br /><br />
2453 But please first discuss your bug with other users:
2454 <br />
2456 http://sourceforge.net/projects/phpmyadmin/</a> (and choose Forums)
2457 </p>
2459 <p>
2460 <b>[7.2] I want to translate the messages to a new language or upgrade an
2461 existing language, where do I start?</b>
2462 <br />
2463 Always use the current cvs version of your language file.
2464 For a new language, start from <i>english-iso-8859-1.inc.php3</i>. If you
2465 don't know how to get the cvs version, please ask one of the developers.
2466 <br />
2467 Please note that we try not to use html entities like &eacute; in
2468 the translations, since we define the right character set in the file.
2469 With html entities, the text on buttons would not display correctly.
2470 <br />
2471 You can then put your translations, as a zip file to avoid losing special
2472 characters, on the sourceforge.net translation tracker.
2473 <br />
2474 It would be a good idea to subscribe to the phpmyadmin-translators mailing
2475 list, because this is where we ask for translations of new messages.
2476 <br />
2477 </p>
2479 <p>
2480 <b>[7.3] I would like to help out with the development of phpMyAdmin. How
2481 should I proceed?</b>
2482 <br />
2483 The following method is preferred for new developers:
2484 </p>
2485 <ul>
2486 <li>
2487 fetch the current CVS tree over anonymous CVS:<br />
2488 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
2489 [Password: simply press the Enter key]<br />
2490 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
2491 [This will create a new sub-directory named phpMyAdmin]
2492 </li>
2493 <li>
2494 add your stuff
2495 </li>
2496 <li>
2497 put the modified files (tar'ed and gzip'ed) inside the patch tracker of
2498 the
2499 <a class="navigation" href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">phpMyAdmin SourceForge account</a>.
2500 </li>
2501 </ul>
2502 <p>
2503 Write access to the CVS tree is granted only to experienced developers who
2504 have already contributed something useful to phpMyAdmin.<br />
2505 Also, have a look at the
2507 </p>
2511 <!-- DEVELOPERS -->
2523 </font>
2526 <h2>Developers Information</h2>
2528 <p>
2529 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
2530 great features have been written by other people and you too can help to
2531 make phpMyAdmin a useful tool.
2532 </p>
2534 <p>
2535 If you're planning to contribute source, please read the following
2536 information:
2537 </p>
2538 <ul>
2539 <li>
2540 All files include <i>header.inc.php3</i> (layout),
2541 <i>libraries/common.lib.php3</i> (common functions) and
2542 <i>config.inc.php3</i>.
2543 <br />
2544 All configuration data belongs in <i>config.inc.php3</i>. Please keep
2545 it free from other code.
2546 <br />
2547 Commonly used functions should be added to
2548 <i>libraries/common.lib.php3</i> and more specific ones may be added
2549 within a library stored into the <i>libraries</i> sub-directory.
2550 </li>
2551 <li>
2552 Obviously, you're free to use whatever coding style you want. But
2553 please try to keep your code as simple as possible: beginners are
2554 using phpMyAdmin as an example application.<br />
2555 As far as possible, we want the scripts to be XHTML1.0 and CSS2
2556 compliant on one hand, they fit
2558 on the other hand. Please pay attention to this.
2559 </li>
2560 <li>
2561 Please try to keep up the file-naming conventions. Table-related stuff
2562 goes to <i>tbl_*.php3</i>, db-related code to <i>db_*.php3</i> and so
2563 on.
2564 </li>
2565 <li>
2566 Please don't use verbose strings in your code, instead add the string
2567 (at least) to <i>english-iso-8859-1.inc.php3</i> and print() it out.
2568 </li>
2569 <li>
2570 If you want to be really helpful, write an entry for the ChangeLog.
2571 </li>
2572 </ul>
2574 <p>
2575 IMPORTANT: With 1.4.1, development has switched to CVS. The following
2576 method is preferred for new developers:
2577 </p>
2578 <ul>
2579 <li>
2580 fetch the current CVS tree over anonymous CVS:<br />
2581 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
2582 [Password: simply press the Enter key]<br />
2583 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
2584 [This will create a new sub-directory named phpMyAdmin]
2585 </li>
2586 <li>
2587 add your stuff
2588 </li>
2589 <li>
2590 put the modified files (tar'ed and gzip'ed) inside the patch tracker
2591 of the phpMyAdmin SourceForge account
2592 (<a class="navigation" href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">http://sourceforge.net/projects/phpmyadmin/</a>)
2593 </li>
2594 </ul>
2595 <p>
2596 Write access to the CVS tree is granted only to developers who have already
2597 contributed something useful to phpMyAdmin. If you're interested in that,
2598 please contact us using the phpmyadmin-devel mailing list.
2599 </p>
2602 <!-- CREDITS -->
2614 </font>
2617 <h2>Credits</h2>
2619 <pre>
2621 phpMyAdmin - Credits
2622 ====================
2624 CREDITS, in chronological order
2625 -------------------------------
2627 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
2628 * creator of the phpmyadmin project
2629 * maintainer from 1998 to summer 2000
2631 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
2632 * multi-language version
2633 * various fixes and improvements
2634 * project co-administrator
2636 - Olivier Müller <om_at_omnis.ch>
2637 * started SourceForge phpMyAdmin project in March 2001
2638 * sync'ed different existing CVS trees with new features and bugfixes
2639 * multi-language improvements, dynamic language selection
2640 * current project maintainer
2641 * many bugfixes and improvements
2643 - Loïc Chapeaux <lolo_at_phpheaven.net>
2644 * rewrote and optimized javascript, DHTML and DOM stuff
2645 * rewrote the scripts so they fit the PEAR coding standards and
2646 generate XHTML1.0 and CSS2 compliant codes
2647 * improved the language detection system
2648 * many bugfixes and improvements
2650 - Robin Johnson <robbat2_at_users.sourceforge.net>
2651 * database maintence controls
2652 * table type code
2653 * Host authentication IP Allow/Deny
2654 * DB-based configuration (Not completed)
2655 * SQL parser
2656 * SQL validator
2657 * many bugfixes and improvements
2659 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
2660 * bookmarks feature
2661 * multiple dump feature
2662 * gzip dump feature
2663 * zip dump feature
2665 - Geert Lund <glund_at_silversoft.dk>
2666 * various fixes
2667 * moderator of the phpMyAdmin users forum at phpwizard.net
2669 - Korakot Chaovavanich <korakot_at_iname.com>
2670 * "insert as new row" feature
2672 - Pete Kelly <webmaster_at_trafficg.com>
2673 * rewrote and fix dump code
2674 * bugfixes
2676 - Steve Alberty <alberty_at_neptunlabs.de>
2677 * rewrote dump code for PHP4
2678 * mySQL table statistics
2679 * bugfixes
2681 - Benjamin Gandon <gandon_at_isia.cma.fr>
2682 * main author of the version 2.1.0.1
2683 * bugfixes
2685 - Alexander M. Turek <rabus_at_bugfixes.info>
2686 * XML exports
2687 * MySQL 4 related features
2688 * various small features and fixes
2689 * German language file updates
2691 - Mike Beck <mike.beck_at_ibmiller.de>
2692 * automatic joins in QBE
2693 * links column in printview
2694 * Relation view
2696 - Michal Cihar <nijel_at_users.sourceforge.net>
2697 * enhanced index creation/display feature
2698 * feature to use a different charset for HTML than for MySQL
2699 * Czech language file updates
2701 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
2702 (http://sourceforge.net/projects/phpmysqlformgen/)
2703 * suggested the patch for multiple table printviews
2705 - Garvin Hicking <hicking_at_faktor-e.de>
2706 * built the patch for vertical display of table rows
2708 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
2709 * japanese kanji encoding conversion feature
2711 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
2712 * the Cookie authentication mode
2714 - Axel Sander <n8falke_at_users.sourceforge.net>
2715 * table relation-links feature
2717 - Maxime Delorme <delorme.maxime_at_free.fr>
2718 * PDF schema output, thanks also to Olivier Plathey for the
2719 "FPDF" library (see http://www.fpdf.org/).
2721 - Olof Edlund <olof.edlund_at_upright.se>
2722 * SQL validator server
2724 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
2725 * phpMyAdmin logo
2727 And also to the following people who have contributed minor changes,
2728 enhancements, bugfixes or support for a new language since version 2.1.0:
2730 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
2731 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
2732 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
2733 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
2734 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
2735 www.securereality.com.au, Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky,
2736 Rachim Tamsjadi, Kositer Uros, Luís V., Martijn W. van der Lee,
2737 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
2738 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas.
2741 Original Credits of Version 2.1.0
2742 ---------------------------------
2744 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
2745 to create a web-based interface to MySQL using PHP3. Although I have not
2746 used any of his source-code, there are some concepts I've borrowed from
2747 him. phpMyAdmin was created because Peter told me he wasn't going to
2748 further develop his (great) tool.
2749 Thanks go to
2750 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
2751 code for the check when dropping a table or database. He also suggested
2752 that you should be able to specify the primary key on tbl_create.php3. To
2753 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
2754 well as a bug-report. Plus many smaller improvements.
2755 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
2756 were introduced in 1.3.0 (including quite significant ones like the
2757 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
2758 bug-fixes and help.
2759 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
2760 language-independent by outsourcing the strings to a separate file. He
2761 also contributed the French translation.
2762 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
2763 tbl_select.php3, a feature to display only some fields from a table.
2764 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
2765 functions in tbl_change.php3. He also added the
2766 "Query by Example" feature in 2.0.
2767 - Dave Walton <walton_at_nordicdms.com> added support for multiple
2768 servers and is a regular contributor for bug-fixes.
2769 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
2770 features for 2.0.6.
2771 The following people have contributed minor changes, enhancements, bugfixes
2772 or support for a new language:
2773 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
2774 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
2775 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
2776 G. Wieggers.
2778 And thanks to everyone else who sent me email with suggestions, bug-reports
2779 and or just some feedback.
2780 </pre>
2795 </font>
2800 <img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" border="0" height="31" width="88" /></a>
2801
2803 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" border="0" width="88" height="31" /></a>
2804 </p>
2806 </body>
2807 </html>