MySQL Bugs: #69800: Shows incorrect value of tx_isolation variable in Workbench.

Bug #69800	Shows incorrect value of tx_isolation variable in Workbench.
Submitted:	20 Jul 2013 4:23	Modified:	27 Jan 2023 18:07
Reporter:	Ye Tang	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.47,6.0.3	OS:	Windows (win7)
Assigned to:		CPU Architecture:	Any
Tags:	workbench tx_isolation

Description:
When execute the command "show variables like 'tx_isolation';" in query window,
I always get 'REPEATABLE-READ'. Although, the 'transaction-isolation' option has been set to 'READ-COMMITTED' in mysqld section in option file. I can get correct value in other tools like mysql command-line client and sqlyog. And I can not find anywhere to change the behave of the Workbench.

How to repeat:
Set the transaction-isolation to be 'READ-COMMITTED' in mysql server.
Execute "show varibales like 'tx_isolation'" in query window of the workbench.

Hello Tang,

Thank you for the bug report. 
Verified as described.

"show variables like 'tx_isolation';" executed in SQL Editor's query window always returns REPEATABLE-READ' where as same query executed on mysql> prompt returns exact value:

mysql> show variables like 'tx_isolation';
+---------------+----------------+
| Variable_name | Value          |
+---------------+----------------+
| tx_isolation  | READ-COMMITTED |
+---------------+----------------+
1 row in set (0.00 sec)

mysql> show global variables like 'tx_isolation';
+---------------+----------------+
| Variable_name | Value          |
+---------------+----------------+
| tx_isolation  | READ-COMMITTED |
+---------------+----------------+
1 row in set (0.00 sec)

mysql> 

Thanks,
Umesh

Does anyone know the actual status of this bug?

It still exist in 6.2.3.12312 build 2280 for Ubuntu 12.04/64 bit.

Its quite a pain, specially in development, when working in non-autocommit mode as SELECT use the snapshot established at the first read.

Non of the changes that happen in other sessions (applications/command line client/etc.) are visible as the isolation is set to REPEATABLE READ for workbench session, even when global isolation is set to other values.

This should be an easy fix, it's very painful for developers to use workbench with this bug. Mac version is also affected.

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?

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

Looking forward offical reply.

Posted by developer:
 
Couldn't reproduce it on newer connector / server.

Closing it.