You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thus this issue is closed as transactions are now built in, but mysql still wont rollback any ddl actions such as drop table.
Nevertheless, migrations will get more intelligent in the next versions of db-migrate. So db-migrate knows about states, tables and metadata.
But this still wont fix a deleted table and restore the data within this, may be I will offer a dump table action on all ddl actions, which can optionally be activated.
Implement transactions per migration, thus everything gets rolled back on failure.
Notes:
Make it possible to deactivate transactions within the migrations.
Drivers gets flagged with transaction capability
The text was updated successfully, but these errors were encountered: