MySQL Bugs: #7526: Executing empty query doesn't show error window in all cases

Bug #7526	Executing empty query doesn't show error window in all cases
Submitted:	24 Dec 2004 13:12	Modified:	15 Feb 2005 10:48
Reporter:	Thomas CORBIERE	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.4	OS:	Windows (Windows XP)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When you launch Query Browser, and after connecting to a server, if you click on the Execute button you'll get this error message : "No SQL Command. You tried to execute an empty string. Please type an SQL command into the SQL edit field and execute again".
But if you have executed a non-empty query before executing an empty one, then it will ignore the empty query and re-execute the previous query.
While this may be the expected behaviour for the refresh button, Execute button should report an error in this case.

How to repeat:
Execute a valid query, hit Ctrl+N to empty the query field and finally hit the Execute button

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