View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001241 | SymmetricDS | Bug | public | 2013-05-24 07:12 | 2023-09-13 17:25 |
| Reporter | vinhvo | Assigned To | josh-a-hicks | ||
| Priority | high | ||||
| Status | closed | Resolution | open | ||
| Product Version | 3.4.4 | ||||
| Summary | 0001241: Timestamp with timezone for Conflict resolution NEWER_WIN does not work | ||||
| Description | I have oracle and postgres nodes. When I use column "Timestamp with timezone" to do newer_win, oracle always wins. When I change column to "Timestamp", newer_win works correctly. So there is bug in comparing "Timestamp with timezone" between Postgres and Oracle. | ||||
| Tags | conflict manager | ||||
|
|
I tested this using SymmetricDS 3.14.0, Postgres 13.6, and Oracle 21.3. The comparison was successful and the Postgres row won when the timestamp was newer. It's likely that this issue has already been resolved since 3.4.4. Can you upgrade to the latest version of SymmetricDS and see if you still encounter this issue? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-05-24 07:12 | vinhvo | New Issue | |
| 2013-06-08 15:04 | chenson | Target Version | => 3.6.0 |
| 2014-03-03 14:53 | chenson | Assigned To | => abrougher |
| 2014-03-03 14:53 | chenson | Status | new => assigned |
| 2014-04-18 17:01 | chenson | Assigned To | abrougher => |
| 2014-04-18 17:01 | chenson | Target Version | 3.6.0 => 3.7.0 |
| 2014-12-10 14:59 | chenson | Assigned To | => josh-a-hicks |
| 2015-01-05 19:06 | chenson | Target Version | 3.7.0 => |
| 2019-04-23 12:36 | elong | Tag Attached: conflict manager | |
| 2022-08-09 20:27 | emiller | Note Added: 0002149 | |
| 2022-08-09 20:27 | emiller | Status | assigned => feedback |
| 2023-09-13 17:25 | emiller | Status | feedback => closed |