“Check out… View|Options|Editor|Code Assist. Uncheck “Use inline assistance””
Quoting my original post:
In Toad Options I have “Enable parameter assistance” turned on (and Use inline assistance turned off).
“I believe in the spring. We just started the cycle.”
Too bad. This was really a handy shortcut
“What kind of statements are you executing when you see this behavior? If it’s
truly finished then we should get an end execution notification from the DB and
Toad should update accordingly. It sounds like we are not in your case. If you
have a reproducible case, run SQL Tracker (in same path as Toad.exe) and monitor
Toad. Reproduce your scenario and see if there is a query that is hanging. It’s
possible that your Toad options require some post-execution queries to be run
that may be problematic.”
I can’t reproduce really, since the statements that cause this vary. If I remember correctly it involved in some memory error or access violation error that toad popped up and then the tab got stuck. Other tabs in the same editor were still working, only the specific tab didn’t respond. I’ve encountered it about a dozen times already. This happened also in 10.6.1, so it’s not something that was introduced only in this new release.
“In the past it has been brought up many times that query cancellation can be
slow. We send a cancel request and await the DB’s response. As far as I know the
delay is due to the DB or the client DLL taking a long time to process the
request, but my knowledge of the OCI and DB in this area is pretty shallow so
that’s just a guess.”
I don’t think it’s actually trying to cancel the query execution or do anything related to the DB. My guess that it’s something more generic than that. If I remember correctly - the statements did finish on the DB side on all occasions- it’s not like I had a long running query that i’m trying to stop…
The next time it happens i’ll try to attach some screenshots.