2023-05-03 11:06:20 +02:00
== Why is this an issue?
2021-04-28 16:49:39 +02:00
For better readability, column aliases should be used with the ``++AS++`` keyword. If it is missing, it could be misread as another column being selected.
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
----
DECLARE
result DUAL.dummy%TYPE;
BEGIN
SELECT
dummy d -- Non-Compliant - could be misread as selecting both "dummy" and a column "d"
INTO
result
FROM
DUAL;
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
result DUAL.dummy%TYPE;
BEGIN
SELECT
dummy AS d -- Compliant
INTO
result
FROM
DUAL;
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
Add the "AS" keyword to this alias of "xxx".
2021-09-20 15:38:42 +02:00
endif::env-github,rspecator-view[]