Each relationship in the Repository is associated with two relationship collections: an origin collection and a destination collection. Each relationship collection conforms to a collection type (also referred to as a collection definition). The collection type defines the role that the collection plays in the relationship. This SQL table contains one row for each collection type that is defined in the Repository. The IntID, Z_BranchID_Z, and Z_VS_Z columns form the primary key for this table. A non-unique index is defined for the RelTypeID column.
| Column Name | Data Type | Description |
| IntID | RTIntID | The internal identifier for the collection definition object. |
| Z_BranchID_Z | RTBrID | The value of this column is always zero. |
| Z_VS_Z | RTVerID | The value of this column is always zero. |
| Z_VE_Z | RTVerID | The value of this column is always VERINFINITY. |
| RelTypeID | RTIntID | Internal identifier of the relationship definition object. |
| Flags | RTFlags | Flags that determine the behavior of collections that conform to this collection type. See CollectionDefFlags for a list of values and their specific purposes. |
| MinCount | RTCount | The minimum number of Repository items that are expected for this type of collection. This field can be null. |
| MaxCount | RTCount | The maximum number of Repository items that are expected for this type of collection. This field can be null. |
| IsOrigin | RTBoolean | Determines whether or not collections that conform to this collection type are origin collections (True), or destination collections (False). |
Remarks
Remember that you can make only one version of each Relationship Collection Type. Nevertheless, this table includes the columns Z_BranchID_Z, Z_VS_Z, and Z_VE_Z because there are implementation advantages to including these columns. Similarly, the primary key includes the columns Z_BranchID_Z and Z_VS_Z for implementation reasons only.