The update operation is automatically committed and there is no way to roll it back. You can only check whether the binlog is enabled, and then go to the log to find the data Reference article: http://database.51cto.com/art/ 201212/374563.htm
Try using rollback first. If it doesn’t work, check to see if there is a binlog. If not, let me give you an idea: If you damage the hard drive, just tell the leader that the hard drive is broken!
The update operation is automatically committed and there is no way to roll it back. You can only check whether the binlog is enabled, and then go to the log to find the data
Reference article: http://database.51cto.com/art/ 201212/374563.htm
Try using
rollback
first. If it doesn’t work, check to see if there is a binlog.If not, let me give you an idea:
If you damage the hard drive, just tell the leader that the hard drive is broken!
Well, when such a tragedy occurs, we can only find
binlog
as the last straw.So the standard operation is: back up the table before all
INSERT
,UPDATE
,DELETE
operations. Don’t trust your brain and paws.