-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
FallbackToDestructiveMigration feature #7786
Labels
Comments
I found different workarounds for this in StackOverFlow. |
We don't have explicit support for it right now, but you could just catch the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we are using a Room database, we are allowed to use .fallbackToDestructiveMigration() option.
Setting this option, Room tries to execute the migrations we specified. If any error occurs, Room will delete the schema.
How can we achieve this with Realm. .deleteRealmIfMigrationNeeded() is just dropping the database. It just ignores the migration.
The text was updated successfully, but these errors were encountered: