MySQL Bugs: #66931: Default database missing from sql editor tab

Bug #66931	Default database missing from sql editor tab
Submitted:	23 Sep 2012 12:47	Modified:	27 Oct 2012 14:37
Reporter:	Teodor Hadjiev	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.43	OS:	Windows (Win7 x64)
Assigned to:		CPU Architecture:	Any
Tags:	database, DEFAULT, editor, tab

Description:
Although I saw this as a new feature in some of the latest few versions (5.2.40 if I recall correctly), it seems it is still not working correctly.
If I open an sql editor tab from the home screen, any default database is not shown in the tab, either snapshot-saved from before or selected afterwards.
I could only manage to get the default database name in the tab when I opened a new tab from the current one (New Tab To Current Server - Ctrl+Shift+T). Then both tabs (original and the new one) got the database name in them already.

How to repeat:
Start Workbench and open your first SQL editor tab from some of your DB connections.
Select a database and make it the default (right click - Set As Default Schema).
It gets striked through (I filed another bug report for this) but the tab remains silent about the change.
Also after closing and reopening the connection with snapshot-saving option enabled, the tab doesn't mention the default database either.

Suggested fix:
When opening an SQL editor from the Home screen, the tab should get any already-default database (also if one was specified for the connection itself - this scenario is not working as well), and reflect immediately any change in the default database set in the tree.

Thank you for the bug report. Close/Reopen the connection I can't repeat the behavior reported about default schema however if you meant exit/start WorkBench then the connection don't has the default schema selected before. 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".