Can't parse timestamp with large date about greptimedb HOT 4 CLOSED

As for large Date values, we support expanded ISO8601 timestamo format like +99999-01-01 00:00:01, but these values may cause arithmetic overflows. Is there any particular cases where large timestamp is required?

from greptimedb.

As for large Date values, we support expanded ISO8601 timestamo format like +99999-01-01 00:00:01, but these values may cause arithmetic overflows. Is there any particular cases where large timestamp is required?

I just migrated the tests from duckdb and found this issue #2073

from greptimedb.

When executing SQL SELECT TIMESTAMP '100000-01-01 00:00:01.5'::VARCHAR, the conversion from string to timestamp seems to happen inside datafusion. Maybe we should find a way to hook that conversion with Timestamp::from_str so that large timestamp strings can be parsed properly.

from greptimedb.

Lots of duckdb tests contain such cases, for example

https://github.com/duckdb/duckdb/blob/master/test/sql/types/timestamp/timestamp_limits.test

If we can support it, it would be great.

from greptimedb.