When doing advanced development work, you can work from
the UML model. This topic lists specific issues that you should consider
when working with UML.
The UML model provides abstract classes and interfaces. You can
configure column properties of these abstract classes and interfaces,
unless they are set as private.
Assumptions
You should note
the following assumptions about the UML and how it maps to the database:
- Any class in the UML is treated as a table.
- Any property of a class is treated as a column.
- Other UML items are ignored, including the following items:
- Operations
- Methods in the class
Considerations
Note the
following considerations when working with the UML model:
- If you have defined an abstract class in UML, you cannot apply
the Database Application Generator table transform to the class. However,
you can configure properties.
- If you have defined an interface in UML, you cannot apply the
Database Application Generator table transform to the interface. However,
you can configure properties.
- If you have defined any relationships between classes, those are
ignored.
- When you import from a database, the relationships are ignored,
and the application is not generated.