I updated my PhpMyAdmin database engine from MyISAM to INNODB to allow rollback.
This is my SQL query :
START TRANSACTION;
UPDATE jkm_content SET st
Changes you made within one transaction are not visible to other transactions (except transactions with READ UNCOMMITTED isolation level) until the transaction is committed.
There is a huge difference between rolling back transaction and keeping it open forever (or until the engine kill it due to timeout). The latter means server cannot free resources allocated to support transaction. In addition, since you do UPDATE, mysql has to issue exclusive locks on rows affected, and no other transaction can update/delete these rows. If you have an application that leaves transactions open, you will very likely end up with either all connections busy and waiting forever, or bunch of deadlocks .
Yes, they all start a new transaction in mysql.