Bug #60569 Unexpected SQL editor saved state behaviour

• Submitted: 21 Mar 2011 15:48
• Modified: 31 Aug 2011 21:37
• Reporter: Stephanie Sullivan
• Status: Closed
• Category: MySQL Workbench: SQL Editor
• Severity: S3 (Non-critical)
• Version: 5.2.33
• OS: Windows
• CPU Architecture: Any

[21 Mar 2011 15:48] Stephanie Sullivan

Description:
The restoration of a previously closed session creates extra query tabs

How to repeat:
Open a sql development connection
Create and save a sql script of 'select 1' in query tab 1 as 'Script1'
Create and save a sql script of 'select 2' in query tab 2 as 'Script2'
Close and re-open workbench allowing it to save state

When I do this I have 3 tabs: SQL File 1 (containing query 1), Query 1 (containing query 1), Query 2 (containing query 2)

[24 May 2011 22:00] Alfredo Kojima

Verified a similar problem with 5.2.34, although it is better, but still not reliable in Windows.

[31 Aug 2011 21:37] Philip Olson

Fixed as of 5.2.35:

+        On Microsoft Windows, the following scenario generated an error
+        and a bogus SQL editor tab upon &workbench; restoration: Having
+        multiple open SQL Editor tabs, closing the first, and then
+        closing the database connection (while the <literal>Auto-save
+        scripts interval</literal> option is enabled).