MySQL Bugs: #776: Double click of sql command in history tab should (re)run sql

Bug #776	Double click of sql command in history tab should (re)run sql
Submitted:	2 Jul 2003 6:48	Modified:	27 Aug 2003 19:47
Reporter:	Ronan O'Connor	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQLCC	Severity:	S4 (Feature request)
Version:	0.9.2	OS:	Linux (Redhat 9)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
In the history tab of a query window for a table, if you double click one of the commands, you should be able to run the command again. This would be especially useful for a 'select * from ...' command, which I often run directly after making changes to the database, to confirm changes.
At present a double click of a command in the history tab, writes the command to the SQL window which then requires executing. This could be better implemented as a double click. 
A single click on a command in the history tab could then cause the command to be written to the SQL window. (As currently implemented by double click).

How to repeat:
In an open Table query window, where several previous sql commands have been executed, open the history tab and double click a previously run history command.

Suggested fix:
Double click of command in History tab causes sql query to run. Single click would write the command to the Sql window.

Hi!

This is the expected behavior.  What you can do is right-click on the history panel and select the "Execute Query" option.