Skip to content
This repository was archived by the owner on May 13, 2024. It is now read-only.

feat: Handle auto DB upgrade#47

Open
madmath03 wants to merge 4 commits into
psi-4ward:masterfrom
Monogramm:feat/db_upgrade
Open

feat: Handle auto DB upgrade#47
madmath03 wants to merge 4 commits into
psi-4ward:masterfrom
Monogramm:feat/db_upgrade

Conversation

@madmath03
Copy link
Copy Markdown

feat: Handle auto DB upgrade to fix #45

Signed-off-by: mathieu.brunot mathieu.brunot@monogramm.io

madmath03 added 2 commits May 27, 2020 20:39
Signed-off-by: mathieu.brunot <mathieu.brunot@monogramm.io>
Signed-off-by: mathieu.brunot <mathieu.brunot@monogramm.io>
@madmath03 madmath03 marked this pull request as ready for review May 27, 2020 19:12
@madmath03 madmath03 changed the title WIP: feat: Handle auto DB upgrade feat: Handle auto DB upgrade May 27, 2020
@madmath03 madmath03 marked this pull request as draft May 27, 2020 19:12
Signed-off-by: mathieu.brunot <mathieu.brunot@monogramm.io>
@madmath03 madmath03 marked this pull request as ready for review May 28, 2020 06:44
Signed-off-by: mathieu.brunot <mathieu.brunot@monogramm.io>
@micw
Copy link
Copy Markdown

micw commented Jun 3, 2020

The schema version should be stored along with the database, so the best way to do it is to store it into a custom table. This table can also be used to lock the database during schema update. There are several tools that does exactly this way (liquibase, flyway, sqlalchemie-migrate, ...).

@madmath03
Copy link
Copy Markdown
Author

True... but this would be an evolution in PowerDNS itself, so not really in the scope of this docker container 😅

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handle automatic DB upgrade

2 participants