MySQL Bugs: #86880: MySQL Workbench set tx_isolation=REPEATABLE-READ regardless of the server's defi

Bug #86880	MySQL Workbench set tx_isolation=REPEATABLE-READ regardless of the server's defi
Submitted:	30 Jun 2017 8:45	Modified:	6 Jun 2018 8:14
Reporter:	镇熙林	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	6.3.9	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
I set transaction_isolation=READ-COMMITTED in <my.cnf>, and get right result in command line:

[root@localhost][(none)]> select @@global.tx_isolation,@@session.tx_isolation;
+-----------------------+------------------------+
| @@global.tx_isolation | @@session.tx_isolation |
+-----------------------+------------------------+
| READ-COMMITTED        | READ-COMMITTED         |
+-----------------------+------------------------+
1 row in set (0.00 sec)

But when I execute the same SQL in MySQL Workbench, @@session.tx_isolation is REPEATABLE-READ. It seems that MySQL Workbench change session value of tx_isolation regardless of the server's definition for that parameter. That's unacceptable, because runing script in MySQL Workbench will block other script.

How to repeat:
see Description

Hello!

Thank you for the report and feedback!
Observed this with WB 6.3.9 on Win7.

Thanks,
Umesh

I check MySQL Workbench 6.3.9 and 6.3.10, but the problem not resolved.

Hi, MySQL bug support team, We have met the same issue in 

MySQL Version: MySQL 5.6.26 
MySQL workbench Version: 6.3 CE.

Reprodure:
Step1: check the my.cnf files to confirm the transaction isolation was setting as Read-committed.
Step2: open one connection in MySQL workbench
Step3: Go to audit log and check what has been done:
I have found: the SQLTEXT like below, the line3 updated the isolation:
SET NAMES utf8
set autocommit=1
SET SESSION TRANSACTION ISOLATION LEVEL REPEATABLE READ
SET CHARACTER SET utf8
SET NAMES utf8
Step3: Check the session level transaction isolation.
it retruned REPEATABLE-READ.
show session variables like 'tx_isolation';

Step4: check other applicaitons, I have checked by MySQL client for linux, Toad for MySQL, Sqlyog, all shows with correct value: show session variables like 'tx_isolation'; as Read-committed.

What we have done: 
1. We tried to modify the file from installnation file: modules/opts.py for the transaction-isolation, we changed the default value to READ-COMMITTED, and restart the MySQL Workbench, but it not helped.
then we tried to remove the setting for the transaction_isolation and innodb_api_trx_level line and  it not helped either.

2. We tried to find somesettings on MySQL workbench GUI, but nothing related to the isolation setttings.

Please help to identify the root cause and provide a solution or ETA for fixing. Thanks.

Hi, I have found new update under this ticket:
https://bugs.mysql.com/bug.php?id=78852

But it says, this only fixed in 8.0 Version. How about the 6.2 and 6.3 Verison?

Looking forward offical reply.

Hi, I have found new update under this ticket:
https://bugs.mysql.com/bug.php?id=78852

But it says, this only fixed in 8.0 Version. How about the 6.2 and 6.3 Verison?

You can merge these 3 tickets as one ticket.
Bug no:
#69800
#86880
#78852

Looking forward offical reply.

Hi, I have found new update under this ticket:
https://bugs.mysql.com/bug.php?id=78852

But it says, this only fixed in 8.0 Version. How about the 6.2 and 6.3 Verison?

You can merge these 3 tickets as one ticket.
Bug no:
#69800
#86880
#78852

Looking forward offical reply.