2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 16:49:39 +02:00
It is a best practice to have variable declarations outside of the loop. Additionally, declaring variables inside a loop is slightly less efficient because memory management is then performed with each iteration of the loop.
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
----
BEGIN
FOR i IN 1..10
LOOP
DECLARE
variableX NUMBER:= 10;
BEGIN
variableX:= variableX+i;
dbms_output.put_line(variableX);
END;
END LOOP;
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
----
DECLARE
variableX NUMBER:= 0;
BEGIN
FOR i IN 1..10
LOOP
variableX:= variableX+1;
dbms_output.put_line(variableX);
END LOOP;
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
Move this variable declaration outside of the loop.
=== Highlighting
Variable declaration
2021-09-20 15:38:42 +02:00
endif::env-github,rspecator-view[]