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

Posted to dev@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/07/24 09:58:00 UTC

[jira] [Created] (IGNITE-12009) Clarify java.time.LocalTime mapping in SQL queries

Ivan Pavlukhin created IGNITE-12009:
---------------------------------------

             Summary: Clarify java.time.LocalTime mapping in SQL queries
                 Key: IGNITE-12009
                 URL: https://issues.apache.org/jira/browse/IGNITE-12009
             Project: Ignite
          Issue Type: Task
          Components: sql
    Affects Versions: 2.7.5
            Reporter: Ivan Pavlukhin


Currently mappings between, java.time. java.sql and h2 temporal types provokes some surprising behavior. Need to figure out if there are bugs or it is an expected behavior.

One example is using java.time.LocalTime as QueryEntity field. If a value of such column is modified by SQL {{UPDATE}} then precision more than milliseconds is lost.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)