This type of conflict happens when CDV tries to perform an Insert operation on a record which already exists in the database. You can resolve this type of conflict in any of the following ways:
This type of conflict happens when CDV tries to perform an Delete or Update operation on a record which does not exist in the database. You can resolve this type of conflict in any of the following ways:
This type of conflict happens when CDV tries to perform an Update operation on a record whose value has already changed in the database. You can resolve this type of conflict in any of the following ways:
Below is a sample <Audit> element entry from the ydkversionexport.xml file:
<Audit AuditKey="20081219134644594514" Operation="Insert"
TableKey="20081219134644594512" TableName="YFS_QUEUE_SUBSCRIPTION">
<AuditDetail AuditType="QueueSubscription">
<IDs>
<ID DataType="class java.lang.String" Name="QueueKey"
Value="20081110160649488514"/>
</IDs>
<Attributes>
<Attribute DataType="class com.yantra.yfc.date.YTimestamp"
Name="Createts" NewValue="20081219134644"/>
<Attribute DataType="class com.yantra.yfc.date.YTimestamp"
Name="Modifyts" NewValue="20081219134644"/>
<Attribute DataType="class java.lang.String" Name="UserKey"
NewValue="20051121111734438480"/>
</Attributes>
</AuditDetail>
<Conflict ConflictDescription="Record already exists"
ConflictType="RECORD_ALREADY_EXISTS">
<ConflictAttribute ExpectedOldValue=""
FoundOldValue="20081219134644594512"
Name="QueueSubscriptionKey" NewValue="20081219134644594512"/>
<ConflictAttribute ExpectedOldValue="" FoundOldValue=""
Name="Createts" NewValue="2008-12-19T13:46:44+00:00"/>
<ConflictAttribute ExpectedOldValue="" FoundOldValue=""
Name="Modifyts" NewValue="2008-12-19T13:46:44+00:00"/>
</Conflict>
</Audit>