update from kolab 3.1 to 3.3

[Daniel Hoffend]

Usually if you use the RPM/DEB packages, updatedb.sh is called in the 
%post section or postinst for debian. Usually upgrading the package 
should automatically update the roundcube database.

The downside is that the kolab database (with its *_types tables) 
doesn't provide a version number like the roundcube stuff does. And 
there're no upgrade files in GIT either. That's why I added a few notes 
including the changes into the upgrade guide:

https://docs.kolab.org/administrator-guide/upgrading-from-kolab-3.1-to-3.3.html#mysql-database-kolab

--
Regards
Daniel

------ Originalnachricht ------
Von: "Toke Høiland-Jørgensen" <toke at toke.dk>
An: "Enrico Tagliavini" <enrico.tagliavini at gmail.com>
Cc: "users at lists.kolab.org" <users at lists.kolab.org>
Gesendet: 18.09.2014 10:16:53
Betreff: Re: update from kolab 3.1 to 3.3

>Enrico Tagliavini <enrico.tagliavini at gmail.com> writes:
>
>>  just for your knowledge: there is an easy way to update the database
>>  schema. The roundcube DB schema updates can be found at
>>  /usr/share/doc/roundcubemail-<version>/SQL/
>
>Nice to know!
>
>Would it be possible to have an 'upgrade' task to the setup-kolab that
>knew which db schema upgrades to apply (not asking you specifically,
>more of a general feature request)? :)
>
>-Toke