You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Kuznetsov (JIRA)" <ji...@apache.org> on 2019/03/13 17:28:00 UTC

[jira] [Updated] (IGNITE-11538) SQL: Support new features (precision, scale, etc) in JDBC drivers

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

Pavel Kuznetsov updated IGNITE-11538:
-------------------------------------
    Description: 
Currently JDBC result set meta data return dummy value (0) for the precision and scale, but we already have all the info to return correct values.

*Both thin and v2 driver are affected.*

See 
{{org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata#getPrecision}} - dummy 0
{{org.apache.ignite.internal.processors.odbc.jdbc.JdbcQueryCursor#meta}} - thin driver actually uses v1 version of the JdbcColumnMeta; {{org.apache.ignite.internal.jdbc.thin.JdbcThinResultSetMetadata#getPrecision}} ignores precision and returns 0;

  was:
Currently JDBC result set meta data return dummy value (0 or -1 depending on the driver) for the precision and scale, but we already have all the info to return correct values.

*Both thin and v2 driver are affected.*

See 
{{org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata#getPrecision}} - dummy 0
{{org.apache.ignite.internal.processors.odbc.jdbc.JdbcQueryCursor#meta}} - thin driver actually uses v1 version of the JdbcColumnMeta which returns -1 


> SQL: Support new features (precision, scale, etc) in JDBC drivers
> -----------------------------------------------------------------
>
>                 Key: IGNITE-11538
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11538
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Pavel Kuznetsov
>            Priority: Major
>
> Currently JDBC result set meta data return dummy value (0) for the precision and scale, but we already have all the info to return correct values.
> *Both thin and v2 driver are affected.*
> See 
> {{org.apache.ignite.internal.jdbc2.JdbcResultSetMetadata#getPrecision}} - dummy 0
> {{org.apache.ignite.internal.processors.odbc.jdbc.JdbcQueryCursor#meta}} - thin driver actually uses v1 version of the JdbcColumnMeta; {{org.apache.ignite.internal.jdbc.thin.JdbcThinResultSetMetadata#getPrecision}} ignores precision and returns 0;



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)