View Revisions: Issue #3438
| Summary | 0003438: Provide parameter to pass Oracle's DATE field's time part over to target database by mapping to a timestamp instead of just DATE | ||
|---|---|---|---|
| Revision | 2018-02-21 11:42 by zulus | ||
| Description | Oracle date field can (and often) contain time part, unfortunately SymmetricDS transform it to postgresql date field and "time" part is lost, also after sync-schema. |
||
| Revision | 2018-10-17 18:26 by hanes | ||
| Description | Oracle's DATE field per documentation is just a date, but in practice can contain time information. Provide a new parameter to control whether the field should be treated as just a DATE (as currently is the case) or whether to treat it as date and time. Original Bug Description: Oracle date field can (and often) contain time part, unfortunately SymmetricDS transform it to postgresql date field and "time" part is lost, also after sync-schema. |
||