You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2020/07/09 09:26:00 UTC

[jira] [Created] (IGNITE-13233) Invalid milliseconds value of java.util.Date converted to java.sql.Timestamp via JDBC Thin.

Alexander Lapin created IGNITE-13233:
----------------------------------------

             Summary: Invalid milliseconds value of java.util.Date converted to java.sql.Timestamp via JDBC Thin.
                 Key: IGNITE-13233
                 URL: https://issues.apache.org/jira/browse/IGNITE-13233
             Project: Ignite
          Issue Type: Bug
            Reporter: Alexander Lapin


In some cases, for example in case of new java.util.Date(Long.MAX_VALUE), milliseconds part of java.sql.Timestamp retrieved via JDBC has different value than previously putted via cache API java.util.Date.
Date.getTime() 9223372036854775*807*
Timestamp.getTime() 9223372036854775*191*

Reproducer org.apache.ignite.jdbc.thin.JdbcThinCacheToJdbcDataTypesCoverageTest#testDateDataType



--
This message was sent by Atlassian Jira
(v8.3.4#803005)