-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Sharding not support ZoneDateTime #33660
Labels
Milestone
Comments
relative issue,here #27968 |
The CI are all broken, can you fix it? |
Ok, I wil fix it asap |
fyeeme
added a commit
to fyeeme/shardingsphere
that referenced
this issue
Nov 15, 2024
fyeeme
added a commit
to fyeeme/shardingsphere
that referenced
this issue
Nov 15, 2024
7 tasks
fyeeme
added a commit
to fyeeme/shardingsphere
that referenced
this issue
Nov 15, 2024
Well done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sharding not support ZoneDateTime
Which version of ShardingSphere did you use?
5.5.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
zoneDateTime can be parsed correctly
Actual behavior
The field was parsed as LocalDateTime, which subsequently caused a conversion exception.
Reason analyze (If you can)
org.apache.shardingsphere.infra.executor.sql.execute.result.query.impl.driver.jdbc.type.stream.JDBCStreamQueryResult#getValue
The type-specified resultSet.getObject supports parsing ZonedDateTime. However, in
org.apache.shardingsphere.infra.executor.sql.execute.result.query.impl.driver.jdbc.type.stream.JDBCStreamQueryResult#getValue
, the method’s last line calls return resultSet.getObject(columnIndex); without specifying a type, resulting in ZonedDateTime parsing not being applied.As a result, this method defaults to parsing database fields with dateTime types as LocalDateTime.
The text was updated successfully, but these errors were encountered: