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

Investigate the need to support database downgrading #6315

Closed
grzesiek2010 opened this issue Aug 8, 2024 · 0 comments · Fixed by #6366
Closed

Investigate the need to support database downgrading #6315

grzesiek2010 opened this issue Aug 8, 2024 · 0 comments · Fixed by #6366
Assignees
Milestone

Comments

@grzesiek2010
Copy link
Member

Problem description

Our databases (forms, instances, savepoints, entities) currently support downgrading through the #onDowngrade method, which simply recreates the database from scratch. However, this feature may be unnecessary since Android does not allow app downgrades (you must uninstall the newer version before installing an older one).

We began considering this issue in this discussion, so it would be worthwhile to investigate whether we can eliminate the downgrading mechanism entirely or if it is still necessary (for example, if downgrading is possible using ADB or other methods).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: done
Development

Successfully merging a pull request may close this issue.

2 participants