[turba] horde db shortcomings

[Marcus I. Ryan]

Quoting "Eric S. Johansson" <esj at harvee.org>:
> bad choice of words on my part.  If you are going to use a database and
> include any documentation for a particular variety of database then it
> should state basic assumptions and make sure supplied code works.
> otherwise no database scripts should be supplied in the user should be
> left to enter what ever schema was required manually.  supplying scripts
> that cannot work right is actually worse than the second option.

psql -f <script file> <dbname> <username>

I haven't hit a script that hasn't worked.  As for documentation, as others
have already said, the real bragging rights and goal of Horde is to not offer
a solution to a small set of people running a very specific suite of software
but to offer software that works with a vast array of backends.
Unfortunately that makes writing documentation to a specific style of install
very difficult, let alone to each backend.  Through PEAR::DB native drivers
we support nearly a dozen database backends.  Through Pear::DB's ODBC driver,
there are dozens, if not hundreds more.

However, if you check out the hordedoc module you will find, among other
things, hordedoc/hordeadmin/work/MyISP which is a walkthrough from beginning
to end of installing FreeBSD with PostFix, Cyrus, PostgreSQL, and all the
Horde modules in CVS at the time of that writing.  It includes a details
walkthrough of installing PostgreSQL, it's startup files, adding users, etc.
It also covers configuring horde to use PGSQL, though the version of horde
and modules refers to a now rather old CVS install (pre-snapshots even), but
the information is generically useful if you pay attention.

--
Marcus I. Ryan, marcus at horde.org
-----------------------------------------------------------------------
 "Love is a snowmobile racing across the tundra and then suddenly it
 flips over, pinning you underneath.  At night, the ice weasels come."
                 -- Matt Groening
-----------------------------------------------------------------------

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.