Database migration #26

New Issue

Open

opened 2023-03-02 05:38:26 +00:00 by crimsen · 0 comments

crimsen commented

2023-03-02 05:38:26 +00:00

Owner

Adding migrations is important, #19, as this allows users to update the database without manual interaction.

TODO:
Some more work is needed, as currently removing / disabling a plugin might break migrations -> can not identifiy which version is the current migration.

Planned workflow:
Every DB change on develop -> new migration file
stable release on main -> merge migrations into one file (cleanup)

So every user on stable can upgrade and downgrade its db and same on develop, but we do not need to provide X migration files for every development step.
So we can clean up at every stable relase, dropping stable migrations is not needed I think, but can be done with some delay.

Adding migrations is important, #19, as this allows users to update the database without manual interaction. TODO: Some more work is needed, as currently removing / disabling a plugin might break migrations -> can not identifiy which version is the current migration. Planned workflow: Every DB change on develop -> new migration file stable release on main -> merge migrations into one file (cleanup) So every user on stable can upgrade and downgrade its db and same on develop, but we do not need to provide X migration files for every development step. So we can clean up at every stable relase, dropping stable migrations is not needed I think, but can be done with some delay.