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

Posted to dev@ignite.apache.org by pavel-kuznetsov <gi...@git.apache.org> on 2018/10/03 13:19:09 UTC

[GitHub] ignite pull request #4906: IGNITE-9606: JDBC getPrimaryKeys() returns wrong ...

GitHub user pavel-kuznetsov opened a pull request:

    https://github.com/apache/ignite/pull/4906

    IGNITE-9606: JDBC getPrimaryKeys() returns wrong value for COLUMN_NAME

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-9606

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4906.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4906
    
----
commit 5d144b2f57933b96dc4ccb68be119f7c205bb6f7
Author: Pavel Kuznetsov <pa...@...>
Date:   2018-10-02T14:43:31Z

    ignite-9606: Added test that reproduces the bug.

commit 0bf7d1c8265e681cdc5ea8b7d27c013844724be6
Author: Pavel Kuznetsov <pa...@...>
Date:   2018-10-03T13:02:42Z

    ignite-9606: fixed COLUMN_NAME metadata result.
    
    Earlier, if key was of SQL type (so not wrapped), corresponding property thought that it is not a key. This behaviour affected what COLUMN_NAME JDBC metadata would contain.

----


---

[GitHub] ignite pull request #4906: IGNITE-9606: JDBC getPrimaryKeys() returns wrong ...

Posted by pavel-kuznetsov <gi...@git.apache.org>.

Github user pavel-kuznetsov closed the pull request at:

    https://github.com/apache/ignite/pull/4906


---