On 7/30/2015 9:09 AM, Sven Schwedas wrote:
On 2015-07-30 15:05, Chris Coleman wrote:
On 7/30/2015 8:57 AM, Christian Mack wrote:
Hello
Am 30.07.2015 um 14:24 schrieb Márcio Merlone:
On 24-07-2015 08:07, Steve Ankeny wrote:
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 --
http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58)
Since I run Ubuntu, I assume the install/upgrade procedure from apt
already does that, is this correct?
No!
You have to do that manually.
Kind regards,
Christian Mack
I nominate adding the database schema upgrade script to the deb and rpm
install/upgrade scripts. It would need to detect the current db schema
version and apply the appropriate db updates. Which it surely does
already...
That automation alone would probably reduce friction by 5%.
Assuming it doesn't have any bugs and blows up your whole database. You
should read the notes anyway, because schema migrations aren't the only
changes between versions.
Reading notes is good, the upgrade script could and probably should take
an automatic backup of the database (similar to a "system restore
point") before applying schema updates.
mysqldump. pg_dump.
The upgrade script including the schema upgrades, would minimize the
human element of errors, forgetfulness, typing error, copy/paste error,
leading to blowing up the database.
--
[email protected]
https://inverse.ca/sogo/lists
