lidavidm opened a new issue, #732:
URL: https://github.com/apache/arrow-java/issues/732
### Describe the enhancement requested
I believe the JDBC driver is handling
timezones/timestamps/java.sql.Timestamp entirely incorrectly.
- Timestamps are round-tripped through LocalDateTime always. I believe this
is wrong for timestamps with timezones: we should not round trip through a wall
clock time since the same wall clock time may correspond to multiple different
instants (during a DST transition)
- From experimenting with the PostgreSQL JDBC driver, it appears that when
requesting a java.sql.Timestamp, the expected behavior is:
- Naive timestamp: return a Timestamp that appears to have the right wall
clock time in the given Calendar, or the system time zone if no calendar is
supplied. (In other words, use Timestamp as a janky LocalDateTime.)
- Zoned timestamp: return a Timestamp whose value is the timestamp in UTC.
(In other words, use Timestamp as an Instant.)
It appears our driver does not do this properly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@arrow.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
