1 person found this helpful
There was a trivial case sensitivity bug that prevented parser from recognizing pl/sql source. For example,
CREATE OR REPLACE PACKAGE TEST_PACK as
procedure test (
p_arg1 in varchar2 default 'AbcD',
p_arg2 in number default null);
would be recognized (no matter what extension file had), while
CREATE OR REPLACE package ...
won't be. This is fixed, of course, for RC1.
Bug still there
.pck file, opening line is
Not formatted as per pl/sql file.
No coloured keywords.
SQL & PL/SQL source recognition works the following way:
1. If file extension is listed, then file is opened with associated editor. However this is broken in 4.1 (fix scheduled for 4.1.1 patch).
2. The first 5000 characters of the file content are scanned, and parsed. If the first several words are recognized as legitimate PL/SQL then the file is opened with PL/SQL editor. As this doesn't work in your case, how big is the comment? Is it longer than 50 lines? If the comment is short, can you please post the beginning of your file up to the line "create or replace package X" so that I can check where recognition failed?