cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-2956) JDBC ResultSet improperly handles null column values
Date Wed, 27 Jul 2011 17:28:09 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-2956:
--------------------------------------

    Affects Version/s:     (was: 0.8.2)
        Fix Version/s:     (was: 0.8.3)

> JDBC ResultSet improperly handles null column values
> ----------------------------------------------------
>
>                 Key: CASSANDRA-2956
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2956
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Drivers
>            Reporter: Rick Shaw
>            Assignee: Rick Shaw
>            Priority: Minor
>              Labels: JDBC
>         Attachments: jdbc-bugfix-handling-null-values.txt
>
>
> JDBC {{ResultSet}} getters return built-in datatypes such as {{int, long, short, byte,
boolean}} that are not capable of handling a null value. As a consequence, it provides a method:
{{wasNull}} which returns true if the value was null. The spec requires a zero numeric value
(or false in the case of {{boolean}} ) is returned by the getter. This was being mis-handled
and a null value was being cast (boxed) to the return value. An NPE would result.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message