Compiling an invalid packagebody without errormessage

Question

Hi,
I have just altered a package and it became invalid without any notification during compilation.
It took me quite some time to figure it out, but it seems that the number of warnings is limited. If there are too many compilation warnings, the errors get ignored.
The message log states "TEST_ERROR_MESSAGE Body Compiled (with warnings)"
If there are less warnings it states "TEST_ERROR_MESSAGE Body Compiled (with errors and warnings)".
This is a serious problem, because now I can't trust the compiler messages anymore.
I have created a small example. This packagebody can't be compiled without errors, because of the TestTabType_xxx (instead off TestTabType ). But because there are too many warning you don't see an errormessage. If you remove just one of the statements "AND substr(ename,1,2) = 'A'" the error will be shown.
I'm using SQL Developer 1.1.0.21.97
on Windows XP connected to
Oracle 10.2.0.1.0 on Linux.
I hope this will be resolved soon.
Regards Arnoud
CREATE OR REPLACE PACKAGE TEST_ERROR_MESSAGE AS
PROCEDURE test;
END TEST_ERROR_MESSAGE;
CREATE OR REPLACE PACKAGE BODY TEST_ERROR_MESSAGE AS
CURSOR c_test IS
SELECT *
FROM scott.emp
WHERE substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
TYPE TestTabType IS TABLE OF NUMBER;
TYPE TestRecType IS RECORD ( nr TestTabType_xxx );
PROCEDURE test AS
BEGIN
htp.print('Hello world!');
dbms_output.put_line('Hello world!');
END test;
END TEST_ERROR_MESSAGE;
/

Answer 1

There were 2 issues:
1. Query from ALL_ERRORS were not ordering errors first.
2. Highlight plugin (the one that does red and yellow squiggles) was issuing:
ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL'
However, this statement manifested an RDBMS bug when the errors are suppressed and only warnings are present in ALL_ERRORS view. Here is SQL script evidencing the problem (assuming that package and body already created in the schema):
ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL';
CREATE OR REPLACE PACKAGE BODY TEST_ERROR_MESSAGE AS
CURSOR c_test IS
SELECT *
FROM scott.emp
WHERE substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
AND substr(ename,1,2) = 'A'
TYPE TestTabType IS TABLE OF NUMBER;
TYPE TestRecType IS RECORD ( nr TestTabType_xxx );
PROCEDURE test AS
BEGIN
htp.print('Hello world!');
dbms_output.put_line('Hello world!');
END test;
END TEST_ERROR_MESSAGE;
SELECT LINE, POSITION, text
FROM SYS.ALL_ERRORS
WHERE NAME = 'TEST_ERROR_MESSAGE'
and text like 'PLS%';
ALTER SESSION SET succeeded.
PACKAGE BODY TEST_ERROR_MESSAGE Compiled.
LINE POSITION TEXT
0 rows selected
Some other types of errors (for example not existing emp table) are not affected by this bug.
Checked in fixes into 1.5.4 and 2.0.