3 Replies Latest reply on May 13, 2015 4:48 PM by Vadim Tropashko-Oracle

    4.1EA2: no formatting of pl/sql file type

    906783
    906783 Mar 26, 2015 2:06 PM

      I have a ".pck" file type declared as File Type PL/SQL in Tools > Preferences > File Types.

      In 4.1EA2, when I open a ".pck" file, it no longer has any coloured formatting, just black and white text.

       

      ".pks" or ".pkb" files aer formatted fine.

      • 642 Views
      • Tags:
        • 1. Re: 4.1EA2: no formatting of pl/sql file type
          Vadim Tropashko-Oracle
          Vadim Tropashko-Oracle Mar 27, 2015 10:47 PM (in response to 906783)

          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);

          end;

          /

           

          would be recognized (no matter what extension file had), while

           

          CREATE OR REPLACE package ...

          ---------------------------------^^^^^^^^

           

          won't be. This is fixed, of course, for RC1.

          1 person found this helpful
          • 2. Re: 4.1EA2: no formatting of pl/sql file type
            906783
            906783 May 13, 2015 9:08 AM (in response to Vadim Tropashko-Oracle)

            Version 4.1.0.19.07

             

            Bug still there

             

            .pck file, opening line is

             

            /*

            $Log:   ...............

            */

             

            Not formatted as per pl/sql file.

            No coloured keywords.

            • 3. Re: 4.1EA2: no formatting of pl/sql file type
              Vadim Tropashko-Oracle
              Vadim Tropashko-Oracle May 13, 2015 4:48 PM (in response to 906783)

              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?