Fix #54 - Added new rule G-2610: Never use self-defined weak ref cursor types.

Author: kibeha

docs/4-language-usage/2-variables-and-types/6-cursor-variables/.pages

@@ -0,0 +1 @@
+title: Cursor Variables

docs/4-language-usage/2-variables-and-types/6-cursor-variables/g-2610.md

@@ -0,0 +1,47 @@
+# G-2610: Never use self-defined weak ref cursor types.
+
+!!! tip "Minor"
+    Changeability, Maintainability, Portability, Reusability
+
+## Reason
+
+There is no reason to define your own weak ref cursor types, as they are not different from the built-in `sys_refcursor`. Introducing your own types just gives you unnecessary maintenance to perform.
+
+## Example (bad)
+
+``` sql
+declare
+   type local_weak_cursor_type is ref cursor;
+   cv_data  local_weak_cursor_type;
+begin
+   if configuration.use_employee then
+      open cv_data for
+         select e.employee_id, e.first_name, e.last_name
+           from employees e;
+   else
+      open cv_data for
+         select e.emp_id, e.name
+           from emp e;
+   end if;
+end;
+/
+```
+
+## Example (good)
+
+``` sql
+declare
+   cv_data  sys_refcursor;
+begin
+   if configuration.use_employee then
+      open cv_data for
+         select e.employee_id, e.first_name, e.last_name
+           from employees e;
+   else
+      open cv_data for
+         select e.emp_id, e.name
+           from emp e;
+   end if;
+end;
+/
+```

docs/9-appendix/appendix.md

@@ -43,6 +43,7 @@ n/a | 2230 | Try to use SIMPLE_INTEGER datatype when appropriate.  | Minor |  |
 23 | 2340 | Always define your VARCHAR2 variables using CHAR SEMANTIC (if not defined anchored). | Minor |  |  |  |  | ✘ |  |  | 
 24 | 2410 | Try to use boolean data type for values with dual meaning. | Minor |  |  | ✘ |  |  |  |  | 
 25 | 2510 | Avoid using the LONG and LONG RAW data types. | Major |  |  |  | ✘ |  |  |  | 
+n/a | 2610 | Never use self-defined weak ref cursor types. | Minor | ✘ |  | ✘ | ✘ |  | ✘ |  | 
 26 | 3110 | Always specify the target columns when coding an insert statement. | Major |  |  | ✘ |  | ✘ |  |  | 
 n/a | 3115 | Avoid self-assigning a column. | Minor |  |  | ✘ |  |  |  |  | 
 27 | 3120 | Always use table aliases when your SQL statement involves more than one source. | Major |  |  | ✘ |  |  |  |  | 
@@ -89,6 +90,7 @@ n/a | 5010 | Try to use a error/logging framework for your application. | Critic
 55 | 5050 | Avoid use of the RAISE_APPLICATION_ERROR built-in procedure with a hard-coded  20nnn error number or hard-coded message.  | Major | ✘ |  | ✘ |  |  |  |  | 
 56 | 5060 | Avoid unhandled exceptions. | Major |  |  |  |  | ✘ |  |  | 
 57 | 5070 | Avoid using Oracle predefined exceptions. | Critical |  |  |  |  | ✘ |  |  | 
+n/a | 5080 | Always use FORMAT_ERROR_BACKTRACE when using FORMAT_ERROR_STACK or SQLERRM. | Minor |  |  | ✘ |  |  |  |  | ✘
 58 | 6010 | Always use a character variable to execute dynamic SQL. | Major |  |  | ✘ |  |  |  |  | ✘
 59 | 6020 | Try to use output bind arguments in the RETURNING INTO clause of dynamic DML statements rather than the USING clause.  | Minor |  |  | ✘ |  |  |  |  | 
 60 | 7110 | Try to use named notation when calling program units. | Major | ✘ |  | ✘ |  |  |  |  | 

docs/stylesheets/extra.css

@@ -204,6 +204,7 @@
     [id="character-data-types"], 
     [id="boolean-data-types"], 
     [id="large-objects"],
+    [id="cursor-variables"],
     [id="dml-sql"], 
     [id="bulk-operations"], 
     [id="transaction-control"], 

tools/run-in-container/genpdf.sh

@@ -119,6 +119,8 @@ write_text "### Boolean Data Types"
 write_guidelines "4-language-usage/2-variables-and-types/4-boolean-data-types" "####"
 write_text "### Large Objects"
 write_guidelines "4-language-usage/2-variables-and-types/5-large-objects" "####"
+write_text "### Cursor Variables"
+write_guidelines "4-language-usage/2-variables-and-types/6-cursor-variables" "####"
 write_text "## DML & SQL"
 write_text "### General"
 write_guidelines "4-language-usage/3-dml-and-sql/1-general" "####"