| blob | fd9630ee1713118823c1f32b9ff8eabd4e15228a |
4 <!-- $Id$ -->
5 <!--
6 vim: expandtab ts=4 sw=4 sts=4 tw=78
7 -->
9 <head>
13 </head>
15 <body>
30 </div>
35 <!-- TOP MENU -->
36 <ul>
37 <li>
39 Sourceforge phpMyAdmin project page [ http://www.phpmyadmin.net/ ]
40 </a>
41 </li>
42 <li>
43 Local documents:
44 <ul>
48 </ul>
49 </li>
50 <li>
51 Documentation version:
53 </li>
54 </ul>
57 <!-- REQUIREMENTS -->
61 <ul>
62 <li>
63 PHP3 or PHP4: phpMyAdmin widely uses the 'str_replace()' php function
69 support</span>;
70 </li>
71 <li>
74 syntax of string field types, this version of phpMyAdmin probably won't
76 </li>
77 <li>
78 a web-browser (doh!).
79 </li>
80 </ul>
83 <!-- INTRODUCTION -->
87 <p>
88 phpMyAdmin can manage a whole MySQL-server (needs a super-user)
89 but also a single database. To accomplish the latter you'll need
90 a properly set up MySQL-user who can read/write only the desired
91 database. It's up to you to look up the appropriate part in the
92 MySQL manual. Currently phpMyAdmin can:
93 </p>
95 <ul>
107 <li>using Query-by-example (QBE), create complex queries automatically connecting required tables</li>
110 <li>
111 communicate in
113 </li>
114 </ul>
117 (*)
118 phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dumps
121 </p>
124 <!-- INSTALLATION -->
128 <p>
130 methods to the MySQL database server. It is still the sysadmin's job to
131 grant permissions on the MySQL databases properly. </span>phpMyAdmin's
133 </p>
135 <p>
137 version before OS X, Stuffit unstuffs with Mac formats.<br />
138 So you'll have to resave as in Bbedit to unix style ALL phpMyAdmin scripts
139 before uploading them to your server, as PHP seems not to like Mac-style
141 </p>
143 <p>
146 if you are using a kit with files having this extension.
147 </p>
150 <ol>
151 <li> Choose and download a distribution kit with the files having the
153 web/PHP server interprets those extensions.</li>
154 <li> Untar or unzip the distribution (be sure to unzip the subdirectories):
156 document root. If you don't have direct access to your document root,
157 put the files in a directory on your local machine, and, after step 3,
158 transfer the directory on your web server using, for example, ftp.</li>
159 <li> Open the file config.inc.php3 in your favourite editor and change
160 the values for host, user, password and authentication mode to fit
163 Have a look at
165 explanation of all values.</li>
166 <li> It is recommended that you protect the directory in which you
167 installed phpMyAdmin (unless it's on a closed intranet, or you wish to
168 use http or cookie authentication), for example with HTTP-AUTH (in a
171 information.</li>
172 <li> Open the file
174 in your browser. phpMyAdmin should now display a welcome screen
175 and your databases, or a login dialog if using http or cookie
176 authentication mode.</li>
177 </ol>
180 <ul>
181 <li>Please do not copy your older config.inc.php3 over the new one: it may
182 offer new configuration variables, and the new version may depend on
183 these for normal behavior. It is suggested instead to insert your site
184 values in the new one.</li>
185 </ul>
188 <ul>
190 environment</b> where you want to give users access to their own
191 database and don't want them to play around with others.
192 <br />
193 Nevertheless be aware that MS Internet Explorer seems to be really
195 bit buggy in this area!<br />
197 http or cookie mode so that your user/password pair are not in clear
198 in the configuration file.<br /><br /></li>
200 <li>Http and cookie authentication modes are more secure: the MySQL
201 password does not need to be set in the phpMyAdmin configuration file
204 <br />
205 However, keep in mind that the password travels in plain text, unless
206 you are using the https protocol.
207 <br />
208 In cookie mode, we send the password in a temporary cookie, so most
209 browsers should not store the password in their cookie file.
210 <br /><br /></li>
212 <li>
213 For 'http' and 'cookie' modes, phpMyAdmin needs a controluser that has
218 You must specify the details for the controluser in the
224 use something else in your file:</b>
225 <pre>
227 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
228 GRANT SELECT (Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv,
229 Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv,
230 Grant_priv, References_priv, Index_priv, Alter_priv)
231 ON mysql.user TO 'pma'@'localhost';
232 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
233 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
234 ON mysql.tables_priv TO 'pma'@'localhost';
236 </pre>
237 ... and if you want to use the many new relation and bookmark
238 features:
239 <pre>
242 </pre>
243 (this of course requires you to have a special DB for
244 phpMyAdmin, the contents will be explained later)
245 </li>
246 <li>
248 privileges on a set of particular databases. Normally you shouldn't
249 give global privileges to an ordinary user, unless you understand
250 the impact of those privileges (for example, you are creating
251 a superuser).<br />
254 <tt>GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';</tt>
255 <br />
256 What the user may now do is controlled entirely by the MySQL user
257 management system.<br />
258 With http or cookie auth mode, you don't need to fill the user/password
260 </li>
261 </ul>
264 <ul>
267 allows you to login as any valid MySQL user.</li>
268 <li>Is only supported with PHP running as an Apache module, not with
269 cgi.</li>
270 </ul>
273 <ul>
274 <li>You can use this method as a replacement for the http
275 authentication (for example, if you're running IIS).
276 </li>
278 <li>With this mode, the use can truly logout of phpMyAdmin and login back
279 with the same username.</li>
280 </ul>
283 <ul>
284 <li>This mode is the less secure one because it requires you to fill the
289 <li>In the ISP FAQ section, there is an entry explaining how to protect
290 your configuration file.<br /></li>
291 <li>For additional security in this mode, you may wish to consider the
294 directives.</li>
295 </ul>
298 <!-- CONFIGURATION -->
302 <p>
305 the option that allows to use the *nix end of line character
307 you have modified.
308 </p>
311 <dl>
313 <dd>
314 Sets here the complete url (with full path) to your phpMyAdmin version.
316 <br /><br />
317 phpMyAdmin needs this setting, because of requirements of the HTTP
318 protocol, explained in RFC2616, section 14.30.
319 <br /><br />
320 Don't forget the slash at the end of your url. The url must contain
321 characters that are valid for a url, and on some servers, the path
322 is case-sensitive.
323 <br /><br />
324 Starting with version 2.3.0, you can try to leave this parameter
325 empty, because the program tries to auto-detect its proper value.
326 Additional details are in the configuration file.
327 <br /><br />
328 Alternatively, this setting can be dynamically completed. For example,
329 you can try to use such a kind of code:
330 <pre>
331 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
332 . $_SERVER['HTTP_HOST']
333 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
336 or
338 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
339 . $_SERVER['SERVER_NAME']
340 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
342 </pre>
346 <br /><br />
347 </dd>
349 <dd>
350 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the system
351 detects your absolute URI automatically, we display a warning to remind
352 you. If you have tested the automatic detection, and it works perfectly
353 for your setup, then you can set this variable to squelch the warning.
354 <br /><br />
355 </dd>
358 <dd>
359 Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
360 with master / foreign - tables (see
362 <br />
363 If you tried to set this up and it does not work for you, have a look on
365 use it. You will find a link that will analyze why those features have
366 been disabled.<br />
367 If you do not want to use those features set this variable to
369 <br /><br />
370 </dd>
373 <dd>
374 Since version 1.4.2, phpMyAdmin supports the administration of multiple
375 MySQL servers.
376 Therefore, a $cfg['Servers']-array has been added which contains
377 the login information for the different servers. The first
380 the second server, etc.
381 If you have only one server to administer, simply leave free the
382 hostname of the other $cfg['Server']-entries.
383 <br /><br />
384 </dd>
387 <dd>
388 The hostname of your $i-th MySQL-server. E.g. localhost.
389 <br /><br />
390 </dd>
393 <dd>
394 The port-number of your $i-th MySQL-server. Default is 3306 (leave
395 blank).
396 <br /><br />
397 </dd>
400 <dd>
401 The path to the socket to use. Leave blank for default.<br />
402 To use the socket feature you must run php 3.0.10 or more.
403 <br /><br />
404 </dd>
407 <dd>
408 What type connection to use with the MySQL server. Your options are
410 is nearly guarenteed to be available on all MySQL servers, while
411 sockets are not supported on some platforms.
412 <br /><br />
413 To use the socket mode, your MySQL server must be on the same machine
414 as the Web server.
415 <br /><br />
416 </dd>
419 <dd>
420 Wheather to use a compressed protocol for the MySQL server connection
421 or not (experimental).<br />
423 </dd>
425 <dt>
428 </dt>
429 <dd>
430 When using http or cookie authentication modes (or 'config'
431 authentication mode since phpMyAdmin 2.2.1), you need to supply the
436 This account is used to check what databases the user will see at
437 login.<br />
440 <br /><br />
441 Note that if you try login to phpMyAdmin with this
445 <br /><br />
446 In versions before 2.2.5, those were called
448 <br /><br />
449 </dd>
452 <dd>
453 Whether config or cookie or http authentication should be used for this
454 server.
456 <ul>
457 <li>
458 'config' authentication
460 way: username and password are stored in
462 </li>
463 <li>
464 'cookie' authentication mode
466 2.2.3 allows you to log in as any valid MySQL user with the
467 help of... cookies. Log name and password are stored in
468 cookies during the session and password is deleted when it
469 ends.
470 </li>
471 <li>
472 'http' authentication (was called 'advanced' in older versions)
474 allows you to log in as any valid MySQL user via HTTP-Auth.
475 </li>
476 </ul><br />
479 for more information.
480 <br /><br />
481 </dd>
483 <dt>
486 </dt>
487 <dd>
488 The user/password-pair which phpMyAdmin will use to connect to this
489 MySQL-server. This user/password pair is not needed when http or cookie
490 authentication is used, and should be empty.<br /><br />
491 </dd>
494 <dd>
495 If set to a(an array of) database name(s), only this(these) database(s)
496 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
497 database(s) name(s) may contain MySQL wilcards characters
501 This setting is an efficient way to lower the server charge since the
502 latter does not need to send MySQL requests to build the available
504 privileges rules of the MySQL database server</span>. If set, it just
505 means only these databases will be displayed but
507 <br /><br />
508 </dd>
511 <dd>
512 Only useful when using phpMyAdmin with multiple server entries. If set,
513 this string will be displayed instead of the hostname in the pulldown
514 menu on the main page. This can be useful if you want to show only
515 certain databases on your system, for example.
516 <br /><br />
517 </dd>
519 <dt>
522 </dt>
523 <dd>
524 Starting with version 2.3.0 phpMyAdmin offers a lot of features
525 to work with master / foreign - tables. To use those as well as
526 the bookmark feature you need special tables with a
527 predefined structure, which we explain below.<br />
528 If you are the only user of this phpMyAdmin installation, you can
529 use your current database to store those special tables; in this
530 case, just put your current database name in
532 <br /><br />
533 If you are setting up a multi-user phpMyAdmin installation,
534 you will need to create a new db and setup special privileges,
535 so, as superuser:
536 <br /><br />
537 <ul>
538 <li>
539 create a new database for phpmyadmin:<br />
543 privileges on this database. Here is a query to set up
546 controluser):<br />
547 <tt>
548 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to 'pma'@'localhost';
549 </tt><br />
551 </li>
552 <li>
554 </li>
555 </ul><br />
556 </dd>
558 <dt>
561 </dt>
562 <dd>
563 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can be
564 useful for queries you often run.<br /><br />
566 To allow the usage of this functionality you have to:
567 <ul>
569 <li>within this database create a table following this scheme:
570 <br />
571 <tt>
580 </tt>
581 </li>
582 <li>enter the tablename in
584 </ul><br />
585 </dd>
587 <dt>
590 </dt>
591 <dd>
592 Since release 2.2.4 you can describe, in a special 'relation' table,
593 which field is a key in another table (a foreign key). phpMyAdmin
594 currently uses this to
595 <ul>
596 <li>
597 make clickable, when you browse the master table, the data values
598 that point to the foreign table;
599 </li>
600 <li>
602 when browsing the master table, if you move the mouse to a column
603 containing a foreign key (use also the 'table_info' table);
604 </li>
605 <li>
606 display links on the table properties page, to check referential
607 integrity (display missing foreign keys) for each described key;
608 </li>
609 <li>
610 in query-by-example, create automatic joins (see an example in
612 </li>
613 <li>
614 enable you to get a PDF schema of your database (also uses the
615 table_coords table).
616 </li>
617 </ul>
618 <br />
620 The keys can be numeric or character.
621 <br /><br />
623 To allow the usage of this functionality the superuser has to:
624 <ul>
626 <li>
627 within this database create a table following this scheme:
628 <br />
629 <tt>
635 `foreign_table` varchar(64) NOT NULL default '',<br />
636 `foreign_field` varchar(64) NOT NULL default '',<br />
637 PRIMARY KEY (`master_db`, `master_table`, `master_field`),<br />
640 </tt>
641 </li>
642 <li>
643 put the relation table name in
645 </li>
646 <li>
647 now as normal user open phpMyAdmin and for each one of your
648 tables where you want to use this feature, click
650 </li>
651 </ul><br />
654 future development of the cross-db relations.<br /><br />
655 </dd>
657 <dt>
660 </dt>
661 <dd>
662 Since release 2.3.0 you can describe, in a special 'table_info'
663 table, which field is to be displayed as a tooltip when moving the
664 cursor over the corresponding key.
665 <br />
666 This configuration variable will hold the name of this special
667 table.
668 To allow the usage of this functionality the superuser has to:
669 <ul>
671 <li>within this database create a table following this scheme:
672 <br />
673 <tt>
677 `display_field` varchar(64) NOT NULL default '',<br />
680 </tt>
681 </li>
682 <li>
683 put the table name in
685 </li>
686 <li>
687 then for each table where you want to use this feature,
689 to choose the field.
690 </li>
691 </ul><br />
693 <br /><br />
694 </dd>
696 <dt>
700 </dt>
701 <dd>
702 Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
703 the relations between your tables. To do this it needs two tables
706 table will be placed on a PDF schema output).
707 <br /><br />
710 output.
711 <br /><br />
712 To allow the usage of this functionality the superuser has to:
713 <ul>
715 <li>
716 within this database create a table following this scheme:
717 <br />
718 <tt>
725 PRIMARY KEY (`db_name`, `table_name`, `pdf_page_number`)<br />
726 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin PDF output';<br />
727 </tt>
728 </li>
729 <li>
730 also within this database create:<br />
731 <tt>
734 `page_nr` int(10) unsigned NOT NULL auto_increment,<br />
739 </tt>
740 </li>
741 <li>
742 put the first table name in
744 and the second table name in
746 </li>
747 </ul><br />
749 <br /><br />
750 </dd>
752 <dt>
755 </dt>
756 <dd>
757 Since release 2.3.0 you can store comments to describe each column
759 <br />
760 To allow the usage of this functionality the superuser has to:
761 <ul>
763 <li>
764 within this database create a table following this scheme:
765 <br />
766 <tt>
774 UNIQUE KEY db_name (db_name, table_name, column_name)<br />
776 </tt>
777 </li>
778 <li>
779 put the table name in
781 </li>
782 </ul><br />
783 </dd>
785 <dt>
787 </dt>
788 <dd>
789 If your rule order is empty, then IP authentication is disabled.
790 <br /><br />
792 applies all deny rules followed by allow rules.
793 Access is allowed by default. Any client which does not match a Deny
794 command or does match an Allow command will be allowed access to the
795 server.
796 <br /><br />
798 applies all allow rules followed by deny rules. Access is denied by
799 default. Any client which does not match an Allow directive or does
800 match a Deny directive will be denied access to the server.
801 <br /><br />
802 If your rule order is set to 'explicit', the authentication is
803 performed in a similar fashion to rule order 'deny,allow', with the
807 and was available in Apache by specifying allow and deny rules without
808 setting any order.
809 <br /><br />
810 </dd>
812 <dt>
814 </dt>
815 <dd>
816 The general format for the rules is as such:<br />
817 <tt>
818
820 </tt>
821 <br /><br />
826 well:<br />
827 <tt>
830 </tt>
831 <br /><br />
833 Having an empty rule list is equivalent to either using
837 <br /><br />
839 For the IP matching system, the following work:<br />
843 But the following does not work:<br />
845 <br /><br />
846 </dd>
849 <dd>
850 If you have more than one server configured, you can set
852 that server when phpMyAdmin is started, or set it to 0 to be given a
853 list of servers without logging in.<br />
855 MUST be set to that server.
856 <br /><br />
857 </dd>
860 <dd>
861 Defines whether to use gzip output buffering for increased
862 speed in HTTP transfers.
863 <br /><br />
864 </dd>
867 <dd>
868 Whether persistent connections should be used or not (mysql_connect or
869 mysql_pconnect).
870 <br /><br />
871 </dd>
874 <dd>
875 Set the number of seconds a script is allowed to run. If seconds is set
876 to zero, no time limit is imposed.<br />
877 This setting is used while importing/exporting dump files but has no
878 effect when PHP is running in safe mode.
879 <br /><br />
880 </dd>
883 <dd>
884 Mark used tables and make it possible to show databases with locked
885 tables (since 3.23.30).
886 <br /><br />
887 </dd>
890 <dd>
891 Defines whether sql-queries generated by phpMyAdmin should be displayed
892 or not.
893 <br /><br />
894 </dd>
897 <dd>
898 Defines whether normal users (non-administrator) are allowed to
899 delete their own database or not. If set as FALSE, the link "Drop
901 mydatabase" will be rejected. Quite practical for ISP's with many
902 customers.
903 <br /><br />
904 </dd>
907 <dd>
909 displayed when you're about to loose data.
910 <br /><br />
911 </dd>
914 <dd>
915 Define whether the previous login should be recalled or not in cookie
916 authentication mode.
917 <br /><br />
918 </dd>
921 <dd>
922 Define whether the "search string inside database" is enabled or not.
923 <br /><br />
924 </dd>
927 <dd>
928 Defines whether to use select-based menu and display only the current
929 tables in the left frame (smaller page).
930 <br /><br />
931 </dd>
934 <dd>
935 Defines whether to display table comment as tooltip in left frame or
936 not.
937 <br /><br />
938 </dd>
941 <dd>
942 Defines whether to display space usage and statistics about databases
943 and tables or not.<br />
944 Note that statistics requires at least MySQL 3.23.3 and that, at this
945 date, MySQL doesn't return such information for Berkeley DB tables.
946 <br /><br />
947 </dd>
949 <dt>
954 </dt>
955 <dd>
959 starting main (right) frame. This setting does not check MySQL commands
960 entered directly.
961 <br /><br />
963 Please note that to block the usage of phpinfo() in scripts, you
964 have to put this in your php.ini:<br />
966 <br /><br />
970 coded password value in the configuration file, end users can't be
971 allowed to change their passwords.
972 <br /><br />
973 </dd>
976 <dd>
977 Defines whether to suggest a database name on the
979 <br /><br />
980 </dd>
983 <dd>
985 content or not.
986 <br /><br />
987 </dd>
990 <dd>
991 Defines whether navigation bar buttons contain text or symbols only.
992 <br /><br />
993 </dd>
996 <dd>
997 Defines whether an user should be displayed a
999 <br /><br />
1000 </dd>
1003 <dd>
1004 Number of rows displayed when browsing a resultset. If the resultset
1005 contains more rows, Previous/Next links will be shown.
1006 <br /><br />
1007 </dd>
1010 <dd>
1014 DATE, DATETIME & TIMESTAMP, ascending order else- by default.
1015 <br /><br />
1016 </dd>
1019 <dd>
1021 from edition when browsing a table's content or not.
1022 Valid values are:<br />
1025 <br />
1028 <br /><br />
1029 </dd>
1032 <dd>
1033 Defines whether MySQL functions fields should be displayed or not in
1034 edit/insert mode.
1035 <br /><br />
1036 </dd>
1039 <dd>
1040 Defines which type of editing controls should be used for CHAR and
1041 VARCHAR fields. Possible values are:
1042 <ul>
1043 <li>
1044 input - this allows to limit size of text to size of field in
1045 MySQL, but has problems with newlines in fields
1046 </li>
1047 <li>
1048 textarea - no problems with newlines in fields, but also no
1049 length limitations
1050 </li>
1051 </ul>
1052 Default is old behavior so input.
1053 <br /><br />
1054 </dd>
1056 <dt>
1060 </dt>
1061 <dd>
1062 Defines whether to allow the use of zip/gzip/bzip compression when
1063 creating a dump file or not.
1064 <br /><br />
1065 </dd>
1068 <dd>
1069 Defines the tab displayed by default on database view. Possible
1072 <br /><br />
1073 </dd>
1076 <dd>
1077 Defines the tab displayed by default on table view. Possible
1081 <br /><br />
1082 </dd>
1085 <dd>
1086 If set to an URL which points to the MySQL documentation (type depends
1088 generated.
1089 <br />
1091 Documentation page</a> for more information about MySQL manuals and
1092 their types.
1093 <br /><br />
1094 </dd>
1097 <dd>
1098 Type of MySQL documentation:
1099 <ul>
1105 </ul>
1106 <br /><br />
1107 </dd>
1110 <dd>
1111 Defines the default language to use, if not browser-defined or
1112 user-defined.<br />
1114 this setting.
1115 <br /><br />
1116 </dd>
1119 <dd>
1120 Force: always use this language (must be defined in the
1122 <br /><br />
1123 </dd>
1126 <dd>
1127 Default charset to use for recoding of MySQL queries. This must be
1129 option.<br />
1130 You can give here any charset which is in
1132 choice, user can select any of them.
1133 <br /><br />
1134 </dd>
1137 <dd>
1138 Allow charset recoding of MySQL queries. You need recode or iconv
1139 support (compiled in or module) in php to allow MySQL queries recoding
1140 and used language file must have it enabled (by default only these
1141 which are in unicode, just to avoid losing some characters).
1142 <br /><br />
1143 </dd>
1146 <dd>
1147 You can select here which functions will be used for charset
1148 conversion.
1149 Possible values are:<br />
1150 <ul>
1151 <li>auto - automatically use available one (first is tested
1152 iconv, then recode)</li>
1155 </ul>
1156 Default is auto.
1157 <br /><br />
1158 </dd>
1161 <dd>
1162 Available charsets for MySQL conversion. You can add your own (any of
1163 supported by recode/iconv) or remove these which you don't use.
1164 Charsets will be shown in same order as here listed, so if you
1165 frequently use some of these move them to the top.
1166 <br /><br />
1167 </dd>
1170 <dd>
1171 Left frame width in pixel.
1172 <br /><br />
1173 </dd>
1175 <dt>
1178 </dt>
1179 <dd>
1180 The background colors (HTML) used for both the frames.
1181 <br /><br />
1182 </dd>
1184 <dt>
1186 </dt>
1187 <dd>
1188 The URI of the background image used for the right frame. It can be
1189 absolute as well as relative from your phpMyAdmin directory.
1190 </dd>
1193 <dd>
1194 The color (HTML) used for the pointer in the left frame (does not work
1195 with NS4).
1196 <br /><br />
1197 </dd>
1200 <dd>
1201 The size of a table's border.
1202 <br /><br />
1203 </dd>
1206 <dd>
1207 The color (HTML) used for table headers.
1208 <br /><br />
1209 </dd>
1212 <dd>
1213 The color (HTML) #1 for table rows.
1214 <br /><br />
1215 </dd>
1218 <dd>
1219 The color (HTML) #2 for table rows.
1220 <br /><br />
1221 </dd>
1223 <dt>
1226 </dt>
1227 <dd>
1228 The colors (HTML) uses for the pointer and the marker in browse mode
1229 (does not work with NS4).<br />
1230 The former feature highlights the row over which your mouse is passing
1231 and the latter lets you visually mark/unmark rows by clicking on
1232 them.<br />
1233 You can disable both of these features by emptying the respective
1234 directive.
1235 <br /><br />
1236 </dd>
1238 <dt>
1243 </dt>
1244 <dd>
1245 Number of columns and rows for the textareas.<br />
1247 The Char* values are used for CHAR and VARCHAR editing (if configured
1248 via $cfg['CharEditing']).
1249 <br /><br />
1250 </dd>
1252 <dt>
1254 </dt>
1255 <dd>
1256 Defines if the whole textarea of the query box will be selected on
1257 click.
1258 <br /><br />
1259 </dd>
1262 <dd>
1264 field on browse view. Can be turned off by a toggle button on the
1265 browse page.
1266 <br /><br />
1267 </dd>
1269 <dt>
1272 </dt>
1273 <dd>
1274 Defines the place where modify and delete links would be put when
1275 tables contents are displayed (you may have them displayed both at the
1276 left and at the right).
1279 <br /><br />
1280 </dd>
1283 <dd>
1284 There are 2 display modes: horizontal and vertical. Define which one is
1285 displayed by default.
1286 <br /><br />
1287 </dd>
1290 <dd>
1291 The name of the directory, ending with a slash, where SQL files have
1292 been uploaded by other means than phpMyAdmin (for example, ftp).
1293 Those files are available under a drop-down box when you click the
1294 database name, then the SQL tab.
1295 <br /><br />
1297 <br /><br />
1298 This feature is useful when your file is too big to be uploaded via
1299 HTTP, or when file uploads are disabled in PHP.
1300 <br /><br />
1301 Please note that if PHP is running in safe mode, this directory must
1302 be owned by the same user as the owner of the phpMyAdmin scripts.
1303 <br /><br />
1304 </dd>
1307 <dd>
1308 Repeat the headers every X cells, or 0 to deactivate.
1309 <br /><br />
1310 </dd>
1313 <dd>
1314 As of phpMyAdmin 2.3.0, we now have a fully functional SQL Parser system.
1315 It is enabled by default, as it is used to format the SQL queries.
1316 <br />
1317 As of 2.3.1, it will become an integral part of phpMyAdmin, as it will
1318 analyze certain queries to improve the behavior of phpMyAdmin. But as
1319 it is very new, and not yet heavily used, we offer you an option to
1320 turn it off.
1321 <br /><br />
1322 </dd>
1325 <dd>
1326 The main use of the new SQL Parser is to pretty-print SQL queries. By
1327 default we use HTML to format the query, but you can disable this by
1329 <br /><br />
1330 </dd>
1334 <dd>
1335 For the pretty-printing of SQL queries, under some cases the part of a
1336 query inside a bracket is indented. By changing
1339 specifies the units of the indent amount that you specified. This is
1340 used via stylesheets.
1341 <br /><br />
1342 </dd>
1345 <dd>
1346 This array is used to define the colours for each type of element of
1347 the pretty-printed SQL queries. The tuple format is<br />
1349 If you specify an empty string for the color of a class, it is ignored
1350 in creating the stylesheet.
1351 You should not alter the class names, only the colour strings.<br />
1353 <ul>
1377 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1378 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1379 </ul><br />
1380 </dd>
1382 <dt><b>$cfg['SQLValidator']['use']</b> boolean</dt>
1383 <dd>
1384 phpMyAdmin now supports use of the <a href="http://developer.mimer.com/validator/index.htm">Mimer SQL Validator</a> service,
1385 as originally published on
1387 <br />
1388 For help in setting up your system to use the service, see the
1390 <br /><br />
1391 </dd>
1393 <dt><b>$cfg['SQLValidator']['username']</b> string<br />
1394 <b>$cfg['SQLValidator']['password']</b> string</dt>
1395 <dd>
1396 The SOAP service allows you to login with <tt>anonymous</tt>
1397 and any password, so we use those by default.. Instead, if
1398 you have an account with them, you can put your login details
1399 here, and it will be used in place of the anonymous login.
1400 <br /><br />
1401 </dd>
1403 <dt><b>$cfg['DBG']['enable']</b> boolean</dt>
1404 <dd>
1405 <b>DEVELOPERS ONLY!</b><br />
1406 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1407 the code.
1408 <br />
1409 For help in setting up your system to this, see the
1411 </dd>
1413 <dt><b>$cfg['DBG']['profile']['enable']</b> boolean</dt>
1414 <dd>
1415 <b>DEVELOPERS ONLY!</b><br />
1416 Enable profiling support for phpMyAdmin. This will append a chunk of data
1417 to the end of every page displayed in the main window with profiling
1418 statistics for that page.<br />
1419 You may need need to increase the maximum execution time for this to
1420 complete successfully.
1421 </dd>
1423 <dt><b>$cfg['DBG']['profile']['threshold']</b> float (units in milliseconds)</dt>
1424 <dd>
1425 <b>DEVELOPERS ONLY!</b><br />
1426 When profiling data is displayed, this variable controls the threshold of
1427 display for any profiling data, based on the average time each time has
1428 taken. If it is over the threshold it is displayed, otherwise it is not
1429 displayed. This takes a value in milliseconds. In most cases you don't need
1430 to edit this.
1431 </dd>
1433 <dt><b>$cfg['ColumnTypes'] </b>array</dt>
1434 <dd>
1435 All possible types of a MySQL column. In most cases you don't need to
1436 edit this.
1437 <br /><br />
1438 </dd>
1440 <dt><b>$cfg['AttributeTypes'] </b>array</dt>
1441 <dd>
1442 Possible attributes for fields. In most cases you don't need to edit
1443 this.
1444 <br /><br />
1445 </dd>
1447 <dt><b>$cfg['Functions'] </b>array</dt>
1448 <dd>
1449 A list of functions MySQL supports. In most cases you don't need to
1450 edit this.
1451 <br /><br />
1452 </dd>
1454 </dl>
1457 <!-- FAQ -->
1459 <h2>FAQ - Frequently Asked Questions</h2>
1461 <p>
1469 </p>
1472 <h3>[1. Server]</h3>
1474 <h4>
1475 [1.1] I'm running php 4+ and my server is crashing each time a specific
1476 action is required or phpMyAdmin sends a blank page or a page full of
1477 cryptic characters to my browser, what can I do
1478 </h4>
1479 <p>
1480 There are some known php bugs with output buffering and compression.<br />
1481 Try to set the <tt>$cfg['OBGzip']</tt> directive to <tt>FALSE</tt> in your
1482 <i>config.inc.php or .php3</i> file and the
1483 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
1484 configuration file.<br />
1485 Furthermore, we know about such problems connected to the release
1486 candidates of php 4.2.0 (tested with php 4.2.0 RC1 to RC4) together with
1487 MS Internet Explorer. Please upgrade to the release version php 4.2.0.
1488 </p>
1490 <h4>
1491 [1.2] My Apache server crashes when using phpMyAdmin
1492 </h4>
1493 <p>
1494 You should first try the latest versions of Apache (and possibly MySQL).
1495 <br />
1496 See also the other FAQ entry about php bugs with output buffering.
1497 <br />
1498 If your server keeps crashing, please ask for help in the various
1499 Apache support groups.
1500 </p>
1502 <h4>
1504 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
1505 script: I'm always displayed the login screen
1506 </h4>
1507 <p>
1508 This is a known PHP bug (see this
1510 official php bug database. It means there is and won't be any phpMyAdmin
1511 fix against it because there is no way to code a fix.
1512 </p>
1514 <h4>
1515 [1.4] Using phpMyAdmin on IIS, I'm displayed the error message:
1516 "The specified CGI application misbehaved by not returning a
1517 complete set of HTTP headers...."</h4>
1518 <p>
1519 You just forgot to read the <i>install.txt</i> file from the php
1520 distribution. Have a look at the last message in this
1522 official php bug database.
1523 </p>
1525 <h4>
1526 [1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
1527 messages with the http or advanced authentication mode
1528 </h4>
1529 <p>
1530 This is a known problem with the php ISAPI filter: it's not so stable. For
1531 some more information and complete testings see the messages posted by
1532 André B. aka "djdeluxe76" in
1533 <a href="http://www.phpwizard.net/phorum/read.php?f=1&i=6624&t=6300">this thread</a>
1534 from the phpWizard forum.<br />
1535 Please use instead the cookie authentication mode.
1536 </p>
1538 <h4>
1539 [1.6] I can't use phpMyAdmin on PWS: nothing is displayed!</h4>
1540 <p>
1541 This seems to be a PWS bug. Filippo Simoncini found a workaroud (at this
1542 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
1543 declarations (2 lines) from the scripts <i>header.inc.php3</i>,
1544 <i>header_printview.inc.php3</i>, <i>index.php3</i>, <i>left.php3</i> and
1545 <i>libraries/common.lib.php3</i>.
1546 </p>
1548 <h4>
1549 [1.7] How can I GZip or Bzip a dump or a CSV export. It seems to not
1550 work
1551 </h4>
1552 <p>
1553 These features are based on the <tt>gzencode()</tt> and
1554 <tt>bzcompress()</tt> php functions to be more independent of the platform
1555 (Unix/Windows, Safe Mode or not, and so on).
1556 So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
1557 (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
1558 We faced php crashes when trying to download a dump with MS Internet
1559 Explorer when phpMyAdmin is run with a release candidate of php 4.2.0. In
1560 this case you should switch to the release version of php 4.2.0.
1561 </p>
1563 <h4>
1564 [1.8] I cannot insert a text file in a table, and I get an error about
1565 safe mode being in effect
1566 </h4>
1567 <p>
1568 Your uploaded file is saved by PHP in the "upload dir", as
1569 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
1570 the system default is <i>/tmp</i>).
1571 <br />
1572 We recommend the following setup for Apache servers running in safe mode,
1573 to enable uploads of files while being reasonably secure:
1574 </p>
1575 <ul>
1576 <li>create a separate directory for uploads:
1577 <tt>mkdir /tmp/php</tt></li>
1578 <li>give ownership to the Apache server's user.group:
1579 <tt>chown apache.apache /tmp/php</tt></li>
1580 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
1581 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in php.ini</li>
1582 <li>restart Apache</li>
1583 </ul>
1585 <h4>
1586 [1.9] I'm having troubles when uploading files. In general file uploads
1587 don't work on my system and uploaded files have a <tt>Content-Type:</tt>
1588 header in the first line
1589 </h4>
1590 <p>
1591 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
1592 and you updated your php rpm to php-4.0.4pl1-3.i386.rpm, didn't you?
1593 <br />
1594 So the problem is that this package has a serious bug that was corrected
1595 ages ago in php (2001-01-28: see
1597 for more details). The problem is that the bugged package is still
1598 available though it was corrected (see
1600 for more details).
1601 <br />
1602 So please download
1603 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
1604 and the problem should go away.
1605 <br />
1606 And that fixes the \r\n problem with file uploads!
1607 </p>
1609 <h4>
1610 [1.10] I'm having troubles when uploading files with phpMyAdmin running
1611 on a secure server. My browser is Internet Explorer and I'm using the
1612 Apache server
1613 </h4>
1614 <p>
1615 As suggested by "Rob M" in the phpWizard forum, add this line to
1616 your <i>httpd.conf</i>:<br />
1617 <tt>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</tt><br />
1618 It seems to clear up many problems between IE and SSL.
1619 </p>
1621 <h4>
1622 [1.11] I get an 'open_basedir restriction' while uploading a file from
1623 the query box
1624 </h4>
1625 <p>
1626 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
1627 restrictions. Assuming that the restriction allows you to open files in the
1628 current directory ('.'), all you have to do is create a 'tmp' directory
1629 under the phpMyAdmin install directory, with permissions 777 and the same
1630 owner as the owner of your phpMyAdmin directory. The uploaded files will
1631 be moved there, and after execution of your SQL commands, removed.
1632 </p>
1634 <h4>
1635 [1.12] I have lost my MySQL root password, what can I do
1636 </h4>
1637 <p>
1638 The MySql manual explains how to
1640 reset the permissions</a>.
1641 </p>
1643 <h4>
1644 [1.13] I get an error 'No SQL query' when trying to execute a
1645 bookmark
1646 </h4>
1647 <p>
1648 If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
1649 cannot access the uploaded query.
1650 </p>
1652 <h4>
1653 [1.14] I get an error 'No SQL query' when trying to submit a query from
1654 the convenient text area
1655 </h4>
1656 <p>
1657 Check the <tt>post_max_size</tt> directive from your php configuration file
1658 and try to increase it.
1659 </p>
1661 <h4>
1662 [1.15] I have problems with <i>mysql.user</i> field names
1663 </h4>
1664 <p>
1665 In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
1666 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
1667 names to align with current standards.
1668 </p>
1669 <h4>
1670 [1.16] I cannot upload big dump files
1671 </h4>
1672 <p>
1673 The first things to check (or ask your host provider to check) are the
1674 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
1675 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
1676 <br />
1677 All of these three settings limit the maximum size of data that can be
1678 submitted and handled by php. One user also said that post_max_size
1679 and memory_limit need to be larger than upload_max_filesize.
1680 </p>
1682 <h4>
1683 [1.17] Does phpMyAdmin support MySQL 4.1
1684 </h4>
1685 <p>
1686 Because of a major change in the definition syntax of string field types,
1687 this version of phpMyAdmin probably won't work correctly with
1688 MySQL >= 4.1.0! We will work on the support as soon as
1689 MySQL 4.1.0 is released.
1690 </p>
1692 <h4>
1693 [1.18] I'm running MySQL <= 4.0.1 having
1694 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
1695 capital letter in its name it is changed to lowercase as it should. But
1696 if I try to DROP this table MySQL is unable to find the corresponding
1697 file
1698 </h4>
1699 <p>
1700 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
1701 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
1702 directive.
1703 </p>
1705 <h4>
1706 [1.19] I can't run the "display relations" feature because the
1707 script seems not to know the font face I'm using!</h4>
1708 <p>
1709 The "FPDF" library we're using for this feature requires some
1710 special files to use font faces.<br />
1711 Please refers to the
1713 these files.
1714 </p>
1717 <h4>
1718 [1.20] I receive the error "cannot load MySQL extension, please
1719 check PHP Configuration"
1720 </h4>
1721 <p>
1722 To connect to a MySQL server, PHP needs a set of MySQL functions called
1723 "MySQL extension".
1724 This extension may be part of the PHP server (compiled-in), otherwise it
1725 needs to be loaded dynamically. Its name is probably <i>mysql.so</i> or
1726 <i>mysql.dll</i>. phpMyAdmin tried to load the extension but failed.
1727 <br /><br />
1728 Usually, the problem is solved by installing a software package called
1729 "PHP-MySQL" or something similar.
1730 </p>
1732 <h4>
1733 [1.21] I am running the CGI version of PHP under Unix, and I cannot
1734 login using cookie auth
1735 </h4>
1736 <p>
1737 In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.
1738 </p>
1740 <h4>
1741 [1.22] I don't see the "Location of text file" field, so
1742 I cannot upload
1743 </h4>
1744 <p>
1745 This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
1746 parameter is not set to "on".
1747 </p>
1749 <h4>
1750 [1.23] I'm running MySQL on a Win32 machine. Each time I create a new
1751 table the table and field names are changed to lowercase!</h4>
1752 <p>
1753 This happens because the MySQL directive <tt>lower_case_table_names</tt>
1754 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
1755 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
1756 Just edit you <tt>my.ini</tt> file that should be located in your Windows
1757 directory and add the following line:<br />
1758 <tt>set-variable = lower-case-table-names=0</tt><br />
1759 Next, save the file and restart the MySQL service. You can always check the
1760 value of this directive using the query<br />
1761 <tt>SHOW VARIABLES LIKE 'lower_case_table_names';</tt>
1762 </p>
1764 <h4>
1765 [1.24] Some characters are being truncated in my queries, or I get
1766 characters randomly added. I am running PHP 4.2.3
1767 </h4>
1768 <p>
1769 This is a
1771 </p>
1773 <h4>
1774 [1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
1775 and I get problems, such as undefined variables when I run a SQL query
1776 </h4>
1777 <p>
1778 A tip from Jose Fandos: put a comment on the following two lines
1779 in httpd.conf, like this:<br />
1780 <tt># mod_gzip_item_include file \.php$</tt><br />
1782 as this version of mod_gzip on Apache (Windows) has problems handling
1783 php scripts. Of course you have to restart Apache.
1784 </p>
1786 <h4>
1787 [1.26] I just installed phpMyAdmin in my document root of IIS but
1788 I get the error "No input file specified" when trying to
1789 run phpMyAdmin.
1790 </h4>
1791 <p>
1792 This is a permission problem. Right-click on the phpmyadmin folder
1793 and choose properties. Under the tab Security, click on "Add"
1794 and select the user "IUSER_machine" from the list. Now set his
1795 permissions and it should work.
1796 </p>
1798 <h4>
1799 [1.27] I get empty page when I want to view huge page (eg.
1800 db_details_structure.php3 with plenty of dabases)
1801 </h4>
1802 <p>
1804 GZIP output buffering enabled. If you turn off it (by <code>$cfg['OBGzip']
1805 = FALSE</code> in config.inc.php3), it should work. This bug will be fixed
1806 in PHP 5.0.0.
1807 </p>
1810 <h3>[2. Configuration]</h3>
1812 <h4>
1813 [2.1] The error message "Warning: Cannot add header information -
1814 headers already sent by ..." is displayed, what's the problem
1815 </h4>
1816 <p>
1817 Edit your <i>config.inc.php or .php3</i> file and ensure there is nothing
1818 (ie no blank lines, no spaces, no characters...) neither before the
1819 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
1820 tag at the end.
1821 </p>
1823 <h4>
1824 [2.2] phpMyAdmin can't connect to MySQL. What's wrong
1825 </h4>
1826 <p>
1827 Either there is an error with your PHP setup or your username/password is
1828 wrong. Try to make a small script which uses mysql_connect and see if it
1829 works. If it doesn't, it may be you haven't even compiled MySQL support
1830 into PHP.
1831 </p>
1833 <h4>
1834 [2.3] The error message "Warning: MySQL Connection Failed: Can't
1835 connect to local MySQL server through socket '/tmp/mysql.sock'
1836 (111)..." is displayed. What can I do
1837 </h4>
1838 <p><br />
1839 For RedHat users, Harald Legner suggests this on the mailing list:
1840 <br /><br />
1841 On my RedHat-Box the socket of mysql is <i>/var/lib/mysql/mysql.sock</i>.
1842 In your php.ini you will find a line
1843 <br />
1844 <tt>mysql.default_socket = /tmp/mysql.sock</tt>
1845 <br />
1846 change it to
1847 <br />
1848 <tt>mysql.default_socket = /var/lib/mysql/mysql.sock</tt>
1849 <br />
1850 Then restart apache and it will work.
1851 <br /><br />
1852 Here is a fix suggested by Brad Ummer in the phpwizard forum:
1853 </p>
1854 <ul>
1855 <li>
1856 First, you need to determine what socket is being used by MySQL.
1857 <br />
1858 To do this, telnet to your server and go to the MySQL bin directory. In
1859 this directory there should be a file named <i>mysqladmin</i>. Type
1860 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
1861 info about your MySQL server, including the socket
1862 (<i>/tmp/mysql.sock</i>, for example).
1863 </li>
1864 <li>
1865 Then, you need to tell PHP to use this socket.<br />Assuming you are
1866 using PHP 3.0.10 or better, you can specify the socket to use when you
1867 open the connection. To do this in phpMyAdmin, you need to complete the
1868 socket information in the config.inc.php3.<br />
1869 For example:
1870 <tt>$cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</tt>
1871 </li>
1872 </ul>
1873 <p>
1874 Have also a look at the
1876 corresponding section of the MySQL documentation</a>.
1877 </p>
1879 <h4>
1880 [2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
1881 what can I do
1882 </h4>
1883 <p>
1884 Try to set the <tt>$cfg['OBGZip']</tt> directive to <tt>FALSE</tt> in the
1885 phpMyAdmin configuration file. It helps sometime.<br />
1886 Also have a look at your php version number: if it contains
1887 "4.0b..." it means you're running a beta version of PHP. That's
1888 not a so good idea, please upgrade to a plain revision.
1889 </p>
1891 <h4>
1892 [2.5] Each time I want to insert or change a record or drop a database
1893 or a table, an error 404 (page not found) is displayed or, with http or
1894 cookie authentication, I'm asked to login again. What's wrong
1895 </h4>
1896 <p>
1897 Check the value you set for the <tt>$cfg['PmaAbsoluteUri']</tt> directive
1898 in the phpMyAdmin configuration file.
1899 </p>
1903 <h3>[3. Known limitations]</h3>
1905 <h4>
1906 [3.1] When using http authentication, an user who logged out can not
1907 relog in with the same nick
1908 </h4>
1909 <p>
1910 This is related to the authentication mechanism (protocol) used by
1911 phpMyAdmin. We plan to change it as soon as we may find enough free time
1912 to do it, but you can bypass this problem: just close all the opened
1913 browser windows and then go back to phpMyAdmin. You should be able to
1914 logs in again.
1915 </p>
1917 <h4>
1918 [3.2] When dumping a large table in compressed mode, I get a memory
1919 limit error or a time limit error
1920 </h4>
1921 <p>
1922 As of version 2.2.4, we build the compressed dump in memory, so large
1923 tables dumps may hang. The only alternative we can think about (using
1924 system calls to mysqldump then gzip or bzip2) would not be applicable in
1925 environments where PHP is in safe mode: access to system programs is
1926 is limited by the system administrator, and time limit is enforced.
1927 </p>
1929 <h4>
1930 [3.3] With InnoDB tables, I lose foreign key relationships when I rename
1931 or alter a table
1932 </h4>
1933 <p>
1934 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in
1935 mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
1936 </p>
1938 <h4>
1939 [3.4] I am unable to import dumps I created with the mysqldump tool
1940 bundled with the MySQL server distribution
1941 </h4>
1942 <p>
1943 The problem is that mysqldump creates invalid comments like this:
1944 </p>
1945 <pre>
1946 -- MySQL dump 8.22
1947 --
1948 -- Host: localhost Database: database
1949 ---------------------------------------------------------
1950 -- Server version 3.23.54
1951 </pre>
1952 <p>
1953 The invalid part of the code is the horizontal line made of dashes that
1954 appears once in every dump created with mysqldump. If you want to run your
1955 dump you have to turn it into valid MySQL. This means, you have to add a
1956 whitespace after the first to dashes of the line or add a # before it:
1957 <br />
1958 <code>
1959 -- -------------------------------------------------------<br />
1960 </code>
1961 or<br />
1962 <code>
1963 #---------------------------------------------------------
1964 </code>
1965 </p>
1969 <h3>[4. ISPs, multi-user installations ]</h3>
1971 <h4>
1972 [4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
1973 need to install it for each customer
1974 </h4>
1975 <p>
1976 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
1977 your users. The development of this feature was kindly sponsored by
1978 NetCologne GmbH.
1979 This requires a properly setup MySQL user management and phpMyAdmin
1980 http or cookie authentication. See the install section on
1981 "Using http authentication".
1982 </p>
1984 <h4>
1985 [4.2] What's the preferred way of making phpMyAdmin secure against evil
1986 access
1987 </h4>
1988 <p>
1989 This depends on your system.<br />
1990 If you're running a server which cannot be accessed by other people, it's
1991 sufficient to use the directory protection bundled with your webserver
1992 (with Apache you can use <i>.htaccess</i> files, for example).<br />
1993 If other people have telnet access to your server, you should use
1994 phpMyAdmin's http authentication feature.
1995 <br /><br />
1996 Suggestions:
1997 </p>
1998 <ul>
1999 <li>
2000 Your <i>config.inc.php3</i> file should be <tt>chmod 660</tt>.
2001 </li>
2002 <li>
2003 All your phpMyAdmin files should be chown phpmy.apache, where phpmy
2004 is a user whose password is only known to you, and apache is the
2005 group under which Apache runs.
2006 </li>
2007 <li>
2008 You should use PHP safe mode, to protect from other users that try
2009 to include your <i>config.inc.php3</i> in their scripts.
2010 </li>
2011 </ul>
2013 <h4>
2014 [4.3] I get errors about not being able to include a file in
2015 <i>/lang</i> or in <i>/libraries</i>
2016 </h4>
2017 <p>
2018 Check <i>php.ini</i>, or ask your sysadmin to check it. The
2019 <tt>include_path</tt> must contain "." somewhere in it, and
2020 <tt>open_basedir</tt>, if used, must contain "." and
2021 "./lang" to allow normal operation of phpMyAdmin.
2022 </p>
2023 <h4>
2024 [4.4] phpMyAdmin always gives "Access denied" when using http
2025 authentication
2026 </h4>
2027 <p>
2028 This could happen for several reasons:
2029 </p>
2030 <ul>
2031 <li>
2032 <tt>$cfg['Servers'][$i]['controluser']</tt> and/or
2033 <tt>$cfg['Servers'][$i]['controlpass']</tt> are wrong.
2034 </li>
2035 <li>
2036 The username/password you specify in the login-dialog are invalid.
2037 </li>
2038 <li>
2039 You have already setup a security mechanism for the
2040 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
2041 phpMyAdmin's authentication, so remove it.
2042 </li>
2043 </ul>
2045 <h4>
2046 [4.5] Is it possible to let users create their own databases
2047 </h4>
2048 <p>
2049 Starting with 2.2.5, in the user management page, you can enter a wildcard
2050 database name for a user, and put the privileges you want. For example,
2051 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
2052 would let a user create/manage his/her database(s).
2053 </p>
2055 <h4>
2056 [4.6] How can I use the Host-based authentication additions
2057 </h4>
2058 <p>
2059 If you have existing rules from an old .htaccess file, you can take them
2060 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
2061 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
2062 be a major benefit here if your installation is suited to using it. Then
2063 you can just add those updated lines into the
2064 <tt>$cfg['Servers'][$i]['AllowDeny']['rules']</tt> array.
2065 <br /><br />
2066 If you want a pre-made sample, you can try this fragment. It stops the
2067 'root' user from logging in from any networks other than the private
2068 network IP blocks.
2069 <br />
2070 <tt>
2071 //block root from logging in except from the private networks<br />
2072 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';<br />
2073 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(<br />
2074 'deny root from all',<br />
2075 'allow root from localhost',<br />
2076 'allow root from 10.0.0.0/8',<br />
2077 'allow root from 192.168.0.0/16',<br />
2078 'allow root from 172.16.0.0/12',<br />
2079 );
2080 </tt>
2081 </p>
2084 <h3>[5. Browsers or client OS]</h3>
2086 <h4>
2087 [5.1] I get an out of memory error, and my controls are non-functional,
2088 when trying to create a table with more than 14 fields
2089 </h4>
2090 <p>
2091 We could reproduce this problem only under Win98/98SE. Testing under
2092 WinNT4 or Win2K, we could easily create more than 60 fields.
2093 <br />
2094 A workaround is to create a smaller number of fields, then come back to
2095 your table properties and add the other fields.
2096 </p>
2098 <h4>
2099 [5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields
2100 </h4>
2101 <p>
2102 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
2103 with each script/website that use forms.<br />
2104 Upgrade or downgrade your Xitami server.
2105 </p>
2107 <h4>
2108 [5.3] I have problems dumping tables with Konqueror
2109 (phpMyAdmin 2.2.2)</h4>
2110 <p>
2111 With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except that
2112 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
2113 don't seem to work.<br />
2115 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
2116 the user's temporary directory, so they must be moved before closing
2117 Konqueror, or else they disappear. Gzip dumps give an error message.<br />
2119 Testing needs to be done for Konqueror 2.2.2.<br />
2120 </p>
2122 <h4>
2123 [5.4] I can't use the cookie authentication mode because Internet
2124 Explorer never stores the cookies
2125 </h4>
2126 <p>
2127 MS Internet Explorer seems to be really buggy about cookies, at least till
2128 version 6. And thanks to Andrew Zivolup we've traced also a php 4.1.1 bug
2129 in this area!
2130 <br />
2131 Then, if you're running php 4.1.1, try to upgrade or downgrade... it may
2132 work!
2133 </p>
2135 <h4>
2136 [5.5] In Internet Explorer 5.0, I get Javascript errors when browsing my
2137 rows
2138 </h4>
2139 <p>
2140 Upgrade to at least Internet Explorer 5.5SP2.<br />
2141 </p>
2143 <h4>
2144 [5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying
2145 to modify a row in a table with many fields, or with a text field
2146 </h4>
2147 <p>
2148 Your table neither have a primary key nor an unique one, so we must use a
2149 long URL to identify this row. There is a limit on the lenght of the URL in
2150 those browsers, and this not happen in Netscape, for example. The
2151 workaround is to create a primary or unique key, or use another browser.
2152 <br />
2153 </p>
2155 <h4>
2156 [5.7] I refresh (reload) my browser, and come back to the welcome
2157 page
2158 </h4>
2159 <p>
2160 Some browsers support right-clicking into the frame you want to refresh,
2161 just do this in the right frame.<br />
2162 </p>
2164 <h4>
2165 [5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
2166 query box
2167 </h4>
2168 <p>
2169 Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future
2170 Mozilla versions.<br />
2171 </p>
2173 <h4>
2174 [5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
2175 whitespace in the SQL-Query edit area: the page scrolls down
2176 </h4>
2177 <p>
2178 This is a Mozilla bug (see bug #26882 at
2180 </p>
2182 <h4>
2183 [5.10] With Netscape 4.75 I get empty rows between each row of data in a
2184 CSV exported file
2185 </h4>
2186 <p>
2187 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
2188 data in octet-stream mode. Since we can't detect the specific Netscape
2189 version, we cannot workaround this bug.
2190 </p>
2192 <h4>
2193 [5.11] Extended-ASCII characters like German umlauts are displayed
2194 wrong
2195 </h4>
2196 <p>
2197 Please ensure that you have set your browser's charset to the one of the
2198 language file you have selected on phpMyAdmin's start page.
2199 Alternatively, you can try the auto detection mode that is supported by the
2200 recent versions of the most browsers.
2201 </p>
2203 <h4>
2204 [5.12] Apple OS X: Safari browser changes special characters to
2205 "?"
2206 </h4>
2207 <p>
2208 This issue has been reported by a OS X user, who adds that Chimera,
2209 Netscape and Mozilla do not have this problem.
2210 </p>
2212 <h4>
2213 [5.13] With Internet Explorer 5.5 or 6, and http authentication type,
2214 I cannot manage two servers: I login to the first one, then the other one,
2215 but if I switch back to the first, I have to login on each operation.
2216 </h4>
2217 <p>
2218 This is a bug in Internet Explorer, other browsers do not behave this way.
2219 </p>
2222 <h3>[6. Using phpMyAdmin]</h3>
2224 <h4>
2225 [6.1] I can't insert new rows into a table / I can't create a table
2226 - MySQL brings up a SQL-error
2227 </h4>
2228 <p>
2229 Examine the SQL error with care. Often the problem is caused by
2230 specifying a wrong field-type.<br />
2231 Common errors include:
2232 </p>
2233 <ul>
2234 <li>Using <tt>VARCHAR</tt> without a size argument</li>
2235 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
2236 </ul>
2237 <p>
2238 Also, look at the syntax chapter in the MySQL manual to confirm that your
2239 syntax is correct.
2240 </p>
2242 <h4>
2243 [6.2] When I create a table, I click the Index checkbox for 2 fields and
2244 phpMyAdmin generates only one index with those 2 fields
2245 </h4>
2246 <p>
2247 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
2248 index. If you want two indexes, create the first one when creating the
2249 table, save, then display the table properties and click the Index link to
2250 create the other index.
2251 </p>
2253 <h4>
2254 [6.3] How can I insert a null value into my table
2255 </h4>
2256 <p>
2257 Since version 2.2.3, you have a checkbox for each field that can be null.
2258 Before 2.2.3, you had to enter "null", without the quotes, as the
2259 field's value.
2260 </p>
2262 <h4>
2263 [6.4] How can I backup my database or table
2264 </h4>
2265 <p>
2266 Click on a database or table name in the left frame, the properties will be
2267 displayed. Then on the menu, click "Export", you can dump
2268 the structure, the data, or both. This will generate standard SQL
2269 statements that can be used to recreate your database/table.
2270 <br /><br />
2271 You will need to choose "Save as file", so that phpMyAdmin can
2272 transmit the resulting dump to your station. Depending on your PHP
2273 configuration, you will see options to compress the dump. See also the
2274 <tt>$cfg['ExecTimeLimit']</tt> configuration variable.
2275 <br /><br />
2276 For additional help on this subject, look for the word "dump" in
2277 this document.
2278 </p>
2280 <h4>
2281 [6.5] How can I restore (upload) my database or table using a dump?
2282 How can I run a ".sql" file
2283 </h4>
2284 <p>
2285 Click on a database name in the left frame, the properties will be
2286 local displayed. Then in the "Run SQL query" section, type in
2287 your dump filename, or use the Browse button. Then click Go.
2288 <br /><br />
2289 For additional help on this subject, look for the word "upload"
2290 in this document.
2291 </p>
2293 <h4>
2294 [6.6] How can I use the relation table in Query-by-example
2295 </h4>
2296 <p>
2297 Here is an example with the tables persons, towns and countries, all
2298 located in the database mydb. If you don't have a <tt>PMA_relation</tt>
2299 table, create it as explained in the configuration section. Then create the
2300 example tables:
2301 <br /><br />
2302 <tt>
2303 CREATE TABLE REL_countries (<br />
2304 country_code char(1) NOT NULL default '',<br />
2305 description varchar(10) NOT NULL default '',<br />
2306 PRIMARY KEY (country_code)<br />
2307 ) TYPE=MyISAM;<br />
2308 <br />
2309 INSERT INTO REL_countries VALUES ('C', 'Canada');<br />
2310 <br />
2311 CREATE TABLE REL_persons (<br />
2312 id tinyint(4) NOT NULL auto_increment,<br />
2313 person_name varchar(32) NOT NULL default '',<br />
2314 town_code varchar(5) default '0',<br />
2315 country_code char(1) NOT NULL default '',<br />
2316 PRIMARY KEY (id)<br />
2317 ) TYPE=MyISAM;<br />
2318 <br />
2319 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');<br />
2320 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');<br />
2321 <br />
2322 CREATE TABLE REL_towns (<br />
2323 town_code varchar(5) NOT NULL default '0',<br />
2324 description varchar(30) NOT NULL default '',<br />
2325 PRIMARY KEY (town_code)<br />
2326 ) TYPE=MyISAM;<br />
2327 <br />
2328 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');<br />
2329 INSERT INTO REL_towns VALUES ('M', 'Montréal');<br />
2330 <br />
2331 </tt>
2332 To setup appropriate links and display information:
2333 </p>
2334 <ul>
2335 <li>on table "REL_persons" click Structure, then Relation view</li>
2336 <li>in Links, for "town_code" choose "REL_towns->code"</li>
2337 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
2338 <li>on table "REL_towns" click Structure, then Relation view</li>
2339 <li>in "Choose field to display", choose "description"</li>
2340 <li>repeat the two previous steps for table "REL_countries"</li>
2341 </ul>
2343 <p>
2344 Then test like this:
2345 </p>
2346 <ul>
2347 <li>Click on your db name in the left frame</li>
2348 <li>Choose "Query"</li>
2349 <li>Use tables: persons, towns, countries</li>
2350 <li>Click "Update query"</li>
2351 <li>In the fields row, choose persons.person_name and click the
2352 "Show" tickbox </li>
2353 <li>Do the same for towns.description and countries.descriptions in the
2354 other 2 columns</li>
2355 <li>Click "Update query" and you will see in the query box that
2356 the correct joins have been generated</li>
2357 <li>Click "Submit query"</li>
2358 </ul>
2359 <br />
2362 <h4>
2363 [6.7] How can I use the "display field" feature
2364 </h4>
2365 <p>
2366 Starting from the previous example, create the PMA_table_info as explained
2367 in the configuration section, then browse your persons table,
2368 and move the mouse over a town code or country code.
2369 </p>
2372 <h4>
2373 [6.8] How can I produce a PDF schema of my database
2374 </h4>
2375 <p>
2376 First you have to fill the "relation", "table_coords"
2377 and "pdf_pages" configuration variables.
2378 <br /><br />
2379 Then, think about your schema layout: which tables will go on which pages.
2380 </p>
2381 <ul>
2382 <li>Click on your db name in the left frame</li>
2383 <li>Choose "Structure" in the navigation on top</li>
2384 <li>Choose "Edit PDF Pages" which should be somewhere at the
2385 bottom of the page</li>
2386 <li>Enter the name for a first pdf page and submit</li>
2387 <li>Choose this page to edit</li>
2388 <li>Now add a table you want to show on this page and it's coordinates and
2389 submit<br />
2390 First you will have to guess this coordinates of course, so just expect
2391 to have an area of about 297 * 210 and put the tables coordinates
2392 somewhere in there, you will be able to have a look at what happened
2393 and change them later.<br />
2394 For example, x=100 and y=200 means that the table will be at 200 mm
2395 down and 100 mm right from the upper left corner.<br />
2396 Actually if you have a width of more than 300 or a height of more than
2397 200 than it will automatically be scaled but 300*100 is a good start to
2398 have an idea of what coordinates to use.</li>
2399 <li>After every table you submitted you will have the possibility to submit
2400 more tables</li>
2401 <li>When you have entered enough tables Click on your db name in the left
2402 frame again</li>
2403 <li>Now, again at the bottom of the page you should be able to choose
2404 "Display PDF schema"<br />
2405 For testing it might be useful to show the grid as well, so you can see
2406 the coordinates used.<br />
2407 Maybe also choose color and submit.</li>
2408 <li>Save the file he will offer you to something like <i>Schema.pdf</i>
2409 (Internet Explorer has some bug there which might make it offer it
2410 without an extension. Under Windows it is important to have the
2411 extension ".pdf", under other OSes you should be fine just
2412 saving the file under the name it offers).</li>
2413 </ul>
2415 <h4>
2416 [6.9] phpMyAdmin is changing the type of one of my columns!</h4>
2417 <p>
2418 No, it's MySQL that is doing
2419 <a href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent column type changing</a>.
2420 </p>
2423 <h4>
2424 [6.10] My database has an underscore in it's name, and when I grant
2425 privileges to a user for this database, a backslash is added before the
2426 underscore
2427 </h4>
2428 <p>
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>
2438 <h4>
2439 [6.11] What is the curious symbol ø in the table statistics
2440 </h4>
2441 <p>
2442 It means "average".
2443 </p>
2446 <h4>
2447 [6.12] I want to understand some Export options
2448 </h4>
2449 <p>
2450 "Complete inserts" adds the column names on every INSERT command,
2451 for better documentation (but resulting file is bigger).<br />
2452 "Extended inserts" provides a shorter dump file by using only
2453 once the INSERT verb and the table name.<br />
2454 "Enclose table and field names with backquotes" ensures that
2455 field and table names formed with special characters are protected.<br />
2456 </p>
2458 <h4>
2459 [6.13] I would like to create a database with a dot in its name
2460 </h4>
2461 <p>
2462 This is a bad idea, because in MySQL the syntax "database.table"
2463 is the normal way to reference a database and table name. Worse, MySQL
2464 will usually let you create a database with a dot, but then you cannot
2465 work with it, nor delete it.<br />
2466 </p>
2469 <h4>
2470 [6.14] How do I set up the SQL validator
2471 </h4>
2472 <p>
2473 To use it, you need a very recent version of PHP, 4.3.0 recommended, with
2474 XML, PCRE and PEAR support. On your system command line, run
2475 <tt>"pear install Net_Socket Net_URL HTTP_Request Mail_Mime Net_DIME
2476 SOAP"</tt> to get the nessecary PEAR modules for usage.
2477 <br />
2478 If you use it, you should be aware that any SQL statement you
2479 submit will be stored anonymously (database/table/column names,
2480 strings, numbers replaced with generic values). The Mimer SQL
2481 Validator itself, is © 2001 Upright Database Technology.
2482 We utilize it as free SOAP service.
2483 </p>
2485 <h4>
2486 [6.15] I want to add a BLOB field and put an index on it, but MySQL
2487 says "BLOB column '...' used in key specification without a key
2488 length"
2489 </h4>
2490 <p>
2491 The right way to do this, is to create the field without any indexes,
2492 then display the table structure and use the "Create an index"
2493 dialog. On this page, you will be able to choose your BLOB field, and
2494 set a size to the index, which is the condition to create an index on
2495 a BLOB field.
2496 <br />
2497 </p>
2499 <h4>
2500 [6.16] How can I simply move in page with plenty editing fields
2501 </h4>
2502 <p>
2503 You can use Ctrl+arrows for moving on most pages with plenty editing
2504 fields (table structure changes, row editing, etc.).
2505 <br />
2506 </p>
2509 <h4>
2510 [6.17] Why is there checkbox called "Binary" when uplaoding file
2511 into database?
2512 </h4>
2513 <p>
2514 It defines how data will be inserted into MySQL. When not checked, the
2515 data from file will be treated as text, if charset conversion is enabled
2516 (you are using utf-8 translation) charset of the text will be converted
2517 according to it and could possibly be displayed as part of update SQL
2518 after upload. When checked data will be inserted as hexadecimal value and
2519 so will be in database exactly as in file. In most cases you should keep
2520 it checked.
2521 <br />
2522 </p>
2525 <h3>[7. phpMyAdmin project]</h3>
2527 <h4>
2528 [7.1] I have found a bug. How do I inform developers?
2529 </h4>
2530 <p>
2531 Our Bug Tracker is located at
2532 <a href="http://sourceforge.net/projects/phpmyadmin/">http://sourceforge.net/projects/phpmyadmin/</a>
2533 under the Bugs section.
2534 <br /><br />
2535 But please first discuss your bug with other users:
2536 <br />
2538 http://sourceforge.net/projects/phpmyadmin/</a> (and choose Forums)
2539 </p>
2541 <h4>
2542 [7.2] I want to translate the messages to a new language or upgrade an
2543 existing language, where do I start?
2544 </h4>
2545 <p>
2546 Always use the current cvs version of your language file.
2547 For a new language, start from <i>english-iso-8859-1.inc.php3</i>. If you
2548 don't know how to get the cvs version, please ask one of the developers.
2549 <br />
2550 Please note that we try not to use html entities like &eacute; in
2551 the translations, since we define the right character set in the file.
2552 With html entities, the text on javascript messages would not
2553 display correctly.
2554 However there are some entities that need to be there, for quotes
2555 ,non-breakable spaces, ampersands, less than, greater than.
2556 <br />
2557 You can then put your translations, as a zip file to avoid losing special
2558 characters, on the sourceforge.net translation tracker.
2559 <br />
2560 It would be a good idea to subscribe to the phpmyadmin-translators mailing
2561 list, because this is where we ask for translations of new messages.
2562 <br />
2563 </p>
2565 <h4>
2566 [7.3] I would like to help out with the development of phpMyAdmin. How
2567 should I proceed?
2568 </h4>
2569 <p>
2570 The following method is preferred for new developers:
2571 </p>
2572 <ol>
2573 <li>
2574 fetch the current CVS tree over anonymous CVS:<br />
2575 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
2576 [Password: simply press the Enter key]<br />
2577 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
2578 [This will create a new sub-directory named phpMyAdmin]
2579 </li>
2580 <li>
2581 add your stuff
2582 </li>
2583 <li>
2584 put the modified files (tar'ed and gzip'ed) inside the patch tracker of
2585 the
2586 <a href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">phpMyAdmin SourceForge account</a>.
2587 </li>
2588 </ol>
2589 <p>
2590 Write access to the CVS tree is granted only to experienced developers who
2591 have already contributed something useful to phpMyAdmin.<br />
2592 Also, have a look at the
2594 </p>
2598 <!-- DEVELOPERS -->
2600 <h2>Developers Information</h2>
2602 <p>
2603 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
2604 great features have been written by other people and you too can help to
2605 make phpMyAdmin a useful tool.
2606 </p>
2608 <p>
2609 If you're planning to contribute source, please read the following
2610 information:
2611 </p>
2612 <ul>
2613 <li>
2614 All files include <i>header.inc.php3</i> (layout),
2615 <i>libraries/common.lib.php3</i> (common functions) and
2616 <i>config.inc.php3</i>.
2617 <br />
2618 All configuration data belongs in <i>config.inc.php3</i>. Please keep
2619 it free from other code.
2620 <br />
2621 Commonly used functions should be added to
2622 <i>libraries/common.lib.php3</i> and more specific ones may be added
2623 within a library stored into the <i>libraries</i> sub-directory.
2624 </li>
2625 <li>
2626 Obviously, you're free to use whatever coding style you want. But
2627 please try to keep your code as simple as possible: beginners are
2628 using phpMyAdmin as an example application.<br />
2629 As far as possible, we want the scripts to be XHTML1.0 and CSS2
2630 compliant on one hand, they fit the
2632 on the other hand. Please pay attention to this.
2633 </li>
2634 <li>
2635 Please try to keep up the file-naming conventions. Table-related stuff
2636 goes to <i>tbl_*.php3</i>, db-related code to <i>db_*.php3</i>,
2637 server-related tools to <i>server_*.php3</i> and so on.
2638 </li>
2639 <li>
2640 Please don't use verbose strings in your code, instead add the string
2641 (at least) to <i>english-iso-8859-1.inc.php3</i> and print() it out.
2642 </li>
2643 <li>
2644 If you want to be really helpful, write an entry for the ChangeLog.
2645 </li>
2648 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
2649 better debug and profile their code.<br />
2650 Please see the <tt>$cfg['DBG']*</tt> configuration options for more
2651 information.<br />
2652 This is in memorium of the Space Shuttle Columbia (STS-107) which was
2653 lost during its re-entry into Earth's atmosphere and in memory of the
2654 brave men and women who gave their lives for the people of Earth.
2655 </li>
2657 </ul>
2659 <!-- CREDITS -->
2661 <h2>Credits</h2>
2663 <pre>
2665 phpMyAdmin - Credits
2666 ====================
2668 CREDITS, in chronological order
2669 -------------------------------
2671 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
2672 * creator of the phpmyadmin project
2673 * maintainer from 1998 to summer 2000
2675 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
2676 * multi-language version
2677 * various fixes and improvements
2678 * project co-administrator
2680 - Olivier Müller <om_at_omnis.ch>
2681 * started SourceForge phpMyAdmin project in March 2001
2682 * sync'ed different existing CVS trees with new features and bugfixes
2683 * multi-language improvements, dynamic language selection
2684 * current project maintainer
2685 * many bugfixes and improvements
2687 - Loïc Chapeaux <lolo_at_phpheaven.net>
2688 * rewrote and optimized javascript, DHTML and DOM stuff
2689 * rewrote the scripts so they fit the PEAR coding standards and
2690 generate XHTML1.0 and CSS2 compliant codes
2691 * improved the language detection system
2692 * many bugfixes and improvements
2694 - Robin Johnson <robbat2_at_users.sourceforge.net>
2695 * database maintence controls
2696 * table type code
2697 * Host authentication IP Allow/Deny
2698 * DB-based configuration (Not completed)
2699 * SQL parser
2700 * SQL validator
2701 * many bugfixes and improvements
2703 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
2704 * bookmarks feature
2705 * multiple dump feature
2706 * gzip dump feature
2707 * zip dump feature
2709 - Geert Lund <glund_at_silversoft.dk>
2710 * various fixes
2711 * moderator of the phpMyAdmin users forum at phpwizard.net
2713 - Korakot Chaovavanich <korakot_at_iname.com>
2714 * "insert as new row" feature
2716 - Pete Kelly <webmaster_at_trafficg.com>
2717 * rewrote and fix dump code
2718 * bugfixes
2720 - Steve Alberty <alberty_at_neptunlabs.de>
2721 * rewrote dump code for PHP4
2722 * mySQL table statistics
2723 * bugfixes
2725 - Benjamin Gandon <gandon_at_isia.cma.fr>
2726 * main author of the version 2.1.0.1
2727 * bugfixes
2729 - Alexander M. Turek <rabus_at_bugfixes.info>
2730 * XML exports
2731 * MySQL 4 related features
2732 * various small features and fixes
2733 * German language file updates
2735 - Mike Beck <mike.beck_at_ibmiller.de>
2736 * automatic joins in QBE
2737 * links column in printview
2738 * Relation view
2740 - Michal Cihar <nijel_at_users.sourceforge.net>
2741 * enhanced index creation/display feature
2742 * feature to use a different charset for HTML than for MySQL
2743 * Czech language file updates
2745 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
2746 (http://sourceforge.net/projects/phpmysqlformgen/)
2747 * suggested the patch for multiple table printviews
2749 - Garvin Hicking <hicking_at_faktor-e.de>
2750 * built the patch for vertical display of table rows
2752 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
2753 * japanese kanji encoding conversion feature
2755 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
2756 * the Cookie authentication mode
2758 - Axel Sander <n8falke_at_users.sourceforge.net>
2759 * table relation-links feature
2761 - Maxime Delorme <delorme.maxime_at_free.fr>
2762 * PDF schema output, thanks also to Olivier Plathey for the
2763 "FPDF" library (see http://www.fpdf.org/).
2765 - Olof Edlund <olof.edlund_at_upright.se>
2766 * SQL validator server
2768 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
2769 * phpMyAdmin logo
2771 And also to the following people who have contributed minor changes,
2772 enhancements, bugfixes or support for a new language since version 2.1.0:
2774 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
2775 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
2776 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
2777 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
2778 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
2779 www.securereality.com.au, Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky,
2780 Rachim Tamsjadi, Kositer Uros, Luís V., Martijn W. van der Lee,
2781 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
2782 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas.
2785 Original Credits of Version 2.1.0
2786 ---------------------------------
2788 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
2789 to create a web-based interface to MySQL using PHP3. Although I have not
2790 used any of his source-code, there are some concepts I've borrowed from
2791 him. phpMyAdmin was created because Peter told me he wasn't going to
2792 further develop his (great) tool.
2793 Thanks go to
2794 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
2795 code for the check when dropping a table or database. He also suggested
2796 that you should be able to specify the primary key on tbl_create.php3. To
2797 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
2798 well as a bug-report. Plus many smaller improvements.
2799 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
2800 were introduced in 1.3.0 (including quite significant ones like the
2801 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
2802 bug-fixes and help.
2803 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
2804 language-independent by outsourcing the strings to a separate file. He
2805 also contributed the French translation.
2806 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
2807 tbl_select.php3, a feature to display only some fields from a table.
2808 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
2809 functions in tbl_change.php3. He also added the
2810 "Query by Example" feature in 2.0.
2811 - Dave Walton <walton_at_nordicdms.com> added support for multiple
2812 servers and is a regular contributor for bug-fixes.
2813 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
2814 features for 2.0.6.
2815 The following people have contributed minor changes, enhancements, bugfixes
2816 or support for a new language:
2817 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
2818 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
2819 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
2820 G. Wieggers.
2822 And thanks to everyone else who sent me email with suggestions, bug-reports
2823 and or just some feedback.
2824 </pre>
2831 <img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" border="0" height="31" width="88" /></a>
2832
2834 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" border="0" width="88" height="31" /></a>
2835 </p>
2837 </body>
2838 </html>