Today's issue: open a package body to edit, attempt to compile it. Receive a "No more data to read from socket" error. Click "Disconnect" on the connection in the browser.This is fixed in the next release. When you learn your VPN connection is lost, reconnect it, then use the Reconnect option rather than Disconnect from your connection node.
Why are you editing something directly in the database?Using a source control management system is always a good idea. Even so, everyone wants this tool to be rock solid -- the next release should be much better.
the next release should be much better.Thanks for teasing us, Gary, but are you referring to 3.3 or hopefully some sooner released revision (perhaps 3.2.2) specifically addresssing the long-standing connection stability issues? I wouln't call sqldev buggy as hell but its behaviour in the face of a lost link has been the number one annoyance for me. I believe there have been plenty of posts about it, too. It may not affect that many users, but those with unstable connections do feel the pain. Not really oracle nor sqldev's fault, but some have to deal with poor connectivity and ideally this should be handled gracefully.
are you referring to 3.3 or hopefully some sooner released revision (perhaps 3.2.2)Standard policy here is to say only that a fix or enhancement is in the "next" release or patch. Sometimes we slip and give the number. In this case, expect the fix sooner rather than later. As always, watch for an announcement in this forum.