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.

Sign up for GitHub

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

Jump to bottom

Warn about "impossible" downs #6

Open
aldeed opened this issue May 22, 2020 · 1 comment
Open

Warn about "impossible" downs #6

aldeed opened this issue May 22, 2020 · 1 comment
Labels
enhancement For issues that describe a feature that needs to be added, changed, or removed, but is not a bug help wanted For issues that have a clear solution described and are not currently prioritized core team work

Comments

@aldeed
Copy link
Contributor

aldeed commented May 22, 2020

Warn and confirm before migrating if any of the up migrations have an "impossible" down. Ask them to be sure they have a current db backup.
@aldeed aldeed added enhancement For issues that describe a feature that needs to be added, changed, or removed, but is not a bug help wanted For issues that have a clear solution described and are not currently prioritized core team work labels May 22, 2020
@brent-hoover
Copy link
Collaborator

How would one programmaticly determine that a down is impossible? I would think that almost any operation that modifies data would be irreversible?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement For issues that describe a feature that needs to be added, changed, or removed, but is not a bug help wanted For issues that have a clear solution described and are not currently prioritized core team work
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@brent-hoover @aldeed