Positional vs. named parameter passing. : Procedure Parameters « Stored Procedure Function « Oracle PL / SQL






  1. Oracle PL / SQL
  2. Stored Procedure Function
  3. Procedure Parameters

Positional vs. named parameter passing.

    

SQL> CREATE OR REPLACE PROCEDURE CallMe(pA VARCHAR2,pB NUMBER,pC BOOLEAN,pD DATE) AS
  2  BEGIN
  3    NULL;
  4  END CallMe;
  5  /

SP2-0804: Procedure created with compilation warnings

SQL>
SQL>
SQL> -- This call uses positional notation
SQL> DECLARE
  2    v1 VARCHAR2(10);
  3    v2 NUMBER(7,6);
  4    v3 BOOLEAN;
  5    v4 DATE;
  6  BEGIN
  7    CallMe(v1, v2, v3, v4);
  8  END;
  9  /

PL/SQL procedure successfully completed.

SQL>








Related examples in the same category

1.Number type parameter
2.create and pass in three parms
3.Store procedure with three parameters
4.create default values
5.positional and named notation for procedure calls.
6.Passing parameter by parameter name
7.Procedure with four parameters
8.First 2 parameters passed by position, the second 2 are passed by name
9.Pass null to procedure
10.Wrong way to reference parameters
11.Procedure with colunm type as parameter type
12.NOCOPY modifier.
13.Legal and illegal formal parameters which are constrained by length.
14.ParameterLength using %TYPE for the parameters(Calling ParameterLength illegally (ORA-6502))
15.Use SYS_REFCURSOR as parameter type
16.Different ways of calling a procedure with default parameters.
17.Default Parameter Values
18.Use column type to control parameter type
19.Use concatenation to wrap string passed in
20.User-defined collection type parameter