2023-05-03 11:06:20 +02:00
|
|
|
== Why is this an issue?
|
|
|
|
|
2021-04-28 16:49:39 +02:00
|
|
|
By default, the parameter mode is ``++IN++``. However, specifying it explicitly makes the code easier to read.
|
|
|
|
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2023-05-03 11:06:20 +02:00
|
|
|
=== Noncompliant code example
|
2021-04-28 16:49:39 +02:00
|
|
|
|
2022-02-04 17:28:24 +01:00
|
|
|
[source,sql]
|
2021-04-28 16:49:39 +02:00
|
|
|
----
|
|
|
|
SET SERVEROUTPUT ON
|
|
|
|
|
|
|
|
DECLARE
|
|
|
|
PROCEDURE printName(name VARCHAR2) AS -- Noncompliant; relies on default mode
|
|
|
|
BEGIN
|
|
|
|
DBMS_OUTPUT.PUT_LINE('name: ' || name);
|
|
|
|
END;
|
|
|
|
|
|
|
|
BEGIN
|
|
|
|
printName('Foo');
|
|
|
|
END;
|
|
|
|
/
|
|
|
|
----
|
|
|
|
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2023-05-03 11:06:20 +02:00
|
|
|
=== Compliant solution
|
2021-04-28 16:49:39 +02:00
|
|
|
|
2022-02-04 17:28:24 +01:00
|
|
|
[source,sql]
|
2021-04-28 16:49:39 +02:00
|
|
|
----
|
|
|
|
SET SERVEROUTPUT ON
|
|
|
|
|
|
|
|
DECLARE
|
|
|
|
PROCEDURE printName(name IN VARCHAR2) AS
|
|
|
|
BEGIN
|
|
|
|
DBMS_OUTPUT.PUT_LINE('name: ' || name);
|
|
|
|
END;
|
|
|
|
BEGIN
|
|
|
|
printName('Foo');
|
|
|
|
END;
|
|
|
|
/
|
|
|
|
----
|
2021-04-28 18:08:03 +02:00
|
|
|
|
2021-09-20 15:38:42 +02:00
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
|
|
|
|
'''
|
|
|
|
== Implementation Specification
|
|
|
|
(visible only on this page)
|
|
|
|
|
2023-05-25 14:18:12 +02:00
|
|
|
=== Message
|
|
|
|
|
|
|
|
Specify this parmeter mode as "IN".
|
|
|
|
|
2021-09-20 15:38:42 +02:00
|
|
|
|
|
|
|
endif::env-github,rspecator-view[]
|