When a relationship class is built between a feature class in one dataset and a featureclass in another dataset and the first dataset is unregistered as versioned, the second dataset also becomes unregistered without warning.
上次发布: August 25, 2014No Product Found
漏洞 ID 编号
NIM012874
已提交
November 5, 2007
上次修改时间
April 2, 2025
适用范围
No Product Found
找到的版本
9.2
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
We apologize that we were unable to address this issue within the current product support cycle. If the issue continues to affect your work in a supported release, please contact Technical Support.
解决办法
If Unregister as Versioned is called on the relationship class the destination will also be unregistered as versioned. In this workflow Unregister as Versioned command is being executed on a feature dataset with both the origin feature class and the relationship class in it. That means that RegisterAsVersioned(False) will be called on both objects resulting in the destination feature class (in another feature dataset) being unregistered as versioned. It is the user’s responsibility to understand relationships within their data model.