| Column Name | Description | Datatype | Length | Allow Nulls | Default | Formula | |
|---|---|---|---|---|---|---|---|
| ESTR_RELATION_NAME | The name of the relation. The format is <entity>to<entity><relation description>. For example, requirementToAttachmentAttachment, requirementToRequirementContainment, and so on. This name is not unique. Different subtypes may have the same relationship. For example, the relation requirementToRequirementContainment where a folder subtype is the source can have several instances with different subtypes of requirement on the target side. The ID of the subtype-subtype pair. | varchar | 80 | ||||
| ESTR_SOURCE_SUBTYPE_ID | Either "*", for all the subtypes of the source entity, or the ENTITY_SUBTYPES.EST_ID of the subtype. | varchar | 100 | ||||
| ESTR_TARGET_SUBTYPE_ID | Either "*", for all the subtypes of the target entity, or the ENTITY_SUBTYPES.EST_ID of the subtype. | varchar | 100 | ||||
| ESTR_STATUS | ON if this relation exists, or OFF if there is no relation between the two subtypes. | varchar | 10 | ||||
| ESTR_IS_DEFAULT | IF Y, this is the default relation among the relations between the subtypes of the entities. For example, a TEST of subtype QTP can be associated with RUNs of subtypes QTP and MANUAL. If the relation between the QTP subtype of a TEST and the QTP subtype of a Run is the default, then when a QTP TEST's RUN is created, it will be of subtype QTP unless set otherwise. | varchar | 1 |  |
| Index | Description | Primary | Unique |
|---|---|---|---|
| ESTR_RELATION_IDX | |