This content has been marked as final. Show 9 replies
It does take a long time until the cancel kicks in, sometimes it plain doesn't 'till the query returns.
The developers are aware of this and promised to improve this in v2.0 (scheduled later this year).
Good news that this will be improved. Can't resist to post this Link: [plsql forum thread about start/stop.. | http://forums.oracle.com/forums/thread.jspa?forumID=75&threadID=927697]
I have experienced the same and also noted that it feels better to execute stored procedures in sqldeveloper
- by editing
- compiling (might hang if already busy)
- run from the same dialog just to get the the cylon's eye for emergency stops (which waits .... ) meanwhile jump to apex to fiddle with small table triggering exception to stop the procedure.
If stored procedure is executed from the list via 'right mouse click'-style then you see in the log-region "connecting to databse ... ." but no method to stop nor cancel or cylon's eye is well hidden.
When such "busy" is running I also noted that the database-connection right mouse click has greyed/inactivated the selections "connect/disconnect" so the next logical step for stopping via "disconnect" is out of the question.
I think this also boils down also to question whether the user has rights to see gv$session and be able to drop/stop busy/jamming sessions. E.g. public synonyms listing has small icons with mystic red :)
Java(TM) Platform 1.6.0_14
Oracle IDE 184.108.40.206.40
Now that we're here, another one that bothers me is getting all results in the Result grids (CTRL-END), which even locks up redrawing.
That issue has been brought out many a times. We are tackling it in 2.x.
Are you referring to the OP or the CTRL-END behaviour (or both, I hope)?
Both - Original Post on Cancel not canceling immediately & crtl-end.
Great! Both can make you lose a lot of time, so the ability to cancel is highly appreciated.
What ever happened to this being improved in 2.x? I'm using 3.2.09, and queries still don't cancel properly. I can't run any more queries, and when I try to disconnect or even exit SQL Developer completely, it says the connection is busy with options "Try Again" and "Abort" when I really need a third option "Force Disconnect".
jarnold wrote:You are aware of the unshared worksheet feature? Ctrl-shift-N when you are in a worksheet will open a new worksheet with a separate connection. You can carry on working on that.
What ever happened to this being improved in 2.x? I'm using 3.2.09, and queries still don't cancel properly. I can't run any more queries,
As to cancelling, the last time one of the team posted about this it was said that they simply send a cancel to the database and the rest is up to the database so it is out of their hands.