View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001716 | SymmetricDS | New Feature | public | 2014-05-09 12:45 | 2022-08-05 19:55 |
| Reporter | Thomas.Weinhold@encontec.de | Assigned To | elong | ||
| Priority | low | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.5.20 | ||||
| Target Version | 3.12.6 | Fixed in Version | 3.12.6 | ||
| Summary | 0001716: Conflict detect collision of primary key and/or unique key | ||||
| Description | There is a use case, where next to the primary key another table column has to be unique at the replication target (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 collisions. Except from USE_OLD_DATA but this one compares the whole data row. | ||||
| Tags | conflict manager | ||||
|
|
This sounds like a great idea. We'll consider it for an upcoming release. |
|
|
Are there any plans to do implement this in the next releases ? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-05-09 12:45 | Thomas.Weinhold@encontec.de | New Issue | |
| 2014-07-08 00:08 | chenson | Note Added: 0000541 | |
| 2016-02-17 10:49 | Christian.Geiger | Note Added: 0000763 | |
| 2019-04-23 13:06 | elong | Tag Attached: conflict manager | |
| 2019-04-26 17:45 | elong | Summary | new collision detect_type (independent from primary key) => New collision detect_type USE_CUSTOM_COL |
| 2019-04-26 17:46 | elong | Relationship added | related to 0000780 |
| 2019-05-14 14:29 | josh-a-hicks | Priority | high => low |
| 2022-08-05 19:53 | elong | Relationship added | related to 0004743 |
| 2022-08-05 19:55 | elong | Assigned To | => elong |
| 2022-08-05 19:55 | elong | Status | new => closed |
| 2022-08-05 19:55 | elong | Resolution | open => fixed |
| 2022-08-05 19:55 | elong | Fixed in Version | => 3.12.18 |
| 2022-08-05 19:55 | elong | Target Version | => 3.12.18 |
| 2022-08-05 19:55 | elong | Summary | New collision detect_type USE_CUSTOM_COL => Conflict detect collision of primary key and/or unique key |
| 2022-08-05 19:55 | elong | Description Updated | View Revisions |