MySQL Bugs: #67766: No Error Reported for Invalid Queries

Bug #67766	No Error Reported for Invalid Queries
Submitted:	30 Nov 2012 14:43	Modified:	28 Jan 2013 13:16
Reporter:	Mike Tonks	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5240 rev 8790	OS:	Linux (Ubuntu Quantal 12.10)
Assigned to:		CPU Architecture:	Any

Description:
When executing an invalid query - e.g. with a syntax error, invalid table or field name, anything that results in an error, no feedback or error message is visible.

I would expect to see the error returned somewhere, as you get in a terminal or the old query browser.

How to repeat:
When I run a valid query, it works fine, e.g.:

select * from users;

At the bottom of the window in what I would call the 'Status Bar' it says 'Executing Query...' for a few seconds while the query runs, and then changes to 'Query Completed' and displays the results.

So far so good.

If I then change the query to something invalid, e.g. :

select * from invalid_table;

The status bar says 'Executing Query...' and stays that way. I cannot see the error message reported anywhere.

If I run the same query in a terminal I get:

mysql> select * from invalid_table;
ERROR 1146 (42S02): Table 'mydb.invalid_table' doesn't exist

Similarly, anything invalid e.g.:

select xxxx;

select where;

gives the same result - i.e. no feedback.

In the terminal:

mysql> select xxx;
ERROR 1054 (42S22): Unknown column 'xxx' in 'field list'

mysql> select where;
ERROR 1064 (42000): 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 'where' at line 1

Suggested fix:
Display error message somewhere - in the status bar and detailed error in the results area for example.

Please try version 5.2.44. Thanks.

This problem also presents on Mac OSX 10.7.5 with Workbench Version 5244 rev 9933.

I installed 5.2.44 and there is a slight improvement.  The status bar now says 'Query Interrupted' for failed queries.

This is better but does still not give me the actual error message.

I noticed the following error since I am now running workbench from a console:

(mysql-workbench-bin:11393): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

I don't know if this is related, but maybe it will give someone a clue?

Error showed

Attachment: bug_67766.png (image/png, text), 218.19 KiB.

The error isn't showed in the status bar, please see prior attached picture at the bottom red marked part. Tested on CentOS 6.3.

Miguel, I will try this on Windows when I get back next week. For me this problem happens as I said on Mac OSx with the release stated.

Thankyou Miguel for the screenshot, that has really helped.

After some clicking and dragging around to try and get the 'Action Oputput' (or whatever you call that bottom panel) to appear, I managed it.

I think this is not visible and minimised by default, which means that clicking the buttons at the top does nothing (or virtually nothing unless you have very good vision and know what you're looking for).  Additionally those buttons at the top have no tool tip or anything to indicate what they do.

So maybe it's an issue with the installer / usability issue, or just down to user error.  I can now see the error message, thankyou.

I will uninstall tomorrow and go back to try the ubuntu packaged version to see if the same thing works.

Please try version 5.2.45. Thanks.

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".