SQL/DDL Implementation › Extended SQL Naming › Understanding Extended SQL Naming

Understanding Extended SQL Naming

EXEC SQL                                             
     COMMENT ON RWCSQL.ORDL1 (                       
           ABABCD   IS   ‘Order code’                
          ,ABADCD   IS   ‘Customer code’             
          ,ABACTX   IS   ‘Customer name’             
          ,ABABST   IS   ‘Order status’              
          ,ABABDT   IS   ‘Order date’                
                                         )           
END-EXEC                                             
                                                     
EXEC SQL                                             
     LABEL ON TABLE RWCSQL.ORDL IS                   
         ‘Orders       Retr’                         
END-EXEC                                             
                                                     
EXEC SQL                                             
     CREATE UNIQUE INDEX RWCSQL.ORDL1I ON RWCSQL.ORDP
         (ABABCD        ASC                          
          )                                          
END-EXEC                                            

The optional extended SQL naming feature assigns longer, more meaningful names as follows:

• SQL Tables and Columns—These are assigned the 25 character unique file and field names currently found in the model. Since names for CA 2E model files and fields can be any combination of allowable characters and blanks as long as the name is unique within the model, you need to ensure that no illegal characters are used.

  The CA 2E generators map special characters as shown in the following table.

Note: When you generate the SQL/DDL with certain column names, they fail to generate and throw error messages. However, using the same field names for the DDS implementation result in successful generation.

Example: If you have a field starting with a number such as “2nd_Order”, the SQL/DDL fails to generate a table with such column name with the following error:

“SQL0103 - Numeric constant 2nd_Order not valid.” 

However, the DDS implementation with the same field name is successfully generated.

• SQL Views—Views are assigned the access path source member name.
• SQL Indexes—Index names are assigned at generation time by appending an ‘ to the access path source member name. They are a maximum of ten characters long.