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.