ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-10745) SQL: jdbc metadata's getColumns returns wrong value for "ORDINAL_POSITION"
Date Thu, 20 Dec 2018 15:12:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-10745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725813#comment-16725813
] 

Pavel Kuznetsov edited comment on IGNITE-10745 at 12/20/18 3:11 PM:
--------------------------------------------------------------------

-Also see the same proble with indexes metadata- 
Upd: seems it's not


was (Author: pkouznet):
Also see the same proble with indexes metadata.

> SQL: jdbc metadata's getColumns returns wrong value for "ORDINAL_POSITION" 
> ---------------------------------------------------------------------------
>
>                 Key: IGNITE-10745
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10745
>             Project: Ignite
>          Issue Type: Bug
>          Components: jdbc, sql
>            Reporter: Pavel Kuznetsov
>            Priority: Minor
>              Labels: jdbc, metadata, sql
>
> Affected both thin and jdbc v2 drivers.
> jdbc spec says : 
> {noformat}
> ORDINAL_POSITION int => index of column in table (starting at 1)
> {noformat}
> but in fact it is a position in the metadata table itself, not position in the original
table. 
> For example we have table 
> {code:sql}
> Person(id int primary key, val1 int, val2 bigint, val3 int)
> {code}
> Oridinal number for {{val3}} is 4, but if we specified patterns that leave only 1 result
 ({{PUBLIC.Person.val3}}) returned value will be 1. If we select 2 columns by pattern - 2
or 1 and so on.



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

Mime
View raw message