agrosner / agrosner/DBFlow

Drop Schema instead of migrating.

Open
#1,349 7 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Kotlin
Stars
4.8k
Forks
593
Avg merge
1m
Merged PRs (30d)
1

Description

DBFlow Version: 4+
Issue Kind: Question

Description:
Sometimes it is not necessary to migrate data from version to version. For example models have significantly changed and we don't need locally stored data on upgrade as we will refresh it from the backend anyway. It would save us a lot of time if we could just drop my schema and let dbFlow generate a new DB when the versions change....instead of spending a lot of time writing migration scripts.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.