MySQL Bugs: #50747: Hotkey for executing a single query

Bug #50747	Hotkey for executing a single query
Submitted:	29 Jan 2010 19:13	Modified:	8 Feb 2010 14:24
Reporter:	Daniel Katz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S4 (Feature request)
Version:	5.0.15 OSS BETA	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	hotkey

Description:
The new version has lost the ability to _easily_ execute single queries in order with hotkeys.

In your active window, you can't selectively execute one at a time without highlighting the subsection in question.

Ctrl-enter used to do this.  

How to repeat:
In essence, having 
Query A;
Query B;
Query C;
Query D;
Query E;
Query F;

In your active window, you can't selectively execute one at a time without highlighting the subsection in question.

Ctrl-enter used to do this.  

Suggested fix:
* Please make a hotkey for doing this (ctrl-shift-enter?) 
-- or better --
* Bring back the old hotkey support for single queries and make ctrl-shift-enter, which makes sense (shift = set selection), execute all queries in the open tab.

we decided not to change the current setting, but added Ctrl+Shift+Enter as shortcut for "execute current statement".
will be included in 5.2.16

I'm happy that the feature is making it into the next release however -- 

Can I make one last effort to present a case for changing the two options 
(ctrl-shift-enter vs ctrl-enter)?

1: It's the way it used to be.
Ctrl-enter used to execute a single query.  Also, it's the way that MS (I know...) SQL server does it.  So existing users of the query tool feel at home, converts will also feel at home.

2: More keys for more dangerous applications.
In the many different environments and developers, I've noticed that they like to stack queries as they work through a problem.  If they're writing queries that have deletes / updates / etc in them and accidentally hit ctrl-enter instead of ctrl-shift-enter they would be making multiple successive changes to the database.  (I guess with transactions, they could roll them back, however this is not always the case.)

Similarly, considering this is potentially harmful, I'd even say there should be a popup warning with a singleton remove ("Warning - you are about to execute multiple queries ... [X] Don't show this again")

3: Shift is a known (to windows users at least) set operator
This is just to add fodder to the fire, but control-X is a known event handler, and shift is often used to do multiple things (or alternate actions).

Like selecting files!

Please consider this.  because it is a departure from the existing way things are being done and it could be the bain of fat-fingered developers everywhere.

After discussion with Tax it appears it will be changed to be as indicated in the change entry below.

A 'change' entry has been added to the 5.2.16 changelog:

In the SQL editor, the keyboard shortcut to run a single query has been changed to Ctrl + Enter. To run all queries the keyboard shortcut has been changed to Ctrl + Shift + Enter.

I does not work on Windows 7 32 bit.

I'm using version 5.2.16 and I have to hit ctrl+shift+Enter to run the SQL that my cursor is currently positioned on, ctrl+enter runs the first statement in the editor.

Also, after hitting "Ctrl"+"Shift"+"Enter" the focus moves from the editor windows to the resultset window which is very unwanted behavior as most of the times I would like to continue editing the SQL after hitting the "Execute Current SQL Statement..." button / keyboard shortcut.

Thank you for the good work,
Maxim.