2 phpMyAdmin 2.4.0-dev Documentation
4 * Sourceforge phpMyAdmin project page [ http://www.phpmyadmin.net/
7 + Version history: ChangeLog
8 + General notes: README
10 * Documentation version: $Id: Documentation.html,v 1.373 2003/01/07
12 ______________________________________________________________________
14 Top - Requirements - Introduction - Installation -
15 Configuration - FAQ - Developers - Credits
16 ______________________________________________________________________
20 * PHP3 or PHP4: phpMyAdmin widely uses the 'str_replace()' php
21 function that was added in PHP 3.0.6, but was buggy up until
22 PHP 3.0.8. Then you should not run this script with PHP3 < 3.0.8.
23 PHP also needs to be compiled with MySQL support;
24 * MySQL (tested with 3.21.x, 3.22.x, 3.23.x and 4.0.x);
25 Note: Because of a major change in the definition syntax of string
26 field types, this version of phpMyAdmin probably won't work
27 correctly with MySQL >= 4.1.0!
28 * a web-browser (doh!).
29 ______________________________________________________________________
31 Top - Requirements - Introduction - Installation -
32 Configuration - FAQ - Developers - Credits
33 ______________________________________________________________________
37 phpMyAdmin can manage a whole MySQL-server (needs a super-user) but
38 also a single database. To accomplish the latter you'll need a
39 properly set up MySQL-user who can read/write only the desired
40 database. It's up to you to look up the appropriate part in the MySQL
41 manual. Currently phpMyAdmin can:
42 * create and drop databases
43 * create, copy, drop and alter tables
44 * delete, edit and add fields
45 * execute any SQL-statement, even batch-queries
46 * manage keys on fields
47 * load text files into tables
48 * create (*) and read dumps of tables
49 * export (*) and import data to CSV values
50 * administer multiple servers and single databases
51 * check referential integrity
52 * create complex queries automatically connecting required tables
53 * create PDF graphics of your Database layout
54 * communicate in more than 41 different languages
56 (*) phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats)
57 dumps and CSV exports if you use PHP4 >= 4.0.4 with Zlib support
58 (--with-zlib) and/or Bzip2 support (--with-bz2).
59 ______________________________________________________________________
61 Top - Requirements - Introduction - Installation -
62 Configuration - FAQ - Developers - Credits
63 ______________________________________________________________________
67 NOTE: phpMyAdmin does not apply any special security methods to the
68 MySQL database server. It is still the sysadmin's job to grant
69 permissions on the MySQL databases properly. phpMyAdmin's "Users" page
72 Warning for Mac users:if you are on a MacOS version before OS X,
73 Stuffit unstuffs with Mac formats.
74 So you'll have to resave as in Bbedit to unix style ALL phpMyAdmin
75 scripts before uploading them to your server, as PHP seems not to like
76 Mac-style end of lines character ("\r").
78 Documentation warning: when you see in this document a .php3 file
79 extension, please transpose to .php if you are using a kit with files
80 having this extension.
83 1. Choose and download a distribution kit with the files having the
84 extension (.php3 or .php) depending on the way your web/PHP server
85 interprets those extensions.
86 2. Untar or unzip the distribution (be sure to unzip the
87 subdirectories): tar xzvf phpMyAdmin_x.x.x.tar.gz in your
88 webserver's document root. If you don't have direct access to your
89 document root, put the files in a directory on your local machine,
90 and, after step 3, transfer the directory on your web server
91 using, for example, ftp.
92 3. Open the file config.inc.php3 in your favourite editor and change
93 the values for host, user, password and authentication mode to fit
94 your environment. Also insert the correct value for
95 $cfg['PmaAbsoluteUri']. Have a look at Configuration section for
96 an explanation of all values.
97 4. It is recommended that you protect the directory in which you
98 installed phpMyAdmin (unless it's on a closed intranet, or you
99 wish to use http or cookie authentication), for example with
100 HTTP-AUTH (in a .htaccess file). See the FAQ section for
101 additional information.
102 5. Open the file <www.your-host.com>/<your-install-dir>/index.php3 in
103 your browser. phpMyAdmin should now display a welcome screen and
104 your databases, or a login dialog if using http or cookie
107 Upgrading from an older version:
108 * Please do not copy your older config.inc.php3 over the new one: it
109 may offer new configuration variables, and the new version may
110 depend on these for normal behavior. It is suggested instead to
111 insert your site values in the new one.
113 Using authentication modes:
114 * Http and cookie authentication modes are recommended in a
115 multi-user environment where you want to give users access to
116 their own database and don't want them to play around with others.
117 Nevertheless be aware that MS Internet Explorer seems to be really
118 buggy about cookies, at least till version 6. And php 4.1.1 is
119 also a bit buggy in this area!
120 Even in a single-user environment, you might prefer to use http or
121 cookie mode so that your user/password pair are not in clear in
122 the configuration file.
123 * Http and cookie authentication modes are more secure: the MySQL
124 password does not need to be set in the phpMyAdmin configuration
125 file (except for the "controluser" -see the Configuration
127 However, keep in mind that the password travels in plain text,
128 unless you are using the https protocol.
129 In cookie mode, we send the password in a temporary cookie, so
130 most browsers should not store the password in their cookie file.
131 * For 'http' and 'cookie' modes, phpMyAdmin needs a controluser that
132 has only the SELECT privilege on the mysql.user (all columns
133 except "Password"), mysql.db (all columns) & mysql.tables_priv
134 (all columns except "Grantor" & "Timestamp") tables.
135 You must specify the details for the controluser in the
136 config.inc.php3 file under the $cfg['Servers'][$i]['controluser']&
137 $cfg['Servers'][$i]['controlpass'] settings.
138 This example assumes you want to use pma as the controluser and
139 pmapass as the controlpass, but this is only an example: use
140 something else in your file:
142 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY
144 GRANT SELECT (Host, User, Select_priv, Insert_priv, Update_priv,
145 Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv,
146 Process_priv, File_priv, Grant_priv, References_priv, Index_priv,
147 Alter_priv) ON mysql.user TO 'pma'@'localhost';
148 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
149 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv) ON
150 mysql.tables_priv TO 'pma'@'localhost';
151 ... and if you want to use the many new relation and bookmark
153 GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db> TO
154 'pma'@'localhost'; (this of course requires you to have a special DB
155 for phpMyAdmin, the contents will be explained later)
156 * Then each of the true users should be granted a set of privileges
157 on a set of particular databases. Normally you shouldn't give
158 global privileges to an ordinary user, unless you understand the
159 impact of those privileges (for example, you are creating a
161 For example, to grant the user real_user with all privileges on
162 the database user_base:
163 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost
164 IDENTIFIED BY 'real_password';
165 What the user may now do is controlled entirely by the MySQL user
167 With http or cookie auth mode, you don't need to fill the
168 user/password fields inside the $cfg['Servers'] array.
170 'http' authentication mode:
171 * Was called 'advanced' in versions before 2.2.3.
172 * Introduced in 1.3.0, it uses Basic HTTP authentication method and
173 allows you to login as any valid MySQL user.
174 * Is only supported with PHP running as an Apache module, not with
177 'cookie' authentication mode:
178 * You can use this method as a replacement for the http
179 authentication (for example, if you're running IIS).
180 * Obviously, the user must enable cookies in the browser.
181 * With this mode, the use can truly logout of phpMyAdmin and login
182 back with the same username.
184 'config' authentication mode:
185 * This mode is the less secure one because it requires you to fill
186 the $cfg['Servers'][$i]['user'] and
187 $cfg['Servers'][$i]['password'] fields.
188 But you don't need to setup a "controluser" here: using the
189 $cfg['Servers'][$i]['only_db'] might be enough.
190 * In the ISP FAQ section, there is an entry explaining how to
191 protect your configuration file.
192 * For additional security in this mode, you may wish to consider the
193 Host authentication $cfg['Servers'][$i]['AllowDeny']['order'] and
194 $cfg['Servers'][$i]['AllowDeny']['rules'] configuration
196 ______________________________________________________________________
198 Top - Requirements - Introduction - Installation -
199 Configuration - FAQ - Developers - Credits
200 ______________________________________________________________________
204 Warning for Mac users: php seems not to like Mac end of lines
205 character ("\r"). So ensure you choose the option that allows to use
206 the *nix end of line character ("\n") in your text editor before
207 registering a script you have modified.
209 All configurable data is placed in config.inc.php3.
211 $cfg['PmaAbsoluteUri'] string
212 Sets here the complete url (with full path) to your phpMyAdmin
214 http://www.your_web.net/path_to_your_phpMyAdmin_directory/.
215 phpMyAdmin needs this setting, because of requirements of the
216 HTTP protocol, explained in RFC2616, section 14.30.
217 Don't forget the slash at the end of your url. The url must
218 contain characters that are valid for a url, and on some
219 servers, the path is case-sensitive.
220 Starting with version 2.3.0, you can try to leave this
221 parameter empty, because the program tries to auto-detect its
222 proper value. Additional details are in the configuration file.
223 Alternatively, this setting can be dynamically completed. For
224 example, you can try to use such a kind of code:
226 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
227 . $_SERVER['HTTP_HOST']
228 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SER
230 . substr($_SERVER['PHP_SELF'], 0, strrpos($_SERVER['PHP_
235 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
236 . $_SERVER['SERVER_NAME']
237 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SER
239 . substr($_SERVER['SCRIPT_NAME'], 0, strrpos($_SERVER['S
240 CRIPT_NAME'], '/')+1);
243 Please note that the $_SERVER array doesn't exist in
244 PHP < 4.1.0. Try to replace $_SERVER by $HTTP_SERVER_VARS or
245 $GLOBALS in this case.
247 $cfg['PmaAbsoluteUri_DisableWarning'] boolean
248 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and
249 the system detects your absolute URI automatically, we display
250 a warning to remind you. If you have tested the automatic
251 detection, and it works perfectly for your setup, then you can
252 set this variable to squelch the warning.
254 $cfg['PmaNoRelation_DisableWarning'] boolean
255 Starting with version 2.3.0 phpMyAdmin offers a lot of features
256 to work with master / foreign - tables (see
257 $cfg['Servers'][$i]['pmadb']).
258 If you tried to set this up and it does not work for you, have
259 a look on the "Structure" page of one database where you would
260 like to use it. You will find a link that will analyze why
261 those features have been disabled.
262 If you do not want to use those features set this variable to
263 TRUE to stop this message from appearing.
265 $cfg['Servers'] array
266 Since version 1.4.2, phpMyAdmin supports the administration of
267 multiple MySQL servers. Therefore, a $cfg['Servers']-array has
268 been added which contains the login information for the
269 different servers. The first $cfg['Servers'][$i]['host']
270 contains the hostname of the first server, the second
271 $cfg['Servers'][$i]['host'] the hostname of the second server,
272 etc. If you have only one server to administer, simply leave
273 free the hostname of the other $cfg['Server']-entries.
275 $cfg['Servers'][$i]['host'] string
276 The hostname of your $i-th MySQL-server. E.g. localhost.
278 $cfg['Servers'][$i]['port'] string
279 The port-number of your $i-th MySQL-server. Default is 3306
282 $cfg['Servers'][$i]['socket'] string
283 The path to the socket to use. Leave blank for default.
284 To use the socket feature you must run php 3.0.10 or more.
286 $cfg['Servers'][$i]['connect_type'] string
287 What type connection to use with the MySQL server. Your options
288 are 'socket' & 'tcp'. It defaults to 'tcp' as that is nearly
289 guarenteed to be available on all MySQL servers, while sockets
290 are not supported on some platforms.
292 $cfg['Servers'][$i]['controluser'] string
293 $cfg['Servers'][$i]['controlpass'] string
294 When using http or cookie authentication modes (or 'config'
295 authentication mode since phpMyAdmin 2.2.1), you need to supply
296 the details of a MySQL account that has SELECT privilege on the
297 mysql.user (all columns except "Password"), mysql.db (all
298 columns) & mysql.tables_priv (all columns except "Grantor" &
299 "Timestamp") tables. This account is used to check what
300 databases the user will see at login.
301 Please see the install section on "Using http authentication"
302 for more information.
303 Note that if you try login to phpMyAdmin with this
304 "controluser", you could get some errors, depending the exact
305 privileges you gave to the "controluser". phpMyAdmin does not
306 support a direct login with the "controluser".
307 In versions before 2.2.5, those were called "stduser/stdpass".
309 $cfg['Servers'][$i]['auth_type'] string ['http'|'cookie'|'config']
310 Whether config or cookie or http authentication should be used
313 + 'config' authentication ($auth_type = 'config') is the plain
314 old way: username and password are stored in config.inc.php3.
315 + 'cookie' authentication mode ($auth_type = 'cookie') as
316 introduced in 2.2.3 allows you to log in as any valid MySQL
317 user with the help of... cookies. Log name and password are
318 stored in cookies during the session and password is deleted
320 + 'http' authentication (was called 'advanced' in older
321 versions) ($auth_type = 'http') as introduced in 1.3.0 allows
322 you to log in as any valid MySQL user via HTTP-Auth.
324 Please see the install section on "Using authentication modes"
325 for more information.
327 $cfg['Servers'][$i]['user'] string
328 $cfg['Servers'][$i]['password'] string
329 The user/password-pair which phpMyAdmin will use to connect to
330 this MySQL-server. This user/password pair is not needed when
331 http or cookie authentication is used, and should be empty.
333 $cfg['Servers'][$i]['only_db'] string or array
334 If set to a(an array of) database name(s), only this(these)
335 database(s) will be shown to the user. Since phpMyAdmin 2.2.1,
336 this/these database(s) name(s) may contain MySQL wilcards
337 characters ("_" and "%"): if you want to use literal instances
338 of these characters, escape them (ie use 'my\_db' and not
340 This setting is an efficient way to lower the server charge
341 since the latter does not need to send MySQL requests to build
342 the available database list. But it does not replace the
343 privileges rules of the MySQL database server. If set, it just
344 means only these databases will be displayed but not at all
345 other databases can't be used.
347 $cfg['Servers'][$i]['verbose'] string
348 Only useful when using phpMyAdmin with multiple server entries.
349 If set, this string will be displayed instead of the hostname
350 in the pulldown menu on the main page. This can be useful if
351 you want to show only certain databases on your system, for
354 $cfg['Servers'][$i]['pmadb'] string
355 Starting with version 2.3.0 phpMyAdmin offers a lot of features
356 to work with master / foreign - tables. To use those as well as
357 the bookmark feature you need special tables with a predefined
358 structure, which we explain below.
359 If you are the only user of this phpMyAdmin installation, you
360 can use your current database to store those special tables; in
361 this case, just put your current database name in
362 $cfg['Servers'][$i]['pmadb'].
363 If you are setting up a multi-user phpMyAdmin installation, you
364 will need to create a new db and setup special privileges, so,
367 + create a new database for phpmyadmin:
368 CREATE DATABASE phpmyadmin;
369 Note that "controluser" must have SELECT, INSERT, UPDATE and
370 DELETE privileges on this database. Here is a query to set up
371 those privileges (using "phpmyadmin" as the database name,
372 and "pma" as the controluser):
373 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to
375 do not give any other user rights on this database.
376 + enter the databasename in $cfg['Servers'][$i]['pmadb']
378 $cfg['Servers'][$i]['bookmarktable'] string
379 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This
380 can be useful for queries you often run.
381 To allow the usage of this functionality you have to:
383 + set up "pmadb" as described above
384 + within this database create a table following this scheme:
385 CREATE TABLE `PMA_bookmark` (
386 id int(11) DEFAULT '0' NOT NULL auto_increment,
387 dbase varchar(255) NOT NULL,
388 user varchar(255) NOT NULL,
389 label varchar(255) NOT NULL,
392 ) TYPE=MyISAM COMMENT='Bookmarks';
393 + enter the tablename in $cfg['Servers'][$i]['bookmarktable']
395 $cfg['Servers'][$i]['relation'] string
396 Since release 2.2.4 you can describe, in a special 'relation'
397 table, which field is a key in another table (a foreign key).
398 phpMyAdmin currently uses this to
400 + make clickable, when you browse the master table, the data
401 values that point to the foreign table;
402 + display in an optional tooltip the "display field" when
403 browsing the master table, if you move the mouse to a column
404 containing a foreign key (use also the 'table_info' table);
405 + display links on the table properties page, to check
406 referential integrity (display missing foreign keys) for each
408 + in query-by-example, create automatic joins (see an example
409 in the FAQ, section "Using phpMyAdmin");
410 + enable you to get a PDF schema of your database (also uses
411 the table_coords table).
413 The keys can be numeric or character.
414 To allow the usage of this functionality the superuser has to:
416 + set up "pmadb" as described above
417 + within this database create a table following this scheme:
418 CREATE TABLE `PMA_relation` (
419 `master_db` varchar(64) NOT NULL default '',
420 `master_table` varchar(64) NOT NULL default '',
421 `master_field` varchar(64) NOT NULL default '',
422 `foreign_db` varchar(64) NOT NULL default '',
423 `foreign_table` varchar(64) NOT NULL default '',
424 `foreign_field` varchar(64) NOT NULL default '',
425 PRIMARY KEY (`master_db`, `master_table`,
427 KEY foreign_field (foreign_db, foreign_table)
428 ) TYPE=MyISAM COMMENT='Relation table';
429 + put the relation table name in
430 $cfg['Servers'][$i]['relation']
431 + now as normal user open phpMyAdmin and for each one of your
432 tables where you want to use this feature, click
433 "Structure/Relation view/" and choose foreign fields.
435 Please note that in the current (2.3.0) version, master_db must
436 be the same as foreign_db. Those fields have been put in future
437 development of the cross-db relations.
439 $cfg['Servers'][$i]['table_info'] string
440 Since release 2.3.0 you can describe, in a special 'table_info'
441 table, which field is to be displayed as a tooltip when moving
442 the cursor over the corresponding key.
443 This configuration variable will hold the name of this special
444 table. To allow the usage of this functionality the superuser
447 + set up "pmadb" as described above
448 + within this database create a table following this scheme:
449 CREATE TABLE `PMA_table_info` (
450 `db_name` varchar(64) NOT NULL default '',
451 `table_name` varchar(64) NOT NULL default '',
452 `display_field` varchar(64) NOT NULL default '',
453 PRIMARY KEY (`db_name`, `table_name`)
454 ) TYPE=MyISAM COMMENT='Table information for
456 + put the table name in $cfg['Servers'][$i]['table_info']
457 + then for each table where you want to use this feature, click
458 "Structure/Relation view/Choose field to display" to choose
461 Usage tip: Display field.
463 $cfg['Servers'][$i]['table_coords'] string
464 $cfg['Servers'][$i]['pdf_pages'] string
465 Since release 2.3.0 you can have phpMyAdmin create PDF pages
466 showing the relations between your tables. To do this it needs
467 two tables "pdf_pages" (storing information about the available
468 pdf pages) and "table_coords" (storing coordinates where each
469 table will be placed on a PDF schema output).
470 You must be using the "relation" feature and have a table of
471 PDF pages (see $cfg['Servers'][$i]['pdf_pages']) to create PDF
473 To allow the usage of this functionality the superuser has to:
475 + set up "pmadb" as described above
476 + within this database create a table following this scheme:
477 CREATE TABLE `PMA_table_coords` (
478 `db_name` varchar(64) NOT NULL default '',
479 `table_name` varchar(64) NOT NULL default '',
480 `pdf_page_number` int NOT NULL default '0',
481 `x` float unsigned NOT NULL default '0',
482 `y` float unsigned NOT NULL default '0',
483 PRIMARY KEY (`db_name`, `table_name`,
485 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin
487 + also within this database create:
488 CREATE TABLE `PMA_pdf_pages` (
489 `db_name` varchar(64) NOT NULL default '',
490 `page_nr` int(10) unsigned NOT NULL auto_increment,
491 `page_descr` varchar(50) NOT NULL default '',
492 PRIMARY KEY (page_nr),
494 ) TYPE=MyISAM COMMENT='PDF Relationpages for PMA';
495 + put the first table name in
496 $cfg['Servers'][$i]['table_coords'] and the second table name
497 in $cfg['Servers'][$i]['pdf_pages']
499 Usage tips: PDF output.
501 $cfg['Servers'][$i]['column_comments'] string
502 Since release 2.3.0 you can store comments to describe each
503 column for each table. These will then be shown on the
505 To allow the usage of this functionality the superuser has to:
507 + set up "pmadb" as described above
508 + within this database create a table following this scheme:
509 CREATE TABLE `PMA_column_comments` (
510 id int(5) unsigned NOT NULL auto_increment,
511 db_name varchar(64) NOT NULL default '',
512 table_name varchar(64) NOT NULL default '',
513 column_name varchar(64) NOT NULL default '',
514 comment varchar(255) NOT NULL default '',
516 UNIQUE KEY db_name (db_name, table_name, column_name)
517 ) TYPE=MyISAM COMMENT='Comments for Columns';
518 + put the table name in $cfg['Servers'][$i]['column_comments']
520 $cfg['Servers'][$i]['AllowDeny']['order'] string
521 If your rule order is empty, then IP authentication is
523 If your rule order is set to 'deny,allow' then the system
524 applies all deny rules followed by allow rules. Access is
525 allowed by default. Any client which does not match a Deny
526 command or does match an Allow command will be allowed access
528 If your rule order is set to 'allow,deny' then the system
529 applies all allow rules followed by deny rules. Access is
530 denied by default. Any client which does not match an Allow
531 directive or does match a Deny directive will be denied access
533 If your rule order is set to 'explicit', the authentication is
534 performed in a similar fashion to rule order 'deny,allow', with
535 the added restriction that your host/username combination must
536 be listed in the allow rules, and not listed in the deny rules.
537 This is the most secure means of using Allow/Deny rules, and
538 was available in Apache by specifying allow and deny rules
539 without setting any order.
541 $cfg['Servers'][$i]['AllowDeny']['rules'] array of strings
542 The general format for the rules is as such:
543 <'allow' | 'deny'> <username> [from] <ipmask>
544 If you wish to match all users, it is possible to use a '%' as
545 a wildcard in the username field.
546 There are a few shortcuts you can use in the ipmask field as
549 'localhost' -> 127.0.0.1/8
550 Having an empty rule list is equivalent to either using 'allow
551 % from all' if your rule order is set to 'deny,allow' or 'deny
552 % from all' if your rule order is set to 'allow,deny' or
554 For the IP matching system, the following work:
555 xxx.xxx.xxx.xxx (an exact IP address)
556 xxx.xxx.xxx.[yyy-zzz] (an IP address range)
557 xxx.xxx.xxx.xxx/nn (CIDR, Classless Inter-Domain Routing type
559 But the following does not work:
560 xxx.xxx.xxx.xx[yyy-zzz] (partial IP address range)
562 $cfg['ServerDefault'] integer
563 If you have more than one server configured, you can set
564 $cfg['ServerDefault'] to any one of them to autoconnect to that
565 server when phpMyAdmin is started, or set it to 0 to be given a
566 list of servers without logging in.
567 If you have only one server configured, $cfg['ServerDefault']
568 MUST be set to that server.
570 $cfg['OBGzip'] boolean
571 Defines whether to use gzip output buffering for increased
572 speed in HTTP transfers.
574 $cfg['PersistentConnections'] boolean
575 Whether persistent connections should be used or not
576 (mysql_connect or mysql_pconnect).
578 $cfg['ExecTimeLimit'] integer [number of seconds]
579 Set the number of seconds a script is allowed to run. If
580 seconds is set to zero, no time limit is imposed.
581 This setting is used while importing/exporting dump files but
582 has no effect when PHP is running in safe mode.
584 $cfg['SkipLockedTables'] boolean
585 Mark used tables and make it possible to show databases with
586 locked tables (since 3.23.30).
588 $cfg['ShowSQL'] boolean
589 Defines whether sql-queries generated by phpMyAdmin should be
592 $cfg['AllowUserDropDatabase'] boolean
593 Defines whether normal users (non-administrator) are allowed to
594 delete their own database or not. If set as FALSE, the link
595 "Drop Database" will not be shown, and even a "DROP DATABASE
596 mydatabase" will be rejected. Quite practical for ISP's with
599 $cfg['Confirm'] boolean
600 Whether a warning ("Are your really sure..") should be
601 displayed when you're about to loose data.
603 $cfg['LoginCookieRecall'] boolean
604 Define whether the previous login should be recalled or not in
605 cookie authentication mode.
607 $cfg['UseDbSearch'] boolean
608 Define whether the "search string inside database" is enabled
611 $cfg['LeftFrameLight'] boolean
612 Defines whether to use select-based menu and display only the
613 current tables in the left frame (smaller page).
615 $cfg['ShowTooltip'] boolean
616 Defines whether to display table comment as tooltip in left
619 $cfg['ShowStats'] boolean
620 Defines whether to display space usage and statistics about
621 databases and tables or not.
622 Note that statistics requires at least MySQL 3.23.3 and that,
623 at this date, MySQL doesn't return such information for
626 $cfg['ShowMysqlInfo'] boolean
627 $cfg['ShowMysqlVars'] boolean
628 $cfg['ShowPhpInfo'] boolean
629 $cfg['ShowChgPassword'] boolean
630 Defines whether to display the "MySQL runtime information",
631 "MySQL system variables", "PHP information" and "Change
632 password " links or not for simple users at the starting main
633 (right) frame. This setting does not check MySQL commands
635 Please note that to block the usage of phpinfo() in scripts,
636 you have to put this in your php.ini:
637 disable_functions = phpinfo()
638 Also note that enabling the "Change password " link has no
639 effect with "config" authentication mode: because of the hard
640 coded password value in the configuration file, end users can't
641 be allowed to change their passwords.
643 $cfg['SuggestDBName'] boolean
644 Defines whether to suggest a database name on the "Create
645 Database" form or to keep the textfield empty.
647 $cfg['ShowBlob'] boolean
648 Defines whether BLOB fields are shown when browsing a table's
651 $cfg['NavigationBarIconic'] boolean
652 Defines whether navigation bar buttons contain text or symbols
655 $cfg['ShowAll'] boolean
656 Defines whether an user should be displayed a "show all
657 (records)" button in browse mode or not.
659 $cfg['MaxRows'] integer
660 Number of rows displayed when browsing a resultset. If the
661 resultset contains more rows, Previous/Next links will be
664 $cfg['Order'] string [DESC|ASC|SMART]
665 Defines whether fields are displayed in ascending (ASC) order,
666 in descending (DESC) order or in a "smart" (SMART) order -ie
667 descending order for fields of type TIME, DATE, DATETIME &
668 TIMESTAMP, ascending order else- by default.
670 $cfg['ProtectBinary'] boolean or string
671 Defines whether BLOB or BINARY fields are protected from
672 edition when browsing a table's content or not. Valid values
674 - FALSE to allow edition of all fields;
675 - blob to allow edition of all fields except BLOBS;
676 - all to disallow edition of all BINARY or BLOB fields.
678 $cfg['ShowFunctionFields'] boolean
679 Defines whether MySQL functions fields should be displayed or
680 not in edit/insert mode.
682 $cfg['CharEditing'] string
683 Defines which type of editing controls should be used for CHAR
684 and VARCHAR fields. Possible values are:
686 + input - this allows to limit size of text to size of field in
687 MySQL, but has problems with newlines in fields
688 + textarea - no problems with newlines in fields, but also no
691 Default is old behavior so input.
693 $cfg['ZipDump'] boolean
694 $cfg['GZipDump'] boolean
695 $cfg['BZipDump'] boolean
696 Defines whether to allow the use of zip/gzip/bzip compression
697 when creating a dump file or not.
699 $cfg['DefaultTabDatabase'] string
700 Defines the tab displayed by default on database view. Possible
701 values: "db_details_structure.php3", "db_details.php3" or
704 $cfg['DefaultTabTable'] string
705 Defines the tab displayed by default on table view. Possible
706 values: "tbl_properties_structure.php3", "tbl_properties.php3",
707 "tbl_select.php3" or "tbl_change.php3".
709 $cfg['MySQLManualBase'] string
710 If set to an URL which points to the MySQL documentation (type
711 depends on $cfg['MySQLManualType']), appropriate help links are
713 See MySQL Documentation page for more information about MySQL
714 manuals and their types.
716 $cfg['MySQLManualType'] string
717 Type of MySQL documentation:
719 + old - old style used in phpMyAdmin 2.3.0 and sooner
720 + searchable - "Searchable, with user comments"
721 + chapters - "HTML, one page per chapter"
722 + big - "HTML, all on one page"
723 + none - do not show documentation links
725 $cfg['DefaultLang'] string
726 Defines the default language to use, if not browser-defined or
728 See the select_lang.inc.php3 script to know the valid values
732 Force: always use this language (must be defined in the
733 select_lang.inc.php3 script).
735 $cfg['DefaultCharset'] string
736 Default charset to use for recoding of MySQL queries. This must
737 be enabled and it's described by $cfg['AllowAnywhereRecoding']
739 You can give here any charset which is in
740 $cfg['AvailableCharsets'] array and this is just default
741 choice, user can select any of them.
743 $cfg['AllowAnywhereRecoding'] boolean
744 Allow charset recoding of MySQL queries. You need recode or
745 iconv support (compiled in or module) in php to allow MySQL
746 queries recoding and used language file must have it enabled
747 (by default only these which are in unicode, just to avoid
748 losing some characters).
750 $cfg['RecodingEngine'] string
751 You can select here which functions will be used for charset
752 conversion. Possible values are:
754 + auto - automatically use available one (first is tested
756 + iconv - use iconv or libiconv functions
757 + recode - use recode_string function
761 $cfg['AvailableCharsets'] array
762 Available charsets for MySQL conversion. You can add your own
763 (any of supported by recode/iconv) or remove these which you
764 don't use. Charsets will be shown in same order as here listed,
765 so if you frequently use some of these move them to the top.
767 $cfg['LeftWidth'] integer
768 Left frame width in pixel.
770 $cfg['LeftBgColor'] string [HTML color]
771 $cfg['RightBgColor'] string [HTML color]
772 The background colors (HTML) used for both the frames.
774 $cfg['RightBgImage'] string
775 The URI of the background image used for the right frame. It
776 can be absolute as well as relative from your phpMyAdmin
779 $cfg['LeftPointerColor'] string [HTML color]
780 The color (HTML) used for the pointer in the left frame (does
783 $cfg['Border'] integer
784 The size of a table's border.
786 $cfg['ThBgcolor'] string [HTML color]
787 The color (HTML) used for table headers.
789 $cfg['BgcolorOne'] string [HTML color]
790 The color (HTML) #1 for table rows.
792 $cfg['BgcolorTwo'] string [HTML color]
793 The color (HTML) #2 for table rows.
795 $cfg['BrowsePointerColor'] string [HTML color]
796 $cfg['BrowseMarkerColor'] string [HTML color]
797 The colors (HTML) uses for the pointer and the marker in browse
798 mode (does not work with NS4).
799 The former feature highlights the row over which your mouse is
800 passing and the latter lets you visually mark/unmark rows by
802 You can disable both of these features by emptying the
803 respective directive.
805 $cfg['TextareaCols'] integer
806 $cfg['TextareaRows'] integer
807 $cfg['CharTextareaCols'] integer
808 $cfg['CharTextareaRows'] integer
809 Number of columns and rows for the textareas.
810 This value will be emphasized (*2) for sql query textareas.
811 The Char* values are used for CHAR and VARCHAR editing (if
812 configured via $cfg['CharEditing']).
814 $cfg['TextareaAutoSelect'] boolean
815 Defines if the whole textarea of the query box will be selected
818 $cfg['LimitChars'] integer
819 Maximal number of Chars showed in a TEXT OR a BLOB field on
820 browse view. Can be turned off by a toggle button on the browse
823 $cfg['ModifyDeleteAtLeft'] boolean
824 $cfg['ModifyDeleteAtRight'] boolean
825 Defines the place where modify and delete links would be put
826 when tables contents are displayed (you may have them displayed
827 both at the left and at the right). "Left" and "right" are
828 parsed as "top" and "bottom" with vertical display mode.
830 $cfg['DefaultDisplay'] string
831 There are 2 display modes: horizontal and vertical. Define
832 which one is displayed by default.
834 $cfg['UploadDir'] string
835 The name of the directory, ending with a slash, where SQL files
836 have been uploaded by other means than phpMyAdmin (for example,
837 ftp). Those files are available under a drop-down box when you
838 click the database name, then the SQL tab.
839 Please note that the file names must have the suffix ".sql".
840 This feature is useful when your file is too big to be uploaded
841 via HTTP, or when file uploads are disabled in PHP.
842 Please note that if PHP is running in safe mode, this directory
843 must be owned by the same user as the owner of the phpMyAdmin
846 $cfg['RepeatCells'] integer
847 Repeat the headers every X cells, or 0 to deactivate.
849 $cfg['SQP']['enable'] boolean
850 As of phpMyAdmin 2.3.0, we now have a fully functional SQL
851 Parser system. It is enabled by default, as it is used to
852 format the SQL queries.
853 As of 2.3.1, it will become an integral part of phpMyAdmin, as
854 it will analyze certain queries to improve the behavior of
855 phpMyAdmin. But as it is very new, and not yet heavily used, we
856 offer you an option to turn it off.
858 $cfg['SQP']['fmtType'] string [html|none]
859 The main use of the new SQL Parser is to pretty-print SQL
860 queries. By default we use HTML to format the query, but you
861 can disable this by setting this varible to 'none'
863 $cfg['SQP']['fmtInd'] float
864 $cfg['SQP']['fmtIndUnit'] string [em|px|pt|ex]
865 For the pretty-printing of SQL queries, under some cases the
866 part of a query inside a bracket is indented. By changing
867 $cfg['SQP']['fmtInd'] you can change the amount of this indent.
868 Related in purpose is $cfg['SQP']['fmtIndUnit'] which specifies
869 the units of the indent amount that you specified. This is used
872 $cfg['SQP']['fmtColor'] array of string tuples
873 This array is used to define the colours for each type of
874 element of the pretty-printed SQL queries. The tuple format is
875 class => [HTML colour code | empty string]
876 If you specify an empty string for the color of a class, it is
877 ignored in creating the stylesheet. You should not alter the
878 class names, only the colour strings.
881 + comment Applies to all comment sub-classes
882 + comment_mysql Comments as "#...\n"
883 + comment_ansi Comments as "-- ...\n"
884 + comment_c Comments as "/*...*/"
885 + digit Applies to all digit sub-classes
886 + digit_hex Hexadecimal numbers
887 + digit_integer Integer numbers
888 + digit_float Floating point numbers
889 + punct Applies to all punctuation sub-classes
890 + punct_bracket_open_round Opening brackets"("
891 + punct_bracket_close_round Closing brackets ")"
892 + punct_listsep List item seperator ","
893 + punct_qualifier Table/Column Qualifer "."
894 + punct_queryend End of query marker ";"
895 + alpha Applies to all alphabetic classes
896 + alpha_columnType Identifers matching a column type
897 + alpha_columnAttrib Identifers matching a
898 database/table/column attribute
899 + alpha_functionName Identifiers matching a MySQL function name
900 + alpha_reservedWord Identifiers matching any other reserved
902 + alpha_variable Identifers matching a SQL variable "@foo"
903 + alpha_identifier All other identifiers
904 + quote Applies to all quotation mark classes
905 + quote_double Double quotes "
906 + quote_single Single quotes '
907 + quote_backtick Backtick quotes `
909 $cfg['SQLValidator']['use'] boolean
910 phpMyAdmin now supports use of the Mimer SQL Validator service,
911 as originally published on Slashdot.
912 For help in setting up your system to use the service, see the
915 $cfg['SQLValidator']['username'] string
916 $cfg['SQLValidator']['password'] string
917 The SOAP service allows you to login with anonymous and any
918 password, so we use those by default.. Instead, if you have an
919 account with them, you can put your login details here, and it
920 will be used in place of the anonymous login.
922 $cfg['ColumnTypes'] array
923 All possible types of a MySQL column. In most cases you don't
926 $cfg['AttributeTypes'] array
927 Possible attributes for fields. In most cases you don't need to
930 $cfg['Functions'] array
931 A list of functions MySQL supports. In most cases you don't
933 ______________________________________________________________________
935 Top - Requirements - Introduction - Installation -
936 Configuration - FAQ - Developers - Credits
937 ______________________________________________________________________
939 FAQ - Frequently Asked Questions
941 Server - Configuration - Limitations - Multi-user - Browsers
942 - Usage tips - Project
946 [1.1] I'm running php 4+ and my server is crashing each time a
947 specific action is required or phpMyAdmin sends a blank page or a page
948 full of cryptic characters to my browser, what can I do?
949 There are some known php bugs with output buffering and compression.
950 Try to set the $cfg['OBGzip'] directive to FALSE in your
951 config.inc.php or .php3 file and the zlib.output_compression directive
952 to Off in your php configuration file.
953 Furthermore, we know about such problems connected to the release
954 candidates of php 4.2.0 (tested with php 4.2.0 RC1 to RC4) together
955 with MS Internet Explorer. Please upgrade to the release version php
958 [1.2] My Apache server crashes when using phpMyAdmin.
959 You should first try the latest versions of Apache (and possibly
961 See also the other FAQ entry about php bugs with output buffering.
962 If your server keeps crashing, please ask for help in the various
963 Apache support groups.
965 [1.3] I'm running phpMyAdmin with "cookie" authentication mode under
966 PHP 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the
967 script: I'm always displayed the login screen.
968 This is a known PHP bug (see this bug report) from the official php
969 bug database. It means there is and won't be any phpMyAdmin fix
970 against it because there is no way to code a fix.
972 [1.4] Using phpMyAdmin on IIS, I'm displayed the error message: "The
973 specified CGI application misbehaved by not returning a complete set
975 You just forgot to read the install.txt file from the php
976 distribution. Have a look at the last message in this bug report from
977 the official php bug database.
979 [1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
980 messages with the http or advanced authentication mode.
981 This is a known problem with the php ISAPI filter: it's not so stable.
982 For some more information and complete testings see the messages
983 posted by André B. aka "djdeluxe76" in this thread from the phpWizard
985 Please use instead the cookie authentication mode.
987 [1.6] I can't use phpMyAdmin on PWS: nothing is displayed!
988 This seems to be a PWS bug. Filippo Simoncini found a workaroud (at
989 this time there is no better fix): remove or comment the DOCTYPE
990 declarations (2 lines) from the scripts header.inc.php3,
991 header_printview.inc.php3, index.php3, left.php3 and
992 libraries/common.lib.php3.
994 [1.7] How can I GZip or Bzip a dump or a CSV export. It seems to not
996 These features are based on the gzencode() and bzcompress() php
997 functions to be more independent of the platform (Unix/Windows, Safe
998 Mode or not, and so on). So, you must have PHP4 >= 4.0.4 and
999 Zlib/Bzip2 support (--with-zlib and --with-bz2).
1000 We faced php crashes when trying to download a dump with MS Internet
1001 Explorer when phpMyAdmin is run with a release candidate of php 4.2.0.
1002 In this case you should switch to the release version of php 4.2.0.
1004 [1.8] I cannot insert a text file in a table, and I get an error about
1005 safe mode being in effect.
1006 Your uploaded file is saved by PHP in the "upload dir", as defined in
1007 php.ini by the variable upload_tmp_dir (usually the system default is
1009 We recommend the following setup for Apache servers running in safe
1010 mode, to enable uploads of files while being reasonably secure:
1011 * create a separate directory for uploads: mkdir /tmp/php
1012 * give ownership to the Apache server's user.group: chown
1013 apache.apache /tmp/php
1014 * give proper permission: chmod 600 /tmp/php
1015 * put upload_tmp_dir = /tmp/php in php.ini
1018 [1.9] I'm having troubles when uploading files. In general file
1019 uploads don't work on my system and uploaded files have a
1020 Content-Type: header in the first line.
1021 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat
1022 7.0 and you updated your php rpm to php-4.0.4pl1-3.i386.rpm, didn't
1024 So the problem is that this package has a serious bug that was
1025 corrected ages ago in php (2001-01-28: see php's bug tracking system
1026 for more details). The problem is that the bugged package is still
1027 available though it was corrected (see redhat's bugzilla for more
1029 So please download the fixed package (4.0.4pl1-9) and the problem
1031 And that fixes the \r\n problem with file uploads!
1033 [1.10] I'm having troubles when uploading files with phpMyAdmin
1034 running on a secure server. My browser is Internet Explorer and I'm
1035 using the Apache server.
1036 As suggested by "Rob M" in the phpWizard forum, add this line to your
1038 SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
1039 It seems to clear up many problems between IE and SSL.
1041 [1.11] I get an 'open_basedir restriction' while uploading a file from
1043 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
1044 restrictions. Assuming that the restriction allows you to open files
1045 in the current directory ('.'), all you have to do is create a 'tmp'
1046 directory under the phpMyAdmin install directory, with permissions 777
1047 and the same owner as the owner of your phpMyAdmin directory. The
1048 uploaded files will be moved there, and after execution of your SQL
1051 [1.12] I have lost my MySQL root password, what can I do?
1052 The MySql manual explains how to reset the permissions.
1054 [1.13] I get an error 'No SQL query' when trying to execute a
1056 If PHP does not have read/write access to its upload_tmp_dir, it
1057 cannot access the uploaded query.
1059 [1.14] I get an error 'No SQL query' when trying to submit a query
1060 from the convenient text area.
1061 Check the post_max_size directive from your php configuration file and
1064 [1.15] I have problems with mysql.user field names.
1065 In older MySQL versions, the User and Password fields were named user
1066 and password. Please modify your field names to align with current
1069 [1.16] I cannot upload big dump files.
1070 The first things to check (or ask your host provider to check) are the
1071 values of upload_max_filesize, memory_limit and post_max_size in the
1072 php.ini configuration file.
1073 All of these three settings limit the maximum size of data that can be
1074 submitted and handled by php. One user also said that post_max_size
1075 and memory_limit need to be larger than upload_max_filesize.
1077 [1.17] Does phpMyAdmin support MySQL 4?
1078 MySQL 4 is not yet fully supported by phpMyAdmin.
1079 Because of MySQL 4's backwards compatibility you can use phpMyAdmin
1080 for administering MySQL 4 servers, but phpMyAdmin does not yet support
1081 its new features. Please notice that in this case it is recommended to
1082 use php >= 4.1 since older versions of php are not compatible to
1084 Furthermore, several users reported problems with phpMyAdmin related
1085 to bugs in MySQL 4. MySQL 4 is still a beta release and should be used
1086 for test purposes only! Because of a major change in the definition
1087 syntax of string field types, this version of phpMyAdmin probably
1088 won't work correctly with MySQL >= 4.1.0! We will work on the support
1089 as soon as MySQL 4.1.0 is released.
1091 [1.18] I'm running MySQL <= 4.0.1 having lower_case_table_names set to
1092 1. If I create a new table with a capital letter in its name it is
1093 changed to lowercase as it should. But if I try to DROP this table
1094 MySQL is unable to find the corresponding file.
1095 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
1096 MySQL 4.0.2 or turn off your lower_case_table_names directive.
1098 [1.19] I can't run the "display relations" feature because the script
1099 seems not to know the font face I'm using!
1100 The "FPDF" library we're using for this feature requires some special
1101 files to use font faces.
1102 Please refers to the FPDF manual to build these files.
1104 [1.20] I receive the error "cannot load MySQL extension, please check
1106 To connect to a MySQL server, PHP needs a set of MySQL functions
1107 called "MySQL extension". This extension may be part of the PHP server
1108 (compiled-in), otherwise it needs to be loaded dynamically. Its name
1109 is probably mysql.so or mysql.dll. phpMyAdmin tried to load the
1110 extension but failed.
1111 Usually, the problem is solved by installing a software package called
1112 "PHP-MySQL" or something similar.
1114 [1.21] I am running the CGI version of PHP under Unix, and I cannot
1115 login using cookie auth.
1116 In php.ini, set mysql.max_links higher than 1.
1118 [1.22] I don't see the "Location of text file" field, so I cannot
1120 This is most likely because in php.ini, your file_uploads parameter is
1123 [1.23] I'm running MySQL on a Win32 machine. Each time I create a new
1124 table the table and field names are changed to lowercase!
1125 This happens because the MySQL directive lower_case_table_names
1126 defaults to 1 (ON) in the Win32 version of MySQL. You can change this
1127 behavior by simply changing the directive to 0 (OFF):
1128 Just edit you my.ini file that should be located in your Windows
1129 directory and add the following line:
1130 lower-case-table-names=0
1131 Next, save the file and restart the MySQL service. You can always
1132 check the value of this directive using the query
1133 SHOW VARIABLES LIKE 'lower_case_table_names';
1135 [1.24] Some characters are being truncated in my queries, or I get
1136 characters randomly added. I am running PHP 4.2.3.
1137 This is a PHP 4.2.3 bug.
1139 [1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP, and
1140 I get problems, such as undefined variables when I run a SQL query.
1141 A tip from Jose Fandos: put a comment on the following two lines in
1142 httpd.conf, like this:
1143 # mod_gzip_item_include file \.php$
1144 # mod_gzip_item_include mime "application/x-httpd-php.*"
1145 as this version of mod_gzip on Apache (Windows) has problems handling
1146 php scripts. Of course you have to restart Apache.
1150 [2.1] The error message "Warning: Cannot add header information -
1151 headers already sent by ..." is displayed, what's the problem?
1152 Edit your config.inc.php or .php3 file and ensure there is nothing (ie
1153 no blank lines, no spaces, no characters...) neither before the <?php
1154 tag at the beginning, neither after the ?> tag at the end.
1156 [2.2] phpMyAdmin can't connect to MySQL. What's wrong?
1157 Either there is an error with your PHP setup or your username/password
1158 is wrong. Try to make a small script which uses mysql_connect and see
1159 if it works. If it doesn't, it may be you haven't even compiled MySQL
1162 [2.3] The error message "Warning: MySQL Connection Failed: Can't
1163 connect to local MySQL server through socket '/tmp/mysql.sock'
1164 (111)..." is displayed. What can I do?
1165 For RedHat users, Harald Legner suggests this on the mailing list:
1166 On my RedHat-Box the socket of mysql is /var/lib/mysql/mysql.sock. In
1167 your php.ini you will find a line
1168 mysql.default_socket = /tmp/mysql.sock
1170 mysql.default_socket = /var/lib/mysql/mysql.sock
1171 Then restart apache and it will work.
1172 Here is a fix suggested by Brad Ummer in the phpwizard forum:
1173 * First, you need to determine what socket is being used by MySQL.
1174 To do this, telnet to your server and go to the MySQL bin
1175 directory. In this directory there should be a file named
1176 mysqladmin. Type ./mysqladmin variables, and this should give you
1177 a bunch of info about your MySQL server, including the socket
1178 (/tmp/mysql.sock, for example).
1179 * Then, you need to tell PHP to use this socket.
1180 Assuming you are using PHP 3.0.10 or better, you can specify the
1181 socket to use when you open the connection. To do this in
1182 phpMyAdmin, you need to complete the socket information in the
1184 For example: $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';
1186 Have also a look at the corresponding section of the MySQL
1189 [2.4] Nothing is displayed by my browser when I try to run phpMyAdmin,
1191 Try to set the $cfg['OBGZip'] directive to FALSE in the phpMyAdmin
1192 configuration file. It helps sometime.
1193 Also have a look at your php version number: if it contains "4.0b..."
1194 it means you're running a beta version of PHP. That's not a so good
1195 idea, please upgrade to a plain revision.
1197 [2.5] Each time I want to insert or change a record or drop a database
1198 or a table, an error 404 (page not found) is displayed or, with http
1199 or cookie authentication, I'm asked to login again. What's wrong?
1200 Check the value you set for the $cfg['PmaAbsoluteUri'] directive in
1201 the phpMyAdmin configuration file.
1203 [3. Known limitations]
1205 [3.1] When using http authentication, an user who logged out can not
1206 relog in with the same nick.
1207 This is related to the authentication mechanism (protocol) used by
1208 phpMyAdmin. We plan to change it as soon as we may find enough free
1209 time to do it, but you can bypass this problem: just close all the
1210 opened browser windows and then go back to phpMyAdmin. You should be
1211 able to logs in again.
1213 [3.2] When dumping a large table in compressed mode, I get a memory
1214 limit error or a time limit error.
1215 As of version 2.2.4, we build the compressed dump in memory, so large
1216 tables dumps may hang. The only alternative we can think about (using
1217 system calls to mysqldump then gzip or bzip2) would not be applicable
1218 in environments where PHP is in safe mode: access to system programs
1219 is is limited by the system administrator, and time limit is enforced.
1221 [3.3] With InnoDB tables, I lose foreign key relationships when I
1222 rename or alter a table.
1223 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep
1224 in mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
1226 [3.4] I am unable to import dumps I created with the mysqldump tool
1227 bundled with the MySQL server distribution.
1228 The problem is that mysqldump creates invalid comments like this:
1232 -- Host: localhost Database: database
1233 ---------------------------------------------------------
1234 -- Server version 3.23.54
1236 The invalid part of the code is the horizontal line made of dashes
1237 that appears once in every dump created with mysqldump. If you want to
1238 run your dump you have to turn it into valid MySQL. This means, you
1239 have to add a whitespace after the first to dashes of the line or add
1241 -- -------------------------------------------------------
1243 #---------------------------------------------------------
1245 [4. ISPs, multi-user installations ]
1247 [4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I
1248 need to install it for each customer?
1249 Since version 2.0.3, you can setup a central copy of phpMyAdmin for
1250 all your users. The development of this feature was kindly sponsored
1251 by NetCologne GmbH. This requires a properly setup MySQL user
1252 management and phpMyAdmin http or cookie authentication. See the
1253 install section on "Using http authentication".
1255 [4.2] What's the preferred way of making phpMyAdmin secure against
1257 This depends on your system.
1258 If you're running a server which cannot be accessed by other people,
1259 it's sufficient to use the directory protection bundled with your
1260 webserver (with Apache you can use .htaccess files, for example).
1261 If other people have telnet access to your server, you should use
1262 phpMyAdmin's http authentication feature.
1264 * Your config.inc.php3 file should be chmod 660.
1265 * All your phpMyAdmin files should be chown phpmy.apache, where
1266 phpmy is a user whose password is only known to you, and apache is
1267 the group under which Apache runs.
1268 * You should use PHP safe mode, to protect from other users that try
1269 to include your config.inc.php3 in their scripts.
1271 [4.3] I get errors about not being able to include a file in /lang or
1273 Check php.ini, or ask your sysadmin to check it. The include_path must
1274 contain "." somewhere in it, and open_basedir, if used, must contain
1275 "." and "./lang" to allow normal operation of phpMyAdmin.
1277 [4.4] phpMyAdmin always gives "Access denied" when using http
1279 This could happen for several reasons:
1280 * $cfg['Servers'][$i]['controluser'] and/or
1281 $cfg['Servers'][$i]['controlpass'] are wrong.
1282 * The username/password you specify in the login-dialog are invalid.
1283 * You have already setup a security mechanism for the
1284 phpMyAdmin-directory, eg. a .htaccess file. This would interfere
1285 with phpMyAdmin's authentication, so remove it.
1287 [4.5] Is it possible to let users create their own databases?
1288 Starting with 2.2.5, in the user management page, you can enter a
1289 wildcard database name for a user, and put the privileges you want.
1290 For example, adding SELECT, INSERT, UPDATE, DELETE, CREATE, DROP,
1291 INDEX, ALTER would let a user create/manage his/her database(s).
1293 [4.6] How can I use the Host-based authentication additions?
1294 If you have existing rules from an old .htaccess file, you can take
1295 them and add a username between the 'deny'/'allow' and 'from' strings.
1296 Using the username wildcard of '%' would be a major benefit here if
1297 your installation is suited to using it. Then you can just add those
1298 updated lines into the $cfg['Servers'][$i]['AllowDeny']['rules']
1300 If you want a pre-made sample, you can try this fragment. It stops the
1301 'root' user from logging in from any networks other than the private
1303 //block root from logging in except from the private networks
1304 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
1305 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
1306 'deny root from all',
1307 'allow root from localhost',
1308 'allow root from 10.0.0.0/8',
1309 'allow root from 192.168.0.0/16',
1310 'allow root from 172.16.0.0/12',
1313 [5. Browsers or client OS]
1315 [5.1] I get an out of memory error, and my controls are
1316 non-functional, when trying to create a table with more than 14
1318 We could reproduce this problem only under Win98/98SE. Testing under
1319 WinNT4 or Win2K, we could easily create more than 60 fields.
1320 A workaround is to create a smaller number of fields, then come back
1321 to your table properties and add the other fields.
1323 [5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.
1324 This is not a phpMyAdmin problem but a Xitami known bug: you'll face
1325 it with each script/website that use forms.
1326 Upgrade or downgrade your Xitami server.
1328 [5.3] I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2)
1329 With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except
1330 that the proposed file name for the dump is always 'tbl_dump.php'.
1331 Bzip2 dumps don't seem to work.
1332 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into the
1333 user's temporary directory, so they must be moved before closing
1334 Konqueror, or else they disappear. Gzip dumps give an error message.
1335 Testing needs to be done for Konqueror 2.2.2.
1337 [5.4] I can't use the cookie authentication mode because Internet
1338 Explorer never stores the cookies.
1339 MS Internet Explorer seems to be really buggy about cookies, at least
1340 till version 6. And thanks to Andrew Zivolup we've traced also a php
1341 4.1.1 bug in this area!
1342 Then, if you're running php 4.1.1, try to upgrade or downgrade... it
1345 [5.5] In Internet Explorer 5.0, I get Javascript errors when browsing
1347 Upgrade to at least Internet Explorer 5.5SP2.
1349 [5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying
1350 to modify a row in a table with many fields, or with a text field.
1351 Your table neither have a primary key nor an unique one, so we must
1352 use a long URL to identify this row. There is a limit on the lenght of
1353 the URL in those browsers, and this not happen in Netscape, for
1354 example. The workaround is to create a primary or unique key, or use
1357 [5.7] I refresh (reload) my browser, and come back to the welcome
1359 Some browsers support right-clicking into the frame you want to
1360 refresh, just do this in the right frame.
1362 [5.8] With Mozilla 0.9.7 I have problems sending a query modified in
1364 Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future
1367 [5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
1368 whitespace in the SQL-Query edit area: the page scrolls down.
1369 This is a Mozilla bug (see bug #26882 at Bugzilla).
1371 [5.10] With Netscape 4.75 I get empty rows between each row of data in
1372 a CSV exported file.
1373 This is a known Netscape 4.75 bug: it adds some line feeds when
1374 exporting data in octet-stream mode. Since we can't detect the
1375 specific Netscape version, we cannot workaround this bug.
1377 [5.11] Extended-ASCII characters like German umlauts are displayed
1379 Please ensure that you have set your browser's charset to the one of
1380 the language file you have selected on phpMyAdmin's start page.
1381 Alternatively, you can try the auto detection mode that is supported
1382 by the recent versions of the most browsers.
1384 [6. Using phpMyAdmin]
1386 [6.1] I can't insert new rows into a table / I can't create a table -
1387 MySQL brings up a SQL-error.
1388 Examine the SQL error with care. Often the problem is caused by
1389 specifying a wrong field-type.
1390 Common errors include:
1391 * Using VARCHAR without a size argument
1392 * Using TEXT or BLOB with a size argument
1394 Also, look at the syntax chapter in the MySQL manual to confirm that
1395 your syntax is correct.
1397 [6.2] When I create a table, I click the Index checkbox for 2 fields
1398 and phpMyAdmin generates only one index with those 2 fields.
1399 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a
1400 multi-fields index. If you want two indexes, create the first one when
1401 creating the table, save, then display the table properties and click
1402 the Index link to create the other index.
1404 [6.3] How can I insert a null value into my table?
1405 Since version 2.2.3, you have a checkbox for each field that can be
1406 null. Before 2.2.3, you had to enter "null", without the quotes, as
1409 [6.4] How can I backup my database or table?
1410 Click on a database or table name in the left frame, the properties
1411 will be displayed. Then on the menu, click "Export", you can dump the
1412 structure, the data, or both. This will generate standard SQL
1413 statements that can be used to recreate your database/table.
1414 You will need to choose "Save as file", so that phpMyAdmin can
1415 transmit the resulting dump to your station. Depending on your PHP
1416 configuration, you will see options to compress the dump. See also the
1417 $cfg['ExecTimeLimit'] configuration variable.
1418 For additional help on this subject, look for the word "dump" in this
1421 [6.5] How can I restore (upload) my database or table using a dump?
1422 How can I run a ".sql" file?
1423 Click on a database name in the left frame, the properties will be
1424 local displayed. Then in the "Run SQL query" section, type in your
1425 dump filename, or use the Browse button. Then click Go.
1426 For additional help on this subject, look for the word "upload" in
1429 [6.6] How can I use the relation table in Query-by-example?
1430 Here is an example with the tables persons, towns and countries, all
1431 located in the database mydb. If you don't have a PMA_relation table,
1432 create it as explained in the configuration section. Then create the
1434 CREATE TABLE REL_countries (
1435 country_code char(1) NOT NULL default '',
1436 description varchar(10) NOT NULL default '',
1437 PRIMARY KEY (country_code)
1439 INSERT INTO REL_countries VALUES ('C', 'Canada');
1440 CREATE TABLE REL_persons (
1441 id tinyint(4) NOT NULL auto_increment,
1442 person_name varchar(32) NOT NULL default '',
1443 town_code varchar(5) default '0',
1444 country_code char(1) NOT NULL default '',
1447 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
1448 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
1449 CREATE TABLE REL_towns (
1450 town_code varchar(5) NOT NULL default '0',
1451 description varchar(30) NOT NULL default '',
1452 PRIMARY KEY (town_code)
1454 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
1455 INSERT INTO REL_towns VALUES ('M', 'Montréal');
1456 To setup appropriate links and display information:
1457 * on table "REL_persons" click Structure, then Relation view
1458 * in Links, for "town_code" choose "REL_towns->code"
1459 * in Links, for "country_code" choose "REL_countries->country_code"
1460 * on table "REL_towns" click Structure, then Relation view
1461 * in "Choose field to display", choose "description"
1462 * repeat the two previous steps for table "REL_countries"
1464 Then test like this:
1465 * Click on your db name in the left frame
1467 * Use tables: persons, towns, countries
1468 * Click "Update query"
1469 * In the fields row, choose persons.person_name and click the "Show"
1471 * Do the same for towns.description and countries.descriptions in
1473 * Click "Update query" and you will see in the query box that the
1474 correct joins have been generated
1475 * Click "Submit query"
1477 [6.7] How can I use the "display field" feature?
1478 Starting from the previous example, create the PMA_table_info as
1479 explained in the configuration section, then browse your persons
1480 table, and move the mouse over a town code or country code.
1482 [6.8] How can I produce a PDF schema of my database?
1483 First you have to fill the "relation", "table_coords" and "pdf_pages"
1484 configuration variables.
1485 Then, think about your schema layout: which tables will go on which
1487 * Click on your db name in the left frame
1488 * Choose "Structure" in the navigation on top
1489 * Choose "Edit PDF Pages" which should be somewhere at the bottom of
1491 * Enter the name for a first pdf page and submit
1492 * Choose this page to edit
1493 * Now add a table you want to show on this page and it's coordinates
1495 First you will have to guess this coordinates of course, so just
1496 expect to have an area of about 297 * 210 and put the tables
1497 coordinates somewhere in there, you will be able to have a look at
1498 what happened and change them later.
1499 For example, x=100 and y=200 means that the table will be at 200
1500 mm down and 100 mm right from the upper left corner.
1501 Actually if you have a width of more than 300 or a height of more
1502 than 200 than it will automatically be scaled but 300*100 is a
1503 good start to have an idea of what coordinates to use.
1504 * After every table you submitted you will have the possibility to
1506 * When you have entered enough tables Click on your db name in the
1508 * Now, again at the bottom of the page you should be able to choose
1509 "Display PDF schema"
1510 For testing it might be useful to show the grid as well, so you
1511 can see the coordinates used.
1512 Maybe also choose color and submit.
1513 * Save the file he will offer you to something like Schema.pdf
1514 (Internet Explorer has some bug there which might make it offer it
1515 without an extension. Under Windows it is important to have the
1516 extension ".pdf", under other OSes you should be fine just saving
1517 the file under the name it offers).
1519 [6.9] phpMyAdmin is changing the type of one of my columns!
1520 No, it's MySQL that is doing silent column type changing.
1522 [6.10] My database has an underscore in it's name, and when I grant
1523 privileges to a user for this database, a backslash is added before
1525 This is normal and means that the grant is done only for this
1526 database. If there was no backslash, this would be a wildcard grant,
1527 and the underscore would mean "any character". So, if the database
1528 name is "john_db", the user would get rights to john1db, john2db...
1529 instead of just john_db.
1530 If you really want to grant using a wildcard, there is a dialog box "
1531 Database (wildcards allowed)" for this.
1533 [6.11] What is the curious symbol ø in the table statistics?
1536 [6.12] I want to understand some Export options.
1537 "Complete inserts" adds the column names on every INSERT command, for
1538 better documentation (but resulting file is bigger).
1539 "Extended inserts" provides a shorter dump file by using only once the
1540 INSERT verb and the table name.
1541 "Enclose table and field names with backquotes" ensures that field and
1542 table names formed with special characters are protected.
1544 [6.13] I would like to create a database with a dot in its name.
1545 This is a bad idea, because in MySQL the syntax "database.table" is
1546 the normal way to reference a database and table name. Worse, MySQL
1547 will usually let you create a database with a dot, but then you cannot
1548 work with it, nor delete it.
1550 [6.14] How do I set up the SQL validator?
1551 To use it, you need a very recent version of PHP, built with Overload,
1552 XML and PEAR support. On your system command line, run "pear install
1553 Mail_Mime Net_DIME SOAP" to get the nessecary PEAR modules for usage.
1554 If you use it, you should be aware that any SQL statement you submit
1555 will be stored anonymously (database/table/column names, strings,
1556 numbers replaced with generic values). The Mimer SQL Validator itself,
1557 is © 2001 Upright Database Technology. We utilize it as free XML-SOAP
1559 The overload module is crucial to the functionality of the validator
1562 [6.15] I want to add a BLOB field and put an index on it, but MySQL
1563 says "BLOB column '...' used in key specification without a key
1565 The right way to do this, is to create the field without any indexes,
1566 then display the table structure and use the "Create an index" dialog.
1567 On this page, you will be able to choose your BLOB field, and set a
1568 size to the index, which is the condition to create an index on a BLOB
1571 [6.16] How can I simply move in page with plenty editing fields?
1572 You can use Ctrl+arrows for moving on most pages with plenty editing
1573 fields (table structure changes, row editing, etc.).
1575 [7. phpMyAdmin project]
1577 [7.1] I have found a bug. How do I inform developers?
1578 Our Bug Tracker is located at
1579 http://sourceforge.net/projects/phpmyadmin/ under the Bugs section.
1580 But please first discuss your bug with other users:
1581 http://sourceforge.net/projects/phpmyadmin/ (and choose Forums)
1583 [7.2] I want to translate the messages to a new language or upgrade an
1584 existing language, where do I start?
1585 Always use the current cvs version of your language file. For a new
1586 language, start from english-iso-8859-1.inc.php3. If you don't know
1587 how to get the cvs version, please ask one of the developers.
1588 Please note that we try not to use html entities like é in the
1589 translations, since we define the right character set in the file.
1590 With html entities, the text on buttons would not display correctly.
1591 You can then put your translations, as a zip file to avoid losing
1592 special characters, on the sourceforge.net translation tracker.
1593 It would be a good idea to subscribe to the phpmyadmin-translators
1594 mailing list, because this is where we ask for translations of new
1597 [7.3] I would like to help out with the development of phpMyAdmin. How
1599 The following method is preferred for new developers:
1600 * fetch the current CVS tree over anonymous CVS:
1602 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmy
1604 [Password: simply press the Enter key]
1606 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmy
1607 admin checkout phpMyAdmin
1608 [This will create a new sub-directory named phpMyAdmin]
1610 * put the modified files (tar'ed and gzip'ed) inside the patch
1611 tracker of the phpMyAdmin SourceForge account.
1613 Write access to the CVS tree is granted only to experienced developers
1614 who have already contributed something useful to phpMyAdmin.
1615 Also, have a look at the Developers section.
1616 ______________________________________________________________________
1618 Top - Requirements - Introduction - Installation -
1619 Configuration - FAQ - Developers - Credits
1620 ______________________________________________________________________
1622 Developers Information
1624 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
1625 great features have been written by other people and you too can help
1626 to make phpMyAdmin a useful tool.
1628 If you're planning to contribute source, please read the following
1630 * All files include header.inc.php3 (layout),
1631 libraries/common.lib.php3 (common functions) and config.inc.php3.
1632 All configuration data belongs in config.inc.php3. Please keep it
1633 free from other code.
1634 Commonly used functions should be added to
1635 libraries/common.lib.php3 and more specific ones may be added
1636 within a library stored into the libraries sub-directory.
1637 * Obviously, you're free to use whatever coding style you want. But
1638 please try to keep your code as simple as possible: beginners are
1639 using phpMyAdmin as an example application.
1640 As far as possible, we want the scripts to be XHTML1.0 and CSS2
1641 compliant on one hand, they fit PEAR coding standards on the other
1642 hand. Please pay attention to this.
1643 * Please try to keep up the file-naming conventions. Table-related
1644 stuff goes to tbl_*.php3, db-related code to db_*.php3,
1645 server-related tools to server_*.php3 and so on.
1646 * Please don't use verbose strings in your code, instead add the
1647 string (at least) to english-iso-8859-1.inc.php3 and print() it
1649 * If you want to be really helpful, write an entry for the
1652 IMPORTANT: With 1.4.1, development has switched to CVS. The following
1653 method is preferred for new developers:
1654 * fetch the current CVS tree over anonymous CVS:
1656 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmy
1658 [Password: simply press the Enter key]
1660 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmy
1661 admin checkout phpMyAdmin
1662 [This will create a new sub-directory named phpMyAdmin]
1664 * put the modified files (tar'ed and gzip'ed) inside the patch
1665 tracker of the phpMyAdmin SourceForge account
1666 (http://sourceforge.net/projects/phpmyadmin/)
1668 Write access to the CVS tree is granted only to developers who have
1669 already contributed something useful to phpMyAdmin. If you're
1670 interested in that, please contact us using the phpmyadmin-devel
1672 ______________________________________________________________________
1674 Top - Requirements - Introduction - Installation -
1675 Configuration - FAQ - Developers - Credits
1676 ______________________________________________________________________
1681 phpMyAdmin - Credits
1682 ====================
1684 CREDITS, in chronological order
1685 -------------------------------
1687 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
1688 * creator of the phpmyadmin project
1689 * maintainer from 1998 to summer 2000
1691 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
1692 * multi-language version
1693 * various fixes and improvements
1694 * project co-administrator
1696 - Olivier Müller <om_at_omnis.ch>
1697 * started SourceForge phpMyAdmin project in March 2001
1698 * sync'ed different existing CVS trees with new features and bugfixes
1699 * multi-language improvements, dynamic language selection
1700 * current project maintainer
1701 * many bugfixes and improvements
1703 - Loïc Chapeaux <lolo_at_phpheaven.net>
1704 * rewrote and optimized javascript, DHTML and DOM stuff
1705 * rewrote the scripts so they fit the PEAR coding standards and
1706 generate XHTML1.0 and CSS2 compliant codes
1707 * improved the language detection system
1708 * many bugfixes and improvements
1710 - Robin Johnson <robbat2_at_users.sourceforge.net>
1711 * database maintence controls
1713 * Host authentication IP Allow/Deny
1714 * DB-based configuration (Not completed)
1717 * many bugfixes and improvements
1719 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
1721 * multiple dump feature
1725 - Geert Lund <glund_at_silversoft.dk>
1727 * moderator of the phpMyAdmin users forum at phpwizard.net
1729 - Korakot Chaovavanich <korakot_at_iname.com>
1730 * "insert as new row" feature
1732 - Pete Kelly <webmaster_at_trafficg.com>
1733 * rewrote and fix dump code
1736 - Steve Alberty <alberty_at_neptunlabs.de>
1737 * rewrote dump code for PHP4
1738 * mySQL table statistics
1741 - Benjamin Gandon <gandon_at_isia.cma.fr>
1742 * main author of the version 2.1.0.1
1745 - Alexander M. Turek <rabus_at_bugfixes.info>
1747 * MySQL 4 related features
1748 * various small features and fixes
1749 * German language file updates
1751 - Mike Beck <mike.beck_at_ibmiller.de>
1752 * automatic joins in QBE
1753 * links column in printview
1756 - Michal Cihar <nijel_at_users.sourceforge.net>
1757 * enhanced index creation/display feature
1758 * feature to use a different charset for HTML than for MySQL
1759 * Czech language file updates
1761 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
1762 (http://sourceforge.net/projects/phpmysqlformgen/)
1763 * suggested the patch for multiple table printviews
1765 - Garvin Hicking <hicking_at_faktor-e.de>
1766 * built the patch for vertical display of table rows
1768 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
1769 * japanese kanji encoding conversion feature
1771 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
1772 * the Cookie authentication mode
1774 - Axel Sander <n8falke_at_users.sourceforge.net>
1775 * table relation-links feature
1777 - Maxime Delorme <delorme.maxime_at_free.fr>
1778 * PDF schema output, thanks also to Olivier Plathey for the
1779 "FPDF" library (see http://www.fpdf.org/).
1781 - Olof Edlund <olof.edlund_at_upright.se>
1782 * SQL validator server
1784 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
1787 And also to the following people who have contributed minor changes,
1788 enhancements, bugfixes or support for a new language since version 2.1.0:
1790 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
1791 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
1792 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
1793 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley
1795 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
1796 www.securereality.com.au, Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky,
1797 Rachim Tamsjadi, Kositer Uros, Luís V., Martijn W. van der Lee,
1798 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
1799 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas.
1802 Original Credits of Version 2.1.0
1803 ---------------------------------
1805 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
1806 to create a web-based interface to MySQL using PHP3. Although I have not
1807 used any of his source-code, there are some concepts I've borrowed from
1808 him. phpMyAdmin was created because Peter told me he wasn't going to
1809 further develop his (great) tool.
1811 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
1812 code for the check when dropping a table or database. He also suggested
1813 that you should be able to specify the primary key on tbl_create.php3. To
1814 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
1815 well as a bug-report. Plus many smaller improvements.
1816 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
1817 were introduced in 1.3.0 (including quite significant ones like the
1818 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
1820 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
1821 language-independent by outsourcing the strings to a separate file. He
1822 also contributed the French translation.
1823 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
1824 tbl_select.php3, a feature to display only some fields from a table.
1825 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
1826 functions in tbl_change.php3. He also added the
1827 "Query by Example" feature in 2.0.
1828 - Dave Walton <walton_at_nordicdms.com> added support for multiple
1829 servers and is a regular contributor for bug-fixes.
1830 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
1832 The following people have contributed minor changes, enhancements, bugfixes
1833 or support for a new language:
1834 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
1835 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
1836 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
1839 And thanks to everyone else who sent me email with suggestions, bug-reports
1840 and or just some feedback.
1841 ______________________________________________________________________
1843 Top - Requirements - Introduction - Installation -
1844 Configuration - FAQ - Developers - Credits
1845 ______________________________________________________________________
1847 Valid XHTML 1.0! Valid CSS!