The purpose of the DDL Transformation is to create a data model from the logical model, generating a model targeted at the default database type that is ready for DDL generation. The data model can then be used to automatically generate DDL statements to run in one of the Enterprise Architect supported database products.
It uses and demonstrates support in the intermediary language for the following database-specific concepts:
Table |
Mapped one-to-one onto Class elements. |
Column |
Mapped one-to-one onto attributes. |
Primary Key |
Lists all the columns involved; this ensures that they exist in the class and creates a primary key method for them. |
Foreign Key |
This is a special sort of connector. In the Source and Target sections, lists all of the columns involved; this ensures that they exist and that a matching primary key exists in the destination class, and creates the appropriate foreign key. |
The following two diagrams show a typical PIM to Data Model Transformation.
The PIM:
The PSM as automatically generated:
Generalizations are handled by providing the child element with a foreign key to the parent element, as shown below. Copy-down inheritance is not supported.
