An object that defines information about the relationship between tables. A relationship consists of two and only two tables, each having one of these roles in the relationship:
Origin table, sometimes referred to as the source table or original table.
One table must have one of these roles and the other table must have the other role. A table can participate in more than one relationship. Further, a table may be an origin table in one relationship and also a destination table in another relationship. The relationship's cardinality describes whether features in a table are related to only one feature in the other table, or whether a feature may be related to multiple features. In a simple relationship, the features in the participating tables can exist without the other. For example, a transformer and an electric pole may be related but one's existence does not depend on the other. Deleting the origin features will simply disassociate the destination features from the origin features. In a composite relationship, the destination features cannot exist without the origin features. When the origin feature is deleted, the related destination feature is deleted as well. This is called a cascade delete. This dependency also means that each destination feature must be linked to a counterpart origin feature.
Whether this is a composite relationship. In a composite relationship, a feature in the destination table must always be associated with an origin feature. Orphan features in the destination tables are not permitted. Therefore, destination table features will be deleted when their associated origin table features are deleted (this is called a cascade delete).