[horde] 3.2 database?

[Chuck Hagenbuch]

Quoting Kevin Konowalec <webadmin at ualberta.ca>:

> I'm in the final stages of putting together a rebuild of our system on
> RC3 of horde, imp, turba, etc.  I'm wondering if there are any changes
> to the existing database tables for the new version?  I'd like to just
> be able to use our production database to test against but I don't
> want to alter any of the tables that are in use by the existing
> version.  I noticed there are a few new tables needed but don't know
> if any changes are required to existing ones.
>
> Can I just run the scripts/upgrades/3.1_to_3.2.mysql.sql script on my
> production database or will that bone me for my 3.1 installation?
> Would it be better to just install another instance of mysql and work
> on it there?

Well, taking Horde as an example, the only destructive change in the  
SQL script is removing old syncml entries from the datatree. If you  
don't use SyncML in production, you're fine.

Your mileage may vary with other apps - look at the upgrade script,  
and see if there are any ALTER, UPDATE, DELETE, or other potentially  
destructive changes. You can ignore changes that increase a field's  
length, for instance, but possibly not others.

-chuck

-- 
"I have concerns that we are not behaving like a mature, responsible,  
collection of interdependent organisms." - Rick O.