PLD 11 - long running query makes UI unresponsive

[shunte]

This may have been reported elsewhere but I have noticed after upgrading to vers. 11 that long running queries cause PLD to stop responding and the application locks up, No Response Windows exhibit, while the query is running.

Normal behavior has been to run the query and indicate the query time in the status bar, in addition the "Break" tool bar button becomes active.

With PLD 11 the UI locks up until the query completes

I have an version 9 "parked" on my machine too and running the same query PLD acts as expected

My read is the threading model is broken for whatever causal functionality has been added.

This is a bit of a show stopper for us as we work with VLDB datasets and sadly nothing is sub-second.

I just tried the transaction indicator solution that is mentioned on the "slow response" thread and that looks to have helped although I've not threw anything horrible at PLD thus far today.

Hopefully this is the same issue and it's addressed soon

 

[Marco Kalter]

Can you go to Tools > Preferences > Oracle / Connection and let me know the "Session Mode" preference?

 

[shunte]

session mode is currently multi but with that said through the .ini file I'd set to single at one point; through the .ini I've disabled connections at start up as just starting 11 was causing it to hang; I tend to have several oft used scripts open for easy access and with 11 it was struggling. I've now also disabled auto connection in general and close all scripts as soon as I'm done.

it's changing my workflow a lot, that I can deal with that short term but may revert to 10 soon - as I said I still have a version 9 installed and that's given me breathing room on occasion.

there seem to be a couple of threads describing very similar exhibits with SQL execution (and connection)

 

[shunte]

forgot to mention that disabling "Show transaction indicator in Window List" is helping with the UI "Non Responding" when executing long running queries - the break button becomes active and the timer is displayed in the the toolbar so back to expected behavior there