Enhancement: Don't clear SQL result set after an error

[juanian]

I have a tendency to work with some very large tables, and the joins can be painfully slow. I occasionally get the "snapshot too old" Oracle error (after slowly getting a few thousand rows returned). That is a problem I have to deal with based on the tables I am working with.

What is painful is that PL/SQL Developer clears the SQL window result set frame after I dismiss the error message dialog box. I can see how many rows were returned so far (in the status bar), but all of that work is tossed away.

My question is: Why? Can't PL/SQL Developer leave the already retrieved rows in the result set frame? Why does it clear the frame?!?

So, a suggested enhancement is this: IF rows have been returned, don't clear the frame after an Oracle error has occurred.

Has anyone else run into this? (At work here, I get nods from others who have had returned rows suffer the same fate as mine.)

Thanks
Juan

 

[Marco Kalter]

I'm not sure why this happens, but we'll check it out and will try to enhance this. I don't see any immediate reasons why the records that are already fetched should be cleared.

 

[BWendling]

Hi,

I had a similar experience shortly: After launching a query over night, on the next morning, I could see the first 100 rows (which would have given me a good indication), but when I clicked on the window, I got "not connected to Oracle" error and the so far retrieved results were gone.

 

[juanian]

Does anyone know if this was fixed in 7.1.5? (It is not listed as one of the enhancements for 7.1.5, so I'm assuming it was not.) I'm currently using a stable version of 7.1.4.1390, and I'd rather wait until an update fixes/has something I'd like before I upgrade.