Meta Data Services Programming
RTblRelshipDefs SQL Table
RTblRelshipDefs stores persistent properties associated with relationship definitions defined in the repository database.
| Column name | Data type | Description |
|---|---|---|
| IntID | RTIntID | The internal identifier for the relationship definition object. |
| Z_BranchID_Z | RTBrID | The branch identifier for repository API versioning. It is reserved for proprietary use by the repository engine. The value of this column is always zero. |
| Z_VS_Z | RTVerID | An identifier for repository API versioning. It is reserved for proprietary use by the repository engine. The value of this column is always zero. |
| Z_VE_Z | RTVerID | An identifier for repository API versioning. It is reserved for proprietary use by the repository engine. The value of this column is always VERINFINITY. |
| ViewFlags | Integer, 4 bytes |
A set of flags that determine the view generation behavior for relationship definitions. The maximum length for this value is 4 bytes. For more information about flag values, see ViewFlags Property. |
| ColumnNamePrefix | Varchar, 118 bytes |
A string prefixed to the column name NAME, PrevDstID, and RelTypeID. The string is used in all views where the corresponding columns appear. The maximum length for this value is 118 bytes. |
| JunctionViewName | Varchar, 128 bytes |
Specifies a user-defined view name for an SQL view based on the relationship. View generation is supported on Microsoft® SQL Server™ 2000 databases only. The maximum length for this value is 128 bytes. For more information, see IViewRelationshipDef Interface. |
Remarks
The RTblRelshipDefs table stores values that direct view generation behavior for relationship definitions and indicate whether to create a junction-table view of a relationship. Another SQL table stores relationship instance data. For more information, see RTblRelships SQL Table.
The primary key for this table is formed from the IntID, Z_BranchID_Z, and Z_VS_Z columns.
Z_BranchID_Z, Z_VS_Z, and Z_VE_Z are included to provide future support for versioning repository API definitions in case more than one version of this repository API structure is created.