[GitHub] ignite pull request #1210: IGNITE-4175: SQL: JdbcResultSet class wasNull() m...

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

[GitHub] ignite pull request #1210: IGNITE-4175: SQL: JdbcResultSet class wasNull() m...

andrey-kuznetsov
GitHub user AMashenkov opened a pull request:

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

    IGNITE-4175: SQL: JdbcResultSet class wasNull() method should return true on column NULL value.

    JdbcResultSet.wasNull() method should return null on column NULL value, if column value is null String.


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

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

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

    https://github.com/apache/ignite/pull/1210.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 #1210
   
----
commit 76b89dc43d8902dc8532f43ea0a631fb441fe10f
Author: Andrey V. Mashenkov <[hidden email]>
Date:   2016-11-03T19:10:41Z

    Trivial fix.
   
    JdbcResultSet.wasNull() method should return null on column NULL value.

----


---
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 #1210: IGNITE-4175: SQL: JdbcResultSet class wasNull() m...

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

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


---
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.
---