[turba] how to simplify my turba upgrade process

[Robert P. J. Day]

On Mon, 31 Aug 2009, Michael Rubinsky wrote:

> Can you point me to where in the docs referring to turba_objects is
> misleading you?

  ok, it's possible i was confusing myself between two of the upgrade
scripts.  i think we can both agree that, if there was an upgrade
script somewhere in turba/scripts/upgrades whose invocation upgraded
*only* the "turba_objects" table with no option to upgrade *other*
tables that represented addressbooks, and the accompanying
documentation *also* didn't make it clear that you should run that
script on all of your other addressbook tables, that would be somewhat
misleading.  but i can't find such an example, so i'm thinking i
misread something.  sorry.

rday

p.s.  oh, wait, here's an example but it might be so old, it's not
relevant.  ugpgrading to turba 2.0, the UPGRADING doc reads:

=====

Four new fields have been added to the default SQL table layout, one
being mandatory.  The new ``object_uid`` field provides a global
unique ID to objects.

Execute the provided SQL script to update your data to the new Turba
version::

   mysql --user=root --password=<MySQL-root-password> <db name> <
1.2_to_2.0.sql

=====

  the script 1.2_to_2.0.sql reads, in full:

=====

ALTER TABLE turba_objects ADD COLUMN object_uid VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_freebusyurl VARCHAR(255);
ALTER TABLE turba_objects ADD COLUMN object_smimepublickey TEXT;
ALTER TABLE turba_objects ADD COLUMN object_pgppublickey TEXT;

=====

  that script clearly updates the schema of only the turba_objects
table, and the documentation says nothing about having to do that for
*all* addressbook tables that might exist, but since that refers to a
very old version of turba, maybe (and i'm just guessing) that that
wasn't relevant back then or something.

  so am i at least making sense here?  in the sense that, during the
upgrade process (and i'm going from turba 2.0.5 to 2.3.1), any
instructions and/or scripts that describe upgrading the schema of
turba_objects should also effect or make it clear that that upgrade
should be done on *all* addressbook tables.  i guess that's the only
point i was trying to make.

  more shortly.

--

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

        Linux Consulting, Training and Annoying Kernel Pedantry.

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