If you are running a query in TOAD for MySQL and you press "Stop Processes" button or "Cancel Executing Query" sometimes TOAD fails to stop the query: If you are running a SELECT query is properly stopped and you remain in current session. So the behavior of TOAD is similar of that "KILL QUERY processlist_id". But if you are running a INSERT INTO ... SELECT command for example, instead of stopping the query: TOAD opens a new session (Loosing all the temporary tables we had in such session). And continues executing in the backside the INSERT INTO ... SELECT statement, blocking the used tables. The second behavior forces us to: Re-execute Temporary Table Scripts. And use a "KILL CONNECTION processlist_id" for being able to stop the query. So "Cancel Executing Query" does not always have a good performance. Some sort of Option for having control over these behaviour would be appreciated. Thank you.
↧