| blob | 14c38509ec2fbf44fe054bbf9365d55c3d85be01 |
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>
177 <li>using Query-by-example (QBE), create complex queries automatically connecting required tables</li>
180 <li>
181 communicate in
183 </li>
184 </ul>
187 <tr>
189 <td>
190 phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dumps
193 </td>
194 </tr>
195 </table>
198 <!-- INSTALLATION -->
210 </font>
215 <p>
217 methods to the MySQL database server. It is still the sysadmin's job to
218 grant permissions on the MySQL databases properly. </font>phpMyAdmin's
220 </p>
222 <p>
224 version before OS X, Stuffit unstuffs with Mac formats.<br />
225 So you'll have to resave as in Bbedit to unix style ALL phpMyAdmin scripts
226 before uploading them to your server, as PHP seems not to like Mac-style
228 </p>
230 <p>
233 if you are using a kit with files having this extension.
234 </p>
237 <ol>
238 <li> Choose and download a distribution kit with the files having the
240 web/PHP server interprets those extensions.</li>
241 <li> Untar or unzip the distribution (be sure to unzip the subdirectories):
243 document root. If you don't have direct access to your document root,
244 put the files in a directory on your local machine, and, after step 3,
245 transfer the directory on your web server using, for example, ftp.</li>
246 <li> Open the file config.inc.php3 in your favourite editor and change
247 the values for host, user, password and authentication mode to fit
248 your environment.
250 Have a look at
252 explanation of all values.</li>
253 <li> It is recommended that you protect the directory in which you
254 installed phpMyAdmin (unless it's on a closed intranet, or you wish to
255 use http or cookie authentication), for example with HTTP-AUTH (in a
258 information.</li>
259 <li> Open the file
261 in your browser. phpMyAdmin should now display a welcome screen
262 and your databases, or a login dialog if using http or cookie
263 authentication mode.</li>
264 </ol>
267 <ul>
268 <li>Please do not copy your older config.inc.php3 over the new one: it may
269 offer new configuration variables, and the new version may depend on
270 these for normal behavior. It is suggested instead to insert your site
271 values in the new one.</li>
272 </ul>
275 <ul>
277 environment</b> where you want to give users access to their own
278 database and don't want them to play around with others.
279 <br />
280 Nevertheless be aware that MS Internet Explorer seems to be really
282 bit buggy in this area!<br />
284 http or cookie mode so that your user/password pair are not in clear
285 in the configuration file.<br /><br /></li>
287 <li>Http and cookie authentication modes are more secure: the MySQL
288 password does not need to be set in the phpMyAdmin configuration file
291 <br />
292 However, keep in mind that the password travels in plain text, unless
293 you are using the https protocol.
294 <br />
295 In cookie mode, we send the password in a temporary cookie, so most
296 browsers should not store the password in their cookie file.
297 <br /><br /></li>
299 <li>
300 For 'http' and 'cookie' modes, phpMyAdmin needs a controluser that has
305 You must specify the details for the controluser in the
311 use something else in your file:</b><br />
313 <tr>
315 <td>
317 <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 />
319 <tt>GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv) ON mysql.tables_priv TO 'pma'@'localhost';</tt>
320 </td>
321 </tr>
322 <tr>
324 ... and if you want to use the many new relation and bookmark
325 features:
326 </td>
327 </tr>
328 <tr>
330 <td>
332 (this of course requires you to have a special DB for
333 phpMyAdmin, the contents will be explained later)
334 </td>
335 </tr>
336 </table>
337 <br />
338 </li>
339 <li>
341 privileges on a set of particular databases. Normally you shouldn't
342 give global privileges to an ordinary user, unless you understand
343 the impact of those privileges (for example, you are creating
344 a superuser).<br />
347 <tt>GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';</tt>
348 <br />
349 What the user may now do is controlled entirely by the MySQL user
350 management system.<br />
351 With http or cookie auth mode, you don't need to fill the user/password
353 </li>
354 </ul>
357 <ul>
360 allows you to login as any valid MySQL user.</li>
361 <li>Is only supported with PHP running as an Apache module, not with
362 cgi.</li>
363 </ul>
366 <ul>
367 <li>You can use this method as a replacement for the http
368 authentication (for example, if you're running IIS).
369 </li>
371 <li>With this mode, the use can truly logout of phpMyAdmin and login back
372 with the same username.</li>
373 </ul>
376 <ul>
377 <li>This mode is the less secure one because it requires you to fill the
382 <li>In the ISP FAQ section, there is an entry explaining how to protect
383 your configuration file.<br /></li>
384 <li>For additional security in this mode, you may wish to consider the
387 directives.</li>
388 </ul>
391 <!-- CONFIGURATION -->
403 </font>
408 <p>
411 the option that allows to use the *nix end of line character
413 you have modified.
414 </p>
417 <dl>
419 <dd>
420 Sets here the complete url (with full path) to your phpMyAdmin version.
422 <br /><br />
423 phpMyAdmin needs this setting, because of requirements of the HTTP
424 protocol, explained in RFC2616, section 14.30.
425 <br /><br />
426 Don't forget the slash at the end of your url. The url must contain
427 characters that are valid for a url, and on some servers, the path
428 is case-sensitive.
429 <br /><br />
430 Starting with version 2.3.0, you can try to leave this parameter
431 empty, because the program tries to auto-detect its proper value.
432 Additional details are in the configuration file.
433 <br /><br />
434 Alternatively, this setting can be dynamically completed. For example,
435 you can try to use such a kind of code:
436 <pre>
437 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
438 . $_SERVER['HTTP_HOST']
439 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
442 or
444 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
445 . $_SERVER['SERVER_NAME']
446 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
448 </pre>
452 <br /><br />
453 </dd>
455 <dd>
456 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the system
457 detects your absolute URI automatically, we display a warning to remind
458 you. If you have tested the automatic detection, and it works perfectly
459 for your setup, then you can set this variable to squelch the warning.
460 <br /><br />
461 </dd>
464 <dd>
465 Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
466 with master / foreign - tables (see
468 <br />
469 If you tried to set this up and it does not work for you, have a look on
471 use it. You will find a link that will analyze why those features have
472 been disabled.<br />
473 If you do not want to use those features set this variable to
475 <br /><br />
476 </dd>
479 <dd>
480 Since version 1.4.2, phpMyAdmin supports the administration of multiple
481 MySQL servers.
482 Therefore, a $cfg['Servers']-array has been added which contains
483 the login information for the different servers. The first
486 the second server, etc.
487 If you have only one server to administer, simply leave free the
488 hostname of the other $cfg['Server']-entries.
489 <br /><br />
490 </dd>
493 <dd>
494 The hostname of your $i-th MySQL-server. E.g. localhost.
495 <br /><br />
496 </dd>
499 <dd>
500 The port-number of your $i-th MySQL-server. Default is 3306 (leave
501 blank).
502 <br /><br />
503 </dd>
506 <dd>
507 The path to the socket to use. Leave blank for default.<br />
508 To use the socket feature you must run php 3.0.10 or more.
509 <br /><br />
510 </dd>
513 <dd>
514 What type connection to use with the MySQL server. Your options are
516 is nearly guarenteed to be available on all MySQL servers, while
517 sockets are not supported on some platforms.
518 <br /><br />
519 To use the socket mode, your MySQL server must be on the same machine
520 as the Web server.
521 <br /><br />
522 </dd>
524 <dt>
527 </dt>
528 <dd>
529 When using http or cookie authentication modes (or 'config'
530 authentication mode since phpMyAdmin 2.2.1), you need to supply the
535 This account is used to check what databases the user will see at
536 login.<br />
539 <br /><br />
540 Note that if you try login to phpMyAdmin with this
544 <br /><br />
545 In versions before 2.2.5, those were called
547 <br /><br />
548 </dd>
551 <dd>
552 Whether config or cookie or http authentication should be used for this
553 server.
555 <ul>
556 <li>
557 'config' authentication
559 way: username and password are stored in
561 </li>
562 <li>
563 'cookie' authentication mode
565 2.2.3 allows you to log in as any valid MySQL user with the
566 help of... cookies. Log name and password are stored in
567 cookies during the session and password is deleted when it
568 ends.
569 </li>
570 <li>
571 'http' authentication (was called 'advanced' in older versions)
573 allows you to log in as any valid MySQL user via HTTP-Auth.
574 </li>
575 </ul><br />
578 for more information.
579 <br /><br />
580 </dd>
582 <dt>
585 </dt>
586 <dd>
587 The user/password-pair which phpMyAdmin will use to connect to this
588 MySQL-server. This user/password pair is not needed when http or cookie
589 authentication is used, and should be empty.<br /><br />
590 </dd>
593 <dd>
594 If set to a(an array of) database name(s), only this(these) database(s)
595 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
596 database(s) name(s) may contain MySQL wilcards characters
600 This setting is an efficient way to lower the server charge since the
601 latter does not need to send MySQL requests to build the available
603 privileges rules of the MySQL database server</font>. If set, it just
604 means only these databases will be displayed but
606 <br /><br />
607 </dd>
610 <dd>
611 Only useful when using phpMyAdmin with multiple server entries. If set,
612 this string will be displayed instead of the hostname in the pulldown
613 menu on the main page. This can be useful if you want to show only
614 certain databases on your system, for example.
615 <br /><br />
616 </dd>
618 <dt>
621 </dt>
622 <dd>
623 Starting with version 2.3.0 phpMyAdmin offers a lot of features
624 to work with master / foreign - tables. To use those as well as
625 the bookmark feature you need special tables with a
626 predefined structure, which we explain below.<br />
627 If you are the only user of this phpMyAdmin installation, you can
628 use your current database to store those special tables; in this
629 case, just put your current database name in
631 <br /><br />
632 If you are setting up a multi-user phpMyAdmin installation,
633 you will need to create a new db and setup special privileges,
634 so, as superuser:
635 <br /><br />
636 <ul>
637 <li>
638 create a new database for phpmyadmin:<br />
642 privileges on this database. Here is a query to set up
645 controluser):<br />
646 <tt>
647 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to 'pma'@'localhost';
648 </tt><br />
650 </li>
651 <li>
653 </li>
654 </ul><br />
655 </dd>
657 <dt>
660 </dt>
661 <dd>
662 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can be
663 useful for queries you often run.<br /><br />
665 To allow the usage of this functionality you have to:
666 <ul>
668 <li>within this database create a table following this scheme:
669 <br />
670 <tt>
679 </tt>
680 </li>
681 <li>enter the tablename in
683 </ul><br />
684 </dd>
686 <dt>
689 </dt>
690 <dd>
691 Since release 2.2.4 you can describe, in a special 'relation' table,
692 which field is a key in another table (a foreign key). phpMyAdmin
693 currently uses this to
694 <ul>
695 <li>
696 make clickable, when you browse the master table, the data values
697 that point to the foreign table;
698 </li>
699 <li>
701 when browsing the master table, if you move the mouse to a column
702 containing a foreign key (use also the 'table_info' table);
703 </li>
704 <li>
705 display links on the table properties page, to check referential
706 integrity (display missing foreign keys) for each described key;
707 </li>
708 <li>
709 in query-by-example, create automatic joins (see an example in
711 </li>
712 <li>
713 enable you to get a PDF schema of your database (also uses the
714 table_coords table).
715 </li>
716 </ul>
717 <br />
719 The keys can be numeric or character.
720 <br /><br />
722 To allow the usage of this functionality the superuser has to:
723 <ul>
725 <li>
726 within this database create a table following this scheme:
727 <br />
728 <tt>
734 `foreign_table` varchar(64) NOT NULL default '',<br />
735 `foreign_field` varchar(64) NOT NULL default '',<br />
736 PRIMARY KEY (`master_db`, `master_table`, `master_field`),<br />
739 </tt>
740 </li>
741 <li>
742 put the relation table name in
744 </li>
745 <li>
746 now as normal user open phpMyAdmin and for each one of your
747 tables where you want to use this feature, click
749 </li>
750 </ul><br />
753 future development of the cross-db relations.<br /><br />
754 </dd>
756 <dt>
759 </dt>
760 <dd>
761 Since release 2.3.0 you can describe, in a special 'table_info'
762 table, which field is to be displayed as a tooltip when moving the
763 cursor over the corresponding key.
764 <br />
765 This configuration variable will hold the name of this special
766 table.
767 To allow the usage of this functionality the superuser has to:
768 <ul>
770 <li>within this database create a table following this scheme:
771 <br />
772 <tt>
776 `display_field` varchar(64) NOT NULL default '',<br />
779 </tt>
780 </li>
781 <li>
782 put the table name in
784 </li>
785 <li>
786 then for each table where you want to use this feature,
788 to choose the field.
789 </li>
790 </ul><br />
792 <br /><br />
793 </dd>
795 <dt>
799 </dt>
800 <dd>
801 Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
802 the relations between your tables. To do this it needs two tables
805 table will be placed on a PDF schema output).
806 <br /><br />
809 output.
810 <br /><br />
811 To allow the usage of this functionality the superuser has to:
812 <ul>
814 <li>
815 within this database create a table following this scheme:
816 <br />
817 <tt>
824 PRIMARY KEY (`db_name`, `table_name`, `pdf_page_number`)<br />
825 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin PDF output';<br />
826 </tt>
827 </li>
828 <li>
829 also within this database create:<br />
830 <tt>
833 `page_nr` int(10) unsigned NOT NULL auto_increment,<br />
838 </tt>
839 </li>
840 <li>
841 put the first table name in
843 and the second table name in
845 </li>
846 </ul><br />
848 <br /><br />
849 </dd>
851 <dt>
854 </dt>
855 <dd>
856 Since release 2.3.0 you can store comments to describe each column
858 <br />
859 To allow the usage of this functionality the superuser has to:
860 <ul>
862 <li>
863 within this database create a table following this scheme:
864 <br />
865 <tt>
873 UNIQUE KEY db_name (db_name, table_name, column_name)<br />
875 </tt>
876 </li>
877 <li>
878 put the table name in
880 </li>
881 </ul><br />
882 </dd>
884 <dt>
886 </dt>
887 <dd>
888 If your rule order is empty, then IP authentication is disabled.
889 <br /><br />
891 applies all deny rules followed by allow rules.
892 Access is allowed by default. Any client which does not match a Deny
893 command or does match an Allow command will be allowed access to the
894 server.
895 <br /><br />
897 applies all allow rules followed by deny rules. Access is denied by
898 default. Any client which does not match an Allow directive or does
899 match a Deny directive will be denied access to the server.
900 <br /><br />
901 If your rule order is set to 'explicit', the authentication is
902 performed in a similar fashion to rule order 'deny,allow', with the
906 and was available in Apache by specifying allow and deny rules without
907 setting any order.
908 <br /><br />
909 </dd>
911 <dt>
913 </dt>
914 <dd>
915 The general format for the rules is as such:<br />
916 <tt>
917
919 </tt>
920 <br /><br />
925 well:<br />
926 <tt>
929 </tt>
930 <br /><br />
932 Having an empty rule list is equivalent to either using
936 <br /><br />
938 For the IP matching system, the following work:<br />
942 But the following does not work:<br />
944 <br /><br />
945 </dd>
948 <dd>
949 If you have more than one server configured, you can set
951 that server when phpMyAdmin is started, or set it to 0 to be given a
952 list of servers without logging in.<br />
954 MUST be set to that server.
955 <br /><br />
956 </dd>
959 <dd>
960 Defines whether to use gzip output buffering for increased
961 speed in HTTP transfers.
962 <br /><br />
963 </dd>
966 <dd>
967 Whether persistent connections should be used or not (mysql_connect or
968 mysql_pconnect).
969 <br /><br />
970 </dd>
973 <dd>
974 Set the number of seconds a script is allowed to run. If seconds is set
975 to zero, no time limit is imposed.<br />
976 This setting is used while importing/exporting dump files but has no
977 effect when PHP is running in safe mode.
978 <br /><br />
979 </dd>
982 <dd>
983 Mark used tables and make it possible to show databases with locked
984 tables (since 3.23.30).
985 <br /><br />
986 </dd>
989 <dd>
990 Defines whether sql-queries generated by phpMyAdmin should be displayed
991 or not.
992 <br /><br />
993 </dd>
996 <dd>
997 Defines whether normal users (non-administrator) are allowed to
998 delete their own database or not. If set as FALSE, the link "Drop
1000 mydatabase" will be rejected. Quite practical for ISP's with many
1001 customers.
1002 <br /><br />
1003 </dd>
1006 <dd>
1008 displayed when you're about to loose data.
1009 <br /><br />
1010 </dd>
1013 <dd>
1014 Define whether the previous login should be recalled or not in cookie
1015 authentication mode.
1016 <br /><br />
1017 </dd>
1020 <dd>
1021 Define whether the "search string inside database" is enabled or not.
1022 <br /><br />
1023 </dd>
1026 <dd>
1027 Defines whether to use select-based menu and display only the current
1028 tables in the left frame (smaller page).
1029 <br /><br />
1030 </dd>
1033 <dd>
1034 Defines whether to display table comment as tooltip in left frame or
1035 not.
1036 <br /><br />
1037 </dd>
1040 <dd>
1041 Defines whether to display space usage and statistics about databases
1042 and tables or not.<br />
1043 Note that statistics requires at least MySQL 3.23.3 and that, at this
1044 date, MySQL doesn't return such information for Berkeley DB tables.
1045 <br /><br />
1046 </dd>
1048 <dt>
1053 </dt>
1054 <dd>
1058 starting main (right) frame. This setting does not check MySQL commands
1059 entered directly.
1060 <br /><br />
1062 Please note that to block the usage of phpinfo() in scripts, you
1063 have to put this in your php.ini:<br />
1065 <br /><br />
1069 coded password value in the configuration file, end users can't be
1070 allowed to change their passwords.
1071 <br /><br />
1072 </dd>
1075 <dd>
1076 Defines whether to suggest a database name on the
1078 <br /><br />
1079 </dd>
1082 <dd>
1084 content or not.
1085 <br /><br />
1086 </dd>
1089 <dd>
1090 Defines whether navigation bar buttons contain text or symbols only.
1091 <br /><br />
1092 </dd>
1095 <dd>
1096 Defines whether an user should be displayed a
1098 <br /><br />
1099 </dd>
1102 <dd>
1103 Number of rows displayed when browsing a resultset. If the resultset
1104 contains more rows, Previous/Next links will be shown.
1105 <br /><br />
1106 </dd>
1109 <dd>
1113 DATE, DATETIME & TIMESTAMP, ascending order else- by default.
1114 <br /><br />
1115 </dd>
1118 <dd>
1120 from edition when browsing a table's content or not.
1121 Valid values are:<br />
1124 <br />
1127 <br /><br />
1128 </dd>
1131 <dd>
1132 Defines whether MySQL functions fields should be displayed or not in
1133 edit/insert mode.
1134 <br /><br />
1135 </dd>
1138 <dd>
1139 Defines which type of editing controls should be used for CHAR and
1140 VARCHAR fields. Possible values are:
1141 <ul>
1142 <li>
1143 input - this allows to limit size of text to size of field in
1144 MySQL, but has problems with newlines in fields
1145 </li>
1146 <li>
1147 textarea - no problems with newlines in fields, but also no
1148 length limitations
1149 </li>
1150 </ul>
1151 Default is old behavior so input.
1152 <br /><br />
1153 </dd>
1155 <dt>
1159 </dt>
1160 <dd>
1161 Defines whether to allow the use of zip/gzip/bzip compression when
1162 creating a dump file or not.
1163 <br /><br />
1164 </dd>
1167 <dd>
1168 Defines the tab displayed by default on database view. Possible
1171 <br /><br />
1172 </dd>
1175 <dd>
1176 Defines the tab displayed by default on table view. Possible
1180 <br /><br />
1181 </dd>
1184 <dd>
1185 If set to an URL which points to the MySQL documentation (type depends
1187 generated.
1188 <br />
1190 Documentation page</a> for more information about MySQL manuals and
1191 their types.
1192 <br /><br />
1193 </dd>
1196 <dd>
1197 Type of MySQL documentation:
1198 <ul>
1204 </ul>
1205 <br /><br />
1206 </dd>
1209 <dd>
1210 Defines the default language to use, if not browser-defined or
1211 user-defined.<br />
1213 this setting.
1214 <br /><br />
1215 </dd>
1218 <dd>
1219 Force: always use this language (must be defined in the
1221 <br /><br />
1222 </dd>
1225 <dd>
1226 Default charset to use for recoding of MySQL queries. This must be
1228 option.<br />
1229 You can give here any charset which is in
1231 choice, user can select any of them.
1232 <br /><br />
1233 </dd>
1236 <dd>
1237 Allow charset recoding of MySQL queries. You need recode or iconv
1238 support (compiled in or module) in php to allow MySQL queries recoding
1239 and used language file must have it enabled (by default only these
1240 which are in unicode, just to avoid losing some characters).
1241 <br /><br />
1242 </dd>
1245 <dd>
1246 You can select here which functions will be used for charset
1247 conversion.
1248 Possible values are:<br />
1249 <ul>
1250 <li>auto - automatically use available one (first is tested
1251 iconv, then recode)</li>
1254 </ul>
1255 Default is auto.
1256 <br /><br />
1257 </dd>
1260 <dd>
1261 Available charsets for MySQL conversion. You can add your own (any of
1262 supported by recode/iconv) or remove these which you don't use.
1263 Charsets will be shown in same order as here listed, so if you
1264 frequently use some of these move them to the top.
1265 <br /><br />
1266 </dd>
1269 <dd>
1270 Left frame width in pixel.
1271 <br /><br />
1272 </dd>
1274 <dt>
1277 </dt>
1278 <dd>
1279 The background colors (HTML) used for both the frames.
1280 <br /><br />
1281 </dd>
1283 <dt>
1285 </dt>
1286 <dd>
1287 The URI of the background image used for the right frame. It can be
1288 absolute as well as relative from your phpMyAdmin directory.
1289 </dd>
1292 <dd>
1293 The color (HTML) used for the pointer in the left frame (does not work
1294 with NS4).
1295 <br /><br />
1296 </dd>
1299 <dd>
1300 The size of a table's border.
1301 <br /><br />
1302 </dd>
1305 <dd>
1306 The color (HTML) used for table headers.
1307 <br /><br />
1308 </dd>
1311 <dd>
1312 The color (HTML) #1 for table rows.
1313 <br /><br />
1314 </dd>
1317 <dd>
1318 The color (HTML) #2 for table rows.
1319 <br /><br />
1320 </dd>
1322 <dt>
1325 </dt>
1326 <dd>
1327 The colors (HTML) uses for the pointer and the marker in browse mode
1328 (does not work with NS4).<br />
1329 The former feature highlights the row over which your mouse is passing
1330 and the latter lets you visually mark/unmark rows by clicking on
1331 them.<br />
1332 You can disable both of these features by emptying the respective
1333 directive.
1334 <br /><br />
1335 </dd>
1337 <dt>
1342 </dt>
1343 <dd>
1344 Number of columns and rows for the textareas.<br />
1346 The Char* values are used for CHAR and VARCHAR editing (if configured
1347 via $cfg['CharEditing']).
1348 <br /><br />
1349 </dd>
1351 <dt>
1353 </dt>
1354 <dd>
1355 Defines if the whole textarea of the query box will be selected on
1356 click.
1357 <br /><br />
1358 </dd>
1361 <dd>
1363 field on browse view. Can be turned off by a toggle button on the
1364 browse page.
1365 <br /><br />
1366 </dd>
1368 <dt>
1371 </dt>
1372 <dd>
1373 Defines the place where modify and delete links would be put when
1374 tables contents are displayed (you may have them displayed both at the
1375 left and at the right).
1378 <br /><br />
1379 </dd>
1382 <dd>
1383 There are 2 display modes: horizontal and vertical. Define which one is
1384 displayed by default.
1385 <br /><br />
1386 </dd>
1389 <dd>
1390 The name of the directory, ending with a slash, where SQL files have
1391 been uploaded by other means than phpMyAdmin (for example, ftp).
1392 Those files are available under a drop-down box when you click the
1393 database name, then the SQL tab.
1394 <br /><br />
1396 <br /><br />
1397 This feature is useful when your file is too big to be uploaded via
1398 HTTP, or when file uploads are disabled in PHP.
1399 <br /><br />
1400 Please note that if PHP is running in safe mode, this directory must
1401 be owned by the same user as the owner of the phpMyAdmin scripts.
1402 <br /><br />
1403 </dd>
1406 <dd>
1407 Repeat the headers every X cells, or 0 to deactivate.
1408 <br /><br />
1409 </dd>
1412 <dd>
1413 As of phpMyAdmin 2.3.0, we now have a fully functional SQL Parser system.
1414 It is enabled by default, as it is used to format the SQL queries.
1415 <br />
1416 As of 2.3.1, it will become an integral part of phpMyAdmin, as it will
1417 analyze certain queries to improve the behavior of phpMyAdmin. But as
1418 it is very new, and not yet heavily used, we offer you an option to
1419 turn it off.
1420 <br /><br />
1421 </dd>
1424 <dd>
1425 The main use of the new SQL Parser is to pretty-print SQL queries. By
1426 default we use HTML to format the query, but you can disable this by
1428 <br /><br />
1429 </dd>
1433 <dd>
1434 For the pretty-printing of SQL queries, under some cases the part of a
1435 query inside a bracket is indented. By changing
1438 specifies the units of the indent amount that you specified. This is
1439 used via stylesheets.
1440 <br /><br />
1441 </dd>
1444 <dd>
1445 This array is used to define the colours for each type of element of
1446 the pretty-printed SQL queries. The tuple format is<br />
1448 If you specify an empty string for the color of a class, it is ignored
1449 in creating the stylesheet.
1450 You should not alter the class names, only the colour strings.<br />
1452 <ul>
1476 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1477 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1478 </ul><br />
1479 </dd>
1481 <dt><b>$cfg['SQLValidator']['use']</b> boolean</dt>
1482 <dd>
1483 phpMyAdmin now supports use of the <a class="navigation" href="http://developer.mimer.com/validator/index.htm">Mimer SQL Validator</a> service,
1484 as originally published on
1485 <a class="navigation" href="http://developers.slashdot.org/article.pl?sid=02/02/19/1720246">Slashdot</a>.
1486 <br />
1487 For help in setting up your system to use the service, see the
1489 <br /><br />
1490 </dd>
1492 <dt><b>$cfg['SQLValidator']['username']</b> string<br />
1493 <b>$cfg['SQLValidator']['password']</b> string</dt>
1494 <dd>
1495 The SOAP service allows you to login with <tt>anonymous</tt>
1496 and any password, so we use those by default.. Instead, if
1497 you have an account with them, you can put your login details
1498 here, and it will be used in place of the anonymous login.
1499 <br /><br />
1500 </dd>
1502 <dt><b>$cfg['ColumnTypes'] </b>array</dt>
1503 <dd>
1504 All possible types of a MySQL column. In most cases you don't need to
1505 edit this.
1506 <br /><br />
1507 </dd>
1509 <dt><b>$cfg['AttributeTypes'] </b>array</dt>
1510 <dd>
1511 Possible attributes for fields. In most cases you don't need to edit
1512 this.
1513 <br /><br />
1514 </dd>
1516 <dt><b>$cfg['Functions'] </b>array</dt>
1517 <dd>
1518 A list of functions MySQL supports. In most cases you don't need to
1519 edit this.
1520 <br /><br />
1521 </dd>
1523 </dl>
1526 <!-- FAQ -->
1538 </font>
1541 <h2>FAQ - Frequently Asked Questions</h2>
1551 <h3>[1. Server]</h3>
1552 <p>
1553 <b>[1.1] I'm running php 4+ and my server is crashing each time a specific
1554 action is required or phpMyAdmin sends a blank page or a page full of
1555 cryptic characters to my browser, what can I do?</b>
1556 <br />
1557 There are some known php bugs with output buffering and compression.<br />
1558 Try to set the <tt>$cfg['OBGzip']</tt> directive to <tt>FALSE</tt> in your
1559 <i>config.inc.php or .php3</i> file and the
1560 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
1561 configuration file.<br />
1562 Furthermore, we know about such problems connected to the release
1563 candidates of php 4.2.0 (tested with php 4.2.0 RC1 to RC4) together with
1564 MS Internet Explorer. Please upgrade to the release version php 4.2.0.
1565 </p>
1567 <p>
1568 <b>[1.2] My Apache server crashes when using phpMyAdmin.</b>
1569 <br />
1570 You should first try the latest versions of Apache (and possibly MySQL).
1571 <br />
1572 See also the other FAQ entry about php bugs with output buffering.
1573 <br />
1574 If your server keeps crashing, please ask for help in the various
1575 Apache support groups.
1576 </p>
1578 <p>
1580 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
1581 script: I'm always displayed the login screen.</b>
1582 <br />
1583 This is a known PHP bug (see this
1585 official php bug database. It means there is and won't be any phpMyAdmin
1586 fix against it because there is no way to code a fix.
1587 </p>
1589 <p>
1590 <b>[1.4] Using phpMyAdmin on IIS, I'm displayed the error message:
1591 "The specified CGI application misbehaved by not returning a
1592 complete set of HTTP headers...."</b>
1593 <br />
1594 You just forgot to read the <i>install.txt</i> file from the php
1595 distribution. Have a look at the last message in this
1597 official php bug database.
1598 </p>
1600 <p>
1601 <b>[1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
1602 messages with the http or advanced authentication mode.</b>
1603 <br />
1604 This is a known problem with the php ISAPI filter: it's not so stable. For
1605 some more information and complete testings see the messages posted by
1606 André B. aka "djdeluxe76" in
1607 <a href="http://www.phpwizard.net/phorum/read.php?f=1&i=6624&t=6300">this thread</a>
1608 from the phpWizard forum.<br />
1609 Please use instead the cookie authentication mode.
1610 </p>
1612 <p>
1613 <b>[1.6] I can't use phpMyAdmin on PWS: nothing is displayed!</b>
1614 <br />
1615 This seems to be a PWS bug. Filippo Simoncini found a workaroud (at this
1616 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
1617 declarations (2 lines) from the scripts <i>header.inc.php3</i>,
1618 <i>header_printview.inc.php3</i>, <i>index.php3</i>, <i>left.php3</i> and
1619 <i>libraries/common.lib.php3</i>.
1620 </p>
1622 <p>
1623 <b>[1.7] How can I GZip or Bzip a dump or a CSV export. It seems to not
1624 work?</b>
1625 <br />
1626 These features are based on the <tt>gzencode()</tt> and
1627 <tt>bzcompress()</tt> php functions to be more independent of the platform
1628 (Unix/Windows, Safe Mode or not, and so on).
1629 So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
1630 (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
1631 We faced php crashes when trying to download a dump with MS Internet
1632 Explorer when phpMyAdmin is run with a release candidate of php 4.2.0. In
1633 this case you should switch to the release version of php 4.2.0.
1634 </p>
1636 <p>
1637 <b>[1.8] I cannot insert a text file in a table, and I get an error about
1638 safe mode being in effect.</b>
1639 <br />
1640 Your uploaded file is saved by PHP in the "upload dir", as
1641 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
1642 the system default is <i>/tmp</i>).
1643 <br />
1644 We recommend the following setup for Apache servers running in safe mode,
1645 to enable uploads of files while being reasonably secure:
1646 </p>
1647 <ul>
1648 <li>create a separate directory for uploads:
1649 <tt>mkdir /tmp/php</tt></li>
1650 <li>give ownership to the Apache server's user.group:
1651 <tt>chown apache.apache /tmp/php</tt></li>
1652 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
1653 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in php.ini</li>
1654 <li>restart Apache</li>
1655 </ul>
1657 <p>
1658 <b>[1.9] I'm having troubles when uploading files. In general file uploads
1659 don't work on my system and uploaded files have a <tt>Content-Type:</tt>
1660 header in the first line.</b>
1661 <br />
1662 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
1663 and you updated your php rpm to php-4.0.4pl1-3.i386.rpm, didn't you?
1664 <br />
1665 So the problem is that this package has a serious bug that was corrected
1666 ages ago in php (2001-01-28: see
1668 for more details). The problem is that the bugged package is still
1669 available though it was corrected (see
1671 for more details).
1672 <br />
1673 So please download
1674 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
1675 and the problem should go away.
1676 <br />
1677 And that fixes the \r\n problem with file uploads!
1678 </p>
1680 <p>
1681 <b>[1.10] I'm having troubles when uploading files with phpMyAdmin running
1682 on a secure server. My browser is Internet Explorer and I'm using the
1683 Apache server.</b>
1684 <br />
1685 As suggested by "Rob M" in the phpWizard forum, add this line to
1686 your <i>httpd.conf</i>:<br />
1687 <tt>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</tt><br />
1688 It seems to clear up many problems between IE and SSL.
1689 </p>
1691 <p>
1692 <b>[1.11] I get an 'open_basedir restriction' while uploading a file from
1693 the query box.</b>
1694 <br />
1695 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
1696 restrictions. Assuming that the restriction allows you to open files in the
1697 current directory ('.'), all you have to do is create a 'tmp' directory
1698 under the phpMyAdmin install directory, with permissions 777 and the same
1699 owner as the owner of your phpMyAdmin directory. The uploaded files will
1700 be moved there, and after execution of your SQL commands, removed.
1701 </p>
1703 <p>
1704 <b>[1.12] I have lost my MySQL root password, what can I do?</b>
1705 <br />
1706 The MySql manual explains how to
1708 reset the permissions</a>.
1709 </p>
1711 <p>
1712 <b>[1.13] I get an error 'No SQL query' when trying to execute a
1713 bookmark.</b>
1714 <br />
1715 If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
1716 cannot access the uploaded query.
1717 </p>
1719 <p>
1720 <b>[1.14] I get an error 'No SQL query' when trying to submit a query from
1721 the convenient text area.</b>
1722 <br />
1723 Check the <tt>post_max_size</tt> directive from your php configuration file
1724 and try to increase it.
1725 </p>
1727 <p>
1728 <b>[1.15] I have problems with <i>mysql.user</i> field names.</b>
1729 <br />
1730 In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
1731 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
1732 names to align with current standards.
1733 </p>
1734 <p>
1735 <b>[1.16] I cannot upload big dump files.</b>
1736 <br />
1737 The first things to check (or ask your host provider to check) are the
1738 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
1739 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
1740 <br />
1741 All of these three settings limit the maximum size of data that can be
1742 submitted and handled by php. One user also said that post_max_size
1743 and memory_limit need to be larger than upload_max_filesize.
1744 </p>
1746 <p>
1747 <b>[1.17] Does phpMyAdmin support MySQL 4?</b>
1748 <br />
1749 MySQL 4 is not yet fully supported by phpMyAdmin.<br />
1750 Because of MySQL 4's backwards compatibility you can use phpMyAdmin
1751 for administering MySQL 4 servers, but phpMyAdmin does not yet
1752 support its new features. Please notice that in this case it is recommended
1753 to use php >= 4.1 since older versions of php are not
1754 compatible to MySQL 4.<br />
1755 Furthermore, several users reported problems with phpMyAdmin related to
1757 release and should be used for test purposes only!</font>
1758 Because of a major change in the definition syntax of string field types,
1759 this version of phpMyAdmin probably won't work correctly with
1760 MySQL >= 4.1.0! We will work on the support as soon as
1761 MySQL 4.1.0 is released.
1762 </p>
1764 <p>
1765 <b>[1.18] I'm running MySQL <= 4.0.1 having
1766 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
1767 capital letter in its name it is changed to lowercase as it should. But
1768 if I try to DROP this table MySQL is unable to find the corresponding
1769 file.</b>
1770 <br />
1771 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
1772 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
1773 directive.
1774 </p>
1776 <p>
1777 <b>[1.19] I can't run the "display relations" feature because the
1778 script seems not to know the font face I'm using!</b>
1779 <br />
1780 The "FPDF" library we're using for this feature requires some
1781 special files to use font faces.<br />
1782 Please refers to the
1784 these files.
1785 </p>
1788 <p>
1789 <b>[1.20] I receive the error "cannot load MySQL extension, please
1790 check PHP Configuration".</b>
1791 <br />
1792 To connect to a MySQL server, PHP needs a set of MySQL functions called
1793 "MySQL extension".
1794 This extension may be part of the PHP server (compiled-in), otherwise it
1795 needs to be loaded dynamically. Its name is probably <i>mysql.so</i> or
1796 <i>mysql.dll</i>. phpMyAdmin tried to load the extension but failed.
1797 <br /><br />
1798 Usually, the problem is solved by installing a software package called
1799 "PHP-MySQL" or something similar.
1800 </p>
1802 <p>
1803 <b>[1.21] I am running the CGI version of PHP under Unix, and I cannot
1804 login using cookie auth.</b>
1805 <br />
1806 In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.
1807 </p>
1809 <p>
1810 <b>[1.22] I don't see the "Location of text file" field, so
1811 I cannot upload.</b>
1812 <br />
1813 This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
1814 parameter is not set to "on".
1815 </p>
1817 <p>
1818 <b>[1.23] I'm running MySQL on a Win32 machine. Each time I create a new
1819 table the table and field names are changed to lowercase!</b>
1820 <br />
1821 This happens because the MySQL directive <tt>lower_case_table_names</tt>
1822 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
1823 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
1824 Just edit you <tt>my.ini</tt> file that should be located in your Windows
1825 directory and add the following line:<br />
1826 <tt>lower-case-table-names=0</tt><br />
1827 Next, save the file and restart the MySQL service. You can always check the
1828 value of this directive using the query<br />
1829 <tt>SHOW VARIABLES LIKE 'lower_case_table_names';</tt>
1830 </p>
1832 <p>
1833 <b>[1.24] Some characters are being truncated in my queries, or I get
1834 characters randomly added. I am running PHP 4.2.3.</b>
1835 <br />
1836 This is a
1838 </p>
1840 <p>
1841 <b>[1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
1842 and I get problems, such as undefined variables when I run a SQL query.</b>
1843 <br />
1844 A tip from Jose Fandos: put a comment on the following two lines
1845 in httpd.conf, like this:<br />
1846 <tt># mod_gzip_item_include file \.php$</tt><br />
1848 as this version of mod_gzip on Apache (Windows) has problems handling
1849 php scripts. Of course you have to restart Apache.
1850 </p>
1852 <p>
1853 <b>[1.26] I just installed phpMyAdmin in my document root of IIS but
1854 I get the error "No input file specified" when trying to
1855 run phpMyAdmin.</b>
1856 <br />
1857 This is a permission problem. Right-click on the phpmyadmin folder
1858 and choose properties. Under the tab Security, click on "Add"
1859 and select the user "IUSER_machine" from the list. Now set his
1860 permissions and it should work.
1861 </p>
1864 <h3>[2. Configuration]</h3>
1866 <p>
1867 <b>[2.1] The error message "Warning: Cannot add header information -
1868 headers already sent by ..." is displayed, what's the problem?</b>
1869 <br />
1870 Edit your <i>config.inc.php or .php3</i> file and ensure there is nothing
1871 (ie no blank lines, no spaces, no characters...) neither before the
1872 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
1873 tag at the end.
1874 </p>
1876 <p>
1877 <b>[2.2] phpMyAdmin can't connect to MySQL. What's wrong?</b>
1878 <br />
1879 Either there is an error with your PHP setup or your username/password is
1880 wrong. Try to make a small script which uses mysql_connect and see if it
1881 works. If it doesn't, it may be you haven't even compiled MySQL support
1882 into PHP.
1883 </p>
1885 <p>
1886 <b>[2.3] The error message "Warning: MySQL Connection Failed: Can't
1887 connect to local MySQL server through socket '/tmp/mysql.sock'
1888 (111)..." is displayed. What can I do?</b>
1889 <br /><br />
1890 For RedHat users, Harald Legner suggests this on the mailing list:
1891 <br /><br />
1892 On my RedHat-Box the socket of mysql is <i>/var/lib/mysql/mysql.sock</i>.
1893 In your php.ini you will find a line
1894 <br />
1895 <tt>mysql.default_socket = /tmp/mysql.sock</tt>
1896 <br />
1897 change it to
1898 <br />
1899 <tt>mysql.default_socket = /var/lib/mysql/mysql.sock</tt>
1900 <br />
1901 Then restart apache and it will work.
1902 <br /><br />
1903 Here is a fix suggested by Brad Ummer in the phpwizard forum:
1904 </p>
1905 <ul>
1906 <li>
1907 First, you need to determine what socket is being used by MySQL.
1908 <br />
1909 To do this, telnet to your server and go to the MySQL bin directory. In
1910 this directory there should be a file named <i>mysqladmin</i>. Type
1911 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
1912 info about your MySQL server, including the socket
1913 (<i>/tmp/mysql.sock</i>, for example).
1914 </li>
1915 <li>
1916 Then, you need to tell PHP to use this socket.<br />Assuming you are
1917 using PHP 3.0.10 or better, you can specify the socket to use when you
1918 open the connection. To do this in phpMyAdmin, you need to complete the
1919 socket information in the config.inc.php3.<br />
1920 For example:
1921 <tt>$cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</tt>
1922 </li>
1923 </ul>
1924 <p>
1925 Have also a look at the
1926 <a class="navigation" href="http://www.mysql.com/doc/C/a/Can_not_connect_to_server.html" target="_blank">
1927 corresponding section of the MySQL documentation</a>.
1928 </p>
1930 <p>
1931 <b>[2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
1932 what can I do?</b>
1933 <br />
1934 Try to set the <tt>$cfg['OBGZip']</tt> directive to <tt>FALSE</tt> in the
1935 phpMyAdmin configuration file. It helps sometime.<br />
1936 Also have a look at your php version number: if it contains
1937 "4.0b..." it means you're running a beta version of PHP. That's
1938 not a so good idea, please upgrade to a plain revision.
1939 </p>
1941 <p>
1942 <b>[2.5] Each time I want to insert or change a record or drop a database
1943 or a table, an error 404 (page not found) is displayed or, with http or
1944 cookie authentication, I'm asked to login again. What's wrong?</b>
1945 <br />
1946 Check the value you set for the <tt>$cfg['PmaAbsoluteUri']</tt> directive
1947 in the phpMyAdmin configuration file.
1948 </p>
1952 <h3>[3. Known limitations]</h3>
1954 <p>
1955 <b>[3.1] When using http authentication, an user who logged out can not
1956 relog in with the same nick.</b>
1957 <br />
1958 This is related to the authentication mechanism (protocol) used by
1959 phpMyAdmin. We plan to change it as soon as we may find enough free time
1960 to do it, but you can bypass this problem: just close all the opened
1961 browser windows and then go back to phpMyAdmin. You should be able to
1962 logs in again.
1963 </p>
1965 <p>
1966 <b>[3.2] When dumping a large table in compressed mode, I get a memory
1967 limit error or a time limit error.</b>
1968 <br />
1969 As of version 2.2.4, we build the compressed dump in memory, so large
1970 tables dumps may hang. The only alternative we can think about (using
1971 system calls to mysqldump then gzip or bzip2) would not be applicable in
1972 environments where PHP is in safe mode: access to system programs is
1973 is limited by the system administrator, and time limit is enforced.
1974 </p>
1976 <p>
1977 <b>[3.3] With InnoDB tables, I lose foreign key relationships when I rename
1978 or alter a table.</b>
1979 <br />
1980 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in
1981 mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
1982 </p>
1984 <p>
1985 <b>[3.4] I am unable to import dumps I created with the mysqldump tool
1986 bundled with the MySQL server distribution.</b>
1987 <br />
1988 The problem is that mysqldump creates invalid comments like this:<br />
1989 <blockquote><tt>
1990 -- MySQL dump 8.22<br />
1991 --<br />
1992 -- Host: localhost Database: database<br />
1993 ---------------------------------------------------------<br />
1994 -- Server version 3.23.54<br />
1995 </tt></blockquote>
1996 The invalid part of the code is the horizontal line made of dashes that
1997 appears once in every dump created with mysqldump. If you want to run your
1998 dump you have to turn it into valid MySQL. This means, you have to add a
1999 whitespace after the first to dashes of the line or add a # before it:<br/>
2000 <tt>
2001 -- -------------------------------------------------------<br />
2002 </tt>
2003 or<br />
2004 <tt>
2005 #---------------------------------------------------------
2006 </tt>
2007 </p>
2011 <h3>[4. ISPs, multi-user installations ]</h3>
2012 <p>
2013 <b>[4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
2014 need to install it for each customer?</b>
2015 <br />
2016 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
2017 your users. The development of this feature was kindly sponsored by
2018 NetCologne GmbH.
2019 This requires a properly setup MySQL user management and phpMyAdmin
2020 http or cookie authentication. See the install section on
2021 "Using http authentication".
2022 </p>
2024 <p>
2025 <b>[4.2] What's the preferred way of making phpMyAdmin secure against evil
2026 access?</b>
2027 <br />
2028 This depends on your system.<br />
2029 If you're running a server which cannot be accessed by other people, it's
2030 sufficient to use the directory protection bundled with your webserver
2031 (with Apache you can use <i>.htaccess</i> files, for example).<br />
2032 If other people have telnet access to your server, you should use
2033 phpMyAdmin's http authentication feature.
2034 <br /><br />
2035 Suggestions:
2036 </p>
2037 <ul>
2038 <li>
2039 Your <i>config.inc.php3</i> file should be <tt>chmod 660</tt>.
2040 </li>
2041 <li>
2042 All your phpMyAdmin files should be chown phpmy.apache, where phpmy
2043 is a user whose password is only known to you, and apache is the
2044 group under which Apache runs.
2045 </li>
2046 <li>
2047 You should use PHP safe mode, to protect from other users that try
2048 to include your <i>config.inc.php3</i> in their scripts.
2049 </li>
2050 </ul>
2052 <p>
2053 <b>[4.3] I get errors about not being able to include a file in
2054 <i>/lang</i> or in <i>/libraries</i>.</b>
2055 <br />
2056 Check <i>php.ini</i>, or ask your sysadmin to check it. The
2057 <tt>include_path</tt> must contain "." somewhere in it, and
2058 <tt>open_basedir</tt>, if used, must contain "." and
2059 "./lang" to allow normal operation of phpMyAdmin.
2060 </p>
2061 <p>
2062 <b>[4.4] phpMyAdmin always gives "Access denied" when using http
2063 authentication.</b><br />
2064 This could happen for several reasons:
2065 </p>
2066 <ul>
2067 <li>
2068 <tt>$cfg['Servers'][$i]['controluser']</tt> and/or
2069 <tt>$cfg['Servers'][$i]['controlpass']</tt> are wrong.
2070 </li>
2071 <li>
2072 The username/password you specify in the login-dialog are invalid.
2073 </li>
2074 <li>
2075 You have already setup a security mechanism for the
2076 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
2077 phpMyAdmin's authentication, so remove it.
2078 </li>
2079 </ul>
2081 <p>
2082 <b>[4.5] Is it possible to let users create their own databases?</b>
2083 <br />
2084 Starting with 2.2.5, in the user management page, you can enter a wildcard
2085 database name for a user, and put the privileges you want. For example,
2086 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
2087 would let a user create/manage his/her database(s).
2088 </p>
2090 <p>
2091 <b>[4.6] How can I use the Host-based authentication additions?</b>
2092 <br />
2093 If you have existing rules from an old .htaccess file, you can take them
2094 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
2095 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
2096 be a major benefit here if your installation is suited to using it. Then
2097 you can just add those updated lines into the
2098 <tt>$cfg['Servers'][$i]['AllowDeny']['rules']</tt> array.
2099 <br /><br />
2100 If you want a pre-made sample, you can try this fragment. It stops the
2101 'root' user from logging in from any networks other than the private
2102 network IP blocks.
2103 <br />
2104 <tt>
2105 //block root from logging in except from the private networks<br />
2106 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';<br />
2107 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(<br />
2108 'deny root from all',<br />
2109 'allow root from localhost',<br />
2110 'allow root from 10.0.0.0/8',<br />
2111 'allow root from 192.168.0.0/16',<br />
2112 'allow root from 172.16.0.0/12',<br />
2113 );
2114 </tt>
2115 </p>
2118 <h3>[5. Browsers or client OS]</h3>
2119 <p>
2120 <b>[5.1] I get an out of memory error, and my controls are non-functional,
2121 when trying to create a table with more than 14 fields.</b>
2122 <br />
2123 We could reproduce this problem only under Win98/98SE. Testing under
2124 WinNT4 or Win2K, we could easily create more than 60 fields.
2125 <br />
2126 A workaround is to create a smaller number of fields, then come back to
2127 your table properties and add the other fields.
2128 </p>
2130 <p>
2131 <b>[5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.</b>
2132 <br />
2133 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
2134 with each script/website that use forms.<br />
2135 Upgrade or downgrade your Xitami server.
2136 </p>
2138 <p>
2139 <b>[5.3] I have problems dumping tables with Konqueror
2140 (phpMyAdmin 2.2.2)</b>
2141 <br />
2142 With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except that
2143 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
2144 don't seem to work.<br />
2146 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
2147 the user's temporary directory, so they must be moved before closing
2148 Konqueror, or else they disappear. Gzip dumps give an error message.<br />
2150 Testing needs to be done for Konqueror 2.2.2.<br />
2151 </p>
2153 <p>
2154 <b>[5.4] I can't use the cookie authentication mode because Internet
2155 Explorer never stores the cookies.</b>
2156 <br />
2157 MS Internet Explorer seems to be really buggy about cookies, at least till
2158 version 6. And thanks to Andrew Zivolup we've traced also a php 4.1.1 bug
2159 in this area!
2160 <br />
2161 Then, if you're running php 4.1.1, try to upgrade or downgrade... it may
2162 work!
2163 </p>
2165 <p>
2166 <b>[5.5] In Internet Explorer 5.0, I get Javascript errors when browsing my
2167 rows.</b>
2168 <br />
2169 Upgrade to at least Internet Explorer 5.5SP2.<br />
2170 </p>
2172 <p>
2173 <b>[5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying
2174 to modify a row in a table with many fields, or with a text field.</b>
2175 <br />
2176 Your table neither have a primary key nor an unique one, so we must use a
2177 long URL to identify this row. There is a limit on the lenght of the URL in
2178 those browsers, and this not happen in Netscape, for example. The
2179 workaround is to create a primary or unique key, or use another browser.
2180 <br />
2181 </p>
2183 <p>
2184 <b>[5.7] I refresh (reload) my browser, and come back to the welcome
2185 page.</b>
2186 <br />
2187 Some browsers support right-clicking into the frame you want to refresh,
2188 just do this in the right frame.<br />
2189 </p>
2191 <p>
2192 <b>[5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
2193 query box.</b>
2194 <br />
2195 Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future
2196 Mozilla versions.<br />
2197 </p>
2199 <p>
2200 <b>[5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
2201 whitespace in the SQL-Query edit area: the page scrolls down.</b>
2202 <br />
2203 This is a Mozilla bug (see bug #26882 at
2205 </p>
2207 <p>
2208 <b>[5.10] With Netscape 4.75 I get empty rows between each row of data in a
2209 CSV exported file.</b>
2210 <br />
2211 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
2212 data in octet-stream mode. Since we can't detect the specific Netscape
2213 version, we cannot workaround this bug.
2214 </p>
2216 <p>
2217 <b>[5.11] Extended-ASCII characters like German umlauts are displayed
2218 wrong.</b>
2219 <br />
2220 Please ensure that you have set your browser's charset to the one of the
2221 language file you have selected on phpMyAdmin's start page.
2222 Alternatively, you can try the auto detection mode that is supported by the
2223 recent versions of the most browsers.
2224 </p>
2226 <p>
2227 <b>[5.12] Apple OS X: Safari browser changes special characters to
2228 "?".</b>
2229 <br />
2230 This issue has been reported by a OS X user, who adds that Chimera,
2231 Netscape and Mozilla do not have this problem.
2232 </p>
2235 <h3>[6. Using phpMyAdmin]</h3>
2236 <p>
2237 <b>[6.1] I can't insert new rows into a table / I can't create a table
2238 - MySQL brings up a SQL-error.</b>
2239 <br />
2240 Examine the SQL error with care. Often the problem is caused by
2241 specifying a wrong field-type.<br />
2242 Common errors include:
2243 </p>
2244 <ul>
2245 <li>Using <tt>VARCHAR</tt> without a size argument</li>
2246 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
2247 </ul>
2248 <p>
2249 Also, look at the syntax chapter in the MySQL manual to confirm that your
2250 syntax is correct.
2251 </p>
2252 <p>
2253 <b>[6.2] When I create a table, I click the Index checkbox for 2 fields and
2254 phpMyAdmin generates only one index with those 2 fields.</b>
2255 <br />
2256 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
2257 index. If you want two indexes, create the first one when creating the
2258 table, save, then display the table properties and click the Index link to
2259 create the other index.
2260 </p>
2262 <p>
2263 <b>[6.3] How can I insert a null value into my table?</b>
2264 <br />
2265 Since version 2.2.3, you have a checkbox for each field that can be null.
2266 Before 2.2.3, you had to enter "null", without the quotes, as the
2267 field's value.
2268 </p>
2270 <p>
2271 <b>[6.4] How can I backup my database or table?</b>
2272 <br />
2273 Click on a database or table name in the left frame, the properties will be
2274 displayed. Then on the menu, click "Export", you can dump
2275 the structure, the data, or both. This will generate standard SQL
2276 statements that can be used to recreate your database/table.
2277 <br /><br />
2278 You will need to choose "Save as file", so that phpMyAdmin can
2279 transmit the resulting dump to your station. Depending on your PHP
2280 configuration, you will see options to compress the dump. See also the
2281 <tt>$cfg['ExecTimeLimit']</tt> configuration variable.
2282 <br /><br />
2283 For additional help on this subject, look for the word "dump" in
2284 this document.
2285 </p>
2287 <p>
2288 <b>[6.5] How can I restore (upload) my database or table using a dump?
2289 How can I run a ".sql" file?</b>
2290 <br />
2291 Click on a database name in the left frame, the properties will be
2292 local displayed. Then in the "Run SQL query" section, type in
2293 your dump filename, or use the Browse button. Then click Go.
2294 <br /><br />
2295 For additional help on this subject, look for the word "upload"
2296 in this document.
2297 </p>
2299 <p>
2300 <b>[6.6] How can I use the relation table in Query-by-example?</b>
2301 <br />
2302 Here is an example with the tables persons, towns and countries, all
2303 located in the database mydb. If you don't have a <tt>PMA_relation</tt>
2304 table, create it as explained in the configuration section. Then create the
2305 example tables:
2306 <br /><br />
2307 <tt>
2308 CREATE TABLE REL_countries (<br />
2309 country_code char(1) NOT NULL default '',<br />
2310 description varchar(10) NOT NULL default '',<br />
2311 PRIMARY KEY (country_code)<br />
2312 ) TYPE=MyISAM;<br />
2313 <br />
2314 INSERT INTO REL_countries VALUES ('C', 'Canada');<br />
2315 <br />
2316 CREATE TABLE REL_persons (<br />
2317 id tinyint(4) NOT NULL auto_increment,<br />
2318 person_name varchar(32) NOT NULL default '',<br />
2319 town_code varchar(5) default '0',<br />
2320 country_code char(1) NOT NULL default '',<br />
2321 PRIMARY KEY (id)<br />
2322 ) TYPE=MyISAM;<br />
2323 <br />
2324 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');<br />
2325 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');<br />
2326 <br />
2327 CREATE TABLE REL_towns (<br />
2328 town_code varchar(5) NOT NULL default '0',<br />
2329 description varchar(30) NOT NULL default '',<br />
2330 PRIMARY KEY (town_code)<br />
2331 ) TYPE=MyISAM;<br />
2332 <br />
2333 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');<br />
2334 INSERT INTO REL_towns VALUES ('M', 'Montréal');<br />
2335 <br />
2336 </tt>
2337 To setup appropriate links and display information:
2338 <ul>
2339 <li>on table "REL_persons" click Structure, then Relation view</li>
2340 <li>in Links, for "town_code" choose "REL_towns->code"</li>
2341 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
2342 <li>on table "REL_towns" click Structure, then Relation view</li>
2343 <li>in "Choose field to display", choose "description"</li>
2344 <li>repeat the two previous steps for table "REL_countries"</li>
2345 </ul>
2346 <br />
2347 Then test like this:
2348 </p>
2349 <ul>
2350 <li>Click on your db name in the left frame</li>
2351 <li>Choose "Query"</li>
2352 <li>Use tables: persons, towns, countries</li>
2353 <li>Click "Update query"</li>
2354 <li>In the fields row, choose persons.person_name and click the
2355 "Show" tickbox </li>
2356 <li>Do the same for towns.description and countries.descriptions in the
2357 other 2 columns</li>
2358 <li>Click "Update query" and you will see in the query box that
2359 the correct joins have been generated</li>
2360 <li>Click "Submit query"</li>
2361 </ul>
2362 <br />
2365 <p>
2366 <b>[6.7] How can I use the "display field" feature?</b>
2367 <br />
2368 Starting from the previous example, create the PMA_table_info as explained
2369 in the configuration section, then browse your persons table,
2370 and move the mouse over a town code or country code.
2371 </p>
2374 <p>
2375 <b>[6.8] How can I produce a PDF schema of my database?</b>
2376 <br />
2377 First you have to fill the "relation", "table_coords"
2378 and "pdf_pages" configuration variables.
2379 <br /><br />
2380 Then, think about your schema layout: which tables will go on which pages.
2381 </p>
2382 <ul>
2383 <li>Click on your db name in the left frame</li>
2384 <li>Choose "Structure" in the navigation on top</li>
2385 <li>Choose "Edit PDF Pages" which should be somewhere at the
2386 bottom of the page</li>
2387 <li>Enter the name for a first pdf page and submit</li>
2388 <li>Choose this page to edit</li>
2389 <li>Now add a table you want to show on this page and it's coordinates and
2390 submit<br />
2391 First you will have to guess this coordinates of course, so just expect
2392 to have an area of about 297 * 210 and put the tables coordinates
2393 somewhere in there, you will be able to have a look at what happened
2394 and change them later.<br />
2395 For example, x=100 and y=200 means that the table will be at 200 mm
2396 down and 100 mm right from the upper left corner.<br />
2397 Actually if you have a width of more than 300 or a height of more than
2398 200 than it will automatically be scaled but 300*100 is a good start to
2399 have an idea of what coordinates to use.</li>
2400 <li>After every table you submitted you will have the possibility to submit
2401 more tables</li>
2402 <li>When you have entered enough tables Click on your db name in the left
2403 frame again</li>
2404 <li>Now, again at the bottom of the page you should be able to choose
2405 "Display PDF schema"<br />
2406 For testing it might be useful to show the grid as well, so you can see
2407 the coordinates used.<br />
2408 Maybe also choose color and submit.</li>
2409 <li>Save the file he will offer you to something like <i>Schema.pdf</i>
2410 (Internet Explorer has some bug there which might make it offer it
2411 without an extension. Under Windows it is important to have the
2412 extension ".pdf", under other OSes you should be fine just
2413 saving the file under the name it offers).</li>
2414 </ul>
2416 <p>
2417 <b>[6.9] phpMyAdmin is changing the type of one of my columns!</b>
2418 <br />
2419 No, it's MySQL that is doing
2420 <a class="navigation" href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent column type changing</a>.
2421 </p>
2424 <p>
2425 <b>[6.10] My database has an underscore in it's name, and when I grant
2426 privileges to a user for this database, a backslash is added before the
2427 underscore.</b>
2428 <br />
2429 This is normal and means that the grant is done only for this database. If
2430 there was no backslash, this would be a wildcard grant, and the
2431 underscore would mean "any character". So, if the database name
2432 is "john_db", the user would get rights to john1db, john2db...
2433 instead of just john_db.<br /><br />
2434 If you really want to grant using a wildcard, there is a dialog box "
2435 Database (wildcards allowed)" for this.
2436 </p>
2437 <p>
2438 <b>[6.11] What is the curious symbol ø in the table statistics?</b>
2439 <br />
2440 It means "average".
2441 </p>
2444 <p>
2445 <b>[6.12] I want to understand some Export options.</b>
2446 <br />
2447 "Complete inserts" adds the column names on every INSERT command,
2448 for better documentation (but resulting file is bigger).<br />
2449 "Extended inserts" provides a shorter dump file by using only
2450 once the INSERT verb and the table name.<br />
2451 "Enclose table and field names with backquotes" ensures that
2452 field and table names formed with special characters are protected.<br />
2453 </p>
2455 <p>
2456 <b>[6.13] I would like to create a database with a dot in its name.</b>
2457 <br />
2458 This is a bad idea, because in MySQL the syntax "database.table"
2459 is the normal way to reference a database and table name. Worse, MySQL
2460 will usually let you create a database with a dot, but then you cannot
2461 work with it, nor delete it.<br />
2462 </p>
2465 <p>
2466 <b>[6.14] How do I set up the SQL validator?</b>
2467 <br />
2468 To use it, you need a very recent version of PHP, 4.3.0 recommended, with
2469 XML, PCRE and PEAR support. On your system command line, run
2470 <tt>"pear install Net_Socket Net_URL HTTP_Request Mail_Mime Net_DIME
2471 SOAP"</tt> to get the nessecary PEAR modules for usage.
2472 <br />
2473 If you use it, you should be aware that any SQL statement you
2474 submit will be stored anonymously (database/table/column names,
2475 strings, numbers replaced with generic values). The Mimer SQL
2476 Validator itself, is © 2001 Upright Database Technology.
2477 We utilize it as free SOAP service.
2478 </p>
2480 <p>
2481 <b>[6.15] I want to add a BLOB field and put an index on it, but MySQL
2482 says "BLOB column '...' used in key specification without a key
2483 length".</b>
2484 <br />
2485 The right way to do this, is to create the field without any indexes,
2486 then display the table structure and use the "Create an index"
2487 dialog. On this page, you will be able to choose your BLOB field, and
2488 set a size to the index, which is the condition to create an index on
2489 a BLOB field.
2490 <br />
2491 </p>
2493 <p>
2494 <b>[6.16] How can I simply move in page with plenty editing fields?</b>
2495 <br />
2496 You can use Ctrl+arrows for moving on most pages with plenty editing
2497 fields (table structure changes, row editing, etc.).
2498 <br />
2499 </p>
2502 <h3>[7. phpMyAdmin project]</h3>
2503 <p>
2504 <b>[7.1] I have found a bug. How do I inform developers?</b>
2505 <br />
2506 Our Bug Tracker is located at
2507 <a href="http://sourceforge.net/projects/phpmyadmin/">http://sourceforge.net/projects/phpmyadmin/</a>
2508 under the Bugs section.
2509 <br /><br />
2510 But please first discuss your bug with other users:
2511 <br />
2513 http://sourceforge.net/projects/phpmyadmin/</a> (and choose Forums)
2514 </p>
2516 <p>
2517 <b>[7.2] I want to translate the messages to a new language or upgrade an
2518 existing language, where do I start?</b>
2519 <br />
2520 Always use the current cvs version of your language file.
2521 For a new language, start from <i>english-iso-8859-1.inc.php3</i>. If you
2522 don't know how to get the cvs version, please ask one of the developers.
2523 <br />
2524 Please note that we try not to use html entities like &eacute; in
2525 the translations, since we define the right character set in the file.
2526 With html entities, the text on buttons would not display correctly.
2527 <br />
2528 You can then put your translations, as a zip file to avoid losing special
2529 characters, on the sourceforge.net translation tracker.
2530 <br />
2531 It would be a good idea to subscribe to the phpmyadmin-translators mailing
2532 list, because this is where we ask for translations of new messages.
2533 <br />
2534 </p>
2536 <p>
2537 <b>[7.3] I would like to help out with the development of phpMyAdmin. How
2538 should I proceed?</b>
2539 <br />
2540 The following method is preferred for new developers:
2541 </p>
2542 <ul>
2543 <li>
2544 fetch the current CVS tree over anonymous CVS:<br />
2545 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
2546 [Password: simply press the Enter key]<br />
2547 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
2548 [This will create a new sub-directory named phpMyAdmin]
2549 </li>
2550 <li>
2551 add your stuff
2552 </li>
2553 <li>
2554 put the modified files (tar'ed and gzip'ed) inside the patch tracker of
2555 the
2556 <a class="navigation" href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">phpMyAdmin SourceForge account</a>.
2557 </li>
2558 </ul>
2559 <p>
2560 Write access to the CVS tree is granted only to experienced developers who
2561 have already contributed something useful to phpMyAdmin.<br />
2562 Also, have a look at the
2564 </p>
2568 <!-- DEVELOPERS -->
2580 </font>
2583 <h2>Developers Information</h2>
2585 <p>
2586 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
2587 great features have been written by other people and you too can help to
2588 make phpMyAdmin a useful tool.
2589 </p>
2591 <p>
2592 If you're planning to contribute source, please read the following
2593 information:
2594 </p>
2595 <ul>
2596 <li>
2597 All files include <i>header.inc.php3</i> (layout),
2598 <i>libraries/common.lib.php3</i> (common functions) and
2599 <i>config.inc.php3</i>.
2600 <br />
2601 All configuration data belongs in <i>config.inc.php3</i>. Please keep
2602 it free from other code.
2603 <br />
2604 Commonly used functions should be added to
2605 <i>libraries/common.lib.php3</i> and more specific ones may be added
2606 within a library stored into the <i>libraries</i> sub-directory.
2607 </li>
2608 <li>
2609 Obviously, you're free to use whatever coding style you want. But
2610 please try to keep your code as simple as possible: beginners are
2611 using phpMyAdmin as an example application.<br />
2612 As far as possible, we want the scripts to be XHTML1.0 and CSS2
2613 compliant on one hand, they fit
2615 on the other hand. Please pay attention to this.
2616 </li>
2617 <li>
2618 Please try to keep up the file-naming conventions. Table-related stuff
2619 goes to <i>tbl_*.php3</i>, db-related code to <i>db_*.php3</i>,
2620 server-related tools to <i>server_*.php3</i> and so on.
2621 </li>
2622 <li>
2623 Please don't use verbose strings in your code, instead add the string
2624 (at least) to <i>english-iso-8859-1.inc.php3</i> and print() it out.
2625 </li>
2626 <li>
2627 If you want to be really helpful, write an entry for the ChangeLog.
2628 </li>
2629 </ul>
2631 <p>
2632 IMPORTANT: With 1.4.1, development has switched to CVS. The following
2633 method is preferred for new developers:
2634 </p>
2635 <ul>
2636 <li>
2637 fetch the current CVS tree over anonymous CVS:<br />
2638 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
2639 [Password: simply press the Enter key]<br />
2640 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
2641 [This will create a new sub-directory named phpMyAdmin]
2642 </li>
2643 <li>
2644 add your stuff
2645 </li>
2646 <li>
2647 put the modified files (tar'ed and gzip'ed) inside the patch tracker
2648 of the phpMyAdmin SourceForge account
2649 (<a class="navigation" href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">http://sourceforge.net/projects/phpmyadmin/</a>)
2650 </li>
2651 </ul>
2652 <p>
2653 Write access to the CVS tree is granted only to developers who have already
2654 contributed something useful to phpMyAdmin. If you're interested in that,
2655 please contact us using the phpmyadmin-devel mailing list.
2656 </p>
2659 <!-- CREDITS -->
2671 </font>
2674 <h2>Credits</h2>
2676 <pre>
2678 phpMyAdmin - Credits
2679 ====================
2681 CREDITS, in chronological order
2682 -------------------------------
2684 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
2685 * creator of the phpmyadmin project
2686 * maintainer from 1998 to summer 2000
2688 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
2689 * multi-language version
2690 * various fixes and improvements
2691 * project co-administrator
2693 - Olivier Müller <om_at_omnis.ch>
2694 * started SourceForge phpMyAdmin project in March 2001
2695 * sync'ed different existing CVS trees with new features and bugfixes
2696 * multi-language improvements, dynamic language selection
2697 * current project maintainer
2698 * many bugfixes and improvements
2700 - Loïc Chapeaux <lolo_at_phpheaven.net>
2701 * rewrote and optimized javascript, DHTML and DOM stuff
2702 * rewrote the scripts so they fit the PEAR coding standards and
2703 generate XHTML1.0 and CSS2 compliant codes
2704 * improved the language detection system
2705 * many bugfixes and improvements
2707 - Robin Johnson <robbat2_at_users.sourceforge.net>
2708 * database maintence controls
2709 * table type code
2710 * Host authentication IP Allow/Deny
2711 * DB-based configuration (Not completed)
2712 * SQL parser
2713 * SQL validator
2714 * many bugfixes and improvements
2716 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
2717 * bookmarks feature
2718 * multiple dump feature
2719 * gzip dump feature
2720 * zip dump feature
2722 - Geert Lund <glund_at_silversoft.dk>
2723 * various fixes
2724 * moderator of the phpMyAdmin users forum at phpwizard.net
2726 - Korakot Chaovavanich <korakot_at_iname.com>
2727 * "insert as new row" feature
2729 - Pete Kelly <webmaster_at_trafficg.com>
2730 * rewrote and fix dump code
2731 * bugfixes
2733 - Steve Alberty <alberty_at_neptunlabs.de>
2734 * rewrote dump code for PHP4
2735 * mySQL table statistics
2736 * bugfixes
2738 - Benjamin Gandon <gandon_at_isia.cma.fr>
2739 * main author of the version 2.1.0.1
2740 * bugfixes
2742 - Alexander M. Turek <rabus_at_bugfixes.info>
2743 * XML exports
2744 * MySQL 4 related features
2745 * various small features and fixes
2746 * German language file updates
2748 - Mike Beck <mike.beck_at_ibmiller.de>
2749 * automatic joins in QBE
2750 * links column in printview
2751 * Relation view
2753 - Michal Cihar <nijel_at_users.sourceforge.net>
2754 * enhanced index creation/display feature
2755 * feature to use a different charset for HTML than for MySQL
2756 * Czech language file updates
2758 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
2759 (http://sourceforge.net/projects/phpmysqlformgen/)
2760 * suggested the patch for multiple table printviews
2762 - Garvin Hicking <hicking_at_faktor-e.de>
2763 * built the patch for vertical display of table rows
2765 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
2766 * japanese kanji encoding conversion feature
2768 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
2769 * the Cookie authentication mode
2771 - Axel Sander <n8falke_at_users.sourceforge.net>
2772 * table relation-links feature
2774 - Maxime Delorme <delorme.maxime_at_free.fr>
2775 * PDF schema output, thanks also to Olivier Plathey for the
2776 "FPDF" library (see http://www.fpdf.org/).
2778 - Olof Edlund <olof.edlund_at_upright.se>
2779 * SQL validator server
2781 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
2782 * phpMyAdmin logo
2784 And also to the following people who have contributed minor changes,
2785 enhancements, bugfixes or support for a new language since version 2.1.0:
2787 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
2788 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
2789 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
2790 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
2791 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
2792 www.securereality.com.au, Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky,
2793 Rachim Tamsjadi, Kositer Uros, Luís V., Martijn W. van der Lee,
2794 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
2795 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas.
2798 Original Credits of Version 2.1.0
2799 ---------------------------------
2801 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
2802 to create a web-based interface to MySQL using PHP3. Although I have not
2803 used any of his source-code, there are some concepts I've borrowed from
2804 him. phpMyAdmin was created because Peter told me he wasn't going to
2805 further develop his (great) tool.
2806 Thanks go to
2807 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
2808 code for the check when dropping a table or database. He also suggested
2809 that you should be able to specify the primary key on tbl_create.php3. To
2810 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
2811 well as a bug-report. Plus many smaller improvements.
2812 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
2813 were introduced in 1.3.0 (including quite significant ones like the
2814 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
2815 bug-fixes and help.
2816 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
2817 language-independent by outsourcing the strings to a separate file. He
2818 also contributed the French translation.
2819 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
2820 tbl_select.php3, a feature to display only some fields from a table.
2821 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
2822 functions in tbl_change.php3. He also added the
2823 "Query by Example" feature in 2.0.
2824 - Dave Walton <walton_at_nordicdms.com> added support for multiple
2825 servers and is a regular contributor for bug-fixes.
2826 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
2827 features for 2.0.6.
2828 The following people have contributed minor changes, enhancements, bugfixes
2829 or support for a new language:
2830 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
2831 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
2832 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
2833 G. Wieggers.
2835 And thanks to everyone else who sent me email with suggestions, bug-reports
2836 and or just some feedback.
2837 </pre>
2852 </font>
2857 <img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" border="0" height="31" width="88" /></a>
2858
2860 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" border="0" width="88" height="31" /></a>
2861 </p>
2863 </body>
2864 </html>