MySQL Bugs: #14373: Create / Edit a View / Stored Procedure

Bug #14373	Create / Edit a View / Stored Procedure - ALL text dropped on error
Submitted:	27 Oct 2005 5:34	Modified:	4 Nov 2005 15:28
Reporter:	Daniel Kasak (Candidate Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.1.4	OS:	Linux (Linux)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
If I use mysql-administrator to create or edit a view or stored procedure, and make 1 *tiny*, little typo, when I go to apply my editing, ALL changes are dropped. Instead, I should be able to continue editing.

How to repeat:
Use mysql-administrator to create / edit a view / sp.

Make a small mistake - so that a parsing error occurs. Hit apply. Everything is dropped - ie the editing window closes. If I just spent half an hour on this view, I will not be happy.

Suggested fix:
Upon a parsing error, the full text should be still available in the editing window, so the user can correct the error, and hit apply again.

Sorry, but I can't repeat the problem according to your description with Administrator 1.1.4 on Windows. I have a test table in test database, running on 5.0.15-nt server. So, I had connected, selected test database, choosen view tab and pressed Create View. Administrator asked me about a view name, I proveded one, 'v2', and it created the following template for me to edit:

CREATE OR REPLACE VIEW `test`.`v2` AS SELECT 

I changed the text to the following:

CREATE OR REPLACE VIEW `test`.`v2` AS SELECT * fro test

So, I made a small "tipo", fro instead of FROM. When I clicked Execute SQL, I've got the appropriate error message, 1064, clicked OK, and was able to repeat the editing - text I typed had neither disappeared, nor changed.

So, please, described the exact actions you performed. Do you think it is Linux-specific bug in MySQL Administrator?

It could be Linux-specific, yes. I will try from Windows 2000 when I get back to work tomorrow.

The Linux system I tested on was:

Gentoo Linux ( server and client same machine )
mysql-5.0.15
mysql-administrator-1.1.4

To produce the bug, I basically created a new view, typed in some simple SQL with a small spelling mistake, and hit the 'Execute' button. An error occurs tell me that the SQL couldn't be parsed, and when I hit OK, the window that I'd entered the view in has disappeared.

I'll try from Windows tomorrow and post back.

Hi!

Can you please give us the stored procedure that you used to reproduce this bug ?  I was also unable to repeat this bug using the information you provided.

Thanks!

OK then.

Create a table:

CREATE TABLE `test_table` (
  `ID` int(11) NOT NULL auto_increment,
  `SomeField` varchar(50) NOT NULL default '',
  PRIMARY KEY  (`ID`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1

Now use mysql-administrator to create a new view. Call the view 'vw_select_from_test_table'.

In the dialog with a text field that appears after giving the view a name, add to the text so that it reads:

CREATE OR REPLACE VIEW `test`.`vw_select_from_test_table` AS SELECT * fram test_table

Hit 'Execute'.

The following dialog appears:

Could not create view '%s.%s'.
MySQL Error Nr. 1064
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'fram test_table' at line 1

When you hit 'OK', the dialog for entering the view has disappeared. I swear. It disappears.

I've tried to repeat exactly the steps you described on Windows, and no, dialog box for editing view is here, with the text you entered. Have you tried to repeat this steps on Windows with 1.1.4? 

On Linux, maybe, your dialog box is somewhere "under" the main window. This behaviour may depend on window manager used (which one, by the way?), or may be a bug in Linux code.

Alright. Due to popular demand, I've tested under Windows with version 1.1.4 and I *cannot* reproduce the bug. Therefore I assume it is a Linux-only bug.

And yes, I know the difference between a window which is underneath something and a window which no longer exists.

OK. I'll try to repeat it on my Fedora Core.

Sorry, but I have no all the libraries needed to either build or install it right now:

[root@Fedora tmp]# rpm -i mysql-administrator-1.1.4-1.i586.rpm
error: Failed dependencies:
        libatkmm-1.6.so.1 is needed by mysql-administrator-1.1.4-1.%{targos}
        libgdkmm-2.4.so.1 is needed by mysql-administrator-1.1.4-1.%{targos}
        libglibmm-2.4.so.1 is needed by mysql-administrator-1.1.4-1.%{targos}
        libgtkmm-2.4.so.1 is needed by mysql-administrator-1.1.4-1.%{targos}
        libpangomm-1.4.so.1 is needed by mysql-administrator-1.1.4-1.%{targos}
        libsigc-2.0.so.0 is needed by mysql-administrator-1.1.4-1.%{targos}

I suppose to solve this problem in the nearest future, but in the meantime I leave this report open to somebody who will be able to check.

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html