Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Local database schema changes (migrations) after release #180

Open
nicanorgarcia opened this issue Oct 23, 2018 · 2 comments
Open

Local database schema changes (migrations) after release #180

nicanorgarcia opened this issue Oct 23, 2018 · 2 comments
Labels
bug Something isn't working

Comments

@nicanorgarcia
Copy link
Collaborator

We recently found that if a previous version of the database was installed and the application was updated (new build), the app would crash (in this case, new tables were not found).

We need to implement a way to update the database if the schema is changed once the app is released.

@nicanorgarcia nicanorgarcia added the bug Something isn't working label Oct 23, 2018
@AKuederle
Copy link
Collaborator

Shouldn't this be a well supported scenario? We aren't the only people that need database migrations

@PKlumpp
Copy link
Collaborator

PKlumpp commented Nov 1, 2018

This is pretty straightforward to solve. Every Database has a unique version ID. If this ID does not match the most recent one, the database should provide (implement) the migration to transfer content from the old version to the most recent one. So I would not consider this a bug. It sounds more like missing code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants