of 48
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
   ______________________________________________________________________  Top  Requirements  Introduction  Installation  Configuration Transformations  FAQ  Developers  Credits  Translators ______________________________________________________________________  phpMyAdmin 2.6.3pl1 Documentation * SourceForge phpMyAdmin project page [ ] * Local documents: + Version history: ChangeLog + General notes: README + License: LICENSE * Documentation version: $Id: Documentation.html,v 2005/07/04 21:50:18 lem9 Exp $Requirements * PHP + You need PHP 4.1.0 or newer (*) + If you want to display inline thumbnails of JPEGs with the srcinal 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. Open the file in your favorite editor and change the v alues for host, user, password and authentication mode to fit your environment. 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. It is recommended that you protect the directory in which you install ed phpMyAdmin (unless it's on a closed intranet, or you wish to use HTTP or cookie authentication), for example with HTTPAUTH (in a .htaccess file). See the multiuser subsection of the FAQ for additional information, especially FAQ 4.4. 5. Open the file <www.your>/<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 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 * You can safely copy your older over a new one, if you can live with default values for possible new parameters (you can check release notes to see what new features were added). This compatibility will stay for long time, current version supports importing config files from 2.2 and maybe even older (nobody has tried that). 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 authentication applies only to MySQL servers older than 4.1.2. For 'HTTP' and 'cookie' modes, phpMyAdmin needs a controluser that has only the SELECT privilege on the mysql.user (all columns except  Password ), mysql.db (all columns), (all columns) and mysql.tables_priv (all columns except Grantor & Timestamp ) tables. You must specify the details for the controluser in the file under the $cfg['Servers'][$i]['controluser']& $cfg['Servers'][$i]['controlpass'] settings. The following example assumes you want to use pma as the controluser and pmapass as the controlpass, but this is only an example: use something else in your file! Of course you have to replace localhost by the webserver's host if it's not the same as the MySQL server's one.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, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv ) ON mysql.user TO 'pma'@'localhost';GRANT SELECT ON mysql.db TO 'pma'@'localhost';GRANT SELECT ON TO 'pma'@'localhost';GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)   ON mysql.tables_priv TO 'pma'@'localhost'; If you are using an old MySQL version (below 4.0.2), please replace the first GRANT SELECT query by this one: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'; ... 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) Of course, the above queries only work if your MySQL version supports the GRANT command. This is the case since 3.22.11. * Then each of the true users should be granted a set of privileges on a set of particular databases. Normally you shouldn't give global privileges to an ordinary user, unless you understand the impact of those privileges (for example, you are creating a superuser). For example, to grant the user real_user with all privileges on the database user_base: GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password'; What the user may now do is controlled entirely by the MySQL user management system. With HTTP or cookie authentication mode, you don't need to fill the user/password fields inside the $cfg['Servers'] array. 'http' authentication mode * Was called 'advanced' in versions before 2.2.3. * Introduced in 1.3.0, it uses Basic HTTP authentication method and all ows you to login as any valid MySQL user. * Is supported with PHP running as an Apache module. For IIS (ISAPI) su pport using CGI PHP, see FAQ 1.32. * See also FAQ 4.4 about not using the .htaccess mechanism along with ' http' authentication mode. 'cookie' authentication mode * You can use this method as a replacement for the HTTP authentication (for example, if you're running IIS). * Obviously, the user must enable cookies in the browser. * With this mode, the user can truly logout of phpMyAdmin and login bac k with the same username. * If you want to login to arbitrary server see $cfg['AllowArbitraryServ er'] directive. * See also the requirements section for a way to improve the interface speed while using this mode. 'config' authentication mode * This mode is the less secure one because it requires you to fill the $cfg['Servers'][$i]['user'] and $cfg['Servers'][$i]['password'] fields. But you don't need to setup a controluser here: using the $cfg['Servers'][$i]['only_db'] might be enough.
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks