Bug #22275 mySQL Administrator View Overwrite Error
Submitted: 12 Sep 2006 16:26 Modified: 23 Oct 2006 9:10
Reporter: Andrew Woods Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.1.9 OS:Windows (Windows XP Pro)
Assigned to: CPU Architecture:Any
Tags: mysql administrator, overwrite, VIEW

[12 Sep 2006 16:26] Andrew Woods
Description:
When I add new views using the mySQL Administrator window it has overwritten other saved queries.  This is an intermittent problem but has happened consistently over the past week or so.

I copied the select statement from one view and pasted it into my 'New' view window, amended the content and then saved the new view.  This was the first time that I noticed the problem so could possibly be the cause.  There was no reference to the old query, just the select statement.

I have also added a couple of views that didn't show in the view window.  When I looked into it I found that the content of several queries had been overwritten with this new text!

I have created more views withouth copying any text etc but the problem persists!

How to repeat:
Create and save a new view in mySQL Administrator
Copy the select statement and create a new view
Paste the copied text and amend appropriately (change table/filed names etc)
Save the new view.

Now create and save more views and they should be overwriting one another.

Suggested fix:
?
[12 Sep 2006 18:53] Sveta Smirnova
Thank you for the report.

I can not repeat it using current 1.2.3 rc version accessible from http://dev.mysql.com/downloads/gui-tools/5.0.html. Please, try using current version and if you will repeat the problem, provide accurate CREATE VIEW statements you use.
[12 Oct 2006 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".
[23 Oct 2006 9:10] Sveta Smirnova
Duplicate of Bug #23523