problem with auto select/execute statement

[hbar]

I have auto execute disabled, and auto select enabled, using version 7.1.1.1339.

I typically end task to close plsd, in order to take advantage of the recovery capabilities. I'm sure there is a better way to do this, but old habits die hard. Whenever I do recover, the recovered SQL windows don't obey my auto execute preference. What's more is that it doesn't auto execute right either. Witness:

select *
from dual;

select sysdate
from dual;

If that were in a recovered window, attempting to execute the first query via auto select statement (placing the cursor in the query and hitting F8) results in 2 tabs. The first is the result of the first query. The second tab (and all subsequent tabs) shows a missing expression error, like plsd isn't seeing the next query correctly. Of course, since I have auto execute disabled, it shouldn't even look at the 2nd query.

If I copy/paste into a new SQL window, everything seems to work fine.

 

[Marco van der Linden]

"I typically end task to close plsd, in order to take advantage of the recovery capabilities".

Hbar, you might want to consider using the 'desktop' command line option for this. This will even allow you to have different windows opened automatically for different db instances (you _do_ have to create seperate shortcuts for that however).

 

[hbar]

Like I said, old habits die hard. I definitely need to check out some of the "newer" features.

 

[hbar]

I've just discovered the problem also occurs with previously saved SQL files I reopen. This is mildly frustrating.

 

[Marco Kalter]

I cannot reproduce this. Can you go to Help > Support Info, press the 'Copy all pages' button on this info screen, and paste this text into an e-mail reply?

 

[hbar]

You've got (e)mail.

 

[Marco Kalter]

Thanks, we'll check it out.

 

[hbar]

I just installed 7.1.2.1362, but the problem remains. Just so we're clear, I included some pretty pictures.

Step 1: I have recovered my PL/SQL Developer instance, and have auto select enabled and auto execute disabled.

Step 2: I have manually selected one of the queries to demonstrate that there are no issues with the query.

Step 3: The query returned successfully.

Step 4: I have placed the cursor within the 2nd query, and hit F8 to execute. With AutoSelect on and AutoExecute off, the results should be identical to those of step 3. You'll note that the "ECT *" from the 3rd query is hot-track highlighted and shows an error tab, suggesting that AutoExecute is enabled. Also, the 2nd query has an error tab, suggesting that AutoSelect isn't working properly.

Let me know what else I can provide to help get this problem fixed.

 

[Marco Kalter]

Hmm, can you send me the script?

 

[hbar]

I sent an email to support. Here's another nugget that might help you solve the riddle. I just loaded a saved SQL file. The file had an anonymous block, closed off with a slash, and then below it was a simple query. I attempted to autoselect the block, which worked, but the query below the block successfully autoexecuted. This is odd when you consider I have autoexecute disabled.

 

[hbar]

Well, I'm on to version 7.1.3.1381, and it looks like my problem is finally fixed!! I was sad when I didn't see it addressed in the release notes...imagine my joy when I discovered that everything works as advertised again.

Thanks.