Keep sessions alive by tranparently executing a "select 1 from dual"? - 12/03/19 09:45 AM
I frequently use pl/sql developer to connect to remote databases and often my customer's database/network administrator have put some rule in place for which inactive sessions get terminated.
I know there is already the "check connections" option, but this doesn't seem to be executed periodically (say once every minute): the connection is checked only when I interact with it. This means that every time I move to a sql window whose connection has been closed, I have to wait up to 30-40 seconds for the connection to be re-connected.
This wouldn't happen if pl/sql developer was keeping alive dormient connections by executing periodically a "select x from dual". Could you please add this feature, thanks.
By the way: the above problem gets very annoying when all you want to do is to close PL/SQL developer but you have say 10-20 sql windows open in its session and most of them have been disconnected. In this situation pl/sql developer will try to reconnect every session one at a time, just to ask you if you want to save what you were doing... and it takes 30-40 seconds for each window (because it does it sequentially: it does not try to reconnect them all all at once).
Actually, for me, it is almost impossible to close pl/sql developer in a clean way under these circumstances: I really have to brutally
terminate the process because I can't wait 10 minutes just to have pl/sql developer reconnect all its sessins before closing it...
(As a side note: it would be nice if all the dictionary lookup operations done while editing were done asynchronously by a background process, without having the user interface freeze until the dictionary queries are completed.)
I know there is already the "check connections" option, but this doesn't seem to be executed periodically (say once every minute): the connection is checked only when I interact with it. This means that every time I move to a sql window whose connection has been closed, I have to wait up to 30-40 seconds for the connection to be re-connected.
This wouldn't happen if pl/sql developer was keeping alive dormient connections by executing periodically a "select x from dual". Could you please add this feature, thanks.
By the way: the above problem gets very annoying when all you want to do is to close PL/SQL developer but you have say 10-20 sql windows open in its session and most of them have been disconnected. In this situation pl/sql developer will try to reconnect every session one at a time, just to ask you if you want to save what you were doing... and it takes 30-40 seconds for each window (because it does it sequentially: it does not try to reconnect them all all at once).
Actually, for me, it is almost impossible to close pl/sql developer in a clean way under these circumstances: I really have to brutally
terminate the process because I can't wait 10 minutes just to have pl/sql developer reconnect all its sessins before closing it...
(As a side note: it would be nice if all the dictionary lookup operations done while editing were done asynchronously by a background process, without having the user interface freeze until the dictionary queries are completed.)