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

Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2023/04/19 14:17:00 UTC

[jira] [Updated] (IGNITE-19321) move conversion SQL JDBC date/time from common place

     [ https://issues.apache.org/jira/browse/IGNITE-19321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yury Gerzhedovich updated IGNITE-19321:
---------------------------------------
    Labels: ignite-3  (was: )

> move conversion SQL JDBC date/time from common place
> ----------------------------------------------------
>
>                 Key: IGNITE-19321
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19321
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Priority: Major
>              Labels: ignite-3
>
> Move JDBC specific parameter conversation from common  ClientBinaryTupleUtils to another place. Need take into account that conversion should cover all JDBC SQL date/time interfaces and setObject() method.
> |prepStmt.setDate()|
> | prepStmt.setTime()|
> | prepStmt.setTimestamp()
> |
> |prepStmt.setObject()|
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)