| blob | ac68d65ce3e5f93051bc6f962eb840fc2f60e628 |
4 <!-- $Id$ -->
5 <!--
6 vim: expandtab ts=4 sw=4 sts=4 tw=78
7 -->
9 <head>
13 </head>
15 <body>
25 <br />
32 </div>
37 <!-- TOP MENU -->
38 <ul>
39 <li>
41 SourceForge phpMyAdmin project page [ http://www.phpmyadmin.net/ ]
42 </a>
43 </li>
44 <li>
45 Local documents:
46 <ul>
50 </ul>
51 </li>
52 <li>
53 Documentation version:
55 </li>
56 </ul>
59 <!-- REQUIREMENTS -->
63 <ul>
64 <li>
65 PHP3 or PHP4: phpMyAdmin widely uses the 'str_replace()' PHP function
72 If you want to display inline thumbnails of JPEGs, you also need
73 GD2 support in PHP.
74 </li>
75 <li>
78 syntax of string field types, this version of phpMyAdmin probably won't
80 </li>
81 <li>
82 a web-browser (doh!).
83 </li>
84 </ul>
87 <!-- INTRODUCTION -->
91 <p>
92 phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
93 a single database. To accomplish the latter you'll need a properly set up
94 MySQL user who can read/write only the desired database. It's up to you to
95 look up the appropriate part in the MySQL manual.<br />
96 Currently phpMyAdmin can:
97 </p>
99 <ul>
112 <li>using Query-by-example (QBE), create complex queries automatically connecting required tables</li>
115 <li>transform stored data into any format using a set of predefined functions,
116 like displaying BLOB-data as image or download-link or ...</li>
117 <li>
118 communicate in
120 </li>
121 </ul>
124 (*)
125 phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dumps
128 </p>
131 <!-- INSTALLATION -->
135 <p>
137 methods to the MySQL database server. It is still the system administrator's job to
138 grant permissions on the MySQL databases properly. </span>phpMyAdmin's
140 </p>
142 <p>
144 version before OS X, StuffIt unstuffs with Mac formats.<br />
145 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
146 before uploading them to your server, as PHP seems not to like Mac-style
148 </p>
150 <p>
153 if you are using a kit with files having this extension.
154 </p>
157 <ol>
158 <li> Choose and download a distribution kit with the files having the
160 web/PHP server interprets those extensions.</li>
161 <li> Untar or unzip the distribution (be sure to unzip the subdirectories):
163 document root. If you don't have direct access to your document root,
164 put the files in a directory on your local machine, and, after step 3,
165 transfer the directory on your web server using, for example, ftp.</li>
166 <li> Open the file config.inc.php3 in your favorite editor and change
167 the values for host, user, password and authentication mode to fit
170 Have a look at
172 explanation of all values.</li>
173 <li> It is recommended that you protect the directory in which you
174 installed phpMyAdmin (unless it's on a closed intranet, or you wish to
175 use HTTP or cookie authentication), for example with HTTP-AUTH (in a
178 information.</li>
179 <li> Open the file
181 in your browser. phpMyAdmin should now display a welcome screen
182 and your databases, or a login dialog if using HTTP or cookie
183 authentication mode.</li>
184 <li> For a whole set of new features (bookmarks, comments, SQL-history, PDP-generation)
185 you need to create a set of tables in your database. Please look at your scripts/
187 You can already use your phpMyAdmin to create the tables for you. Please be
188 aware that you may have to have special (administrator) privileges to create
190 you should specify the table names in your config.inc.php3 file. The directives
193 </ol>
196 <ul>
197 <li>Please do not copy your older config.inc.php3 over the new one: it may
198 offer new configuration variables, and the new version may depend on
199 these for normal behavior. It is suggested instead to insert your site
200 values in the new one.</li>
201 </ul>
204 <ul>
206 environment</b> where you want to give users access to their own
207 database and don't want them to play around with others.
208 <br />
209 Nevertheless be aware that MS Internet Explorer seems to be really
211 bit buggy in this area!<br />
213 HTTP or cookie mode so that your user/password pair are not in clear
214 in the configuration file.<br /><br /></li>
216 <li>HTTP and cookie authentication modes are more secure: the MySQL
217 password does not need to be set in the phpMyAdmin configuration file
220 <br />
221 However, keep in mind that the password travels in plain text, unless
222 you are using the HTTPS protocol.
223 <br />
224 In cookie mode, we send the password in a temporary cookie, so most
225 browsers should not store the password in their cookie file.
226 <br /><br /></li>
228 <li>
229 For 'HTTP' and 'cookie' modes, phpMyAdmin needs a controluser that has
234 You must specify the details for the controluser in the
240 only an example: use something else in your file!</b><br />
242 if it's not the same as the MySQL server's one.
243 <pre>
245 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
246 GRANT SELECT (
247 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
248 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
249 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
250 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
251 Execute_priv, Repl_slave_priv, Repl_client_priv
252 ) ON mysql.user TO 'pma'@'localhost';
253 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
254 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
255 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
256 ON mysql.tables_priv TO 'pma'@'localhost';
257 </pre>
258 If you are using an old MySQL version (below 4.0.2), please use this
259 query instead of the second one:
260 <pre>
262 GRANT SELECT (
263 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
264 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
265 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
266 ) ON mysql.user TO 'pma'@'localhost';
267 </pre>
268 ... and if you want to use the many new relation and bookmark
269 features:
270 <pre>
273 </pre>
274 (this of course requires you to have a special DB for phpMyAdmin, the
275 contents will be explained later)<br />
276 Of course, the above queries only work if your MySQL version supports
277 the GRANT command. This is the case since 3.22.11.
278 </li>
279 <li>
281 privileges on a set of particular databases. Normally you shouldn't
282 give global privileges to an ordinary user, unless you understand
283 the impact of those privileges (for example, you are creating
284 a superuser).<br />
287 <tt>GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';</tt>
288 <br />
289 What the user may now do is controlled entirely by the MySQL user
290 management system.<br />
291 With HTTP or cookie authentication mode, you don't need to fill the user/password
293 </li>
294 </ul>
297 <ul>
300 allows you to login as any valid MySQL user.</li>
301 <li>Is only supported with PHP running as an Apache module, not with
302 CGI.</li>
303 </ul>
306 <ul>
307 <li>You can use this method as a replacement for the HTTP
308 authentication (for example, if you're running IIS).
309 </li>
311 <li>With this mode, the use can truly logout of phpMyAdmin and login back
312 with the same username.</li>
313 </ul>
316 <ul>
317 <li>This mode is the less secure one because it requires you to fill the
322 <li>In the ISP FAQ section, there is an entry explaining how to protect
323 your configuration file.<br /></li>
324 <li>For additional security in this mode, you may wish to consider the
327 directives.</li>
328 </ul>
331 <!-- CONFIGURATION -->
335 <p>
338 the option that allows to use the *nix end of line character
340 you have modified.
341 </p>
344 <dl>
346 <dd>
347 Sets here the complete URL (with full path) to your phpMyAdmin version.
349 <br /><br />
350 phpMyAdmin needs this setting, because of requirements of the HTTP
351 protocol, explained in RFC2616, section 14.30.
352 <br /><br />
353 Don't forget the slash at the end of your URL. The URL must contain
354 characters that are valid for a URL, and on some servers, the path
355 is case-sensitive.
356 <br /><br />
357 Starting with version 2.3.0, you can try to leave this parameter
358 empty, because the program tries to auto-detect its proper value.
359 Additional details are in the configuration file.
360 <br /><br />
361 Alternatively, this setting can be dynamically completed. For example,
362 you can try to use such a kind of code:
363 <pre>
364 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
365 . $_SERVER['HTTP_HOST']
366 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
369 or
371 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
372 . $_SERVER['SERVER_NAME']
373 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
375 </pre>
379 <br /><br />
380 </dd>
382 <dd>
383 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and the system
384 detects your absolute URI automatically, we display a warning to remind
385 you. If you have tested the automatic detection, and it works perfectly
386 for your setup, then you can set this variable to squelch the warning.
387 <br /><br />
388 </dd>
391 <dd>
392 Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
393 with master / foreign - tables (see
395 <br />
396 If you tried to set this up and it does not work for you, have a look on
398 use it. You will find a link that will analyze why those features have
399 been disabled.<br />
400 If you do not want to use those features set this variable to
402 <br /><br />
403 </dd>
406 <dd>
407 Since version 1.4.2, phpMyAdmin supports the administration of multiple
408 MySQL servers.
409 Therefore, a $cfg['Servers']-array has been added which contains
410 the login information for the different servers. The first
413 the second server, etc.
414 If you have only one server to administer, simply leave free the
415 hostname of the other $cfg['Server']-entries.
416 <br /><br />
417 </dd>
420 <dd>
421 The hostname of your $i-th MySQL-server. E.g. localhost.
422 <br /><br />
423 </dd>
426 <dd>
427 The port-number of your $i-th MySQL-server. Default is 3306 (leave
429 ignores this port number and connects with the socket, so if you want
430 to connect to a port different from the default port, use
432 $cfg['Servers'][$i]['host'].
433 <br /><br />
434 </dd>
437 <dd>
438 The path to the socket to use. Leave blank for default.<br />
439 To use the socket feature you must run PHP 3.0.10 or more.
440 <br /><br />
441 </dd>
444 <dd>
445 What type connection to use with the MySQL server. Your options are
447 is nearly guaranteed to be available on all MySQL servers, while
448 sockets are not supported on some platforms.
449 <br /><br />
450 To use the socket mode, your MySQL server must be on the same machine
451 as the Web server.
452 <br /><br />
453 </dd>
456 <dd>
457 Whether to use a compressed protocol for the MySQL server connection
458 or not (experimental).<br />
460 </dd>
462 <dt>
465 </dt>
466 <dd>
467 When using HTTP or cookie authentication modes (or 'config'
468 authentication mode since phpMyAdmin 2.2.1), you need to supply the
473 This account is used to check what databases the user will see at
474 login.<br />
477 <br /><br />
478 Note that if you try login to phpMyAdmin with this
482 <br /><br />
483 In versions before 2.2.5, those were called
485 <br /><br />
486 </dd>
489 <dd>
490 Whether config or cookie or http authentication should be used for this
491 server.
493 <ul>
494 <li>
495 'config' authentication
497 way: username and password are stored in
499 </li>
500 <li>
501 'cookie' authentication mode
503 2.2.3 allows you to log in as any valid MySQL user with the
504 help of... cookies. Log name and password are stored in
505 cookies during the session and password is deleted when it
506 ends.
507 </li>
508 <li>
509 'http' authentication (was called 'advanced' in older versions)
511 allows you to log in as any valid MySQL user via HTTP-Auth.
512 </li>
513 </ul><br />
516 for more information.
517 <br /><br />
518 </dd>
520 <dt>
523 </dt>
524 <dd>
525 The user/password-pair which phpMyAdmin will use to connect to this
526 MySQL-server. This user/password pair is not needed when HTTP or cookie
527 authentication is used, and should be empty.<br /><br />
528 </dd>
531 <dd>
532 If set to a(an array of) database name(s), only this(these) database(s)
533 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
534 database(s) name(s) may contain MySQL wildcards characters
538 This setting is an efficient way to lower the server charge since the
539 latter does not need to send MySQL requests to build the available
541 privileges rules of the MySQL database server</span>. If set, it just
542 means only these databases will be displayed but
544 <br /><br />
545 </dd>
548 <dd>
549 Only useful when using phpMyAdmin with multiple server entries. If set,
550 this string will be displayed instead of the hostname in the pull-down
551 menu on the main page. This can be useful if you want to show only
552 certain databases on your system, for example.
553 <br /><br />
554 </dd>
556 <dt>
559 </dt>
560 <dd>
561 Starting with version 2.3.0 phpMyAdmin offers a lot of features
562 to work with master / foreign - tables. To use those as well as
563 the bookmark feature you need special tables with a
564 predefined structure, which we explain below.<br />
565 If you are the only user of this phpMyAdmin installation, you can
566 use your current database to store those special tables; in this
567 case, just put your current database name in
569 <br /><br />
570 If you are setting up a multi-user phpMyAdmin installation,
571 you will need to create a new database and setup special privileges,
572 so, as superuser:
573 <br /><br />
574 <ul>
575 <li>
576 create a new database for phpMyAdmin:<br />
580 privileges on this database. Here is a query to set up
583 controluser):<br />
584 <tt>
585 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to 'pma'@'localhost';
586 </tt><br />
588 </li>
589 <li>
591 </li>
592 </ul><br />
593 </dd>
595 <dt>
598 </dt>
599 <dd>
600 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This can be
601 useful for queries you often run.<br /><br />
603 To allow the usage of this functionality you have to:
604 <ul>
606 <li>within this database create a table following this scheme:
607 <br />
608 <tt>
617 </tt>
618 </li>
619 <li>enter the table name in
621 </ul><br />
622 </dd>
624 <dt>
627 </dt>
628 <dd>
629 Since release 2.2.4 you can describe, in a special 'relation' table,
630 which field is a key in another table (a foreign key). phpMyAdmin
631 currently uses this to
632 <ul>
633 <li>
634 make clickable, when you browse the master table, the data values
635 that point to the foreign table;
636 </li>
637 <li>
639 when browsing the master table, if you move the mouse to a column
640 containing a foreign key (use also the 'table_info' table);
641 </li>
642 <li>
643 display links on the table properties page, to check referential
644 integrity (display missing foreign keys) for each described key;
645 </li>
646 <li>
647 in query-by-example, create automatic joins (see an example in
649 </li>
650 <li>
651 enable you to get a PDF schema of your database (also uses the
652 table_coords table).
653 </li>
654 </ul>
655 <br />
657 The keys can be numeric or character.
658 <br /><br />
660 To allow the usage of this functionality the superuser has to:
661 <ul>
663 <li>
664 within this database create a table following this scheme:
665 <br />
666 <tt>
672 `foreign_table` varchar(64) NOT NULL default '',<br />
673 `foreign_field` varchar(64) NOT NULL default '',<br />
674 PRIMARY KEY (`master_db`, `master_table`, `master_field`),<br />
677 </tt>
678 </li>
679 <li>
680 put the relation table name in
682 </li>
683 <li>
684 now as normal user open phpMyAdmin and for each one of your
685 tables where you want to use this feature, click
687 </li>
688 </ul><br />
691 future development of the cross-db relations.<br /><br />
692 </dd>
694 <dt>
697 </dt>
698 <dd>
699 Since release 2.3.0 you can describe, in a special 'table_info'
700 table, which field is to be displayed as a tool-tip when moving the
701 cursor over the corresponding key.
702 <br />
703 This configuration variable will hold the name of this special
704 table.
705 To allow the usage of this functionality the superuser has to:
706 <ul>
708 <li>within this database create a table following this scheme:
709 <br />
710 <tt>
714 `display_field` varchar(64) NOT NULL default '',<br />
717 </tt>
718 </li>
719 <li>
720 put the table name in
722 </li>
723 <li>
724 then for each table where you want to use this feature,
726 to choose the field.
727 </li>
728 </ul><br />
730 <br /><br />
731 </dd>
733 <dt>
737 </dt>
738 <dd>
739 Since release 2.3.0 you can have phpMyAdmin create PDF pages showing
740 the relations between your tables. To do this it needs two tables
743 table will be placed on a PDF schema output).
744 <br /><br />
747 output.
748 <br /><br />
749 To allow the usage of this functionality the superuser has to:
750 <ul>
752 <li>
753 within this database create a table following this scheme:
754 <br />
755 <tt>
762 PRIMARY KEY (`db_name`, `table_name`, `pdf_page_number`)<br />
763 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin PDF output';<br />
764 </tt>
765 </li>
766 <li>
767 also within this database create:<br />
768 <tt>
771 `page_nr` int(10) unsigned NOT NULL auto_increment,<br />
776 </tt>
777 </li>
778 <li>
779 put the first table name in
781 and the second table name in
783 </li>
784 </ul><br />
786 <br /><br />
787 </dd>
789 <dt>
792 </dt>
793 <dd>
794 <!-- This part requires a content update! -->
795 Since release 2.3.0 you can store comments to describe each column
797 <br /><br />
798 Starting with release 2.5.0, comments are consequently used on the table property
799 pages and table browse view, showing up as tool-tips above the column name (properties page)
800 or embedded within the header of table in browse view. They can also be shown
801 in a table dump. Please see the relevant configuration directives later on.
802 <br /><br />
803 Also new in release 2.5.0 is a mime-transformation system which is also based on
805 for further information. To use the mime-transformation system, your column_info
806 table has to have the three new fields 'mimetype', 'transformation', 'transformation_options'.
807 <br /><br />
808 To allow the usage of this functionality the superuser has to:
809 <ul>
811 <li>
812 within this database create a table following this scheme:
813 <br />
814 <tt>
822 transformation varchar(255) NOT NULL default '',<br />
823 transformation_options varchar(255) NOT NULL default '',<br />
825 UNIQUE KEY db_name (db_name, table_name, column_name)<br />
827 </tt>
828 </li>
829 <li>
830 put the table name in
832 </li>
833 <li>
835 <tt>
839 ADD `transformation_options` VARCHAR( 255 ) NOT NULL ;<br />
840 </tt>
841 and remember that the Variable in config.inc.php has been renamed
842 from <br />$cfg['Servers'][$i]['column_comments'] to $cfg['Servers'][$i]['column_info']
843 </li>
844 </ul><br />
845 </dd>
847 <dt>
850 </dt>
851 <dd>
852 Since release 2.5.0 you can store your SQL history, which means all queries you
853 entered manually into the phpMyAdmin interface. If you don't want to use a table-
854 based history, you can use the JavaScript-based history. Using that, all your
855 history items are deleted when closing the window.<br /><br />
858 you want to have on hold. On every login, this list gets cut to the maximum amount.
859 <br /><br />
861 The query history is only available if you use the JavaScript-based query window,
863 <br /><br />
865 To allow the usage of this functionality the superuser has to:
866 <ul>
868 <li>
869 within this database create a table following this scheme:
870 <br />
871 <tt>
880 INDEX ( `username` , `db` , `table` , `timevalue` )<br />
882 </tt>
883 </li>
884 <li>
885 put the table name in
887 </li>
888 </ul><br />
889 </dd>
891 <dt>
894 </dt>
895 <dd>
896 Because release 2.5.0 introduced the new MIME-transformation support, the
897 column_info table got enhanced with three new fields. If the above variable is
898 set to TRUE (default) phpMyAdmin will check if you have the latest table structure
899 available. If not, it will emit a warning to the superuser.<br /><br />
901 You can disable this checking behavior by setting the variable to false, which
902 should offer a performance increase.<br /><br />
904 Recommended to set to FALSE, when you are sure, your table structure is up to date.
905 <br /><br />
906 </dd>
908 <dt>
910 </dt>
911 <dd>
912 If your rule order is empty, then IP authentication is disabled.
913 <br /><br />
915 applies all deny rules followed by allow rules.
916 Access is allowed by default. Any client which does not match a Deny
917 command or does match an Allow command will be allowed access to the
918 server.
919 <br /><br />
921 applies all allow rules followed by deny rules. Access is denied by
922 default. Any client which does not match an Allow directive or does
923 match a Deny directive will be denied access to the server.
924 <br /><br />
925 If your rule order is set to 'explicit', the authentication is
926 performed in a similar fashion to rule order 'deny,allow', with the
930 and was available in Apache by specifying allow and deny rules without
931 setting any order.
932 <br /><br />
933 </dd>
935 <dt>
937 </dt>
938 <dd>
939 The general format for the rules is as such:<br />
940 <tt>
941
943 </tt>
944 <br /><br />
949 well:<br />
950 <tt>
953 </tt>
954 <br /><br />
956 Having an empty rule list is equivalent to either using
960 <br /><br />
962 For the IP matching system, the following work:<br />
966 But the following does not work:<br />
968 <br /><br />
969 </dd>
972 <dd>
973 If you have more than one server configured, you can set
975 that server when phpMyAdmin is started, or set it to 0 to be given a
976 list of servers without logging in.<br />
978 MUST be set to that server.
979 <br /><br />
980 </dd>
983 <dd>
984 Defines whether to use GZip output buffering for increased
985 speed in HTTP transfers.
986 <br /><br />
987 </dd>
990 <dd>
991 Whether persistent connections should be used or not (mysql_connect or
992 mysql_pconnect).
993 <br /><br />
994 </dd>
997 <dd>
998 Set the number of seconds a script is allowed to run. If seconds is set
999 to zero, no time limit is imposed.<br />
1000 This setting is used while importing/exporting dump files but has no
1001 effect when PHP is running in safe mode.
1002 <br /><br />
1003 </dd>
1006 <dd>
1007 Mark used tables and make it possible to show databases with locked
1008 tables (since 3.23.30).
1009 <br /><br />
1010 </dd>
1013 <dd>
1014 Defines whether SQL-queries generated by phpMyAdmin should be displayed
1015 or not.
1016 <br /><br />
1017 </dd>
1020 <dd>
1021 Defines whether normal users (non-administrator) are allowed to
1022 delete their own database or not. If set as FALSE, the link "Drop
1024 mydatabase" will be rejected. Quite practical for ISP's with many
1025 customers.
1026 <br /><br />
1027 </dd>
1030 <dd>
1032 displayed when you're about to loose data.
1033 <br /><br />
1034 </dd>
1037 <dd>
1038 Define whether the previous login should be recalled or not in cookie
1039 authentication mode.
1040 <br /><br />
1041 </dd>
1044 <dd>
1045 Define whether the "search string inside database" is enabled or not.
1046 <br /><br />
1047 </dd>
1050 <dd>
1051 Defines whether to use select-based menu and display only the current
1052 tables in the left frame (smaller page).
1053 Only in Non-Lightmode you can use the feature to display nested folders
1054 using $cfg['LeftFrameTableSeparator']
1055 <br /><br />
1056 </dd>
1059 <dd>
1060 Defines a string to be used to nest table spaces. Defaults to '__'. This
1061 means if you have tables like 'first__second__third' this will be
1063 If set to FALSE or empty, the feature is disabled.
1064 NOTE: You shall not use this Separator in a table name at the beginning or
1065 end of a table name, or multiple times after another without any other
1066 characters in between.
1067 <br /><br />
1068 </dd>
1071 <dd>
1072 Defines whether to display table comment as tool-tip in left frame or
1073 not.
1074 <br /><br />
1075 </dd>
1078 <dd>
1079 If tool-tips are enabled and a DB comment is set, this will flip the comment
1080 and the real name. That means, if you have a table called 'user0001' and add
1081 the comment 'MyName' on it, you will see the name 'MyName' used consequently
1082 in the left frame and the tool-tip shows the real name of the DB.
1083 <br /><br />
1084 </dd>
1087 <dd>
1088 Same as $cfg['ShowTooltipAliasDB'], except this works for table names.
1089 <br /><br />
1090 </dd>
1093 <dd>
1094 Defines whether to display space usage and statistics about databases
1095 and tables or not.<br />
1096 Note that statistics requires at least MySQL 3.23.3 and that, at this
1097 date, MySQL doesn't return such information for Berkeley DB tables.
1098 <br /><br />
1099 </dd>
1101 <dt>
1106 </dt>
1107 <dd>
1111 starting main (right) frame. This setting does not check MySQL commands
1112 entered directly.
1113 <br /><br />
1115 Please note that to block the usage of phpinfo() in scripts, you
1116 have to put this in your php.ini:<br />
1118 <br /><br />
1122 coded password value in the configuration file, end users can't be
1123 allowed to change their passwords.
1124 <br /><br />
1125 </dd>
1128 <dd>
1129 Defines whether to suggest a database name on the
1131 <br /><br />
1132 </dd>
1135 <dd>
1137 content or not.
1138 <br /><br />
1139 </dd>
1142 <dd>
1143 Defines whether navigation bar buttons contain text or symbols only.
1144 <br /><br />
1145 </dd>
1148 <dd>
1149 Defines whether an user should be displayed a
1151 <br /><br />
1152 </dd>
1155 <dd>
1156 Number of rows displayed when browsing a result set. If the result set
1157 contains more rows, Previous/Next links will be shown.
1158 <br /><br />
1159 </dd>
1162 <dd>
1166 DATE, DATETIME & TIMESTAMP, ascending order else- by default.
1167 <br /><br />
1168 </dd>
1171 <dd>
1173 from edition when browsing a table's content or not.
1174 Valid values are:<br />
1177 <br />
1180 <br /><br />
1181 </dd>
1184 <dd>
1185 Defines whether MySQL functions fields should be displayed or not in
1186 edit/insert mode.
1187 <br /><br />
1188 </dd>
1191 <dd>
1192 Defines which type of editing controls should be used for CHAR and
1193 VARCHAR fields. Possible values are:
1194 <ul>
1195 <li>
1196 input - this allows to limit size of text to size of field in
1197 MySQL, but has problems with newlines in fields
1198 </li>
1199 <li>
1200 textarea - no problems with newlines in fields, but also no
1201 length limitations
1202 </li>
1203 </ul>
1204 Default is old behavior so input.
1205 <br /><br />
1206 </dd>
1208 <dt>
1212 </dt>
1213 <dd>
1214 Defines whether to allow the use of zip/GZip/BZip2 compression when
1215 creating a dump file or not.
1216 <br /><br />
1217 </dd>
1220 <dd>
1221 If set to True, do use less graphically intense tabs on the top of the mainframe.
1222 <br /><br />
1223 </dd>
1226 <dd>
1227 Defines the tab displayed by default on server view. Possible
1232 <br /><br />
1233 </dd>
1236 <dd>
1237 Defines the tab displayed by default on database view. Possible
1240 <br /><br />
1241 </dd>
1244 <dd>
1245 Defines the tab displayed by default on table view. Possible
1249 <br /><br />
1250 </dd>
1253 <dd>
1254 If set to an URL which points to the MySQL documentation (type depends
1256 generated.
1257 <br />
1259 Documentation page</a> for more information about MySQL manuals and
1260 their types.
1261 <br /><br />
1262 </dd>
1265 <dd>
1266 Type of MySQL documentation:
1267 <ul>
1273 </ul>
1274 <br /><br />
1275 </dd>
1278 <dd>
1279 Defines the default language to use, if not browser-defined or
1280 user-defined.<br />
1282 this setting.
1283 <br /><br />
1284 </dd>
1287 <dd>
1288 Force: always use this language (must be defined in the
1290 <br /><br />
1291 </dd>
1294 <dd>
1295 Default character set to use for recoding of MySQL queries. This must be
1297 option.<br />
1298 You can give here any character set which is in
1300 choice, user can select any of them.
1301 <br /><br />
1302 </dd>
1305 <dd>
1306 Allow character set recoding of MySQL queries. You need recode or iconv
1307 support (compiled in or module) in PHP to allow MySQL queries recoding
1308 and used language file must have it enabled (by default only these
1309 which are in Unicode, just to avoid losing some characters).
1310 <br /><br />
1311 </dd>
1314 <dd>
1315 You can select here which functions will be used for character set
1316 conversion.
1317 Possible values are:<br />
1318 <ul>
1319 <li>auto - automatically use available one (first is tested
1320 iconv, then recode)</li>
1323 </ul>
1324 Default is auto.
1325 <br /><br />
1326 </dd>
1329 <dd>
1330 Available character sets for MySQL conversion. You can add your own (any of
1331 supported by recode/iconv) or remove these which you don't use.
1332 Character sets will be shown in same order as here listed, so if you
1333 frequently use some of these move them to the top.
1334 <br /><br />
1335 </dd>
1338 <dd>
1339 Left frame width in pixel.
1340 <br /><br />
1341 </dd>
1343 <dt>
1346 </dt>
1347 <dd>
1348 The background colors (HTML) used for both the frames.
1349 <br /><br />
1350 </dd>
1352 <dt>
1354 </dt>
1355 <dd>
1356 The URI of the background image used for the right frame. It can be
1357 absolute as well as relative from your phpMyAdmin directory.
1358 </dd>
1361 <dd>
1362 The color (HTML) used for the pointer in the left frame (does not work
1363 with Netscape 4).
1364 <br /><br />
1365 </dd>
1368 <dd>
1369 The size of a table's border.
1370 <br /><br />
1371 </dd>
1374 <dd>
1375 The color (HTML) used for table headers.
1376 <br /><br />
1377 </dd>
1380 <dd>
1381 The color (HTML) #1 for table rows.
1382 <br /><br />
1383 </dd>
1386 <dd>
1387 The color (HTML) #2 for table rows.
1388 <br /><br />
1389 </dd>
1391 <dt>
1394 </dt>
1395 <dd>
1396 The colors (HTML) uses for the pointer and the marker in browse mode
1398 The former feature highlights the row over which your mouse is passing
1399 and the latter lets you visually mark/unmark rows by clicking on
1400 them.<br />
1401 You can disable both of these features by emptying the respective
1402 directive.
1403 <br /><br />
1404 </dd>
1406 <dt>
1411 </dt>
1412 <dd>
1413 Number of columns and rows for the textareas.<br />
1415 SQL textareas inside the query window.<br />
1416 The Char* values are used for CHAR and VARCHAR editing (if configured
1417 via $cfg['CharEditing']).
1418 <br /><br />
1419 </dd>
1421 <dt>
1423 </dt>
1424 <dd>
1425 Defines if the whole textarea of the query box will be selected on
1426 click.
1427 <br /><br />
1428 </dd>
1431 <dd>
1433 field on browse view. Can be turned off by a toggle button on the
1434 browse page.
1435 <br /><br />
1436 </dd>
1438 <dt>
1441 </dt>
1442 <dd>
1443 Defines the place where modify and delete links would be put when
1444 tables contents are displayed (you may have them displayed both at the
1445 left and at the right).
1448 <br /><br />
1449 </dd>
1453 </dt>
1454 <dd>
1455 There are 3 display modes: horizontal, horizontalflipped and vertical. Define
1456 which one is displayed by default. The first mode displays each row on a
1457 horizontal line, the second rotates the headers by 90 degrees, so you can use
1458 descriptive headers even though fields only contain small values and still
1459 print them out. The vertical mode sorts each row on a vertical lineup.<br /><br />
1460 The HeaderFlipType can be set to 'css' or 'faked'. When using 'css' the rotation
1461 of the header for horizontalflipped is done via CSS. If set to 'faked' PGP
1462 does the transformation for you, but of course this does not look as good as CSS.
1463 <br /><br />
1464 </dd>
1467 <dd>
1468 When editing/creating new columns in a table all fields normally get lined up
1469 one field a line. (default: 'horizontal'). If you set this to 'vertical' you
1470 can have each field lined up vertically beneath each other. You can save up
1471 a lot of place on the horizontal direction and no longer have to scroll.
1472 <br /><br />
1473 </dd>
1477 </dt>
1478 <dd>
1479 By setting the corresponding variable to TRUE you can enable the display of
1480 column comments in Browse or Property display. In browse mode, the comments
1481 are show inside the header. In property mode, comments are displayed using
1482 a CSS-formatted dashed-line below the name of the field. The comment is shown
1483 as a tool-tip for that field.
1484 <br /><br />
1485 </dd>
1488 <dd>
1489 The name of the directory, ending with a slash, where SQL files have
1490 been uploaded by other means than phpMyAdmin (for example, ftp).
1491 Those files are available under a drop-down box when you click the
1492 database name, then the SQL tab.
1493 <br /><br />
1495 <br /><br />
1496 This feature is useful when your file is too big to be uploaded via
1497 HTTP, or when file uploads are disabled in PHP.
1498 <br /><br />
1499 Please note that if PHP is running in safe mode, this directory must
1500 be owned by the same user as the owner of the phpMyAdmin scripts.
1501 <br /><br />
1502 </dd>
1505 <dd>
1506 Repeat the headers every X cells, or 0 to deactivate.
1507 <br /><br />
1508 </dd>
1518 </dt>
1519 <dd>
1520 All those variables affect the new query frame/window. When $cfg['QueryFrame']
1521 is set to true a new frame is embedded on the left with a small area. Clicking
1522 on that results in opening a direct interface to enter SQL queries.<br /><br />
1523 When $cfg['QueryFrameJS'] is set to true, clicking on that link opens a new
1524 custom sized browser window ($cfg['QueryWindowWidth'], $cfg['QueryWindowWidth'] -
1525 both integers for the size in pixels). If set to false, clicking on the link
1526 only opens the SQL input in the mainframe.<br /><br />
1527 The usage of the JavaScript query window is recommended if you have a JavaScript
1528 enabled browser. Basic functions are used to exchange quite a few variables, so
1529 most 4th generation browsers should be capable to use that feature. It currently
1531 If $cfg['QueryHistoryDB'] is set to TRUE, all your Queries are logged to a table,
1533 If set to FALSE, all your queries will be appended to the form, but only as long
1534 as your window is opened they remain saved.<br /><br />
1535 When using the JavaScript based query window, it will always get updated when you
1536 click on a new table/db to browse and will focus if you click on "Edit SQL" after
1537 using a query.<br /><br />
1538 If $cfg['QueryHistoryDB'] is set to TRUE you can specify the amount of saved
1539 history items using $cfg['QueryHistoryMax'].<br /><br />
1540 The query window also has a custom tabbed look to group the features. Using the
1541 variable $cfg['QueryWindowDefTab'] you can specify the default tab to be used
1542 when opening the query window. It can be set to either 'sql', 'files', 'history'
1543 or 'full'.<br /><br />
1544 The variable $cfg['QueryFrameDebug'] can be used by developers for easier future
1545 feature integration.
1546 <br /><br />
1547 </dd>
1550 <dd>
1552 <br /><br />
1553 </dd>
1556 <dd>
1557 Determines for how large tables phpMyAdmin should get exact row count by
1561 <br /><br />
1562 </dd>
1565 <dd>
1566 The main use of the new SQL Parser is to pretty-print SQL queries. By
1567 default we use HTML to format the query, but you can disable this by
1569 <br /><br />
1570 </dd>
1574 <dd>
1575 For the pretty-printing of SQL queries, under some cases the part of a
1576 query inside a bracket is indented. By changing
1579 specifies the units of the indent amount that you specified. This is
1580 used via stylesheets.
1581 <br /><br />
1582 </dd>
1585 <dd>
1586 This array is used to define the colours for each type of element of
1587 the pretty-printed SQL queries. The tuple format is<br />
1589 If you specify an empty string for the color of a class, it is ignored
1590 in creating the stylesheet.
1591 You should not alter the class names, only the colour strings.<br />
1593 <ul>
1617 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1618 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1619 </ul><br />
1620 </dd>
1622 <dt><b>$cfg['SQLValidator']['use']</b> boolean</dt>
1623 <dd>
1624 phpMyAdmin now supports use of the <a href="http://developer.mimer.com/validator/index.htm">Mimer SQL Validator</a> service,
1625 as originally published on
1627 <br />
1628 For help in setting up your system to use the service, see the
1630 <br /><br />
1631 </dd>
1633 <dt><b>$cfg['SQLValidator']['username']</b> string<br />
1634 <b>$cfg['SQLValidator']['password']</b> string</dt>
1635 <dd>
1636 The SOAP service allows you to login with <tt>anonymous</tt>
1637 and any password, so we use those by default.. Instead, if
1638 you have an account with them, you can put your login details
1639 here, and it will be used in place of the anonymous login.
1640 <br /><br />
1641 </dd>
1643 <dt><b>$cfg['DBG']['enable']</b> boolean</dt>
1644 <dd>
1645 <b>DEVELOPERS ONLY!</b><br />
1646 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1647 the code.
1648 <br />
1649 For help in setting up your system to this, see the
1651 </dd>
1653 <dt><b>$cfg['DBG']['profile']['enable']</b> boolean</dt>
1654 <dd>
1655 <b>DEVELOPERS ONLY!</b><br />
1656 Enable profiling support for phpMyAdmin. This will append a chunk of data
1657 to the end of every page displayed in the main window with profiling
1658 statistics for that page.<br />
1659 You may need need to increase the maximum execution time for this to
1660 complete successfully.
1661 </dd>
1663 <dt><b>$cfg['DBG']['profile']['threshold']</b> float (units in milliseconds)</dt>
1664 <dd>
1665 <b>DEVELOPERS ONLY!</b><br />
1666 When profiling data is displayed, this variable controls the threshold of
1667 display for any profiling data, based on the average time each time has
1668 taken. If it is over the threshold it is displayed, otherwise it is not
1669 displayed. This takes a value in milliseconds. In most cases you don't need
1670 to edit this.
1671 </dd>
1673 <dt><b>$cfg['ColumnTypes'] </b>array</dt>
1674 <dd>
1675 All possible types of a MySQL column. In most cases you don't need to
1676 edit this.
1677 <br /><br />
1678 </dd>
1680 <dt><b>$cfg['AttributeTypes'] </b>array</dt>
1681 <dd>
1682 Possible attributes for fields. In most cases you don't need to edit
1683 this.
1684 <br /><br />
1685 </dd>
1687 <dt><b>$cfg['Functions'] </b>array</dt>
1688 <dd>
1689 A list of functions MySQL supports. In most cases you don't need to
1690 edit this.
1691 <br /><br />
1692 </dd>
1694 </dl>
1696 <!-- TRANSFORMATIONS -->
1698 <h2>Transformations</h2>
1700 <p>
1704 </p>
1707 <h3>[1. Introduction]</h3>
1709 <p>To enable transformations, you have to setup the column_info table and the proper
1711 <br />
1713 <p>You can apply different transformations to the contents of each field. The
1714 transformation will take the content of each field and transform it with
1715 certain rules defined in the selected transformation.</p><br />
1717 <p>Say you have a field 'filename' which contains a filename. Normally you would see
1718 in phpMyAdmin only this filename. Using transformations you can transform that filename
1719 into a HTML link, so you can click inside of the phpMyAdmin structure on the field's
1720 link and will see the file displayed in a new browser window. Using transformation
1721 options you can also specify strings to append/prepend to a string or the format you
1722 want the output stored in.</p><br />
1724 <p>For a general overview of all available transformations and their options, you can
1725 consult your <i><www.your-host.com>/<your-install-dir>/libraries/transformations/overview.php3</i>
1726 installation.</p>
1729 <h3>[2. Usage]</h3>
1731 <p>Go to your tbl_properties.inc.php3 page (i.e. reached through clicking on the
1732 'properties' link for a table). There you will see three new fields at the end of the
1733 line. They are called 'MIME-type', 'Browser transformation' and 'Transformation options'.</p>
1734 <br />
1736 <ul>
1737 <li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
1738 empty or to use 'auto' [this feature is not yet available]. Please note that
1739 transformations are inactive as long as no mime-type is selected.</li>
1741 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
1742 hopefully growing amount of pre-defined transformations. See below for information on
1743 how to build your own transformation.<br />
1745 There are global transformations and mimetype-bound transformations. Global transformations
1746 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
1747 Mimetype-bound transformations usually only operate on a certain mimetype. There are
1748 transformations which operate on the main mimetype (like 'image'), which will most likely
1749 take the subtype into regard, and those who only operate on a
1750 specific subtype (like 'image/jpeg').<br />
1752 You can use transformations on mimetypes for which the function was not defined for. There
1753 is no security check for you selected the right transformation, so take care of what the
1754 output will be like.</li>
1756 <li>The field 'Transformation options' is a free-type textfield. You have to enter
1757 transform-function specific options here. Usually the transforms can operate with default
1758 options, but it is generally a good idea to look up the overview to see which options are
1759 necessary.<br />
1761 Much like the ENUM/SET-Fields, you have to split up several options using the format
1762 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
1763 parsed as an array, leaving the first value the first element in the array, and so
1764 forth.<br />
1766 If you want to specify a MIME character set you can define it in the transformation_options.
1767 You have to put that outside of the pre-defined options of the specific mime-transform,
1769 for which you can specify 2 options and you want to append a character set, enter "'first
1770 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
1772 </ul>
1775 <h3>[3. File structure]</h3>
1777 <p>All mimetypes and their transformations are defined through single files in
1778 the directory 'libraries/transformations/'.</p><br />
1780 <p>They are stored in files to ease up customization and easy adding of new
1781 transformations.</p><br />
1783 <p>Because the user cannot enter own mimetypes, it is kept sure that transformations
1784 always work. It makes no sense to apply a transformation to a mimetype, the
1785 transform-function doesn't know to handle.</p><br />
1787 <p>One can, however, use empty mime-types and global transformations which should work
1788 for many mimetypes. You can also use transforms on a different mimetype they where built
1789 for, but pay attention to option usage as well as what the transformation does to your
1790 field.</p><br />
1792 <p>There is a basic file called 'global.inc.php3'. This function can be included by
1793 any other transform function and provides some basic functions.</p><br />
1795 <p>There are 5 possible file names:</p>
1797 <ol>
1798 <li>A mimetype+subtype transform:<br /><br />
1800 [mimetype]_[subtype]__[transform].inc.php3<br /><br />
1802 Please not that mimetype and subtype are separated via '_', which shall not be
1803 contained in their names. The transform function/filename may contain only
1804 characters which cause no problems in the file system as well as the PHP function
1805 naming convention.<br /><br />
1807 The transform function will the be called 'PMA_transform_[mimetype]_[subtype]__[transform]()'.<br /><br />
1809 <b>Example:</b><br /><br />
1811 text_html__formatted.inc.php3<br />
1812 PMA_transform_text_html__formatted()</li>
1814 <li>A mimetype (w/o subtype) transform:<br /><br />
1816 [mimetype]__[transform].inc.php3<br /><br />
1818 Please note that there are no single '_' characters.
1819 The transform function/filename may contain only characters which cause no problems
1820 in the file system as well as the PHP function naming convention.<br /><br />
1822 The transform function will the be called 'PMA_transform_[mimetype]__[transform]()'.<br /><br />
1824 <b>Example:</b><br /><br />
1826 text__formatted.inc.php3<br />
1827 PMA_transform_text__formatted()</li>
1829 <li>A mimetype+subtype without specific transform function<br /><br />
1831 [mimetype]_[subtype].inc.php3<br /><br />
1833 Please note that there are no '__' characters in the filename. Do not use special
1834 characters in the filename causing problems with the file system.<br /><br />
1836 No transformation function is defined in the file itself.<br /><br />
1838 <b>Example:</b><br /><br />
1840 text_plain.inc.php3<br />
1841 (No function)</li>
1843 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
1845 [mimetype].inc.php3<br /><br />
1847 Please note that there are no '_' characters in the filename. Do not use special
1848 characters in the filename causing problems with the file system.<br /><br />
1850 No transformation function is defined in the file itself.<br /><br />
1852 <b>Example:</b><br /><br />
1854 text.inc.php3<br />
1855 (No function)</li>
1857 <li>A global transform function with no specific mimetype<br /><br />
1859 global__[transform].inc.php3<br /><br />
1861 The transform function will the be called 'PMA_transform_global__[transform]()'.<br /><br />
1863 <b>Example:</b><br /><br />
1865 global__formatted<br />
1866 PMA_transform_global__formatted()</li>
1867 </ol>
1869 <br />
1870 <p>So generally use '_' to split up mimetype and subtype, and '__' to provide a
1871 transform function.</p><br />
1873 <p>All filenames containing no '__' in themselves are not shown as valid transform
1874 functions in the dropdown.</p><br />
1876 <p>Please see the libraries/transformations/TEMPLATE file for adding your own transform
1877 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
1878 without a transform function. Also note the introduction of a function description in
1879 the language files. For each function a $strTransformation_[filename without .inc.php3]
1880 has to exist.</p><br />
1882 <p>You can use the template generator to generate new functions and entries in the
1883 language file.</p><br />
1885 <p>To create a new transform function please see libraries/transformations/template_generator.sh.
1886 To create a new, empty mimetype please see libraries/transformations/template_generator_mimetype.sh.</p><br />
1888 <!-- FAQ -->
1890 <h2>FAQ - Frequently Asked Questions</h2>
1892 <p>
1900 </p>
1903 <h3>[1. Server]</h3>
1905 <h4>
1906 [1.1] I'm running PHP 4+ and my server is crashing each time a specific
1907 action is required or phpMyAdmin sends a blank page or a page full of
1908 cryptic characters to my browser, what can I do?
1909 </h4>
1910 <p>
1911 There are some known PHP bugs with output buffering and compression.<br />
1912 Try to set the <tt>$cfg['OBGzip']</tt> directive to <tt>FALSE</tt> in your
1913 <i>config.inc.php or .php3</i> file and the
1914 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
1915 configuration file.<br />
1916 Furthermore, we know about such problems connected to the release
1917 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
1918 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.
1919 </p>
1921 <h4>
1922 [1.2] My Apache server crashes when using phpMyAdmin.
1923 </h4>
1924 <p>
1925 You should first try the latest versions of Apache (and possibly MySQL).
1926 <br />
1927 See also the other FAQ entry about PHP bugs with output buffering.
1928 <br />
1929 If your server keeps crashing, please ask for help in the various
1930 Apache support groups.
1931 </p>
1933 <h4>
1935 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
1936 script: I'm always displayed the login screen.
1937 </h4>
1938 <p>
1939 This is a known PHP bug (see this
1941 official PHP bug database. It means there is and won't be any phpMyAdmin
1942 fix against it because there is no way to code a fix.
1943 </p>
1945 <h4>
1946 [1.4] Using phpMyAdmin on IIS, I'm displayed the error message:
1947 "The specified CGI application misbehaved by not returning a
1948 complete set of HTTP headers...".
1949 </h4>
1950 <p>
1951 You just forgot to read the <i>install.txt</i> file from the php
1952 distribution. Have a look at the last message in this
1954 official PHP bug database.
1955 </p>
1957 <h4>
1958 [1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
1959 messages with the HTTP or advanced authentication mode.
1960 </h4>
1961 <p>
1962 This is a known problem with the PHP ISAPI filter: it's not so stable. For
1963 some more information and complete testings see the messages posted by
1964 André B. aka "djdeluxe76" in
1965 <a href="http://www.phpwizard.net/phorum/read.php?f=1&i=6624&t=6300">this thread</a>
1966 from the phpWizard forum.<br />
1967 Please use instead the cookie authentication mode.
1968 </p>
1970 <h4>
1971 [1.6] I can't use phpMyAdmin on PWS: nothing is displayed!</h4>
1972 <p>
1973 This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
1974 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
1975 declarations (2 lines) from the scripts <i>header.inc.php3</i>,
1976 <i>header_printview.inc.php3</i>, <i>index.php3</i>, <i>left.php3</i> and
1977 <i>libraries/common.lib.php3</i>.
1978 </p>
1980 <h4>
1981 [1.7] How can I GZip or Bzip a dump or a CSV export. It does not seem to
1982 work.
1983 </h4>
1984 <p>
1985 These features are based on the <tt>gzencode()</tt> and
1986 <tt>bzcompress()</tt> PHP functions to be more independent of the platform
1987 (Unix/Windows, Safe Mode or not, and so on).
1988 So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
1989 (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
1990 We faced PHP crashes when trying to download a dump with MS Internet
1991 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
1992 this case you should switch to the release version of PHP 4.2.0.
1993 </p>
1995 <h4>
1996 [1.8] I cannot insert a text file in a table, and I get an error about
1997 safe mode being in effect.
1998 </h4>
1999 <p>
2000 Your uploaded file is saved by PHP in the "upload dir", as
2001 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2002 the system default is <i>/tmp</i>).
2003 <br />
2004 We recommend the following setup for Apache servers running in safe mode,
2005 to enable uploads of files while being reasonably secure:
2006 </p>
2007 <ul>
2008 <li>create a separate directory for uploads:
2009 <tt>mkdir /tmp/php</tt></li>
2010 <li>give ownership to the Apache server's user.group:
2011 <tt>chown apache.apache /tmp/php</tt></li>
2012 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2013 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in php.ini</li>
2014 <li>restart Apache</li>
2015 </ul>
2017 <h4>
2018 [1.9] I'm having troubles when uploading files. In general file uploads
2019 don't work on my system and uploaded files have a <tt>Content-Type:</tt>
2020 header in the first line.
2021 </h4>
2022 <p>
2023 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2024 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?
2025 <br />
2026 So the problem is that this package has a serious bug that was corrected
2027 ages ago in PHP (2001-01-28: see
2029 for more details). The problem is that the bugged package is still
2030 available though it was corrected (see
2032 for more details).
2033 <br />
2034 So please download
2035 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2036 and the problem should go away.
2037 <br />
2038 And that fixes the \r\n problem with file uploads!
2039 </p>
2041 <h4>
2042 [1.10] I'm having troubles when uploading files with phpMyAdmin running
2043 on a secure server. My browser is Internet Explorer and I'm using the
2044 Apache server.
2045 </h4>
2046 <p>
2047 As suggested by "Rob M" in the phpWizard forum, add this line to
2048 your <i>httpd.conf</i>:<br />
2049 <tt>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</tt><br />
2050 It seems to clear up many problems between Internet Explorer and SSL.
2051 </p>
2053 <h4>
2054 [1.11] I get an 'open_basedir restriction' while uploading a file from
2055 the query box.
2056 </h4>
2057 <p>
2058 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2059 restrictions. Assuming that the restriction allows you to open files in the
2060 current directory ('.'), all you have to do is create a 'tmp' directory
2061 under the phpMyAdmin install directory, with permissions 777 and the same
2062 owner as the owner of your phpMyAdmin directory. The uploaded files will
2063 be moved there, and after execution of your SQL commands, removed.
2064 </p>
2066 <h4>
2067 [1.12] I have lost my MySQL root password, what can I do?
2068 </h4>
2069 <p>
2070 The MySQL manual explains how to
2072 reset the permissions</a>.
2073 </p>
2075 <h4>
2076 [1.13] I get an error 'No SQL query' when trying to execute a bookmark.
2077 </h4>
2078 <p>
2079 If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2080 cannot access the uploaded query.
2081 </p>
2083 <h4>
2084 [1.14] I get an error 'No SQL query' when trying to submit a query from
2085 the convenient text area.
2086 </h4>
2087 <p>
2088 Check the <tt>post_max_size</tt> directive from your PHP configuration file
2089 and try to increase it.
2090 </p>
2092 <h4>
2093 [1.15] I have problems with <i>mysql.user</i> field names.
2094 </h4>
2095 <p>
2096 In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2097 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2098 names to align with current standards.
2099 </p>
2100 <h4>
2101 [1.16] I cannot upload big dump files.
2102 </h4>
2103 <p>
2104 The first things to check (or ask your host provider to check) are the
2105 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2106 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2107 <br />
2108 All of these three settings limit the maximum size of data that can be
2109 submitted and handled by PHP. One user also said that post_max_size
2110 and memory_limit need to be larger than upload_max_filesize.
2111 </p>
2113 <h4>
2114 [1.17] Does phpMyAdmin support MySQL 4.1?
2115 </h4>
2116 <p>
2117 Because of a major change in the definition syntax of string field types,
2118 this version of phpMyAdmin probably won't work correctly with
2119 MySQL >= 4.1.0! We will work on the support as soon as
2120 MySQL 4.1.0 is released.
2121 </p>
2123 <h4>
2124 [1.18] I'm running MySQL <= 4.0.1 having
2125 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2126 capital letter in its name it is changed to lowercase as it should. But
2127 if I try to DROP this table MySQL is unable to find the corresponding
2128 file.
2129 </h4>
2130 <p>
2131 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2132 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2133 directive.
2134 </p>
2136 <h4>
2137 [1.19] I can't run the "display relations" feature because the
2138 script seems not to know the font face I'm using!
2139 </h4>
2140 <p>
2141 The "FPDF" library we're using for this feature requires some
2142 special files to use font faces.<br />
2143 Please refers to the
2145 these files.
2146 </p>
2149 <h4>
2150 [1.20] I receive the error "cannot load MySQL extension, please
2151 check PHP Configuration".
2152 </h4>
2153 <p>
2154 To connect to a MySQL server, PHP needs a set of MySQL functions called
2155 "MySQL extension".
2156 This extension may be part of the PHP server (compiled-in), otherwise it
2157 needs to be loaded dynamically. Its name is probably <i>mysql.so</i> or
2158 <i>mysql.dll</i>. phpMyAdmin tried to load the extension but failed.
2159 <br /><br />
2160 Usually, the problem is solved by installing a software package called
2161 "PHP-MySQL" or something similar.
2162 </p>
2164 <h4>
2165 [1.21] I am running the CGI version of PHP under Unix, and I cannot
2166 login using cookie auth.
2167 </h4>
2168 <p>
2169 In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.
2170 </p>
2172 <h4>
2173 [1.22] I don't see the "Location of text file" field, so
2174 I cannot upload.
2175 </h4>
2176 <p>
2177 This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2178 parameter is not set to "on".
2179 </p>
2181 <h4>
2182 [1.23] I'm running MySQL on a Win32 machine. Each time I create a new
2183 table the table and field names are changed to lowercase!
2184 </h4>
2185 <p>
2186 This happens because the MySQL directive <tt>lower_case_table_names</tt>
2187 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2188 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2189 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2190 directory and add the following line to the group [mysqld]:<br />
2191 <tt>set-variable = lower_case_table_names=0</tt><br />
2192 Next, save the file and restart the MySQL service. You can always check the
2193 value of this directive using the query<br />
2194 <tt>SHOW VARIABLES LIKE 'lower_case_table_names';</tt>
2195 </p>
2197 <h4>
2198 [1.24] Some characters are being truncated in my queries, or I get
2199 characters randomly added. I am running PHP 4.2.3.
2200 </h4>
2201 <p>
2202 This is a
2204 </p>
2206 <h4>
2207 [1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
2208 and I get problems, such as undefined variables when I run a SQL query.
2209 </h4>
2210 <p>
2211 A tip from Jose Fandos: put a comment on the following two lines
2212 in httpd.conf, like this:<br />
2213 <tt># mod_gzip_item_include file \.php$</tt><br />
2215 as this version of mod_gzip on Apache (Windows) has problems handling
2216 PHP scripts. Of course you have to restart Apache.
2217 </p>
2219 <h4>
2220 [1.26] I just installed phpMyAdmin in my document root of IIS but
2221 I get the error "No input file specified" when trying to
2222 run phpMyAdmin.
2223 </h4>
2224 <p>
2225 This is a permission problem. Right-click on the phpmyadmin folder
2226 and choose properties. Under the tab Security, click on "Add"
2227 and select the user "IUSER_machine" from the list. Now set his
2228 permissions and it should work.
2229 </p>
2231 <h4>
2232 [1.27] I get empty page when I want to view huge page (eg.
2233 db_details_structure.php3 with plenty of dabases).
2234 </h4>
2235 <p>
2237 GZIP output buffering enabled. If you turn off it (by <code>$cfg['OBGzip']
2238 = FALSE</code> in config.inc.php3), it should work. This bug will be fixed
2239 in PHP 5.0.0.
2240 </p>
2242 <h4>
2243 [1.28] My MySQL server sometimes refuses queries and returns the message
2244 'Errorcode: 13'. What does this mean?
2245 </h4>
2246 <p>
2247 This can happen due to a MySQL bug when having database / table names with
2248 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2249 To fix this, turn off this directive, convert all database and table names
2250 to lower case and turn it on again. Alternatively, there's a bug-fix
2251 available starting with MySQL 3.23.56 / 4.0.11-gamma.
2252 </p>
2255 <h4>
2256 [1.29] When I create a table or modify a field, I get an error
2257 and the fields are duplicated.
2258 </h4>
2259 <p>
2260 It is possible to configure Apache in such a way that PHP has problems
2261 interpreting .php files.
2262 <br /><br />
2263 The problems occur when two different (and conflicting) set of directives
2264 are used:
2265 <br /><br />
2266 <tt>
2267 SetOutputFilter PHP<br />
2268 SetInputFilter PHP<br />
2269 </tt>
2270 &
2271 <br />
2272 <tt>
2273 AddType application/x-httpd-php .php
2274 </tt>
2275 <br /><br />
2276 In the case we saw, one set of directives was in <tt>httpd.conf</tt>, while
2277 the other set was in <tt>php.conf</tt>.<br />
2278 The recommended way is with <tt>AddType</tt>, so just comment out
2279 the first set of lines and restart Apache:
2280 <br /><br />
2281 <tt><b>
2282 #SetOutputFilter PHP<br />
2283 #SetInputFilter PHP<br /></b>
2284 </tt>
2285 </p>
2288 <h3>[2. Configuration]</h3>
2290 <h4>
2291 [2.1] The error message "Warning: Cannot add header information -
2292 headers already sent by ..." is displayed, what's the problem?
2293 </h4>
2294 <p>
2295 Edit your <i>config.inc.php or .php3</i> file and ensure there is nothing
2296 (I.E. no blank lines, no spaces, no characters...) neither before the
2297 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
2298 tag at the end.
2299 </p>
2301 <h4>
2302 [2.2] phpMyAdmin can't connect to MySQL. What's wrong?
2303 </h4>
2304 <p>
2305 Either there is an error with your PHP setup or your username/password is
2306 wrong. Try to make a small script which uses mysql_connect and see if it
2307 works. If it doesn't, it may be you haven't even compiled MySQL support
2308 into PHP.
2309 </p>
2311 <h4>
2312 [2.3] The error message "Warning: MySQL Connection Failed: Can't
2313 connect to local MySQL server through socket '/tmp/mysql.sock'
2314 (111)..." is displayed. What can I do?
2315 </h4>
2316 <p><br />
2317 For RedHat users, Harald Legner suggests this on the mailing list:
2318 <br /><br />
2319 On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2320 In your php.ini you will find a line
2321 <br />
2322 <tt>mysql.default_socket = /tmp/mysql.sock</tt>
2323 <br />
2324 change it to
2325 <br />
2326 <tt>mysql.default_socket = /var/lib/mysql/mysql.sock</tt>
2327 <br />
2328 Then restart apache and it will work.
2329 <br /><br />
2330 Here is a fix suggested by Brad Ummer in the phpwizard forum:
2331 </p>
2332 <ul>
2333 <li>
2334 First, you need to determine what socket is being used by MySQL.
2335 <br />
2336 To do this, telnet to your server and go to the MySQL bin directory. In
2337 this directory there should be a file named <i>mysqladmin</i>. Type
2338 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2339 info about your MySQL server, including the socket
2340 (<i>/tmp/mysql.sock</i>, for example).
2341 </li>
2342 <li>
2343 Then, you need to tell PHP to use this socket.<br />Assuming you are
2344 using PHP 3.0.10 or better, you can specify the socket to use when you
2345 open the connection. To do this in phpMyAdmin, you need to complete the
2346 socket information in the config.inc.php3.<br />
2347 For example:
2348 <tt>$cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</tt><br /><br />
2349 Please also make sure that the permissions of this file allow to be readable
2350 by your webserver (i.e. '0755').
2351 </li>
2352 </ul>
2353 <p>
2354 Have also a look at the
2356 corresponding section of the MySQL documentation</a>.
2357 </p>
2359 <h4>
2360 [2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
2361 what can I do?
2362 </h4>
2363 <p>
2364 Try to set the <tt>$cfg['OBGZip']</tt> directive to <tt>FALSE</tt> in the
2365 phpMyAdmin configuration file. It helps sometime.<br />
2366 Also have a look at your PHP version number: if it contains
2367 "4.0b..." it means you're running a beta version of PHP. That's
2368 not a so good idea, please upgrade to a plain revision.
2369 </p>
2371 <h4>
2372 [2.5] Each time I want to insert or change a record or drop a database
2373 or a table, an error 404 (page not found) is displayed or, with HTTP or
2374 cookie authentication, I'm asked to login again. What's wrong?
2375 </h4>
2376 <p>
2377 Check the value you set for the <tt>$cfg['PmaAbsoluteUri']</tt> directive
2378 in the phpMyAdmin configuration file.
2379 </p>
2381 <h4>
2382 [2.6] I get an "Access denied for user: 'root@localhost' (Using
2383 password: YES)"-error when trying to access a MySQL-Server on a
2384 host which is port-forwarded for my localhost
2385 </h4>
2386 <p>
2387 When you are using a port on your localhost, which you redirect via
2388 port-forwarding to another host, MySQL is not resolving the localhost
2389 as expected.<br />
2390 Erik Wasser explains: The solution is: if your host is "localhost"
2391 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2392 connection for speeding up things. And that doesn't work in this configuration
2393 with port forwarding.<br />
2395 TCP connection.
2396 </p>
2400 <h3>[3. Known limitations]</h3>
2402 <h4>
2403 [3.1] When using HTTP authentication, an user who logged out can not
2404 relogin in with the same nick.
2405 </h4>
2406 <p>
2407 This is related to the authentication mechanism (protocol) used by
2408 phpMyAdmin. We plan to change it as soon as we may find enough free time
2409 to do it, but you can bypass this problem: just close all the opened
2410 browser windows and then go back to phpMyAdmin. You should be able to
2411 log in again.
2412 </p>
2414 <h4>
2415 [3.2] When dumping a large table in compressed mode, I get a memory
2416 limit error or a time limit error.
2417 </h4>
2418 <p>
2419 As of version 2.2.4, we build the compressed dump in memory, so large
2420 tables dumps may hang. The only alternative we can think about (using
2421 system calls to mysqldump then gzip or bzip2) would not be applicable in
2422 environments where PHP is in safe mode: access to system programs is
2423 is limited by the system administrator, and time limit is enforced.
2424 </p>
2426 <h4>
2427 [3.3] With InnoDB tables, I lose foreign key relationships when I rename
2428 or alter a table.
2429 </h4>
2430 <p>
2431 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in
2432 mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
2433 </p>
2435 <h4>
2436 [3.4] I am unable to import dumps I created with the mysqldump tool
2437 bundled with the MySQL server distribution.
2438 </h4>
2439 <p>
2440 The problem is that mysqldump creates invalid comments like this:
2441 </p>
2442 <pre>
2443 -- MySQL dump 8.22
2444 --
2445 -- Host: localhost Database: database
2446 ---------------------------------------------------------
2447 -- Server version 3.23.54
2448 </pre>
2449 <p>
2450 The invalid part of the code is the horizontal line made of dashes that
2451 appears once in every dump created with mysqldump. If you want to run your
2452 dump you have to turn it into valid MySQL. This means, you have to add a
2453 whitespace after the first to dashes of the line or add a # before it:
2454 <br />
2455 <code>
2456 -- -------------------------------------------------------<br />
2457 </code>
2458 or<br />
2459 <code>
2460 #---------------------------------------------------------
2461 </code>
2462 </p>
2464 <h4>
2465 [3.3] When using nested folders ($cfg['LeftFrameTableSeparator']) there
2466 are some multiple hierarchies displayed in a wrong manner?!
2467 </h4>
2468 <p>
2469 Please note that you should not use the seperating string multiple times
2470 without any characters between them, or at the beginning/end of your table
2471 name. If you have to, think about using another TableSeparator or disabling
2472 that feature
2473 </p>
2476 <h3>[4. ISPs, multi-user installations ]</h3>
2478 <h4>
2479 [4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
2480 need to install it for each customer.
2481 </h4>
2482 <p>
2483 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
2484 your users. The development of this feature was kindly sponsored by
2485 NetCologne GmbH.
2486 This requires a properly setup MySQL user management and phpMyAdmin
2487 HTTP or cookie authentication. See the install section on
2488 "Using HTTP authentication".
2489 </p>
2491 <h4>
2492 [4.2] What's the preferred way of making phpMyAdmin secure against evil
2493 access.
2494 </h4>
2495 <p>
2496 This depends on your system.<br />
2497 If you're running a server which cannot be accessed by other people, it's
2498 sufficient to use the directory protection bundled with your webserver
2499 (with Apache you can use <i>.htaccess</i> files, for example).<br />
2500 If other people have telnet access to your server, you should use
2501 phpMyAdmin's HTTP authentication feature.
2502 <br /><br />
2503 Suggestions:
2504 </p>
2505 <ul>
2506 <li>
2507 Your <i>config.inc.php3</i> file should be <tt>chmod 660</tt>.
2508 </li>
2509 <li>
2510 All your phpMyAdmin files should be chown phpmy.apache, where phpmy
2511 is a user whose password is only known to you, and apache is the
2512 group under which Apache runs.
2513 </li>
2514 <li>
2515 You should use PHP safe mode, to protect from other users that try
2516 to include your <i>config.inc.php3</i> in their scripts.
2517 </li>
2518 </ul>
2520 <h4>
2521 [4.3] I get errors about not being able to include a file in
2522 <i>/lang</i> or in <i>/libraries</i>.
2523 </h4>
2524 <p>
2525 Check <i>php.ini</i>, or ask your sysadmin to check it. The
2526 <tt>include_path</tt> must contain "." somewhere in it, and
2527 <tt>open_basedir</tt>, if used, must contain "." and
2528 "./lang" to allow normal operation of phpMyAdmin.
2529 </p>
2530 <h4>
2531 [4.4] phpMyAdmin always gives "Access denied" when using HTTP
2532 authentication.
2533 </h4>
2534 <p>
2535 This could happen for several reasons:
2536 </p>
2537 <ul>
2538 <li>
2539 <tt>$cfg['Servers'][$i]['controluser']</tt> and/or
2540 <tt>$cfg['Servers'][$i]['controlpass']</tt> are wrong.
2541 </li>
2542 <li>
2543 The username/password you specify in the login-dialog are invalid.
2544 </li>
2545 <li>
2546 You have already setup a security mechanism for the
2547 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
2548 phpMyAdmin's authentication, so remove it.
2549 </li>
2550 </ul>
2552 <h4>
2553 [4.5] Is it possible to let users create their own databases?
2554 </h4>
2555 <p>
2556 Starting with 2.2.5, in the user management page, you can enter a wildcard
2557 database name for a user (for example "joe%"),
2558 and put the privileges you want. For example,
2559 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
2560 would let a user create/manage his/her database(s).
2561 </p>
2563 <h4>
2564 [4.6] How can I use the Host-based authentication additions?
2565 </h4>
2566 <p>
2567 If you have existing rules from an old .htaccess file, you can take them
2568 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
2569 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
2570 be a major benefit here if your installation is suited to using it. Then
2571 you can just add those updated lines into the
2572 <tt>$cfg['Servers'][$i]['AllowDeny']['rules']</tt> array.
2573 <br /><br />
2574 If you want a pre-made sample, you can try this fragment. It stops the
2575 'root' user from logging in from any networks other than the private
2576 network IP blocks.
2577 <br />
2578 <tt>
2579 //block root from logging in except from the private networks<br />
2580 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';<br />
2581 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(<br />
2582 'deny root from all',<br />
2583 'allow root from localhost',<br />
2584 'allow root from 10.0.0.0/8',<br />
2585 'allow root from 192.168.0.0/16',<br />
2586 'allow root from 172.16.0.0/12',<br />
2587 );
2588 </tt>
2589 </p>
2590 <h4>
2591 [4.7] Authentication window is displayed more than once, why?
2592 </h4>
2593 <p>
2594 This happens if you are using a URL to start phpMyAdmin which is
2595 different than the one set in your <tt>$cfg['PmaAbsoluteUri']</tt>.
2596 For example, a missing "www", or entering with an IP address
2597 while a domain name is defined in the config file.
2598 </p>
2601 <h3>[5. Browsers or client OS]</h3>
2603 <h4>
2604 [5.1] I get an out of memory error, and my controls are non-functional,
2605 when trying to create a table with more than 14 fields.
2606 </h4>
2607 <p>
2608 We could reproduce this problem only under Win98/98SE. Testing under
2609 WinNT4 or Win2K, we could easily create more than 60 fields.
2610 <br />
2611 A workaround is to create a smaller number of fields, then come back to
2612 your table properties and add the other fields.
2613 </p>
2615 <h4>
2616 [5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.
2617 </h4>
2618 <p>
2619 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
2620 with each script/website that use forms.<br />
2621 Upgrade or downgrade your Xitami server.
2622 </p>
2624 <h4>
2625 [5.3] I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).
2626 </h4>
2627 <p>
2628 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
2629 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
2630 don't seem to work.<br />
2632 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
2633 the user's temporary directory, so they must be moved before closing
2634 Konqueror, or else they disappear. GZip dumps give an error message.<br />
2636 Testing needs to be done for Konqueror 2.2.2.<br />
2637 </p>
2639 <h4>
2640 [5.4] I can't use the cookie authentication mode because Internet
2641 Explorer never stores the cookies.
2642 </h4>
2643 <p>
2644 MS Internet Explorer seems to be really buggy about cookies, at least till
2645 version 6. And thanks to Andrew Zivolup we've traced also a PHP 4.1.1 bug
2646 in this area!
2647 <br />
2648 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
2649 work!
2650 </p>
2652 <h4>
2653 [5.5] In Internet Explorer 5.0, I get JavaScript errors when browsing my
2654 rows.
2655 </h4>
2656 <p>
2657 Upgrade to at least Internet Explorer 5.5 SP2.<br />
2658 </p>
2660 <h4>
2661 [5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying
2662 to modify a row in a table with many fields, or with a text field
2663 </h4>
2664 <p>
2665 Your table neither have a primary key nor an unique one, so we must use a
2666 long URL to identify this row. There is a limit on the length of the URL in
2667 those browsers, and this not happen in Netscape, for example. The
2668 workaround is to create a primary or unique key, or use another browser.
2669 <br />
2670 </p>
2672 <h4>
2673 [5.7] I refresh (reload) my browser, and come back to the welcome
2674 page.
2675 </h4>
2676 <p>
2677 Some browsers support right-clicking into the frame you want to refresh,
2678 just do this in the right frame.<br />
2679 </p>
2681 <h4>
2682 [5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
2683 query box.
2684 </h4>
2685 <p>
2686 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
2687 Mozilla versions.<br />
2688 </p>
2690 <h4>
2691 [5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
2692 whitespace in the SQL-Query edit area: the page scrolls down.
2693 </h4>
2694 <p>
2695 This is a Mozilla bug (see bug #26882 at
2697 </p>
2699 <h4>
2700 [5.10] With Netscape 4.75 I get empty rows between each row of data in a
2701 CSV exported file.
2702 </h4>
2703 <p>
2704 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
2705 data in octet-stream mode. Since we can't detect the specific Netscape
2706 version, we cannot workaround this bug.
2707 </p>
2709 <h4>
2710 [5.11] Extended-ASCII characters like German umlauts are displayed
2711 wrong.
2712 </h4>
2713 <p>
2714 Please ensure that you have set your browser's character set to the one of the
2715 language file you have selected on phpMyAdmin's start page.
2716 Alternatively, you can try the auto detection mode that is supported by the
2717 recent versions of the most browsers.
2718 </p>
2720 <h4>
2721 [5.12] Apple OS X: Safari browser changes special characters to
2722 "?".
2723 </h4>
2724 <p>
2725 This issue has been reported by a OS X user, who adds that Chimera,
2726 Netscape and Mozilla do not have this problem.
2727 </p>
2729 <h4>
2730 [5.13] With Internet Explorer 5.5 or 6, and HTTP authentication type,
2731 I cannot manage two servers: I login to the first one, then the other one,
2732 but if I switch back to the first, I have to login on each operation.
2733 </h4>
2734 <p>
2735 This is a bug in Internet Explorer, other browsers do not behave this way.
2736 </p>
2739 <h3>[6. Using phpMyAdmin]</h3>
2741 <h4>
2742 [6.1] I can't insert new rows into a table / I can't create a table
2743 - MySQL brings up a SQL-error.
2744 </h4>
2745 <p>
2746 Examine the SQL error with care. Often the problem is caused by
2747 specifying a wrong field-type.<br />
2748 Common errors include:
2749 </p>
2750 <ul>
2751 <li>Using <tt>VARCHAR</tt> without a size argument</li>
2752 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
2753 </ul>
2754 <p>
2755 Also, look at the syntax chapter in the MySQL manual to confirm that your
2756 syntax is correct.
2757 </p>
2759 <h4>
2760 [6.2] When I create a table, I click the Index checkbox for 2 fields and
2761 phpMyAdmin generates only one index with those 2 fields.
2762 </h4>
2763 <p>
2764 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
2765 index. If you want two indexes, create the first one when creating the
2766 table, save, then display the table properties and click the Index link to
2767 create the other index.
2768 </p>
2770 <h4>
2771 [6.3] How can I insert a null value into my table?
2772 </h4>
2773 <p>
2774 Since version 2.2.3, you have a checkbox for each field that can be null.
2775 Before 2.2.3, you had to enter "null", without the quotes, as the
2776 field's value.
2777 </p>
2779 <h4>
2780 [6.4] How can I backup my database or table?
2781 </h4>
2782 <p>
2783 Click on a database or table name in the left frame, the properties will be
2784 displayed. Then on the menu, click "Export", you can dump
2785 the structure, the data, or both. This will generate standard SQL
2786 statements that can be used to recreate your database/table.
2787 <br /><br />
2788 You will need to choose "Save as file", so that phpMyAdmin can
2789 transmit the resulting dump to your station. Depending on your PHP
2790 configuration, you will see options to compress the dump. See also the
2791 <tt>$cfg['ExecTimeLimit']</tt> configuration variable.
2792 <br /><br />
2793 For additional help on this subject, look for the word "dump" in
2794 this document.
2795 </p>
2797 <h4>
2798 [6.5] How can I restore (upload) my database or table using a dump?
2799 How can I run a ".sql" file.
2800 </h4>
2801 <p>
2802 Click on a database name in the left frame, the properties will be
2803 local displayed. Then in the "Run SQL query" section, type in
2804 your dump filename, or use the Browse button. Then click Go.
2805 <br /><br />
2806 For additional help on this subject, look for the word "upload"
2807 in this document.
2808 </p>
2810 <h4>
2811 [6.6] How can I use the relation table in Query-by-example?
2812 </h4>
2813 <p>
2814 Here is an example with the tables persons, towns and countries, all
2815 located in the database mydb. If you don't have a <tt>PMA_relation</tt>
2816 table, create it as explained in the configuration section. Then create the
2817 example tables:
2818 <br /><br />
2819 <tt>
2820 CREATE TABLE REL_countries (<br />
2821 country_code char(1) NOT NULL default '',<br />
2822 description varchar(10) NOT NULL default '',<br />
2823 PRIMARY KEY (country_code)<br />
2824 ) TYPE=MyISAM;<br />
2825 <br />
2826 INSERT INTO REL_countries VALUES ('C', 'Canada');<br />
2827 <br />
2828 CREATE TABLE REL_persons (<br />
2829 id tinyint(4) NOT NULL auto_increment,<br />
2830 person_name varchar(32) NOT NULL default '',<br />
2831 town_code varchar(5) default '0',<br />
2832 country_code char(1) NOT NULL default '',<br />
2833 PRIMARY KEY (id)<br />
2834 ) TYPE=MyISAM;<br />
2835 <br />
2836 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');<br />
2837 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');<br />
2838 <br />
2839 CREATE TABLE REL_towns (<br />
2840 town_code varchar(5) NOT NULL default '0',<br />
2841 description varchar(30) NOT NULL default '',<br />
2842 PRIMARY KEY (town_code)<br />
2843 ) TYPE=MyISAM;<br />
2844 <br />
2845 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');<br />
2846 INSERT INTO REL_towns VALUES ('M', 'Montréal');<br />
2847 <br />
2848 </tt>
2849 To setup appropriate links and display information:
2850 </p>
2851 <ul>
2852 <li>on table "REL_persons" click Structure, then Relation view</li>
2853 <li>in Links, for "town_code" choose "REL_towns->code"</li>
2854 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
2855 <li>on table "REL_towns" click Structure, then Relation view</li>
2856 <li>in "Choose field to display", choose "description"</li>
2857 <li>repeat the two previous steps for table "REL_countries"</li>
2858 </ul>
2860 <p>
2861 Then test like this:
2862 </p>
2863 <ul>
2864 <li>Click on your db name in the left frame</li>
2865 <li>Choose "Query"</li>
2866 <li>Use tables: persons, towns, countries</li>
2867 <li>Click "Update query"</li>
2868 <li>In the fields row, choose persons.person_name and click the
2869 "Show" tickbox </li>
2870 <li>Do the same for towns.description and countries.descriptions in the
2871 other 2 columns</li>
2872 <li>Click "Update query" and you will see in the query box that
2873 the correct joins have been generated</li>
2874 <li>Click "Submit query"</li>
2875 </ul>
2876 <br />
2879 <h4>
2880 [6.7] How can I use the "display field" feature?
2881 </h4>
2882 <p>
2883 Starting from the previous example, create the PMA_table_info as explained
2884 in the configuration section, then browse your persons table,
2885 and move the mouse over a town code or country code.
2886 </p>
2889 <h4>
2890 [6.8] How can I produce a PDF schema of my database?
2891 </h4>
2892 <p>
2893 First you have to fill the "relation", "table_coords"
2894 and "pdf_pages" configuration variables.
2895 <br /><br />
2896 Then, think about your schema layout: which tables will go on which pages.
2897 </p>
2898 <ul>
2899 <li>Click on your db name in the left frame</li>
2900 <li>Choose "Structure" in the navigation on top</li>
2901 <li>Choose "Edit PDF Pages" which should be somewhere at the
2902 bottom of the page</li>
2903 <li>Enter the name for a first pdf page and submit</li>
2904 <li>Choose this page to edit</li>
2905 <li>Now add a table you want to show on this page and it's coordinates and
2906 submit<br />
2907 First you will have to guess this coordinates of course, so just expect
2908 to have an area of about 297 * 210 and put the tables coordinates
2909 somewhere in there, you will be able to have a look at what happened
2910 and change them later.<br />
2911 For example, x=100 and y=200 means that the table will be at 200 mm
2912 down and 100 mm right from the upper left corner.<br />
2913 Actually if you have a width of more than 300 or a height of more than
2914 200 than it will automatically be scaled but 300*100 is a good start to
2915 have an idea of what coordinates to use.</li>
2916 <li>After every table you submitted you will have the possibility to submit
2917 more tables</li>
2918 <li>When you have entered enough tables Click on your db name in the left
2919 frame again</li>
2920 <li>Now, again at the bottom of the page you should be able to choose
2921 "Display PDF schema"<br />
2922 For testing it might be useful to show the grid as well, so you can see
2923 the coordinates used.<br />
2924 Maybe also choose color and submit.</li>
2925 <li>Save the file he will offer you to something like <i>Schema.pdf</i>
2926 (Internet Explorer has some bug there which might make it offer it
2927 without an extension. Under Windows it is important to have the
2928 extension ".pdf", under other OSes you should be fine just
2929 saving the file under the name it offers).</li>
2930 </ul>
2932 <h4>
2933 [6.9] phpMyAdmin is changing the type of one of my columns!
2934 </h4>
2935 <p>
2936 No, it's MySQL that is doing
2937 <a href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent column type changing</a>.
2938 </p>
2941 <h4>
2942 [6.10] When creating a privilege, what happens with underscores in
2943 the database name?
2944 </h4>
2945 <p>
2946 If you do not put a backslash before the underscore, this is a wildcard
2947 grant, and the underscore means "any character". So, if the
2948 database name is "john_db", the user would get rights to john1db,
2949 john2db...<br /><br />
2950 If you put a backslash before the underscore, it means that the database
2951 name will have a real underscore.
2952 </p>
2954 <h4>
2955 [6.11] What is the curious symbol ø in the statistics pages?
2956 </h4>
2957 <p>
2958 It means "average".
2959 </p>
2962 <h4>
2963 [6.12] I want to understand some Export options.
2964 </h4>
2965 <p>
2966 "Complete inserts" adds the column names on every INSERT command,
2967 for better documentation (but resulting file is bigger).<br />
2968 "Extended inserts" provides a shorter dump file by using only
2969 once the INSERT verb and the table name.<br />
2970 "Enclose table and field names with backquotes" ensures that
2971 field and table names formed with special characters are protected.<br />
2972 "Include column comments as inline SQL-comments" includes any
2973 column comments set in the PMA-DB in the dump as SQL comments (<i>/* xxx */</i>).<br /></p>
2975 <h4>
2976 [6.13] I would like to create a database with a dot in its name.
2977 </h4>
2978 <p>
2979 This is a bad idea, because in MySQL the syntax "database.table"
2980 is the normal way to reference a database and table name. Worse, MySQL
2981 will usually let you create a database with a dot, but then you cannot
2982 work with it, nor delete it.<br />
2983 </p>
2986 <h4>
2987 [6.14] How do I set up the SQL Validator?
2988 </h4>
2989 <p>
2990 To use it, you need a very recent version of PHP, 4.3.0 recommended, with
2991 XML, PCRE and PEAR support. On your system command line, run
2992 <tt>"pear install Net_Socket Net_URL HTTP_Request Mail_Mime Net_DIME
2993 SOAP"</tt> to get the necessary PEAR modules for usage.
2994 <br />
2995 If you use it, you should be aware that any SQL statement you
2996 submit will be stored anonymously (database/table/column names,
2997 strings, numbers replaced with generic values). The Mimer SQL
2998 Validator itself, is © 2001 Upright Database Technology.
2999 We utilize it as free SOAP service.
3000 </p>
3002 <h4>
3003 [6.15] I want to add a BLOB field and put an index on it, but MySQL
3004 says "BLOB column '...' used in key specification without a key
3005 length".
3006 </h4>
3007 <p>
3008 The right way to do this, is to create the field without any indexes,
3009 then display the table structure and use the "Create an index"
3010 dialog. On this page, you will be able to choose your BLOB field, and
3011 set a size to the index, which is the condition to create an index on
3012 a BLOB field.
3013 <br />
3014 </p>
3016 <h4>
3017 [6.16] How can I simply move in page with plenty editing fields?
3018 </h4>
3019 <p>
3020 You can use Ctrl+arrows for moving on most pages with plenty editing
3021 fields (table structure changes, row editing, etc.). You can also have
3022 a look at the directive $cfg['DefaultPropDisplay'] ('vertical') and see
3023 if this eases up editing for you.
3024 <br />
3025 </p>
3027 <h4>
3028 [6.17] Transformations: I can't enter my own mimetype! WTF is this feature
3029 then useful for?
3030 </h4>
3031 <p>
3032 Slow down :). Defining mimetypes is of no use, if you can't put transformations on them.
3033 Otherwise you could just put a comment on the field. Because entering your own mimetype will
3034 cause serious syntax checking issues and validation, this introduces a high-risk false-user-input
3035 situation. Instead you have to initialize mimetypes using functions or empty mimetype definitions.
3036 <br />
3037 Plus, you have a whole overview of available mimetypes. Who knows all those mimetypes by heart so
3038 he/she can enter it at will?
3039 <br />
3040 </p>
3043 <h4>
3044 [6.17] Bookmarks: Where can I store bookmarks? Why can't I see any bookmarks below the query box?
3045 What is this variable for?
3046 </h4>
3047 <p>
3048 Any query you have executed can be stored as a bookmark on the page where the results are displayed.
3049 You will find a button labeled 'Bookmark this query' just at the end of the page.<br />
3050 As soon as you have stored a bookmark, it is related to the database you run the query on. You can
3051 now access a bookmark dropdown on each page, the query box appears on for that database.<br />
3052 <br />
3053 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks. Just use the string
3054 <b>/*[VARIABLE]*/</b> anywhere in your query. Everything which is put into the <i>value</i> input
3055 box on the query box page will replace the string "/*[VARIABLE]*/" in your stored query.
3056 Just be aware of that you HAVE to create a valid query, otherwise your query won't be even able to be
3057 stored in the database.<br />
3058 Also remember, that everything else inside the <b>/*[VARIABLE]*/</b> string for your query will remain
3059 the way it is, but will be stripped of the /**/ chars. So you can use:<br /><br />
3060 <code>/*, [VARIABLE] AS myname */</code><br /><br />
3061 which will be expanded to<br /><br />
3062 <code>, VARIABLE as myname</code><br /><br />
3063 in your query, where VARIABLE is the string you entered in the input box. If an empty string is
3064 provided, no replacements are made.<br />
3065 <br />
3066 A more complex example. Say you have stored this query:<br /><br />
3067 <code>SELECT Name, Address FROM addresses WHERE 1 /* AND Name LIKE '%[VARIABLE]%' */</code><br /><br />
3068 Say, you now enter "phpMyAdmin" as the variable for the stored query, the full query will
3069 be:<br /><br />
3070 <code>SELECT Name, Address FROM addresses WHERE 1 AND Name LIKE '%phpMyAdmin%'</code>
3071 <br />
3072 <br />
3073 You can use multiple occurences of <b>/*[VARIABLE]*/</b> in a single query.<br />
3074 <b>NOTE THE ABSENCE OF SPACES</b> inside the "/**/" construct. Any spaces inserted there
3075 will be later also inserted as spaces in your query and may lead to unexpected results especially when
3076 using the variable expansion inside of a "LIKE ''" expression.<br />
3077 Your initial query which is going to be stored as a bookmark has to yield at least one result row so
3078 you can store the bookmark. You may have that to work around using well positioned "/**/"
3079 comments.
3080 </p>
3083 <h3>[7. phpMyAdmin project]</h3>
3085 <h4>
3086 [7.1] I have found a bug. How do I inform developers?
3087 </h4>
3088 <p>
3089 Our Bug Tracker is located at
3090 <a href="http://sourceforge.net/projects/phpmyadmin/">http://sourceforge.net/projects/phpmyadmin/</a>
3091 under the Bugs section.
3092 <br /><br />
3093 But please first discuss your bug with other users:
3094 <br />
3096 http://sourceforge.net/projects/phpmyadmin/</a> (and choose Forums)
3097 </p>
3099 <h4>
3100 [7.2] I want to translate the messages to a new language or upgrade an
3101 existing language, where do I start?
3102 </h4>
3103 <p>
3104 Always use the current CVS version of your language file.
3105 For a new language, start from <i>english-iso-8859-1.inc.php3</i>. If you
3106 don't know how to get the CVS version, please ask one of the developers.
3107 <br />
3108 Please note that we try not to use HTML entities like &eacute; in
3109 the translations, since we define the right character set in the file.
3110 With HTML entities, the text on JavaScript messages would not
3111 display correctly.
3112 However there are some entities that need to be there, for quotes
3113 ,non-breakable spaces, ampersands, less than, greater than.
3114 <br />
3115 You can then put your translations, as a zip file to avoid losing special
3116 characters, on the sourceforge.net translation tracker.
3117 <br />
3118 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3119 list, because this is where we ask for translations of new messages.
3120 <br />
3121 </p>
3123 <h4>
3124 [7.3] I would like to help out with the development of phpMyAdmin. How
3125 should I proceed?
3126 </h4>
3127 <p>
3128 The following method is preferred for new developers:
3129 </p>
3130 <ol>
3131 <li>
3132 fetch the current CVS tree over anonymous CVS:<br />
3133 <tt>cvs -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
3134 [Password: simply press the Enter key]<br />
3135 <tt>cvs -z3 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
3136 [This will create a new sub-directory named phpMyAdmin]
3137 </li>
3138 <li>
3139 add your stuff
3140 </li>
3141 <li>
3142 put the modified files (tar'ed and gzip'ed) inside the patch tracker of
3143 the
3144 <a href="http://sourceforge.net/projects/phpmyadmin/" target="_blank">phpMyAdmin SourceForge account</a>.
3145 </li>
3146 </ol>
3147 <p>
3148 Write access to the CVS tree is granted only to experienced developers who
3149 have already contributed something useful to phpMyAdmin.<br />
3150 Also, have a look at the
3152 </p>
3154 <!-- DEVELOPERS -->
3156 <h2>Developers Information</h2>
3158 <p>
3159 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3160 great features have been written by other people and you too can help to
3161 make phpMyAdmin a useful tool.
3162 </p>
3164 <p>
3165 If you're planning to contribute source, please read the following
3166 information:
3167 </p>
3168 <ul>
3169 <li>
3170 All files include <i>header.inc.php3</i> (layout),
3171 <i>libraries/common.lib.php3</i> (common functions) and
3172 <i>config.inc.php3</i>.
3173 <br />
3174 All configuration data belongs in <i>config.inc.php3</i>. Please keep
3175 it free from other code.
3176 <br />
3177 Commonly used functions should be added to
3178 <i>libraries/common.lib.php3</i> and more specific ones may be added
3179 within a library stored into the <i>libraries</i> sub-directory.
3180 </li>
3181 <li>
3182 Obviously, you're free to use whatever coding style you want. But
3183 please try to keep your code as simple as possible: beginners are
3184 using phpMyAdmin as an example application.<br />
3185 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3186 compliant on one hand, they fit the
3188 on the other hand. Please pay attention to this.
3189 </li>
3190 <li>
3191 Please try to keep up the file-naming conventions. Table-related stuff
3192 goes to <i>tbl_*.php3</i>, db-related code to <i>db_*.php3</i>,
3193 server-related tools to <i>server_*.php3</i> and so on.
3194 </li>
3195 <li>
3196 Please don't use verbose strings in your code, instead add the string
3197 (at least) to <i>english-iso-8859-1.inc.php3</i> and print() it out.
3198 </li>
3199 <li>
3200 If you want to be really helpful, write an entry for the ChangeLog.
3201 </li>
3204 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3205 better debug and profile their code.<br />
3206 Please see the <tt>$cfg['DBG']*</tt> configuration options for more
3207 information.<br />
3208 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3209 lost during its re-entry into Earth's atmosphere and in memory of the
3210 brave men and women who gave their lives for the people of Earth.
3211 </li>
3213 </ul>
3215 <!-- CREDITS -->
3217 <h2>Credits</h2>
3219 <pre>
3221 phpMyAdmin - Credits
3222 ====================
3224 CREDITS, in chronological order
3225 -------------------------------
3227 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
3228 * creator of the phpmyadmin project
3229 * maintainer from 1998 to summer 2000
3231 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
3232 * multi-language version
3233 * various fixes and improvements
3234 * project co-administrator
3236 - Olivier Müller <om_at_omnis.ch>
3237 * started SourceForge phpMyAdmin project in March 2001
3238 * sync'ed different existing CVS trees with new features and bugfixes
3239 * multi-language improvements, dynamic language selection
3240 * current project maintainer
3241 * many bugfixes and improvements
3243 - Loïc Chapeaux <lolo_at_phpheaven.net>
3244 * rewrote and optimized javascript, DHTML and DOM stuff
3245 * rewrote the scripts so they fit the PEAR coding standards and
3246 generate XHTML1.0 and CSS2 compliant codes
3247 * improved the language detection system
3248 * many bugfixes and improvements
3250 - Robin Johnson <robbat2_at_users.sourceforge.net>
3251 * database maintence controls
3252 * table type code
3253 * Host authentication IP Allow/Deny
3254 * DB-based configuration (Not completed)
3255 * SQL parser
3256 * SQL validator
3257 * many bugfixes and improvements
3259 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
3260 * bookmarks feature
3261 * multiple dump feature
3262 * gzip dump feature
3263 * zip dump feature
3265 - Geert Lund <glund_at_silversoft.dk>
3266 * various fixes
3267 * moderator of the phpMyAdmin users forum at phpwizard.net
3269 - Korakot Chaovavanich <korakot_at_iname.com>
3270 * "insert as new row" feature
3272 - Pete Kelly <webmaster_at_trafficg.com>
3273 * rewrote and fix dump code
3274 * bugfixes
3276 - Steve Alberty <alberty_at_neptunlabs.de>
3277 * rewrote dump code for PHP4
3278 * mySQL table statistics
3279 * bugfixes
3281 - Benjamin Gandon <gandon_at_isia.cma.fr>
3282 * main author of the version 2.1.0.1
3283 * bugfixes
3285 - Alexander M. Turek <rabus_at_bugfixes.info>
3286 * XML exports
3287 * MySQL 4 related features
3288 * various small features and fixes
3289 * German language file updates
3291 - Mike Beck <mike.beck_at_ibmiller.de>
3292 * automatic joins in QBE
3293 * links column in printview
3294 * Relation view
3296 - Michal Cihar <nijel_at_users.sourceforge.net>
3297 * enhanced index creation/display feature
3298 * feature to use a different charset for HTML than for MySQL
3299 * Czech language file updates
3301 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
3302 (http://sourceforge.net/projects/phpmysqlformgen/)
3303 * suggested the patch for multiple table printviews
3305 - Garvin Hicking <hicking_at_faktor-e.de>
3306 * built the patch for vertical display of table rows
3307 * built the Javascript based Query window + SQL history
3308 * Improvement of column/db comments
3309 * (MIME)-Transformations for columns
3310 * Use custom alias names for Databases in left frame
3311 * vertical display of column properties page
3312 * some bugfixes, smaller features
3314 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
3315 * japanese kanji encoding conversion feature
3317 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
3318 * the Cookie authentication mode
3320 - Axel Sander <n8falke_at_users.sourceforge.net>
3321 * table relation-links feature
3323 - Maxime Delorme <delorme.maxime_at_free.fr>
3324 * PDF schema output, thanks also to Olivier Plathey for the
3325 "FPDF" library (see http://www.fpdf.org/).
3327 - Olof Edlund <olof.edlund_at_upright.se>
3328 * SQL validator server
3330 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
3331 * phpMyAdmin logo
3333 And also to the following people who have contributed minor changes,
3334 enhancements, bugfixes or support for a new language since version 2.1.0:
3336 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
3337 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
3338 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
3339 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
3340 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
3341 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
3342 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
3343 Luís V., Martijn W. van der Lee,
3344 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
3345 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas, "Manuzhai".
3348 Original Credits of Version 2.1.0
3349 ---------------------------------
3351 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
3352 to create a web-based interface to MySQL using PHP3. Although I have not
3353 used any of his source-code, there are some concepts I've borrowed from
3354 him. phpMyAdmin was created because Peter told me he wasn't going to
3355 further develop his (great) tool.
3356 Thanks go to
3357 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
3358 code for the check when dropping a table or database. He also suggested
3359 that you should be able to specify the primary key on tbl_create.php3. To
3360 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
3361 well as a bug-report. Plus many smaller improvements.
3362 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
3363 were introduced in 1.3.0 (including quite significant ones like the
3364 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
3365 bug-fixes and help.
3366 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
3367 language-independent by outsourcing the strings to a separate file. He
3368 also contributed the French translation.
3369 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
3370 tbl_select.php3, a feature to display only some fields from a table.
3371 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
3372 functions in tbl_change.php3. He also added the
3373 "Query by Example" feature in 2.0.
3374 - Dave Walton <walton_at_nordicdms.com> added support for multiple
3375 servers and is a regular contributor for bug-fixes.
3376 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
3377 features for 2.0.6.
3378 The following people have contributed minor changes, enhancements, bugfixes
3379 or support for a new language:
3380 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
3381 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
3382 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
3383 G. Wieggers.
3385 And thanks to everyone else who sent me email with suggestions, bug-reports
3386 and or just some feedback.
3387 </pre>
3394 <img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" border="0" height="31" width="88" /></a>
3395
3397 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" border="0" width="88" height="31" /></a>
3398 </p>
3400 </body>
3401 </html>