[
https://issues.apache.org/jira/browse/DERBY-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen resolved DERBY-6081.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
Thank you, Bryan!
The test run failed in Changes10_10.testFloatLimits() and
SystemPrivilegesPermissionTest.policyTestDatabasePermissionGrants(). The former
also fails in the continuous testing, and the latter fails on Java 8 in my
environment without the patch, so I believe they are both unrelated to my patch.
Committed revision 1448278.
> JDBC 4.2 setObject() and updateObject() methods throw NPE when type is null
> ---------------------------------------------------------------------------
>
> Key: DERBY-6081
> URL: https://issues.apache.org/jira/browse/DERBY-6081
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.10.0.0
> Reporter: Knut Anders Hatlen
> Assignee: Knut Anders Hatlen
> Fix For: 10.10.0.0
>
> Attachments: d6081-1a.diff
>
>
> If the SQLType argument to the new JDBC 4.2 methods in PreparedStatement and
> ResultSet is null, the call will fail with a NullPointerException. It should
> fail with an SQLException.
> Stack trace on embedded:
> java.lang.NullPointerException
> at org.apache.derby.impl.jdbc.Util42.getTypeAsInt(Util42.java:57)
> at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement42.setObject(EmbedPreparedStatement42.java:57)
> Stack trace on client:
> java.lang.NullPointerException
> at org.apache.derby.client.am.Utils42.getTypeAsInt(Utils42.java:55)
> at
> org.apache.derby.client.am.PreparedStatement42.setObject(PreparedStatement42.java:78)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
