Use the General tab in the Relationships Editor in the physical model to specify the properties of a relationship such as its constraint name, cardinality, type, and null options.
Note: The options described are available for all relationships in a physical model. However, some target databases can have additional physical properties that you can specify. For more information about using these properties, see your vendor's SQL documentation.
To specify physical properties for a relationship
The Relationships Editor opens.
Lets you enter or edit the foreign key constraint name for the parent-to-child and child-to-parent relationship.
Note: For Logical/Physical models, you can click the Reset button to inherit the constraint name from the logical name. If you delete the text from the Foreign Key Constraint Name field, the constraint name is set to an empty string.
Specifies the parent of the selected relationship. This column is read-only.
Specifies the child of the selected relationship. This column is read-only.
Lets you specify whether or not the relationship should display in the physical model only. Select this check box if you want the relationship to appear in the physical model only. Clear this check box if you want the relationship to appear in both the physical and logical model. Physical-only relationships do not appear when you switch to the logical model, but the parent table's primary key still migrates as a foreign key to the child table.
Specifies to use the preferences selected in the Relationship Editor when DDL is generated during Forward Engineering. Select the check box to enable this option.
Specifies the type of the relationship. Select from the drop-down list; valid values are Identifying and Non-identifying.
Specifies whether null values are allowed for non-identifying relationships.
Specifies the physical name of the object. This field appears only when you are working with a physical model. You can choose to inherit, override, or harden the name.
Lets you specify the cardinality for the relationship. Select one of the following options:
Zero, One or More
Specifies that each parent table is connected to zero, one, or more instances of the child table.
One or More (P)
Specifies that each parent table is connected to one or more instances of the child table.
Zero or One (Z)
Specifies that each parent table is connected to zero or one instance of the child table.
Specifies the exact number of child entity instances that each parent entity is connected to. Enter an integer.
Physical properties are specified for the relationship and the Relationship Editor closes.
Note: Other tasks you can perform in the Relationship Editor include entering a comment, defining rolenames for migrated keys, and defining referential integrity trigger actions.
Copyright © 2017 erwin Inc.
All rights reserved.
|
|