Since VP-UML supports schema, users can make use of model to manage database. Users can develop ERDs under models, thereby, entities in different models can share the same name, but different schema. This page will demonstrate how to create model, how to create ERD under model and then how to apply schema.
By pinning, users can read those specification window of various model elements consecutively, no longer have to close the previous specification window and open new specification dialog box repeatedly. Reading the specification window of different entities in ERD now becomes an easy task.
When you reverse database, you will find all existing entities are overwritten in the project. This article is going to teach you how to solve this problem.
When defining class model for your persistent layer, a class is defined as part of the static data model instead of controller or user interface items. And the class is directly mapped to table(s) in your database. As the class is mapped to tables, its attributes is also mapped to columns in table. In order to make the mapping work, you have to model attributes with primitive types like integer, boolean, String, etc. You cannot model the attribute as any other types which are not compatible with database.
To overcome this, you can make use of ORM User Type to define customized datatype for attributes, and persistent its value into database. This article will teach you how to use ORM User Type. Read more
The reverse database tool of VP-UML provides a handy approach to instantly convert a relational database into an ERD, to aid in the studying of database structure, entities properties and their inter-relationships.
Being able to study a database with an ERD is great because ERD is so easy to read and understand. However, the relationships among entities may increase the complexity of diagram when there are many entities and are highly coupled. If you just want to focus on seeing the database tables and their columns, but not pretty much interested in their inter-relationship, you can optionally form an ERD database diagram with solely entities, without including their relationships. In this article, you will see how to form an ERD from a MS SQL database, with just entities showing in the diagram. You will also learn how to optionally show the relationships.
Visual Paradigm for UML (VP-UML) comes with an ERD database designer where database developers can model physical database with Entity Relationship Diagram. The database designer supports popular database constructs like database table (called Entity in VP-UML), View, Sequence, Stored Procedure, Trigger, etc, supporting the need of database modeling for any kind of database management systems.
