Bug #60610 Don't assign a correct tab name when open a sql script

• Submitted: 24 Mar 2011 0:28
• Modified: 6 Jun 2011 22:14
• Reporter: Ivan Cachicatari
• Status: Closed
• Category: MySQL Workbench: SQL Editor
• Severity: S3 (Non-critical)
• Version: 5.2.33 rev 7506
• OS: Any (Ubuntu 10.10, Mac OS X)
• CPU Architecture: Any

[24 Mar 2011 0:28] Ivan Cachicatari

Description:
Workbench don't assign a correct tab name when open a sql script from recent file list menu.

How to repeat:
1. Open SQL Editor
2. Try to open a recent sql file from Menu: File->Open Recent...
3. Workbench will create a new tab but without the file name opened (SQL File # is placed instead).

[24 Mar 2011 4:32] Valeriy Kravchuk

SQL Script # is used as a tab name even if I explicitly open script...

[24 Mar 2011 4:59] Ivan Cachicatari

I found another bug:
My recent list may be:
1: sql01.sql
2: sql02.sql
3: sql03.sql
4: sql04.sql

When I select a file from recent list, for examen the option 4 (sql04.sql), Workbench open another file in this case opens the second sql02.sql.

Please verify.

[18 May 2011 20:17] Johannes Taxacher

Bug #61217 has been marked as duplicate of this one

[3 Jun 2011 13:07] Peter Platek

RE: [24 Mar 5:59] Ivan Cachicatari

Same thing happens on Mac as well, to reiterate: wrong file from the list of "open recent" files is opened.

[6 Jun 2011 22:14] Paul DuBois

Noted in 5.2.34 changelog.

Workbench did not assign a correct tab name when opening an SQL
script from the recent file list menu.