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

Destructive migration #356

Open
Bolling88 opened this issue Jun 10, 2020 · 7 comments
Open

Destructive migration #356

Bolling88 opened this issue Jun 10, 2020 · 7 comments
Labels
feature Request and implementation of a feature (release drafter)

Comments

@Bolling88
Copy link

Hi!
Are there any plans for adding Destructive migration?
Like, if we change the database, and increase the DB version number, and we don't provide any migration, we can flag that we would like a destructive migration, which means we clear the database and it just keeps working, without crashes.

@vitusortner
Copy link
Collaborator

Hi! This sounds like a great feature request 👍 Let's add destructive migrations.

@vitusortner vitusortner added the feature Request and implementation of a feature (release drafter) label Jun 10, 2020
@Faiizii
Copy link

Faiizii commented Jan 4, 2021

any update on it ?

@vitusortner
Copy link
Collaborator

Unluckily we didn't make any progress on that front. Contributions are welcome!

@Faiizii
Copy link

Faiizii commented Jan 5, 2021

I prepared the contribution, on which branch should I create the pull request? 473

@wamaeb
Copy link

wamaeb commented Apr 11, 2021

Is this available?

@DJafari
Copy link

DJafari commented Mar 5, 2022

@vitusortner any update about this feature ?

@hukjordanjanaq
Copy link

@DJafari still no updates. I use this PR for now #572

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Request and implementation of a feature (release drafter)
Development

No branches or pull requests

6 participants