Oracle SQL Developer: New window, new session. Bad behavior?

Yay, it’s there. SQL Developer 4 is usable. It brings a new session for a new window (“unshared worksheet” in Oracle terms) – I was told lately SQL Developer 3 already had this. Did you know? Now we are kind of stable in 4: The 4.0.2 build 1521 (hehe) works good, so it’s time to see how “Unshared Worksheet” works here. That’s what we alwas had – one sheet, one session:

That's what we alwas had: One sheet, one session

 

Now let’s open a new sheet…

SDEV2_new-ws

… and we still have one session:

SDEV3_two-tabs

Version 4 allows to change this behavior – enable “New worksheet to use unshared connection”:

SDEV4_pref

Now we have two tabs, and two sessions:

SDEV5_two-sess

But when we close this second tab, we still have a session:

SDEV6_one-sess-closed

Open a third tab (second is closed), now we have a third session:

SDEV7_three-sess

When we disconnect and connect …

SDEV8_disconSDEV8_con

… we don’t change anything with the two “abandoned” sessions, but the tab being opened first is re-connected (has a new SID):

SDEV9_open-close

But if we cleanly restart the SQL Developer, we only have one, clean session:

SDEV10_reconnect

Not bad, but still not perfect.

Take care
Martin Klier




You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Leave a Reply