MySQL Bugs: #61856: Open Recent SQL opens wrong script

Bug #61856	Open Recent SQL opens wrong script
Submitted:	13 Jul 2011 17:19	Modified:	18 Nov 2011 0:12
Reporter:	Bill Baker	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.34, 5.2.35	OS:	Any (Fedora Core 15, Windows)
Assigned to:		CPU Architecture:	Any
Tags:	file open, recent, stored SQL

Description:
I have several SQL utility scripts that I store in a SQL directory on my local machine. I use some of them quite frequently and so they are listed in the File -> Open Recent list. The first time I select a recent sql script from the list after opening workbench - the correct one is opened but if I follow the 'how to repeat' steps all subsequent ones are wrong.

How to repeat:
1. Open workbench and select a connection so the SQL Editor tab is active.
2. Select an entry in the File -> Open Recent that is somewhere below the first one in the list.
3. Do this operation again for a 'Recent' file that is above the one in the list you just opened and it will open the wrong script.

Thank you for the bug report. Testing on Windows I got the following behavior:

Open a connection tab.
Open a recent file says the 5th of the list.
Click Open in the dialog warning saying the current one will be closed.
The above opened model goes to the top of the list of open recent item menu.
Open recent which was placed above the first recent opened.
At random way sometimes works correctly, sometimes opens several model.
Quitting the application always crashes.

Have you notided similar behavior?. Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Miguel,
I am not using windows - so I can't address your situation directly. I am not referring to opening different database models - only opening stored SQL files using the File -> Open Recent mechanism. I am not seeing program crashes from this problem, only that the wrong SQL file is opened. I have tried your scenario and it appears to work in the manner you state - only that the program doesn't crash.

Thanks a lot for your report Bill.
Reproduced as stated for the reported.
Thanks.

Bug #63121 was marked as a duplicate of this one.

Fixed as of 5.2.36:

+        The <guimenu>File</guimenu>, <guimenu>Open Recent</guimenu>
+        feature would open the incorrect script.