Bug #66025 Default behavior of Ctrl + Enter now changed to execute the last query or the cu

Description:
Previously (prior to version 5.2.41), Ctrl + Enter used to execute the current statement where the cursor is, no matter the position, start/end or middle of the statement.

With 5.2.41, it either executes the last query in the editor or if the cursor is at the beginning of the query (line), then it executes that query. 

This is a sudden change in bahavior and fans like me who are used to Workbench find it confusing to adapt to the change.

Please give us an option to update the behavior for Ctrl + Enter in the 'Preferences' menu. 

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.41  revision 9727
Configuration Directory: C:\Users\Kiran\AppData\Roaming\MySQL\Workbench
Data Directory: E:\WinPrograms\WorkBench
Cairo Version: 1.8.8
OS: Microsoft Windows 7  Service Pack 1 (build 7601), 64-bit
CPU: 8x Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, 8.0 GiB RAM
Active video adapter (0): NVIDIA GeForce GT 420
Installed video RAM: 1024 MB
Current video mode: 1920 x 1080 x 4294967296 colors
Used bit depth: 32
Driver version: 8.17.12.5915
Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Active video adapter (1): LogMeIn Mirror Driver
Installed video RAM: 0 MB
Current video mode: 1920 x 1080 x 4294967296 colors
Used bit depth: 32
Driver version: 7.1.542.0
Installed display drivers: NULL
Current user language: English (United States)

How to repeat:
Write few simple querious in the query editor, say :

desc table; [cursor is here]

desc table2;

truncate table;

Hit 'Ctrl + Enter' and you will see that table is truncated instead of a description of the table being displayed! I am hoping this is a simple configuration fix. Please let us change this behavior in preferences. 

Thank you!

Thank you for the problem report.

Fixed as of the upcoming Workbench 5.2.43, and here's the changelog entry:

 On Microsoft Windows, the behavior of "Control" +
 "Enter" was changed back to the previous
 behavior, which is to execute the statement that
 contains the cursor, instead of the last statement 
 in the SQL editor, or the current statement if the 
 cursor is at the beginning. 

Thank you for the report.