You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andreas Korneliussen (JIRA)" <de...@db.apache.org> on 2006/04/11 10:29:20 UTC
[jira] Oppdatert: (DERBY-1177) updateObject with null as argument
causes network driver to fail with NullPointerException
[ http://issues.apache.org/jira/browse/DERBY-1177?page=all ]
Andreas Korneliussen updated DERBY-1177:
----------------------------------------
Derby Info: [Patch Available, Regression, Release Note Needed] (was: [Patch Available, Regression])
Release Note:
The following changes have been made to the Derby client driver:
Derby no longer throws an exception if ResultSet.updateObject(..) is called with a null as parameter. Instead it will update the column with a SQL NULL value.
After calling ResultSet.updateObject(..) with null as parameter, or after calling ResultSet.updateNull(..), ResultSet.wasNull() will return true, and ResultSet.getObject() will return null. Previously Derby would incorrectly return the old value for the column.
The Derby embedded jdbc driver behaves the same way w.r.t this behavior.
> updateObject with null as argument causes network driver to fail with NullPointerException
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-1177
> URL: http://issues.apache.org/jira/browse/DERBY-1177
> Project: Derby
> Type: Bug
> Components: Network Client
> Versions: 10.2.0.0
> Reporter: Andreas Korneliussen
> Assignee: Andreas Korneliussen
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-1177.diff, DERBY-1177.stat, DERBY-1177v2.diff, DERBY-1177v2.stat, DERBY-1177v3.diff, UpdateXXXTest.java, derbyall_report.txt, derbyall_report.txt
>
> Calling ResultSet.updateObject(column, object) causes the network driver to give NullPointerException if the object parameter is null.
> Stack trace from test:
> Test output:
> ........E.
> Time: 7.597
> There was 1 error:
> 1) testUpdateObjectWithNull(org.apache.derbyTesting.functionTests.tests.jdbcapi.UpdateXXXTest)java.lang.NullPointerException
> at org.apache.derby.client.am.CrossConverters.setObject(CrossConverters.java:845)
> at org.apache.derby.client.am.ResultSet.updateObject(ResultSet.java:3073)
> at org.apache.derbyTesting.functionTests.tests.jdbcapi.UpdateXXXTest.testUpdateObjectWithNull(UpdateXXXTest.java:215)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> Will attach the test.
> To run:
> java -Dframework=DerbyNetClient org.apache.derbyTesting.functionTests.harness.RunTest jdbcapi/UpdateXXXTest.junit
> The test does not fail with the embedded framework.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira