As of version 17.0.1, data modeling features (DDL and XML Schema diagrams as well as their associated code engineering features and transformations), have been transferred from MagicDraw to the Cameo Data Modeler plugin which until now provided users only with the ER modeling features.
A new profile has been adopted for database modeling. The new profile covers many more of the concepts specified in the SQL standard than either the Generic DDL or Oracle DDL profiles did and therefore replaces them. This allows for modeling databases in much more detail than was possible in earlier versions. Since the Generic DDL and Oracle DDL Profiles are obsolete, they are no longer used for creating models and code engineering; these profiles are provided only for opening old DDL models and migrating them to new DDL models that are based on the IMM Relational profile.
Note: The database code generation / reverse feature was not changed and does not include the new concepts yet. However, it will be improved in future versions of the Cameo Data Modeler plugin.
Note on terminology: In earlier versions, most of the database modeling features were named “DDL” (for example, DDL diagrams, DDL code engineering set). Since DDL is only a subset of the SQL standard, DDL diagrams have been renamed SQL diagrams in order to reflect the extension of modeling scope. SQL consists of the following:
- DML (data manipulation language) – statements for selecting and editing data.
- DDL (data definition language) – statements for creating and changing database structures, e.g., tables, indexes, etc.
- DCL (data control language) – statements for authorizing user and user group access to data.
After upgrading the plugin to the new version, MagicDraw will ask you if you want to migrate your model to use the new IMM Relational profile. If you choose to do so, MagicDraw will do the migration automatically.
Model elements appear as if they were real database elements instead of UML elements with stereotypes applied (for example, there is the table Specification window instead of the UML class Specification window). Database element Specification windows now show only the model information which is relevant to SQL. UML model information which is irrelevant to SQL (like a property’s visibility) is hidden. This improvement makes database modeling more user-friendly.
In earlier releases there were only two predefined type libraries: one for Oracle and one for all other databases (Generic, DB2, MS SQL Server, MySQL, PostgreSQL, and others). In this release, each database has its own predefined type library, containing collections of the database-specific types. This allows you to be more specific when assigning data types in your database model.
Ability to extend type maps. You can now easily create a custom transformation type map that is based on a predefined (standard) type map by adding your own mapping rules and linking the custom type map to the predefined one. You do not need to copy and / or edit predefined type maps anymore.