This discussion is archived
3 Replies Latest reply: Aug 5, 2013 1:12 PM by Vadim Tropashko RSS

R4 EA - Run packaged procedure - loss of utility

Vin Steele Newbie
Currently Being Moderated

I am running SQL Developer R4 EA 64 bit.

 

The  "Run" function (from either the right-click menu or the green icon in the top of the code editor) for standalone procedures has been enhanced to be aware and use default values, a great improvement!

 

However, the "Run" function for packages now generates the popup window, but does not generate the PLSQL anonymous block to execute procedures and functions within the package.

 

Also, it would be nice if the schema name was automatically generated in the PLSQL block, for both standalone and packaged procedures and functions.

  • 1. Re: R4 EA - Run packaged procedure - loss of utility
    Vadim Tropashko Pro
    Currently Being Moderated

    There were fixes coming after EA1. However, to doublecheck, can you please post an example of package that fails to start?

  • 2. Re: R4 EA - Run packaged procedure - loss of utility
    Vin Steele Newbie
    Currently Being Moderated

    The popup box appears. There are 3 windows in that box: 'Target', 'Parameters', and 'PL/SQL Block'. The first two windows are populated, the third is not. I can select different procedures, and the parameters window contents change accordingly. The 'PLSQL Block' window remains empty. I can shift focus to that window, and type in it. It is simply not prepopulated. Here is a sample package specification.

     

    create or replace PACKAGE         "PKG_EXTRACT_DIM" AUTHID DEFINER

    AS

    en_assertfail constant NUMBER := -20999;

    exc_assertfail exception;

    pragma exception_init (exc_assertfail,-20999);

    exc_unique_constraint exception;

    pragma exception_init (exc_unique_constraint,-00001);

    en_captured_error constant NUMBER := -20005;

    exc_captured_error exception;

    pragma exception_init (exc_captured_error,-20005);

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

    /* The following code, bounded by the $IF and $END

    statements, is an example of conditional compilation. Under

    normal (default) conditions, the 3 "assert" procedures are private

    methods, are not exposed in the package signature, and CANNOT be invoked

    by themselves. However, if the command:

    "alter session set plsql_ccflags = 'yesmail_debug:true';"

    is issued prior to compilation, they become exposed. This is done

    in order to conditionally expose them for testing.

    */

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

    $IF $$yesmail_debug $THEN

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

        PROCEDURE assert(

            pi_condition IN BOOLEAN,

            pi_msg IN VARCHAR2 DEFAULT NULL,

            pi_module IN VARCHAR2 DEFAULT NULL

        );   

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

        PROCEDURE assert_precondition(

            pi_condition IN BOOLEAN,

            pi_msg IN VARCHAR2 DEFAULT NULL,

            pi_module IN VARCHAR2 DEFAULT NULL

        );   

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

        PROCEDURE assert_postcondition(

            pi_condition IN BOOLEAN,

            pi_msg IN VARCHAR2 DEFAULT NULL,

            pi_module IN VARCHAR2 DEFAULT NULL

        );

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

    $END

    PROCEDURE run_extract (

        pi_wf_name IN VARCHAR2,

        pi_extract_start_dttm IN DATE,

        pi_extract_end_dttm IN DATE DEFAULT SYSDATE,

        pi_update_dt_or_event_dt_flag IN VARCHAR2 DEFAULT 'D'   

    );

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

    PROCEDURE extract_urlalias(

        pi_wf_name IN VARCHAR2,

        pi_comp_name IN VARCHAR2,

        pi_wf_start_dttm IN DATE DEFAULT SYSDATE,

        pi_extract_start_dttm IN DATE DEFAULT NULL,

        pi_extract_end_dttm   IN DATE DEFAULT SYSDATE,

        pi_update_dt_or_event_dt_flag IN VARCHAR2 DEFAULT 'D'    

    );

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

    PROCEDURE extract_contenturlalias_hpccm(

        pi_wf_name IN VARCHAR2,

        pi_comp_name IN VARCHAR2,

        pi_wf_start_dttm IN DATE DEFAULT SYSDATE    

    );  

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

    PROCEDURE extract_contenturlalias_hpusa(

        pi_wf_name IN VARCHAR2,

        pi_comp_name IN VARCHAR2,

        pi_wf_start_dttm IN DATE DEFAULT SYSDATE    

    ); 

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

    PROCEDURE extract_campaigns(

        pi_wf_name in varchar2,

        pi_comp_name IN VARCHAR2,

        pi_wf_start_dttm IN DATE DEFAULT SYSDATE    

    );

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

    PROCEDURE extract_tqs_program(

        pi_wf_name IN VARCHAR2,

        pi_comp_name IN VARCHAR2,

        pi_wf_start_dttm IN DATE DEFAULT SYSDATE,

        pi_extract_start_dttm IN DATE DEFAULT NULL,

        pi_extract_end_dttm   IN DATE DEFAULT SYSDATE,

        pi_update_dt_or_event_dt_flag in varchar2 default 'D'         

    );

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

    PROCEDURE extract_event_context_values(

        pi_wf_name IN VARCHAR2,

        pi_comp_name IN VARCHAR2,

        pi_wf_start_dttm IN DATE DEFAULT SYSDATE,

        pi_extract_start_dttm IN DATE DEFAULT NULL,

        pi_extract_end_dttm   IN DATE DEFAULT SYSDATE,

        pi_update_dt_or_event_dt_flag in varchar2 default 'D'         

    );

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

    PROCEDURE extract_user (

            pi_wf_name IN VARCHAR2,

            pi_comp_name IN VARCHAR2,

            pi_wf_start_dttm IN DATE,

            pi_extract_start_dttm IN DATE DEFAULT to_date('1970-01-01','YYYY-MM-DD'),

            pi_extract_end_dttm IN DATE DEFAULT SYSDATE,

            pi_rfc_flag IN VARCHAR2 DEFAULT 'N'

        );

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

    PROCEDURE filter_user(

              pi_wf_name IN VARCHAR2

            , pi_comp_name IN VARCHAR2

            , PI_WF_START_DTTM IN DATE

        );   

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

    PROCEDURE extract_state_lookup(

              pi_wf_name IN VARCHAR2

            , pi_comp_name IN VARCHAR2

            , pi_wf_start_dttm IN DATE DEFAULT SYSDATE

            );

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

    PROCEDURE extract_list_source(

              pi_wf_name IN VARCHAR2

            , pi_comp_name IN VARCHAR2

            , pi_wf_start_dttm IN DATE DEFAULT SYSDATE

            );       

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

    END pkg_extract_dim;

  • 3. Re: R4 EA - Run packaged procedure - loss of utility
    Vadim Tropashko Pro
    Currently Being Moderated

    Reproduced: I'm getting

    "Syntax Error at line 21, column 26; Expected: ':',default_expr_opt,'DEFAULT',NOT_NULL_opt,'NULL',"

    in java console.

     

    Bugged as 17271729

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points