51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
43 lines
891 B
Plaintext
43 lines
891 B
Plaintext
== Why is this an issue?
|
|
|
|
The requirement for a final ``++ELSE++`` clause is defensive programming. The ``++CASE++`` statement should always provide a value.
|
|
|
|
=== Noncompliant code example
|
|
|
|
[source,sql]
|
|
----
|
|
CASE grade -- Noncompliant, can raise a CASE_NOT_FOUND exception.
|
|
WHEN 'A' THEN DBMS_OUTPUT.PUT_LINE('Excellent');
|
|
WHEN 'B' THEN DBMS_OUTPUT.PUT_LINE('Very Good');
|
|
END CASE;
|
|
----
|
|
|
|
=== Compliant solution
|
|
|
|
[source,sql]
|
|
----
|
|
CASE grade
|
|
WHEN 'A' THEN DBMS_OUTPUT.PUT_LINE('Excellent');
|
|
WHEN 'B' THEN DBMS_OUTPUT.PUT_LINE('Very Good');
|
|
ELSE DBMS_OUTPUT.PUT_LINE('No such grade');
|
|
END CASE;
|
|
----
|
|
|
|
include::../see.adoc[]
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|