Bug #17739 Editing Views causes view to be dropped
Submitted: 27 Feb 2006 14:29 Modified: 9 Aug 2006 9:18
Reporter: Charlie Farrow Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Administrator Severity:S2 (Serious)
Version:1.1.9 OS:Windows (WIN XP SP 2)
Assigned to: Vladimir Kolesnikov CPU Architecture:Any
Tags: Object Editors

[27 Feb 2006 14:29] Charlie Farrow 
Description:
When using mysql admin, editing views can causes the view to be dropped when it is edited to an error status.

How to repeat:
Create a view.
Now edit the view, make an error in the view, for example, change a table name to one that does not exist.
Now click execute SQL, you will get an error.
Now close the window using the X.
Now open the view for editing..... only the view name remains in the edit window!

The view has been lost.

Suggested fix:
I wonder if Administrator executes the statement and its the server that is dropping the old statement and this is hence a server bug?

Maybe if it is performing this opperation it should try and execute the statement under a different name, if err, then no problem, if no error it should then drop the old view and rename the temp view to the old name.
[27 Feb 2006 14:30] Charlie Farrow 
Changed status, this is serious.
[27 Feb 2006 14:42] Valeriy Kravchuk 
Thank you for a problem report. It is a MySQL Administrator's problem. It simply drops the view and then tries to recreate... Should have to store the previous view definition somewhere, and recreate the original view in case of failure like those you described.
[28 Apr 2006 14:38] Willem Bastein 
same here. views get dropped when editing (another!!) view. 
(it also overwrites the selected view when adding a new one!!)
using administrator 1.1.9 on winxp pro sp2 AND on win2003 server r2.

DO NOT USE 1.1.9 since this is not the ONLY BUG with this release...
(really, it's the worst version of admin i've come across... its buggy on everything.. views, editing tables drops default values (and you can't re-set them), timestamp fields can't be set (states a wrong default value), editing users not allowed..or crashes... 
1.1.9 is a disaster!! )