On 07/30/2015 12:46 PM, Chris Coleman wrote:
Yes, but I believe the goal is (and needs to be) zero-effort upgrades,
to whatever extent possible within reason.
For the admins using 3 different database engines, to provide separate
login (microsoft ldap), session (mysql in memory), and data storage
(postgres) , to achieve extreme high performance, maybe we can let
them risk manually running db schema upgrade scripts (and run the
wrong versions of the schema scripts, or completely forget to run
them), but even then, a config file parser class should automatically
extract those 3 sets of db credentials from sogo.conf and perform
automated schema upgrades.
If you run the wrong script, it fails. The script did not change the
schema except to expand one of the calendar fields from a few characters
to many, so there was no risk whatsoever. As my initial response
suggested --
The only issues I remember with the running of the script were --
(1) users fail to run it
(2) or, they run the wrong script
Instructions are*always* at the back pages of the Installation Guide
I believe you answer it yourself when you suggest "to whatever extent
possible within reason" Go read about my struggle to upgrade the Ubuntu
'samba' package with the Inverse package. Isn't always "zero-effort"
--
[email protected]
https://inverse.ca/sogo/lists
