[ https://issues.apache.org/jira/browse/IGNITE-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114538#comment-16114538 ]
Taras Ledkov commented on IGNITE-5384: -------------------------------------- Looks like we must not implement date conversion explicitly because Ignite store a date as {{long millis}} gathered from {{Date}}. For all methods of the {{ResultSet}} that contain Calendar to convert JDBC javadoc says: {quote} This method uses the given calendar to construct an appropriate millisecond value for the date if the underlying database does not store timezone information. {quote} So, Ignite store timezone information because the UTC milliseconds are stored. [~vozerov], please provide your thoughts. > JDBC Driver: implement ResultSet#getDate(int, Calendar) > ------------------------------------------------------- > > Key: IGNITE-5384 > URL: https://issues.apache.org/jira/browse/IGNITE-5384 > Project: Ignite > Issue Type: Task > Components: jdbc > Affects Versions: 2.1 > Reporter: Taras Ledkov > Assignee: Taras Ledkov > Fix For: 2.2 > > > Current implementation doesn't use Calendar object to convert the date. -- This message was sent by Atlassian JIRA (v6.4.14#64029)