Program Window - enhancement request

[Aviga]

Hello,

Would this be possible to ignore "prompt" and "show errors" (or "show") SQL*Plus commands in the context of Program Windows?

Indeed, in my company, coding standards require that every code object creation/replacement is preceeded by "prompt" lines and followed by a "show errors".

The problem is that every time we compile an object (function, procedure, package spec., package body, trigger), we get at least one error : a syntax error on the "show errors" line.

Furthermore, since "show errors" is displayed as a separate tab, this second tab is selected and we have to go back to the first tab.

In the context of a project, compiling several files results in errors in every file, which is not very meaningful.

Let me know what you think.

Thanks in advance.

Best regards,

Avigael

 

[Marco Kalter]

This is already possible. Just go to Tools > Preferences > Program Window and select the "Ignore unrecognized PL/SQL" option. As a result, SQL*Plus commands like "show errors" are ignored, but also non-PL/SQL commands like "grant", "create synonym", and so on.

 

[Aviga]

Hi Marco,

Thanks. I tried this setting.

Actually, it seems that these commands are ignored if they are located in the first tabbed window, but not in the second.

Tab 1:
-----

prompt Compiling package

create or replace package
...
end ;

Tab 2:
-----

show errors package

---------------------

The two tabs are separated by an invisible "/".

Is there another way?

Thanks.

Best regards,

Avigael Levy

 

[Marco Kalter]

This should not cause any errors though.

 

[Aviga]

Hi,

A simple test case. I created a file containing the following lines:

prompt creating PROCEDURE test

CREATE OR REPLACE PROCEDURE test
AS
BEGIN
NULL;
END test;
/

show errors PROCEDURE test

1) I saved/closed it and reopened/executed it using Command window.

No problem, this displayed these messages in the Dialog tab:

creating PROCEDURE test
Procedure created
No errors for PROCEDURE .TEST

2) I closed the Command window and reopened the procedure file using Program window.

I got an invalid SQL statement error (ORA-00900) and the cursor was positioned at the beginning of the second tab ("show errors" line).

Thanks again.

Regards

Avigael

 

[Marco Kalter]

Hmm, this seems to be a bug. We'll fix it.