The system table TB_RELATIONS table stores relations between feature classes. For example, you can define relations when you add an attribute to a feature class, using the Data model administrator.
|
Attributes of TB_RELATIONS |
Description |
|
ID |
Stores the unique key, which is system-generated. |
|
PARENT_TABLE_NAME |
Stores the name of the parent table, for example a domain table *_TDB. Domain tables usually are parent tables. |
|
PARENT_COLUMN_NAME |
Stores the parent attribute name. Example:
|
|
CHILD_TABLE_NAME |
Stores the name of the child table, for example a label feature class table. |
|
CHILD_COLUMN_NAME |
Stores the name of the child attribute. Example:
|
|
DELETE_CHILD |
Specifies whether the child feature is deleted when the parent feature is deleted. N—Set Relation to Parent to NULL when Parent is deleted. Default. L—Do not alter child when parent is deleted. D—Delete Feature when Parent is Deleted. C—Don't delete Feature when a parent exists. P—Don't delete Feature when a child exists. |
|
CREATE_CHILD |
Specifies whether a child feature is created. Either 1 = Yes or 0 = No. Default = 0. |
|
SPLIT_MODE |
Specifies the handling of related child features when splitting features. NULL—Split acts like a Delete. S—Duplicate Children. A—Assign Children. |
|
MERGE_MODE |
Specifies the handling of related child features when joining features. NULL—Merge acts like a Delete. I—Join Children If Identical. M—Join Children. K—Keep All Children. |
|
ACTIVE |
Specifies that the record is active. Either 1 = Yes or 0 = No. Default = 1. |