As much as possible, Relational Design Center uses Enterprise Database Server names in the descriptions it generates. However, the SQL names are different if the Enterprise Database Server names are modified through additional semantics or if there is a naming conflict. The rules for names are slightly different between SQL and Enterprise Database Server. For example, Relational Design Center sometimes needs to substitute names for new tables when mapping occurring items. These new table names might conflict with other names in an Enterprise Database Server database or with other substituted table names. These naming conflicts must be resolved.
Handling Naming Conflicts
If Relational Design Center encounters a naming conflict between SQL and Enterprise Database Server, it resolves the conflict by altering the Enterprise Database Server name in the SQL description as follows:
-
For the first occurrence of a conflict, Relational Design Center appends the type of the SQL object to the Enterprise Database Server name, connecting them with an underscore character (_).
-
For additional occurrences of a naming conflict, Relational Design Center appends a unique name.
Typically, item name conflicts are resolved by truncating the name to 24 characters and then appending _COLnn to the name. Structure name conflicts are resolved by truncating the name to 22, 23, or 24 characters and appending _INDEXnn, _VIEWnn, or _TBLnn to the name.
The variable nn is a unique integer.
For example, the first occurrence of an item named SELECT would become SELECT_COL00 because SELECT is a reserved word in SQL. Another occurrence of SELECT would become SELECT_COL01.
-
Relational Design Center records any name changes in the results file.
For more information about Enterprise Database Server naming conventions, refer to the Data and Structure Definition Language (DASDL) Programming Reference Manual. For more information about SQL naming conventions, refer to the Query Processor Programming Guide.
