Project

General

Profile

Bug #1507

Database schema should not be automatically updated without backup

Added by mgorny over 1 year ago.

Status:
New
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
01/03/2019
Due date:
% Done:

0%

Estimated time:
Version:
0.13.0
OS:
Any

Description

So we've upgraded quassel on our server only to discover the new version crashes beyond usability. However, since upon starting quasselcore it immediately updated the database without any prior warning or backup, I'm now stuck with database that's incompatible with the previous version. I really do think that potentially destructive, non-trivially reversible actions such as database schema upgrade should not happen without prior warning.

I would like to request that whenever quasselcore needs to perform a database update, it refuses to start and explicitly requests confirmation e.g. via additional command-line option. Additionally, it would probably be a good idea to suggest user to make a backup while at it.

Also available in: Atom PDF