[
https://issues.apache.org/jira/browse/DERBY-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-5534:
----------------------------------
Issue & fix info: Newcomer,Repro attached
Urgency: Normal
Labels: derby_triage10_9 (was: )
Triage for 10.9. Marking normal urgency also Newcomer. Verified this test
still fails when enabled for client. I am not totally sure what happens to the
value, does something get updated since there is no exception?
This test in ParameterMappingTest
// Remove test when DERBY-5534 is fixed
if (usingEmbedded()) {
assertUpdateState(rs, "F04",
_X, Float.NaN, XXX_FLOAT, "22003");
assertUpdateState(rs, "F04",
_X, Double.MIN_VALUE, XXX_DOUBLE, "22003");
// REAL DB2 limits: remove if DERBY-3398 is implemented
assertUpdateState(rs, "F04", bdSmallestPosFloatValue, "22003");
assertUpdateState(rs, "F04", bdSmallestNegFloatValue, "22003");
assertUpdateState(rs, "F04", bdMaxFloatValue, "22003");
assertUpdateState(rs, "F04", bdMinFloatValue, "22003");
}
here was 1 failure:
)
testDerby5533UpdateXXX(org.apache.derbyTesting.functionTests.tests.jdbcapi.ParameterMappingTest)junit.framework
ionFailedError: exception expected
at
org.apache.derbyTesting.functionTests.tests.jdbcapi.ParameterMappingTest.assertUpdateState(ParameterMap
t.java:5051)
at
org.apache.derbyTesting.functionTests.tests.jdbcapi.ParameterMappingTest.testDerby5533UpdateXXX(Paramet
ngTest.java:4775)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
FAILURES!!!
Tests run: 18, Failures: 1, Errors: 0
> ResultSet#updateFloat, #updateDouble do not check for NaN and other
> conditions on client
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-5534
> URL: https://issues.apache.org/jira/browse/DERBY-5534
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.8.2.2
> Reporter: Dag H. Wanvik
> Priority: Minor
> Labels: derby_triage10_9
>
> In updateXXX, where XXX is one of Float or Double, embedded throws value out
> of range when the argument is Float.NaN or Double.NaN, the client does not
> catch it.
> The server will balk when the row is updated, though, in ResultSet#updateRow.
> It will be more regular if this is caught in updateXXX also on the client as
> other range errors are. The SQL state seen is 22003, which is what embedded
> throws on updateXXX. See also DERBY-5533.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
