Chris@0: 
Chris@0: CREATE THE MySQL DATABASE
Chris@0: --------------------------
Chris@0: 
Chris@0: This step is only necessary if you don't already have a database set up (e.g.,
Chris@0: by your host). In the following examples, 'username' is an example MySQL user
Chris@0: which has the CREATE and GRANT privileges. Use the appropriate user name for
Chris@0: your system.
Chris@0: 
Chris@0: First, you must create a new database for your Drupal site (here, 'databasename'
Chris@0: is the name of the new database):
Chris@0: 
Chris@0:   mysqladmin -u username -p create databasename
Chris@0: 
Chris@0: MySQL will prompt for the 'username' database password and then create the
Chris@0: initial database files. Next you must log in and set the access database rights:
Chris@0: 
Chris@0:   mysql -u username -p
Chris@0: 
Chris@0: Again, you will be asked for the 'username' database password. At the MySQL
Chris@0: prompt, enter the following command:
Chris@0: 
Chris@0:   GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER,
Chris@0:   CREATE TEMPORARY TABLES ON databasename.*
Chris@0:   TO 'username'@'localhost' IDENTIFIED BY 'password';
Chris@0: 
Chris@0: where:
Chris@0: 
Chris@0:  'databasename' is the name of your database
Chris@0:  'username' is the username of your MySQL account
Chris@0:  'localhost' is the web server host where Drupal is installed
Chris@0:  'password' is the password required for that username
Chris@0: 
Chris@0: Note: Unless the database user/host combination for your Drupal installation
Chris@0: has all of the privileges listed above (except possibly CREATE TEMPORARY TABLES,
Chris@0: which is currently only used by Drupal core automated tests and some
Chris@0: contributed modules), you will not be able to install or run Drupal.
Chris@0: 
Chris@0: If successful, MySQL will reply with:
Chris@0: 
Chris@0:   Query OK, 0 rows affected
Chris@0: 
Chris@0: If the InnoDB storage engine is available, it will be used for all database
Chris@0: tables. InnoDB provides features over MyISAM such as transaction support,
Chris@0: row-level locks, and consistent non-locking reads.