solidDB Help : Replication : C Replicator : Managing replication : Conflict resolution
  
Conflict resolution
Conflict resolution defines how the replicator should resolve possible data conflicts. The following options are possible:
▪ keep the target version of the conflicting rows,
▪ remove conflicting target rows, and insert source rows,
▪ ignore row delete errors when the row does not exist in the target database, in this case only conflicting data is ignored, the rest of the transaction is executed,
▪ roll back the whole transaction in the target database,
▪ abort the subscription (default) and stop replicating from the source database until the administrator manually resolves the conflict and restarts the replication.
The following table describes what happens in the target table for each type of action that causes conflicts, depending on the conflict resolution method (target wins, source wins, ignore, abort):
 
Action that causes conflict
Target wins
Source wins
Ignore
Abort
DELETE
deleted row not present
Nothing
Nothing
Nothing
Replication stops
INSERT
primary or unique index conflict
Nothing
Conflicting rows are deleted and replaced by rows from source database.
Nothing
Replication stops.
UPDATE
original row not present
New row inserted.
New row inserted.
Nothing
Replication stops.
UPDATE
new row primary or unique key conflict
Nothing
Conflicting rows are deleted and replaced by rows from source database.
Nothing
Replication stops.
DELETE
foreign key check violation
Nothing
Conflicting row is deleted, and rows (linked by foreign key to conflicting row) in first level child tables are deleted. However, if the deletion of rows in the child table would cause a foreign key violation in a second level of tables, replication stops.
Nothing
Replication stops.
See also CREP Monitoring and diagnostics.