phpMyAdmin can manage a whole MySQL-server (needs a super-user) but also a single database. To accomplish the latter you'll need a properly set up MySQL-user who can read/write only the desired database. It's up to you to look up the appropriate part in the MySQL manual. Currently phpMyAdmin can:
| (*) | phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dumps and CSV exports if you use PHP4 >= 4.0.4 with Zlib support (--with-zlib) and/or Bzip2 support (--with-bz2). |
NOTE: phpMyAdmin does not apply any special security methods to the MySQL database server. It is still the sysadmin's job to grant permissions on the MySQL databases properly.
Warning for Mac users: php seems not to like
Mac end of lines character ("\r") and Stuffit unstuffs
with Mac formats, of course.
So you'll have to resave as in Bbedit to unix style ALL phpMyAdmin scripts
before uploading them to your server.
Documentation warning: when you see in this document a .php3 file extension, please transpose to .php if you are using a kit with files having this extension.
Quick Install:
Upgrading from an older version:
Using authentication modes:
|
GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass'; GRANT SELECT (Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv) ON mysql.user TO 'pma'@'localhost'; GRANT SELECT ON mysql.db TO 'pma'@'localhost'; GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv) ON mysql.tables_priv TO 'pma'@'localhost'; |
|
| ... and if you want to use the many new relation and bookmark features: | |
| GRANT SELECT, INSERT, UPDATE, DELETE ON <pma_db> TO 'pma'@'localhost'; (this of course requires you to have a special DB for phpMyAdmin, the contents will be explained later) | |
'http' authentication mode:
'cookie' authentication mode:
'config' authentication mode:
Warning for Mac users: php seems not to like Mac end of lines character ("\r"). So ensure you choose the option that allows to use the *nix end of line character ("\n") in your text editor before registering a script you have modified.
All configurable data is placed in config.inc.php3.
$cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
. $_SERVER['HTTP_HOST']
. (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
. substr($_SERVER['PHP_SELF'], 0, strrpos($_SERVER['PHP_SELF'], '/')+1);
or
$cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
. $_SERVER['SERVER_NAME']
. (!empty($_SERVER['SERVER_PORT']) ? ':' . $_SERVER['SERVER_PORT'] : '')
. substr($_SERVER['SCRIPT_NAME'], 0, strrpos($_SERVER['SCRIPT_NAME'], '/')+1);
Please note that the $_SERVER array doesn't exist in
PHP < 4.1.0. Try to replace $_SERVER by
$HTTP_SERVER_VARS or $GLOBALS in this case.
[1.1] I'm running php 4+ and my server is crashing each time a specific action
is required or phpMyAdmin sends a blank page or a page full of cryptic
characters to my browser, what can I do?
There are some known php bugs with output buffering and compression.
Try to set the $cfg['OBGzip'] directive to FALSE in your
config.inc.php or .php3 file and the
zlib.output_compression directive to Off in your php
configuration file.
Furthermore, we know about such problems connected to the release
candidates of php 4.2.0 (tested with php 4.2.0 RC1 to RC4) together with
MS Internet Explorer. Please upgrade to the release version php 4.2.0.
[1.2] My Apache server crashes when using phpMyAdmin.
You should first try the latest versions of Apache (and possibly MySQL).
See also the other FAQ entry about php bugs with output buffering.
If your server keeps crashing, please ask for help in the various
Apache support groups.
[1.3] I'm running phpMyAdmin with "cookie" authentication mode under PHP 4.2.0
or 4.2.1 loaded as an Apache 2+ module but can't enter the script: I'm
always displayed the login screen.
This is a kown PHP bug (see this
bug report) from the
official php bug database. It means there is and won't be any phpMyAdmin
fix against it because there is no way to code a fix.
[1.4] Using phpMyAdmin on IIS, I'm displayed the error message: "The
specified CGI application misbehaved by not returning a complete set of
HTTP headers...."
You just forgot to read the install.txt file from the php
distribution. Have a look at the last message in this
bug report from the
official php bug database.
[1.5] Using phpMyAdmin on IIS, I'm facing crashes and/or many error messages
with the http or advanced authentication mode.
This is a known problem with the php ISAPI filter: it's not so stable. For
some more information and complete testings see the messages posted by
André B. aka "djdeluxe76" in
this thread
from the phpWizard forum.
Please use instead the cookie authentication mode.
[1.6] I can't use phpMyAdmin on PWS: nothing is displayed!
This seems to be a PWS bug. Filippo Simoncini found a workaroud (at this
time there is no better fix): remove or comment the DOCTYPE
declarations (3 lines) from the scripts header.inc.php3,
index.php3, left.php3 and libraries/common.lib.php3.
[1.7] How can I GZip or Bzip a dump or a CSV export. It seems to not work?
These features are based on the gzencode() and
bzcompress() php functions to be more independent of the platform
(Unix/Windows, Safe Mode or not, and so on).
So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2 support
(--with-zlib and --with-bz2).
We faced php crashes when trying to download a dump with MS Internet
Explorer when phpMyAdmin is run with a release candidate of php 4.2.0. In
this case you should switch to the release version of php 4.2.0.
[1.8] I cannot insert a text file in a table, and I get an error about safe
mode being in effect.
Your uploaded file is saved by PHP in the "upload dir", as
defined in php.ini by the variable upload_tmp_dir (usually
the system default is /tmp).
We recommend the following setup for Apache servers running in safe mode,
to enable uploads of files while being reasonably secure:
[1.9] I'm having troubles when uploading files. In general file uploads don't
work on my system and uploaded files have a Content-Type: header
in the first line.
It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
and you updated your php rpm to php-4.0.4pl1-3.i386.rpm, didn't you?
So the problem is that this package has a serious bug that was corrected
ages ago in php (2001-01-28: see
php's bug tracking system
for more details). The problem is that the bugged package is still
available though it was corrected (see
redhat's bugzilla
for more details).
So please download
the fixed package (4.0.4pl1-9)
and the problem should go away.
And that fixes the \r\n problem with file uploads!
[1.10] I'm having troubles when uploading files with phpMyAdmin running on a
secure server. My browser is Internet Explorer and I'm using the Apache
server.
As suggested by "Rob M" in the phpWizard forum, add this line to
your httpd.conf:
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
It seems to clear up many problems between IE and SSL.
[1.11] I get an 'open_basedir restriction' while uploading a file from the
query box.
Since version 2.2.4, phpMyAdmin supports servers with open_basedir
restrictions. Assuming that the restriction allows you to open files in the
current directory ('.'), all you have to do is create a 'tmp' directory
under the phpMyAdmin install directory, with permissions 777 and the same
owner as the owner of your phpMyAdmin directory. The uploaded files will
be moved there, and after execution of your SQL commands, removed.
[1.12] I have lost my MySQL root password, what can I do?
The MySql manual explains how to
reset the permissions.
[1.13] I get an error 'No SQL query' when trying to execute a bookmark.
If PHP does not have read/write access to its upload_tmp_dir, it
cannot access the uploaded query.
[1.14] I get an error 'No SQL query' when trying to submit a query from the
convenient text area.
Check the post_max_size directive from your php configuration file
and try to increase it.
[1.15] I have problems with mysql.user field names.
In older MySQL versions, the User and Password fields
were named user and password. Please modify your field
names to align with current standards.
[1.16] I cannot upload big dump files.
The first things to check (or ask your host provider to check) are the
values of upload_max_filesize, memory_limit and
post_max_size in the php.ini configuration file.
All of these three settings limit the maximum size of data that can be
submitted and handled by php. One user also said that post_max_size
and memory_limit need to be larger than upload_max_filesize.
[1.17] Does phpMyAdmin support MySQL 4?
MySQL 4 is not yet fully supported by phpMyAdmin.
Because of MySQL 4's backwards compatibility you can use phpMyAdmin
for administering MySQL 4 servers, but phpMyAdmin does not yet
support its new features. Please notice that in this case it is recommended
to use php >= 4.1 since older versions of php are not
compatible to MySQL 4.
Furthermore, several users reported problems with phpMyAdmin related to
bugs in MySQL 4. MySQL 4 is still an alpha
release and should be used for test purposes only!
[1.18] I'm running MySQL <= 4.0.1 having
lower_case_table_names set to 1. If I create a new table with a
capital letter in its name it is changed to lowercase as it should. But
if I try to DROP this table MySQL is unable to find the corresponding
file.
This is a bug of MySQL <= 4.0.1. Please upgrade to at least
MySQL 4.0.2 or turn off your lower_case_table_names
directive.
[1.19] I can't run the "display relations" feature because the script
seems not to know the font face I'm using!
The "FPDF" library we're using for this feature requires some
special files to use font faces.
Please refers to the
FPDF manual to build
these files.
[1.20] I receive the error "cannot load MySQL extension, please check
PHP Configuration".
To connect to a MySQL server, PHP needs a set of MySQL functions called
"MySQL extension".
This extension may be part of the PHP server (compiled-in), otherwise it
needs to be loaded dynamically. Its name is probably mysql.so or mysql.dll.
phpMyAdmin tried to load the extension but failed.
Usually, the problem is solved by installing a software package called
"PHP-MySQL" or something similar.
[2.1] The error message "Warning: Cannot add header information - headers
already sent by ..." is displayed, what's the problem?
Edit your config.inc.php or .php3 file and ensure there is nothing
(ie no blank lines, no spaces, no characters...) neither before the
<?php tag at the beginning, neither after the ?>
tag at the end.
[2.2] phpMyAdmin can't connect to MySQL. What's wrong?
Either there is an error with your PHP setup or your username/password is
wrong. Try to make a small script which uses mysql_connect and see if it
works. If it doesn't, it may be you haven't even compiled MySQL support
into PHP.
[2.3] The error message "Warning: MySQL Connection Failed: Can't connect
to local MySQL server through socket '/tmp/mysql.sock' (111)...") is
displayed. What can I do?
For RedHat users, Harald Legner suggests this on the mailing list:
On my RedHat-Box the socket of mysql is /var/lib/mysql/mysql.sock.
In your php.ini you will find a line
mysql.default_socket = /tmp/mysql.sock
change it to
mysql.default_socket = /var/lib/mysql/mysql.sock
Then restart apache and it will work.
Here is a fix suggested by Brad Ummer in the
phpwizard forum:
Have also a look at the corresponding section of the MySQL documentation.
[2.4] Nothing is displayed by my browser when I try to run phpMyAdmin, what
can I do?
Try to set the $cfg['OBGZip'] directive to FALSE in the
phpMyAdmin configuration file. It helps sometime.
Also have a look at your php version number: if it contains
"4.0b..." it means you're running a beta version of PHP. That's
not a so good idea, please upgrade to a plain revision.
[2.5] Each time I want to insert or change a record or drop a database or a
table, an error 404 (page not found) is displayed or, with http or
cookie authentication, I'm asked to login again. What's wrong?
Check the value you set for the $cfg['PmaAbsoluteUri'] directive
in the phpMyAdmin configuration file.
[3.1] When using http authentication, an user who logged out can not relog
in with the same nick.
This is related to the authentication mechanism (protocol) used by
phpMyAdmin. We plan to change it as soon as we may find enough free time
to do it, but you can bypass this problem: just close all the opened
browser windows and then go back to phpMyAdmin. You should be able to
logs in again.
[3.2] When dumping a large table in compressed mode, I get a memory limit
error or a time limit error.
As of version 2.2.4, we build the compressed dump in memory, so large
tables dumps may hang. The only alternative we can think about (using
system calls to mysqldump then gzip or bzip2) would not be applicable in
environments where PHP is in safe mode: access to system programs is
is limited by the system administrator, and time limit is enforced.
[3.3] With InnoDB tables, I lose foreign key relationships when I rename
or alter a table.
This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep
in mind that phpMyAdmin as of version 2.3.0 does not support InnoDB.
[4.1] I'm an ISP. Can I setup one central copy of phpMyAdmin or do I need to
install it for each customer?
Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
your users. The development of this feature was kindly sponsored by
NetCologne GmbH.
This requires a properly setup MySQL user management and phpMyAdmin
http or cookie authentication. See the install section on
"Using http authentication".
[4.2] What's the preferred way of making phpMyAdmin secure against evil
access?
This depends on your system.
If you're running a server which cannot be accessed by other people, it's
sufficient to use the directory protection bundled with your webserver
(with Apache you can use .htaccess files, for example).
If other people have telnet access to your server, you should use
phpMyAdmin's http authentication feature.
Suggestions:
[4.3] I get errors about not being able to include a file in /lang
or in /libraries.
Check php.ini, or ask your sysadmin to check it. The
include_path must contain "." somewhere in it, and
open_basedir, if used, must contain "." and
"./lang" to allow normal operation of phpMyAdmin.
[4.4] phpMyAdmin always gives "Access denied" when using http
authentication.
This could happen for several reasons:
[4.5] Is it possible to let users create their own databases?
Starting with 2.2.5, in the user management page, you can enter a wildcard
database name for a user, and put the privileges you want. For example,
adding SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER
would let a user create/manage his/her database(s).
[4.6] How can I use the Host-based authentication additions?
If you have existing rules from an old .htaccess file, you can take them
and add a username between the 'deny'/'allow' and
'from' strings. Using the username wildcard of '%' would
be a major benefit here if your installation is suited to using it. Then
you can just add those updated lines into the
$cfg['Servers'][$i]['AllowDeny']['rules'] array.
If you want a pre-made sample, you can try this fragment. It stops the
'root' user from logging in from any networks other than the private
network IP blocks.
//block root from logging in except from the private networks
$cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
$cfg['Servers'][$i]['AllowDeny']['rules'] = array(
'deny root from all',
'allow root from localhost',
'allow root from 10.0.0.0/8',
'allow root from 192.168.0.0/16',
'allow root from 172.16.0.0/12',
);
[5.1] I get an out of memory error, and my controls are non-functional, when
trying to create a table with more than 14 fields.
We could reproduce this problem only under Win98/98SE. Testing under
WinNT4 or Win2K, we could easily create more than 60 fields.
A workaround is to create a smaller number of fields, then come back to
your table properties and add the other fields.
[5.2] With Xitami 2.5b4, phpMyAdmin won't process form fields.
This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
with each script/website that use forms.
Upgrade or downgrade your Xitami server.
[5.3] I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2)
With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except that
the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
don't seem to work.
With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
the user's temporary directory, so they must be moved before closing
Konqueror, or else they disappear. Gzip dumps give an error message.
Testing needs to be done for Konqueror 2.2.2.
[5.4] I can't use the cookie authentication mode because Internet Explorer
never stores the cookies.
MS Internet Explorer seems to be really buggy about cookies, at least till
version 6. And thanks to Andrew Zivolup we've traced also a php 4.1.1 bug
in this area!
Then, if you're running php 4.1.1, try to upgrade or downgrade... it may
work!
[5.5] In Internet Explorer 5.0, I get Javascript errors when browsing my
rows.
Upgrade to at least Internet Explorer 5.5SP2.
[5.6] In Internet Explorer 5.0, 5.5 or 6.0, I get an error when trying to
modify a row in a table with many fields, or with a text field.
Your table neither have a primary key nor an unique one, so we must use a
long URL to identify this row. There is a limit on the lenght of the URL in
those browsers, and this not happen in Netscape, for example. The
workaround is to create a primary or unique key, or use another browser.
[5.7] I refresh (reload) my browser, and come back to the welcome page.
Some browsers support right-clicking into the frame you want to refresh,
just do this in the right frame.
[5.8] With Mozilla 0.9.7 I have problems sending a query modified in the query
box.
Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future
Mozilla versions.
[5.9] With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a whitespace
in the SQL-Query edit area: the page scrolls down.
This is a Mozilla bug (see bug #26882 at
Bugzilla).
[5.10] With Netscape 4.75 I get empty rows between each row of data in a
CSV exported file.
This is a known Netscape 4.75 bug: it adds some line feeds when exporting
data in octet-stream mode. Since we can't detect the specific Netscape
version, we cannot workaround this bug.
[6.1] I can't insert new rows into a table - MySQL brings up a SQL-error.
Examine the SQL error with care. I've found that many programmers
specifying a wrong field-type.
Common errors include:
Also, look at the syntax chapter in the MySQL manual to confirm that your syntax is correct.
[6.2] When I create a table, I click the Index checkbox for 2 fields and
phpMyAdmin generates only one index with those 2 fields.
In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
index. If you want two indexes, create the first one when creating the
table, save, then display the table properties and click the Index link to
create the other index.
[6.3] How can I insert a null value into my table?
Since version 2.2.3, you have a checkbox for each field that can be null.
Before 2.2.3, you had to enter "null", without the quotes, as the
field's value.
[6.4] How can I backup my database or table?
Click on a database or table name in the left frame, the properties will be
displayed. Then on the menu, click "Export", you can dump
the structure, the data, or both. This will generate standard SQL
statements that can be used to recreate your database/table.
You will need to choose "Save as file", so that phpMyAdmin can
transmit the resulting dump to your station. Depending on your PHP
configuration, you will see options to compress the dump. See also the
$cfg['ExecTimeLimit'] configuration variable.
For additional help on this subject, look for the word "dump" in
this document.
[6.5] How can I restore (upload) my database or table using a dump?
Click on a database name in the left frame, the properties will be
displayed. Then in the "Run SQL query" section, type in your local
dump filename, or use the Browse button. Then click Go.
For additional help on this subject, look for the word "upload" in
this document.
[6.6] How can I use the relation table in Query-by-example?
Here is an example with the tables persons, towns and countries, all
located in the database mydb. If you don't have a PMA_relation
table, create it as explained in the configuration section. Then create the
example tables:
CREATE TABLE countries (
country_code char(1) NOT NULL default '',
description varchar(10) NOT NULL default '',
PRIMARY KEY (country_code)
) TYPE=MyISAM;
INSERT INTO countries VALUES ('C', 'Canada');
CREATE TABLE persons (
id tinyint(4) NOT NULL auto_increment,
person_name varchar(32) NOT NULL default '',
town_code varchar(5) default '0',
country_code char(1) NOT NULL default '',
PRIMARY KEY (id)
) TYPE=MyISAM;
INSERT INTO persons VALUES (11, 'Marc', 'S', '');
INSERT INTO persons VALUES (15, 'Paul', 'S', 'C');
CREATE TABLE towns (
town_code varchar(5) NOT NULL default '0',
description varchar(30) NOT NULL default '',
PRIMARY KEY (town_code)
) TYPE=MyISAM;
INSERT INTO towns VALUES ('S', 'Sherbrooke');
INSERT INTO towns VALUES ('M', 'Montréal');
INSERT INTO `PMA_relation` VALUES ('mydb', 'persons', 'town_code', 'mydb', 'towns', 'town_code');
INSERT INTO `PMA_relation` VALUES ('mydb', 'persons', 'country_code', 'mydb', 'countries', 'country_code');
Then test like this:
[6.7] How can I use the "display field" feature?
Starting from the previous example, create the PMA_table_info as explained
in the configuration section, then browse your persons table,
and move the mouse over a town code or country code.
[6.8] How can I produce a PDF schema of my database?
First you have to fill the "relation", "table_coords"
and "pdf_pages" configuration variables.
Then, think about your schema layout: which tables will go on which pages.
[6.9] phpMyAdmin is changing the type of one of my columns!
No, it's MySQL that is doing silent column type changing.
[6.10] My database has an underscore in it's name, and when I grant privileges
to a user for this database, a backslash is added before the underscore.
This is normal and means that the grant is done only for this database. If
there was no backslash, this would be a wildcard grant, and the
underscore would mean "any character". So, if the database name
is "john_db", the user would get rights to john1db, john2db...
instead of just john_db.
If you really want to grant using a wildcard, there is a dialog box "
Database (wildcards allowed)" for this.
[6.11] What is the curious symbol ø in the table statistics?
It means "average".
[6.12] I want to understand some Export options.
"Complete inserts" adds the column names on every INSERT command,
for better documentation (but resulting file is bigger).
"Extended inserts" provides a shorter dump file by using only
once the INSERT verb and the table name.
"Enclose table and field names with backquotes" ensures that
field and table names formed with special characters are protected.
[7.1] I have found a bug. How do I inform developers?
Our Bug Tracker is located at
http://sourceforge.net/projects/phpmyadmin/ under the Bugs section.
But please first discuss your bug with other users:
http://sourceforge.net/projects/phpmyadmin/ (and choose Forums)
[7.2] I want to translate the messages to a new language or upgrade an
existing language, where do I start?
Always use the current cvs version of your language file.
For a new language, start from english-iso-8859-1.inc.php3. If you
don't know how to get the cvs version, please ask one of the developers.
Please note that we try not to use html entities like é in
the translations, since we define the right character set in the file.
With html entities, the text on buttons would not display correctly.
You can then put your translations, as a zip file to avoid losing special
characters, on the sourceforge.net translation tracker.
It would be a good idea to subscribe to the phpmyadmin-translators mailing
list, because this is where we ask for translations of new messages.
[7.3] I would like to help out with the development of phpMyAdmin. How should
I proceed?
The following method is preferred for new developers:
Write access to the CVS tree is granted only to experienced developers who
have already contributed something useful to phpMyAdmin.
Also, have a look at the Developers section.
phpMyAdmin is Open Source, so you're invited to contribute to it. Many great features have been written by other people and you too can help to make phpMyAdmin a useful tool.
If you're planning to contribute source, please read the following information:
IMPORTANT: With 1.4.1, development has switched to CVS. The following method is preferred for new developers:
Write access to the CVS tree is granted only to developers who have already contributed something useful to phpMyAdmin. If you're interested in that, please contact us using the phpmyadmin-devel mailing list.
phpMyAdmin - Credits
====================
CREDITS, in chronological order
-------------------------------
[tr] - Tobias Ratschiller <tobias_at_phpwizard.net>
* creator of the phpmyadmin project
* maintainer from 1998 to summer 2000
[md] - Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
* multi-language version
* various fixes and improvements
* project co-administrator
[om] - Olivier Müller <om_at_omnis.ch>
* started SourceForge phpMyAdmin project in March 2001
* sync'ed different existing CVS trees with new features and bugfixes
* multi-language improvements, dynamic language selection
* current project maintainer
[lc] - Loïc Chapeaux <lolo_at_phpheaven.net>
* rewrote and optimized javascript, DHTML and DOM stuff
* rewrote the scripts so they fit the PEAR coding standards and
generate XHTML1.0 and CSS2 compliant codes
* improved the language detection system
* many bugfixes and improvements
[rj] - Robin Johnson <robbat2_at_users.sourceforge.net>
* database maintence controls
* table type code
* Host authentication IP Allow/Deny
* DB-based configuration
[af] - Armel Fauveau <armel.fauveau_at_globalis-ms.com>
* bookmarks feature
* multiple dump feature
* gzip dump feature
* zip dump feature
[gl] - Geert Lund <glund_at_silversoft.dk>
* various fixes
* moderator of the phpMyAdmin users forum at phpwizard.net
[kc] - Korakot Chaovavanich <korakot_at_iname.com>
* "insert as new row" feature
[pk] - Pete Kelly <webmaster_at_trafficg.com>
* rewrote and fix dump code
* bugfixes
[sa] - Steve Alberty <alberty_at_neptunlabs.de>
* rewrote dump code for PHP4
* mySQL table statistics
* bugfixes
[bg] - Benjamin Gandon <gandon_at_isia.cma.fr>
* main author of the version 2.1.0.1
* bugfixes
[at] - Alexander M. Turek <rabus_at_bugfixes.info>
* various small features and fixes
* German language file updates
[mb] - Mike Beck <mike.beck at ibmiller.de>
* automatic joint in QBE
* links column in printview
* Relation view
Thanks to these guys who have sent us some major improvements to merge into the
code since version 2.1.0:
- Michal Cihar <nijel at users.sourceforge.net> who implemented the
enhanced index creation/display feature, and the mecanism to display
a character set in MySQL different than the one in HTML.
- Christophe Gesché from the "MySQL Form Generator for PHPMyAdmin"
(http://sourceforge.net/projects/phpmysqlformgen/) who suggested the patch
for multiple table printviews.
- Garvin Hicking <hicking at faktor-e.de> who built the patch for
vertical display of table rows.
- Yukihiro Kawada <kawada at den.fujifilm.co.jp> for the japanese kanji
encoding conversion feature.
- Piotr Roszatycki <d3xter at users.sourceforge.net> and Dan Wilson, for
the Cookie authentication mode.
- Axel Sander <n8falke at users.sourceforge.net> for the table
relation-links feature.
- Maxime Delorme <delorme.maxime at free.fr> for the PDF schema output;
thanks also to Olivier Plathey for the "FPDF" library
(see http://www.fpdf.org/).
And also to the following people who have contributed minor changes,
enhancements, bugfixes or support for a new language since version 2.1.0:
Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow, Laurent Dhima,
Kristof Hamann, Thomas Kläger, Lubos Klokner, Martin Marconcini,
Girish Nair, David Nordenberg, Bernard M. Piller, Laurent Haas,
"Sakamoto", Yuval Sarna, www.securereality.com.au,
Alvar Soome, Siu Sun, Peter Svec, Michael Tacelosky, Rachim Tamsjadi,
Kositer Uros, Luís V., Martijn W. van der Lee, Algis Vainauskas,
Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai, Jakub Wilk,
Thomas Michael Winningham, Vilius Zigmantas.
Original Credits of Version 2.1.0
---------------------------------
This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
to create a web-based interface to MySQL using PHP3. Although I have not
used any of his source-code, there are some concepts I've borrowed from
him. phpMyAdmin was created because Peter told me he wasn't going to
further develop his (great) tool.
Thanks go to
- Amalesh Kempf <ak-lsml_at_living-source.com> who contributed the
code for the check when dropping a table or database. He also suggested
that you should be able to specify the primary key on tbl_create.php3. To
version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
well as a bug-report. Plus many smaller improvements.
- Jan Legenhausen <jan_at_nrw.net>: He made many of the changes that
were introduced in 1.3.0 (including quite significant ones like the
authentication). For 1.4.1 he enhanced the table-dump feature. Plus
bug-fixes and help.
- Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca> made phpMyAdmin
language-independent by outsourcing the strings to a separate file. He
also contributed the French translation.
- Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
tbl_select.php3, a feature to display only some fields from a table.
- Chris Jackson <chrisj_at_ctel.net> added support for MySQL
functions in tbl_change.php3. He also added the
"Query by Example" feature in 2.0.
- Dave Walton <walton_at_nordicdms.com> added support for multiple
servers and is a regular contributor for bug-fixes.
- Gabriel Ash <ga244_at_is8.nyu.edu> contributed the random access
features for 2.0.6.
The following people have contributed minor changes, enhancements, bugfixes
or support for a new language:
Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
G. Wieggers.
And thanks to everyone else who sent me email with suggestions, bug-reports
and or just some feedback.