Return
-
Title
Script output not bound to editor tab and only shows the last result -
Description
The "Data grids" output IS bound to the editor tab which is generating the result.
The "Script output" is NOT bound to the editor tab, it only shows the last result.
With this behaviour it's not possible to compare autotrace- outputs.The "Script output" should also (like the "Data grids" output) be bound to the editor tab, meaning every editor tab should have its own "Script output" tab. -
Resolution
WORKAROUND:
None
STATUS:
This has always been the case and is by design.
Both the script output tab and the PL/SQL debugger have a 1-many relationship with editor tabs.
The debugger works on multiple scripts/objects and can spawn additional editor tabs during debugging, so they need to have the 1-many relationship."
-
Additional Information
1. open an editor and paste following statement into the tab:
select level from dual connect by level < 10
2. press F5 to execute the statement as a script.
3. make sure the output is shown permanently.
4. press F9 to execute the statement again ans see the result in the data grid.5. open an new tab in the same editor
6. paste following statement into it
select level from dual connect by level < 157. press F5 to execute the statement as a script.
8. see it's output
9. press F9 to execute the statement again ans see the result in the data grid.10. switch to the first tab and see the data grid:
DataGrid shows results of last statement in this tab11. switch to the "Script Output" in this tab
"Script Output" shows the result from the other tabThis behavior prevents the possibility of comparing autotrace- outputs.