MySQL Bugs: #23551: Successful command execution does not clear previous error message

Bug #23551	Successful command execution does not clear previous error message
Submitted:	23 Oct 2006 13:39	Modified:	24 Nov 2006 15:49
Reporter:	Joerg Bruehe	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S3 (Non-critical)
Version:	1.1.17	OS:	Windows (Windows 2003 (x86))
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Detected when smoke-testing 5.0.27:

The successful execution of a command does not clear the error message produced by a previous command failure.

How to repeat:
1) Start the Query Browser on some running server.

2) Issue a command, I do: "show variables like 'version%';"
   -> results are output.

3) Start the MySQL Administrator,
   stop the server.

4) Go back into QB, re-issue the command
   -> empty result window, message in status line
      "Query Execute Thread cannot connect to MySQL"
   To be expected.

5) Go back into MA, start the server again.

6) Go back into QB, re-issue the command
   -> results are output again (correct),
      but the status line still shows the error.

Suggested fix:
Clear the status line on command execution,
either immediately at the start
or on successful return.

Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/