Fix #88 and #89 - Added "Unsupported" mark and reason to G-3160, G-3170, G-5010, G-7170, G-8410, G-8510. Added explanation to introduction.md

Author: kibeha

docs/1-introduction/introduction.md

@@ -52,6 +52,15 @@ Example     | Precedes text used to illustrate a rule or a recommendation.
 Reason      | Explains the thoughts and purpose behind a rule or a recommendation.
 Restriction | Describes the circumstances to be fulfilled to make use of a rule.
 
+### Validator support ###
+
+The tool PL/SQL Cop (see the "Tool Support" chapter) cannot support *all* the guidelines in this document. Those guidelines that are *not* supported by PL/SQL Cop validators are marked like this:
+
+!!! missing "Unsupported in PL/SQL Cop Validators"
+    Reason why the specific guideline is not supported by the validators.
+
+The PL/SQL Cop repository documents the [details of validator limitations](https://github.com/Trivadis/plsql-cop-cli/blob/main/validator-limitations.md#guidelines).
+
 ### Why are standards important
 
 For a machine executing a program, code formatting is of no importance. However, for the human eye, well-formatted code is much easier to read. Modern tools can help to implement format and coding rules.

docs/4-language-usage/3-dml-and-sql/1-general/g-3160.md

@@ -3,6 +3,9 @@
 !!! warning "Major"
     Maintainability, Reliability
 
+!!! missing "Unsupported in PL/SQL Cop Validators"
+    We cannot identify the type of a column. Requires `create table` and `alter table` parser support or access to the Oracle Data Dicionary.
+
 ## Restriction
 
 ORACLE 12c

docs/4-language-usage/3-dml-and-sql/1-general/g-3170.md

@@ -3,6 +3,9 @@
 !!! warning "Major"
     Reliability
 
+!!! missing "Unsupported in PL/SQL Cop Validators"
+    We cannot identify column default values. Requires `create table` and `alter table` parser support or access to the Oracle Data Dicionary.
+
 ## Restriction
 
 ORACLE 12c

docs/4-language-usage/5-exception-handling/g-5010.md

@@ -3,6 +3,9 @@
 !!! danger "Critical"
     Reliability, Reusability, Testability
 
+!!! missing "Unsupported in PL/SQL Cop Validators"
+    We cannot identify logging framework and where it should be applied. Requires further definition regarding naming of the error/logging framework and its minimal use in PL/SQL code.
+
 ## Reason
 
 Having a framework to raise/handle/log your errors allows you to easily avoid duplicate application error numbers and having different error messages for the same type of error.

docs/4-language-usage/7-stored-objects/1-general/g-7170.md

@@ -4,7 +4,7 @@
     Efficiency, Maintainability
 
 !!! missing "Unsupported in PL/SQL Cop Validators"
-    Rule G-7170 is not expected to be implemented in the static code analysis validators.
+    We cannot determine the usage of an `in out` parameter in a reliable way, especially when other units are involved which are maintained in another file.
 
 ## Reason
 

docs/4-language-usage/8-patterns/4-ensure-single-execution-at-a-time-of-a-program-unit/g-8410.md

@@ -3,6 +3,9 @@
 !!! tip "Minor"
     Efficiency, Reliability
 
+!!! missing "Unsupported in PL/SQL Cop Validators"
+    We cannot identify where an application lock would make sense. Algorithms to detect wrong, missing and right usages of this pattern are virtually impossible to implement without understanding the context.
+
 ## Reason
 
 This technique allows us to have locks across transactions as well as a proven way to clean up at the end of the session.

docs/4-language-usage/8-patterns/5-use-dbms-application-info-package-to-follow-progress-of-a-process/g-8510.md

@@ -3,6 +3,9 @@
 !!! tip "Minor"
     Efficiency, Reliability
 
+!!! missing "Unsupported in PL/SQL Cop Validators"
+    We cannot know where the use of `dbms_application_info` is sensible. Algorithms to detect wrong, missing and right usages of this pattern are virtually impossible to implement without understanding the context.
+
 ## Reason
 
 This technique allows us to view progress of a process without having to persistently write log data in either a table or a file. The information is accessible through the `v$session` view.