Internally, we talked about automatic schema upgrades multiple times. The current state of manual schema upgrades are far from perfect from a user's point of view and have resulted in messy situations in the past1.
I created this issue to collect ideas and to keep the problem on our radar.
There was already #770, but IMO letting Icinga DB just apply any schema upgrade will result in other kinds of errors, as explained there.
In a broader sense, this issue is not Icinga DB-only, but also applies to other daemons with a relational database schema, such as Icinga Notifications.
Internally, we talked about automatic schema upgrades multiple times. The current state of manual schema upgrades are far from perfect from a user's point of view and have resulted in messy situations in the past1.
I created this issue to collect ideas and to keep the problem on our radar.
There was already #770, but IMO letting Icinga DB just apply any schema upgrade will result in other kinds of errors, as explained there.
In a broader sense, this issue is not Icinga DB-only, but also applies to other daemons with a relational database schema, such as Icinga Notifications.
Footnotes
There are multiple reports of forgotten or incorrectly applied upgrades in the community forum. ↩