WIP - Lower the datetime limit to what CH also accepts - 1900-01-01

[abdelhakimbendjabeur]

Summary

Removing the layer that performs whether a datetime is within a predefined range works fine.

On Postgres
created_datetime     |    sent_datetime    
---------------------+---------------------
 2022-11-10 13:39:35 | 2300-11-09 20:38:58
 
On CH
"created_datetime": "2022-11-10 13:39:35.000000"
"sent_datetime": "2299-12-31 23:38:58.000000"
 
 
PS. writeDateTime64 does not seem to be used anywhere

Checklist

Delete items not relevant to your PR:

• Unit and integration tests covering the common scenarios were added
• A human-readable description of the changes was provided to include in CHANGELOG
• For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

[zhicwu]

Thanks @abdelhakimbendjabeur for the pull request. I linked an issue whifh contains more information that you may want to check. Ideally, we probably should drop range check in Java client and only do that JDBC driver.

[den-crane]

https://clickhouse.com/docs/en/sql-reference/data-types/datetime64

Note: The precision of the maximum value is 8. If the maximum precision of 9 digits (nanoseconds) is used, the maximum supported value is 2262-04-11 23:47:16 in UTC.

[abdelhakimbendjabeur]

https://clickhouse.com/docs/en/sql-reference/data-types/datetime64

Note: The precision of the maximum value is 8. If the maximum precision of 9 digits (nanoseconds) is used, the maximum supported value is 2262-04-11 23:47:16 in UTC.

Hi @den-crane , in the docs it says the upper limit is 2299-12-31 23:59:59.99999999. I have some rows that could go up to this datetime

[den-crane]

@abdelhakimbendjabeur Note: The precision of the maximum value is 8.
I don't see a check of the precision in JAVA code.