The terms revert and amend have a well defined meaning in Git. In contrast, rollback and undo do not have such a well defined meaning, and are open to interpretation. Reverting a commit… …means creating (on the current branch) a new commit that applies the inverse changes that another commit introduced. It’s the preferred approach … Read more
Rolling back all migrations To rollback all migrations the best solution is the one @Claudio Floreani proposed: rake db:migrate VERSION=0 This will rollback every migration. You can read why this is the best approach in his answer. Then, run all migrations again with rake db:migrate Resetting the database Reset rake db:migrate:reset #runs db:drop db:create db:migrate … Read more
If you haven’t made a backup, you are pretty much fudged.
git reset –hard HEAD^1 will take you back one commit from what you pulled. If you want it back to the state it was in before you pulled, use git reset –hard HEAD@{1}. The @{1} tracks where the head was at before the last operation that changed it in your local repo, so it will … Read more
While Flyway supports rollbacks (as a commercial-only feature) its use is discouraged: https://flywaydb.org/documentation/command/undo While the idea of undo migrations is nice, unfortunately it sometimes breaks down in practice. As soon as you have destructive changes (drop, delete, truncate, …), you start getting into trouble. And even if you don’t, you end up creating home-made alternatives … Read more
If you define table type as InnoDB, you can use transactions. You will need set AUTOCOMMIT=0, and after you can issue COMMIT or ROLLBACK at the end of query or session to submit or cancel a transaction. ROLLBACK — will undo the changes that you have made
You just need this command: hg rollback See: http://hgbook.red-bean.com/read/finding-and-fixing-mistakes.html. (Technically, this is deprecated as of version 2.7, August 2013, but I’ve yet to see an alternative that does exactly the same thing.)
None of the other answers fix the root cause of the issue. The problem is that when Postgres raises an exception, it poisons future transactions on the same connection. The fix is to rollback the offending transaction: begin ActiveRecord…do something… rescue Exception => e puts “SQL error in #{ __method__ }” ActiveRecord::Base.connection.execute ‘ROLLBACK’ raise e … Read more
Dispose method for transaction class performs a rollback while Oracle’s class doesn’t. So from transaction’s perspective it’s implementation dependent. The using statement for the connection object on the other hand would either close the connection to the database or return the connection to the pool after resetting it. In either case, the outstanding transactions should … Read more
Download and install Team Foundation Power Tools. Open up the Visual Studio command prompt Navigate to the directory on the file system that TFS is mapped to. If you don’t do this you’ll get an “Unable to determine the workspace” error when you try to roll back Make sure everything else is checked in or … Read more