head	1.4;
access;
symbols
	HORDE_1_2_7:1.1.2.12
	HORDE_1_2_6:1.1.2.12
	HORDE_1_2_5:1.1.2.12
	HORDE_1_2_4:1.1.2.12
	HORDE_1_2_3:1.1.2.12
	HORDE_1_2_2:1.1.2.10
	HORDE_1_2_1:1.1.2.9
	HORDE_1_2_0:1.1.2.8
	HORDE_1_2_0_pre14:1.1.2.10
	HORDE_1_2_0_pre13:1.1.2.7
	HORDE_1_2_0_pre11:1.1.2.3
	HORDE_1_3_2:1.3
	HORDE_1_2_0_pre10:1.1.2.3
	HORDE_1_3_1:1.3
	HORDE_1_2_0_pre9:1.1.2.3
	HORDE_1_2_0_pre8:1.1.2.3
	HORDE_1_2_0_pre6:1.1.2.3
	horde-dev-20000104:1.3
	HORDE_1_2_0_pre5:1.1.2.1
	HORDE_1_2_0_pre4:1.1.2.1
	STABLE_1_2:1.1.0.2;
locks; strict;
comment	@# @;


1.4
date	2000.05.02.15.17.15;	author chuck;	state dead;
branches;
next	1.3;

1.3
date	99.09.22.05.38.13;	author mhardy;	state Exp;
branches;
next	1.2;

1.2
date	99.08.26.13.13.15;	author rkrusty;	state Exp;
branches;
next	1.1;

1.1
date	99.08.25.04.48.55;	author rkrusty;	state dead;
branches
	1.1.2.1;
next	;

1.1.2.1
date	99.08.25.04.48.55;	author rkrusty;	state Exp;
branches;
next	1.1.2.2;

1.1.2.2
date	99.12.28.02.32.31;	author jon;	state Exp;
branches;
next	1.1.2.3;

1.1.2.3
date	2000.01.06.20.31.50;	author jon;	state Exp;
branches;
next	1.1.2.4;

1.1.2.4
date	2000.04.09.22.07.07;	author chuck;	state Exp;
branches;
next	1.1.2.5;

1.1.2.5
date	2000.05.19.21.27.04;	author bjn;	state Exp;
branches;
next	1.1.2.6;

1.1.2.6
date	2000.05.20.03.46.15;	author bjn;	state Exp;
branches;
next	1.1.2.7;

1.1.2.7
date	2000.05.30.03.24.20;	author bjn;	state Exp;
branches;
next	1.1.2.8;

1.1.2.8
date	2000.06.27.14.59.47;	author bjn;	state Exp;
branches;
next	1.1.2.9;

1.1.2.9
date	2000.09.09.02.44.43;	author bjn;	state Exp;
branches;
next	1.1.2.10;

1.1.2.10
date	2000.09.10.19.47.23;	author jon;	state Exp;
branches;
next	1.1.2.11;

1.1.2.11
date	2000.09.20.04.48.44;	author chuck;	state Exp;
branches;
next	1.1.2.12;

1.1.2.12
date	2000.10.02.13.28.17;	author bjn;	state Exp;
branches;
next	;


desc
@@


1.4
log
@PHPLIB is no longer needed.
DATABASE was specific to phplib; I think we should just re-write it from
         scratch once we have a concrete idea of db use in the post-phplib
	 world.
INSTALL is updated to reflect that php4 is required, and you don't need
        phplib anymore.
@
text
@HORDE Database Installation Guide
Copyright 1999 Ivan E. Moore II <rkrusty@@tdyc.com>
Copyright 1999 Mike Hardy <mikeh@@spark.com>

This code is licensed under the GNU Public License.
See the file COPYING in this directory.

Last Updated: 8/25/99 [IEM]

--------------------
Purpose of this file
--------------------

What this file will hopefully do for you is make setting up
your database for use with HORDE much easier.  The goal
is not to help you setup your database for general use, just
how to setup the tables and users for HORDE.


----------------------
Requirements for HORDE
----------------------

Horde uses PHPLib to handle it's database management.  If 
PHPLib supports your database of choice most likely it will
work with HORDE.  Currently we know for sure that HORDE works
with:

   MySql
   PostgreSql
   Oracle
   Sybase
   Informix

MySql was the original database supported by HORDE and should at all
times (most likely) work for sure.  PostgreSql I can verify works
like a champ.  The others are more recent additions or those that
have less support currently.  For this reason (and the reason
that I cannot verify personally that they work or have ever
configured them) they won't be mentioned much in this file.
No one using Informix has contacted us for a while, but Oracle and 
Sybase are both currently used and should work.

You will need to have your database preconfigured and working
on your system before you even get to this stage.  For help
with this please consult your database specific help files.


--------------------------
Methods of Installation
--------------------------

There are 2 basic methods for configuring your database. The
first is manually doing it yourself. This is the method
that will make sure that things are setup as you can see 
step by step that things are being configured properly.

The other method is to use one of the scripts that have been
created to automatically configure your database.  These
scripts should work but there are times when things may not
work the way they are supposed to.  Also, when using scripts
you need to be aware that they may not be setup exactly
for your system so you need to verify them to make sure things
are correct for your particular install before using them.


=-=-=-=-=-=-=-=-=
MANUAL INSTALL:
=-=-=-=-=-=-=-=-=

For the 1.2.x version of HORDE you will need to install the 
PHPLib session tables.  We have included the create scripts for
Postgresql and MySql.  You can find them in config/scripts.
If you are using a different type of database, please check your
PHPLib distribution for the proper creation scripts.  

Your database name needs to be 'horde'.  Insert the PHPLib 
session tables into your newly created 'horde' database.  If you
look through the creation scripts, you'll notice there are tables
for auth_user and auth_user_md5.  We are currently not using these
tables but are slowing working them in so it's a good idea to
insert them as well. 

Here is a breakdown of the tables and their elements:

Table 1:

   active_sessions (
      sid varchar(32) DEFAULT '',
      name varchar(32) DEFAULT '',
      val text,
      changed varchar(14) DEFAULT '' NOT NULL,
      PRIMARY KEY (sid,name)
   )

   auth_user (
      uid varchar(32) PRIMARY KEY,
      username varchar(32) DEFAULT '' NOT NULL,
      password varchar(32) DEFAULT '' NOT NULL,
      perms varchar(255)
   )

   auth_user_md5 (
       uid varchar(32) PRIMARY KEY,
       username varchar(32) DEFAULT '' NOT NULL,
       password varchar(32) DEFAULT '' NOT NULL,
       perms varchar(255)
   )
   


I kind of broke them down as they would go into the database...ie, the
name then what it is...(example:  val is a text field).

The database name itself needs to be "horde" and needs to be created.

Next you'll need to create a user or give a user access to this
database.  This user will need pretty much full control over this
database.  The username we use for the most part is hordemgr.
Here are a few configuration tips for MySql and PostGreSql:

MYSQL:

INSERT INTO user ( host, user, password )
   VALUES (
      'localhost',
      'hordemgr',
      password( 'hordemgr' )
      );

INSERT INTO db (
      host, db, user,
         Select_priv, Insert_priv, Update_priv, Delete_priv,
         Create_priv, Drop_priv )
      VALUES (
      'localhost',
      'horde',
      'hordemgr',
      'Y', 'Y', 'Y', 'Y',
      'Y', 'Y'
        );

This will setup a user called hordemgr with a password of 'hordemgr' and
give them access to the horde database. 

*** NOTES ***

Use the scripts provided in horde/config/scripts.  They will make your
life alot happier.

After either using the scripts (read the top of them for instructions)
or manually doing it: ( 
       mysql> create database horde
       mysql> insert into user (host, user, password) values ('localhost', 'horde', password('hordemgr'));
       mysql> insert into db values ('localhost', 'horde', 'horde', 'y', 'y', 'y', 'y', 'y', 'y');
       mysql> quit
    )

After setting up your tables in MySql you need to run this command:

     mysqladmin -u root -p reload

It is always a good idea to stop and restart your mysql process as well.



=-=-=-=

POSTGRESQL:

insert into pg_shadow (usename, usesysid, usecreatedb, usetrace, usesuper, \
       usecatupd, passwd) values ('hordemgr', '33', 't', 't', 't', 't', \
       'hordemgr') ;

   This will create a postgres user called hordemgr who will be connecting
to the database as the user who's userid is 33 (on Debian, apache is ran
as user www-data which uses the userid of 33, this will be nobody on other
systems.).  This user also has the password of 'hordemgr'.

GRANT SELECT, INSERT, UPDATE ON active_sessions, auth_user, auth_user_md5 TO hordemgr;

  This will give the user hordemgr access to these tables (active_sessions, 
etc...).  

Also, you need to make sure you allow TCP connections into your 
database.  PostgreSql has a switch in one of it's configuration files
(postmaster.init on Debian) that needs to be set to yes:

PGALLOWTCPIP=yes

Without this set to yes HORDE won't be able to talk to your database and
you'll get tons of errors. :)

That's about it.  You need to restart your database just to make sure
everything starts up the way it should.

=-=-=-=-=-=-=-=-=
SCRIPTED INSTALL:
=-=-=-=-=-=-=-=-=

(NOTE: Scripts are located in horde/config/scripts)

The easier way of configuring your database is to use one of the
scripts that have been made available to you.  Here is a breakdown
of how to use each script.

MySql:

MySql's script is called mysql_create.sql.  The method you would call
it is by first logging into an account that has full access to the
database or by using a switch to call that user.  I'll show both
methods.

Before using any of these scripts, please look over them to make
sure that any system specific settings (or personal choices) are
set to your desired settings...ie usernames, etc...

MySql: 

 su - root

   mysql < mysql_create.sql
     or
   mysql -password=rootspasswordformysql < mysql_create.sql

 or (without changing to root)

   mysql -user=username < mysql_create.sql
     or
   mysql -user=username -password=rootspasswordformysql < mysql_create.sql


That's it..restart MySql (or 'mysqladmin reload') and try it out...

PostgreSql:

  su - postgres  (or whoever your database runs as..usually postgres)

  psql template1 < pgsql_create.sql

That's it, restart PostgreSql and try it out.

=-=-=-=
Notes:
=-=-=-=

     This is by far no complete HOWTO.  This is just a compiled list
of what people have contributed so far.  Some of this is from my
personal experience (MySql and PostgreSql).  If you have tips, ideas,
suggestions or anything else that you think could help others in
setting up their database for use with HORDE please let me know and
I'll include them.  (or contribute to HORDE yourself and change this
file on your own!)
@


1.3
log
@Mike: omg - I'm committing something. This is more 'mysqladmin reload' stuff,
somebody already beat me to it one of the places...
@
text
@@


1.2
log
@[IEM] copying over the database docs from horde 1.2 tree
@
text
@d144 1
a144 1
give them access to the horde database.
d233 1
a233 1
That's it..restart MySql and try it out
@


1.1
log
@file DATABASE was initially added on branch STABLE_1_2.
@
text
@d1 253
@


1.1.2.1
log
@[IEM] migrating all core documentaiton (except readme and copying) into
the docs/ sub directory
@
text
@a0 253
HORDE Database Installation Guide
Copyright 1999 Ivan E. Moore II <rkrusty@@tdyc.com>
Copyright 1999 Mike Hardy <mikeh@@spark.com>

This code is licensed under the GNU Public License.
See the file COPYING in this directory.

Last Updated: 8/25/99 [IEM]

--------------------
Purpose of this file
--------------------

What this file will hopefully do for you is make setting up
your database for use with HORDE much easier.  The goal
is not to help you setup your database for general use, just
how to setup the tables and users for HORDE.


----------------------
Requirements for HORDE
----------------------

Horde uses PHPLib to handle it's database management.  If 
PHPLib supports your database of choice most likely it will
work with HORDE.  Currently we know for sure that HORDE works
with:

   MySql
   PostgreSql
   Oracle
   Sybase
   Informix

MySql was the original database supported by HORDE and should at all
times (most likely) work for sure.  PostgreSql I can verify works
like a champ.  The others are more recent additions or those that
have less support currently.  For this reason (and the reason
that I cannot verify personally that they work or have ever
configured them) they won't be mentioned much in this file.
No one using Informix has contacted us for a while, but Oracle and 
Sybase are both currently used and should work.

You will need to have your database preconfigured and working
on your system before you even get to this stage.  For help
with this please consult your database specific help files.


--------------------------
Methods of Installation
--------------------------

There are 2 basic methods for configuring your database. The
first is manually doing it yourself. This is the method
that will make sure that things are setup as you can see 
step by step that things are being configured properly.

The other method is to use one of the scripts that have been
created to automatically configure your database.  These
scripts should work but there are times when things may not
work the way they are supposed to.  Also, when using scripts
you need to be aware that they may not be setup exactly
for your system so you need to verify them to make sure things
are correct for your particular install before using them.


=-=-=-=-=-=-=-=-=
MANUAL INSTALL:
=-=-=-=-=-=-=-=-=

For the 1.2.x version of HORDE you will need to install the 
PHPLib session tables.  We have included the create scripts for
Postgresql and MySql.  You can find them in config/scripts.
If you are using a different type of database, please check your
PHPLib distribution for the proper creation scripts.  

Your database name needs to be 'horde'.  Insert the PHPLib 
session tables into your newly created 'horde' database.  If you
look through the creation scripts, you'll notice there are tables
for auth_user and auth_user_md5.  We are currently not using these
tables but are slowing working them in so it's a good idea to
insert them as well. 

Here is a breakdown of the tables and their elements:

Table 1:

   active_sessions (
      sid varchar(32) DEFAULT '',
      name varchar(32) DEFAULT '',
      val text,
      changed varchar(14) DEFAULT '' NOT NULL,
      PRIMARY KEY (sid,name)
   )

   auth_user (
      uid varchar(32) PRIMARY KEY,
      username varchar(32) DEFAULT '' NOT NULL,
      password varchar(32) DEFAULT '' NOT NULL,
      perms varchar(255)
   )

   auth_user_md5 (
       uid varchar(32) PRIMARY KEY,
       username varchar(32) DEFAULT '' NOT NULL,
       password varchar(32) DEFAULT '' NOT NULL,
       perms varchar(255)
   )
   


I kind of broke them down as they would go into the database...ie, the
name then what it is...(example:  val is a text field).

The database name itself needs to be "horde" and needs to be created.

Next you'll need to create a user or give a user access to this
database.  This user will need pretty much full control over this
database.  The username we use for the most part is hordemgr.
Here are a few configuration tips for MySql and PostGreSql:

MYSQL:

INSERT INTO user ( host, user, password )
   VALUES (
      'localhost',
      'hordemgr',
      password( 'hordemgr' )
      );

INSERT INTO db (
      host, db, user,
         Select_priv, Insert_priv, Update_priv, Delete_priv,
         Create_priv, Drop_priv )
      VALUES (
      'localhost',
      'horde',
      'hordemgr',
      'Y', 'Y', 'Y', 'Y',
      'Y', 'Y'
        );

This will setup a user called hordemgr with a password of 'hordemgr' and
give them access to the horde database.

*** NOTES ***

Use the scripts provided in horde/config/scripts.  They will make your
life alot happier.

After either using the scripts (read the top of them for instructions)
or manually doing it: ( 
       mysql> create database horde
       mysql> insert into user (host, user, password) values ('localhost', 'horde', password('hordemgr'));
       mysql> insert into db values ('localhost', 'horde', 'horde', 'y', 'y', 'y', 'y', 'y', 'y');
       mysql> quit
    )

After setting up your tables in MySql you need to run this command:

     mysqladmin -u root -p reload

It is always a good idea to stop and restart your mysql process as well.



=-=-=-=

POSTGRESQL:

insert into pg_shadow (usename, usesysid, usecreatedb, usetrace, usesuper, \
       usecatupd, passwd) values ('hordemgr', '33', 't', 't', 't', 't', \
       'hordemgr') ;

   This will create a postgres user called hordemgr who will be connecting
to the database as the user who's userid is 33 (on Debian, apache is ran
as user www-data which uses the userid of 33, this will be nobody on other
systems.).  This user also has the password of 'hordemgr'.

GRANT SELECT, INSERT, UPDATE ON active_sessions, auth_user, auth_user_md5 TO hordemgr;

  This will give the user hordemgr access to these tables (active_sessions, 
etc...).  

Also, you need to make sure you allow TCP connections into your 
database.  PostgreSql has a switch in one of it's configuration files
(postmaster.init on Debian) that needs to be set to yes:

PGALLOWTCPIP=yes

Without this set to yes HORDE won't be able to talk to your database and
you'll get tons of errors. :)

That's about it.  You need to restart your database just to make sure
everything starts up the way it should.

=-=-=-=-=-=-=-=-=
SCRIPTED INSTALL:
=-=-=-=-=-=-=-=-=

(NOTE: Scripts are located in horde/config/scripts)

The easier way of configuring your database is to use one of the
scripts that have been made available to you.  Here is a breakdown
of how to use each script.

MySql:

MySql's script is called mysql_create.sql.  The method you would call
it is by first logging into an account that has full access to the
database or by using a switch to call that user.  I'll show both
methods.

Before using any of these scripts, please look over them to make
sure that any system specific settings (or personal choices) are
set to your desired settings...ie usernames, etc...

MySql: 

 su - root

   mysql < mysql_create.sql
     or
   mysql -password=rootspasswordformysql < mysql_create.sql

 or (without changing to root)

   mysql -user=username < mysql_create.sql
     or
   mysql -user=username -password=rootspasswordformysql < mysql_create.sql


That's it..restart MySql and try it out

PostgreSql:

  su - postgres  (or whoever your database runs as..usually postgres)

  psql template1 < pgsql_create.sql

That's it, restart PostgreSql and try it out.

=-=-=-=
Notes:
=-=-=-=

     This is by far no complete HOWTO.  This is just a compiled list
of what people have contributed so far.  Some of this is from my
personal experience (MySql and PostgreSql).  If you have tips, ideas,
suggestions or anything else that you think could help others in
setting up their database for use with HORDE please let me know and
I'll include them.  (or contribute to HORDE yourself and change this
file on your own!)
@


1.1.2.2
log
@Correct the location of COPYING
@
text
@d6 1
a6 1
See the file COPYING in the main directory.
@


1.1.2.3
log
@Changed to reflect the correct location of the database scripts.
@
text
@d148 1
a148 1
Use the scripts provided in horde/scripts/database/.  They will make your
d201 1
a201 1
(NOTE: Scripts are located in horde/scripts/database/)
@


1.1.2.4
log
@More documentation updates
@
text
@a3 1
Copyright 2000 Chuck Hagenbuch <chuck@@horde.org>
d8 1
a8 10
Last Updated: 2000-04-09 (cjh)


----
NOTE
----

There are database-specific readme-type files, along with the scripts
mentioned below, in horde/scripts/database/.

d96 16
d118 2
a119 2
database. This user will need pretty much full control over this
database. The username we use for the most part is hordemgr.
d247 7
a253 6
This is by far not a complete HOWTO. This is just a compiled list of what
people have contributed so far. Some of this is from my personal experience
(MySql and PostgreSql). If you have tips, ideas, suggestions or anything
else that you think could help others in setting up their database for use
with HORDE please let me know and I'll include them. (or contribute to HORDE
yourself and change this file on your own!) 
@


1.1.2.5
log
@The manual MySQL instructions had two copies of the INSERT statements to
add the user, and the second set had user "horde" instead of "hordemgr" as
it should be.  Thanks to Barry Lynam <b.lynam@@qut.edu.au> for pointing this
out.

I cleaned up that section by removing the first set of INSERTs and
referring them to the script (since that's where they came from).
Also made capitalization of MySQL and PostrgreSQL consistent and fixed
a few typos.
@
text
@d34 1
a34 1
Horde uses PHPLib to handle its database management.  If 
d39 2
a40 2
   MySQL
   PostgreSQL
d45 2
a46 2
MySQL was the original database supported by HORDE and should at all
times (most likely) work for sure.  PostgreSQL I can verify works
d83 1
a83 1
PostgreSQL and MySQL.  You can find them in config/scripts.
d114 1
a114 1
Here are a few configuration tips for MySQL and PostgreSQL:
d116 1
a116 1
MySQL:
d118 21
a138 1
*** NOTE ***
d140 1
a140 3
The script (horde/scripts/database/mysql_create.sql) does the following
steps so you wouldn't have to retype them.  See the SCRIPTED INSTALL
section, below.
d142 2
a143 2
These commands will setup a user called hordemgr with a password of
'hordemgr' and give it access to the horde database:
d145 2
a146 1
    mysql -u root -p mysql
d148 2
a149 3
       mysql> insert into user (host, user, password) values ('localhost', 'hordemgr', password('hordemgr'));
       mysql> insert into db values ('localhost', 'horde', 'hordemgr', 'y', 'y', 'y', 'y', 'y', 'y');
       mysql> flush privileges
d151 1
d153 1
a153 1
After setting up your tables in MySQL you need to run this command:
d155 1
a155 1
    mysqladmin -u root -p reload
d163 1
a163 1
PostgreSQL:
d180 1
a180 1
database.  PostgreSQL has a switch in one of its configuration files
d201 1
a201 1
MySQL:
d203 1
a203 1
MySQL's script is called mysql_create.sql.  The method you would call
d212 1
a212 1
MySQL: 
d227 1
a227 1
That's it..restart MySQL and try it out
d229 1
a229 1
PostgreSQL:
d235 1
a235 1
That's it, restart PostgreSQL and try it out.
d243 1
a243 1
(MySQL and PostgreSQL). If you have tips, ideas, suggestions or anything
@


1.1.2.6
log
@Capitalization fixes (s/HORDE/Horde/ etc.)
@
text
@d1 1
a1 1
Horde Database Installation Guide
d25 1
a25 1
your database for use with Horde much easier.  The goal
d27 1
a27 1
how to setup the tables and users for Horde.
d31 1
a31 1
Requirements for Horde
d36 1
a36 1
work with Horde.  Currently we know for sure that Horde works
d45 1
a45 1
MySQL was the original database supported by Horde and should at all
d81 1
a81 1
For the 1.2.x version of Horde you will need to install the 
d166 1
a166 1
Without this set to yes Horde won't be able to talk to your database and
d226 1
a226 1
with Horde please let me know and I'll include them. (or contribute to Horde
@


1.1.2.7
log
@Nits and typos.  mysql_create.sql needs to flush privileges after adding
the hordemgr user or we'll get bug reports.
@
text
@d128 1
a128 1
       mysql> create database horde;
d131 1
a131 1
       mysql> flush privileges;
@


1.1.2.8
log
@Substantial edits/improvements to the docs:

(1)  horde/docs/INSTALL: correct subdirectory list
     ** I removed "horde/db" -- if you know something I don't, put it back.
(2)  Gut horde/scripts/database/MYSQL and point them to horde/docs/DATABASE
     ** The db-specific READMEs (esp. PostgreSQL) should get merged into
        horde/docs/DATABASE as we have time.
(3)  horde/docs/DATABASE: tell the user to reload, but not restart
(4)  */docs/INSTALL: clean up the extraction/directory rename instructions
(5)  horde/docs/DATABASE: mention dbpasswd.sh
(6)  */docs/INSTALL: strongly urge the user to use test.php3
(7)  other nits...

Most of these submitted by: Robin Whittle <rw@@firstpr.com.au>
@
text
@a4 1
Copyright 2000 Brent J. Nordquist <bjn@@horde.org>
d9 1
a9 3
$Author$
$Revision$
$Date$
d17 1
a17 3
mentioned below, in horde/scripts/database/.  [Note 06/27/2000 by BJN:
However, the db-specific READMEs are being merged into this file, and
will eventually be obsolete.  For MySQL, this file is the one you want.]
d59 1
a59 16
---------------------------
Database Name/User/Password
---------------------------

Please NOTE that the database configuration steps listed below MUST
match what is configured within Horde/IMP.

Specifically, if you change the database name, user, or password while
configuring the database (below), you will need to make the same changes
to your imp/config/defaults.php3 and phplib/local.inc files as well.

See also the horde/scripts/database/dbpasswd.sh script which can be used
to change the database password in all required locations.


-----------------------
d61 1
a61 1
-----------------------
d77 1
a77 1
=-=-=-=-=-=-=-=
d79 1
a79 1
=-=-=-=-=-=-=-=
d83 1
a83 1
PostgreSQL and MySQL.  You can find them in horde/scripts/database.
d113 1
a113 2
database. The username we suggest is "hordemgr".

d116 1
a116 3
---------------------
MySQL Manual Install:
---------------------
d138 7
a144 3
--------------------------
PostgreSQL Manual Install:
--------------------------
a171 1

d182 6
a187 3
-----------------------
MySQL Scripted Install:
-----------------------
d189 3
a191 3
MySQL's script is called mysql_create.sql.  Please look it over to make
sure that any system specific settings (or personal choices) are set to
your desired settings...ie usernames, etc...
d193 1
a193 2
Then run the script to create the Horde user and tables (you will be
prompted for the MySQL root password):
d195 1
a195 1
   mysql -u root -p < mysql_create.sql
d197 3
a199 1
You then need to do a "reload":
d201 1
a201 1
   mysqladmin -u root -p reload
d203 3
a205 3
----------------------------
PostgreSQL Scripted Install:
----------------------------
a206 3
PostgreSQL's script is called pgsql_create.sql.  Please look it over
to make sure that any system specific settings (or personal choices)
are set to your desired settings...ie usernames, etc...
d208 3
a210 1
Then run the script to create the Horde user and tables:
a217 1

d219 1
a219 1
NOTES:
d226 1
a226 1
with Horde please let us know and we'll include them. (Or contribute to Horde
@


1.1.2.9
log
@Synchronize this doc with recent SQL table optmizations.
@
text
@d10 3
a12 3
$Author: bjn $
$Revision: 1.1.2.8 $
$Date: 2000/06/27 14:59:47 $
d119 5
a123 26
      sid         varchar(32) not null,
      name        varchar(32) not null,
      val         text,
      changed     varchar(14) not null,
      primary key (name, sid),
      key changed (changed)
   )

Table 2:

   imp_addr (
      user        varchar(120) not null,
      address     varchar(120) not null,
      nickname    varchar(255),
      fullname    varchar(255),
      primary key (user, address)
   )

Table 3:

   imp_pref (
      user        varchar(255) not null primary key,
      fullname    varchar(70),
      replyto     varchar(70),
      lang        varchar(30),
      sig         text
@


1.1.2.10
log
@Bring this in line with my last change to the MySQL database schema.
@
text
@a5 1
Copyright 2000 Jon Parise <jon@@horde.org>
d11 2
a12 2
$Revision: 1.1.2.9 $
$Date: 2000/09/09 02:44:43 $
d140 1
a140 1
      user        varchar(120) not null primary key,
@


1.1.2.11
log
@make db example name columns - better sql.

Bug: 469
Submitted by: jsmith@@caldera.com
@
text
@d11 3
a13 3
$Author: jon $
$Revision: 1.1.2.10 $
$Date: 2000/09/10 19:47:23 $
d175 1
a175 3
       mysql> insert into db (host, db, user, select_priv, insert_priv, \
           -> update_priv, delete_priv, create_priv, drop_priv) values \
           -> ('localhost', 'horde', 'hordemgr', 'y', 'y', 'y', 'y', 'y', 'y');
@


1.1.2.12
log
@Make horde/docs/DATABASE and SECURITY just pointers to the imp/docs
versions, so we only have to maintain this info in one place.

Reported by: J Klein <jr_klein@@yahoo.com>
@
text
@d1 6
a6 1
$Horde$
d8 262
a269 2
Please see imp/docs/DATABASE for database installation instructions for
both Horde and IMP.
@


