Bug #82873 Manual commit/rollback with auto-commit turned off reports 0 rows affected.
Submitted: 6 Sep 2016 16:10
Reporter: Steve Sommer Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S4 (Feature request)
Version:6.3.7 OS:Mac OS X (OS X 10.11.x El Capitan)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[6 Sep 2016 16:10] Steve Sommer
Description:
----[For better reports, please attach the log file after submitting. You can find it in /Users/ssommer/Library/Application Support/MySQL/Workbench/log/wb.log]

When auto-commit is turned off and a DML statement is issued then manually committed or rolled back, the response from MySQL Workbench is "0 row(s) affected". This is misleading as it implies either the auto-commit was in fact in place or the DML statement did not change anything. It would be beneficial to state how many records were in fact committed or rolled back.

How to repeat:
Issue the following statements and monitor the ACTION OUTPUT section.

create table T1 (
foo INT);

insert into T1 values (19);

rollback;

select * from T1;

Suggested fix:
Clarify the feedback of DML actions when auto-commit it turned off to include the effect row count.