[GitHub] ignite pull request #2506: IGNITE-6125 Increase robustness of JDBC Metadata

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #2506: IGNITE-6125 Increase robustness of JDBC Metadata

andrey-kuznetsov
GitHub user alamar opened a pull request:

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

    IGNITE-6125 Increase robustness of JDBC Metadata

    Avoid toUpperCase() where possible.
    Check that catalog matches to empty catalog.
    Ported several tests from Thin driver implementation.
    Fixed faulty toUpperCase() in Primary Keys metadata.

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

    $ git pull https://github.com/alamar/ignite ignite-6125

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

    https://github.com/apache/ignite/pull/2506.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 #2506
   
----
commit 0936d9e8ebbb4b4f4450a915791de728eaa6e845
Author: Ilya Kasnacheev <[hidden email]>
Date:   2017-08-18T11:40:42Z

    IGNITE-6125 Increase robustness of JDBC Metadata
   
    Avoid toUpperCase() where possible.
    Check that catalog matches to empty catalog.
    Ported several tests from Thin driver implementation.
    Fixed faulty toUpperCase() in Primary Keys metadata.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #2506: IGNITE-6125 Increase robustness of JDBC Metadata

andrey-kuznetsov
Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---