-
Notifications
You must be signed in to change notification settings - Fork 192
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
Destructive migration for missing or broken migrations #572
base: develop
Are you sure you want to change the base?
Conversation
40b6824
to
324ccdc
Compare
Hi, have you fix it? How can I use this in pubspec.yaml? |
You are missing the path, e.g.:
|
Thank you so much for answering. Should I use ref: destructive-migration-test or ref: destructive-migration? With ref: destructive-migration i'm getting and error. |
@vitusortner could you please check it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems alright
Hello everyone, are there any updates? |
This add the ability to configure your database to drop all existing data if a migration fails or is missing.
These changes are inspired by #473 but do not always drop the scheme if
fallbackToDestructiveMigration
is set totrue
.Additionally, when dropping data, these changes make sure to drop all existing tables and views, without relying to the current available metadata.