Bug #1515
Database shema mismatch is not detected and remedied
Status:
New
Priority:
Normal
Assignee:
-
Category:
Quassel Core
Target version:
-
Start date:
02/11/2019
Due date:
% Done:
0%
Estimated time:
Version:
0.13.0
OS:
Linux
Description
I just recently found out that the database schema my instance had did not match what Quassel core was supposed to create, this caused massive slowdowns, data corruption and was overall an huge hassle. This could have been avoided if Quassel verified the database before starting each time. I also propose that if a mismatch is detected the schema should be automatically fixed.