The custom split policy for handling relationships.
[Visual Basic .NET] Public Function get_CustomSplitPolicyForRelationship ( _ ByVal Row As IRow, _ ByVal relClass As IRelationshipClass _ ) As esriRelationshipSplitPolicy
[C#] public esriRelationshipSplitPolicy get_CustomSplitPolicyForRelationship ( IRow Row, IRelationshipClass relClass );
[C++]
HRESULT get_CustomSplitPolicyForRelationship(
IRow* Row,
IRelationshipClass* relClass,
esriRelationshipSplitPolicy* policy
);
[C++]Parameters
Row [in]Row is a parameter of type IRow
relClass [in]relClass is a parameter of type IRelationshipClass
policy [out, retval]policy is a parameter of type esriRelationshipSplitPolicy
Product Availability
Remarks
When a Feature with related objects is split, the geodatabase will modify the relationships based on the type (simple or composite) and cardinality of the relationship.
If the default behavior is not appropriate for a class, return True for the HasCustomSplitPolicy method. Through the CustomSplitPolicyForRelationship property, a custom split policy can be specified according to subtype and relationship. The support split policies are defined in the esriRelationshipSplitPolicy enumeration and described below:
esriRSPUseDefault: The default behavior, which is esriRSPPreserveOnLargest for simple relationships and esriRSPDeleteParts for composite relationships.
esriRSPPreserveOnLargest: Preserve related objects and create a relationship with the Feature with the largest part of the split geometry.
esriRSPPreserveOnSmallest: Preserve related objects and create a relationship with the Feature with the smallest part of the split geometry.
esriRSPPreserveOnAll: Preserve related objects and create a relationship with both Features. This option is not valid with relationships with 1..1 cardinality or composite relationships.
esriRSPDeleteRelationship: Delete the relationship.
esriRSPDeleteParts: Delete the related Objects.
See Also
IFeatureClassEdit Interface | IClassExtension Interface | IRelationshipClass Interface