View Issue Details

IDProjectCategoryView StatusLast Update
0001716SymmetricDSNew Featurepublic2019-05-14 10:29
ReporterThomas.Weinhold@encontec.deAssigned To 
Status newResolutionopen 
Product Version3.5.20 
Target VersionFixed in Version 
Summary0001716: New collision detect_type USE_CUSTOM_COL
DescriptionThere is a use case, where next to the primary key another table column has to be unique at the replication tagret (eg. a unique secondary key). A collision of an insert into the target table with a non-existing PK and an already existing SK is not possible to detect.

Actual detect_types use always the primary key to detect collsions. Except from USE_OLD_DATA but this one compares the whole data row.

Maybe a detect_type "USE_CUSTOM_COL" would be great to detect confilcts at custom table columns (independant from PK).
Tagsconflict manager


related to 0000780 new Allow specific columns to be chosen with the USE_OLD_DATA conflict detection option 



2014-07-07 20:08

administrator   ~0000541

This sounds like a great idea. We'll consider it for an upcoming release.


2016-02-17 05:49

reporter   ~0000763

Are there any plans to do implement this in the next releases ?

Issue History

Date Modified Username Field Change
2014-05-09 08:45 New Issue
2014-07-07 20:08 chenson Note Added: 0000541
2016-02-17 05:49 Christian.Geiger Note Added: 0000763
2019-04-23 09:06 elong Tag Attached: conflict manager
2019-04-26 13:45 elong Summary new collision detect_type (independent from primary key) => New collision detect_type USE_CUSTOM_COL
2019-04-26 13:46 elong Relationship added related to 0000780
2019-05-14 10:29 josh-a-hicks Priority high => low