I've discovered a bug in the command window.
I noticed that if your session gets disconnected while idle (examples include: kill session or temporary network disconnect), PL/SQL Developer will not inform you of the disconnect, it will simply reconnect a new session and continue without letting you ever know.
This means that if you are disconnected while running a multiple part transaction, the first part is rolled back and the user is not informed.
Example :
Update/Select/Insert/**disconnect**/Update/Delete/ then Commit;
Everything before the disconnect is lost.
I noticed that if your session gets disconnected while idle (examples include: kill session or temporary network disconnect), PL/SQL Developer will not inform you of the disconnect, it will simply reconnect a new session and continue without letting you ever know.
This means that if you are disconnected while running a multiple part transaction, the first part is rolled back and the user is not informed.
Example :
Update/Select/Insert/**disconnect**/Update/Delete/ then Commit;
Everything before the disconnect is lost.
