MySQL Bugs: #82873: Manual commit/rollback with auto-commit turned off reports 0 rows affected.

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

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.

Hello Steve Sommer,

Thank you for the bug report.
Imho this is not a bug, I tried to reproduce your issue on CLI and the action is same.

Regards,
Ashwini Patil

8.0.21 test results

Attachment: 82873_results.PNG (image/png, text), 45.09 KiB.

Hi Ashwini,

That's probably because you are using CLI. This bug was opened for MySQL Workbench.

Since it's been a while I'm now running 8.0.20 with autocommit turned out. Note the Output pane does correctly report 1 row inserted but does not show the number of rows rolled back.

Regards,
Steve

MySQL Workbench 8.0.20 Output Grid

Attachment: Screen Shot 2020-10-01 at 7.40.57 AM.png (image/png, text), 901.04 KiB.