Mapping Database Schema in the Conceptual Model

General

DB-ER mapping is created based on M2M SDK; it has all options with regard to customization and extension that you get in M2M SDK.

What is Mapped?

1. The user selection should be adopted.
   1. All model elements should be mapped upon multiple selection.
   2. The model should be mapped if a model is selected.
   3. The package should be mapped if a package is selected.
   4. The table should be mapped if a table is selected.
   5. The view should be mapped if a view is selected.
   6. If a semantic data type is selected, the semantic data type should be mapped if the option is de.mid.data.UseSDTinDB=true; this is not the default setting.
   7. The sequence should be mapped if a sequence is selected.
   8. The diagram should be mapped if a diagram is selected.
   9. Other elements selected are ignored.
2. Dependent elements should be adopted.
   1. If a view is selected, the view and entities and views used are mapped.
   2. If a diagram is selected, the diagram's contents is mapped.
   3. A column's semantic data type, sequence or data type definition used is mapped; this also applies for a foreign key column's derived type.
   4. A sequence's foreign key type is mapped.
   5. The foreign key which points to a mapped table or view in a mapped table is mapped. The user needs to explicitly select the primary tables, foreign tables and foreign views to map them.
   6. The whole transitive content of a model element is always mapped.
   7. The transitive owner of all mapped model elements is also mapped. Exception: Sequences and semantic data types

What is Created in the ER?

1. Nothing is created if a model element is already connected in the ER; this model element may be modified.
2. One package from DB should be mapped in a package in ER. The owner of the newly-created package in ER is the model.
3. Entities, attributes and keys are created from tables, columns and keys.
4. Nothing is created from indexes.
5. A foreign key and relation is created from a foreign key; a generalization is not created.
6. The diagram is created as per name and owner. Create defaults which may exist are taken into consideration. Creation only takes place if a diagram with the same name does not already exist there and if the de.mid.data.CreateDiagram=true option is set (which is set as default). The diagram content (nodes and edges included, visibility of the compartment and size and placement of the nodes) is not updated if the de.mid.data.MaintainDiagram=false option is set (which is set as default). If you want to update a diagram when mapping, you need to delete it or set the de.mid.data.MaintainDiagram=true option.
7. A semantic data type is created from a semantic data type if de.mid.data.UseSDTinDB=true is set (this is not set as default). A semantic data type is also created for a semantic data type that is the foreign key type of a sequence. The semantic data type is created according to the create default.
8. A semantic data type is created from a data type definition which types a column if the option is set to de.mid.data.UseSDTinER=true (this is not set as default). The owner of this semantic data type is a package with the name of the data type definition. This package is created below the package that is the create default's target for semantic data types. The semantic data type has a name made up of tables and columns. The data type definition's type is mapped according to the type mapping in the type system. However, if the type in the target can be mapped to the source's type in accordance with type mapping, then no replacement takes place. If the same type system is used in the conceptual and database model, then the same type is used.
9. A sequence is created from a sequence.The sequences are created in accordance with the create default.