______________________________________________________________________
Top - Requirements - Introduction - Installation - Configuration
Transformations - FAQ - Developers - Credits - Translators
______________________________________________________________________
phpMyAdmin 2.7.0 Documentation
* SourceForge phpMyAdmin project page [ http://www.phpmyadmin.net/ ]
* Local documents:
+ Version history: ChangeLog
+ General notes: README
+ License: LICENSE
* Documentation version: $Id: Documentation.html,v 2.177.2.1 2005/12/04 21:45:33 lem9 Exp $
Requirements
* PHP
+ You need PHP 4.1.0 or newer, with session support (*)
+ If you want to display inline thumbnails of JPEGs with the original
aspect ratio, you also need GD2 support in PHP
+ Starting with phpMyAdmin 2.6.1, MIME-based transformations that use
an external program need PHP 4.3.0 or newer
* MySQL 3.23.32 or newer (details);
* Not really a requirement but a strong suggestion: if you are using th e "cookie" authentication method, having the mcrypt PHP extension on
your web server accelerates not only the login phase but every other
action that you do in phpMyAdmin.
* a web-browser (doh!).
Introduction
phpMyAdmin can manage a whole MySQL server (needs a super-user) as well a s 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:
* create and drop databases
* create, copy, drop, rename and alter tables
* do table maintenance
* delete, edit and add fields
* execute any SQL-statement, even batch-queries
* manage keys on fields
* load text files into tables
* create (*) and read dumps of tables
* export (*) data to CSV, XML and Latex formats
* administer multiple servers
* manage MySQL users and privileges
* check referential integrity in MyISAM tables
* using Query-by-example (QBE), create complex queries automatically co nnecting required tables
* create PDF graphics of your Database layout
* search globally in a database or a subset of it
* transform stored data into any format using a set of predefined funct ions, like displaying BLOB-data as image or download-link or ...
* support InnoDB tables and foreign keys (see FAQ 3.6)
* support mysqli, the improved MySQL extension (see FAQ 1.17)
* communicate in 50 different languages
(*) phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats) dump s and CSV exports if you use PHP4 >= 4.0.4 with Zlib support (--with-zli b) and/or Bzip2 support (--with-bz2).
Installation
NOTE: phpMyAdmin does not apply any special security methods to the MySQL database server. It is still the system administrator's job to grant pe rmissions on the MySQL databases properly. phpMyAdmin's "Privileges" pag e can be used for this.
Warning for Mac users:if you are on a MacOS version before OS X, StuffIt unstuffs with Mac formats.
So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin script s before uploading them to your server, as PHP seems not to like Mac-sty le end of lines character ("\r").
Quick Install
1. Untar or unzip the distribution (be sure to unzip the subdirectories) : tar -xzvf phpMyAdmin_x.x.x.tar.gz in your webserver's document root.
If you don't have direct access to your document root, put the files in
a directory on your local machine, and, after step 3, transfer the
directory on your web server using, for example, ftp.
2. Ensure that all the scripts have the appropriate owner (if PHP is run ning in safe mode, having some scripts with an owner different from the
owner of other scripts will be a problem). See FAQ 4.2 for suggestions.
3. Create the file config.inc.php in your favorite editor and fill in th ere values for host, user, password and authentication mode to fit your
environment. Look at config.default.php how these fields should be
defined. Here, "host" means the MySQL server. Have a look at
Configuration section for an explanation of all values. Please also read
the remaining of this Installation section for information about
authentication modes and the linked-tables infrastructure.
4. If you are using the config auth_type, it is suggested that you prote ct the phpMyAdmin installation directory, for example with HTTP–AUTH in
a .htaccess file. See the multi–user sub–section of this FAQ for
additional information, especially FAQ 4.4.
5. Open the file <www.your-host.com>/<your-install-dir>/index.php in you r browser. phpMyAdmin should now display a welcome screen and your
databases, or a login dialog if using HTTP or cookie authentication
mode.
Linked-tables infrastructure
For a whole set of new features (bookmarks, comments, SQL-history, PDF-ge neration, field contents transformation, etc.) you need to create a set of special tables. Those tables can be located in your own database, or in a central database for a multi-user installation (this database would then be accessed by the controluser, so no other user should have right s to it).
Please look at your scripts/ directory, where you should find a file call ed create_tables.sql. (If you are using a Windows server, pay special at tention to FAQ 1.23).
If your MySQL server's version is 4.1.2 or later, please use create_table s_mysql_4_1_2+.sql instead, for a new installation.
If you already had this infrastructure and upgraded to MySQL 4.1.2 or lat er, please use upgrade_tables_mysql_4_1_2+.sql.
You can use your phpMyAdmin to create the tables for you. Please be aware that you may need special (administrator) privileges to create the data base and tables, and that the script may need some tuning, depending on the database name.
After having imported the create_tables.sql file, you should specify the table names in your config.inc.php file. The directives used for that ca n be found in the Configuration section. You will also need to have a co ntroluser with the proper rights to those tables (see section Using auth entication modes below).
Upgrading from an older version
Just copy config.inc.php from previous installation into a newly unpacked one. If your previous phpMyAdmin version was 2.3.0 or older, some tweak ing may be required because, as of 2.7.0, using those old config files i s no longer supported.
Using authentication modes
* HTTP and cookie authentication modes are recommended in a multi-user environment where you want to give users access to their own database
and don't want them to play around with others.
Nevertheless be aware that MS Internet Explorer seems to be really buggy
about cookies, at least till version 6. And PHP 4.1.1 is also a bit
buggy in this area!
Even in a single-user environment, you might prefer to use HTTP or
cookie mode so that your user/password pair are not in clear in the
configuration file.
* HTTP and cookie authentication modes are more secure: the MySQL login information does not need to be set in the phpMyAdmin configuration
file (except possibly for the controluser).
However, keep in mind that the password travels in plain text, unless
you are using the HTTPS protocol.
In cookie mode, the password is stored, encrypted with the blowfish
algorithm, in a temporary cookie.
* Note: starting with phpMyAdmin 2.6.1, configuring the controluser to enable HTTP and cookie authenti