View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004261 | SymmetricDS | Bug | public | 2020-01-23 17:27 | 2020-04-21 14:51 |
| Reporter | pmarzullo | Assigned To | |||
| Priority | normal | ||||
| Status | new | Resolution | open | ||
| Product Version | 3.11.5 | ||||
| Summary | 0004261: Oracle: Need to handle negative years or BC years | ||||
| Description | Oracle dialect needs to handle negative years, or BC years. Conversion from timestamp to char for transport to target system: select to_char(to_timestamp('-3546-02-13 12:00:00','SYYYY-MM-DD HH24:MI:SS'), 'SYYYY-MM-DD HH24:MI:SS') from dual; select to_char(to_timestamp('-3546-02-13 12:00:00','SYYYY-MM-DD HH24:MI:SS'), 'YYYY-MM-DD HH24:MI:SS AD') from dual; select to_char(to_timestamp('3546-02-13 12:00:00 BC','YYYY-MM-DD HH24:MI:SS BC'), 'SYYYY-MM-DD HH24:MI:SS') from dual; select to_char(to_timestamp('3546-02-13 12:00:00 BC','YYYY-MM-DD HH24:MI:SS BC'), 'YYYY-MM-DD HH24:MI:SS AD') from dual; The SYYYY means signed years. The AD indicates BC or AD as appropriate. I would suggest going with SYYYY on parsing and formatting. DBCompare also needs to be looked at, since milliseconds since EPOCH is used for comparison, and this negative date does not make sense in that context. | ||||
| Tags | data conversion, dbcompare, dialect: oracle | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-01-23 17:27 | pmarzullo | New Issue | |
| 2020-01-23 17:27 | pmarzullo | Tag Attached: data conversion | |
| 2020-01-23 17:27 | pmarzullo | Tag Attached: dialect: oracle | |
| 2020-01-23 17:30 | pmarzullo | Description Updated | View Revisions |
| 2020-01-23 17:31 | pmarzullo | Tag Attached: dbcompare | |
| 2020-02-14 13:10 | elong | Target Version | 3.11.5 => 3.11.6 |
| 2020-03-04 18:15 | chenson | Target Version | 3.11.6 => 3.11.7 |
| 2020-03-16 20:14 | admin | Target Version | 3.11.7 => 3.11.8 |
| 2020-04-21 14:51 | elong | Target Version | 3.11.8 => |