No error in SQL window

Daniele

Member³
Hi,
when I run a script (or a package body) in the SQL window if there are errors these are not shown.
I have to run the script from the command window and write "show err" if they want to see them.
Since the command window is quite slow in the execution of scripts (especially if they are long enough), there is a way to display errors from the SQL window?

Thanks
 
The SQL Window will not display compilation errors from the sys.user_errors view. You should preferably use the Program Window for this. It displays the errors and allows you to quickly navigate to the error location in the editor.
 
Yes, it is true, but in the program window I can not enter the / at the end of the script.
In addition in the program window I can't see the results of the select so I'm forced to change window for each type of execution.
Would not it be convenient to have a single window to perform all the operations?
And maybe to put the / without unnecessary errors?
 
The Program Window will implicitly add a terminating / to the program units to make it compatible with other tools like SQL*Plus.
 
Yes it's right,
but many times I have to copy and paste text (script) from external file and every time I have to delete the / if I don't want to have errors.
You can not create an option that do not display the errors for this type of character?
When I save a file the / is placed in automatic at the end of file, when I open the same file it is deleted (made implicit) in automatic.
It 'so strange to leave him visible?
 
Last edited:
Back
Top