Quantcast
Channel: Toad for MySQL
Viewing all articles
Browse latest Browse all 1315

Forum Post: Toad Beta 7.x bug: Execute current statement (F9) does not work as expected

$
0
0
In Toad 6.0.x if you positioned the cursor at the end of a statement immediately following the semi-colon and then selected the "Execute Current Statement" or pressed the F9 key, Toad, as expected, would execute that statement and only that statement. In the most recent download of Toad Beta (7.0.0.2040) if I position the cursor after the final semicolon, and then select "Execute Current Statement" (or F9) , Toad 7 quite unexpectedly executes the NEXT STATEMENT instead of the current statement, even though that statement may be on another line or separated by several blank lines.  "Execute Current Statement" now only works if the cursor is positioned BEFORE the semicolon in a statement. This is a really sneaky useability change because I was used to typing a statement including a semicolon then finishing off with the F9 key.  NOT GOOD!  I totally destroyed a database a couple of nights ago when Toad executed the statement following the one I was working on. PLEASE FIX! EXAMPLE: In the following statements try positioning the cursor before and after the final semi colons and see what happens: show variables like 'log%'; select now(); show variables like '%memory%'; select hour(now()); - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Toad Beta (7.0.0.2040) installed on a clean system, no other instances of Toad present. Windows 7 Professional 64-Bit , SP1;  Intel(R) Core(TM)2 Duo CPU  P8700 @ 2.53 GHz ;  4.00 GB RAM

Viewing all articles
Browse latest Browse all 1315

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>