2 ______________________________________________________________________
4 Top - Requirements - Introduction - Installation -
5 Configuration - FAQ - Developers - Credits - Translators
6 ______________________________________________________________________
8 phpMyAdmin 2.4.0-rc2 Documentation
10 * Sourceforge phpMyAdmin project page [ http://www.phpmyadmin.net/
13 + Version history: ChangeLog
14 + General notes: README
16 * Documentation version: $Id: Documentation.html,v 1.391 2003/02/04
21 * PHP3 or PHP4: phpMyAdmin widely uses the 'str_replace()' php
22 function that was added in PHP 3.0.6, but was buggy up until
23 PHP 3.0.8. Then you should not run this script with PHP3 < 3.0.8.
24 PHP also needs to be compiled with MySQL support;
25 * MySQL (tested with 3.21.x, 3.22.x, 3.23.x and 4.0.x);
26 Note: Because of a major change in the definition syntax of string
27 field types, this version of phpMyAdmin probably won't work
28 correctly with MySQL >= 4.1.0!
29 * a web-browser (doh!).
33 phpMyAdmin can manage a whole MySQL-server (needs a super-user) but
34 also a single database. To accomplish the latter you'll need a
35 properly set up MySQL-user who can read/write only the desired
36 database. It's up to you to look up the appropriate part in the MySQL
37 manual. Currently phpMyAdmin can:
38 * create and drop databases
39 * create, copy, drop, rename and alter tables
40 * do table maintenance
41 * delete, edit and add fields
42 * execute any SQL-statement, even batch-queries
43 * manage keys on fields
44 * load text files into tables
45 * create (*) and read dumps of tables
46 * export (*) data to CSV, XML and Latex formats
47 * administer multiple servers
48 * check referential integrity
49 * using Query-by-example (QBE), create complex queries automatically
50 connecting required tables
51 * create PDF graphics of your Database layout
52 * search globally in a database or a subset of it
53 * communicate in 43 different languages
55 (*) phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats)
56 dumps and CSV exports if you use PHP4 >= 4.0.4 with Zlib support
57 (--with-zlib) and/or Bzip2 support (--with-bz2).
61 NOTE: phpMyAdmin does not apply any special security methods to the
62 MySQL database server. It is still the sysadmin's job to grant
63 permissions on the MySQL databases properly. phpMyAdmin's "Users" page
66 Warning for Mac users:if you are on a MacOS version before OS X,
67 Stuffit unstuffs with Mac formats.
68 So you'll have to resave as in Bbedit to unix style ALL phpMyAdmin
69 scripts before uploading them to your server, as PHP seems not to like
70 Mac-style end of lines character ("\r").
72 Documentation warning: when you see in this document a .php3 file
73 extension, please transpose to .php if you are using a kit with files
74 having this extension.
77 1. Choose and download a distribution kit with the files having the
78 extension (.php3 or .php) depending on the way your web/PHP server
79 interprets those extensions.
80 2. Untar or unzip the distribution (be sure to unzip the
81 subdirectories): tar xzvf phpMyAdmin_x.x.x.tar.gz in your
82 webserver's document root. If you don't have direct access to your
83 document root, put the files in a directory on your local machine,
84 and, after step 3, transfer the directory on your web server
85 using, for example, ftp.
86 3. Open the file config.inc.php3 in your favourite editor and change
87 the values for host, user, password and authentication mode to fit
88 your environment. Also insert the correct value for
89 $cfg['PmaAbsoluteUri']. Have a look at Configuration section for
90 an explanation of all values.
91 4. It is recommended that you protect the directory in which you
92 installed phpMyAdmin (unless it's on a closed intranet, or you
93 wish to use http or cookie authentication), for example with
94 HTTP-AUTH (in a .htaccess file). See the FAQ section for
95 additional information.
96 5. Open the file <www.your-host.com>/<your-install-dir>/index.php3 in
97 your browser. phpMyAdmin should now display a welcome screen and
98 your databases, or a login dialog if using http or cookie
101 Upgrading from an older version:
102 * Please do not copy your older config.inc.php3 over the new one: it
103 may offer new configuration variables, and the new version may
104 depend on these for normal behavior. It is suggested instead to
105 insert your site values in the new one.
107 Using authentication modes:
108 * Http and cookie authentication modes are recommended in a
109 multi-user environment where you want to give users access to
110 their own database and don't want them to play around with others.
111 Nevertheless be aware that MS Internet Explorer seems to be really
112 buggy about cookies, at least till version 6. And php 4.1.1 is
113 also a bit buggy in this area!
114 Even in a single-user environment, you might prefer to use http or
115 cookie mode so that your user/password pair are not in clear in
116 the configuration file.
117 * Http and cookie authentication modes are more secure: the MySQL
118 password does not need to be set in the phpMyAdmin configuration
119 file (except for the "controluser" -see the Configuration
121 However, keep in mind that the password travels in plain text,
122 unless you are using the https protocol.
123 In cookie mode, we send the password in a temporary cookie, so
124 most browsers should not store the password in their cookie file.
125 * For 'http' and 'cookie' modes, phpMyAdmin needs a controluser that
126 has only the SELECT privilege on the mysql.user (all columns
127 except "Password"), mysql.db (all columns) & mysql.tables_priv
128 (all columns except "Grantor" & "Timestamp") tables.
129 You must specify the details for the controluser in the
130 config.inc.php3 file under the $cfg['Servers'][$i]['controluser']&
131 $cfg['Servers'][$i]['controlpass'] settings.
132 This example assumes you want to use pma as the controluser and
133 pmapass as the controlpass, but this is only an example: use
134 something else in your file:
136 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
137 GRANT SELECT (Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv,
138 Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv,
139 Grant_priv, References_priv, Index_priv, Alter_priv)
140 ON mysql.user TO 'pma'@'localhost';
141 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
142 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
143 ON mysql.tables_priv TO 'pma'@'localhost';
145 ... and if you want to use the many new relation and bookmark
148 GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db> TO 'pma'@'localhost';
150 (this of course requires you to have a special DB for phpMyAdmin,
151 the contents will be explained later)
152 * Then each of the true users should be granted a set of privileges
153 on a set of particular databases. Normally you shouldn't give
154 global privileges to an ordinary user, unless you understand the
155 impact of those privileges (for example, you are creating a
157 For example, to grant the user real_user with all privileges on
158 the database user_base:
159 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost
160 IDENTIFIED BY 'real_password';
161 What the user may now do is controlled entirely by the MySQL user
163 With http or cookie auth mode, you don't need to fill the
164 user/password fields inside the $cfg['Servers'] array.
166 'http' authentication mode:
167 * Was called 'advanced' in versions before 2.2.3.
168 * Introduced in 1.3.0, it uses Basic HTTP authentication method and
169 allows you to login as any valid MySQL user.
170 * Is only supported with PHP running as an Apache module, not with
173 'cookie' authentication mode:
174 * You can use this method as a replacement for the http
175 authentication (for example, if you're running IIS).
176 * Obviously, the user must enable cookies in the browser.
177 * With this mode, the use can truly logout of phpMyAdmin and login
178 back with the same username.
180 'config' authentication mode:
181 * This mode is the less secure one because it requires you to fill
182 the $cfg['Servers'][$i]['user'] and
183 $cfg['Servers'][$i]['password'] fields.
184 But you don't need to setup a "controluser" here: using the
185 $cfg['Servers'][$i]['only_db'] might be enough.
186 * In the ISP FAQ section, there is an entry explaining how to
187 protect your configuration file.
188 * For additional security in this mode, you may wish to consider the
189 Host authentication $cfg['Servers'][$i]['AllowDeny']['order'] and
190 $cfg['Servers'][$i]['AllowDeny']['rules'] configuration
195 Warning for Mac users: php seems not to like Mac end of lines
196 character ("\r"). So ensure you choose the option that allows to use
197 the *nix end of line character ("\n") in your text editor before
198 registering a script you have modified.
200 All configurable data is placed in config.inc.php3.
202 $cfg['PmaAbsoluteUri'] string
203 Sets here the complete url (with full path) to your phpMyAdmin
205 http://www.your_web.net/path_to_your_phpMyAdmin_directory/.
206 phpMyAdmin needs this setting, because of requirements of the
207 HTTP protocol, explained in RFC2616, section 14.30.
208 Don't forget the slash at the end of your url. The url must
209 contain characters that are valid for a url, and on some
210 servers, the path is case-sensitive.
211 Starting with version 2.3.0, you can try to leave this
212 parameter empty, because the program tries to auto-detect its
213 proper value. Additional details are in the configuration file.
214 Alternatively, this setting can be dynamically completed. For
215 example, you can try to use such a kind of code:
217 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
218 . $_SERVER['HTTP_HOST']
219 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
220 . substr($_SERVER['PHP_SELF'], 0, strrpos($_SERVER['PHP_SELF'], '/')+1);
224 $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
225 . $_SERVER['SERVER_NAME']
226 . (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
227 . substr($_SERVER['SCRIPT_NAME'], 0, strrpos($_SERVER['SCRIPT_NAME'], '/')+1);
230 Please note that the $_SERVER array doesn't exist in
231 PHP < 4.1.0. Try to replace $_SERVER by $HTTP_SERVER_VARS or
232 $GLOBALS in this case.
234 $cfg['PmaAbsoluteUri_DisableWarning'] boolean
235 By default, when you leave $cfg['PmaAbsoluteUri'] empty, and
236 the system detects your absolute URI automatically, we display
237 a warning to remind you. If you have tested the automatic
238 detection, and it works perfectly for your setup, then you can
239 set this variable to squelch the warning.
241 $cfg['PmaNoRelation_DisableWarning'] boolean
242 Starting with version 2.3.0 phpMyAdmin offers a lot of features
243 to work with master / foreign - tables (see
244 $cfg['Servers'][$i]['pmadb']).
245 If you tried to set this up and it does not work for you, have
246 a look on the "Structure" page of one database where you would
247 like to use it. You will find a link that will analyze why
248 those features have been disabled.
249 If you do not want to use those features set this variable to
250 TRUE to stop this message from appearing.
252 $cfg['Servers'] array
253 Since version 1.4.2, phpMyAdmin supports the administration of
254 multiple MySQL servers. Therefore, a $cfg['Servers']-array has
255 been added which contains the login information for the
256 different servers. The first $cfg['Servers'][$i]['host']
257 contains the hostname of the first server, the second
258 $cfg['Servers'][$i]['host'] the hostname of the second server,
259 etc. If you have only one server to administer, simply leave
260 free the hostname of the other $cfg['Server']-entries.
262 $cfg['Servers'][$i]['host'] string
263 The hostname of your $i-th MySQL-server. E.g. localhost.
265 $cfg['Servers'][$i]['port'] string
266 The port-number of your $i-th MySQL-server. Default is 3306
269 $cfg['Servers'][$i]['socket'] string
270 The path to the socket to use. Leave blank for default.
271 To use the socket feature you must run php 3.0.10 or more.
273 $cfg['Servers'][$i]['connect_type'] string
274 What type connection to use with the MySQL server. Your options
275 are 'socket' & 'tcp'. It defaults to 'tcp' as that is nearly
276 guarenteed to be available on all MySQL servers, while sockets
277 are not supported on some platforms.
278 To use the socket mode, your MySQL server must be on the same
279 machine as the Web server.
281 $cfg['Servers'][$i]['compress'] boolean
282 Wheather to use a compressed protocol for the MySQL server
283 connection or not (experimental).
284 This feature requires PHP >= 4.3.0.
286 $cfg['Servers'][$i]['controluser'] string
287 $cfg['Servers'][$i]['controlpass'] string
288 When using http or cookie authentication modes (or 'config'
289 authentication mode since phpMyAdmin 2.2.1), you need to supply
290 the details of a MySQL account that has SELECT privilege on the
291 mysql.user (all columns except "Password"), mysql.db (all
292 columns) & mysql.tables_priv (all columns except "Grantor" &
293 "Timestamp") tables. This account is used to check what
294 databases the user will see at login.
295 Please see the install section on "Using http authentication"
296 for more information.
297 Note that if you try login to phpMyAdmin with this
298 "controluser", you could get some errors, depending the exact
299 privileges you gave to the "controluser". phpMyAdmin does not
300 support a direct login with the "controluser".
301 In versions before 2.2.5, those were called "stduser/stdpass".
303 $cfg['Servers'][$i]['auth_type'] string ['http'|'cookie'|'config']
304 Whether config or cookie or http authentication should be used
307 + 'config' authentication ($auth_type = 'config') is the plain
308 old way: username and password are stored in config.inc.php3.
309 + 'cookie' authentication mode ($auth_type = 'cookie') as
310 introduced in 2.2.3 allows you to log in as any valid MySQL
311 user with the help of... cookies. Log name and password are
312 stored in cookies during the session and password is deleted
314 + 'http' authentication (was called 'advanced' in older
315 versions) ($auth_type = 'http') as introduced in 1.3.0 allows
316 you to log in as any valid MySQL user via HTTP-Auth.
318 Please see the install section on "Using authentication modes"
319 for more information.
321 $cfg['Servers'][$i]['user'] string
322 $cfg['Servers'][$i]['password'] string
323 The user/password-pair which phpMyAdmin will use to connect to
324 this MySQL-server. This user/password pair is not needed when
325 http or cookie authentication is used, and should be empty.
327 $cfg['Servers'][$i]['only_db'] string or array
328 If set to a(an array of) database name(s), only this(these)
329 database(s) will be shown to the user. Since phpMyAdmin 2.2.1,
330 this/these database(s) name(s) may contain MySQL wilcards
331 characters ("_" and "%"): if you want to use literal instances
332 of these characters, escape them (ie use 'my\_db' and not
334 This setting is an efficient way to lower the server charge
335 since the latter does not need to send MySQL requests to build
336 the available database list. But it does not replace the
337 privileges rules of the MySQL database server. If set, it just
338 means only these databases will be displayed but not at all
339 other databases can't be used.
341 $cfg['Servers'][$i]['verbose'] string
342 Only useful when using phpMyAdmin with multiple server entries.
343 If set, this string will be displayed instead of the hostname
344 in the pulldown menu on the main page. This can be useful if
345 you want to show only certain databases on your system, for
348 $cfg['Servers'][$i]['pmadb'] string
349 Starting with version 2.3.0 phpMyAdmin offers a lot of features
350 to work with master / foreign - tables. To use those as well as
351 the bookmark feature you need special tables with a predefined
352 structure, which we explain below.
353 If you are the only user of this phpMyAdmin installation, you
354 can use your current database to store those special tables; in
355 this case, just put your current database name in
356 $cfg['Servers'][$i]['pmadb'].
357 If you are setting up a multi-user phpMyAdmin installation, you
358 will need to create a new db and setup special privileges, so,
361 + create a new database for phpmyadmin:
362 CREATE DATABASE phpmyadmin;
363 Note that "controluser" must have SELECT, INSERT, UPDATE and
364 DELETE privileges on this database. Here is a query to set up
365 those privileges (using "phpmyadmin" as the database name,
366 and "pma" as the controluser):
367 GRANT SELECT,INSERT,UPDATE,DELETE ON phpmyadmin.* to
369 do not give any other user rights on this database.
370 + enter the databasename in $cfg['Servers'][$i]['pmadb']
372 $cfg['Servers'][$i]['bookmarktable'] string
373 Since release 2.2.0 phpMyAdmin allows to bookmark queries. This
374 can be useful for queries you often run.
375 To allow the usage of this functionality you have to:
377 + set up "pmadb" as described above
378 + within this database create a table following this scheme:
379 CREATE TABLE `PMA_bookmark` (
380 id int(11) DEFAULT '0' NOT NULL auto_increment,
381 dbase varchar(255) NOT NULL,
382 user varchar(255) NOT NULL,
383 label varchar(255) NOT NULL,
386 ) TYPE=MyISAM COMMENT='Bookmarks';
387 + enter the tablename in $cfg['Servers'][$i]['bookmarktable']
389 $cfg['Servers'][$i]['relation'] string
390 Since release 2.2.4 you can describe, in a special 'relation'
391 table, which field is a key in another table (a foreign key).
392 phpMyAdmin currently uses this to
394 + make clickable, when you browse the master table, the data
395 values that point to the foreign table;
396 + display in an optional tooltip the "display field" when
397 browsing the master table, if you move the mouse to a column
398 containing a foreign key (use also the 'table_info' table);
399 + display links on the table properties page, to check
400 referential integrity (display missing foreign keys) for each
402 + in query-by-example, create automatic joins (see an example
403 in the FAQ, section "Using phpMyAdmin");
404 + enable you to get a PDF schema of your database (also uses
405 the table_coords table).
407 The keys can be numeric or character.
408 To allow the usage of this functionality the superuser has to:
410 + set up "pmadb" as described above
411 + within this database create a table following this scheme:
412 CREATE TABLE `PMA_relation` (
413 `master_db` varchar(64) NOT NULL default '',
414 `master_table` varchar(64) NOT NULL default '',
415 `master_field` varchar(64) NOT NULL default '',
416 `foreign_db` varchar(64) NOT NULL default '',
417 `foreign_table` varchar(64) NOT NULL default '',
418 `foreign_field` varchar(64) NOT NULL default '',
419 PRIMARY KEY (`master_db`, `master_table`,
421 KEY foreign_field (foreign_db, foreign_table)
422 ) TYPE=MyISAM COMMENT='Relation table';
423 + put the relation table name in
424 $cfg['Servers'][$i]['relation']
425 + now as normal user open phpMyAdmin and for each one of your
426 tables where you want to use this feature, click
427 "Structure/Relation view/" and choose foreign fields.
429 Please note that in the current (2.3.0) version, master_db must
430 be the same as foreign_db. Those fields have been put in future
431 development of the cross-db relations.
433 $cfg['Servers'][$i]['table_info'] string
434 Since release 2.3.0 you can describe, in a special 'table_info'
435 table, which field is to be displayed as a tooltip when moving
436 the cursor over the corresponding key.
437 This configuration variable will hold the name of this special
438 table. To allow the usage of this functionality the superuser
441 + set up "pmadb" as described above
442 + within this database create a table following this scheme:
443 CREATE TABLE `PMA_table_info` (
444 `db_name` varchar(64) NOT NULL default '',
445 `table_name` varchar(64) NOT NULL default '',
446 `display_field` varchar(64) NOT NULL default '',
447 PRIMARY KEY (`db_name`, `table_name`)
448 ) TYPE=MyISAM COMMENT='Table information for
450 + put the table name in $cfg['Servers'][$i]['table_info']
451 + then for each table where you want to use this feature, click
452 "Structure/Relation view/Choose field to display" to choose
455 Usage tip: Display field.
457 $cfg['Servers'][$i]['table_coords'] string
458 $cfg['Servers'][$i]['pdf_pages'] string
459 Since release 2.3.0 you can have phpMyAdmin create PDF pages
460 showing the relations between your tables. To do this it needs
461 two tables "pdf_pages" (storing information about the available
462 pdf pages) and "table_coords" (storing coordinates where each
463 table will be placed on a PDF schema output).
464 You must be using the "relation" feature and have a table of
465 PDF pages (see $cfg['Servers'][$i]['pdf_pages']) to create PDF
467 To allow the usage of this functionality the superuser has to:
469 + set up "pmadb" as described above
470 + within this database create a table following this scheme:
471 CREATE TABLE `PMA_table_coords` (
472 `db_name` varchar(64) NOT NULL default '',
473 `table_name` varchar(64) NOT NULL default '',
474 `pdf_page_number` int NOT NULL default '0',
475 `x` float unsigned NOT NULL default '0',
476 `y` float unsigned NOT NULL default '0',
477 PRIMARY KEY (`db_name`, `table_name`,
479 ) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin
481 + also within this database create:
482 CREATE TABLE `PMA_pdf_pages` (
483 `db_name` varchar(64) NOT NULL default '',
484 `page_nr` int(10) unsigned NOT NULL auto_increment,
485 `page_descr` varchar(50) NOT NULL default '',
486 PRIMARY KEY (page_nr),
488 ) TYPE=MyISAM COMMENT='PDF Relationpages for PMA';
489 + put the first table name in
490 $cfg['Servers'][$i]['table_coords'] and the second table name
491 in $cfg['Servers'][$i]['pdf_pages']
493 Usage tips: PDF output.
495 $cfg['Servers'][$i]['column_comments'] string
496 Since release 2.3.0 you can store comments to describe each
497 column for each table. These will then be shown on the
499 To allow the usage of this functionality the superuser has to:
501 + set up "pmadb" as described above
502 + within this database create a table following this scheme:
503 CREATE TABLE `PMA_column_comments` (
504 id int(5) unsigned NOT NULL auto_increment,
505 db_name varchar(64) NOT NULL default '',
506 table_name varchar(64) NOT NULL default '',
507 column_name varchar(64) NOT NULL default '',
508 comment varchar(255) NOT NULL default '',
510 UNIQUE KEY db_name (db_name, table_name, column_name)
511 ) TYPE=MyISAM COMMENT='Comments for Columns';
512 + put the table name in $cfg['Servers'][$i]['column_comments']
514 $cfg['Servers'][$i]['AllowDeny']['order'] string
515 If your rule order is empty, then IP authentication is
517 If your rule order is set to 'deny,allow' then the system
518 applies all deny rules followed by allow rules. Access is
519 allowed by default. Any client which does not match a Deny
520 command or does match an Allow command will be allowed access
522 If your rule order is set to 'allow,deny' then the system
523 applies all allow rules followed by deny rules. Access is
524 denied by default. Any client which does not match an Allow
525 directive or does match a Deny directive will be denied access
527 If your rule order is set to 'explicit', the authentication is
528 performed in a similar fashion to rule order 'deny,allow', with
529 the added restriction that your host/username combination must
530 be listed in the allow rules, and not listed in the deny rules.
531 This is the most secure means of using Allow/Deny rules, and
532 was available in Apache by specifying allow and deny rules
533 without setting any order.
535 $cfg['Servers'][$i]['AllowDeny']['rules'] array of strings
536 The general format for the rules is as such:
537 <'allow' | 'deny'> <username> [from] <ipmask>
538 If you wish to match all users, it is possible to use a '%' as
539 a wildcard in the username field.
540 There are a few shortcuts you can use in the ipmask field as
543 'localhost' -> 127.0.0.1/8
544 Having an empty rule list is equivalent to either using 'allow
545 % from all' if your rule order is set to 'deny,allow' or 'deny
546 % from all' if your rule order is set to 'allow,deny' or
548 For the IP matching system, the following work:
549 xxx.xxx.xxx.xxx (an exact IP address)
550 xxx.xxx.xxx.[yyy-zzz] (an IP address range)
551 xxx.xxx.xxx.xxx/nn (CIDR, Classless Inter-Domain Routing type
553 But the following does not work:
554 xxx.xxx.xxx.xx[yyy-zzz] (partial IP address range)
556 $cfg['ServerDefault'] integer
557 If you have more than one server configured, you can set
558 $cfg['ServerDefault'] to any one of them to autoconnect to that
559 server when phpMyAdmin is started, or set it to 0 to be given a
560 list of servers without logging in.
561 If you have only one server configured, $cfg['ServerDefault']
562 MUST be set to that server.
564 $cfg['OBGzip'] boolean
565 Defines whether to use gzip output buffering for increased
566 speed in HTTP transfers.
568 $cfg['PersistentConnections'] boolean
569 Whether persistent connections should be used or not
570 (mysql_connect or mysql_pconnect).
572 $cfg['ExecTimeLimit'] integer [number of seconds]
573 Set the number of seconds a script is allowed to run. If
574 seconds is set to zero, no time limit is imposed.
575 This setting is used while importing/exporting dump files but
576 has no effect when PHP is running in safe mode.
578 $cfg['SkipLockedTables'] boolean
579 Mark used tables and make it possible to show databases with
580 locked tables (since 3.23.30).
582 $cfg['ShowSQL'] boolean
583 Defines whether sql-queries generated by phpMyAdmin should be
586 $cfg['AllowUserDropDatabase'] boolean
587 Defines whether normal users (non-administrator) are allowed to
588 delete their own database or not. If set as FALSE, the link
589 "Drop Database" will not be shown, and even a "DROP DATABASE
590 mydatabase" will be rejected. Quite practical for ISP's with
593 $cfg['Confirm'] boolean
594 Whether a warning ("Are your really sure..") should be
595 displayed when you're about to loose data.
597 $cfg['LoginCookieRecall'] boolean
598 Define whether the previous login should be recalled or not in
599 cookie authentication mode.
601 $cfg['UseDbSearch'] boolean
602 Define whether the "search string inside database" is enabled
605 $cfg['LeftFrameLight'] boolean
606 Defines whether to use select-based menu and display only the
607 current tables in the left frame (smaller page).
609 $cfg['ShowTooltip'] boolean
610 Defines whether to display table comment as tooltip in left
613 $cfg['ShowStats'] boolean
614 Defines whether to display space usage and statistics about
615 databases and tables or not.
616 Note that statistics requires at least MySQL 3.23.3 and that,
617 at this date, MySQL doesn't return such information for
620 $cfg['ShowMysqlInfo'] boolean
621 $cfg['ShowMysqlVars'] boolean
622 $cfg['ShowPhpInfo'] boolean
623 $cfg['ShowChgPassword'] boolean
624 Defines whether to display the "MySQL runtime information",
625 "MySQL system variables", "PHP information" and "Change
626 password " links or not for simple users at the starting main
627 (right) frame. This setting does not check MySQL commands
629 Please note that to block the usage of phpinfo() in scripts,
630 you have to put this in your php.ini:
631 disable_functions = phpinfo()
632 Also note that enabling the "Change password " link has no
633 effect with "config" authentication mode: because of the hard
634 coded password value in the configuration file, end users can't
635 be allowed to change their passwords.
637 $cfg['SuggestDBName'] boolean
638 Defines whether to suggest a database name on the "Create
639 Database" form or to keep the textfield empty.
641 $cfg['ShowBlob'] boolean
642 Defines whether BLOB fields are shown when browsing a table's
645 $cfg['NavigationBarIconic'] boolean
646 Defines whether navigation bar buttons contain text or symbols
649 $cfg['ShowAll'] boolean
650 Defines whether an user should be displayed a "show all
651 (records)" button in browse mode or not.
653 $cfg['MaxRows'] integer
654 Number of rows displayed when browsing a resultset. If the
655 resultset contains more rows, Previous/Next links will be
658 $cfg['Order'] string [DESC|ASC|SMART]
659 Defines whether fields are displayed in ascending (ASC) order,
660 in descending (DESC) order or in a "smart" (SMART) order -ie
661 descending order for fields of type TIME, DATE, DATETIME &
662 TIMESTAMP, ascending order else- by default.
664 $cfg['ProtectBinary'] boolean or string
665 Defines whether BLOB or BINARY fields are protected from
666 edition when browsing a table's content or not. Valid values
668 - FALSE to allow edition of all fields;
669 - blob to allow edition of all fields except BLOBS;
670 - all to disallow edition of all BINARY or BLOB fields.
672 $cfg['ShowFunctionFields'] boolean
673 Defines whether MySQL functions fields should be displayed or
674 not in edit/insert mode.
676 $cfg['CharEditing'] string
677 Defines which type of editing controls should be used for CHAR
678 and VARCHAR fields. Possible values are:
680 + input - this allows to limit size of text to size of field in
681 MySQL, but has problems with newlines in fields
682 + textarea - no problems with newlines in fields, but also no
685 Default is old behavior so input.
687 $cfg['ZipDump'] boolean
688 $cfg['GZipDump'] boolean
689 $cfg['BZipDump'] boolean
690 Defines whether to allow the use of zip/gzip/bzip compression
691 when creating a dump file or not.
693 $cfg['DefaultTabDatabase'] string
694 Defines the tab displayed by default on database view. Possible
695 values: "db_details_structure.php3", "db_details.php3" or
698 $cfg['DefaultTabTable'] string
699 Defines the tab displayed by default on table view. Possible
700 values: "tbl_properties_structure.php3", "tbl_properties.php3",
701 "tbl_select.php3" or "tbl_change.php3".
703 $cfg['MySQLManualBase'] string
704 If set to an URL which points to the MySQL documentation (type
705 depends on $cfg['MySQLManualType']), appropriate help links are
707 See MySQL Documentation page for more information about MySQL
708 manuals and their types.
710 $cfg['MySQLManualType'] string
711 Type of MySQL documentation:
713 + old - old style used in phpMyAdmin 2.3.0 and sooner
714 + searchable - "Searchable, with user comments"
715 + chapters - "HTML, one page per chapter"
716 + big - "HTML, all on one page"
717 + none - do not show documentation links
719 $cfg['DefaultLang'] string
720 Defines the default language to use, if not browser-defined or
722 See the select_lang.inc.php3 script to know the valid values
726 Force: always use this language (must be defined in the
727 select_lang.inc.php3 script).
729 $cfg['DefaultCharset'] string
730 Default charset to use for recoding of MySQL queries. This must
731 be enabled and it's described by $cfg['AllowAnywhereRecoding']
733 You can give here any charset which is in
734 $cfg['AvailableCharsets'] array and this is just default
735 choice, user can select any of them.
737 $cfg['AllowAnywhereRecoding'] boolean
738 Allow charset recoding of MySQL queries. You need recode or
739 iconv support (compiled in or module) in php to allow MySQL
740 queries recoding and used language file must have it enabled
741 (by default only these which are in unicode, just to avoid
742 losing some characters).
744 $cfg['RecodingEngine'] string
745 You can select here which functions will be used for charset
746 conversion. Possible values are:
748 + auto - automatically use available one (first is tested
750 + iconv - use iconv or libiconv functions
751 + recode - use recode_string function
755 $cfg['AvailableCharsets'] array
756 Available charsets for MySQL conversion. You can add your own
757 (any of supported by recode/iconv) or remove these which you
758 don't use. Charsets will be shown in same order as here listed,
759 so if you frequently use some of these move them to the top.
761 $cfg['LeftWidth'] integer
762 Left frame width in pixel.
764 $cfg['LeftBgColor'] string [HTML color]
765 $cfg['RightBgColor'] string [HTML color]
766 The background colors (HTML) used for both the frames.
768 $cfg['RightBgImage'] string
769 The URI of the background image used for the right frame. It
770 can be absolute as well as relative from your phpMyAdmin
773 $cfg['LeftPointerColor'] string [HTML color]
774 The color (HTML) used for the pointer in the left frame (does
777 $cfg['Border'] integer
778 The size of a table's border.
780 $cfg['ThBgcolor'] string [HTML color]
781 The color (HTML) used for table headers.
783 $cfg['BgcolorOne'] string [HTML color]
784 The color (HTML) #1 for table rows.
786 $cfg['BgcolorTwo'] string [HTML color]
787 The color (HTML) #2 for table rows.
789 $cfg['BrowsePointerColor'] string [HTML color]
790 $cfg['BrowseMarkerColor'] string [HTML color]
791 The colors (HTML) uses for the pointer and the marker in browse
792 mode (does not work with NS4).
793 The former feature highlights the row over which your mouse is
794 passing and the latter lets you visually mark/unmark rows by
796 You can disable both of these features by emptying the
797 respective directive.
799 $cfg['TextareaCols'] integer
800 $cfg['TextareaRows'] integer
801 $cfg['CharTextareaCols'] integer
802 $cfg['CharTextareaRows'] integer
803 Number of columns and rows for the textareas.
804 This value will be emphasized (*2) for sql query textareas.
805 The Char* values are used for CHAR and VARCHAR editing (if
806 configured via $cfg['CharEditing']).
808 $cfg['TextareaAutoSelect'] boolean
809 Defines if the whole textarea of the query box will be selected
812 $cfg['LimitChars'] integer
813 Maximal number of Chars showed in a TEXT OR a BLOB field on
814 browse view. Can be turned off by a toggle button on the browse
817 $cfg['ModifyDeleteAtLeft'] boolean
818 $cfg['ModifyDeleteAtRight'] boolean
819 Defines the place where modify and delete links would be put
820 when tables contents are displayed (you may have them displayed
821 both at the left and at the right). "Left" and "right" are
822 parsed as "top" and "bottom" with vertical display mode.
824 $cfg['DefaultDisplay'] string
825 There are 2 display modes: horizontal and vertical. Define
826 which one is displayed by default.
828 $cfg['UploadDir'] string
829 The name of the directory, ending with a slash, where SQL files
830 have been uploaded by other means than phpMyAdmin (for example,
831 ftp). Those files are available under a drop-down box when you
832 click the database name, then the SQL tab.
833 Please note that the file names must have the suffix ".sql".
834 This feature is useful when your file is too big to be uploaded
835 via HTTP, or when file uploads are disabled in PHP.
836 Please note that if PHP is running in safe mode, this directory
837 must be owned by the same user as the owner of the phpMyAdmin
840 $cfg['RepeatCells'] integer
841 Repeat the headers every X cells, or 0 to deactivate.
843 $cfg['SQP']['enable'] boolean
844 As of phpMyAdmin 2.3.0, we now have a fully functional SQL
845 Parser system. It is enabled by default, as it is used to
846 format the SQL queries.
847 As of 2.3.1, it will become an integral part of phpMyAdmin, as
848 it will analyze certain queries to improve the behavior of
849 phpMyAdmin. But as it is very new, and not yet heavily used, we
850 offer you an option to turn it off.
852 $cfg['SQP']['fmtType'] string [html|none]
853 The main use of the new SQL Parser is to pretty-print SQL
854 queries. By default we use HTML to format the query, but you
855 can disable this by setting this varible to 'none'
857 $cfg['SQP']['fmtInd'] float
858 $cfg['SQP']['fmtIndUnit'] string [em|px|pt|ex]
859 For the pretty-printing of SQL queries, under some cases the
860 part of a query inside a bracket is indented. By changing
861 $cfg['SQP']['fmtInd'] you can change the amount of this indent.
862 Related in purpose is $cfg['SQP']['fmtIndUnit'] which specifies
863 the units of the indent amount that you specified. This is used
866 $cfg['SQP']['fmtColor'] array of string tuples
867 This array is used to define the colours for each type of
868 element of the pretty-printed SQL queries. The tuple format is
869 class => [HTML colour code | empty string]
870 If you specify an empty string for the color of a class, it is
871 ignored in creating the stylesheet. You should not alter the
872 class names, only the colour strings.
875 + comment Applies to all comment sub-classes
876 + comment_mysql Comments as "#...\n"
877 + comment_ansi Comments as "-- ...\n"
878 + comment_c Comments as "/*...*/"
879 + digit Applies to all digit sub-classes
880 + digit_hex Hexadecimal numbers
881 + digit_integer Integer numbers
882 + digit_float Floating point numbers
883 + punct Applies to all punctuation sub-classes
884 + punct_bracket_open_round Opening brackets"("
885 + punct_bracket_close_round Closing brackets ")"
886 + punct_listsep List item seperator ","
887 + punct_qualifier Table/Column Qualifer "."
888 + punct_queryend End of query marker ";"
889 + alpha Applies to all alphabetic classes
890 + alpha_columnType Identifers matching a column type
891 + alpha_columnAttrib Identifers matching a
892 database/table/column attribute
893 + alpha_functionName Identifiers matching a MySQL function name
894 + alpha_reservedWord Identifiers matching any other reserved
896 + alpha_variable Identifers matching a SQL variable "@foo"
897 + alpha_identifier All other identifiers
898 + quote Applies to all quotation mark classes
899 + quote_double Double quotes "
900 + quote_single Single quotes '
901 + quote_backtick Backtick quotes `
903 $cfg['SQLValidator']['use'] boolean
904 phpMyAdmin now supports use of the Mimer SQL Validator service,
905 as originally published on Slashdot.
906 For help in setting up your system to use the service, see the
909 $cfg['SQLValidator']['username'] string
910 $cfg['SQLValidator']['password'] string
911 The SOAP service allows you to login with anonymous and any
912 password, so we use those by default.. Instead, if you have an
913 account with them, you can put your login details here, and it
914 will be used in place of the anonymous login.
916 $cfg['DBG']['enable'] boolean
918 Enable the DBG extension for debugging phpMyAdmin. Required for
920 For help in setting up your system to this, see the Developers
923 $cfg['DBG']['profile']['enable'] boolean
925 Enable profiling support for phpMyAdmin. This will append a
926 chunk of data to the end of every page displayed in the main
927 window with profiling statistics for that page.
928 You may need need to increase the maximum execution time for
929 this to complete successfully.
931 $cfg['DBG']['profile']['threshold'] float (units in milliseconds)
933 When profiling data is displayed, this variable controls the
934 threshold of display for any profiling data, based on the
935 average time each time has taken. If it is over the threshold
936 it is displayed, otherwise it is not displayed. This takes a
937 value in milliseconds. In most cases you don't need to edit
940 $cfg['ColumnTypes'] array
941 All possible types of a MySQL column. In most cases you don't
944 $cfg['AttributeTypes'] array
945 Possible attributes for fields. In most cases you don't need to
948 $cfg['Functions'] array
949 A list of functions MySQL supports. In most cases you don't
952 FAQ - Frequently Asked Questions
954 Server - Configuration - Limitations - Multi-user - Browsers
955 - Usage tips - Project
959 [1.1] I'm running php 4+ and my server is crashing each time a specific
960 action is required or phpMyAdmin sends a blank page or a page full of
961 cryptic characters to my browser, what can I do
963 There are some known php bugs with output buffering and compression.
964 Try to set the $cfg['OBGzip'] directive to FALSE in your
965 config.inc.php or .php3 file and the zlib.output_compression directive
966 to Off in your php configuration file.
967 Furthermore, we know about such problems connected to the release
968 candidates of php 4.2.0 (tested with php 4.2.0 RC1 to RC4) together
969 with MS Internet Explorer. Please upgrade to the release version php
972 [1.2] My Apache server crashes when using phpMyAdmin
974 You should first try the latest versions of Apache (and possibly
976 See also the other FAQ entry about php bugs with output buffering.
977 If your server keeps crashing, please ask for help in the various
978 Apache support groups.
980 [1.3] I'm running phpMyAdmin with "cookie" authentication mode under PHP
981 4.2.0 or 4.2.1 loaded as an Apache 2+ module but can't enter the script:
982 I'm always displayed the login screen
984 This is a known PHP bug (see this bug report) from the official php
985 bug database. It means there is and won't be any phpMyAdmin fix
986 against it because there is no way to code a fix.
988 [1.4] Using phpMyAdmin on IIS, I'm displayed the error message: "The
989 specified CGI application misbehaved by not returning a complete set of
992 You just forgot to read the install.txt file from the php
993 distribution. Have a look at the last message in this bug report from
994 the official php bug database.
996 [1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error
997 messages with the http or advanced authentication mode
999 This is a known problem with the php ISAPI filter: it's not so stable.
1000 For some more information and complete testings see the messages
1001 posted by André B. aka "djdeluxe76" in this thread from the phpWizard
1003 Please use instead the cookie authentication mode.
1005 [1.6] I can't use phpMyAdmin on PWS: nothing is displayed!
1007 This seems to be a PWS bug. Filippo Simoncini found a workaroud (at
1008 this time there is no better fix): remove or comment the DOCTYPE
1009 declarations (2 lines) from the scripts header.inc.php3,
1010 header_printview.inc.php3, index.php3, left.php3 and
1011 libraries/common.lib.php3.
1013 [1.7] How can I GZip or Bzip a dump or a CSV export. It seems to not work
1015 These features are based on the gzencode() and bzcompress() php
1016 functions to be more independent of the platform (Unix/Windows, Safe
1017 Mode or not, and so on). So, you must have PHP4 >= 4.0.4 and
1018 Zlib/Bzip2 support (--with-zlib and --with-bz2).
1019 We faced php crashes when trying to download a dump with MS Internet
1020 Explorer when phpMyAdmin is run with a release candidate of php 4.2.0.
1021 In this case you should switch to the release version of php 4.2.0.
1023 [1.8] I cannot insert a text file in a table, and I get an error about safe
1024 mode being in effect
1026 Your uploaded file is saved by PHP in the "upload dir", as defined in
1027 php.ini by the variable upload_tmp_dir (usually the system default is
1029 We recommend the following setup for Apache servers running in safe
1030 mode, to enable uploads of files while being reasonably secure:
1031 * create a separate directory for uploads: mkdir /tmp/php
1032 * give ownership to the Apache server's user.group: chown
1033 apache.apache /tmp/php
1034 * give proper permission: chmod 600 /tmp/php
1035 * put upload_tmp_dir = /tmp/php in php.ini
1038 [1.9] I'm having troubles when uploading files. In general file uploads
1039 don't work on my system and uploaded files have a Content-Type: header in
1042 It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat
1043 7.0 and you updated your php rpm to php-4.0.4pl1-3.i386.rpm, didn't
1045 So the problem is that this package has a serious bug that was
1046 corrected ages ago in php (2001-01-28: see php's bug tracking system
1047 for more details). The problem is that the bugged package is still
1048 available though it was corrected (see redhat's bugzilla for more
1050 So please download the fixed package (4.0.4pl1-9) and the problem
1052 And that fixes the \r\n problem with file uploads!
1054 [1.10] I'm having troubles when uploading files with phpMyAdmin running on
1055 a secure server. My browser is Internet Explorer and I'm using the Apache
1058 As suggested by "Rob M" in the phpWizard forum, add this line to your
1060 SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
1061 It seems to clear up many problems between IE and SSL.
1063 [1.11] I get an 'open_basedir restriction' while uploading a file from the
1066 Since version 2.2.4, phpMyAdmin supports servers with open_basedir
1067 restrictions. Assuming that the restriction allows you to open files
1068 in the current directory ('.'), all you have to do is create a 'tmp'
1069 directory under the phpMyAdmin install directory, with permissions 777
1070 and the same owner as the owner of your phpMyAdmin directory. The
1071 uploaded files will be moved there, and after execution of your SQL
1074 [1.12] I have lost my MySQL root password, what can I do
1076 The MySql manual explains how to reset the permissions.
1078 [1.13] I get an error 'No SQL query' when trying to execute a bookmark
1080 If PHP does not have read/write access to its upload_tmp_dir, it
1081 cannot access the uploaded query.
1083 [1.14] I get an error 'No SQL query' when trying to submit a query from the
1084 convenient text area
1086 Check the post_max_size directive from your php configuration file and
1089 [1.15] I have problems with mysql.user field names
1091 In older MySQL versions, the User and Password fields were named user
1092 and password. Please modify your field names to align with current
1095 [1.16] I cannot upload big dump files
1097 The first things to check (or ask your host provider to check) are the
1098 values of upload_max_filesize, memory_limit and post_max_size in the
1099 php.ini configuration file.
1100 All of these three settings limit the maximum size of data that can be
1101 submitted and handled by php. One user also said that post_max_size
1102 and memory_limit need to be larger than upload_max_filesize.
1104 [1.17] Does phpMyAdmin support MySQL 4
1106 MySQL 4 is not yet fully supported by phpMyAdmin.
1107 Because of MySQL 4's backwards compatibility you can use phpMyAdmin
1108 for administering MySQL 4 servers, but phpMyAdmin does not yet support
1109 its new features. Please notice that in this case it is recommended to
1110 use php >= 4.1 since older versions of php are not compatible to
1112 Furthermore, several users reported problems with phpMyAdmin related
1113 to bugs in MySQL 4. MySQL 4 is still a beta release and should be used
1114 for test purposes only! Because of a major change in the definition
1115 syntax of string field types, this version of phpMyAdmin probably
1116 won't work correctly with MySQL >= 4.1.0! We will work on the support
1117 as soon as MySQL 4.1.0 is released.
1119 [1.18] I'm running MySQL <= 4.0.1 having lower_case_table_names set to 1.
1120 If I create a new table with a capital letter in its name it is changed to
1121 lowercase as it should. But if I try to DROP this table MySQL is unable to
1122 find the corresponding file
1124 This is a bug of MySQL <= 4.0.1. Please upgrade to at least
1125 MySQL 4.0.2 or turn off your lower_case_table_names directive.
1127 [1.19] I can't run the "display relations" feature because the script seems
1128 not to know the font face I'm using!
1130 The "FPDF" library we're using for this feature requires some special
1131 files to use font faces.
1132 Please refers to the FPDF manual to build these files.
1134 [1.20] I receive the error "cannot load MySQL extension, please check PHP
1137 To connect to a MySQL server, PHP needs a set of MySQL functions
1138 called "MySQL extension". This extension may be part of the PHP server
1139 (compiled-in), otherwise it needs to be loaded dynamically. Its name
1140 is probably mysql.so or mysql.dll. phpMyAdmin tried to load the
1141 extension but failed.
1142 Usually, the problem is solved by installing a software package called
1143 "PHP-MySQL" or something similar.
1145 [1.21] I am running the CGI version of PHP under Unix, and I cannot login
1148 In php.ini, set mysql.max_links higher than 1.
1150 [1.22] I don't see the "Location of text file" field, so I cannot upload
1152 This is most likely because in php.ini, your file_uploads parameter is
1155 [1.23] I'm running MySQL on a Win32 machine. Each time I create a new table
1156 the table and field names are changed to lowercase!
1158 This happens because the MySQL directive lower_case_table_names
1159 defaults to 1 (ON) in the Win32 version of MySQL. You can change this
1160 behavior by simply changing the directive to 0 (OFF):
1161 Just edit you my.ini file that should be located in your Windows
1162 directory and add the following line:
1163 lower-case-table-names=0
1164 Next, save the file and restart the MySQL service. You can always
1165 check the value of this directive using the query
1166 SHOW VARIABLES LIKE 'lower_case_table_names';
1168 [1.24] Some characters are being truncated in my queries, or I get
1169 characters randomly added. I am running PHP 4.2.3
1171 This is a PHP 4.2.3 bug.
1173 [1.25] I am running Apache with mod_gzip-1.3.26.1a on Windows XP, and I get
1174 problems, such as undefined variables when I run a SQL query
1176 A tip from Jose Fandos: put a comment on the following two lines in
1177 httpd.conf, like this:
1178 # mod_gzip_item_include file \.php$
1179 # mod_gzip_item_include mime "application/x-httpd-php.*"
1180 as this version of mod_gzip on Apache (Windows) has problems handling
1181 php scripts. Of course you have to restart Apache.
1183 [1.26] I just installed phpMyAdmin in my document root of IIS but I get the
1184 error "No input file specified" when trying to run phpMyAdmin.
1186 This is a permission problem. Right-click on the phpmyadmin folder and
1187 choose properties. Under the tab Security, click on "Add" and select
1188 the user "IUSER_machine" from the list. Now set his permissions and it
1191 [1.27] I get empty page when I want to view huge page (eg.
1192 db_details_structure.php3 with plenty of dabases)
1194 This is a PHP bug that occur when GZIP output buffering enabled. If
1195 you turn off it (by $cfg['OBGzip'] = FALSE in config.inc.php3), it
1196 should work. This bug will be fixed in PHP 5.0.0.
1200 [2.1] The error message "Warning: Cannot add header information - headers
1201 already sent by ..." is displayed, what's the problem
1203 Edit your config.inc.php or .php3 file and ensure there is nothing (ie
1204 no blank lines, no spaces, no characters...) neither before the <?php
1205 tag at the beginning, neither after the ?> tag at the end.
1207 [2.2] phpMyAdmin can't connect to MySQL. What's wrong
1209 Either there is an error with your PHP setup or your username/password
1210 is wrong. Try to make a small script which uses mysql_connect and see
1211 if it works. If it doesn't, it may be you haven't even compiled MySQL
1214 [2.3] The error message "Warning: MySQL Connection Failed: Can't connect to
1215 local MySQL server through socket '/tmp/mysql.sock' (111)..." is displayed.
1218 For RedHat users, Harald Legner suggests this on the mailing list:
1219 On my RedHat-Box the socket of mysql is /var/lib/mysql/mysql.sock. In
1220 your php.ini you will find a line
1221 mysql.default_socket = /tmp/mysql.sock
1223 mysql.default_socket = /var/lib/mysql/mysql.sock
1224 Then restart apache and it will work.
1225 Here is a fix suggested by Brad Ummer in the phpwizard forum:
1226 * First, you need to determine what socket is being used by MySQL.
1227 To do this, telnet to your server and go to the MySQL bin
1228 directory. In this directory there should be a file named
1229 mysqladmin. Type ./mysqladmin variables, and this should give you
1230 a bunch of info about your MySQL server, including the socket
1231 (/tmp/mysql.sock, for example).
1232 * Then, you need to tell PHP to use this socket.
1233 Assuming you are using PHP 3.0.10 or better, you can specify the
1234 socket to use when you open the connection. To do this in
1235 phpMyAdmin, you need to complete the socket information in the
1237 For example: $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';
1239 Have also a look at the corresponding section of the MySQL
1242 [2.4] Nothing is displayed by my browser when I try to run phpMyAdmin, what
1245 Try to set the $cfg['OBGZip'] directive to FALSE in the phpMyAdmin
1246 configuration file. It helps sometime.
1247 Also have a look at your php version number: if it contains "4.0b..."
1248 it means you're running a beta version of PHP. That's not a so good
1249 idea, please upgrade to a plain revision.
1251 [2.5] Each time I want to insert or change a record or drop a database or a
1252 table, an error 404 (page not found) is displayed or, with http or cookie
1253 authentication, I'm asked to login again. What's wrong
1255 Check the value you set for the $cfg['PmaAbsoluteUri'] directive in
1256 the phpMyAdmin configuration file.
1258 [3. Known limitations]
1260 [3.1] When using http authentication, an user who logged out can not relog
1261 in with the same nick
1263 This is related to the authentication mechanism (protocol) used by
1264 phpMyAdmin. We plan to change it as soon as we may find enough free
1265 time to do it, but you can bypass this problem: just close all the
1266 opened browser windows and then go back to phpMyAdmin. You should be
1267 able to logs in again.
1269 [3.2] When dumping a large table in compressed mode, I get a memory limit
1270 error or a time limit error
1272 As of version 2.2.4, we build the compressed dump in memory, so large
1273 tables dumps may hang. The only alternative we can think about (using
1274 system calls to mysqldump then gzip or bzip2) would not be applicable
1275 in environments where PHP is in safe mode: access to system programs
1276 is is limited by the system administrator, and time limit is enforced.
1278 [3.3] With InnoDB tables, I lose foreign key relationships when I rename or
1281 This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep
1282 in mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
1284 [3.4] I am unable to import dumps I created with the mysqldump tool bundled
1285 with the MySQL server distribution
1287 The problem is that mysqldump creates invalid comments like this:
1290 -- Host: localhost Database: database
1291 ---------------------------------------------------------
1292 -- Server version 3.23.54
1294 The invalid part of the code is the horizontal line made of dashes
1295 that appears once in every dump created with mysqldump. If you want to
1296 run your dump you have to turn it into valid MySQL. This means, you
1297 have to add a whitespace after the first to dashes of the line or add
1299 -- -------------------------------------------------------
1301 #---------------------------------------------------------
1303 [4. ISPs, multi-user installations ]
1305 [4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I need
1306 to install it for each customer
1308 Since version 2.0.3, you can setup a central copy of phpMyAdmin for
1309 all your users. The development of this feature was kindly sponsored
1310 by NetCologne GmbH. This requires a properly setup MySQL user
1311 management and phpMyAdmin http or cookie authentication. See the
1312 install section on "Using http authentication".
1314 [4.2] What's the preferred way of making phpMyAdmin secure against evil
1317 This depends on your system.
1318 If you're running a server which cannot be accessed by other people,
1319 it's sufficient to use the directory protection bundled with your
1320 webserver (with Apache you can use .htaccess files, for example).
1321 If other people have telnet access to your server, you should use
1322 phpMyAdmin's http authentication feature.
1324 * Your config.inc.php3 file should be chmod 660.
1325 * All your phpMyAdmin files should be chown phpmy.apache, where
1326 phpmy is a user whose password is only known to you, and apache is
1327 the group under which Apache runs.
1328 * You should use PHP safe mode, to protect from other users that try
1329 to include your config.inc.php3 in their scripts.
1331 [4.3] I get errors about not being able to include a file in /lang or in
1334 Check php.ini, or ask your sysadmin to check it. The include_path must
1335 contain "." somewhere in it, and open_basedir, if used, must contain
1336 "." and "./lang" to allow normal operation of phpMyAdmin.
1338 [4.4] phpMyAdmin always gives "Access denied" when using http
1341 This could happen for several reasons:
1342 * $cfg['Servers'][$i]['controluser'] and/or
1343 $cfg['Servers'][$i]['controlpass'] are wrong.
1344 * The username/password you specify in the login-dialog are invalid.
1345 * You have already setup a security mechanism for the
1346 phpMyAdmin-directory, eg. a .htaccess file. This would interfere
1347 with phpMyAdmin's authentication, so remove it.
1349 [4.5] Is it possible to let users create their own databases
1351 Starting with 2.2.5, in the user management page, you can enter a
1352 wildcard database name for a user, and put the privileges you want.
1353 For example, adding SELECT, INSERT, UPDATE, DELETE, CREATE, DROP,
1354 INDEX, ALTER would let a user create/manage his/her database(s).
1356 [4.6] How can I use the Host-based authentication additions
1358 If you have existing rules from an old .htaccess file, you can take
1359 them and add a username between the 'deny'/'allow' and 'from' strings.
1360 Using the username wildcard of '%' would be a major benefit here if
1361 your installation is suited to using it. Then you can just add those
1362 updated lines into the $cfg['Servers'][$i]['AllowDeny']['rules']
1364 If you want a pre-made sample, you can try this fragment. It stops the
1365 'root' user from logging in from any networks other than the private
1367 //block root from logging in except from the private networks
1368 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
1369 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
1370 'deny root from all',
1371 'allow root from localhost',
1372 'allow root from 10.0.0.0/8',
1373 'allow root from 192.168.0.0/16',
1374 'allow root from 172.16.0.0/12',
1377 [5. Browsers or client OS]
1379 [5.1] I get an out of memory error, and my controls are non-functional,
1380 when trying to create a table with more than 14 fields
1382 We could reproduce this problem only under Win98/98SE. Testing under
1383 WinNT4 or Win2K, we could easily create more than 60 fields.
1384 A workaround is to create a smaller number of fields, then come back
1385 to your table properties and add the other fields.
1387 [5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields
1389 This is not a phpMyAdmin problem but a Xitami known bug: you'll face
1390 it with each script/website that use forms.
1391 Upgrade or downgrade your Xitami server.
1393 [5.3] I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2)
1395 With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except
1396 that the proposed file name for the dump is always 'tbl_dump.php'.
1397 Bzip2 dumps don't seem to work.
1398 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into the
1399 user's temporary directory, so they must be moved before closing
1400 Konqueror, or else they disappear. Gzip dumps give an error message.
1401 Testing needs to be done for Konqueror 2.2.2.
1403 [5.4] I can't use the cookie authentication mode because Internet Explorer
1404 never stores the cookies
1406 MS Internet Explorer seems to be really buggy about cookies, at least
1407 till version 6. And thanks to Andrew Zivolup we've traced also a php
1408 4.1.1 bug in this area!
1409 Then, if you're running php 4.1.1, try to upgrade or downgrade... it
1412 [5.5] In Internet Explorer 5.0, I get Javascript errors when browsing my
1415 Upgrade to at least Internet Explorer 5.5SP2.
1417 [5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying to
1418 modify a row in a table with many fields, or with a text field
1420 Your table neither have a primary key nor an unique one, so we must
1421 use a long URL to identify this row. There is a limit on the lenght of
1422 the URL in those browsers, and this not happen in Netscape, for
1423 example. The workaround is to create a primary or unique key, or use
1426 [5.7] I refresh (reload) my browser, and come back to the welcome page
1428 Some browsers support right-clicking into the frame you want to
1429 refresh, just do this in the right frame.
1431 [5.8] With Mozilla 0.9.7 I have problems sending a query modified in the
1434 Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future
1437 [5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
1438 whitespace in the SQL-Query edit area: the page scrolls down
1440 This is a Mozilla bug (see bug #26882 at Bugzilla).
1442 [5.10] With Netscape 4.75 I get empty rows between each row of data in a
1445 This is a known Netscape 4.75 bug: it adds some line feeds when
1446 exporting data in octet-stream mode. Since we can't detect the
1447 specific Netscape version, we cannot workaround this bug.
1449 [5.11] Extended-ASCII characters like German umlauts are displayed wrong
1451 Please ensure that you have set your browser's charset to the one of
1452 the language file you have selected on phpMyAdmin's start page.
1453 Alternatively, you can try the auto detection mode that is supported
1454 by the recent versions of the most browsers.
1456 [5.12] Apple OS X: Safari browser changes special characters to "?"
1458 This issue has been reported by a OS X user, who adds that Chimera,
1459 Netscape and Mozilla do not have this problem.
1461 [5.13] With Internet Explorer 5.5 or 6, and http authentication type, I
1462 cannot manage two servers: I login to the first one, then the other one,
1463 but if I switch back to the first, I have to login on each operation.
1465 This is a bug in Internet Explorer, other browsers do not behave this
1468 [6. Using phpMyAdmin]
1470 [6.1] I can't insert new rows into a table / I can't create a table - MySQL
1471 brings up a SQL-error
1473 Examine the SQL error with care. Often the problem is caused by
1474 specifying a wrong field-type.
1475 Common errors include:
1476 * Using VARCHAR without a size argument
1477 * Using TEXT or BLOB with a size argument
1479 Also, look at the syntax chapter in the MySQL manual to confirm that
1480 your syntax is correct.
1482 [6.2] When I create a table, I click the Index checkbox for 2 fields and
1483 phpMyAdmin generates only one index with those 2 fields
1485 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a
1486 multi-fields index. If you want two indexes, create the first one when
1487 creating the table, save, then display the table properties and click
1488 the Index link to create the other index.
1490 [6.3] How can I insert a null value into my table
1492 Since version 2.2.3, you have a checkbox for each field that can be
1493 null. Before 2.2.3, you had to enter "null", without the quotes, as
1496 [6.4] How can I backup my database or table
1498 Click on a database or table name in the left frame, the properties
1499 will be displayed. Then on the menu, click "Export", you can dump the
1500 structure, the data, or both. This will generate standard SQL
1501 statements that can be used to recreate your database/table.
1502 You will need to choose "Save as file", so that phpMyAdmin can
1503 transmit the resulting dump to your station. Depending on your PHP
1504 configuration, you will see options to compress the dump. See also the
1505 $cfg['ExecTimeLimit'] configuration variable.
1506 For additional help on this subject, look for the word "dump" in this
1509 [6.5] How can I restore (upload) my database or table using a dump? How can
1512 Click on a database name in the left frame, the properties will be
1513 local displayed. Then in the "Run SQL query" section, type in your
1514 dump filename, or use the Browse button. Then click Go.
1515 For additional help on this subject, look for the word "upload" in
1518 [6.6] How can I use the relation table in Query-by-example
1520 Here is an example with the tables persons, towns and countries, all
1521 located in the database mydb. If you don't have a PMA_relation table,
1522 create it as explained in the configuration section. Then create the
1524 CREATE TABLE REL_countries (
1525 country_code char(1) NOT NULL default '',
1526 description varchar(10) NOT NULL default '',
1527 PRIMARY KEY (country_code)
1529 INSERT INTO REL_countries VALUES ('C', 'Canada');
1530 CREATE TABLE REL_persons (
1531 id tinyint(4) NOT NULL auto_increment,
1532 person_name varchar(32) NOT NULL default '',
1533 town_code varchar(5) default '0',
1534 country_code char(1) NOT NULL default '',
1537 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
1538 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
1539 CREATE TABLE REL_towns (
1540 town_code varchar(5) NOT NULL default '0',
1541 description varchar(30) NOT NULL default '',
1542 PRIMARY KEY (town_code)
1544 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
1545 INSERT INTO REL_towns VALUES ('M', 'Montréal');
1546 To setup appropriate links and display information:
1547 * on table "REL_persons" click Structure, then Relation view
1548 * in Links, for "town_code" choose "REL_towns->code"
1549 * in Links, for "country_code" choose "REL_countries->country_code"
1550 * on table "REL_towns" click Structure, then Relation view
1551 * in "Choose field to display", choose "description"
1552 * repeat the two previous steps for table "REL_countries"
1554 Then test like this:
1555 * Click on your db name in the left frame
1557 * Use tables: persons, towns, countries
1558 * Click "Update query"
1559 * In the fields row, choose persons.person_name and click the "Show"
1561 * Do the same for towns.description and countries.descriptions in
1563 * Click "Update query" and you will see in the query box that the
1564 correct joins have been generated
1565 * Click "Submit query"
1567 [6.7] How can I use the "display field" feature
1569 Starting from the previous example, create the PMA_table_info as
1570 explained in the configuration section, then browse your persons
1571 table, and move the mouse over a town code or country code.
1573 [6.8] How can I produce a PDF schema of my database
1575 First you have to fill the "relation", "table_coords" and "pdf_pages"
1576 configuration variables.
1577 Then, think about your schema layout: which tables will go on which
1579 * Click on your db name in the left frame
1580 * Choose "Structure" in the navigation on top
1581 * Choose "Edit PDF Pages" which should be somewhere at the bottom of
1583 * Enter the name for a first pdf page and submit
1584 * Choose this page to edit
1585 * Now add a table you want to show on this page and it's coordinates
1587 First you will have to guess this coordinates of course, so just
1588 expect to have an area of about 297 * 210 and put the tables
1589 coordinates somewhere in there, you will be able to have a look at
1590 what happened and change them later.
1591 For example, x=100 and y=200 means that the table will be at 200
1592 mm down and 100 mm right from the upper left corner.
1593 Actually if you have a width of more than 300 or a height of more
1594 than 200 than it will automatically be scaled but 300*100 is a
1595 good start to have an idea of what coordinates to use.
1596 * After every table you submitted you will have the possibility to
1598 * When you have entered enough tables Click on your db name in the
1600 * Now, again at the bottom of the page you should be able to choose
1601 "Display PDF schema"
1602 For testing it might be useful to show the grid as well, so you
1603 can see the coordinates used.
1604 Maybe also choose color and submit.
1605 * Save the file he will offer you to something like Schema.pdf
1606 (Internet Explorer has some bug there which might make it offer it
1607 without an extension. Under Windows it is important to have the
1608 extension ".pdf", under other OSes you should be fine just saving
1609 the file under the name it offers).
1611 [6.9] phpMyAdmin is changing the type of one of my columns!
1613 No, it's MySQL that is doing silent column type changing.
1615 [6.10] My database has an underscore in it's name, and when I grant
1616 privileges to a user for this database, a backslash is added before the
1619 This is normal and means that the grant is done only for this
1620 database. If there was no backslash, this would be a wildcard grant,
1621 and the underscore would mean "any character". So, if the database
1622 name is "john_db", the user would get rights to john1db, john2db...
1623 instead of just john_db.
1624 If you really want to grant using a wildcard, there is a dialog box "
1625 Database (wildcards allowed)" for this.
1627 [6.11] What is the curious symbol ø in the table statistics
1631 [6.12] I want to understand some Export options
1633 "Complete inserts" adds the column names on every INSERT command, for
1634 better documentation (but resulting file is bigger).
1635 "Extended inserts" provides a shorter dump file by using only once the
1636 INSERT verb and the table name.
1637 "Enclose table and field names with backquotes" ensures that field and
1638 table names formed with special characters are protected.
1640 [6.13] I would like to create a database with a dot in its name
1642 This is a bad idea, because in MySQL the syntax "database.table" is
1643 the normal way to reference a database and table name. Worse, MySQL
1644 will usually let you create a database with a dot, but then you cannot
1645 work with it, nor delete it.
1647 [6.14] How do I set up the SQL validator
1649 To use it, you need a very recent version of PHP, 4.3.0 recommended,
1650 with XML, PCRE and PEAR support. On your system command line, run
1651 "pear install Net_Socket Net_URL HTTP_Request Mail_Mime Net_DIME SOAP"
1652 to get the nessecary PEAR modules for usage.
1653 If you use it, you should be aware that any SQL statement you submit
1654 will be stored anonymously (database/table/column names, strings,
1655 numbers replaced with generic values). The Mimer SQL Validator itself,
1656 is © 2001 Upright Database Technology. We utilize it as free SOAP
1659 [6.15] I want to add a BLOB field and put an index on it, but MySQL says
1660 "BLOB column '...' used in key specification without a key length"
1662 The right way to do this, is to create the field without any indexes,
1663 then display the table structure and use the "Create an index" dialog.
1664 On this page, you will be able to choose your BLOB field, and set a
1665 size to the index, which is the condition to create an index on a BLOB
1668 [6.16] How can I simply move in page with plenty editing fields
1670 You can use Ctrl+arrows for moving on most pages with plenty editing
1671 fields (table structure changes, row editing, etc.).
1673 [6.17] Why is there checkbox called "Binary" when uplaoding file into
1676 It defines how data will be inserted into MySQL. When not checked, the
1677 data from file will be treated as text, if charset conversion is
1678 enabled (you are using utf-8 translation) charset of the text will be
1679 converted according to it and could possibly be displayed as part of
1680 update SQL after upload. When checked data will be inserted as
1681 hexadecimal value and so will be in database exactly as in file. In
1682 most cases you should keep it checked.
1684 [7. phpMyAdmin project]
1686 [7.1] I have found a bug. How do I inform developers
1688 Our Bug Tracker is located at
1689 http://sourceforge.net/projects/phpmyadmin/ under the Bugs section.
1690 But please first discuss your bug with other users:
1691 http://sourceforge.net/projects/phpmyadmin/ (and choose Forums)
1693 [7.2] I want to translate the messages to a new language or upgrade an
1694 existing language, where do I start
1696 Always use the current cvs version of your language file. For a new
1697 language, start from english-iso-8859-1.inc.php3. If you don't know
1698 how to get the cvs version, please ask one of the developers.
1699 Please note that we try not to use html entities like é in the
1700 translations, since we define the right character set in the file.
1701 With html entities, the text on buttons would not display correctly.
1702 You can then put your translations, as a zip file to avoid losing
1703 special characters, on the sourceforge.net translation tracker.
1704 It would be a good idea to subscribe to the phpmyadmin-translators
1705 mailing list, because this is where we ask for translations of new
1708 [7.3] I would like to help out with the development of phpMyAdmin. How
1711 The following method is preferred for new developers:
1712 1. fetch the current CVS tree over anonymous CVS:
1714 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmy
1716 [Password: simply press the Enter key]
1718 -d:pserver:anonymous@cvs.phpmyadmin.sourceforge.net:/cvsroot/phpmy
1719 admin checkout phpMyAdmin
1720 [This will create a new sub-directory named phpMyAdmin]
1722 3. put the modified files (tar'ed and gzip'ed) inside the patch
1723 tracker of the phpMyAdmin SourceForge account.
1725 Write access to the CVS tree is granted only to experienced developers
1726 who have already contributed something useful to phpMyAdmin.
1727 Also, have a look at the Developers section.
1729 Developers Information
1731 phpMyAdmin is Open Source, so you're invited to contribute to it. Many
1732 great features have been written by other people and you too can help
1733 to make phpMyAdmin a useful tool.
1735 If you're planning to contribute source, please read the following
1737 * All files include header.inc.php3 (layout),
1738 libraries/common.lib.php3 (common functions) and config.inc.php3.
1739 All configuration data belongs in config.inc.php3. Please keep it
1740 free from other code.
1741 Commonly used functions should be added to
1742 libraries/common.lib.php3 and more specific ones may be added
1743 within a library stored into the libraries sub-directory.
1744 * Obviously, you're free to use whatever coding style you want. But
1745 please try to keep your code as simple as possible: beginners are
1746 using phpMyAdmin as an example application.
1747 As far as possible, we want the scripts to be XHTML1.0 and CSS2
1748 compliant on one hand, they fit the PEAR coding standards on the
1749 other hand. Please pay attention to this.
1750 * Please try to keep up the file-naming conventions. Table-related
1751 stuff goes to tbl_*.php3, db-related code to db_*.php3,
1752 server-related tools to server_*.php3 and so on.
1753 * Please don't use verbose strings in your code, instead add the
1754 string (at least) to english-iso-8859-1.inc.php3 and print() it
1756 * If you want to be really helpful, write an entry for the
1758 * The DBG extension (PHP Debugger DBG) is now supported by
1759 phpMyAdmin for developers to better debug and profile their code.
1760 Please see the $cfg['DBG']* configuration options for more
1762 This is in memorium of the Space Shuttle Columbia (STS-107) which
1763 was lost during its re-entry into Earth's atmosphere and in memory
1764 of the brave men and women who gave their lives for the people of
1770 phpMyAdmin - Credits
1771 ====================
1773 CREDITS, in chronological order
1774 -------------------------------
1776 - Tobias Ratschiller <tobias.ratschiller_at_maguma.com>
1777 * creator of the phpmyadmin project
1778 * maintainer from 1998 to summer 2000
1780 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
1781 * multi-language version
1782 * various fixes and improvements
1783 * project co-administrator
1785 - Olivier Müller <om_at_omnis.ch>
1786 * started SourceForge phpMyAdmin project in March 2001
1787 * sync'ed different existing CVS trees with new features and bugfixes
1788 * multi-language improvements, dynamic language selection
1789 * current project maintainer
1790 * many bugfixes and improvements
1792 - Loïc Chapeaux <lolo_at_phpheaven.net>
1793 * rewrote and optimized javascript, DHTML and DOM stuff
1794 * rewrote the scripts so they fit the PEAR coding standards and
1795 generate XHTML1.0 and CSS2 compliant codes
1796 * improved the language detection system
1797 * many bugfixes and improvements
1799 - Robin Johnson <robbat2_at_users.sourceforge.net>
1800 * database maintence controls
1802 * Host authentication IP Allow/Deny
1803 * DB-based configuration (Not completed)
1806 * many bugfixes and improvements
1808 - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
1810 * multiple dump feature
1814 - Geert Lund <glund_at_silversoft.dk>
1816 * moderator of the phpMyAdmin users forum at phpwizard.net
1818 - Korakot Chaovavanich <korakot_at_iname.com>
1819 * "insert as new row" feature
1821 - Pete Kelly <webmaster_at_trafficg.com>
1822 * rewrote and fix dump code
1825 - Steve Alberty <alberty_at_neptunlabs.de>
1826 * rewrote dump code for PHP4
1827 * mySQL table statistics
1830 - Benjamin Gandon <gandon_at_isia.cma.fr>
1831 * main author of the version 2.1.0.1
1834 - Alexander M. Turek <rabus_at_bugfixes.info>
1836 * MySQL 4 related features
1837 * various small features and fixes
1838 * German language file updates
1840 - Mike Beck <mike.beck_at_ibmiller.de>
1841 * automatic joins in QBE
1842 * links column in printview
1845 - Michal Cihar <nijel_at_users.sourceforge.net>
1846 * enhanced index creation/display feature
1847 * feature to use a different charset for HTML than for MySQL
1848 * Czech language file updates
1850 - Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
1851 (http://sourceforge.net/projects/phpmysqlformgen/)
1852 * suggested the patch for multiple table printviews
1854 - Garvin Hicking <hicking_at_faktor-e.de>
1855 * built the patch for vertical display of table rows
1857 - Yukihiro Kawada <kawada_at_den.fujifilm.co.jp>
1858 * japanese kanji encoding conversion feature
1860 - Piotr Roszatycki <d3xter_at_users.sourceforge.net> and Dan Wilson
1861 * the Cookie authentication mode
1863 - Axel Sander <n8falke_at_users.sourceforge.net>
1864 * table relation-links feature
1866 - Maxime Delorme <delorme.maxime_at_free.fr>
1867 * PDF schema output, thanks also to Olivier Plathey for the
1868 "FPDF" library (see http://www.fpdf.org/).
1870 - Olof Edlund <olof.edlund_at_upright.se>
1871 * SQL validator server
1873 - Ivan R. Lanin <ivanlanin_at_users.sourceforfe.net>
1876 And also to the following people who have contributed minor changes,
1877 enhancements, bugfixes or support for a new language since version 2.1.0:
1879 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
1880 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
1881 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
1882 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
1883 Bernard M. Piller, Laurent Haas, "Sakamoto", Yuval Sarna,
1884 www.securereality.com.au, Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky,
1885 Rachim Tamsjadi, Kositer Uros, Luís V., Martijn W. van der Lee,
1886 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
1887 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas.
1890 Original Credits of Version 2.1.0
1891 ---------------------------------
1893 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
1894 to create a web-based interface to MySQL using PHP3. Although I have not
1895 used any of his source-code, there are some concepts I've borrowed from
1896 him. phpMyAdmin was created because Peter told me he wasn't going to
1897 further develop his (great) tool.
1899 - Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
1900 code for the check when dropping a table or database. He also suggested
1901 that you should be able to specify the primary key on tbl_create.php3. To
1902 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
1903 well as a bug-report. Plus many smaller improvements.
1904 - Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
1905 were introduced in 1.3.0 (including quite significant ones like the
1906 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
1908 - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
1909 language-independent by outsourcing the strings to a separate file. He
1910 also contributed the French translation.
1911 - Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
1912 tbl_select.php3, a feature to display only some fields from a table.
1913 - Chris Jackson <chrisj_at_ctel.net> added support for MySQL
1914 functions in tbl_change.php3. He also added the
1915 "Query by Example" feature in 2.0.
1916 - Dave Walton <walton_at_nordicdms.com> added support for multiple
1917 servers and is a regular contributor for bug-fixes.
1918 - Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
1920 The following people have contributed minor changes, enhancements, bugfixes
1921 or support for a new language:
1922 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
1923 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
1924 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
1927 And thanks to everyone else who sent me email with suggestions, bug-reports
1928 and or just some feedback.
1930 Valid XHTML 1.0! Valid CSS!