[horde] upgrading a *new* database doesn't look like it's going to work

[Robert P. J. Day]

On Wed, 26 Aug 2009, lst_hoe02 at kwsoft.de wrote:

> -Apply all schema changes since 3.0. If you prepare in advance this
> will not even take a minute to actually apply.

> - Now the trickier Part : You need a new working Horde version to
> run the update scripts. If your brave this can be done with a
> separate Webroot pointing to the same database ;-)

  (just about to head out for lunch, so i'll dash this off.)

  ah, i think i see what you're getting at (maybe).  even without a
working horde install, i can certainly run the scripts that
represent just *schema* changes, since they can be done outside the
context of a working install.

  however, some of the other upgrade steps (move history out of
datatree) need a working install but they can be left until later, is
that what you're saying?  so i can upgrade the DB with all the
possible schema changes, then configure 3.3.4 to refer to that DB, and
finally go back and run the scripts that needed an install context.
is that what you're suggesting.

  off to lunch.  back in a bit.

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
========================================================================