| Numéro d’ID de bogue |
BUG-000131226 |
| Envoi | May 28, 2020 |
| Dernière modification | December 13, 2024 |
| S’applique à | ArcSDE/Enterprise Geodatabase |
| Version trouvée | N/A |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | N/A |
| Statut | Will Not Be Addressed
L’équipe de développement a examiné le problème ou la demande et a décidé qu’ils ne seraient pas traités. Pour d’autres explications, reportez-vous à la section Informations supplémentaires correspondant au problème.
|
Informations supplémentaires
Editing feature classes through a versioned view in the geodatabase functionality such a relationship class is an unsupported workflow. This is documented at the link below:
What type of data can be edited using SQL
https://desktop.arcgis.com/en/arcmap/10.4/manage-data/using-sql-with-gdbs/what-type-of-data-can-be-edited-using-sql.htm
To add more context, editing feature classes through a versioned view in relationship classes does not maintain referential integrity. For example, using ArcGIS Desktop or ArcGIS Pro, the foreign key in the destination object is set to null when it's origin object is deleted, editing through the versioned view does not. Therefore, unexpected behavior is seen while generating conflicts.
Solution de contournement
The issue is not reproducible when the primary key field and foreign key field of the relationship class are set in two different fields.
Étapes pour reproduire