The SQL Designer module provides services for modeling databases at the conceptual (data model) and logical (table model) levels.
The term conceptual model refers here to a UML class model that has been annotated ready for the generation of SQL script files. This model also serves as the data model for the Hibernate Designer module.
They are two methods for obtaining an SQL persistence model:
The SQL Designer module comes with a set of commands for use when building a class model annotated for the generation of SQL script files.
List of commands:
DataModel (avaialable on Package UML): Creation of the root of the conceptual model.
DataModel (available on
DataModel /
DataModel): Creation of a package in the conceptual model.
Entity: (available on
DataModel /
DataModel): Creation of a persistent class.
Identifier: (available on
Entity): Creation of an attribute that will serve as the identifier of a persistent class.
Attribute (available on
Entity): Creation of an attribute for a persistent class.
Relationship (available on
Entity): Creation of an association between two persistent classes.
Hierarchy (available on
Entity): Creation of a generalization link between two persistent classes.
Persistent Diagram
(available on
DataModel /
DataModel): Creation of a diagram dedicated to conceptual SQL modeling.
An existing UML class model can be transformed into an SQL persistence model. To do this, simply select the package containing the classes that you want to make persistent and then check the “Persistent” tickbox in the SQL tab.
If you uncheck this tickbox, then an SQL model will be transformed into a class model.