add parameters p_dml_view_name and p_one_to_one_view_name

Author: ogobrecht

README.md

@@ -79,7 +79,7 @@ SIGNATURE
 ```sql
 PACKAGE om_tapigen AUTHID CURRENT_USER IS
 c_generator         CONSTANT VARCHAR2(10 CHAR) := 'OM_TAPIGEN';
-c_generator_version CONSTANT VARCHAR2(10 CHAR) := '0.5.2.32';
+c_generator_version CONSTANT VARCHAR2(10 CHAR) := '0.5.2.33';
 ```
 
 
@@ -114,8 +114,10 @@ PROCEDURE compile_api
   p_double_quote_names          IN BOOLEAN  DEFAULT TRUE,  -- If true, object names (owner, table, columns) are placed in double quotes.
   p_default_bulk_limit          IN INTEGER  DEFAULT 1000,  -- The default bulk size for the set based methods (create_rows, read_rows, update_rows)
   p_enable_dml_view             IN BOOLEAN  DEFAULT FALSE, -- If true, a view with an instead of trigger is generated, which simply calls the API methods - can be useful for low code frontends like APEX.
+  p_dml_view_name               IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the DML view - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
   p_enable_one_to_one_view      IN BOOLEAN  DEFAULT FALSE, -- If true, a 1:1 view with read only is generated - useful when you want to separate the tables into an own schema without direct user access.
-  p_api_name                    IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the API - you can use substitution like #TABLE_NAME_4_20# (treated as substr(4,20)).
+  p_one_to_one_view_name        IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the 1:1 view - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
+  p_api_name                    IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the API - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
   p_sequence_name               IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the create_row methods - same substitutions like with API name possible.
   p_exclude_column_list         IN VARCHAR2 DEFAULT NULL,  -- If not null, the provided comma separated column names are excluded on inserts and updates (virtual columns are implicitly excluded).
   p_audit_column_mappings       IN VARCHAR2 DEFAULT NULL,  -- If not null, the provided comma separated column names are excluded and populated by the API (you don't need a trigger for update_by, update_on...).
@@ -161,8 +163,10 @@ FUNCTION compile_api_and_get_code
   p_double_quote_names          IN BOOLEAN  DEFAULT TRUE,  -- If true, object names (owner, table, columns) are placed in double quotes.
   p_default_bulk_limit          IN INTEGER  DEFAULT 1000,  -- The default bulk size for the set based methods (create_rows, read_rows, update_rows)
   p_enable_dml_view             IN BOOLEAN  DEFAULT FALSE, -- If true, a view with an instead of trigger is generated, which simply calls the API methods - can be useful for low code frontends like APEX.
+  p_dml_view_name               IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the DML view - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
   p_enable_one_to_one_view      IN BOOLEAN  DEFAULT FALSE, -- If true, a 1:1 view with read only is generated - useful when you want to separate the tables into an own schema without direct user access.
-  p_api_name                    IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the API - you can use substitution like #TABLE_NAME_4_20# (treated as substr(4,20)).
+  p_one_to_one_view_name        IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the 1:1 view - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
+  p_api_name                    IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the API - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
   p_sequence_name               IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the create_row methods - same substitutions like with API name possible.
   p_exclude_column_list         IN VARCHAR2 DEFAULT NULL,  -- If not null, the provided comma separated column names are excluded on inserts and updates (virtual columns are implicitly excluded).
   p_audit_column_mappings       IN VARCHAR2 DEFAULT NULL,  -- If not null, the provided comma separated column names are excluded and populated by the API (you don't need a trigger for update_by, update_on...).
@@ -210,8 +214,10 @@ FUNCTION get_code
   p_double_quote_names          IN BOOLEAN  DEFAULT TRUE,  -- If true, object names (owner, table, columns) are placed in double quotes.
   p_default_bulk_limit          IN INTEGER  DEFAULT 1000,  -- The default bulk size for the set based methods (create_rows, read_rows, update_rows)
   p_enable_dml_view             IN BOOLEAN  DEFAULT FALSE, -- If true, a view with an instead of trigger is generated, which simply calls the API methods - can be useful for low code frontends like APEX.
+  p_dml_view_name               IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the DML view - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
   p_enable_one_to_one_view      IN BOOLEAN  DEFAULT FALSE, -- If true, a 1:1 view with read only is generated - useful when you want to separate the tables into an own schema without direct user access.
-  p_api_name                    IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the API - you can use substitution like #TABLE_NAME_4_20# (treated as substr(4,20)).
+  p_one_to_one_view_name        IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the 1:1 view - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
+  p_api_name                    IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the API - you can use substitutions like #TABLE_NAME# or #TABLE_NAME_4_20# (treated as substr(table_name, 4, 20)).
   p_sequence_name               IN VARCHAR2 DEFAULT NULL,  -- If not null, the given name is used for the create_row methods - same substitutions like with API name possible.
   p_exclude_column_list         IN VARCHAR2 DEFAULT NULL,  -- If not null, the provided comma separated column names are excluded on inserts and updates (virtual columns are implicitly excluded).
   p_audit_column_mappings       IN VARCHAR2 DEFAULT NULL,  -- If not null, the provided comma separated column names are excluded and populated by the API (you don't need a trigger for update_by, update_on...).

docs/changelog.md

@@ -39,6 +39,7 @@ Please use for all comments, discussions, feature requests or bug reports the Gi
 - added: support for audit columns (parameters p_audit_column_mappings and p_audit_user_expression)
 - added: support for a row version column (parameter p_row_version_column_mapping)
 - added: support for a 1:1 view with read only (parameter p_enable_one_to_one_view)
+- added: support for naming the generated views (parameters p_dml_view_name and p_one_to_one_view_name)
 - added: double quoting of table and column names can now be configured (parameter p_double_quote_names, default true)
 - added: update function with return clause (mainly for use in create_or_update_row to prevent read row after update)
 - added: unit tests with utPLSQL (it will be a permanent task to improve the tests with every new feature or bugfix)

docs/parameters.md

@@ -28,7 +28,9 @@
 - [p_double_quote_names (since v0.6.0)](#p_double_quote_names-since-v060)
 - [p_default_bulk_limit (since v0.6.0)](#p_default_bulk_limit-since-v060)
 - [p_enable_dml_view (since v0.4.0)](#p_enable_dml_view-since-v040)
+- [p_dml_view_name (since v0.6.0)](#p_dml_view_name-since-v060)
 - [p_enable_one_to_one_view (since v0.6.0)](#p_enable_one_to_one_view-since-v060)
+- [p_one_to_one_view_name (since v0.6.0)](#p_one_to_one_view_name-since-v060)
 - [p_api_name (since v0.5.0)](#p_api_name-since-v050)
 - [p_sequence_name (since v0.2.0)](#p_sequence_name-since-v020)
 - [p_exclude_column_list (since v0.5.0)](#p_exclude_column_list-since-v050)
@@ -43,7 +45,7 @@
 
 ## p_table_name (since v0.0.0 ;-)
 
-- String (all_objects.object_name%TYPE), mandatory
+- String (varchar2), mandatory
 - The table for which an API should be generated
 
 ## p_owner (since v0.5.0)
@@ -131,25 +133,45 @@
 - If true, a view trigger named `#TABLE_NAME#_IOIUD` is created to handle DML operations on the view
 - If false, view and trigger are NOT generated
 
+## p_dml_view_name (since v0.6.0)
+
+- String (varchar2), default: null
+- If not null, the given name is used for the DML view
+- You can use substitutions - examples:
+  - `#TABLE_NAME_20#` is treated as `substr(table_name, 1, 20)`
+  - `#TABLE_NAME_5_20#` is treated as `substr(table_name, 5, 20)`
+  - `#TABLE_NAME_-20_20#` is treated as `substr(table_name, -20, 20)`
+  - For table EMP and `p_dml_view_name => '#TABLE_NAME_26#_V'` you get `EMP_V`
+
 ## p_enable_one_to_one_view (since v0.6.0)
 
 - Boolean, default: false
 - If true, a 1:1 view with read only is generated
 - Can be useful when you want to separate the tables into an own schema without direct user access
 
+## p_one_to_one_view_name (since v0.6.0)
+
+- String (varchar2), default: null
+- If not null, the given name is used for the 1:1 view
+- You can use substitutions - examples:
+  - `#TABLE_NAME_20#` is treated as `substr(table_name, 1, 20)`
+  - `#TABLE_NAME_5_20#` is treated as `substr(table_name, 5, 20)`
+  - `#TABLE_NAME_-20_20#` is treated as `substr(table_name, -20, 20)`
+  - For table EMP and `p_one_to_one_view_name => '#TABLE_NAME_26#_V'` you get `EMP_V`
+
 ## p_api_name (since v0.5.0)
 
-- String (all_objects.object_name%TYPE), default: null
+- String (varchar2), default: null
 - If not null, the given name is used for the API
 - You can use substitutions - examples:
-  - `#TABLE_NAME_20#` is treated as `substr(table_name,1,20)`
-  - `#TABLE_NAME_5_20#` is treated as `substr(table_name,5,20)`
-  - `#TABLE_NAME_-20_20#` is treated as `substr(table_name,-20,20)`
+  - `#TABLE_NAME_20#` is treated as `substr(table_name, 1, 20)`
+  - `#TABLE_NAME_5_20#` is treated as `substr(table_name, 5, 20)`
+  - `#TABLE_NAME_-20_20#` is treated as `substr(table_name, -20, 20)`
   - For table EMP and `p_api_name => '#TABLE_NAME_26#_API'` you get `EMP_API`
 
 ## p_sequence_name (since v0.2.0)
 
-- String (all_objects.object_name%TYPE), default: null
+- String (varchar2), default: null
 - If a sequence name is given here, then the resulting API is taken the ID for the create_row methods and you don't need to create a trigger for your table only for the sequence handling
 - you can use the following substitution Strings, the generator is replacing this at runtime: `#TABLE_NAME_24#`, `#TABLE_NAME_26#`, `#TABLE_NAME_28#`, `#PK_COLUMN_26#`, `#PK_COLUMN_28#`, `#COLUMN_PREFIX#`
 - Example 1: `#TABLE_NAME_26#_SEQ`