MySQL Bugs: #49282: DROP SCHEMA does not remove schema from SQL Editor

Bug #49282	DROP SCHEMA does not remove schema from SQL Editor
Submitted:	1 Dec 2009 17:34	Modified:	21 Jan 2010 16:48
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.10	OS:	Any
Assigned to:	Sergei Tkachenko	CPU Architecture:	Any

Description:
I dropped a database/schema with one table in it.  After confirming, the schema remained in the SQL Editor.  Navigating away and back has no impact; the table even remains.

Furthermore, there appears to be no indication of success/failure of the DROP DATABASE command; while the database has indeed been dropped, running the same command repeatedly (because it lets you) generates no error or message, despite the fact that the database no longer exists.

How to repeat:
DROP SCHEMA
DROP SCHEMA
DROP SCHEMA

Suggested fix:
Remove the dropped schema once it is dropped.
Provide appropriate confirmation or alert if statement fails.

Also, dropping INFORMATION_SCHEMA (which fails for insufficient privileges) doesn't generate any error message, even though it clearly should.

Added reference from here to Bug #49454, which generally describes what is missing.

Todd, as a workaround do a manual refresh (context menu => "Refresh All").

schema representations are now removed from overview and sidebar-tree.
will be included in 5.2.12

An entry has been added to the 5.2.12 changelog:

In the SQL Editor, when a schema was dropped, it was still displayed in the Overview tab and in the schemata explorer of the side panel. Further, MySQL Workbench did not provide any confirmation that the schema had been dropped successfully or otherwise.