View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004116 | SymmetricDS | Bug | public | 2019-10-18 10:36 | 2019-11-14 14:49 |
| Reporter | hanes | Assigned To | |||
| Priority | normal | ||||
| Status | confirmed | Resolution | open | ||
| Product Version | 3.11.0 | ||||
| Target Version | 3.12.0 | Fixed in Version | |||
| Summary | 0004116: Syncing from Time to Timestamp (or vice versa) in Postgres produced inaccurate values | ||||
| Description | For Postgres, when syncing from a Time column to a Timestamp column (or vice versa), the time amount is not the correct value. Perhaps it's an incorrect interpretation of the microseconds when doing the conversion? Time to Time, and Timestamp to Timestamp seem to work okay. | ||||
| Tags | dialect: postgresql | ||||
|
|
Note that the CSV being sent seems to be correct. For example: insert,"foo6","2019-10-18 10:29:32.307966" for the timestamp on the source case, and insert,"foo5","10:28:03.074378" for the time on the source case. FYI, for the Time to Timestamp case, the date portion of the timestamp defaults to 1/1/1970, which seems reasonable (since the time is unknown) |
|
|
Issues appears to occur with initial load, as well. |
|
|
This scenario with an H2 source and target works just fine. In fact, H2 as a source and Postgres as a target works as well. However, Postgres as a source and H2 as a target doesn't work. My guess is it has something to do with the six digit "microsecond" value postgres seems to use. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-10-18 10:36 | hanes | New Issue | |
| 2019-10-18 10:36 | hanes | Tag Attached: dialect: postgresql | |
| 2019-10-18 10:36 | hanes | Status | new => confirmed |
| 2019-10-18 10:38 | hanes | Note Added: 0001617 | |
| 2019-10-18 10:39 | hanes | Note Added: 0001618 | |
| 2019-10-18 11:03 | hanes | Note Added: 0001619 | |
| 2019-11-14 14:49 | elong | Target Version | 3.11.0 => 3.12.0 |