Toad Data Modeler allows you to design Entity Relationship Diagrams of specific database platforms, convert physical model from one database platform to another, create an ER Diagram directly from your database (Reverse Engineering feature), update physical models, generate DDL/SQL scripts and Change Scripts, create Dictionary Types, Views, Triggers, Functions, generate detailed documentation to your model (in HTML, RTF, PDF, XSLT formats) and much more.
This chapter describes features and functions related to Physical Data Modeling. Look around each section to get the information you need.
|
Note: See the sample physical model Videorental (Oracle 10g db) that is included in the installation package of Toad Data Modeler. Default location is: C:\Program Files (x86)\Quest Software\Toad Data Modeler6.4\Samples. |
One-to-many relationship is represented by this symbol:
One-to-one relationship is represented by this symbol:
Parent: mandatory Child: mandatory
Parent: mandatory Child: optional
Parent: optional Child: mandatory
Parent: optional Child: optional
,
,
zero, one or more
one or more
zero or one
Parent: mandatory Child: mandatory
Parent: mandatory Child: optional
Parent: optional Child: mandatory
Parent: optional Child: optional
See Synchronization of Not Null and Mandatory Parent for more information.
Toad Data Modeler supports the following relationship types (physical model):
Primary key migrates from parent entity to child entity and there becomes a part of the primary key. It is used when the primary key of the child entity is unable to provide definite identification.
An entity, connected with a parent entity through an identifying relationship, is called "dependent" entity and is shown in a model with rounded corners.
The Order Record entity cannot exist itself. It is dependent on entities Customer and Film. Therefore the Identifying relationship is used. The Order Record entity is a dependent entity, and the Customer ID and Movie ID items are its unique record identifiers.
Primary key migrates from parent entity to child entity and does not become a part of the primary key. Non-identifying relationships are represented by dashed lines. In the dependent table, the attribute is referred to as a foreign key.
The Film ID as the unique identifier for Film is sufficient. Therefore the non-identifying relationship is used. The Genre ID is only a foreign key. The film can exist without being assigned to a genre, therefore the Film entity is an Independent entity.
Identifying relationship (also CTRL+R)
Non-identifying relationship
M:N relationship
|
TIP: Hide relationship names:
|
To create self-relationship for non-identifying relationship
|
TIP: Before you create a self-relationship, select Settings | Options | Physical Model | Self Relation Attribute Name/Caption and define a name for propagated attributes there (e.g. via prefix, suffix, application variable.) |
To add multiple relationships
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy