MENU
An editor performs a field calculation on 500,000 records of a traditional versioned feature class while connected to a child version of Default. In the meantime, the Default version is updated by another editor. The child version is then reconciled with Default.
What will happen to the 500,000 updated records during the reconcile?
Scenario Overview:
An editor updates 500,000 records in a child version of the Default version using a field calculation.
Another editor updates the Default version, and the child version is reconciled with Default.
What Happens During Reconciliation?
In traditional versioning, edits to feature classes are stored in the Adds and Deletes tables.
During reconciliation:
Changes in the child version that differ from the Default version are duplicated in the Adds and Deletes tables to track the differences.
This allows conflicts to be detected and resolved while preserving all edits. (ArcGIS Documentation: Traditional Versioning Workflow)
Alternative Options:
Option B: They will be migrated to the Base table
Migration to the base table occurs only when changes are posted and the geodatabase is compressed.
Option C: They will be removed from the States repository table
The States repository table tracks state transitions and is unaffected during reconciliation.
Thus, during reconciliation, the 500,000 records are duplicated in the Adds and Deletes tables to manage and detect conflicts.
Currently there are no comments in this discussion, be the first to comment!