You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/1-introduction/introduction.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,12 +54,12 @@ Restriction | Describes the circumstances to be fulfilled to make use of a rule.
54
54
55
55
### Validator support ###
56
56
57
-
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:
57
+
The tool db\* CODECOP (see the "Tool Support" chapter) cannot support *all* the guidelines in this document. Those guidelines that are *not* supported by db\* CODECOP validators are marked like this:
58
58
59
-
!!! missing "Unsupported in PL/SQL Cop Validators"
59
+
!!! missing "Unsupported in db\* CODECOP Validators"
60
60
Reason why the specific guideline is not supported by the validators.
61
61
62
-
The PL/SQL Cop repository documents the [details of validator limitations](https://github.com/Trivadis/plsql-cop-cli/blob/main/validator-limitations.md#guidelines).
62
+
The db\* CODECOP repository documents the [details of validator limitations](https://github.com/Trivadis/plsql-cop-cli/blob/main/validator-limitations.md#guidelines).
Copy file name to clipboardExpand all lines: docs/4-language-usage/5-exception-handling/g-5010.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
!!! danger "Critical"
4
4
Reliability, Reusability, Testability
5
5
6
-
!!! missing "Unsupported in PL/SQL Cop Validators"
6
+
!!! missing "Unsupported in db\* CODECOP Validators"
7
7
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.
Copy file name to clipboardExpand all lines: docs/4-language-usage/7-stored-objects/1-general/g-7170.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
!!! warning "Major"
4
4
Efficiency, Maintainability
5
5
6
-
!!! missing "Unsupported in PL/SQL Cop Validators"
6
+
!!! missing "Unsupported in db\* CODECOP Validators"
7
7
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.
Copy file name to clipboardExpand all lines: docs/4-language-usage/8-patterns/4-ensure-single-execution-at-a-time-of-a-program-unit/g-8410.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
!!! tip "Minor"
4
4
Efficiency, Reliability
5
5
6
-
!!! missing "Unsupported in PL/SQL Cop Validators"
6
+
!!! missing "Unsupported in db\* CODECOP Validators"
7
7
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.
Copy file name to clipboardExpand all lines: docs/4-language-usage/8-patterns/5-use-dbms-application-info-package-to-follow-progress-of-a-process/g-8510.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
!!! tip "Minor"
4
4
Efficiency, Reliability
5
5
6
-
!!! missing "Unsupported in PL/SQL Cop Validators"
6
+
!!! missing "Unsupported in db\* CODECOP Validators"
7
7
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.
0 commit comments