| blob | 5799b4878da0814ded786f00bbd006747963cc76 |
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 but shouldn't have any
339 <tt>GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';</tt>
340 <br />
341 What the user may now do is controlled entirely by the MySQL user
342 management system.<br />
343 With http or cookie auth mode, you don't need to fill the user/password
345 </li>
346 </ul>
349 <ul>
352 allows you to login as any valid MySQL user.</li>
353 <li>Is only supported with PHP running as an Apache module, not with
354 cgi.</li>
355 </ul>
358 <ul>
359 <li>You can use this method as a replacement for the http
360 authentication (for example, if you're running IIS).
361 </li>
363 <li>With this mode, the use can truly logout of phpMyAdmin and login back
364 with the same username.</li>
365 </ul>
368 <ul>
369 <li>This mode is the less secure one because it requires you to fill the
374 <li>In the ISP FAQ section, there is an entry explaining how to protect
375 your configuration file.<br /></li>
376 <li>For additional security in this mode, you may wish to consider the
379 directives.</li>
380 </ul>
383 <!-- CONFIGURATION -->
395 </font>
400 <p>
403 the option that allows to use the *nix end of line character
405 you have modified.
406 </p>
409 <dl>
411 <dd>
412 Sets here the complete url (with full path) to your phpMyAdmin version.
414 <br /><br />
415 phpMyAdmin needs this setting, because of requirements of the HTTP
416 protocol, explained in RFC2616, section 14.30.
417 <br /><br />
418 Don't forget the slash at the end of your url. The url must contain
419 characters that are valid for a url, and on some servers, the path
420 is case-sensitive.
421 <br /><br />
422 Starting with version 2.3.0, you can try to leave this parameter
423 empty, because the program tries to auto-detect its proper value.
424 Additional details are in the configuration file.
425 <br /><br />
426 Alternatively, this setting can be dynamically completed. For example,
427 you can try to use such a kind of code:
428 <pre>
429 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
430 . $_SERVER['HTTP_HOST']
431 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
434 or
436 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
437 . $_SERVER['SERVER_NAME']
438 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
440 </pre>
444 <br /><br />
445 </dd>
447 <dd>
448 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the system
449 detects your absolute URI automatically, we display a warning to remind
450 you. If you have tested the automatic detection, and it works perfectly
451 for your setup, then you can set this variable to squelch the warning.
452 <br /><br />
453 </dd>
456 <dd>
457 Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
458 with master / foreign - tables (see
460 <br />
461 If you tried to set this up and it does not work for you, have a look on
463 use it. You will find a link that will analyze why those features have
464 been disabled.<br />
465 If you do not want to use those features set this variable to
467 <br /><br />
468 </dd>
471 <dd>
472 Since version 1.4.2, phpMyAdmin supports the administration of multiple
473 MySQL servers.
474 Therefore, a $cfg['Servers']-array has been added which contains
475 the login information for the different servers. The first
478 the second server, etc.
479 If you have only one server to administer, simply leave free the
480 hostname of the other $cfg['Server']-entries.
481 <br /><br />
482 </dd>
485 <dd>
486 The hostname of your $i-th MySQL-server. E.g. localhost.
487 <br /><br />
488 </dd>
491 <dd>
492 The port-number of your $i-th MySQL-server. Default is 3306 (leave
493 blank).
494 <br /><br />
495 </dd>
498 <dd>
499 The path to the socket to use. Leave blank for default.<br />
500 To use the socket feature you must run php 3.0.10 or more.
501 <br /><br />
502 </dd>
505 <dd>
506 What type connection to use with the MySQL server. Your options are
508 is nearly guarenteed to be available on all MySQL servers, while
509 sockets are not supported on some platforms.
510 <br /><br />
511 </dd>
513 <dt>
516 </dt>
517 <dd>
518 When using http or cookie authentication modes (or 'config'
519 authentication mode since phpMyAdmin 2.2.1), you need to supply the
524 This account is used to check what databases the user will see at
525 login.<br />
528 <br /><br />
529 Note that if you try login to phpMyAdmin with this
533 <br /><br />
534 In versions before 2.2.5, those were called
536 <br /><br />
537 </dd>
540 <dd>
541 Whether config or cookie or http authentication should be used for this
542 server.
544 <ul>
545 <li>
546 'config' authentication
548 way: username and password are stored in
550 </li>
551 <li>
552 'cookie' authentication mode
554 2.2.3 allows you to log in as any valid MySQL user with the
555 help of... cookies. Log name and password are stored in
556 cookies during the session and password is deleted when it
557 ends.
558 </li>
559 <li>
560 'http' authentication (was called 'advanced' in older versions)
562 allows you to log in as any valid MySQL user via HTTP-Auth.
563 </li>
564 </ul><br />
567 for more information.
568 <br /><br />
569 </dd>
571 <dt>
574 </dt>
575 <dd>
576 The user/password-pair which phpMyAdmin will use to connect to this
577 MySQL-server. This user/password pair is not needed when http or cookie
578 authentication is used, and should be empty.<br /><br />
579 </dd>
582 <dd>
583 If set to a(an array of) database name(s), only this(these) database(s)
584 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
585 database(s) name(s) may contain MySQL wilcards characters
589 This setting is an efficient way to lower the server charge since the
590 latter does not need to send MySQL requests to build the available
592 privileges rules of the MySQL database server</font>. If set, it just
593 means only these databases will be displayed but
595 <br /><br />
596 </dd>
599 <dd>
600 Only useful when using phpMyAdmin with multiple server entries. If set,
601 this string will be displayed instead of the hostname in the pulldown
602 menu on the main page. This can be useful if you want to show only
603 certain databases on your system, for example.
604 <br /><br />
605 </dd>
607 <dt>
610 </dt>
611 <dd>
612 Starting with version 2.3.0 phpMyAdmin offers a lot of features
613 to work with master / foreign - tables. To use those as well as
614 the bookmark feature you need special tables with a
615 predefined structure, which we explain below.<br />
616 If you are the only user of this phpMyAdmin installation, you can
617 use your current database to store those special tables; in this
618 case, just put your current database name in
620 <br /><br />
621 If you are setting up a multi-user phpMyAdmin installation,
622 you will need to create a new db and setup special privileges,
623 so, as superuser:
624 <br /><br />
625 <ul>
626 <li>
627 create a new database for phpmyadmin:<br />
631 privileges on this database. Here is a query to set up
634 controluser):<br />
635 <tt>
636 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to 'pma'@'localhost';
637 </tt><br />
639 </li>
640 <li>
642 </li>
643 </ul><br />
644 </dd>
646 <dt>
649 </dt>
650 <dd>
651 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can be
652 useful for queries you often run.<br /><br />
654 To allow the usage of this functionality you have to:
655 <ul>
657 <li>within this database create a table following this scheme:
658 <br />
659 <tt>
668 </tt>
669 </li>
670 <li>enter the tablename in
672 </ul><br />
673 </dd>
675 <dt>
678 </dt>
679 <dd>
680 Since release 2.2.4 you can describe, in a special 'relation' table,
681 which field is a key in another table (a foreign key). phpMyAdmin
682 currently uses this to
683 <ul>
684 <li>
685 make clickable, when you browse the master table, the data values
686 that point to the foreign table;
687 </li>
688 <li>
690 when browsing the master table, if you move the mouse to a column
691 containing a foreign key (use also the 'table_info' table);
692 </li>
693 <li>
694 display links on the table properties page, to check referential
695 integrity (display missing foreign keys) for each described key;
696 </li>
697 <li>
698 in query-by-example, create automatic joins (see an example in
700 </li>
701 <li>
702 enable you to get a PDF schema of your database (also uses the
703 table_coords table).
704 </li>
705 </ul>
706 <br />
708 The keys can be numeric or character.
709 <br /><br />
711 To allow the usage of this functionality the superuser has to:
712 <ul>
714 <li>
715 within this database create a table following this scheme:
716 <br />
717 <tt>
723 `foreign_table` varchar(64) NOT NULL default '',<br />
724 `foreign_field` varchar(64) NOT NULL default '',<br />
725 PRIMARY KEY (`master_db`, `master_table`, `master_field`),<br />
728 </tt>
729 </li>
730 <li>
731 put the relation table name in
733 </li>
734 <li>
735 now as normal user open phpMyAdmin and for each one of your
736 tables where you want to use this feature, click
738 </li>
739 </ul><br />
742 future development of the cross-db relations.<br /><br />
743 </dd>
745 <dt>
748 </dt>
749 <dd>
750 Since release 2.3.0 you can describe, in a special 'table_info'
751 table, which field is to be displayed as a tooltip when moving the
752 cursor over the corresponding key.
753 <br />
754 This configuration variable will hold the name of this special
755 table.
756 To allow the usage of this functionality the superuser has to:
757 <ul>
759 <li>within this database create a table following this scheme:
760 <br />
761 <tt>
765 `display_field` varchar(64) NOT NULL default '',<br />
768 </tt>
769 </li>
770 <li>
771 put the table name in
773 </li>
774 <li>
775 then for each table where you want to use this feature,
777 to choose the field.
778 </li>
779 </ul><br />
781 <br /><br />
782 </dd>
784 <dt>
788 </dt>
789 <dd>
790 Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
791 the relations between your tables. To do this it needs two tables
794 table will be placed on a PDF schema output).
795 <br /><br />
798 output.
799 <br /><br />
800 To allow the usage of this functionality the superuser has to:
801 <ul>
803 <li>
804 within this database create a table following this scheme:
805 <br />
806 <tt>
813 PRIMARY KEY (`db_name`, `table_name`, `pdf_page_number`)<br />
814 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin PDF output';<br />
815 </tt>
816 </li>
817 <li>
818 also within this database create:<br />
819 <tt>
822 `page_nr` int(10) unsigned NOT NULL auto_increment,<br />
827 </tt>
828 </li>
829 <li>
830 put the first table name in
832 and the second table name in
834 </li>
835 </ul><br />
837 <br /><br />
838 </dd>
840 <dt>
843 </dt>
844 <dd>
845 Since release 2.3.0 you can store comments to describe each column
847 <br />
848 To allow the usage of this functionality the superuser has to:
849 <ul>
851 <li>
852 within this database create a table following this scheme:
853 <br />
854 <tt>
862 UNIQUE KEY db_name (db_name, table_name, column_name)<br />
864 </tt>
865 </li>
866 <li>
867 put the table name in
869 </li>
870 </ul><br />
871 </dd>
873 <dt>
875 </dt>
876 <dd>
877 If your rule order is empty, then IP authentication is disabled.
878 <br /><br />
880 applies all deny rules followed by allow rules.
881 Access is allowed by default. Any client which does not match a Deny
882 command or does match an Allow command will be allowed access to the
883 server.
884 <br /><br />
886 applies all allow rules followed by deny rules. Access is denied by
887 default. Any client which does not match an Allow directive or does
888 match a Deny directive will be denied access to the server.
889 <br /><br />
890 If your rule order is set to 'explicit', the authentication is
891 performed in a similar fashion to rule order 'deny,allow', with the
895 and was available in Apache by specifying allow and deny rules without
896 setting any order.
897 <br /><br />
898 </dd>
900 <dt>
902 </dt>
903 <dd>
904 The general format for the rules is as such:<br />
905 <tt>
906
908 </tt>
909 <br /><br />
914 well:<br />
915 <tt>
918 </tt>
919 <br /><br />
921 Having an empty rule list is equivalent to either using
925 <br /><br />
927 For the IP matching system, the following work:<br />
931 But the following does not work:<br />
933 <br /><br />
934 </dd>
937 <dd>
938 If you have more than one server configured, you can set
940 that server when phpMyAdmin is started, or set it to 0 to be given a
941 list of servers without logging in.<br />
943 MUST be set to that server.
944 <br /><br />
945 </dd>
948 <dd>
949 Defines whether to use gzip output buffering for increased
950 speed in HTTP transfers.
951 <br /><br />
952 </dd>
955 <dd>
956 Whether persistent connections should be used or not (mysql_connect or
957 mysql_pconnect).
958 <br /><br />
959 </dd>
962 <dd>
963 Set the number of seconds a script is allowed to run. If seconds is set
964 to zero, no time limit is imposed.<br />
965 This setting is used while importing/exporting dump files but has no
966 effect when PHP is running in safe mode.
967 <br /><br />
968 </dd>
971 <dd>
972 Mark used tables and make it possible to show databases with locked
973 tables (since 3.23.30).
974 <br /><br />
975 </dd>
978 <dd>
979 Defines whether sql-queries generated by phpMyAdmin should be displayed
980 or not.
981 <br /><br />
982 </dd>
985 <dd>
986 Defines whether normal users (non-administrator) are allowed to
987 delete their own database or not. If set as FALSE, the link "Drop
989 mydatabase" will be rejected. Quite practical for ISP's with many
990 customers.
991 <br /><br />
992 </dd>
995 <dd>
997 displayed when you're about to loose data.
998 <br /><br />
999 </dd>
1002 <dd>
1003 Define whether the previous login should be recalled or not in cookie
1004 authentication mode.
1005 <br /><br />
1006 </dd>
1009 <dd>
1010 Define whether the "search string inside database" is enabled or not.
1011 <br /><br />
1012 </dd>
1015 <dd>
1016 Defines whether to use select-based menu and display only the current
1017 tables in the left frame (smaller page).
1018 <br /><br />
1019 </dd>
1022 <dd>
1023 Defines whether to display table comment as tooltip in left frame or
1024 not.
1025 <br /><br />
1026 </dd>
1029 <dd>
1030 Defines whether to display space usage and statistics about databases
1031 and tables or not.<br />
1032 Note that statistics requires at least MySQL 3.23.3 and that, at this
1033 date, MySQL doesn't return such information for Berkeley DB tables.
1034 <br /><br />
1035 </dd>
1037 <dt>
1042 </dt>
1043 <dd>
1047 starting main (right) frame. This setting does not check MySQL commands
1048 entered directly.
1049 <br /><br />
1051 Please note that to block the usage of phpinfo() in scripts, you
1052 have to put this in your php.ini:<br />
1054 <br /><br />
1058 coded password value in the configuration file, end users can't be
1059 allowed to change their passwords.
1060 <br /><br />
1061 </dd>
1064 <dd>
1065 Defines whether to suggest a database name on the
1067 <br /><br />
1068 </dd>
1071 <dd>
1073 content or not.
1074 <br /><br />
1075 </dd>
1078 <dd>
1079 Defines whether navigation bar buttons contain text or symbols only.
1080 <br /><br />
1081 </dd>
1084 <dd>
1085 Defines whether an user should be displayed a
1087 <br /><br />
1088 </dd>
1091 <dd>
1092 Number of rows displayed when browsing a resultset. If the resultset
1093 contains more rows, Previous/Next links will be shown.
1094 <br /><br />
1095 </dd>
1098 <dd>
1102 DATE, DATETIME & TIMESTAMP, ascending order else- by default.
1103 <br /><br />
1104 </dd>
1107 <dd>
1109 from edition when browsing a table's content or not.
1110 Valid values are:<br />
1113 <br />
1116 <br /><br />
1117 </dd>
1120 <dd>
1121 Defines whether MySQL functions fields should be displayed or not in
1122 edit/insert mode.
1123 <br /><br />
1124 </dd>
1127 <dd>
1128 Defines which type of editing controls should be used for CHAR and
1129 VARCHAR fields. Possible values are:
1130 <ul>
1131 <li>
1132 input - this allows to limit size of text to size of field in
1133 MySQL, but has problems with newlines in fields
1134 </li>
1135 <li>
1136 textarea - no problems with newlines in fields, but also no
1137 length limitations
1138 </li>
1139 </ul>
1140 Default is old behavior so input.
1141 <br /><br />
1142 </dd>
1144 <dt>
1148 </dt>
1149 <dd>
1150 Defines whether to allow the use of zip/gzip/bzip compression when
1151 creating a dump file or not.
1152 <br /><br />
1153 </dd>
1156 <dd>
1157 Defines the tab displayed by default on database view. Possible
1160 <br /><br />
1161 </dd>
1164 <dd>
1165 Defines the tab displayed by default on table view. Possible
1169 <br /><br />
1170 </dd>
1173 <dd>
1174 If set to an URL which points to the MySQL documentation (type depends
1176 generated.
1177 <br />
1179 Documentation page</a> for more information about MySQL manuals and
1180 their types.
1181 <br /><br />
1182 </dd>
1185 <dd>
1186 Type of MySQL documentation:
1187 <ul>
1193 </ul>
1194 <br /><br />
1195 </dd>
1198 <dd>
1199 Defines the default language to use, if not browser-defined or
1200 user-defined.<br />
1202 this setting.
1203 <br /><br />
1204 </dd>
1207 <dd>
1208 Force: always use this language (must be defined in the
1210 <br /><br />
1211 </dd>
1214 <dd>
1215 Default charset to use for recoding of MySQL queries. This must be
1217 option.<br />
1218 You can give here any charset which is in
1220 choice, user can select any of them.
1221 <br /><br />
1222 </dd>
1225 <dd>
1226 Allow charset recoding of MySQL queries. You need recode or iconv
1227 support (compiled in or module) in php to allow MySQL queries recoding
1228 and used language file must have it enabled (by default only these
1229 which are in unicode, just to avoid losing some characters).
1230 <br /><br />
1231 </dd>
1234 <dd>
1235 You can select here which functions will be used for charset
1236 conversion.
1237 Possible values are:<br />
1238 <ul>
1239 <li>auto - automatically use available one (first is tested
1240 iconv, then recode)</li>
1243 </ul>
1244 Default is auto.
1245 <br /><br />
1246 </dd>
1249 <dd>
1250 Available charsets for MySQL conversion. You can add your own (any of
1251 supported by recode/iconv) or remove these which you don't use.
1252 Charsets will be shown in same order as here listed, so if you
1253 frequently use some of these move them to the top.
1254 <br /><br />
1255 </dd>
1258 <dd>
1259 Left frame width in pixel.
1260 <br /><br />
1261 </dd>
1263 <dt>
1266 </dt>
1267 <dd>
1268 The background colors (HTML) used for both the frames.
1269 <br /><br />
1270 </dd>
1272 <dt>
1274 </dt>
1275 <dd>
1276 The URI of the background image used for the right frame. It can be
1277 absolute as well as relative from your phpMyAdmin directory.
1278 </dd>
1281 <dd>
1282 The color (HTML) used for the pointer in the left frame (does not work
1283 with NS4).
1284 <br /><br />
1285 </dd>
1288 <dd>
1289 The size of a table's border.
1290 <br /><br />
1291 </dd>
1294 <dd>
1295 The color (HTML) used for table headers.
1296 <br /><br />
1297 </dd>
1300 <dd>
1301 The color (HTML) #1 for table rows.
1302 <br /><br />
1303 </dd>
1306 <dd>
1307 The color (HTML) #2 for table rows.
1308 <br /><br />
1309 </dd>
1311 <dt>
1314 </dt>
1315 <dd>
1316 The colors (HTML) uses for the pointer and the marker in browse mode
1317 (does not work with NS4).<br />
1318 The former feature highlights the row over which your mouse is passing
1319 and the latter lets you visually mark/unmark rows by clicking on
1320 them.<br />
1321 You can disable both of these features by emptying the respective
1322 directive.
1323 <br /><br />
1324 </dd>
1326 <dt>
1331 </dt>
1332 <dd>
1333 Number of columns and rows for the textareas.<br />
1335 The Char* values are used for CHAR and VARCHAR editing (if configured
1336 via $cfg['CharEditing']).
1337 <br /><br />
1338 </dd>
1340 <dt>
1342 </dt>
1343 <dd>
1344 Defines if the whole textarea of the query box will be selected on
1345 click.
1346 <br /><br />
1347 </dd>
1350 <dd>
1352 field on browse view. Can be turned off by a toggle button on the
1353 browse page.
1354 <br /><br />
1355 </dd>
1357 <dt>
1360 </dt>
1361 <dd>
1362 Defines the place where modify and delete links would be put when
1363 tables contents are displayed (you may have them displayed both at the
1364 left and at the right).
1367 <br /><br />
1368 </dd>
1371 <dd>
1372 There are 2 display modes: horizontal and vertical. Define which one is
1373 displayed by default.
1374 <br /><br />
1375 </dd>
1378 <dd>
1379 The name of the directory, ending with a slash, where SQL files have
1380 been uploaded by other means than phpMyAdmin (for example, ftp).
1381 Those files are available under a drop-down box when you click the
1382 database name, then the SQL tab.
1383 <br /><br />
1385 <br /><br />
1386 This feature is useful when your file is too big to be uploaded via
1387 HTTP, or when file uploads are disabled in PHP.
1388 <br /><br />
1389 Please note that if PHP is running in safe mode, this directory must
1390 be owned by the same user as the owner of the phpMyAdmin scripts.
1391 <br /><br />
1392 </dd>
1395 <dd>
1396 Repeat the headers every X cells, or 0 to deactivate.
1397 <br /><br />
1398 </dd>
1401 <dd>
1402 As of phpMyAdmin 2.3.0, we now have a fully functional SQL Parser system.
1403 It is enabled by default, as it is used to format the SQL queries.
1404 <br />
1405 As of 2.3.1, it will become an integral part of phpMyAdmin, as it will
1406 analyze certain queries to improve the behavior of phpMyAdmin. But as
1407 it is very new, and not yet heavily used, we offer you an option to
1408 turn it off.
1409 <br /><br />
1410 </dd>
1413 <dd>
1414 The main use of the new SQL Parser is to pretty-print SQL queries. By
1415 default we use HTML to format the query, but you can disable this by
1417 <br /><br />
1418 </dd>
1422 <dd>
1423 For the pretty-printing of SQL queries, under some cases the part of a
1424 query inside a bracket is indented. By changing
1427 specifies the units of the indent amount that you specified. This is
1428 used via stylesheets.
1429 <br /><br />
1430 </dd>
1433 <dd>
1434 This array is used to define the colours for each type of element of
1435 the pretty-printed SQL queries. The tuple format is<br />
1437 If you specify an empty string for the color of a class, it is ignored
1438 in creating the stylesheet.
1439 You should not alter the class names, only the colour strings.<br />
1441 <ul>
1465 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1466 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1467 </ul><br />
1468 </dd>
1470 <dt><b>$cfg['SQLValidator']['use']</b> boolean</dt>
1471 <dd>
1472 phpMyAdmin now supports use of the <a class="navigation" href="http://developer.mimer.com/validator/index.htm">Mimer SQL Validator</a> service,
1473 as originally published on
1474 <a class="navigation" href="http://developers.slashdot.org/article.pl?sid=02/02/19/1720246">Slashdot</a>.
1475 <br />
1476 For help in setting up your system to use the service, see the
1478 <br /><br />
1479 </dd>
1481 <dt><b>$cfg['SQLValidator']['username']</b> string<br />
1482 <b>$cfg['SQLValidator']['password']</b> string</dt>
1483 <dd>
1484 The SOAP service allows you to login with <tt>anonymous</tt>
1485 and any password, so we use those by default.. Instead, if
1486 you have an account with them, you can put your login details
1487 here, and it will be used in place of the anonymous login.
1488 <br /><br />
1489 </dd>
1491 <dt><b>$cfg['ColumnTypes'] </b>array</dt>
1492 <dd>
1493 All possible types of a MySQL column. In most cases you don't need to
1494 edit this.
1495 <br /><br />
1496 </dd>
1498 <dt><b>$cfg['AttributeTypes'] </b>array</dt>
1499 <dd>
1500 Possible attributes for fields. In most cases you don't need to edit
1501 this.
1502 <br /><br />
1503 </dd>
1505 <dt><b>$cfg['Functions'] </b>array</dt>
1506 <dd>
1507 A list of functions MySQL supports. In most cases you don't need to
1508 edit this.
1509 <br /><br />
1510 </dd>
1512 </dl>
1515 <!-- FAQ -->
1527 </font>
1530 <h2>FAQ - Frequently Asked Questions</h2>
1540 <h3>[1. Server]</h3>
1541 <p>
1542 <b>[1.1] I'm running php 4+ and my server is crashing each time a specific
1543 action is required or phpMyAdmin sends a blank page or a page full of
1544 cryptic characters to my browser, what can I do?</b>
1545 <br />
1546 There are some known php bugs with output buffering and compression.<br />
1547 Try to set the <tt>$cfg['OBGzip']</tt> directive to <tt>FALSE</tt> in your
1548 <i>config.inc.php or .php3</i> file and the
1549 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
1550 configuration file.<br />
1551 Furthermore, we know about such problems connected to the release
1552 candidates of php 4.2.0 (tested with php 4.2.0 RC1 to RC4) together with
1553 MS Internet Explorer. Please upgrade to the release version php 4.2.0.
1554 </p>
1556 <p>
1557 <b>[1.2] My Apache server crashes when using phpMyAdmin.</b>
1558 <br />
1559 You should first try the latest versions of Apache (and possibly MySQL).
1560 <br />
1561 See also the other FAQ entry about php bugs with output buffering.
1562 <br />
1563 If your server keeps crashing, please ask for help in the various
1564 Apache support groups.
1565 </p>
1567 <p>
1569 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
1570 script: I'm always displayed the login screen.</b>
1571 <br />
1572 This is a known PHP bug (see this
1574 official php bug database. It means there is and won't be any phpMyAdmin
1575 fix against it because there is no way to code a fix.
1576 </p>
1578 <p>
1579 <b>[1.4] Using phpMyAdmin on IIS, I'm displayed the error message:
1580 "The specified CGI application misbehaved by not returning a
1581 complete set of HTTP headers...."</b>
1582 <br />
1583 You just forgot to read the <i>install.txt</i> file from the php
1584 distribution. Have a look at the last message in this
1586 official php bug database.
1587 </p>
1589 <p>
1590 <b>[1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
1591 messages with the http or advanced authentication mode.</b>
1592 <br />
1593 This is a known problem with the php ISAPI filter: it's not so stable. For
1594 some more information and complete testings see the messages posted by
1595 André B. aka "djdeluxe76" in
1596 <a href="http://www.phpwizard.net/phorum/read.php?f=1&i=6624&t=6300">this thread</a>
1597 from the phpWizard forum.<br />
1598 Please use instead the cookie authentication mode.
1599 </p>
1601 <p>
1602 <b>[1.6] I can't use phpMyAdmin on PWS: nothing is displayed!</b>
1603 <br />
1604 This seems to be a PWS bug. Filippo Simoncini found a workaroud (at this
1605 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
1606 declarations (2 lines) from the scripts <i>header.inc.php3</i>,
1607 <i>header_printview.inc.php3</i>, <i>index.php3</i>, <i>left.php3</i> and
1608 <i>libraries/common.lib.php3</i>.
1609 </p>
1611 <p>
1612 <b>[1.7] How can I GZip or Bzip a dump or a CSV export. It seems to not
1613 work?</b>
1614 <br />
1615 These features are based on the <tt>gzencode()</tt> and
1616 <tt>bzcompress()</tt> php functions to be more independent of the platform
1617 (Unix/Windows, Safe Mode or not, and so on).
1618 So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
1619 (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
1620 We faced php crashes when trying to download a dump with MS Internet
1621 Explorer when phpMyAdmin is run with a release candidate of php 4.2.0. In
1622 this case you should switch to the release version of php 4.2.0.
1623 </p>
1625 <p>
1626 <b>[1.8] I cannot insert a text file in a table, and I get an error about
1627 safe mode being in effect.</b>
1628 <br />
1629 Your uploaded file is saved by PHP in the "upload dir", as
1630 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
1631 the system default is <i>/tmp</i>).
1632 <br />
1633 We recommend the following setup for Apache servers running in safe mode,
1634 to enable uploads of files while being reasonably secure:
1635 </p>
1636 <ul>
1637 <li>create a separate directory for uploads:
1638 <tt>mkdir /tmp/php</tt></li>
1639 <li>give ownership to the Apache server's user.group:
1640 <tt>chown apache.apache /tmp/php</tt></li>
1641 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
1642 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in php.ini</li>
1643 <li>restart Apache</li>
1644 </ul>
1646 <p>
1647 <b>[1.9] I'm having troubles when uploading files. In general file uploads
1648 don't work on my system and uploaded files have a <tt>Content-Type:</tt>
1649 header in the first line.</b>
1650 <br />
1651 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
1652 and you updated your php rpm to php-4.0.4pl1-3.i386.rpm, didn't you?
1653 <br />
1654 So the problem is that this package has a serious bug that was corrected
1655 ages ago in php (2001-01-28: see
1657 for more details). The problem is that the bugged package is still
1658 available though it was corrected (see
1660 for more details).
1661 <br />
1662 So please download
1663 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
1664 and the problem should go away.
1665 <br />
1666 And that fixes the \r\n problem with file uploads!
1667 </p>
1669 <p>
1670 <b>[1.10] I'm having troubles when uploading files with phpMyAdmin running
1671 on a secure server. My browser is Internet Explorer and I'm using the
1672 Apache server.</b>
1673 <br />
1674 As suggested by "Rob M" in the phpWizard forum, add this line to
1675 your <i>httpd.conf</i>:<br />
1676 <tt>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</tt><br />
1677 It seems to clear up many problems between IE and SSL.
1678 </p>
1680 <p>
1681 <b>[1.11] I get an 'open_basedir restriction' while uploading a file from
1682 the query box.</b>
1683 <br />
1684 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
1685 restrictions. Assuming that the restriction allows you to open files in the
1686 current directory ('.'), all you have to do is create a 'tmp' directory
1687 under the phpMyAdmin install directory, with permissions 777 and the same
1688 owner as the owner of your phpMyAdmin directory. The uploaded files will
1689 be moved there, and after execution of your SQL commands, removed.
1690 </p>
1692 <p>
1693 <b>[1.12] I have lost my MySQL root password, what can I do?</b>
1694 <br />
1695 The MySql manual explains how to
1697 reset the permissions</a>.
1698 </p>
1700 <p>
1701 <b>[1.13] I get an error 'No SQL query' when trying to execute a
1702 bookmark.</b>
1703 <br />
1704 If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
1705 cannot access the uploaded query.
1706 </p>
1708 <p>
1709 <b>[1.14] I get an error 'No SQL query' when trying to submit a query from
1710 the convenient text area.</b>
1711 <br />
1712 Check the <tt>post_max_size</tt> directive from your php configuration file
1713 and try to increase it.
1714 </p>
1716 <p>
1717 <b>[1.15] I have problems with <i>mysql.user</i> field names.</b>
1718 <br />
1719 In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
1720 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
1721 names to align with current standards.
1722 </p>
1723 <p>
1724 <b>[1.16] I cannot upload big dump files.</b>
1725 <br />
1726 The first things to check (or ask your host provider to check) are the
1727 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
1728 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
1729 <br />
1730 All of these three settings limit the maximum size of data that can be
1731 submitted and handled by php. One user also said that post_max_size
1732 and memory_limit need to be larger than upload_max_filesize.
1733 </p>
1735 <p>
1736 <b>[1.17] Does phpMyAdmin support MySQL 4?</b>
1737 <br />
1738 MySQL 4 is not yet fully supported by phpMyAdmin.<br />
1739 Because of MySQL 4's backwards compatibility you can use phpMyAdmin
1740 for administering MySQL 4 servers, but phpMyAdmin does not yet
1741 support its new features. Please notice that in this case it is recommended
1742 to use php >= 4.1 since older versions of php are not
1743 compatible to MySQL 4.<br />
1744 Furthermore, several users reported problems with phpMyAdmin related to
1746 release and should be used for test purposes only!</font>
1747 Because of a major change in the definition syntax of string field types,
1748 this version of phpMyAdmin probably won't work correctly with
1749 MySQL >= 4.1.0! We will work on the support as soon as
1750 MySQL 4.1.0 is released.
1751 </p>
1753 <p>
1754 <b>[1.18] I'm running MySQL <= 4.0.1 having
1755 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
1756 capital letter in its name it is changed to lowercase as it should. But
1757 if I try to DROP this table MySQL is unable to find the corresponding
1758 file.</b>
1759 <br />
1760 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
1761 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
1762 directive.
1763 </p>
1765 <p>
1766 <b>[1.19] I can't run the "display relations" feature because the
1767 script seems not to know the font face I'm using!</b>
1768 <br />
1769 The "FPDF" library we're using for this feature requires some
1770 special files to use font faces.<br />
1771 Please refers to the
1773 these files.
1774 </p>
1777 <p>
1778 <b>[1.20] I receive the error "cannot load MySQL extension, please
1779 check PHP Configuration".</b>
1780 <br />
1781 To connect to a MySQL server, PHP needs a set of MySQL functions called
1782 "MySQL extension".
1783 This extension may be part of the PHP server (compiled-in), otherwise it
1784 needs to be loaded dynamically. Its name is probably <i>mysql.so</i> or
1785 <i>mysql.dll</i>. phpMyAdmin tried to load the extension but failed.
1786 <br /><br />
1787 Usually, the problem is solved by installing a software package called
1788 "PHP-MySQL" or something similar.
1789 </p>
1791 <p>
1792 <b>[1.21] I am running the CGI version of PHP under Unix, and I cannot
1793 login using cookie auth.</b>
1794 <br />
1795 In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.
1796 </p>
1798 <p>
1799 <b>[1.22] I don't see the "Location of text file" field, so
1800 I cannot upload.</b>
1801 <br />
1802 This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
1803 parameter is not set to "on".
1804 </p>
1806 <p>
1807 <b>[1.23] I'm running MySQL on a Win32 machine. Each time I create a new
1808 table the table and field names are changed to lowercase!</b>
1809 <br />
1810 This happens because the MySQL directive <tt>lower_case_table_names</tt>
1811 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
1812 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
1813 Just edit you <tt>my.ini</tt> file that should be located in your Windows
1814 directory and add the following line:<br />
1815 <tt>lower-case-table-names=0</tt><br />
1816 Next, save the file and restart the MySQL service. You can always check the
1817 value of this directive using the query<br />
1818 <tt>SHOW VARIABLES LIKE 'lower_case_table_names';</tt>
1819 </p>
1821 <p>
1822 <b>[1.24] Some characters are being truncated in my queries, or I get
1823 characters randomly added. I am running PHP 4.2.3.</b>
1824 <br />
1825 This is a
1827 </p>
1829 <p>
1830 <b>[1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
1831 and I get problems, such as undefined variables when I run a SQL query.</b>
1832 <br />
1833 A tip from Jose Fandos: put a comment on the following two lines
1834 in httpd.conf, like this:<br />
1835 <tt># mod_gzip_item_include file \.php$</tt><br />
1837 as this version of mod_gzip on Apache (Windows) has problems handling
1838 php scripts. Of course you have to restart Apache.
1839 </p>
1842 <h3>[2. Configuration]</h3>
1844 <p>
1845 <b>[2.1] The error message "Warning: Cannot add header information -
1846 headers already sent by ..." is displayed, what's the problem?</b>
1847 <br />
1848 Edit your <i>config.inc.php or .php3</i> file and ensure there is nothing
1849 (ie no blank lines, no spaces, no characters...) neither before the
1850 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
1851 tag at the end.
1852 </p>
1854 <p>
1855 <b>[2.2] phpMyAdmin can't connect to MySQL. What's wrong?</b>
1856 <br />
1857 Either there is an error with your PHP setup or your username/password is
1858 wrong. Try to make a small script which uses mysql_connect and see if it
1859 works. If it doesn't, it may be you haven't even compiled MySQL support
1860 into PHP.
1861 </p>
1863 <p>
1864 <b>[2.3] The error message "Warning: MySQL Connection Failed: Can't
1865 connect to local MySQL server through socket '/tmp/mysql.sock'
1866 (111)..." is displayed. What can I do?</b>
1867 <br /><br />
1868 For RedHat users, Harald Legner suggests this on the mailing list:
1869 <br /><br />
1870 On my RedHat-Box the socket of mysql is <i>/var/lib/mysql/mysql.sock</i>.
1871 In your php.ini you will find a line
1872 <br />
1873 <tt>mysql.default_socket = /tmp/mysql.sock</tt>
1874 <br />
1875 change it to
1876 <br />
1877 <tt>mysql.default_socket = /var/lib/mysql/mysql.sock</tt>
1878 <br />
1879 Then restart apache and it will work.
1880 <br /><br />
1881 Here is a fix suggested by Brad Ummer in the phpwizard forum:
1882 </p>
1883 <ul>
1884 <li>
1885 First, you need to determine what socket is being used by MySQL.
1886 <br />
1887 To do this, telnet to your server and go to the MySQL bin directory. In
1888 this directory there should be a file named <i>mysqladmin</i>. Type
1889 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
1890 info about your MySQL server, including the socket
1891 (<i>/tmp/mysql.sock</i>, for example).
1892 </li>
1893 <li>
1894 Then, you need to tell PHP to use this socket.<br />Assuming you are
1895 using PHP 3.0.10 or better, you can specify the socket to use when you
1896 open the connection. To do this in phpMyAdmin, you need to complete the
1897 socket information in the config.inc.php3.<br />
1898 For example:
1899 <tt>$cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</tt>
1900 </li>
1901 </ul>
1902 <p>
1903 Have also a look at the
1904 <a class="navigation" href="http://www.mysql.com/doc/C/a/Can_not_connect_to_server.html" target="_blank">
1905 corresponding section of the MySQL documentation</a>.
1906 </p>
1908 <p>
1909 <b>[2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
1910 what can I do?</b>
1911 <br />
1912 Try to set the <tt>$cfg['OBGZip']</tt> directive to <tt>FALSE</tt> in the
1913 phpMyAdmin configuration file. It helps sometime.<br />
1914 Also have a look at your php version number: if it contains
1915 "4.0b..." it means you're running a beta version of PHP. That's
1916 not a so good idea, please upgrade to a plain revision.
1917 </p>
1919 <p>
1920 <b>[2.5] Each time I want to insert or change a record or drop a database
1921 or a table, an error 404 (page not found) is displayed or, with http or
1922 cookie authentication, I'm asked to login again. What's wrong?</b>
1923 <br />
1924 Check the value you set for the <tt>$cfg['PmaAbsoluteUri']</tt> directive
1925 in the phpMyAdmin configuration file.
1926 </p>
1930 <h3>[3. Known limitations]</h3>
1932 <p>
1933 <b>[3.1] When using http authentication, an user who logged out can not
1934 relog in with the same nick.</b>
1935 <br />
1936 This is related to the authentication mechanism (protocol) used by
1937 phpMyAdmin. We plan to change it as soon as we may find enough free time
1938 to do it, but you can bypass this problem: just close all the opened
1939 browser windows and then go back to phpMyAdmin. You should be able to
1940 logs in again.
1941 </p>
1943 <p>
1944 <b>[3.2] When dumping a large table in compressed mode, I get a memory
1945 limit error or a time limit error.</b>
1946 <br />
1947 As of version 2.2.4, we build the compressed dump in memory, so large
1948 tables dumps may hang. The only alternative we can think about (using
1949 system calls to mysqldump then gzip or bzip2) would not be applicable in
1950 environments where PHP is in safe mode: access to system programs is
1951 is limited by the system administrator, and time limit is enforced.
1952 </p>
1954 <p>
1955 <b>[3.3] With InnoDB tables, I lose foreign key relationships when I rename
1956 or alter a table.</b>
1957 <br />
1958 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in
1959 mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
1960 </p>
1964 <h3>[4. ISPs, multi-user installations ]</h3>
1965 <p>
1966 <b>[4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
1967 need to install it for each customer?</b>
1968 <br />
1969 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
1970 your users. The development of this feature was kindly sponsored by
1971 NetCologne GmbH.
1972 This requires a properly setup MySQL user management and phpMyAdmin
1973 http or cookie authentication. See the install section on
1974 "Using http authentication".
1975 </p>
1977 <p>
1978 <b>[4.2] What's the preferred way of making phpMyAdmin secure against evil
1979 access?</b>
1980 <br />
1981 This depends on your system.<br />
1982 If you're running a server which cannot be accessed by other people, it's
1983 sufficient to use the directory protection bundled with your webserver
1984 (with Apache you can use <i>.htaccess</i> files, for example).<br />
1985 If other people have telnet access to your server, you should use
1986 phpMyAdmin's http authentication feature.
1987 <br /><br />
1988 Suggestions:
1989 </p>
1990 <ul>
1991 <li>
1992 Your <i>config.inc.php3</i> file should be <tt>chmod 660</tt>.
1993 </li>
1994 <li>
1995 All your phpMyAdmin files should be chown phpmy.apache, where phpmy
1996 is a user whose password is only known to you, and apache is the
1997 group under which Apache runs.
1998 </li>
1999 <li>
2000 You should use PHP safe mode, to protect from other users that try
2001 to include your <i>config.inc.php3</i> in their scripts.
2002 </li>
2003 </ul>
2005 <p>
2006 <b>[4.3] I get errors about not being able to include a file in
2007 <i>/lang</i> or in <i>/libraries</i>.</b>
2008 <br />
2009 Check <i>php.ini</i>, or ask your sysadmin to check it. The
2010 <tt>include_path</tt> must contain "." somewhere in it, and
2011 <tt>open_basedir</tt>, if used, must contain "." and
2012 "./lang" to allow normal operation of phpMyAdmin.
2013 </p>
2014 <p>
2015 <b>[4.4] phpMyAdmin always gives "Access denied" when using http
2016 authentication.</b><br />
2017 This could happen for several reasons:
2018 </p>
2019 <ul>
2020 <li>
2021 <tt>$cfg['Servers'][$i]['controluser']</tt> and/or
2022 <tt>$cfg['Servers'][$i]['controlpass']</tt> are wrong.
2023 </li>
2024 <li>
2025 The username/password you specify in the login-dialog are invalid.
2026 </li>
2027 <li>
2028 You have already setup a security mechanism for the
2029 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
2030 phpMyAdmin's authentication, so remove it.
2031 </li>
2032 </ul>
2034 <p>
2035 <b>[4.5] Is it possible to let users create their own databases?</b>
2036 <br />
2037 Starting with 2.2.5, in the user management page, you can enter a wildcard
2038 database name for a user, and put the privileges you want. For example,
2039 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
2040 would let a user create/manage his/her database(s).
2041 </p>
2043 <p>
2044 <b>[4.6] How can I use the Host-based authentication additions?</b>
2045 <br />
2046 If you have existing rules from an old .htaccess file, you can take them
2047 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
2048 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
2049 be a major benefit here if your installation is suited to using it. Then
2050 you can just add those updated lines into the
2051 <tt>$cfg['Servers'][$i]['AllowDeny']['rules']</tt> array.
2052 <br /><br />
2053 If you want a pre-made sample, you can try this fragment. It stops the
2054 'root' user from logging in from any networks other than the private
2055 network IP blocks.
2056 <br />
2057 <tt>
2058 //block root from logging in except from the private networks<br />
2059 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';<br />
2060 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(<br />
2061 'deny root from all',<br />
2062 'allow root from localhost',<br />
2063 'allow root from 10.0.0.0/8',<br />
2064 'allow root from 192.168.0.0/16',<br />
2065 'allow root from 172.16.0.0/12',<br />
2066 );
2067 </tt>
2068 </p>
2071 <h3>[5. Browsers or client OS]</h3>
2072 <p>
2073 <b>[5.1] I get an out of memory error, and my controls are non-functional,
2074 when trying to create a table with more than 14 fields.</b>
2075 <br />
2076 We could reproduce this problem only under Win98/98SE. Testing under
2077 WinNT4 or Win2K, we could easily create more than 60 fields.
2078 <br />
2079 A workaround is to create a smaller number of fields, then come back to
2080 your table properties and add the other fields.
2081 </p>
2083 <p>
2084 <b>[5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.</b>
2085 <br />
2086 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
2087 with each script/website that use forms.<br />
2088 Upgrade or downgrade your Xitami server.
2089 </p>
2091 <p>
2092 <b>[5.3] I have problems dumping tables with Konqueror
2093 (phpMyAdmin 2.2.2)</b>
2094 <br />
2095 With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except that
2096 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
2097 don't seem to work.<br />
2099 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
2100 the user's temporary directory, so they must be moved before closing
2101 Konqueror, or else they disappear. Gzip dumps give an error message.<br />
2103 Testing needs to be done for Konqueror 2.2.2.<br />
2104 </p>
2106 <p>
2107 <b>[5.4] I can't use the cookie authentication mode because Internet
2108 Explorer never stores the cookies.</b>
2109 <br />
2110 MS Internet Explorer seems to be really buggy about cookies, at least till
2111 version 6. And thanks to Andrew Zivolup we've traced also a php 4.1.1 bug
2112 in this area!
2113 <br />
2114 Then, if you're running php 4.1.1, try to upgrade or downgrade... it may
2115 work!
2116 </p>
2118 <p>
2119 <b>[5.5] In Internet Explorer 5.0, I get Javascript errors when browsing my
2120 rows.</b>
2121 <br />
2122 Upgrade to at least Internet Explorer 5.5SP2.<br />
2123 </p>
2125 <p>
2126 <b>[5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying
2127 to modify a row in a table with many fields, or with a text field.</b>
2128 <br />
2129 Your table neither have a primary key nor an unique one, so we must use a
2130 long URL to identify this row. There is a limit on the lenght of the URL in
2131 those browsers, and this not happen in Netscape, for example. The
2132 workaround is to create a primary or unique key, or use another browser.
2133 <br />
2134 </p>
2136 <p>
2137 <b>[5.7] I refresh (reload) my browser, and come back to the welcome
2138 page.</b>
2139 <br />
2140 Some browsers support right-clicking into the frame you want to refresh,
2141 just do this in the right frame.<br />
2142 </p>
2144 <p>
2145 <b>[5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
2146 query box.</b>
2147 <br />
2148 Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future
2149 Mozilla versions.<br />
2150 </p>
2152 <p>
2153 <b>[5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
2154 whitespace in the SQL-Query edit area: the page scrolls down.</b>
2155 <br />
2156 This is a Mozilla bug (see bug #26882 at
2158 </p>
2160 <p>
2161 <b>[5.10] With Netscape 4.75 I get empty rows between each row of data in a
2162 CSV exported file.</b>
2163 <br />
2164 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
2165 data in octet-stream mode. Since we can't detect the specific Netscape
2166 version, we cannot workaround this bug.
2167 </p>
2169 <p>
2170 <b>[5.11] Extended-ASCII characters like German umlauts are displayed
2171 wrong.</b>
2172 <br />
2173 Please ensure that you have set your browser's charset to the one of the
2174 language file you have selected on phpMyAdmin's start page.
2175 Alternatively, you can try the auto detection mode that is supported by the
2176 recent versions of the most browsers.
2177 </p>
2180 <h3>[6. Using phpMyAdmin]</h3>
2181 <p>
2182 <b>[6.1] I can't insert new rows into a table / I can't create a table
2183 - MySQL brings up a SQL-error.</b>
2184 <br />
2185 Examine the SQL error with care. Often the problem is caused by
2186 specifying a wrong field-type.<br />
2187 Common errors include:
2188 </p>
2189 <ul>
2190 <li>Using <tt>VARCHAR</tt> without a size argument</li>
2191 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
2192 </ul>
2193 <p>
2194 Also, look at the syntax chapter in the MySQL manual to confirm that your
2195 syntax is correct.
2196 </p>
2197 <p>
2198 <b>[6.2] When I create a table, I click the Index checkbox for 2 fields and
2199 phpMyAdmin generates only one index with those 2 fields.</b>
2200 <br />
2201 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
2202 index. If you want two indexes, create the first one when creating the
2203 table, save, then display the table properties and click the Index link to
2204 create the other index.
2205 </p>
2207 <p>
2208 <b>[6.3] How can I insert a null value into my table?</b>
2209 <br />
2210 Since version 2.2.3, you have a checkbox for each field that can be null.
2211 Before 2.2.3, you had to enter "null", without the quotes, as the
2212 field's value.
2213 </p>
2215 <p>
2216 <b>[6.4] How can I backup my database or table?</b>
2217 <br />
2218 Click on a database or table name in the left frame, the properties will be
2219 displayed. Then on the menu, click "Export", you can dump
2220 the structure, the data, or both. This will generate standard SQL
2221 statements that can be used to recreate your database/table.
2222 <br /><br />
2223 You will need to choose "Save as file", so that phpMyAdmin can
2224 transmit the resulting dump to your station. Depending on your PHP
2225 configuration, you will see options to compress the dump. See also the
2226 <tt>$cfg['ExecTimeLimit']</tt> configuration variable.
2227 <br /><br />
2228 For additional help on this subject, look for the word "dump" in
2229 this document.
2230 </p>
2232 <p>
2233 <b>[6.5] How can I restore (upload) my database or table using a dump?
2234 How can I run a ".sql" file?</b>
2235 <br />
2236 Click on a database name in the left frame, the properties will be
2237 local displayed. Then in the "Run SQL query" section, type in
2238 your dump filename, or use the Browse button. Then click Go.
2239 <br /><br />
2240 For additional help on this subject, look for the word "upload"
2241 in this document.
2242 </p>
2244 <p>
2245 <b>[6.6] How can I use the relation table in Query-by-example?</b>
2246 <br />
2247 Here is an example with the tables persons, towns and countries, all
2248 located in the database mydb. If you don't have a <tt>PMA_relation</tt>
2249 table, create it as explained in the configuration section. Then create the
2250 example tables:
2251 <br /><br />
2252 <tt>
2253 CREATE TABLE REL_countries (<br />
2254 country_code char(1) NOT NULL default '',<br />
2255 description varchar(10) NOT NULL default '',<br />
2256 PRIMARY KEY (country_code)<br />
2257 ) TYPE=MyISAM;<br />
2258 <br />
2259 INSERT INTO REL_countries VALUES ('C', 'Canada');<br />
2260 <br />
2261 CREATE TABLE REL_persons (<br />
2262 id tinyint(4) NOT NULL auto_increment,<br />
2263 person_name varchar(32) NOT NULL default '',<br />
2264 town_code varchar(5) default '0',<br />
2265 country_code char(1) NOT NULL default '',<br />
2266 PRIMARY KEY (id)<br />
2267 ) TYPE=MyISAM;<br />
2268 <br />
2269 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');<br />
2270 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');<br />
2271 <br />
2272 CREATE TABLE REL_towns (<br />
2273 town_code varchar(5) NOT NULL default '0',<br />
2274 description varchar(30) NOT NULL default '',<br />
2275 PRIMARY KEY (town_code)<br />
2276 ) TYPE=MyISAM;<br />
2277 <br />
2278 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');<br />
2279 INSERT INTO REL_towns VALUES ('M', 'Montréal');<br />
2280 <br />
2281 </tt>
2282 To setup appropriate links and display information:
2283 <ul>
2284 <li>on table "persons" click Structure, then Relation view</li>
2285 <li>in Links, for "town_code" choose "towns->code"</li>
2286 <li>in Links, for "country_code" choose "countries->country_code"</li>
2287 <li>on table "towns" click Structure, then Relation view</li>
2288 <li>in "Choose field to display", choose "description"</li>
2289 <li>repeat the two previous steps for table "countries"</li>
2290 </ul>
2291 <br />
2292 Then test like this:
2293 </p>
2294 <ul>
2295 <li>Click on your db name in the left frame</li>
2296 <li>Choose "Query"</li>
2297 <li>Use tables: persons, towns, countries</li>
2298 <li>Click "Update query"</li>
2299 <li>In the fields row, choose persons.person_name and click the
2300 "Show" tickbox </li>
2301 <li>Do the same for towns.description and countries.descriptions in the
2302 other 2 columns</li>
2303 <li>Click "Update query" and you will see in the query box that
2304 the correct joins have been generated</li>
2305 <li>Click "Submit query"</li>
2306 </ul>
2307 <br />
2310 <p>
2311 <b>[6.7] How can I use the "display field" feature?</b>
2312 <br />
2313 Starting from the previous example, create the PMA_table_info as explained
2314 in the configuration section, then browse your persons table,
2315 and move the mouse over a town code or country code.
2316 </p>
2319 <p>
2320 <b>[6.8] How can I produce a PDF schema of my database?</b>
2321 <br />
2322 First you have to fill the "relation", "table_coords"
2323 and "pdf_pages" configuration variables.
2324 <br /><br />
2325 Then, think about your schema layout: which tables will go on which pages.
2326 </p>
2327 <ul>
2328 <li>Click on your db name in the left frame</li>
2329 <li>Choose "Structure" in the navigation on top</li>
2330 <li>Choose "Edit PDF Pages" which should be somewhere at the
2331 bottom of the page</li>
2332 <li>Enter the name for a first pdf page and submit</li>
2333 <li>Choose this page to edit</li>
2334 <li>Now add a table you want to show on this page and it's coordinates and
2335 submit<br />
2336 First you will have to guess this coordinates of course, so just expect
2337 to have an area of about 297 * 210 and put the tables coordinates
2338 somewhere in there, you will be able to have a look at what happened
2339 and change them later.<br />
2340 For example, x=100 and y=200 means that the table will be at 200 mm
2341 down and 100 mm right from the upper left corner.<br />
2342 Actually if you have a width of more than 300 or a height of more than
2343 200 than it will automatically be scaled but 300*100 is a good start to
2344 have an idea of what coordinates to use.</li>
2345 <li>After every table you submitted you will have the possibility to submit
2346 more tables</li>
2347 <li>When you have entered enough tables Click on your db name in the left
2348 frame again</li>
2349 <li>Now, again at the bottom of the page you should be able to choose
2350 "Display PDF schema"<br />
2351 For testing it might be useful to show the grid as well, so you can see
2352 the coordinates used.<br />
2353 Maybe also choose color and submit.</li>
2354 <li>Save the file he will offer you to something like <i>Schema.pdf</i>
2355 (Internet Explorer has some bug there which might make it offer it
2356 without an extension. Under Windows it is important to have the
2357 extension ".pdf", under other OSes you should be fine just
2358 saving the file under the name it offers).</li>
2359 </ul>
2361 <p>
2362 <b>[6.9] phpMyAdmin is changing the type of one of my columns!</b>
2363 <br />
2364 No, it's MySQL that is doing
2365 <a class="navigation" href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent column type changing</a>.
2366 </p>
2369 <p>
2370 <b>[6.10] My database has an underscore in it's name, and when I grant
2371 privileges to a user for this database, a backslash is added before the
2372 underscore.</b>
2373 <br />
2374 This is normal and means that the grant is done only for this database. If
2375 there was no backslash, this would be a wildcard grant, and the
2376 underscore would mean "any character". So, if the database name
2377 is "john_db", the user would get rights to john1db, john2db...
2378 instead of just john_db.<br /><br />
2379 If you really want to grant using a wildcard, there is a dialog box "
2380 Database (wildcards allowed)" for this.
2381 </p>
2382 <p>
2383 <b>[6.11] What is the curious symbol ø in the table statistics?</b>
2384 <br />
2385 It means "average".
2386 </p>
2389 <p>
2390 <b>[6.12] I want to understand some Export options.</b>
2391 <br />
2392 "Complete inserts" adds the column names on every INSERT command,
2393 for better documentation (but resulting file is bigger).<br />
2394 "Extended inserts" provides a shorter dump file by using only
2395 once the INSERT verb and the table name.<br />
2396 "Enclose table and field names with backquotes" ensures that
2397 field and table names formed with special characters are protected.<br />
2398 </p>
2400 <p>
2401 <b>[6.13] I would like to create a database with a dot in its name.</b>
2402 <br />
2403 This is a bad idea, because in MySQL the syntax "database.table"
2404 is the normal way to reference a database and table name. Worse, MySQL
2405 will usually let you create a database with a dot, but then you cannot
2406 work with it, nor delete it.<br />
2407 </p>
2410 <p>
2411 <b>[6.14] How do I set up the SQL validator?</b>
2412 <br />
2413 To use it, you need a very recent version of PHP, built with
2414 Overload, XML and PEAR support. On your system command line, run
2416 PEAR modules for usage.
2417 <br />
2418 If you use it, you should be aware that any SQL statement you
2419 submit will be stored anonymously (database/table/column names,
2420 strings, numbers replaced with generic values). The Mimer SQL
2421 Validator itself, is © 2001 Upright Database Technology.
2422 We utilize it as free XML-SOAP service.
2423 <br />
2424 The overload module is crucial to the functionality of the validator
2425 service.
2426 </p>
2428 <p>
2429 <b>[6.15] I want to add a BLOB field and put an index on it, but MySQL
2430 says "BLOB column '...' used in key specification without a key
2431 length".</b>
2432 <br />
2433 The right way to do this, is to create the field without any indexes,
2434 then display the table structure and use the "Create an index"
2435 dialog. On this page, you will be able to choose your BLOB field, and
2436 set a size to the index, which is the condition to create an index on
2437 a BLOB field.
2438 <br />
2439 </p>
2442 <h3>[7. phpMyAdmin project]</h3>
2443 <p>
2444 <b>[7.1] I have found a bug. How do I inform developers?</b>
2445 <br />
2446 Our Bug Tracker is located at
2447 <a href="http://sourceforge.net/projects/phpmyadmin/">http://sourceforge.net/projects/phpmyadmin/</a>
2448 under the Bugs section.
2449 <br /><br />
2450 But please first discuss your bug with other users:
2451 <br />
2453 http://sourceforge.net/projects/phpmyadmin/</a> (and choose Forums)
2454 </p>
2456 <p>
2457 <b>[7.2] I want to translate the messages to a new language or upgrade an
2458 existing language, where do I start?</b>
2459 <br />
2460 Always use the current cvs version of your language file.
2461 For a new language, start from <i>english-iso-8859-1.inc.php3</i>. If you
2462 don't know how to get the cvs version, please ask one of the developers.
2463 <br />
2464 Please note that we try not to use html entities like &eacute; in
2465 the translations, since we define the right character set in the file.
2466 With html entities, the text on buttons would not display correctly.
2467 <br />
2468 You can then put your translations, as a zip file to avoid losing special
2469 characters, on the sourceforge.net translation tracker.
2470 <br />
2471 It would be a good idea to subscribe to the phpmyadmin-translators mailing
2472 list, because this is where we ask for translations of new messages.
2473 <br />
2474 </p>
2476 <p>
2477 <b>[7.3] I would like to help out with the development of phpMyAdmin. How
2478 should I proceed?</b>
2479 <br />
2480 The following method is preferred for new developers:
2481 </p>
2482 <ul>
2483 <li>
2484 fetch the current CVS tree over anonymous CVS:<br />
2485 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
2486 [Password: simply press the Enter key]<br />
2487 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
2488 [This will create a new sub-directory named phpMyAdmin]
2489 </li>
2490 <li>
2491 add your stuff
2492 </li>
2493 <li>
2494 put the modified files (tar'ed and gzip'ed) inside the patch tracker of
2495 the
2496 <a class="navigation" href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">phpMyAdmin SourceForge account</a>.
2497 </li>
2498 </ul>
2499 <p>
2500 Write access to the CVS tree is granted only to experienced developers who
2501 have already contributed something useful to phpMyAdmin.<br />
2502 Also, have a look at the
2504 </p>
2508 <!-- DEVELOPERS -->
2520 </font>
2523 <h2>Developers Information</h2>
2525 <p>
2526 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
2527 great features have been written by other people and you too can help to
2528 make phpMyAdmin a useful tool.
2529 </p>
2531 <p>
2532 If you're planning to contribute source, please read the following
2533 information:
2534 </p>
2535 <ul>
2536 <li>
2537 All files include <i>header.inc.php3</i> (layout),
2538 <i>libraries/common.lib.php3</i> (common functions) and
2539 <i>config.inc.php3</i>.
2540 <br />
2541 All configuration data belongs in <i>config.inc.php3</i>. Please keep
2542 it free from other code.
2543 <br />
2544 Commonly used functions should be added to
2545 <i>libraries/common.lib.php3</i> and more specific ones may be added
2546 within a library stored into the <i>libraries</i> sub-directory.
2547 </li>
2548 <li>
2549 Obviously, you're free to use whatever coding style you want. But
2550 please try to keep your code as simple as possible: beginners are
2551 using phpMyAdmin as an example application.<br />
2552 As far as possible, we want the scripts to be XHTML1.0 and CSS2
2553 compliant on one hand, they fit
2555 on the other hand. Please pay attention to this.
2556 </li>
2557 <li>
2558 Please try to keep up the file-naming conventions. Table-related stuff
2559 goes to <i>tbl_*.php3</i>, db-related code to <i>db_*.php3</i> and so
2560 on.
2561 </li>
2562 <li>
2563 Please don't use verbose strings in your code, instead add the string
2564 (at least) to <i>english-iso-8859-1.inc.php3</i> and print() it out.
2565 </li>
2566 <li>
2567 If you want to be really helpful, write an entry for the ChangeLog.
2568 </li>
2569 </ul>
2571 <p>
2572 IMPORTANT: With 1.4.1, development has switched to CVS. The following
2573 method is preferred for new developers:
2574 </p>
2575 <ul>
2576 <li>
2577 fetch the current CVS tree over anonymous CVS:<br />
2578 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
2579 [Password: simply press the Enter key]<br />
2580 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
2581 [This will create a new sub-directory named phpMyAdmin]
2582 </li>
2583 <li>
2584 add your stuff
2585 </li>
2586 <li>
2587 put the modified files (tar'ed and gzip'ed) inside the patch tracker
2588 of the phpMyAdmin SourceForge account
2589 (<a class="navigation" href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">http://sourceforge.net/projects/phpmyadmin/</a>)
2590 </li>
2591 </ul>
2592 <p>
2593 Write access to the CVS tree is granted only to developers who have already
2594 contributed something useful to phpMyAdmin. If you're interested in that,
2595 please contact us using the phpmyadmin-devel mailing list.
2596 </p>
2599 <!-- CREDITS -->
2611 </font>
2614 <h2>Credits</h2>
2616 <pre>
2618 phpMyAdmin - Credits
2619 ====================
2621 CREDITS, in chronological order
2622 -------------------------------
2624 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
2625 * creator of the phpmyadmin project
2626 * maintainer from 1998 to summer 2000
2628 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
2629 * multi-language version
2630 * various fixes and improvements
2631 * project co-administrator
2633 - Olivier Müller <om_at_omnis.ch>
2634 * started SourceForge phpMyAdmin project in March 2001
2635 * sync'ed different existing CVS trees with new features and bugfixes
2636 * multi-language improvements, dynamic language selection
2637 * current project maintainer
2638 * many bugfixes and improvements
2640 - Loïc Chapeaux <lolo_at_phpheaven.net>
2641 * rewrote and optimized javascript, DHTML and DOM stuff
2642 * rewrote the scripts so they fit the PEAR coding standards and
2643 generate XHTML1.0 and CSS2 compliant codes
2644 * improved the language detection system
2645 * many bugfixes and improvements
2647 - Robin Johnson <robbat2_at_users.sourceforge.net>
2648 * database maintence controls
2649 * table type code
2650 * Host authentication IP Allow/Deny
2651 * DB-based configuration (Not completed)
2652 * SQL parser
2653 * SQL validator
2654 * many bugfixes and improvements
2656 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
2657 * bookmarks feature
2658 * multiple dump feature
2659 * gzip dump feature
2660 * zip dump feature
2662 - Geert Lund <glund_at_silversoft.dk>
2663 * various fixes
2664 * moderator of the phpMyAdmin users forum at phpwizard.net
2666 - Korakot Chaovavanich <korakot_at_iname.com>
2667 * "insert as new row" feature
2669 - Pete Kelly <webmaster_at_trafficg.com>
2670 * rewrote and fix dump code
2671 * bugfixes
2673 - Steve Alberty <alberty_at_neptunlabs.de>
2674 * rewrote dump code for PHP4
2675 * mySQL table statistics
2676 * bugfixes
2678 - Benjamin Gandon <gandon_at_isia.cma.fr>
2679 * main author of the version 2.1.0.1
2680 * bugfixes
2682 - Alexander M. Turek <rabus_at_bugfixes.info>
2683 * XML exports
2684 * MySQL 4 related features
2685 * various small features and fixes
2686 * German language file updates
2688 - Mike Beck <mike.beck_at_ibmiller.de>
2689 * automatic joins in QBE
2690 * links column in printview
2691 * Relation view
2693 - Michal Cihar <nijel_at_users.sourceforge.net>
2694 * enhanced index creation/display feature
2695 * feature to use a different charset for HTML than for MySQL
2696 * Czech language file updates
2698 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
2699 (http://sourceforge.net/projects/phpmysqlformgen/)
2700 * suggested the patch for multiple table printviews
2702 - Garvin Hicking <hicking_at_faktor-e.de>
2703 * built the patch for vertical display of table rows
2705 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
2706 * japanese kanji encoding conversion feature
2708 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
2709 * the Cookie authentication mode
2711 - Axel Sander <n8falke_at_users.sourceforge.net>
2712 * table relation-links feature
2714 - Maxime Delorme <delorme.maxime_at_free.fr>
2715 * PDF schema output, thanks also to Olivier Plathey for the
2716 "FPDF" library (see http://www.fpdf.org/).
2718 - Olof Edlund <olof.edlund_at_upright.se>
2719 * SQL validator server
2721 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
2722 * phpMyAdmin logo
2724 And also to the following people who have contributed minor changes,
2725 enhancements, bugfixes or support for a new language since version 2.1.0:
2727 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
2728 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
2729 Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger, Lubos Klokner,
2730 Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
2731 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
2732 www.securereality.com.au, Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky,
2733 Rachim Tamsjadi, Kositer Uros, Luís V., Martijn W. van der Lee,
2734 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
2735 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas.
2738 Original Credits of Version 2.1.0
2739 ---------------------------------
2741 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
2742 to create a web-based interface to MySQL using PHP3. Although I have not
2743 used any of his source-code, there are some concepts I've borrowed from
2744 him. phpMyAdmin was created because Peter told me he wasn't going to
2745 further develop his (great) tool.
2746 Thanks go to
2747 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
2748 code for the check when dropping a table or database. He also suggested
2749 that you should be able to specify the primary key on tbl_create.php3. To
2750 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
2751 well as a bug-report. Plus many smaller improvements.
2752 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
2753 were introduced in 1.3.0 (including quite significant ones like the
2754 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
2755 bug-fixes and help.
2756 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
2757 language-independent by outsourcing the strings to a separate file. He
2758 also contributed the French translation.
2759 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
2760 tbl_select.php3, a feature to display only some fields from a table.
2761 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
2762 functions in tbl_change.php3. He also added the
2763 "Query by Example" feature in 2.0.
2764 - Dave Walton <walton_at_nordicdms.com> added support for multiple
2765 servers and is a regular contributor for bug-fixes.
2766 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
2767 features for 2.0.6.
2768 The following people have contributed minor changes, enhancements, bugfixes
2769 or support for a new language:
2770 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
2771 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
2772 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
2773 G. Wieggers.
2775 And thanks to everyone else who sent me email with suggestions, bug-reports
2776 and or just some feedback.
2777 </pre>
2792 </font>
2797 <img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" border="0" height="31" width="88" /></a>
2798
2800 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" border="0" width="88" height="31" /></a>
2801 </p>
2803 </body>
2804 </html>