3.1EA2 bug still not fixed - Members of package body not listed in the tree

Question

Hi, I was working today with SQL Developer again and found that this bug is still not fixed even when it was reported more than 1 year ago!!!
I did a quick search and found it here
Package Body Tree not always showing
The problem is when you expand the package specification or package body tree, not all members of the specification/body are listed. This is mostly observable in the package body, but it regards to the specification as well.
Consider this case:
CREATE TABLE EMP (
    ID               NUMBER(6,0) DEFAULT 0,
    NAME             VARCHAR2(20 BYTE) DEFAULT NULL,
    DEPT             VARCHAR2(20 BYTE) DEFAULT NULL,
    FUNCTION         VARCHAR2(20 BYTE),
    PROCEDURE        VARCHAR2(20 BYTE));
CREATE TABLE LOOP (
  AREA    VARCHAR2(5),
  VALUE   VARCHAR2(2));
CREATE OR REPLACE PACKAGE Test_Package1 AS
gvc_const CONSTANT VARCHAR2(10) := 'xxx';
PROCEDURE Test(p_RC OUT NUMBER,
               p_ID IN NUMBER);
END Test_Package1;
CREATE OR REPLACE PACKAGE BODY Test_Package1 AS
PROCEDURE Test(p_RC OUT NUMBER,
               p_ID IN NUMBER)
IS
BEGIN
  --INSERT INTO EMP (ID, NAME, DEPT, PROCEDURE) VALUES (1, 'Tina', 'xxx', 'xxx');
  --INSERT INTO EMP (ID, NAME, DEPT, FUNCTION) VALUES (2, 'Jeff', 'xxx', 'xxx');
  --INSERT INTO LOOP(AREA, VALUE) VALUES('a','b');
  NULL;
END;
END Test_Package1;Compile the package specification and the body. Expand the spec + body in the tree. Uncomment any of the commented lines in the package body and compile the body again. Now expand the package body again and look what is displayed.
Why? It is because SQL Developer handles words "Function", "Procedure" and "Loop" as keywords and according to them does the parsing.
Another case
CREATE OR REPLACE PACKAGE Test_Package1 AS
gvc_const CONSTANT VARCHAR2(10) := 'xxx';
TYPE Loop_rec IS RECORD(
  item1   LOOP.AREA%TYPE);
PROCEDURE Test(p_RC OUT NUMBER,
               p_ID IN NUMBER);
END Test_Package1;Compile just this specification and try to expand it in the tree. Again, during parsing the package, SQL Developer takes the word "LOOP" into consideration and fails to parse the specification.
There is exactly the same problem when you declare functions from external dll libraries in package body. Since there is no "END;" in this case, SQL Developer's parser fails...
To me it seems you simply blindly took some keywords like "FUNCTION" and expect there will be some "END;" keyword corresponding with it.
Can anyone have a look at this and finally fix it?

Answer 1

Hi,
Thanks for trying out SQL Developer 3.1 EA2 and providing a clear, reproducible test case for this issue. I logged an internal bug for it:
Bug 13438696 - 3.1EA2: FORUM: CERTAIN KEYWORDS IN PKG BODY BLOCK MEMBERS FROM CONN VIEW TREE
It seems the bug noted in the other forum thread you reference has been fixed, but really had nothing to do with problems discussed either here or there. That fix involved adding an Edit Body... item to the Package context menu in the Schema Browser, not displaying Package members correctly in the Connection view tree.
Regards,
Gary
SQL Developer Team