migrating some addressbooks forward to a newer turba release?

[Robert P. J. Day-2]

  hi, i want to follow up on some questions i had quite a number of
weeks ago regarding upgrading horde and a number of apps on a debian
server that was itself being upgraded in a huge way (currently running
lenny).  here's the situation.

  currently, on debian lenny server, i have the basic horde framework
installed -- from the horde admin setup page, i'm told it's version
3.3.4 so that's new enough for what i'm after.

  i have four SQL-format addressbooks that used to be accessible thru
a much older turba, and i obviously want to make them available thru
turba on *this* horde installation.  i did go through an exercise of
upgrading the addressbook formats, but it's hard to know if i did that
properly.  at the moment, in MySQL, i have a horde database with four
addressbooks:

  turba_clients
  turba_customers
  turba_objects
  turba_suppliers

if it's not unspeakably painful, i'd like to just install the most
recent stable version of turba (2.3.2) and hook those addressbooks in
again.  right now, in horde config, turba is listed as version 2.3.1
(maybe that's good enough for now unless there's a compelling reason
to switch), and it's listed as "Missing configuration. You must
generate it before using this application.", which i expected since i
haven't configured any of the addressbooks.

  given only four addressbooks, would it just be easiest to install
the latest fresh version of turba, then figure out what it takes to
hook one addressbook back in, at which point the rest should follow
quickly?  if memory serves, i had to change the schema of the
addressbooks but i don't remember how.  in any event, is it just
easiest to install a new turba 2.3.2, then do what it takes to add the
addressbooks back?  (possibly having to adjust the schemas if that
becomes necessary?)

  thanks.

rday
--

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

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================
--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe@...

[Michael Rubinsky-2]

Quoting "Robert P. J. Day" <rpjday@...>:

> > hi, i want to follow up on some questions i had quite a number of
> > weeks ago regarding upgrading horde and a number of apps on a debian
> > server that was itself being upgraded in a huge way (currently running
> > lenny).  here's the situation.
> >
> >   currently, on debian lenny server, i have the basic horde framework
> > installed -- from the horde admin setup page, i'm told it's version
> > 3.3.4 so that's new enough for what i'm after.
> >
> >   i have four SQL-format addressbooks that used to be accessible thru
> > a much older turba, and i obviously want to make them available thru
> > turba on *this* horde installation.  i did go through an exercise of
> > upgrading the addressbook formats, but it's hard to know if i did that
> > properly.  at the moment, in MySQL, i have a horde database with four
> > addressbooks:
> >
> >   turba_clients
> >   turba_customers
> >   turba_objects
> >   turba_suppliers
> >
> > if it's not unspeakably painful, i'd like to just install the most
> > recent stable version of turba (2.3.2) and hook those addressbooks in
> > again.  right now, in horde config, turba is listed as version 2.3.1
> > (maybe that's good enough for now unless there's a compelling reason
> > to switch), and it's listed as "Missing configuration. You must
> > generate it before using this application.", which i expected since i
> > haven't configured any of the addressbooks.
> >
> >   given only four addressbooks, would it just be easiest to install
> > the latest fresh version of turba, then figure out what it takes to
> > hook one addressbook back in, at which point the rest should follow
> > quickly?  if memory serves, i had to change the schema of the
> > addressbooks but i don't remember how.  in any event, is it just
> > easiest to install a new turba 2.3.2, then do what it takes to add the
> > addressbooks back?  (possibly having to adjust the schemas if that
> > becomes necessary?)

If none of those addressbooks were using shares, which if it was a  
*much* older version of Turba, they probably didn't, you really don't  
need to do much at all. If you are OK with keeping the same schema,  
and the same fields available, you *should* be able to just copy over  
the relevant portions of config/sources.php into the new  
config/sources.php (and, of course, migrate the tables to the new DB  
server, if you are using one).  If you want to update the schemas to  
be more in line with the newer, more groupware like schema that's  
available in the newer Turbas, then you will have to tweak your DB  
schemas to match what you want.

--
Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk@...
--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe@...

[Robert P. J. Day-2]

On Wed, 4 Nov 2009, Michael J. Rubinsky wrote:

> If none of those addressbooks were using shares, which if it was a
> *much* older version of Turba, they probably didn't, you really
> don't need to do much at all. If you are OK with keeping the same
> schema, and the same fields available, you *should* be able to just
> copy over the relevant portions of config/sources.php into the new
> config/sources.php (and, of course, migrate the tables to the new DB
> server, if you are using one).  If you want to update the schemas to
> be more in line with the newer, more groupware like schema that's
> available in the newer Turbas, then you will have to tweak your DB
> schemas to match what you want.

  so it sounds like i can install a fresh, current version of turba,
then just copy the relevant parts of the old sources.php file and
perhaps tweak them slightly if i want.  the addressbooks are already
in mysql on the server so all i need to do is point at them, yes?
i'll give that a shot.

rday
--

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

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================
--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe@...