From 25a4309ed0f7d9401e0a8b0fe560e77af6c684ce Mon Sep 17 00:00:00 2001 From: Dries Buytaert Date: Fri, 4 Feb 2011 21:26:25 +0000 Subject: - Patch ##1041474 by 1V: Fixed INSTALL.pgsql.txt and INSTALL.mysql.txt cleanup of various grammatical errors. --- INSTALL.pgsql.txt | 47 ++++++++++++++++++++++++----------------------- 1 file changed, 24 insertions(+), 23 deletions(-) (limited to 'INSTALL.pgsql.txt') diff --git a/INSTALL.pgsql.txt b/INSTALL.pgsql.txt index a2aeaea59..81c181828 100644 --- a/INSTALL.pgsql.txt +++ b/INSTALL.pgsql.txt @@ -7,38 +7,39 @@ Note that the database must be created with UTF-8 (Unicode) encoding. 1. CREATE DATABASE USER - This step is only necessary if you don't already have a user set up (e.g. - by your host) or you want to create new user for use with Drupal only. The - following command creates a new user named "username" and asks for a - password for that user: + This step is only necessary if you don't already have a user set up (e.g., by + your host), or want to create a new user for use with Drupal only. The + following command creates a new user named 'username' and asks for a password + for that user: createuser --pwprompt --encrypted --no-createrole --no-createdb username - If there are no errors then the command was successful + If there are no errors, then the command was successful. -2. CREATE THE DRUPAL DATABASE +2. CREATE DRUPAL DATABASE - This step is only necessary if you don't already have a database set up (e.g. - by your host) or you want to create new database for use with Drupal only. - The following command creates a new database named "databasename", which is - owned by previously created "username": + This step is only necessary if you don't already have a database set up + (e.g., by your host) or want to create a new database for use with Drupal + only. The following command creates a new database named 'databasename', + which is owned by the previously created 'username': createdb --encoding=UTF8 --owner=username databasename - If there are no errors then the command was successful + If there are no errors, then the command was successful. -3. CREATE A SCHEMA OR SCHEMAS (Optional advanced) +3. CREATE SCHEMA OR SCHEMAS (Optional advanced step) - Drupal will run across different schemas within your database if you so wish. - By default, Drupal runs inside the 'public' schema but you can use $db_prefix - inside settings.php to define a schema for Drupal to inside of or specify tables - that are shared inside of a separate schema. Drupal will not create schemas for - you, infact the user that Drupal runs as should not be allowed to. You'll need - execute the SQL below as a superuser (such as a postgres user) and replace - 'drupaluser' with the username that Drupal uses to connect to PostgreSQL with - and replace schema_name with a schema name you wish to use such as 'shared': + Drupal will run across different schemas within your database if you so wish. + By default, Drupal runs inside the 'public' schema but you can use $db_prefix + inside settings.php to define a schema for Drupal to run inside of, or + specify tables that are shared inside of a separate schema. Drupal will not + create schemas for you. In fact, the user that Drupal runs as should not be + allowed to do this. You'll need to execute the SQL below as a superuser, + replace 'username' with the username that Drupal uses to connect to + PostgreSQL, and replace 'schema_name' with a schema name you wish to use, + such as 'shared': - CREATE SCHEMA schema_name AUTHORIZATION drupaluser; + CREATE SCHEMA schema_name AUTHORIZATION username; - Do this for as many schemas as you need. See default.settings.php for how to - set which tables use which schemas. + Do this for as many schemas as you need. See default.settings.php for + instructions on how to set which tables use which schemas. -- cgit v1.2.3