Bug #60268 "selected name conflicts with existing view" on non-existent view
Submitted: 26 Feb 2011 22:30 Modified: 15 Apr 2011 20:32
Reporter: Brad Moore Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.31 OS:MacOS (10.6.6)
Assigned to: CPU Architecture:Any
Tags: create, VIEW, workbench

[26 Feb 2011 22:30] Brad Moore 
Description:
Workbench throws a "Selected name conflicts with existing view" when trying to create a new view (with the same name as a previously dropped view).

Confirmed that the view doesn't exist by issuing a SELECT * FROM myview (returns error).

Tried using "Refresh All" in the editor on the Views list as well as the schema.  Tried disconnecting and reconnecting to the MySQL server.  Tried creating a new connection (i.e. configuring a new connection with a different name).

Workaround was to copy-paste the CREATE VIEW SQL into the editor window and run it manually.

  

How to repeat:
Create a view (right-clicking views under schema and selecting Create View...).
Drop view (right-clicking views under schema and selecting Drop View...).
Create a view as above with the same name.

Suggested fix:
Either there is local caching going on, or the way the editor is determining existence of a view is non-intuitive.
[15 Mar 2011 20:32] Johannes Taxacher 
what server version are you connecting to when the problem occurs?
also, could you try most recent version of workbench to check if the problem still exists in this version?
thanks in advance
[15 Apr 2011 23:00] Bugs System 
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".