[
https://issues.apache.org/jira/browse/IGNITE-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709985#comment-16709985
]
Pavel Kuznetsov commented on IGNITE-9989:
-----------------------------------------
Results for benchmarks that fetch all database:
||Vendor\Benchmark (Q/sec, Avg) ||SelectAll ||SelectAllJoin||
||ignite thin inmemory |1.28 |0.20|
||ignite jdbc v2 inmemory |1.52 |0.19|
||ignite thin persistence |0.91 |0.16|
||ignite jdbc v2 persistence |1.02 |0.16|
||Mysql (tunned) |1.69 |0.31|
||PgSQL (tunned) |4.29 |0.90|
> 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)
