This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
novo_motion_schema_editor [2021/02/03 21:35] dlm |
novo_motion_schema_editor [2021/02/05 21:19] dlm |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | [[main_page|NovoMotion Outbound Menu]] | ||
====== NovoMotion Schema Editor ====== | ====== NovoMotion Schema Editor ====== | ||
- | |||
- | |||
The NovoMotion Schema Editor is used to create or maintain the definition of the elements of a schema generator used with the the SQL environment. | The NovoMotion Schema Editor is used to create or maintain the definition of the elements of a schema generator used with the the SQL environment. | ||
- | + | \\ | |
==== NovoMotion Schema Editor - U2 Options Tab - SA Map Example ==== | ==== NovoMotion Schema Editor - U2 Options Tab - SA Map Example ==== | ||
Line 14: | Line 12: | ||
- | {{: | + | {{:file: |
Line 58: | Line 55: | ||
- | * U2 dictionary is the name of the base dictionary item (for the selected file) within the U2 environment. (I descriptors are also supported. I-descriptors that use the SUBR keyword or that execute a TRANS to translate to another file should be used with caution. | + | * U2 dictionary is the name of the base dictionary item (for the selected file) within the U2 environment. (I-descriptors are also supported. I-descriptors that use the SUBR keyword or that execute a TRANS to translate to another file should be used with caution. Warnings are sent to users if they choose |
- | + | ||
- | + | ||
- | * @MULTIVALUEID - Current suggestion is to use multiple primary keys instead of this. However, it is used to explode the controlling attribute of a multi-valued set @MULTIVALUEID:part1: | + | |
- | + | ||
- | + | ||
- | * @ORDINAL - Assigns a numeric sequence to the value - @ORDINAL: | + | |
- | + | ||
- | + | ||
- | * @ACTION - Used to specify a delete or insert event | + | |
- | + | ||
- | + | ||
- | * @LITERAL - Used to pass static data through the schema - @LITERAL:1 | + | |
- | + | ||
- | + | ||
- | * @FIELD - Field based on info - @FIELD: | + | |
- | + | ||
- | + | ||
- | * @TM - Allows selection of a specific table master - @TM: | + | |
- | + | ||
- | + | ||
- | * @CHANGE - Used to change a specific string from one literal to another - @CHANGE: | + | |
- | + | ||
- | + | ||
- | * @CONVERT - Used to change multiple characters from one character to another - @CONVERT: | + | |
- | + | ||
- | + | ||
- | * @ICONV - Used to convert a string to internal format | + | |
- | + | ||
- | + | ||
- | * @OCONV - Used to convert a string to external format | + | |
- | + | ||
- | + | ||
- | * @FMT - Used to format a string | + | |
- | + | ||
- | + | ||
- | * @NOT - The reverse of a string evaluation - @NOT:mvinfo | + | |
- | + | ||
- | + | ||
- | * @TRIM - Removes errant spaces from a string | + | |
- | + | ||
- | + | ||
- | * @NULL - Returns a null character - @NULL | + | |
+ | ^ **Key Word**^ **Description** | | ||
+ | |@MULTIVALUEID |Current suggestion is to use multiple primary keys instead of this. However, it is used to explode the controlling attribute of a multi-valued set @MULTIVALUEID: | ||
+ | |@ORDINAL |Assigns a numeric sequence to the value - @ORDINAL: | ||
+ | |@ACTION | Used to specify a delete or insert event | | ||
+ | |@LITERAL | Used to pass static data through the schema - @LITERAL:1 | | ||
+ | |@FIELD | Field based on info - @FIELD: | ||
+ | |@TM | Allows selection of a specific table master - @TM: | ||
+ | |@CHANGE | Used to change a specific string from one literal to another - @CHANGE: | ||
+ | |@CONVERT | Used to change multiple characters from one character to another - @CONVERT: | ||
+ | |@ICONV | Used to convert a string to internal format | ||
+ | |@OCONV | Used to convert a string to external format | ||
+ | |@FMT | Used to format a string | ||
+ | |@NOT | The reverse of a string evaluation - @NOT:mvinfo | | ||
+ | |@TRIM | Removes errant spaces from a string | ||
+ | |@NULL | Returns a null character - @NULL | | ||
* Ordinal considerations: | * Ordinal considerations: | ||
Line 118: | Line 88: | ||
- | {{file_novo_schema2.jpg}} | + | {{: |
Line 133: | Line 103: | ||
- | ==== NovoMotion Schema Editor - SQL Options tab - SA map example | + | ==== NovoMotion Schema Editor - SQL Options tab - SA Map Example |
- | + | {{: | |
- | {{file_novo_schema3.jpg}} | + | |
Line 159: | Line 128: | ||
- | ==== NovoMotion Schema Editor - Post Job Options | + | ==== NovoMotion Schema Editor - Post Job Options |
- | {{file_novo_schema4.jpg}} | + | {{: |
Line 183: | Line 152: | ||
- | The function contains the following drop down menus: | + | ==== NovoMotion Schema Editor - Drop Down Menus ==== |
- | * **File** | + | === File === |
+ | |||
Line 206: | Line 177: | ||
- | * **Edit** | + | === Edit === |
Line 216: | Line 188: | ||
- | * **Tools** | + | === Tools === |
Line 229: | Line 201: | ||
- | **Note:** The Generate SQL Script is used when one wants to generate script to create the SQL table (See the Creating a SQL script information) to avoid the necessity of creating the SQL table by hand. This is often used multiple times during the development of new schema to perfect the information between U2 and SQL. | + | Note: The Generate SQL Script is used when one wants to generate script to create the SQL table (see [[creating_a_sql_script|Creating a SQL Script]]) to avoid the necessity of creating the SQL table by hand. This is often used multiple times during the development of new schema to perfect the information between U2 and SQL. |
- | The SQL script can be pasted into SQL Management Studio and executed. It will drop any existing SQL table of the name defined in the schema and re-create it with the columns defined in the schema. It does this for both the base SQL table and - if an @ACTION row exists - for the parallel SQL trigger table. | + | The SQL script can be pasted into SQL Management Studio and executed. It will drop any existing SQL table of the name defined in the schema and re-create it with the columns defined in the schema. It does this for both the base SQL table and - if an @ACTION row exists - for the parallel SQL trigger table. |
+ | If a SQL table has already been established and the schema needs to change, the user has the following options: | ||
+ | - Generate the SQL script through the Schema Editor, copy it, paste it into SQL Management Studio, and execute the script. | ||
+ | - Change, add, or delete the desired information in the schema via the Schema Editor, then make the same changes to the SQL table via SQL tools. | ||
- | **Additional Usage Notes: | ||
- | - Generate the SQL script through the Schema Editor, copy it, paste it into SQL Management Studio, and execute the script. | ||
- | - Change, add, or delete the desired information in the schema via the Schema Editor, then make the same changes to the SQL table via SQL tools. | ||
- | + | === Help === | |
- | * **Help** | + | |
Line 247: | Line 218: | ||
- | + | \\ | |
+ | [[main_page|NovoMotion Outbound |