[horde] the order of doing a horde upgrade

[Robert P. J. Day]

  just realized something critical, and want to verify it.  to move
from 3.0.9 to 3.3.4, i installed 3.3.4 in a sibling directory and, as
a test, browsed explicitly to that directory and got a generic new
horde screen.  perfect.  obviously nothing there as it represents
simply unloading the horde-3.3.4 tarball -- no configuration at all
yet.

  my next step was to go into the configuration process and, tab by
tab, reproduce what i see in the old (3.0.9) conf.php file, *except*
that, for safety's sake, i'm setting the new install to refer to a
*new* horde database, "horde334", which will represent the old one
after it's been upgraded (so i can preserve the old "horde" database,
for whatever reason).

  i hadn't set up the new horde database yet, but went through the
3.3.4 configuration, saved it, then tried to connect but failed to get
authenticated, and i'm *guessing* that, since the new install has been
set up to point to the new "horde334" database, and that database
doesn't even *exist* yet, i kind of screwed myself.  (default admin
and password, anyone?)

  in any event, this suggests that the very first thing i should do is
get that database upgraded and installed, *after* which i should
configure horde-3.3.4 to point to it.  is that pretty much the fatal
mistake i made here?  doing those things in the wrong order?  thanks.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================