[ https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Kuznetsov updated IGNITE-9989: ------------------------------------ Comment: was deleted (was: So first results for select-range benchmarks: ||Vendor\Benchmark (Q/sec, Avg) ||SelectBySalary ||SelectByPk ||SelectBySalaryWithJoin ||SelectByPkWithJoin|| ||ignite thin inmemory |885.36 |1,030.81 |170.41 |189.30| ||ignite jdbc v2 inmemory |891.48 |1,046.89 |157.34 |170.51| ||ignite thin persistence |560.58 |669.73 |141.23 |146.14| ||ignite jdbc v2 persistence |582.89 |653.87 |128.28 |137.35| ||Mysql (tunned) |770.97 |786.83 |199.29 |237.16| ||PgSQL (tunned) |1,845.70 |1,795.23 |73.94 |74.05|) > JDBC v2: getPrimaryKeys always returns constant COLUMN_NAME, KEY_SEQ, PK_NAME > ----------------------------------------------------------------------------- > > Key: IGNITE-9989 > URL: https://issues.apache.org/jira/browse/IGNITE-9989 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.6 > Reporter: Pavel Kuznetsov > Assignee: Pavel Kuznetsov > Priority: Major > Labels: jdbc > > Jdbc v2 driver has hardcoded values for meta attibutes : > COLUMN_NAME = _KEY > KEY_SEQ = 1 > PK_NAME = _KEY > But this values should be different for different tables. > how to reproduce: > 1) connect to the cluser using jdbcv2 driver > 2) CREATE TABLE TAB (ID LONG, SEC_ID LONG, VAL LONG, PRIMARY KEY(ID, SEC_ID)) > 3) check result of connection.getMetadata().getPrimaryKeys() -- This message was sent by Atlassian JIRA (v7.6.3#76005)