Merge pull request #72 from Trivadis/feature/minor-changes

Feature/minor changes

Author: PhilippSalvisberg

PLSQL-and-SQL-Coding-Guidelines.pdf

@@ -60,6 +60,15 @@ Singular name of what is stored in the column (unless the column data type is a
 
 Add a comment to the database dictionary for every column.
 
+### Check Constraint
+
+Table name or table abbreviation followed by the column and/or role of the check constraint, a `_ck` and an optional number suffix.
+
+Examples:
+
+* `employees_salary_min_ck`
+* `orders_mode_ck`
+
 ### DML / Instead of Trigger
 
 Choose a naming convention that includes:
@@ -182,7 +191,9 @@ Examples:
 
 ### Table
 
-Plural[^1] name of what is contained in the table (unless the table is designed to always hold one row only – then you should use a singular name)
+Plural[^1] name of what is contained in the table (unless the table is designed to always hold one row only – then you should use a singular name).
+
+Suffixed by `_eb` when protected by an editioning view.
 
 Add a comment to the database dictionary for every table and every column in the table.
 
@@ -192,6 +203,7 @@ Examples:
 
 * `employees`
 * `departments`
+* `countries_eb` - table interfaced by an editioning view named `countries`
 * `sct_contracts`
 * `sct_contract_lines`
 * `sct_incentive_modules`
@@ -226,6 +238,8 @@ Examples:
 Plural[^1] name of what is contained in the view.
 Optionally suffixed by an indicator identifying the object as a view (mostly used, when a 1:1 view layer lies above the table layer)
 
+Editioning views are named like the original underlying table to avoid changing the existing application code when introducing edition based redefinition (EBR).
+
 Add a comment to the database dictionary for every view and every column.
 
 Optionally prefixed by a project abbreviation.
@@ -234,6 +248,7 @@ Examples:
 
 * `active_orders`
 * `orders_v` - a view to the orders table
+* `countries` - an editioning view for table `countries_eb`
 
 [^1]:
     We see a table and a view as a collection. A jar containing beans is labeled "beans". 

docs/2-naming-conventions/naming-conventions.md

@@ -43,4 +43,8 @@ CREATE TABLE locations (
   ,city               VARCHAR2(30 CHAR) NOT NULL
   ,CONSTRAINT locations_pk PRIMARY KEY (location_id))
 /
-```
+```
+
+`GENERATED ALWAYS AS IDENTITY` ensures that the `location_id` is populated by a sequence. It is not possible to override the behavior in the application. 
+
+However, if you use a framework that produces an `INSERT` statement including the surrogate key column, and you cannot change this behavior, then you have to use the `GENERATED BY DEFAULT ON NULL AS IDENTITY` option. This has the downside that the application may pass a value, which might lead to an immediate or delayed `ORA-00001: unique constraint violated` error.

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

@@ -16,7 +16,7 @@ Default values have been nullifiable until ORACLE 12c. Meaning any tool sending
 ```
 CREATE TABLE null_test (
    test_case        NUMBER(2) NOT NULL
-  ,column_defaulted VARCHAR2(10) DEFAULT 'Default')
+  ,column_defaulted VARCHAR2(10 CHAR) DEFAULT 'Default')
 /
 INSERT INTO null_test(test_case, column_defaulted) VALUES (1,'Value');
 INSERT INTO null_test(test_case, column_defaulted) VALUES (2,DEFAULT);
@@ -36,7 +36,7 @@ TEST_CASE  COLUMN_DEF
 ```
 CREATE TABLE null_test (
    test_case        NUMBER(2) NOT NULL
-  ,column_defaulted VARCHAR2(10) DEFAULT ON NULL 'Default')
+  ,column_defaulted VARCHAR2(10 CHAR) DEFAULT ON NULL 'Default')
 /
 INSERT INTO null_test(test_case, column_defaulted) VALUES (1,'Value');
 INSERT INTO null_test(test_case, column_defaulted) VALUES (2,DEFAULT);

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

@@ -77,8 +77,10 @@
 
     [id="we-do-not-agree-with-all-your-standards"],
     [id="column"],
-    [id="sequence"],
-    [id="temporary-table-global-temporary-table"],
+    [id="function"],
+    [id="procedure"],
+    [id="table"],
+    [id="view"],
     [id="code-commenting"],
     [id="variables-types"], 
     [id="numeric-data-types"],