View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003724 | SymmetricDS | Bug | public | 2018-09-14 15:15 | 2022-08-05 19:33 |
Reporter | josh-a-hicks | Assigned To | elong | ||
Priority | low | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.9.0 | ||||
Target Version | 3.14.0 | Fixed in Version | 3.14.0 | ||
Summary | 0003724: Conflict detection with Timestamps between DB2 and Derby | ||||
Description | Conflict detection is firing on timestamp columns while syncing from Derby to DB2 even if the values appear to match. It could be caused by the precision of the timestamps being compared and each have different formats. | ||||
Tags | conflict manager | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2018-09-14 15:15 | josh-a-hicks | New Issue | |
2018-10-03 21:07 | mmichalek | Target Version | 3.9.14 => 3.9.15 |
2018-10-25 19:17 | hanes | Target Version | 3.9.15 => 3.10.0 |
2018-10-29 17:02 | hanes | Priority | normal => low |
2018-11-16 13:12 | hanes | Status | new => acknowledged |
2019-03-14 12:39 | admin | Target Version | 3.10.0 => 3.10.1 |
2019-04-23 13:46 | elong | Target Version | 3.10.1 => 3.10.2 |
2019-04-24 18:56 | elong | Tag Attached: conflict manager | |
2019-05-08 12:51 | admin | Target Version | 3.10.2 => 3.10.3 |
2019-06-13 18:23 | elong | Target Version | 3.10.3 => |
2022-08-05 19:33 | elong | Relationship added | related to 0005239 |
2022-08-05 19:33 | elong | Assigned To | => elong |
2022-08-05 19:33 | elong | Status | acknowledged => closed |
2022-08-05 19:33 | elong | Resolution | open => fixed |
2022-08-05 19:33 | elong | Fixed in Version | => 3.14.1 |
2022-08-05 19:33 | elong | Target Version | => 3.14.1 |