annotate INSTALL.mysql.txt @ 10:6f15c9d74937

Added tag 6.4 for changeset acef7ccb09b5
author Franck Deroche <webmaster@defr.org>
date Tue, 23 Dec 2008 14:32:08 +0100
parents c1f4ac30525a
children
rev   line source
webmaster@1 1 // $Id: INSTALL.mysql.txt,v 1.10 2007/11/19 19:53:51 goba Exp $
webmaster@1 2
webmaster@1 3 CREATE THE MySQL DATABASE
webmaster@1 4 --------------------------
webmaster@1 5
webmaster@1 6 This step is only necessary if you don't already have a database set-up (e.g. by
webmaster@1 7 your host). In the following examples, 'username' is an example MySQL user which
webmaster@1 8 has the CREATE and GRANT privileges. Use the appropriate user name for your
webmaster@1 9 system.
webmaster@1 10
webmaster@1 11 First, you must create a new database for your Drupal site (here, 'databasename'
webmaster@1 12 is the name of the new database):
webmaster@1 13
webmaster@1 14 mysqladmin -u username -p create databasename
webmaster@1 15
webmaster@1 16 MySQL will prompt for the 'username' database password and then create the
webmaster@1 17 initial database files. Next you must login and set the access database rights:
webmaster@1 18
webmaster@1 19 mysql -u username -p
webmaster@1 20
webmaster@1 21 Again, you will be asked for the 'username' database password. At the MySQL
webmaster@1 22 prompt, enter following command:
webmaster@1 23
webmaster@1 24 GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER
webmaster@1 25 ON databasename.*
webmaster@1 26 TO 'username'@'localhost' IDENTIFIED BY 'password';
webmaster@1 27
webmaster@1 28 where
webmaster@1 29
webmaster@1 30 'databasename' is the name of your database
webmaster@1 31 'username@localhost' is the username of your MySQL account
webmaster@1 32 'password' is the password required for that username
webmaster@1 33
webmaster@1 34 Note: Unless your database user has all of the privileges listed above, you will
webmaster@1 35 not be able to run Drupal.
webmaster@1 36
webmaster@1 37 If successful, MySQL will reply with:
webmaster@1 38
webmaster@1 39 Query OK, 0 rows affected
webmaster@1 40