Manage timestamp infinity values for others databases [DBZ-8033]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-8033](https://issues.redhat.com/browse/DBZ-8033)
With https://issues.redhat.com/browse/DBZ-7920 the PostgreSQL *-+infinity* values has been managed and translated to the equivalent values in the other databases based on the following
|Vendor|-INFINITY|+INFINITY|
|Oracle|`-4712-01-01T00:00:00+00:00`|`9999-12-31T23:59:59+00:00`|
|MySQL|`1970-01-01T00:00:01+00:00`|`2038-01-19T03:14:07+00:00`|
|SQL Server/Db2|`0001/01/01 00:00:00`|`9999/12/31 23:59:59`|
With this task we want to the opposite. For example the Oracle *-infinity* value is not supported value for PostgreSQL and also for MySQL.
So the general idea is when a value represented in the above table arrives the sink connector should convert it to the correct value based on the destination.
Contributor guide
Assessment
This issue has not been assessed yet.