-
Notifications
You must be signed in to change notification settings - Fork 537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DateTime/Date limits not compatible with CH server limits #1103
Comments
Thanks @subkanthi. And the upper limit is different when scale is 9 🤦 As to support limits across server versions, I'm not sure if it's worthy of doing that, but let me investigate once I completed refactoring. |
I can take a shot at fixing the MAX value if it's OK, recently have been looking at a lot of java datetime classes |
Thanks for helping, that'd be great! I'm refactoring *Value classes and data processors to better support unsigned types along with performance improvement of handling arrays and tuples. There's no conflict if the changes are mainly about Date & DateTime. |
There is no any issue with scale (8/9) for Date32 but DATE32_MIN and DATE32_MAX are out of supported by ClickHouse range [1900-01-01, 2299-12-31]. |
In Java 11, the nanosecond part is lost because of converting to
LocalDateTime
, maybe it should be kept asInstant
.Also the limits for DATETIME64 and DATE does not align with the latest CH server limits, is there a strategy to support limits that change across server versions?
Supported range of values: [1900-01-01 00:00:00, 2299-12-31 23:59:59.99999999]
https://clickhouse.com/docs/en/sql-reference/data-types/datetime64/
The text was updated successfully, but these errors were encountered: