Examples¶
The following scenario provides an example of why it is important to enable the uniqueness detection feature:
Uniqueness detection is enabled.
John works on the database
DB1and Scott on the databaseDB2.Both databases are linked to the same database in the VCS repository.
Both databases are currently in the same state and contain the following elements:
A folder named
F1.A folder named
F2.A data source named
DS1located insideF1.A view named
V1also located insideF1.
All the elements are up-to-date and without local modifications.
John moves
V1toF2and checks in the changes.Scott modifies
V1and checks in the changes.Virtual DataPort detects a uniqueness conflict between the different versions of
V1: one located inF1with local changes and the remote version which is currently located inF2.Scott forces the check-in, so
V1is now located inF1again and contains its own changes.
John modifies
V1, which in his database -DB1- still is in the folderF2, and checks out the database.Virtual DataPort detects a uniqueness conflict between the different versions of
V1: one located inF2with local changes and the remote version which is currently located inF1.John forces the check-out, so
V1is now located inF1and contains the changes corresponding to Scott’s previous check-in (John agreed to lose his local changes after forcing the check-out).
Note
In step 3, Virtual DataPort detects a movement and requires John to confirm the check-in, even if this movement is safe. Currently, this is a known limitation of the uniqueness detection feature: all movements of elements require explicit confirmation when checking in the changes.
