Bug #99337 Changes to connection/query timeout value are not saved
Submitted: 23 Apr 2020 16:42 Modified: 23 Apr 2020 21:47
Reporter: Edward Leigh Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.19, 8.0.42 OS:Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:x86
Tags: WBBugReporter

[23 Apr 2020 16:42] Edward Leigh
Description:
Any change to the default value of 60 seconds in the Advanced panel of a Connection's settings is not saved. The next time the connection settings is opened, the figure has reverted to 60.

The log file contains no record of changing the Timeout value.

How to repeat:
Open Manage Server Connections.
Select a connection.
Click on the Advanced tab under Connection.
Change the Timeout value.
Click Close.

Open Manage Server Connections.
Select the same connection as before.
Click on the Advanced tab under Connection.
Verify that the Timeout value has reverted to 60.

Suggested fix:
Save the Timeout value before the next dialog event is processed.
[23 Apr 2020 21:47] MySQL Verification Team
Thank you for the bug report.
[3 Jul 2025 8:30] MySQL Verification Team
Bug #118582 marked as duplicate of this one.
[14 Sep 18:05] Omer Barnir
Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.