SQL Window multi-tab queries bug

[Kirurgs]

I'm facing a multi-tab query bug...
I select 2 statements, execute them, first query finishes fast, next tab appeears and second query is executing, but it takes longer to execute.
While second is executing, I swith to first tab and look at selected data, when first row arrives in second tab, developer automatically switch to second tab. Then I manually swith back to first tab and I see in every field in first tab.

 

[Kirurgs]

Uff, sorry, forgot to enter version: 7.0.0.1050

 

[Kirurgs]

Yea, and one bug more, when select 2 statements and execute - 2 tabs appear, queries finish.
If after that I click on one of highlited statements and execute it alone, it's still highlighted.
If you execute existing statement in that SQL Window, that first one is still highlighted, but if you modify contents of this window, highlight disapear.
If this helps: statements ends with ; and autoselect feature is turned on.

 

[Marco Kalter]

We'll fix it.

 

[William Robertson]

And another thing: there is no right-click menu in the results panel unless some SQL statement returned results. So if you have CREATE TABLE etc statements, you can't clear the results panel unless you SELECT * FROM dual;

 

[Marco Kalter]

We'll fix that too.

 

[ScottMattes]

I can't find where to set the color used to denote the query that goes with the currently selected tab.

 

[Marco van der Linden]

@ScottMattes
It's the hot track highlighting of the program window preferences

 

[ScottMattes]

Marco van,
Thank you, I'd of never found a SQL Window option in the Program Window section

 

[vlevi]

One another question to multi-tab queries: How can I turn it off? I use SQL Developer frequently on dial-up connections, where it is very slow to execute all statements again. An I think it is useless on local databases, too.

 

[jasonvogel]

Just highlight the statement and you get the previous behavior.

 

[ScottMattes]

But, the previous behavior was to hit F8 and the statement your cursor was on was executed. Hiliting the statement first is more work, sometime much more (some of the queries that I test in PLSD from our project are very big).