-
Notifications
You must be signed in to change notification settings - Fork 662
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
Support rollback of SQL schema change #17
Comments
Do you mean to (1) only backup the schema or (2) the data as well as the schema (like mysqldump) ? |
I have added an instance, but I do not see the database information on the instance.If I add a database, I will be prompted that the database already exists. |
Sorry, I am a bit lost here as I couldn't see how it's related to the original "backup of sql change" question. Could you please elaborate a bit more? |
sorry,I confused the two issues. This issue wants to know how to facilitate rollback after database changes |
Do you mean to rollback the schema change like specifying a down "script" as opposed to "up" statement similar to ruby migration? https://edgeguides.rubyonrails.org/active_record_migrations.html ? If that's the case, we are planning to add this in couple weeks. Stay tuned. |
Released in 0.4.1 https://github.com/bytebase/bytebase/releases/tag/0.4.1 |
Can you provide a function for backup of sql change?
This is very necessary for production environment.
The text was updated successfully, but these errors were encountered: